Challenge 01
Resistance to change
For teams where pushback keeps getting framed as attitude instead of a live system response.
Insights Field Guide
Choose the team problem you're facing, or follow a pathway through the core ideas.
This is not a blog archive. It is a practical map of recurring coaching situations, relational patterns, and deeper entry points into the work.
Start With The Challenge
Enter through the situation, not the publish date
Each route below gathers the most relevant published and in-development material for a recurring coaching problem. Choose one and the library will jump to that thread.
Challenge 02
Self-organisation breaking down
For delivery groups that look autonomous on paper but still stall around power, ownership, or dependency.
Challenge 03
Team drama and psychological games
For recurring rescuer, persecutor, and victim loops that keep burning time in ceremonies and stakeholder conversations.
Challenge 04
Psychological safety that feels performative
For environments that say the right words about candour but still punish risk, dissent, or bad news.
Challenge 05
Contracting and sponsor-team confusion
For engagements where expectations, authority, and accountabilities were never made explicit enough to hold.
Beyond Retros and Rituals: Co‑creative TA as a Relational Lens for Agile Team Coaching18 min read · PublishedThe Coach–Team–Sponsor Triangle in Practice11 min read · Published
The Contracting Canvas: A Walkthrough
8 min read · Coming next
Challenge 06
Hidden authority, role, and boundary problems
For situations where recurring friction is really about unclear role, task, or decision boundaries.
Read As A Pathway
Follow a route instead of starting from scratch
These guided paths sequence the available essays and upcoming pieces so readers can build context in a deliberate order.
5 steps · about 77 min
Start here: relational team coaching foundations
Build the core stance first: relational diagnosis, co-creative TA, and the difference between ritual and real contact.
Agile coaches and Scrum Masters building a stronger conceptual base.
- 1
Published · 18 min read
Beyond Retros and Rituals: Co‑creative TA as a Relational Lens for Agile Team Coaching - 2
Published · 12 min read
Resistance Is Relational, Not Just Personal - 3
Published · 14 min read
Why Self-Organisation Fails — and What to Do Instead - 4
Published · 16 min read
Primary Task: The One Question That Cuts Through Everything - 5
Published · 17 min read
The Double Task: What Coaches Are Always Working On (Whether or Not They Name It)
6 steps · about 76 min
Diagnosing stuck teams
Move from surface symptoms to sharper diagnosis when a team keeps repeating the same patterns.
Practitioners working with recurring dysfunction and unclear root causes.
- 1
Published · 14 min read
Why Self-Organisation Fails — and What to Do Instead - 2
Published · 10 min read
Stop the Drama: Coaching Teams Out of Psychological Games - 3
Published · 10 min read
BART for Agile Teams: A Practical Diagnostic for Hidden Dysfunction - 4
Published · 8 min read
Psychological Safety Theatre - 5
Published · 17 min read
The Under-Bounded Team: What Organisational Transition Actually Does to a Group - 6
Published · 17 min read
The Four Sources of Authority: Where Agile Teams Actually Authorise Each Other
6 steps · about 77 min
Working with power, resistance, and authority
Trace where resistance and role confusion actually come from, then choose interventions that fit the system.
Coaches, leads, and sponsors working in politically messy environments.
- 1
Published · 12 min read
Resistance Is Relational, Not Just Personal - 2
Published · 14 min read
Why Self-Organisation Fails — and What to Do Instead - 3
Published · 11 min read
The Coach–Team–Sponsor Triangle in Practice - 4
In Development · 8 min read
The Contracting Canvas: A Walkthrough
- 5
Published · 15 min read
The Wicked Problem the Sprint Cannot Solve - 6
Published · 17 min read
The Four Sources of Authority: Where Agile Teams Actually Authorise Each Other
10 steps · about 172 min
A Jungian lens on Agile team dynamics
Analytical psychology applied to Agile work — shadow, liminality, cultural complex, and the depth layer beneath surface dysfunction.
Coaches and practitioners ready to work with what teams cannot yet name.
- 1
Published · 18 min read
The Elected Carrier: How Agile Teams Create Scapegoats - 2
Published · 20 min read
The Company You're Still Carrying: Organisational Phantom Narratives - 3
Published · 22 min read
The Dissolution Before the Transformation: Why Agile Change Needs a Threshold - 4
Published · 16 min read
The Animus Trap: What Agile Measures and What It Silences - 5
Published · 14 min read
Communitas Is Not Team Building: Why Offsites Leave Everything Unchanged - 6
Published · 18 min read
What the Algorithm Cannot Hold: The Irreducible Human in Team Coaching - 7
Published · 20 min read
When Culture Is the Client: Coaching Agile in High Power Distance Teams - 8
Published · 16 min read
The Wound That Works: Why the Coach's History Is Always in the Room - 9
Published · 14 min read
The Inside-Out Coach: What Internal Agile Coaches Can't See and Why - 10
Published · 14 min read
When the Ceremony Dies: How Agile Rituals Lose Their Power and How to Restore It
8 steps · about 140 min
A group analytic lens on team dynamics
Bion, Foulkes, Argyris, and systemic thinking applied to Agile teams — the invisible processes beneath surface dysfunction.
Coaches and practitioners ready to work with anxiety, collusion, and group-level dynamics.
- 1
Published · 20 min read
Fight, Wait, or Hope: Bion's Basic Assumptions and Why Your Team Is Not Actually Working - 2
Published · 18 min read
The Group Holds What the Individual Cannot: Holding and Containment in Team Coaching - 3
- 4
Published · 14 min read
What Resonates Cannot Be Planned: How Groups Learn Together Without Anyone Trying - 5
Published · 15 min read
The Team That Always Agrees Is at Risk: Groupthink in Agile Settings - 6
- 7
Published · 20 min read
Architecture of Anxiety: How Your Sprint Review Became a Status Report - 8
Published · 18 min read
The Containing Organisation: Why Some Teams Can Do Depth Work and Others Cannot
15 steps · about 267 min
A systems psychodynamics lens on Agile teams
Tavistock Institute frameworks applied to Agile coaching — primary task, social defences, socio-technical systems, turbulent fields, and the structural conditions teams actually need to function.
Coaches and practitioners working with teams in organisational transition, transformation, or persistent structural dysfunction.
- 1
Published · 16 min read
Primary Task: The One Question That Cuts Through Everything - 2
Published · 18 min read
The Task and the Tribe: Why Every Agile Team Is Simultaneously Two Different Things - 3
Published · 17 min read
The Double Task: What Coaches Are Always Working On (Whether or Not They Name It) - 4
Published · 17 min read
The Under-Bounded Team: What Organisational Transition Actually Does to a Group - 5
Published · 20 min read
Architecture of Anxiety: How Your Sprint Review Became a Status Report - 6
Published · 16 min read
Speed as Social Defence: How Delivery Culture Closes the Space Coaching Needs - 7
Published · 15 min read
The Wicked Problem the Sprint Cannot Solve - 8
Published · 18 min read
Joint Optimisation: When Your Team Norms and Your Technical System Are Fighting Each Other - 9
Published · 18 min read
The Turbulent Field: Why Teams Cannot Save Themselves from Their Environment - 10
Published · 19 min read
The System Domain Effect: Why Coaching One Team Doesn't Shift the Pattern - 11
Published · 20 min read
Complex Responsive Processes: Why Change Is Never Installed and Always Emerges - 12
Published · 16 min read
Learning Spaces: Designing Reflection Into the System, Not Just the Session - 13
Published · 18 min read
The Containing Organisation: Why Some Teams Can Do Depth Work and Others Cannot - 14
Published · 17 min read
The Four Sources of Authority: Where Agile Teams Actually Authorise Each Other - 15
Published · 22 min read
A Theory of Change for Coaching: Making Your Impact Visible Before Anyone Demands Proof
8 steps · about 140 min
A contextual lens on team dynamics
Sedgwick's Contextual TA applied to Agile — what happens when you look at team dysfunction from the outside in, asking what the context has withheld rather than what people carry inside them.
Coaches ready to work with organisational conditions, cultural vocabularies, and contextual constraints rather than individual psychology alone.
- 1
Published · 18 min read
When the Problem Isn't Inside Anyone: Horizontal Problems in Agile Teams - 2
Published · 16 min read
Middle Managers Are Not Resisting — They Are Living in Two Worlds - 3
Published · 20 min read
What Your Team Knows Is Not What Your Team KNOWS - 4
Published · 17 min read
Four Conditions Instead of One: What Edmondson's Survey Cannot See - 5
Published · 15 min read
Disorders of Opportunity: When Too Much Freedom Produces Stuck Teams - 6
Published · 19 min read
Why Some Voices Don't Carry: Testimonial Injustice in Self-Organising Teams - 7
Published · 18 min read
The Coach's Frame of Reference Has Gaps Too - 8
Published · 17 min read
Why Sprint Patterns Repeat Without Anyone Choosing to Repeat Them
9 steps · about 137 min
A Transactional Analysis lens on groups that learn
Transactional Analysis applied to Agile teams as living learning systems: social pain, group culture, leadership/followership, inquiry, and the conditions that let groups metabolise experience instead of repeating it.
Agile coaches, Scrum Masters, and team leads who want a TA-grounded way to work with group learning, not only group dysfunction.
- 1
Published · 18 min read
Beyond Retros and Rituals: Co‑creative TA as a Relational Lens for Agile Team Coaching - 2
Published · 15 min read
The Team That Cannot Learn - 3
Published · 14 min read
Engaged Research: The Coach as Practitioner-Researcher - 4
Published · 16 min read
Social Pain in Agile Teams - 5
Published · 14 min read
When Feedback Hurts Too Much to Use - 6
Published · 15 min read
The Shared Bodymind of the Team - 7
Published · 14 min read
Looking for Trouble: Why the Hardest Moment Is Often the Learning Edge - 8
Published · 16 min read
Task Leadership, Anxiety Leadership, Learning Leadership - 9
Published · 15 min read
The Learning Community Agile Forgot
Browse The Library
Filter by challenge, concept, audience, or status
Use the controls below to narrow the library without losing the thematic grouping. Each card keeps the problem context visible so the page still reads like a map.
Filters
Theme
Resistance to change
For teams where pushback keeps getting framed as attitude instead of a live system response.
Resistance to changePublished
essaypractical12 min read
Resistance Is Relational, Not Just Personal
A diagnosis-first article on reading resistance as a field signal: what it protects, what conditions create it, and how to choose the next coaching move.
ResistanceField DynamicsCo-creative TA
For Agile Coach and Scrum Master
Read articleResistance to changePublished
essaydeep dive18 min read
Us vs. Them Is a Survival Strategy: Why Agile Transformations Split Organisations in Two
When Agile teams become tribal — dismissive of stakeholders, convinced management is the enemy — this is not a communication failure. It is a group survival mechanism with a structure, a name, and a resolution that is not a workshop.
EnactmentField DynamicsCo-creative TA
For Agile Coach and Scrum Master
Read articleResistance to changePublished
guidepractical14 min read
Looking for Trouble: Why the Hardest Moment Is Often the Learning Edge
The coach's job is not to smooth the group too quickly. In teams that are trying to learn, the trouble is often where the developmental task appears. Premature reassurance can protect the team from the very material it needs.
Transactional AnalysisLearning EdgeTrouble
For Agile Coach and Scrum Master
Read articleResistance to changePublished
essaydeep dive22 min read
The Dissolution Before the Transformation: Why Agile Change Needs a Threshold
Most Agile transformation programmes attempt to move people from State A to State B while leaving their identity, role, and status intact. Genuine transformation requires a period of dissolution: a liminal threshold where old identity is temporarily surrendered before new identity can form. Without this threshold, what looks like transformation is persona-thickening. People learn the new language while carrying the old script.
Analytical PsychologyLiminalityCommunitas
For Agile Coach and Change Sponsor
Read articleResistance to changePublished
essaydeep dive19 min read
You Cannot Facilitate Your Way Out of a Double Bind: Argyris and Organisational Defence Routines
The retrospective surfaces the issue. Everyone agrees it is a problem. Action items are assigned. Three sprints later, the issue is back. This is not a facilitation failure. It is a defence routine operating exactly as designed. Chris Argyris spent half a century studying why smart people in organisations consistently prevent themselves from learning — and what it would take to stop.
Double-Loop Learning
For Agile Coach and Change Sponsor
Read articleResistance to changePublished
essaydeep dive18 min read
When the Problem Isn't Inside Anyone: Horizontal Problems in Agile Teams
Most Agile team coaching assumes the difficulty lives inside team members — scripts, defences, underdeveloped skills. Sedgwick's horizontal/vertical distinction names the alternative: many Agile team problems arise from what the organisational context is withholding, not what people carry. Applying vertical interventions to horizontal conditions keeps teams stuck at symptom level.
Horizontal Problems
For Agile Coach and Change Sponsor
Read articleResistance to changePublished
essaypractical16 min read
Middle Managers Are Not Resisting — They Are Living in Two Worlds
Middle managers are the most consistently misread figure in Agile transformation. Coaching literature treats them as resistant, defensive, or threatened. Sedgwick's Overlap condition names what is actually happening: two whole yet incompatible frames of reality are simultaneously present. They KNOW the old world at a deep, embodied level. The new world they only know.
OverlapKNOWING
For Agile Coach and Change Sponsor
Read articleResistance to changePublished
essaypractical16 min read
What Agile Cannot Say: Vocabulary, Absence, and the Limits of Coaching Across Cultures
Agile coaching models are built on a specific vocabulary: autonomy, direct feedback, individual voice, productive disagreement. This vocabulary belongs to a cultural context. In communities where the Agile vocabulary is genuinely absent — not blocked but never formed — it cannot be unlocked by insight or permission. The article distinguishes absence from injunction as a diagnostic move.
Vocabulary
For Agile Coach and Change Sponsor
Read articleResistance to changePublished
essaydeep dive17 min read
Why Sprint Patterns Repeat Without Anyone Choosing to Repeat Them
The standard TA account of games explains recurring interpersonal patterns through individual scripts. Sedgwick's horizontal account inverts this: some recurring patterns arise from above, transmitted and circulated by shared vocabularies that foreclose alternative options. Good retrospectives don't stop them because they don't change the vocabulary that generates them.
Horizontal Problems
For Agile Coach and Scrum Master
Read articleResistance to changePublished
essaydeep dive19 min read
The System Domain Effect: Why Coaching One Team Doesn't Shift the Pattern
Andrew Bain, extending Menzies Lyth's work, showed that the social defences of a hospital were not contained within that institution — they operated across the entire domain of similar organisations. A consultant who successfully modified the defences in one hospital would watch the change erode as staff moved between institutions, carrying the system-domain-in-the-mind with them. The Agile coaching world has precisely the same structure. The defences that prevent genuine team autonomy often don't live in the team. They live in the domain — across the certification landscape, shared training, shared job descriptions, and shared assumptions about what a Scrum Master is for.
System Domain DefencesBainMenzies Lyth
For Agile Coach and Change Sponsor
Read articleResistance to changePublished
essaypractical8 min read
The stage Tuckman skipped
Tuckman's model came from passive-leader therapy groups — not agile teams with active coaches. The rebellion stage he collapsed into 'storming' is where genuine ownership forms. Suppressing it produces compliance without commitment.
Team Development StagesRebellion StageTuckman Critique
For Agile Coach and Scrum Master
Read articleTheme
Self-organisation breaking down
For delivery groups that look autonomous on paper but still stall around power, ownership, or dependency.
Self-organisation breaking downPublished
diagnosticpractical14 min read
Why Self-Organisation Fails — and What to Do Instead
A focused article on hidden power, promise collisions, and the authority conditions that keep declared self-management from becoming real.
Power DynamicsAuthoritySelf-Organisation
For Agile Coach and Scrum Master
Read articleSelf-organisation breaking downPublished
essaydeep dive22 min read
You Became the Team's Pattern: What Enactment Tells You About Stuck Agile Teams
The coach's unplanned behaviour — compulsive rescuing, going quiet, taking on team work — is not a coaching failure. It is the most precise diagnostic data available.
EnactmentField DynamicsCo-creative TA
For Agile Coach and Scrum Master
Read articleSelf-organisation breaking downPublished
essaydeep dive20 min read
The Current Beneath the Sprint: Reading Your Team's Undertow
Why surface-level coaching — ceremonies adjusted, working agreements signed, retrospectives facilitated — often produces no lasting change, and what is operating beneath the surface.
EnactmentField DynamicsCo-creative TA
For Agile Coach and Scrum Master
Read articleSelf-organisation breaking downPublished
essaydeep dive15 min read
The Team That Cannot Learn
Some Agile teams do not fail because they lack process, discipline, or motivation. They fail because the group cannot integrate new experience. The same sprint evidence returns, the same retrospective insight is rediscovered, the same defensive explanation protects the same stuck pattern. The team is busy, but it is not learning.
Transactional AnalysisGroup LearningNonlearning
For Agile Coach and Scrum Master
Read articleSelf-organisation breaking downPublished
essaypractical18 min read
The Three Leaders in the Room: Why Coaching the Wrong Person Changes Nothing
Every team has three distinct leadership structures operating simultaneously. The Scrum Master is accountable on paper. Someone else makes the real decisions under pressure. And a third person — often invisible — shapes what the team permits itself to do. Coaching only one of the three is the most common structural error in Agile team coaching.
Group ImagoLeadership TriadPrivate Structure
For Agile Coach and Scrum Master
Read articleSelf-organisation breaking downPublished
essaypractical19 min read
The Canon the Team Lives By: Why Coaching the Ceremonies Leaves the Rulebook Untouched
Every team has two constitutions: the one in the working agreements document, and the one it actually lives by. The second is older, more durable, and almost never reached by standard Agile interventions. Eric Berne called it the group canon. It determines what is genuinely permitted here — and it runs unchanged beneath every retrospective format, working agreement revision, and facilitation improvement the coach produces.
Group CanonPrivate StructureLeadership Fluidity
For Agile Coach and Scrum Master
Read articleSelf-organisation breaking downPublished
essaypractical20 min read
The Picture No One Is Sharing: How Divergent Group Imagoes Make Self-Organisation Impossible
The sprint board is a public object — everyone can see it, update it, argue about it. But each person also carries something the board does not capture: a private mental picture of the team itself. What kind of thing it is. What it is for. Where it is going. When those pictures diverge significantly, self-organisation becomes impossible — not because of structure or safety, but because the team's members are not imagining the same team.
Group ImagoCollective ImagoImago Alignment
For Agile Coach and Scrum Master
Read articleSelf-organisation breaking downPublished
essaypractical22 min read
The Story the Team Was Born Into
Some teams improve their ceremonies repeatedly and still produce the same dysfunction. The explanation is not in the quality of the coaching — it is in the level at which the coaching is operating. Teams carry foundational survival conclusions formed at their origin or under early crisis, and those conclusions determine which coaching interventions hold and which are quietly discarded.
Survival ConclusionTeam ScriptScript Decision
For Agile Coach and Scrum Master
Read articleSelf-organisation breaking downPublished
essaydeep dive15 min read
The Learning Community Agile Forgot
Agile promised learning organisations. Many implementations became delivery systems with learning language attached. A learning community has a higher standard: shared inquiry, peer correction, transmission across generations, and permission to revise the paradigm.
Transactional AnalysisLearning CommunityGroup Culture
For Agile Coach and Scrum Master
Read articleSelf-organisation breaking downPublished
essaydeep dive22 min read
The Coach Who Became the Secure Base
Long-tenured coaches and Scrum Masters become psychological leaders without noticing it happen. The team forms an attachment bond: the coach becomes the secure base from which the team explores. This sounds like trust. It is, in part. But securely attached teams ask the coach before deciding, escalate conflict to the coach, and lose capacity when the coach is absent. The coach has become the single point of failure for the autonomy they're trying to build.
Attachment PatternsPsychological LeaderDependency Paradox
For Agile Coach and Scrum Master
Read articleSelf-organisation breaking downPublished
essaydeep dive18 min read
The Elected Carrier: How Agile Teams Create Scapegoats
Every team under sustained pressure unconsciously elects one person, role, or sub-group to carry the shadow material it cannot own collectively — the failure, the conflict, the anxiety. In Agile contexts this appears as 'QA is always the bottleneck,' 'the architect doesn't get Agile,' 'the legacy team is the reason we can't move.' Removing the scapegoat does not dissolve the pattern. The next carrier is already waiting.
Analytical PsychologyShadowScapegoating
For Agile Coach and Scrum Master
Read articleSelf-organisation breaking downPublished
essaydeep dive20 min read
The Company You're Still Carrying: Organisational Phantom Narratives
Every organisation carries cultural complexes formed by significant historical events — a founder's controlling mythology, a public failure, a traumatic acquisition. These form 'phantom narratives': unconscious stories that silently choreograph present behaviour long after the original event. Why some organisations treat every impediment like an existential threat. Why post-merger teams still behave as if the merger is happening now. The phantom narrative is not visible on the culture deck.
Analytical PsychologyCultural ComplexPhantom Narratives
For Agile Coach and Change Sponsor
Read articleSelf-organisation breaking downPublished
essaydeep dive20 min read
When Culture Is the Client: Coaching Agile in High Power Distance Teams
Agile frameworks were designed in a specific cultural context — individualist, low power distance, with a premium on explicit communication. When deployed in high power distance cultures, the framing of 'make impediments visible,' 'challenge the process,' and 'psychological safety' arrives as a set of culturally alien demands. The coach who imports methods without adapting them will find that teams perform safety rather than experiencing it — a different version of the same theatre.
Analytical PsychologyCultural UnconsciousCultural Complex
For Agile Coach
Read articleSelf-organisation breaking downPublished
essaypractical14 min read
When the Ceremony Dies: How Agile Rituals Lose Their Power and How to Restore It
Nobody decided to kill the retrospective. It just stopped mattering. A ceremony that once had genuine energy — where things were said and decisions made — becomes a scheduled slot that everyone endures. The problem is usually diagnosed as bad facilitation and addressed with better formats. These help briefly, then the decay resumes. The real issue is liminal: the ceremony has lost its threshold quality. Restoration requires redesigning the boundary, not the agenda.
Analytical PsychologyLiminalityTemenos
For Scrum Master and Agile Coach
Read articleSelf-organisation breaking downPublished
essaydeep dive14 min read
When Agile Becomes Its Own Opposite
Teams that have pursued Agile values with consistent commitment often produce, through the unimpeded expression of those values, the exact pathologies the values were designed to prevent. Radical transparency becomes performative. Psychological safety produces passive agreement. Autonomy generates covert hierarchy. Jung's concept of enantiodromia — the law of opposites — explains the mechanism and points toward a different kind of work.
Analytical PsychologyEnantiodromiaShadow Integration
For Agile Coach and Scrum Master
Read articleSelf-organisation breaking downPublished
essaydeep dive15 min read
The Type the Framework Forgot
Agile ceremonies were designed by and for extroverted thinking types. The standup, the planning session, the retrospective — each carries a cognitive bias that structurally favours rapid public verbal exchange, logical categorisation, and concrete task-orientation. Introversion, feeling, sensing, and intuition encounter hostile conditions in every standard ceremony. The result is not resistance or low engagement. It is a systematic loss of cognitive diversity that no amount of psychological safety can address.
Analytical PsychologyPsychological TypesCognitive Diversity
For Scrum Master and Agile Coach
Read articleSelf-organisation breaking downPublished
essaydeep dive14 min read
The Mourning That Organisations Skip
Every genuine transformation involves irreversible loss, but change programmes are structured to bypass grief. The team that is still attached to the way it was is not resisting the new — it is carrying unprocessed mourning that the transformation never made space for. Resistance, nostalgia, passive sabotage, and inability to commit are not communication or management failures. They are the four forms of grief that was not allowed its ending.
Analytical PsychologyMourningEndings
For Agile Coach and Change Sponsor
Read articleSelf-organisation breaking downPublished
essaydeep dive13 min read
The Time That Agile Cannot Measure
Agile operates entirely in chronos — sequential, measurable time. Transformation happens in kairos — the opportune moment when something becomes possible that was not possible before, and that will not remain possible if the moment passes. These moments cannot be scheduled, cannot be repeated, and will not wait for the next retrospective. The coach who is occupied with the agenda when one arrives will not notice it until it has gone.
Analytical PsychologyKairosChronos
For Agile Coach and Scrum Master
Read articleSelf-organisation breaking downPublished
essaypractical14 min read
What Resonates Cannot Be Planned: How Groups Learn Together Without Anyone Trying
Some moments in a team session land differently. Someone says something and the room shifts. The content wasn't exceptional. The framing wasn't clever. Something else happened — something that felt larger than the person who said it. Group analysts call this resonance. You cannot manufacture it, but you can create the conditions where it becomes possible.
Group Matrix
For Agile Coach and Scrum Master
Read articleSelf-organisation breaking downPublished
guidepractical15 min read
The Meeting Belongs to the Group: Beginnings, Endings, and What Sprint Ceremonies Don't Hold
The first five minutes of a team meeting set the ceiling on what is possible for the next fifty. The last five determine whether anything learned will transfer beyond the room. Sprint planning and retrospectives are beginnings and endings — but most Agile frameworks treat them as content containers, not relational thresholds.
Holding & Containment
For Agile Coach and Scrum Master
Read articleSelf-organisation breaking downPublished
guidepractical13 min read
When the Facilitator Cannot Do What the Coach Can: The Real Distinction
There is a diagnostic that takes about thirty seconds. If the group is looking at you, you are facilitating. If they are talking to each other about something that matters, you may be coaching. Most Agile practitioners spend their careers on the facilitation side of this line — not because they lack skill, but because nobody has been clear about what is on the other side of it.
Holding & Containment
For Agile Coach and Scrum Master
Read articleSelf-organisation breaking downPublished
guidepractical16 min read
Coaching Online Is Not Coaching With Less WiFi: Virtual Teams, Anxiety, and What the Platform Cannot Hold
Remote and hybrid teams are not just co-located teams with a technology constraint. They are structurally more anxious — by conditions that group analysts have been able to name since the 1950s. Most of what gets labelled as a communication problem, an engagement problem, or a remote-working problem is an anxiety problem. The platform did not create it. The platform just removed what was containing it.
Holding & ContainmentBasic Assumptions
For Agile Coach and Scrum Master
Read articleSelf-organisation breaking downPublished
essaydeep dive18 min read
What Groups Remember: The Matrix, Membership Change, and Why Restructuring Doesn't Reset a Team
The manager replaces two members of a stuck team and waits for the pattern to change. The pattern does not change. The new members, within three sprints, are doing exactly what their predecessors did — sometimes down to the phrasing. The team was not changed by changing its members. The matrix was not touched.
Group Matrix
For Agile Coach and Team Lead
Read articleSelf-organisation breaking downPublished
essaydeep dive20 min read
What Your Team Knows Is Not What Your Team KNOWS
Teams that can perfectly articulate what needs to change in a retrospective and then do exactly the same thing next sprint. Sedgwick's knowing/KNOWING distinction provides the explanation. Facilitation reliably produces knowing. Coaching at its best produces KNOWING — the deep familiarity when a team's understanding of its pattern genuinely shifts.
KNOWINGAdult Authority
For Agile Coach and Scrum Master
Read articleSelf-organisation breaking downPublished
essaypractical15 min read
Disorders of Opportunity: When Too Much Freedom Produces Stuck Teams
Agile coaching treats stuck teams as though they lack permission. Sedgwick's Chaos configuration inverts this: in many post-transformation teams, permission is not what is lacking. The problem is unconstrained proliferation of options without shared signposts. These teams don't need more permission — they need orientation, structure, and a bounded enough field to move within.
Horizontal Problems
For Agile Coach and Change Sponsor
Read articleSelf-organisation breaking downPublished
essaypractical15 min read
What AI Can Give Your Team — and What Only Coaching Provides
AI tools can already facilitate retrospectives, surface communication patterns, and generate coaching-style language. They do all of this at the level of knowing. What they cannot produce is KNOWING: the deep familiarity when a team's understanding of its pattern snaps together and comes to life. This is not a deficiency of the AI's language model — it is structural.
KNOWING
For Agile Coach and Scrum Master
Read articleSelf-organisation breaking downPublished
essaydeep dive18 min read
The Task and the Tribe: Why Every Agile Team Is Simultaneously Two Different Things
Every Agile team is, at the same moment, two distinct systems with incompatible requirements. The task system demands openness, adaptation, and engagement with the external environment. The sentient system — the team as a tribe — protects belonging, guards identity, and resists exactly the disruption the task requires. Coaches who see only the task level misread resistance. Coaches who see only the relational level enable avoidance. The diagnostic question is always: is this behaviour protecting the work, or protecting the tribe?
Sentient SystemTask SystemPrimary Task
For Agile Coach and Scrum Master
Read articleSelf-organisation breaking downPublished
essaypractical17 min read
The Double Task: What Coaches Are Always Working On (Whether or Not They Name It)
Harold Bridger, working at the Tavistock Institute, proposed that any working group is always simultaneously engaged in two tasks: the stated task (the work) and an implicit relational task (the management of the group's own emotional life, power dynamics, and sense of who belongs and who doesn't). Every Agile ceremony has both. Coaches who attend only to the stated task miss half the available data. Coaches who attend only to the relational task lose the authority that comes from being useful to the work. The double task is not an optional layer — it is always present.
Double TaskBridgerRelational Task
For Agile Coach and Scrum Master
Read articleSelf-organisation breaking downPublished
essaypractical15 min read
The Wicked Problem the Sprint Cannot Solve
Tame problems have identifiable causes, known solutions, and can be resolved through prior experience or analytical method. Wicked problems involve systemic interdependency (you cannot isolate a single cause) and people complexity (multiple stakeholders with incompatible perspectives on what even counts as a problem). Team dynamics are wicked. Sprint velocity is tame. Agile frameworks are designed for tame problems. Coaches who apply tame-problem methods to wicked team dynamics produce partial solutions that generate new problems. Understanding the difference is not academic. It is the most practical thing a coach can know.
Wicked ProblemsTame ProblemsSystems Complexity
For Agile Coach and Scrum Master
Read articleSelf-organisation breaking downPublished
essaypractical16 min read
Primary Task: The One Question That Cuts Through Everything
Eric Miller and Ken Rice at the Tavistock Institute proposed that every organisation and every team has a primary task: the task it must perform to survive. Not the most visible task, not the most valued task, not the task described in the team charter — but the one that, if not performed, means the team ceases to exist. When a team cannot answer this question clearly and consistently, all coaching operates on the symptoms of that confusion. Primary task clarity is not a values exercise. It is a boundary condition for effective work.
Primary TaskMiller and RiceTask Clarity
For Agile Coach and Scrum Master
Read articleSelf-organisation breaking downPublished
essaydeep dive18 min read
Joint Optimisation: When Your Team Norms and Your Technical System Are Fighting Each Other
Socio-technical systems theory, developed by Eric Trist and Fred Emery at the Tavistock Institute, proposes a deceptively simple principle: peak performance is only possible when the needs of both the social system and the technical system are jointly met. Agile teams fail in a recognisable pattern when these two systems diverge — a high-trust, collaborative team running a tool architecture that forces gatekeeping and individual handoffs; or an autonomous team using a delivery pipeline that embeds the authority structure it was supposed to dismantle. The coach who addresses only the social system is fixing half the problem.
Joint OptimisationSocio-technical SystemsTrist and Emery
For Agile Coach and Change Sponsor
Read articleSelf-organisation breaking downPublished
essaydeep dive18 min read
The Turbulent Field: Why Teams Cannot Save Themselves from Their Environment
Fred Emery and Eric Trist identified a category of environment they called the turbulent field: a context in which the sources of disturbance cannot be traced to specific causes, solutions become outdated before they can be implemented, and the interactions between organisations in the field produce unpredictable consequences for all of them. Agile teams live in exactly this kind of field. And Emery and Trist's conclusion was stark: individual organisations cannot adapt to turbulent fields alone. The team that is coached in isolation while its environment remains unaddressed is being asked to stabilise something the environment is continuously destabilising.
Turbulent FieldsEmery and TristSocio-ecological
For Agile Coach and Change Sponsor
Read articleSelf-organisation breaking downPublished
essaypractical17 min read
The Under-Bounded Team: What Organisational Transition Actually Does to a Group
When organisations impose significant change — restructuring, transformation, leadership replacement, strategy shifts — the affected teams become under-bounded: their role definitions blur, decision rights dissolve, relationships to authority become unclear, and identity becomes unstable. This is not resistance in the ordinary sense. It is what happens to any system when its boundaries are threatened. The symptom set of an under-bounded team is specific and recognisable, and it has a distinct intervention logic that is different from resistance coaching, basic assumption work, or psychological safety repair.
Under-bounded SystemsTransitionBoundary Permeability
For Agile Coach and Scrum Master
Read articleSelf-organisation breaking downPublished
essaydeep dive20 min read
Complex Responsive Processes: Why Change Is Never Installed and Always Emerges
Ralph Stacey proposed that organisational change does not result from someone designing an intervention and then managing its implementation. It emerges — unpredictably and non-linearly — from the local responsive interactions between people in the present moment. Values, strategies, and cultural norms have no reality except as they are enacted in those local interactions. The implication for coaching is significant: the retrospective, the working agreement, and the coaching plan are not vehicles for delivering change. They are structured occasions for local interaction from which change may or may not emerge. Coaches who measure themselves against a planned outcome will systematically misread what is happening.
Complex Responsive ProcessesStaceyEmergence
For Agile Coach and Change Sponsor
Read articleSelf-organisation breaking downPublished
diagnosticpractical7 min read
What the team isn't saying about what it wants
Hidden agendas are personal goals at cross-purposes with the sprint that nobody named in planning. They are not sabotage — they are legitimate. Here is how to tell them apart from resistance and drama, and when to surface them.
Hidden AgendasGroup GoalsSocial Interdependence
For Scrum Master and Agile Coach
Read articleSelf-organisation breaking downPublished
diagnosticpractical8 min read
The structure determines the behaviour
Declaring teamwork does not create it. When individual velocity charts, peer-ranked reviews, and personal OKRs are in place, the goal structure is competitive regardless of values. Social Interdependence Theory explains why — and what to change.
Social Interdependence TheoryPositive InterdependenceNegative Interdependence
For Agile Coach and Change Sponsor
Read articleSelf-organisation breaking downPublished
diagnosticpractical7 min read
What no one has to say twice
Explicit working agreements sit above a deeper normative field that no one negotiated and everyone obeys. BART diagnoses structure. Norms diagnose the emergent behaviour that fills that structure. Coaching the wrong layer explains why the behaviour returns.
Group NormsIndirect PowerNorm Formation
For Agile Coach and Team Lead
Read articleTheme
Team drama and psychological games
For recurring rescuer, persecutor, and victim loops that keep burning time in ceremonies and stakeholder conversations.
Team drama and psychological gamesPublished
guidepractical10 min read
Stop the Drama: Coaching Teams Out of Psychological Games
A diagnosis-first guide to spotting live game patterns in Agile work, seeing the payoff, and deciding whether the drama lens is actually the right one.
Drama TriangleGamesInterventions
For Scrum Master and Agile Coach
Read articleTeam drama and psychological gamesPublished
guideintro8 min read
Exit Ramps: Practical Language for De-escalating Drama in Agile Teams
A tactical phrase handbook for live escalation: name the missing choice, slow blame into sequence, and return ownership without rescuing.
LanguageDe-escalationDrama Triangle
For Scrum Master and Agile Coach
Read articleTeam drama and psychological gamesPublished
essaydeep dive20 min read
Fight, Wait, or Hope: Bion's Basic Assumptions and Why Your Team Is Not Actually Working
Every Agile team presenting as 'dysfunctional' is usually doing one of three things: fighting an enemy, waiting to be rescued, or hoping that a future moment will solve everything. Wilfred Bion named these group states in 1952. They have been running teams since long before Scrum existed.
Basic Assumptions
For Agile Coach and Scrum Master
Read articleTheme
Psychological safety that feels performative
For environments that say the right words about candour but still punish risk, dissent, or bad news.
Psychological safety that feels performativePublished
essaypractical8 min read
Psychological Safety Theatre
Why safety slogans, surveys, and rituals fail when authority patterns, delivery pressure, and recognition norms still punish real candour.
CandourRecognitionAuthority Patterns
For Team Lead and Agile Coach
Read articlePsychological safety that feels performativePublished
essaydeep dive19 min read
What Your Team Can't Feel: Projective Identification in Agile Work
When a coach feels urgency the team doesn't show, hopelessness the team doesn't name, or grief after a session that seemed fine — they are often holding what the team has put outside itself. These feelings are not noise. They are the system's most precise available signal.
EnactmentField DynamicsCo-creative TA
For Agile Coach and Scrum Master
Read articlePsychological safety that feels performativePublished
essaydeep dive17 min read
The Expert Who Couldn't See the Team: What 'Not Knowing' Does That Frameworks Can't
The most rigorous thing an experienced Agile coach can do in the first session with a new team is arrive without a diagnosis. Not-knowing is not a beginner's uncertainty. It is an advanced practitioner's discipline — and the prerequisite for genuine contact.
Field DynamicsCo-creative TAEnactment
For Agile Coach and Scrum Master
Read articlePsychological safety that feels performativePublished
essaypractical16 min read
The Meeting That Never Actually Happened: Why Retrospectives Fail to Create Contact
Retrospectives fail not because teams lack safety or facilitators lack technique, but because the ceremony is almost always run as a process rather than as a genuine encounter between people. The format is a container. What goes in it is not technique but contact.
Field DynamicsCo-creative TAEnactment
For Scrum Master and Agile Coach
Read articlePsychological safety that feels performativePublished
essaydeep dive16 min read
Social Pain in Agile Teams
Exclusion, humiliation, rejection, and loss of belonging do not arrive in teams as abstract cultural issues. They register as pain. Many patterns coaches call resistance, defensiveness, or drama are social pain responses before they are attitude problems.
Transactional AnalysisSocial PainShame
For Agile Coach and Scrum Master
Read articlePsychological safety that feels performativePublished
guidepractical14 min read
When Feedback Hurts Too Much to Use
Retrospectives assume teams can metabolise feedback. But when feedback lands as shame, the team protects itself through silence, counterattack, compliance, or avoidance. The issue is not whether the feedback is true; it is whether the group can use it without losing belonging.
Transactional AnalysisFeedbackShame
For Scrum Master and Agile Coach
Read articlePsychological safety that feels performativePublished
essaydeep dive15 min read
The Shared Bodymind of the Team
A team is not just individual minds exchanging information. It is a mutually regulating field of bodies, signals, tempo, silence, and affect. Coaches miss half the data when they listen only to words and Jira events.
Transactional AnalysisShared BodymindEmbodied Sensing
For Agile Coach and Scrum Master
Read articlePsychological safety that feels performativePublished
essaypractical16 min read
The Animus Trap: What Agile Measures and What It Silences
Agile frameworks are structurally biased toward animus-coded values: measurable output, decisive action, visible progress, rational prioritisation, speed. These are not neutral. The complementary anima-coded values — relational attunement, contextual wisdom, symbolic meaning, reflective depth, cyclical rhythm — are treated as soft, secondary, or unmeasurable. What isn't measured goes into shadow. Psychological safety initiatives fail precisely because they are launched with animus energy applied to something that is, by nature, anima-coded.
Analytical PsychologyAnima and AnimusShadow
For Agile Coach and Team Lead
Read articlePsychological safety that feels performativePublished
essaypractical14 min read
Communitas Is Not Team Building: Why Offsites Leave Everything Unchanged
Organisations invest heavily in team events and offsites under the assumption that shared experience creates cohesion. More often, the team has a pleasant time and returns to exactly the same dynamics on Monday. Victor Turner's communitas — the quality of genuine equality and shared humanity that forms only in liminal space — is not the same thing as team building. The difference is not the activity. It is whether anyone actually crossed a threshold.
Analytical PsychologyCommunitasLiminality
For Agile Coach and Team Lead
Read articlePsychological safety that feels performativePublished
essaydeep dive13 min read
The Discomfort That Transforms
Coaching practice routinely short-circuits the transcendent function — the psyche's capacity to generate a genuine third position from the tension between two incompatible ones. Reframing, consensus-seeking, problem-solving, and premature interpretation all interrupt the process at the moment when sitting with the tension is the actual work. The team that is helped past its discomfort has been deprived of the transformation that discomfort was producing.
Analytical PsychologyTranscendent FunctionNegative Capability
For Agile Coach and Scrum Master
Read articlePsychological safety that feels performativePublished
essaydeep dive18 min read
The Group Holds What the Individual Cannot: Holding and Containment in Team Coaching
Organisations measure psychological safety and get back a number. Teams score 4.2 and still say nothing difficult. The problem is not the score — it is the assumption that safety is a belief rather than a felt experience. Winnicott called the condition that makes learning possible 'holding.' It has nothing to do with declarations.
Holding & Containment
For Agile Coach and Scrum Master
Read articlePsychological safety that feels performativePublished
diagnosticpractical15 min read
The Team That Always Agrees Is at Risk: Groupthink in Agile Settings
Psychological safety is often described as the condition where people feel free to disagree. But teams can score high on safety surveys and still be incapable of genuine disagreement. This is not safety. It is collusion. The mechanism has a name — groupthink — and Agile creates many of the conditions that make it more likely, not less.
Groupthink
For Agile Coach and Team Lead
Read articlePsychological safety that feels performativePublished
essaypractical17 min read
Four Conditions Instead of One: What Edmondson's Survey Cannot See
Edmondson's psychological safety construct is well-validated but structurally thin: it measures a perception without diagnosing the conditions that produce it. Sedgwick's four conditions — Resourcefulness, Responsiveness, Truthfulness, Integrity — provide a four-dimensional structural diagnostic. A team can score high on a safety survey while in deficit on Responsiveness or Integrity.
Horizontal Problems
For Agile Coach and Change Sponsor
Read articlePsychological safety that feels performativePublished
essaydeep dive19 min read
Why Some Voices Don't Carry: Testimonial Injustice in Self-Organising Teams
Self-organisation promises that hierarchical position no longer determines whose voice carries weight. In practice this promise is incompletely kept — and the reasons are often structural, not psychological. Testimonial injustice is the condition in which a speaker is assigned reduced credibility not because of what they say but because of who they are perceived to be.
Testimonial Injustice
For Agile Coach and Change Sponsor
Read articlePsychological safety that feels performativePublished
essaydeep dive20 min read
Architecture of Anxiety: How Your Sprint Review Became a Status Report
Isabel Menzies Lyth showed in 1960 that nursing procedures in hospitals were not designed to deliver care efficiently — they were designed, unconsciously and collectively, to protect nurses from the unbearable anxiety of caring for suffering patients. The same process produces the sprint review that became a presentation, the retrospective that became a satisfaction survey, and the standup that became a status meeting. These are not facilitation failures. They are architectural adaptations. The ceremony structure is the defence.
Social DefencesMenzies LythAnxiety
For Agile Coach and Scrum Master
Read articlePsychological safety that feels performativePublished
essaydeep dive16 min read
Speed as Social Defence: How Delivery Culture Closes the Space Coaching Needs
James Krantz observed that new information technologies function as social defences when they enable the speed of work to undermine organisational capacity for reflective thought. The observation was made in 2010. It describes the entire delivery culture of Agile in 2026. Continuous deployment, sprint velocity metrics, and cycle time dashboards are not neutral efficiency tools. When used without counterbalance, they function as a collectively maintained defence against the kind of slow, uncomfortable attention that real team development requires.
Social DefencesReflective SpaceDelivery Culture
For Agile Coach and Scrum Master
Read articlePsychological safety that feels performativePublished
essaypractical16 min read
Learning Spaces: Designing Reflection Into the System, Not Just the Session
Andrew Bain, researching what enabled organisations to sustain genuine learning — not training, not ceremony, but actual modification of defensive patterns — identified a specific structural element common to all cases: a dedicated learning space. Not a coach's session. Not a retrospective. A recurring, boundaried occasion in which the organisation's members could observe their own dynamics and make connections between what they were doing and what was happening. Coaches who do not help organisations build these structures make themselves structurally indispensable. The organisation learns only as long as the coach is present.
Learning SpacesBainReflective Structure
For Agile Coach and Scrum Master
Read articlePsychological safety that feels performativePublished
diagnosticpractical7 min read
Trust is not one thing
Trusting and trustworthy are two separate behaviours, not one spectrum. A team can be safe to share in and still not share. Diagnosing which axis is broken leads to a completely different coaching move.
Two-Axis Trust ModelTrusting BehaviourTrustworthy Behaviour
For Agile Coach and Scrum Master
Read articlePsychological safety that feels performativePublished
guidepractical8 min read
Why agile decisions converge too fast
Concurrence seeking is not a safety problem — it is a structural one. When no process requires dissent, evaluation apprehension fills the gap and the room closes around the first confident voice. Constructive controversy is the structural fix.
Constructive ControversyConcurrence SeekingEpistemic Curiosity
For Scrum Master and Agile Coach
Read articleTheme
Contracting and sponsor-team confusion
For engagements where expectations, authority, and accountabilities were never made explicit enough to hold.
Contracting and sponsor-team confusionPublished
essaydeep dive18 min read
Beyond Retros and Rituals: Co‑creative TA as a Relational Lens for Agile Team Coaching
The conceptual hub for the insights library: co-creative TA, its core stance, the learning contract, and the map to the narrower applied articles.
Relational LensCo-creative TAContracting
For Agile Coach and Scrum Master
Read articleContracting and sponsor-team confusionIn Development
walkthroughpractical8 min read
The Contracting Canvas: A Walkthrough
How to use the Contracting Canvas tool to build coaching agreements that survive real organisational complexity.
ContractingCoaching AgreementsStakeholder Alignment
For Agile Coach and Team Lead
Next branch on the mapContracting and sponsor-team confusionPublished
guidepractical11 min read
The Coach–Team–Sponsor Triangle in Practice
A practice-first article on triangulation in Agile coaching engagements: messenger, ally, and buffer dynamics, plus re-contracting moves that restore direct contact.
TriangulationCollusionRe-contracting
For Agile Coach and Change Sponsor
Read articleContracting and sponsor-team confusionPublished
essaypractical14 min read
Engaged Research: The Coach as Practitioner-Researcher
Coaching becomes more credible when it stops pretending to be either neutral observation or heroic intervention. The coach enters the team as an engaged researcher: observing, hypothesising, intervening, noticing effects, and revising the working theory in public enough that the team learns how inquiry works.
Transactional AnalysisEngaged ResearchHypothesis
For Agile Coach and Scrum Master
Read articleContracting and sponsor-team confusionPublished
essaydeep dive16 min read
The Wound That Works: Why the Coach's History Is Always in the Room
Coaches do not arrive at the team system as blank instruments. They arrive carrying their own developmental history — their own experiences of authority, belonging, failure, and transition. These are actively recruited by the team's dynamics. The Jungian wounded healer concept offers something more useful than 'know your triggers': the coach's wound is also the source of their developmental authority. But only if it is examined. Supervision is not professional development — it is the technical mechanism that keeps the coach's history from running the session.
Analytical PsychologyWounded HealerCountertransference
For Agile Coach and Scrum Master
Read articleContracting and sponsor-team confusionPublished
essaypractical14 min read
The Inside-Out Coach: What Internal Agile Coaches Can't See and Why
Internal Agile coaches are embedded in the organisation's cultural complex — they have absorbed its phantom narratives, its persona and shadow, its language for what can and cannot be said — usually without awareness. This gives them genuine advantages and a specific blind spot: they cannot easily see what has become invisible through familiarity. External coaches have more distance and can see what insiders have stopped noticing — but miss the embedded context. Neither position is superior. Each requires a different discipline.
Analytical PsychologyCultural ComplexParticipation Mystique
For Agile Coach and Change Sponsor
Read articleContracting and sponsor-team confusionPublished
essaydeep dive13 min read
When the Healer Inflates
The examined wound is the foundation of coaching authority — but examination is not the same as integration. Coaches who have done personal work without completing it often inflate around the healer archetype: they become the centre of the work rather than its servant, cannot refer without anxiety, and are covertly dependent on their clients' improvement for their own equilibrium. The engagement that should have made itself unnecessary has instead made itself indispensable.
Analytical PsychologyInflationHealer Archetype
For Agile Coach and Scrum Master
Read articleContracting and sponsor-team confusionPublished
essaydeep dive18 min read
The Containing Organisation: Why Some Teams Can Do Depth Work and Others Cannot
Coaching literature uses containment to describe the practitioner's stance — the ability to hold a team's anxiety without being overwhelmed by it. Systems psychodynamics extends this: the organisation itself must be structured to provide containment for its teams. An organisation that eliminates slack, punishes ambiguity, distributes accountability without authority, and changes direction faster than teams can orient has created an uncontaining environment. In such an environment, no amount of coach skill will produce lasting depth work — because the organisation is continuously doing to the team what the coach is trying to undo.
ContainmentOrganisational StructureHolding Environment
For Agile Coach and Change Sponsor
Read articleContracting and sponsor-team confusionPublished
guidedeep dive22 min read
A Theory of Change for Coaching: Making Your Impact Visible Before Anyone Demands Proof
The field's inability to demonstrate coaching effectiveness is not primarily a measurement problem — it is a theory problem. Coaches who cannot articulate what mechanism they think will produce what outcome for which teams under which conditions cannot design evaluation, cannot recognise when they are succeeding, and cannot explain their work to sponsors asking for evidence. A theory of change for coaching is not an academic exercise. It is a practical specification that makes coaching work more intentional, more assessable, and significantly easier to defend when budgets tighten.
Theory of ChangeEvaluationRealist Evaluation
For Agile Coach and Change Sponsor
Read articleTheme
Hidden authority, role, and boundary problems
For situations where recurring friction is really about unclear role, task, or decision boundaries.
Hidden authority, role, and boundary problemsPublished
diagnosticpractical10 min read
BART for Agile Teams: A Practical Diagnostic for Hidden Dysfunction
How boundary, authority, role, and task confusion create recurring team problems that coaches too often misread as personality or maturity issues.
BARTRoleBoundary
For Agile Coach and Team Lead
Read articleHidden authority, role, and boundary problemsPublished
essaypractical18 min read
The Power You Didn't Know You Had: A Self-Audit for Coaches and Scrum Masters
The most common structural error in Agile coaching is not misreading the team — it is misreading the coach's own power. Coaches and Scrum Masters routinely describe themselves as having no authority, conflating positional power (one of seven available sources) with all power. The sources they discount most confidently — psychological, political, personal — are the ones they use most, invisibly and often at the expense of the team's autonomy.
Power PotentialsPsychological PowerPolitical Power
For Agile Coach and Scrum Master
Read articleHidden authority, role, and boundary problemsPublished
diagnosticdeep dive16 min read
Task Leadership, Anxiety Leadership, Learning Leadership
Agile teams confuse three kinds of leadership: coordinating work, managing anxiety, and enabling learning. Self-organisation fails when anxiety leadership silently takes over and everyone mistakes the fastest calming move for mature leadership.
Transactional AnalysisLeadershipFollowership
For Agile Coach and Scrum Master
Read articleHidden authority, role, and boundary problemsPublished
guidedeep dive24 min read
The Manager Agile Forgot
The most consistent failure point in Agile transformations is not team performance — it is the structural displacement of middle management. Middle managers are not exhibiting a mindset problem. They are experiencing a structural threat: their legitimate power sources are being systematically removed, and the replacement structure has not assigned them a clear function. Coaching for mindset is applying the wrong framework to a power problem.
Structural DisplacementPower SourcesLieutenant Problem
For Agile Coach and Scrum Master
Read articleHidden authority, role, and boundary problemsPublished
essaydeep dive18 min read
What the Algorithm Cannot Hold: The Irreducible Human in Team Coaching
AI tools are entering the team coaching space — retrospective facilitation, sentiment analysis, team health monitoring. The question is not whether AI can assist coaching work. It is what the relational and depth function of coaching provides that AI structurally cannot replicate. The answer has implications for how Agile coaches position their practice, and for a risk that rarely gets named: AI coaching tools that feed team dependency rather than supporting autonomy.
Analytical PsychologyTransferenceWounded Healer
For Agile Coach and Scrum Master
Read articleHidden authority, role, and boundary problemsPublished
essaydeep dive14 min read
What the Product Owner Is Actually Carrying
Product Owner problems — the unilateral, the conflict-avoidant, the impossible — are almost always team projection problems. The PO role is structurally positioned to receive the team's disowned relationship to authority, commercial reality, and the capacity to disappoint. The result is a PO who inflates or collapses, and a team that never develops a mature relationship to constraint. Coaching the PO in isolation will not hold.
Analytical PsychologyProjectionAuthority Complex
For Agile Coach and Scrum Master
Read articleHidden authority, role, and boundary problemsPublished
essaypractical16 min read
The Team Is Not the Patient: Why 'Dysfunctional' Is a Frame the Coach Should Resist
The coach is hired to fix a dysfunctional team. Six months later, the team is functioning. The coach is then challenged — not on their work with the team, but on something else entirely. The organisation that commissioned the work has begun to resist what it asked for. This is not betrayal. It is the system behaving exactly as systems do when the dysfunction they housed gets disturbed.
Groupthink
For Agile Coach and Change Sponsor
Read articleHidden authority, role, and boundary problemsPublished
essaypractical14 min read
The Route to Autonomy Goes Through Dependency: A Paradox Every Coach Must Hold
Coaches are trained to avoid creating dependency. The irony is that this training produces coaches who withdraw too early — and teams that never develop the autonomy the coach was trying to build. Winnicott showed that the route to independence is not around dependency but through it. The coach who cannot tolerate being needed cannot be used.
Holding & Containment
For Agile Coach and Scrum Master
Read articleHidden authority, role, and boundary problemsPublished
essaydeep dive17 min read
When the Mirror Speaks: Parallel Process and What Your Feelings Are Telling You About the Team
Carolyn had been working with the top team for nine months. The coaching was grinding to a halt. She felt increasingly bored, increasingly avoidant, and increasingly tempted to end the contract. In supervision, it took about fifteen minutes to see that her boredom was not her own. It was the team's — mirrored in her. This is parallel process. Most Agile coaches have never heard of it.
Parallel ProcessCountertransference
For Agile Coach
Read articleHidden authority, role, and boundary problemsPublished
essaydeep dive18 min read
The Coach's Frame of Reference Has Gaps Too
Psychodynamic and TA traditions address the coach's involvement through countertransference — personal history activated in the present. Sedgwick adds a different dimension: cognitive vulnerability is irreducible for everyone, including the coach. The coach's frame of reference has absences shaped by their own social context, vocabulary, and cultural history.
Adult Authority
For Agile Coach
Read articleHidden authority, role, and boundary problemsPublished
essaypractical17 min read
The Four Sources of Authority: Where Agile Teams Actually Authorise Each Other
Agile frameworks address one source of authority: from above (role-based, formally delegated). Anton Obholzer, working in the Tavistock tradition, identified three others: from below (followership that grants or withholds authority regardless of role), from alongside (peer recognition that a person has standing to act), and from within (the internal conviction that one has the right to act). In self-organising teams, formal authority from above is deliberately reduced. But the other three sources have not been designed — they are simply present, operating invisibly, and usually misread as personality factors or culture problems.
AuthorityObholzerFollowership
For Agile Coach and Scrum Master
Read articleNext Branches
What is being added to the map next
These pieces are in active development and designed as new entry points, not padded rewrites of what is already published.
Contracting and sponsor-team confusion
The Contracting Canvas: A Walkthrough
How to use the Contracting Canvas tool to build coaching agreements that survive real organisational complexity.
8 min read
Go Deeper
When the article is not enough, move to tools, frameworks, or a working session.
The insights are meant to orient real practice. From here, the next step can be a deeper framework, a practical tool, or a live conversation around your context.