Practitioners often describe their role as advisory. They provide insight, surface risks, and suggest options. They do not decide. That boundary is appropriate.
But there is a second boundary that is less frequently examined: the line between offering interpretation and actively advocating for structural correction.
Why advisory distance feels safe
Maintaining distance protects objectivity. It avoids being perceived as political, reduces exposure, and preserves neutrality across stakeholders. But distance can also dilute influence.
If a practitioner identifies authority ambiguity yet frames it tentatively, the system may treat it as optional. Advisory language can soften structural reality. “Something to consider” does not carry the same weight as “This condition will continue to destabilise outcomes.” The difference is not tone.1 It is commitment.
When advocacy becomes necessary
Advocacy does not mean siding with a faction. It means standing behind a structural interpretation — being clear that incentive misalignment is driving behaviour, that decision rights ambiguity is producing repeated escalation, that portfolio saturation is creating performance variance.
Without that clarity, the organisation may interpret recurring instability as effort deficit rather than design issue. Advocacy, in this sense, is architectural insistence.2
Advocacy carries risk. It may challenge executive assumptions, create discomfort in the room, or slow momentum. But avoiding advocacy carries risk as well. It leaves structural conditions unchallenged. Over time, the practitioner may become valued for insight but not for stabilisation — advisory in language but limited in influence.
The consequence of blurred boundaries
When practitioners remain permanently advisory and never advocate for structural clarity, instability persists, conversations repeat, and facilitation cycles continue. The practitioner becomes part of the reinforcement loop.3 Not intentionally. But through restraint.
Boundary discipline, then, is not about staying out of politics. It is about knowing when architectural clarity requires stronger language.
Responsible advocacy is precise, not dramatic. It states: “If authority remains distributed this way, this pattern will continue.” It links observation to design, makes consequence visible, does not accuse — it clarifies.4
The boundary between advice and advocacy determines whether practitioners merely interpret instability or help alter it. Too much neutrality softens structural truth. Too much advocacy without discipline becomes political. The balance requires judgement.
This is one way of understanding how practitioner stance interacts with diagnostic integrity and sponsorship architecture to either interrupt or reinforce systemic instability.
-
O’Neill, M. B. (2002). Executive Coaching with Backbone and Heart: A Systems Approach to Engaging Leaders with Their Challenges. Jossey-Bass. O’Neill’s framework distinguishes between practitioners who have “heart” (relational attunement, sensitivity to impact) and those who combine this with “backbone” — the willingness to hold a structural position even when it creates discomfort. The difference between “something to consider” and “this condition will continue to destabilise outcomes” is the presence or absence of backbone: the first invites the client to choose whether to engage with the concern; the second names the consequence of not engaging. That is not a tonal difference. It is a commitment to the accuracy of the structural interpretation. ↩︎
-
Pfeffer, J. (1981). Power in Organizations. Pitman. Pfeffer demonstrates that effective influence in organisational settings requires active framing of structural conditions, not passive provision of information. Organisations do not automatically draw the correct structural conclusions from diagnostic data — they require someone to assert those conclusions with sufficient confidence to make them actionable. The practitioner who merely offers “something to consider” has not entered the influence process at the level required to shift how the organisation understands its own design. Advocacy — the insistence that a structural condition is real and consequential — is the mechanism by which structural interpretation becomes actionable. ↩︎
-
Argyris, C. (1990). Overcoming Organizational Defenses: Facilitating Organizational Learning. Allyn & Bacon. Argyris describes “skilled incompetence” — the phenomenon by which highly capable practitioners become most effective at maintaining dysfunction because their skill at managing relationships prevents them from surfacing the double-loop questions that would interrupt it. A practitioner who is permanently advisory and never advocates for structural clarity has become skilled at the wrong thing: they have mastered the management of conversation while leaving the structural conditions that make those conversations necessary untouched. Through restraint, they become part of the loop. ↩︎
-
Schein, E. H. (1999). Process Consultation Revisited: Building the Helping Relationship. Addison-Wesley. Schein argues that the diagnostic phase of process consultation requires naming structural conditions explicitly — not suggesting them, not implying them, but saying what they are and what they produce. This naming is the precondition for the client having access to the correct level of the problem. The practitioner who softens structural diagnosis with tentative language prevents the client from engaging with the condition that actually needs to change. Responsible advocacy is not confrontation; it is the precision that makes the structural condition visible and therefore addressable. ↩︎