9 problems the Adaptive Organization helps you solve.
A field guide to the organizational tensions the AO Method diagnoses and redesigns — beyond framework compliance.
01
Problem 01
Framework theater: teams “do agile,” the org stays rigid
Scrum, SAFe, Kanban, and DevOps run perfectly at team level — while decision rights, interfaces, and structure never change. AO reads coherence of the whole system, not compliance of a single practice.
Framework vs. systemOperating model designStructural coherence
02
Problem 02
Change that never becomes transformation
New roles, rituals, and reorganizations — without any shift in identity, decision rights, or culture. AO separates surface change from transformation of operating logic.
Decision rightsOperating logicIdentity shift
03
Problem 03
Strategy that never reaches the front line
Leadership intent stalls before it becomes local decisions and trade-offs. AO uses Hoshin Kanri, catchball, and a vision–strategy–tactics cascade to keep intent traceable to action.
Blurred ownership and executive decision bottlenecks
Escalation paths are unclear and authority pools at the top, creating latency everywhere below it. AO maps decision flow the way VSM thinking maps value flow.
Decision flowAuthority mappingEscalation design
05
Problem 05
Local agility, global chaos
Individual teams are fast and adaptive — the enterprise around them stays incoherent. AO’s five-dimension lens (Deliver, Demand, Capacity, Capability, Organisation) names the systemic constraint before prescribing a fix.
Nice meetings mask misalignment, conflict avoidance, and undiscussables. AO diagnostics separate surface civility from substantive candor.
Candor vs. politenessPsychological safetyUndiscussables
07
Problem 07
M&A integration that stalls after day one
Two systems merge on paper but never truly integrate decision flow or culture. AO applies a Diagnose–Design–Pilot–Scale loop with flocking primitives — alignment, cohesion, separation, avoidance — for day-one coordination.
Transformation fatigue and AI-driven change that dictates people
Another initiative, another tool rollout — trust and adaptive capacity erode with each cycle. AO treats ERP and AI as accelerants that must land on redesigned human decision flow, not replace it.
One method, read as a design problem — not a checklist.
The AO Method diagnoses decision flow, culture, structure, and adaptive capacity as one connected system — then redesigns it with you, not for you. Curious where your organization sits? Start with an AO Health Check across the Deliver, Demand, Capacity, Capability, and Organisation dimensions.
Internal coaching supervision for agile leaders presents a set of challenges that are structurally different from external coaching supervision. When a coach operates inside an organization — whether as an embedded agile coach, a leader-as-coach, or an internal AO practitioner — the layered power relationships of hierarchy, role ambiguity, organizational loyalty, and confidentiality create tensions that can undermine both the quality of coaching and the psychological safety of all parties. This report identifies the unique challenges, maps the dominant power dynamics at play, and provides practical frameworks and strategies to navigate them effectively.
Why Internal Coaching Supervision Is Uniquely Complex
Internal coaches operate in dynamic, constantly changing organizations and face multiple unique challenges not common to external coaches. The core structural tension is the dual role: the internal coach is simultaneously an employee and a coach, which creates inherent conflict around confidentiality, neutral positioning, and organizational loyalty — especially when the organization’s priorities conflict with individual client needs.
For agile leaders specifically, this complexity is amplified. They are often “stuck in the middle,” holding simultaneous pressure from executives above who expect delivery and alignment, and from teams below who need psychological safety, empowerment, and autonomy. Adding a supervision relationship to this structure introduces yet another layer: who holds power over whom, and in whose interest does the supervision serve?
Without proper supervision support, these dynamics lead to predictable failure modes: loss of perspective, enmeshment in organizational conflicts, erosion of coaching quality, and ultimately burnout.
The Power Dynamics at Play
1. Hierarchical Power
Even when an agile coach or leader-coach has no formal authority over a supervisee, their organizational rank creates implicit power. Supervisees may withhold sensitive cases, avoid bringing “failure” stories, or self-censor when they fear that information will circulate in performance evaluations, team assignments, or leadership assessments.
The supervisor’s rank — whether they are a senior leader, an organizational development expert, or a designated internal coach supervisor — carries inherent authority that can “lead to anxiety on the part of the supervisee, and even fear”. The risk is that supervision becomes an evaluative relationship rather than a reflective one, shutting down the very vulnerability that makes supervision valuable.
2. Dual Relationships and Role Confusion
Coaching within the same organizational system heightens power dynamics even when formal authority does not exist. When an agile leader coaches their own team members and simultaneously receives or provides supervision, multiple relationship layers overlap. Supervisees may be unsure which “hat” is being worn — colleague, coach, supervisor, or peer — leading to confusion, mistrust, and compromised safety.
Dual relationships introduce specific risks:
Blurred boundaries: Harder to keep interactions within the contracted scope of the coaching or supervision relationship.
Conflicts of interest: The agile leader’s organizational role may unconsciously influence how they coach or what they bring to supervision.
Loss of objectivity: Pre-existing knowledge of colleagues or organizational politics makes neutral presence difficult.
Unconscious games: Leader-coaches are susceptible to parent-child dynamics with team members, which can replicate in the supervision relationship itself.
3. Confidentiality Under Organizational Pressure
Confidentiality is both a practical and ethical challenge in internal supervision. Clients (coachees or leaders in supervision) may reasonably question whether their reflections could influence promotion decisions, performance reviews, or team restructuring — even if the supervisor has no formal mandate to share information.
The question is not only “what is kept confidential” but “is absolute confidentiality even possible inside an organization?”. When supervision is embedded in an internal coaching program, there is often an implicit expectation from the organization (sponsor) that some accountability information will flow back. Without explicit contracting, this ambiguity corrodes trust and safety.
4. Systemic Enmeshment and Loss of “Balcony” Perspective
Internal agile coaches and leaders risk becoming so entangled in the organizational system that they lose the “balcony view” necessary for effective coaching and supervision. This manifests as:
Normalization of toxic dynamics (accepting dysfunction as “just how things work here”)
Unconscious collusion with leadership narratives that serve the organization at the expense of teams
“No-one speaking truth to power,” where coaches internalize a culture of silence around senior-level bullying or political behavior
The longer the coach is embedded in the system, the more their perception becomes shaped by the system’s own assumptions, making the external supervisor (or external supervision element) essential.
Key Challenges in Practice
Challenge
Internal Context
Supervision Risk
Dual loyalty
Coach serves both organization and individual
Supervision colluded into organizational agenda
Confidentiality
Information circulates within same system
Coachees self-censor; cases not fully explored
Power imbalance
Supervisor may be senior in hierarchy
Supervisee withholds vulnerability; fear of evaluation
No clear separation between coaching, management, consulting
Standards drift; harm risk increases
Strategies for Navigating Power Dynamics
1. Name the Power Dynamic Explicitly
The first and most important step is to make power dynamics visible rather than leaving them latent. At the start of a supervision relationship, the supervisor should explicitly acknowledge:
The natural hierarchy within the relationship and what it does or does not imply
How the supervisor and supervisee feel about sharing vulnerable or uncertain topics in this organizational context
Moments when the supervisor recognizes they are “leading” rather than co-exploring
Naming the dynamic removes its invisibility and creates space for open, honest dialogue. This is a relational act, not a procedural one: it must be revisited regularly, not just stated once at contracting.
2. Invest Deeply in Tripartite Contracting
Arguably, the most common cause of problems in organizational coaching — and therefore in supervision — is a mismatch of expectations at the contracting stage. For internal coaching supervision involving agile leaders, a tripartite contract between supervisor, supervisee-coach, and organizational sponsor is essential.
The C.O.N.T.R.A.C.T. model offers a structured map:
C – Context & Purpose: Why is supervision happening? Who commissioned it and why?
O – Outcomes & Objectives: What does the supervisee-coach want to develop?
N – Norms & Ethics: Which ethical framework applies (ICF, EMCC, AC)? How will ethical dilemmas be handled?
T – Terms & Practicalities: Frequency, format, duration, virtual or in-person
R – Roles & Responsibilities: What does the supervisor do? What does the supervisee bring?
A – Agreements on Confidentiality: What is shared with the sponsor, and in what form?
C – Closure: What are the review points and exit conditions?
In the three-way contracting meeting with the organizational sponsor, key commitments to establish include: that the supervisor will not provide performance feedback to the sponsor unless explicitly agreed with the supervisee; that coaching insights will not be used in evaluations; and that the sponsor’s role is support, not oversight.
3. Use the 7-Eyed Model as a Systemic Navigation Tool
The Seven-Eyed Model (Hawkins & Shohet) is one of the most widely used frameworks in coaching supervision and is directly applicable to agile leadership contexts. It offers seven lenses through which to examine what is happening in the supervision space:
The client and their story — What is the coachee (the agile team or leader) actually bringing?
The coach’s interventions — How is the agile coach/leader working with the situation?
The coach–client relationship — What dynamics exist between coach and coachee?
The coach’s own process and feelings — What is being triggered in the supervisor?
The supervisory relationship — What is happening between supervisor and supervisee right now?
The supervisor’s own process — What is the supervisor bringing from their own system?
The wider organizational context — How is the organizational system shaping everything above?
For agile leaders, Eye 7 (the organizational system) is particularly important and often under-examined. Using this lens helps supervision avoid being only a “case clinic” and instead examines how structural power, culture, and transformation pressures shape both the coaching work and the supervision conversation.
4. Separate Supervision from Performance Management
A clear structural distinction must be made between supervision (developmental, reflective, confidential) and performance management (evaluative, organizational, hierarchical). Without this separation:
Internal coaches will self-censor and bring only “safe” cases to supervision
The supervision space becomes contaminated by organizational politics
Ethical dilemmas will not surface until they become crises
In practice, this means the supervisor should hold no formal evaluative power over the supervisee in the organizational hierarchy. Where this is not structurally possible — as in many lean agile organizations — the supervisor must make the developmental intent of supervision explicit through contracting, re-contracting regularly, and modeling the humility and vulnerability they wish the supervisee to bring.
5. Introduce External Supervision as a Complement
For cases involving toxic dynamics, conflicts of interest, or deep enmeshment, external supervision is often the most responsible option. External supervisors bring:
A fresh, independent perspective untainted by organizational history
Ability to challenge assumptions that internal supervisors may share
A safe container for ethical dilemmas that are “forbidden to discuss with a colleague”
Accountability and quality assurance outside the organizational reporting structure
A blended model — internal group supervision for routine developmental reflection, plus periodic external individual supervision for high-complexity cases — offers both accessibility and independence.
6. Build Psychological Safety Through Preparation and Co-Creation
Group coaching supervision in agile contexts faces particular challenges: differences in coaching styles, personalities, cultural nuances, and power differences between participants can lead to conflict, misunderstanding, and rupture. Strategies to address this include:
Psychological contracting at setup: Establish clear ways of working, including confidentiality norms, respect, and active listening, before any case work begins.
Surfacing rank and privilege: Explicitly discuss whether power, rank, or organizational proximity may be affecting participation.
Preparation rituals: Ask supervisees to reflect on their practice, identify a challenge, and set a session intention before each meeting.
Regular feedback loops: Build in structured feedback — not only on cases, but on the group’s own dynamics and the supervisor’s facilitation.
7. Model Supervisory Reflexivity
Supervisors have a responsibility to model how power can be used constructively. Supervisors who demonstrate humility, curiosity, and openness — including naming their own uncertainties and blind spots — create permission for supervisees to do the same. This is especially important in agile cultures that espouse transparency and learning but often struggle to enact these values at the leadership level.
The supervisor of supervisors (meta-supervision) dimension is equally important: supervisors of internal agile leader coaches should themselves receive supervision, ensuring that the reflective practice loops outward rather than terminating at the internal layer.
Specific Risks in Agile Transformation Contexts
Agile transformations add layers of complexity not present in standard organizational coaching:
Framework pressure: Agile leaders are expected to adopt and role-model specific practices (Scrum, Kanban, OKRs). Supervision cases may be unconsciously filtered through “are we doing agile right?” rather than “what is this person actually needing?”
Sponsor–coach collusion: An agile coach acting as internal supervisor may reinforce an organization’s agile “story” rather than challenging it, especially when the transformation is tied to the coach’s own professional identity or the AO Method being implemented.
Restorative underinvestment: Agile transformations are high-pressure; the restorative function of supervision (processing stress, role conflicts, emotional load) is often neglected in favor of the formative function (skill building). This increases burnout risk.
Ethical ambiguity in hybrid roles: An agile leader simultaneously coaching team members, attending retrospectives, writing performance reviews, and influencing roadmap priorities cannot maintain clean coaching boundaries without explicit, ongoing contracting.
Recommendations for AO Method Practitioners and Internal Agile Leaders
Contract explicitly for power: At every new supervision relationship, name the organizational power hierarchy and agree on what it does and does not mean for the supervision space.
Adopt a systemic model: Use the 7-Eyed Model or equivalent to ensure supervision addresses the organizational context, not only the coach–coachee dyad.
Separate evaluation from reflection: Ensure that the supervisor holds no evaluative function over the supervisee in the same period and context as the supervision relationship.
Use tripartite contracting: Always involve the organizational sponsor in initial contracting to align expectations on confidentiality, outcomes, and accountability — and document agreements explicitly.
Blend internal and external supervision: Reserve internal supervision for formative and peer-reflective work; use external supervision for restorative, ethical, and high-complexity cases.
Revisit contracts regularly: Power dynamics, organizational contexts, and role configurations shift continuously in agile organizations; supervision contracts must be living documents, not one-time agreements.
Model vulnerability from the top: Leaders who receive and are transparent about their own supervision involvement normalize reflective practice and signal genuine commitment to psychological safety across the system.
Politeness, candor, and feedback in adaptive organizations.
This page turns the paper into a readable editorial experience with a Swiss-modern consulting aesthetic: restrained, precise, and built for executive reading.
Executive summary
Why this paper matters
Many organizations confuse politeness with maturity, health, or alignment. In practice, politeness is a social coordination device, while truth is a question of whether relevant reality becomes discussable in time.
This distinction matters in transformation work because polite systems often hide risk, delay escalation, and weaken learning. Adaptive organizations need a design that protects dignity without suppressing candor.
Section 01
The assumption: politeness does not guarantee truth
Politeness and truth belong to different domains. One regulates social friction; the other regulates epistemic quality. A team may therefore appear composed, collegial, and professional while still failing to surface disagreement, error, or structural tension.
For leaders, the practical question is not whether the atmosphere feels smooth. It is whether the organization can process inconvenient signals before they become expensive consequences.
Section 02
Radical candor as disciplined respect
Radical candor is useful precisely because it refuses the false choice between kindness and challenge. The aim is neither aggression nor soft avoidance, but direct feedback delivered in a way that preserves dignity and improves usefulness.
When care lacks challenge
People protect feelings in the short term but leave capability gaps untouched. This usually feels humane in the moment yet often creates delayed frustration and mistrust.
When challenge lacks care
People hear contempt rather than commitment. The information may be technically correct, but the receiver experiences it as status threat rather than developmental support.
Section 03
Cognitive bias inside feedback conversations
Feedback is difficult because the brain does not process it as neutral data. It quickly entangles feedback with identity, competence, fairness, and belonging. Once that happens, bias shapes both how feedback is given and how it is interpreted.
Givers often distort through confirmation bias, attribution error, and courtesy bias.
Receivers often distort through negativity bias, self-serving bias, and belief perseverance.
The conversation itself becomes a fragile social arena where meaning and self-protection compete.
Section 04
Design feedback loops, not heroic conversations
Receiver bias cannot be removed, but it can be bounded by process. Organizations learn better when feedback is behavior-based, routine, multi-source, and framed as joint hypothesis testing rather than personal verdict.
That means using evidence, separating observation from interpretation, inviting the receiver’s meaning-making, and looking for patterns across time rather than overreacting to single episodes.
Section 05
Psychological safety in performance reviews
Performance reviews are especially sensitive because they combine evaluation, hierarchy, and future consequences. Without psychological safety, the review becomes a ritual of impression management instead of a learning device.
What increases safety
Transparent criteria, year-round conversation, specific evidence, employee voice, and leaders who model vulnerability.
What destroys safety
Ambiguous standards, surprise judgments, diplomatic vagueness, one-way verdicts, and punitive reactions to dissent.
Section 06
Operating principles for healthier feedback cultures
Respect people, test interpretations
Protect dignity while keeping assumptions discussable.
Leaders must receive feedback, not only administer it.
Design for bias
Use multiple perspectives, reflection prompts, and recalibration points.
Translate truth into learning
The organizational task is not harmony alone, but usable adaptation.
The central proposition is simple: organizational adaptability depends less on surface harmony than on the system’s capacity to convert uncomfortable truth into shared learning.
Distinguishing between local autonomy and organizational risk is one of the trickiest balances in AO work. The goal is not to choose one over the other, but to make the boundary explicit so teams can move fast where it is safe and slow down where it genuinely matters.
The core distinction
Local autonomy is the freedom of a team to decide how they work, what they prioritize within their mandate, and which local trade-offs they make — without seeking permission upward.
Organizational risk is exposure that, if a decision goes wrong, spills beyond the team: legal, financial, safety, reputational, security, or systemic consequences that affect others who did not make the call.
The principle: autonomy should be wide where blast radius is small and reversible; constrained where blast radius is large and irreversible.
A simple test for any decision
Ask three questions:
Reversibility — Can we undo this within days at low cost? (Reversible = lean toward autonomy.)
Blast radius — Does the downside stay inside the team, or spill onto customers, other teams, regulators, or the brand? (Contained = autonomy; spreading = shared/escalated.)
Correlation — If every team made this same call independently, would the aggregate create a systemic problem? (e.g., each team picking its own data-handling approach creates a compliance risk no single team can see.)
If all three point local, delegate fully. If any point to wide, irreversible, or correlated risk, that decision needs guardrails or escalation.
Decision categories
Category
Risk profile
Who decides
Reversible, contained
Low
Team, full autonomy, no notification
Reversible, visible to others
Low–medium
Team decides, informs affected parties
Hard to reverse, contained
Medium
Team decides within explicit guardrails
High blast radius or correlated
High
Escalate or decide against a shared policy
Legal / safety / security / brand
High
Always governed by org-level boundaries
How to make the boundary work in practice
Set guardrails, not approvals. Instead of “ask before X,” define the boundaries inside which teams are free: budget limits, risk appetite, mandatory standards (security, data, accessibility), and the few things that always require escalation. Within those lines, autonomy is real.
Name the few non-negotiables explicitly. Most organizations have a small set of genuine org-level risks. Make them a short, visible list rather than a vague sense that “leadership might not like this.”
Distinguish risk type from risk size. A team can have full autonomy over a high-effort decision that carries low organizational risk. Effort and risk are different axes.
Push the decision to where the knowledge is — unless the risk is shared. The team usually understands the local context best. The exception is when the consequences land on people who weren’t in the room.
Make correlated risk a leadership job. No single team can see that “everyone is independently doing the same risky thing.” Surfacing and governing correlation is precisely what the center is for.
Common failure modes
False autonomy — teams are told they’re empowered, but every meaningful decision quietly gets second-guessed. Result: people stop deciding.
Risk laundering — large organizational risks are pushed down to teams that lack the authority or visibility to carry them, so the org “feels agile” while exposure accumulates.
Blanket caution — treating all decisions as high-risk, which kills speed for the 90% that are actually reversible and contained.
Invisible boundaries — the line between “your call” and “needs escalation” exists only in leaders’ heads, so teams hesitate or guess.
A practical move
For one team this week, take five recurring decisions and sort them on two axes: reversibility (easy ↔ hard to undo) and blast radius (contained ↔ spreads beyond the team). Decisions in the easy/contained corner get full autonomy, made explicit. Decisions in the hard/spreading corner get a named guardrail or escalation path. The middle gets autonomy within stated limits. Write the result down where the team can see it — that visible map is usually what converts vague empowerment into confident, fast local decisions.
The aim is a system where teams rarely have to ask “am I allowed?” because they already know exactly where their freedom ends and shared risk begins.
Using the three supervision functions (normative, formative, restorative), the dual‑relationship situation surfaces different types of challenges. Each function highlights specific risks you would want to explore in supervision.
Normative function: ethics and standards
From a normative (ethical/standards) lens, challenges include:
Ambiguity about conflicts of interest and whether the dual relationship breaches your code of ethics or internal coaching policy (e.g. coaching someone you also appraise or influence organizationally).
Pressure from the organization or sponsor that pulls you away from agreed boundaries (e.g. requests for confidential information, subtle alignment with management’s agenda).
Formative function: learning and practice
From a formative (learning/development) lens, challenges include:
Limited skill or repertoire to work cleanly in a dual role: contracting. This includes resetting boundaries mid‑engagement. It also involves naming power dynamics in the room.
Your other role, whether HR, leader, or Agile coach, shapes your questions. It affects your challenge level and the topics you unconsciously avoid with this client.
Restorative function: well-being and impact on you
From a restorative (support/well-being) lens, challenges include:
Emotional strain arises from “split loyalties” between the client and the organization. There is also anxiety about “getting it wrong” ethically in a political system you belong to.
Over‑involvement or depletion: ruminating about the case. It includes difficulty switching off. You feel isolated because you can’t freely discuss it with internal peers due to confidentiality.
Systemic themes to surface in supervision
Across all three functions, supervision would explore:
How organizational culture (politics, expectations of HR/OD, leadership style) amplifies dual‑relationship risks for internal coaches.
What structures are missing or weak? These include policy, allocation rules, or access to external supervision. This issue is making you personally carry too much of the ethical and emotional load.
Internal coaches face several recurring ethical challenges, mostly around confidentiality, role conflict, and organizational power dynamics. Even when aligned with a formal code of ethics (e.g. ICF), the internal context makes these dilemmas more frequent and ambiguous.
Key ethical tensions
Confidentiality vs. sponsor expectations
Leaders or HR often expect detailed “updates” on the coachee’s progress or mindset. This expectation clashes with strict confidentiality obligations in most coaching codes.
Internal coaches can be formally or informally pressured to reveal sensitive information. This includes whether someone is a “flight risk”, under-performing, or critical of leadership. Such pressures directly test the code of ethics.
Conflict of interest and multiple roles
Internal coaches commonly hold another role, like manager, HR, OD, or Agile coach. This creates overlapping obligations and loyalties to the organization, the boss, and the client.
Expectations to “follow the boss’s directive” are a major source of pressure. This pressure often leads HR and internal practitioners to compromise ethical standards.
Perceived independence and psychological safety
Coachees not fully trust an internal coach’s independence. They fear that what they share harm their careers. This fear persists even if the coach adheres strictly to the code.
Organizational politics and informal networks can influence how people perceive the coach’s neutrality. They can also subtly shape which topics Coachees feel safe to explore.
Code of ethics specifics that get strained
Confidentiality and privacy
Professional frameworks (like ICF) emphasize that what is shared in sessions stays private unless explicitly agreed otherwise in the contract.
In internal coaching, standard HR practices (e.g. documenting risk, performance, misconduct) can clash with these commitments when the coach is also part of HR or management.
Autonomy and non-maleficence (no harm)
Ethical guidance highlights protecting client well‑being and autonomy, avoiding harm, and not exploiting the relationship.
Internal coaches are aware of organizational plans. These can include restructuring, layoffs, or performance procedures. These plans affect the client. But, coaches can’t always share them. This inability creates moral tension around “harm” and transparency.
Objectivity and avoiding misuse of power
Codes emphasize fairness, avoiding favoritism, and keeping clear boundaries with other roles.
Internal coaches are drawn into political games. They are used to influence employees towards certain decisions. Coaches also be subtly expected to “align” employees with management agendas rather than the client’s goals.
Typical dilemma patterns for internal coaches
Triangular relationship: sponsor–coach–Coachees
Ambiguity around what is shared at “three‑way” meetings (e.g. between HR, manager and Coachees) risks sliding from high‑level themes into personal details, breaching the code.
Misaligned expectations at the contracting stage can often lead to ethical conflict later in the engagement. The manager expects behavioral reports, but the coach promises confidentiality.
Boundary management and scope creep
Internal coaches can be asked to “just give some advice” on HR or performance issues. This can cross into consulting, assessment, or even disciplinary influence. These areas differ from coaching.
Coachees also seek special treatment or information since the coach is “on the inside”. This tests the boundary between coaching and confidential organizational knowledge.
Supervision and escalation challenges
Internal coaches sometimes lack a truly independent supervisor or ethics body inside the organization to discuss dilemmas safely.
Without clear internal policies and an external reference (e.g. ICF’s ethical complaint and review structures), coaches can feel isolated when they need to push back against senior leaders.
Practices that help uphold the code
Robust contracting and transparency
Clear three‑way contracting that spells out goals, reporting limits, and confidentiality boundaries from the start reduces later pressure and misunderstanding.
Documented coaching policies are aligned with a recognized code of ethics. They give internal coaches a formal reference when they need to say “no” to inappropriate requests.
Structural protections for independence
Some norms help preserve perceived and actual independence. One such norm is coaching outside one’s line of control. Another is having an independent ethics or review board.
Regular supervision, often with an external supervisor, aids reflection on ethical tensions. It also helps find blind spots and assess the impact of organizational politics on the coaching stance.
If helpful, the next step can be to map your specific internal role (e.g. HR, Agile coach, OD) against these patterns and design a tailored “ethical operating model” for your internal coaching practice.
Dual relationships are best handled by minimizing them where possible. When they can’t be avoided, it is important to make them highly explicit, contracted, and supervised. As an internal coach, that usually means separating roles structurally, naming conflicts early, and sometimes declining or ending coaching relationships.
Clarify what “dual relationship” means
A dual relationship exists when you and the Coachees have more than one role or relationship (e.g. coach and line manager, coach and HRBP, coach and close colleague/friend).
These situations create conflicts of interest and power imbalances. The ICF and EMCC codes need you to recognize, reveal, and manage or avoid these conflicts.
Design structural safeguards
Avoid coaching people where you have evaluative or formal power (direct reports, people you appraise, HR cases you manage). Swap coaches across units or levels instead.
Define in your internal coaching policy who internal coaches can and not coach (e.g. “never within own reporting line, never in active HR processes”).
Use transparent contracting
In the intake, name the dual role explicitly. You say, “I am both your Agile coach and your internal coach; here is how that will affect us.” Then explore risks together.
Build the dual role and its limits into the written coaching agreement: what you will not do (e.g. no performance advice, no participation in promotion decisions) and what happens if a conflict appears.
Monitor boundaries in practice
Regularly check: “Are my other roles influencing this conversation?” and “The client feel pressured because of my position?”
If topics drift into areas where your other role is dominant (e.g. HR investigation, performance rating), pause and either re‑route that topic to the appropriate process or end the coaching relationship for that issue.
Escalate, supervise, or step out
Use supervision (ideally external) to unpack any dual‑relationship tensions, blind spots, or emotional hooks before they harm the client.
If the conflict of interest can’t be mitigated, ethics guidance supports ending or transferring the coaching. For example, you must soon evaluate the Coachees. In such cases, it’s important to explain clearly why this step is necessary.
If you share your specific dual roles (e.g. “HR + internal coach for managers”), a concrete script and decision rules can be drafted for your context.
In a dual‑relationship case, HR gets involved when organizational risk or formal processes are triggered. An external supervisor is involved as soon as you feel ethically “stuck”. You should also involve them if you feel emotionally entangled or unsure how to continue. In practice, internal coaches are encouraged to consult supervision early. They should escalate to HR when the dilemma touches employment decisions. This includes policy breaches or potential harm to the client or others.
When to involve HR
Involve HR (or your equivalent role) when:
There is possible misconduct, discrimination, harassment, or safety risk disclosed in coaching. The organization is legally or ethically obliged to tackle these issues.
The dual relationship intersects with formal HR processes. These include performance management, restructuring, investigation, grievance, and whistle-blowing. You are expected to play a role in those processes.
You need to renegotiate the three‑way contract (sponsor–coach–Coachees). For example, do this if expectations on confidentiality have become misaligned. You should also do it if reporting has become impossible to honor.
When to seek external supervision
Seek an external (or at least independent) supervisor when:
You notice conflicting loyalties, strong emotions, or attraction. Over‑identification with the client can cloud your judgment in the dual relationship.
You are unsure whether to continue, refer, or terminate the coaching because of boundary issues or conflict of interest.
You need help to clarify options that protect client welfare. These options should respect the coaching code of ethics. They must also remain realistic in your internal political context.
How to decide whom to involve first
If the issue is primarily about organizational rules or employment risk, start with HR. Consult a trusted senior HR or ethics contact. Ideally, obtain the client’s knowledge where possible.
If the issue is primarily about your own boundaries, bias, or confusion, begin with external supervision. Consider a confidential ethics consultation. Then decide whether HR involvement is needed.
Good practice in a case study response
For a written case study or exam scenario, you can show ethical maturity by:
Stating that you would seek supervision early when a dual relationship emerges or shifts, to explore impact and options.
Explain clear criteria for HR escalation. These include risk, policy breach, and formal processes. State your intention to be transparent with the client about any need to involve HR.
Supervision coaching is a sophisticated method designed to support both coaches and the systems they are part of.
While coaching primarily focuses on deep listening, questioning, and guiding, supervision emphasizes advising, mentoring, and coaching.
Supervision focuses primarily on three approaches: formative, normative and restorative.
Formative: The Supervisor offers feedback and guidance. This helps the supervisee develop their skills, theoretical knowledge, and personal attributes. These improvements ultimately lead to the supervisee becoming a more competent practitioner.
Normative: The Supervisor and supervisee share the responsibility. They make sure that the supervisee’s work is professional. It operates ethically within the relevant codes, laws, and organizational standards.
Restorative:
Supervision in Agile?
Agile refers to the way agents interact within a system. It encompasses the behaviors of the team, the organization, and your individual responses.
The AO method is helping you to create Agile areas while addressing We, Me and US, or :
WE: How my team is working
ME: How I interact with my team? Am I a team member, or do I have team membership? Or I prefer to stand alone.
US: How the company is working. Here I have a membership.
Menschgeist is a wordplay with Mensch (Human) and Zeitgeist.
Our activities serve individuals, and their interactions.
Our unique approach is called AO (agile organization).
“AO stands for Agile Organizations, which is a straightforward framework designed to help your organization experiment with agile practices.
Organizations operate similarly to social networks, after a few fundamental principles:
Simple rules: The work game operates under very simple rules. The work and its environment can often be quite complex.
Alignment: The way people coordinate and connect with one another is crucial.
Cohesion: The factors that unite agents.
Separation: The elements that distinguish agents from one another.”
Avoidance: Make sure that every organization can prevent conflicts with other systems.
This picture depicts Mike Beedle. Mike was one of the authors of the Agile Manifesto for Software Development. He was also the co-author of Agile Software Development with Scrum.
I was honored to be asked by him to contribute to the creation of Enterprise Scrum. During our work, I added a missing piece to his work. Unfortunately, Mike passed without completing Enterprise Scrum. That missing piece, mostly based on organizational behavior, became the AO Model.
The bridge between Enterprise Scrum and AO was built on the experience layers:
EX : enterprise experience
SX : service experience
CX : customer experience
PX: people experience
During my research, OX or organizational experience as been added to the first concept. More here
