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.
The emotion that didn't come with you
The coach arrives feeling fine. The team looks fine. The sprint review proceeds normally. Halfway through, the coach is seized by a sense of impending disaster they cannot locate or explain.
The team is a product squad at a fintech, three weeks from a significant release. The atmosphere in the room is calm. The PO is satisfied with progress. The sprint goal was met. The coach facilitates the review competently. Then, midway through the session, a feeling begins: sourceless but insistent, a certainty that something is about to go badly wrong. By the end the coach is almost shaking. They drive home rehearsing worst-case scenarios about a product that is not theirs and a deadline they are not responsible for. Nothing in the session's content explains it.
The internal response is familiar: I'm too attached. I need to maintain better professional distance. This is my anxiety, not the team's problem.
All of that may be true. It is also possible that the feeling arrived in the room before the coach and was waiting for someone to carry it.
The team's managed-down anxiety about the release — held below the surface, not named in the review — had to go somewhere. It went into the coach. The coach felt, for forty minutes, what the team had been suppressing for three weeks. This is not a metaphor. It is a mechanism. It has a name, a structure, and, when recognised, a use.
What projective identification actually is
Groups under sustained pressure cannot hold all of their emotional experience simultaneously. Some of it — the anxiety, the grief, the rage, the hopelessness — is too destabilising to carry at the surface. The group finds a way to deposit it elsewhere. Not deliberately. Not through any conscious decision. Through the ordinary texture of being together: the particular questions deflected toward the coach, the quality of attention directed at certain moments, the body language that communicates, below the threshold of words, that this belongs to you now.
The coach does not consciously receive the assignment. The feeling arrives as if it were always their own. It has the texture of a personal reaction. It is accompanied by the entirely plausible internal narrative that explains it in personal terms: too attached, too invested, boundary problem, stress from another engagement. The personal narrative is usually available and always convincing. It is also frequently wrong.
This is projective identification. Van Beekum (2015), drawing on Wells: "Through projective identification, members of an organization or group are 'connected to each other by passion, indifference, silence, contempt, respect, love, guilt, hate and in other ways. The patterning of projective identification bonds group members together.'" These are unconscious alliances. The coach is not outside the alliance. They are inside it, and the alliance assigns them a role in the group's emotional economy without consulting them.
Projective identification is not primarily about the individual recipient. It is a group phenomenon that uses individual recipients as a medium. The coach who feels the team's anxiety is not being unprofessional or over-attached. They are serving a function: the group has found someone to carry what it cannot afford to carry itself.
The relationship to enactment and splitting
Enactment is behavioural: the coach starts doing something the team's pattern requires — rescuing, going quiet, absorbing urgency into extra preparation. Projective identification is emotional: the coach starts feeling something the team has deposited. Both are involuntary. Both carry diagnostic information. The distinction matters because the response differs — enactment is worked with by noticing behaviour; projective identification is worked with by noticing feeling and tolerating it rather than acting on it.
Projective identification is also the flip side of splitting. What the group has divided off and declared "not us" has to land somewhere. The coach, the sponsor, the PO, the team's line manager — whoever stands close enough to the group's emotional field — receives what the group cannot hold. Understanding splitting and projective identification together gives the practitioner a complete picture of what is moving through the system and where it is going.
Five projective identification patterns in Agile work
These are not personality differences or variations in coaching style. They are recurring patterns of emotional transfer that practitioners encounter repeatedly — and usually explain away as personal reactions before they have a chance to become diagnostic.
The Urgency Transfer
The coach feels frantic about a deadline the team seems calm about.
A delivery coach at a logistics platform company. Three weeks to a major integration release. The team's sprint ceremonies are unhurried. The retrospective produces five action items about process improvement. The coach spends the weekend drafting a risk summary nobody asked for, sends it Sunday evening, and receives a polite acknowledgment on Monday. The team continues at the same pace.
The team's calm is not equanimity. It is managed suppression. They are spending significant energy holding deadline fear below the surface. The coach is carrying it for them, which frees up their attention — and disconnects them from the urgency they need to make good decisions about scope.
The Hopelessness Transfer
The coach feels increasingly hopeless about the team's ability to improve; the team seems unworried, even confident.
An experienced Agile coach, six months into an engagement with a cross-functional squad at a fintech. The team's velocity is stable. Their retrospectives are constructive. Their language about the future is optimistic. The coach's session notes become shorter and more resigned. They find themselves thinking, on the drive in, that nothing is going to change.
What the coach feels is the team's defended-against knowledge that something fundamental is wrong — knowledge they cannot afford to hold because holding it would require a conversation no one is ready to have. The hopelessness belongs to the team. The coach is its current address.
The Competence Transfer
The coach feels incompetent and like an imposter in this engagement; the team appears highly functional.
A coach assigned to a senior engineering team at a platform company. The team is technically sophisticated. Their discussions are fast and precise. The coach's questions land well but feel thin to them. They begin preparing more extensively, second-guessing their facilitation choices, and privately wondering whether they are the right person for this engagement.
The team's functional surface is covering significant anxiety about expertise and mastery — the unspoken question of whether they are actually as capable as they appear. They have put their not-knowing into the coach. The coach is experiencing the team's imposter syndrome.
The Anger Transfer
The coach feels unusual irritation toward a sponsor or stakeholder; the team remains neutrally professional.
A coach to a product squad at a logistics company. The product director attends sprint reviews. The team's manner toward her is measured and cooperative. The coach finds themselves composing critical assessments of the director's questions on the drive home — assessments they do not voice but cannot set down.
The team's real anger at a constraint the director imposed three months ago — too dangerous to express directly, too present to disappear — has been housed in the coach. The coach's irritation is the team's anger looking for a face.
The Grief Transfer
The coach feels inexplicably sad after a session that appeared to go well. The work feels weighted.
A coach to a newly reorganised team at a fintech. The reorganisation merged two previously separate squads. The team is professional and cooperative. Sessions end productively. The coach drives home after the third session with a heaviness they cannot account for. Nothing went wrong. Something feels lost.
Unprocessed organisational grief — the loss of previous team structures, the colleagues who were separated, the identity each sub-group held before the merger — has no legitimate channel. The team carries it but cannot name it. The coach picks it up at the end of every session, carries it to their car, and leaves it in the car park.
The Containment Discipline
What to do when you're holding the team's material
The response to projective identification is not suppression, not immediate disclosure, and not acting on the feeling. It is containment: holding the projected material long enough for it to transform from impulse into information.
Suppression discards the data. Immediate disclosure — I'm feeling your anxiety right now — hands the material back before the team is ready to receive it and typically produces defensiveness or confusion. Acting on the feeling is what produces the enactment patterns from Article 1: the Urgency Absorber who starts working weekends, the Invisible Coach who matches the team's managed-down flatness. All three responses miss the diagnostic value the projection is carrying. Containment uses it.
Recognise and own the experience
— Internal — not voiced to the teamThe first move is private. The question the coach asks themselves is: this feeling may not be primarily mine — what might the group be doing with it? This is not certainty. It is a hypothesis that opens a different quality of attention. Instead of managing the feeling as personal noise, the coach holds it as potential field data and stays curious about what it is pointing toward. The feeling is not suppressed. It is held.
Metabolise
— Between sessions or in supervisionBion's alpha function, translated: the capacity to sit with raw emotional experience long enough for it to become thought rather than impulse. For the coach holding the team's urgency: what does this urgency tell me about what the team cannot currently afford to feel? What would happen if they felt it? What are they protecting by keeping it out of consciousness? This is not interpretation to deliver. It is the coach processing the projection into a hypothesis.
Return the material
— When the hypothesis is formed — as observation, not disclosureThe material is returned not as emotional self-disclosure but as an observation that opens a door. For the Urgency Transfer: I keep noticing a theme of speed in this team — even when we're talking about quality, the conversation comes back to speed. I'm curious what's underneath that. For the Grief Transfer: I wonder if this team has had time to mark what changed in the reorganisation — not just structurally but in terms of what it was like to be in the previous configuration. In each case the coach opens the door. The team walks through if they are ready.
Van Beekum: "a strong internal tendency or drive can be contained and used for the benefit of understanding the client rather than enacted." This is the distinction between the coach who absorbs the Urgency Transfer and starts working weekends, and the coach who holds the urgency, metabolises it into a hypothesis about what the team is suppressing, and returns it as an observation that opens an inquiry.
When the return is well-timed, the team typically experiences a moment of relief, then uncertainty, then access to something they had been keeping at a distance. This is the shift from projective identification back to genuine feeling — a small but significant expansion of the team's capacity to hold its own experience rather than distributing it outward.
What this requires of the coach
Containment is a practice, not a disposition. It requires specific conditions: the coach's own emotional range, a supervision structure in which what they carry between sessions can be examined, and a clear understanding of the ethical boundary between organisational work and therapy.
The discipline of not acting out
The distinction between enactment and containment is the difference between involuntary acting-out and deliberate holding. Enactment happens when the coach follows the projection into behaviour — the Urgency Absorber who starts working weekends, the Invisible Coach who goes quiet because the team has deposited its managed-down flatness into the room. Containment happens when the coach feels the pull, does not follow it into behaviour, and processes what the pull is pointing toward.
The capacity to not act out is not a personality trait. It is built through practice — specifically through the practice of noticing, in real time, that a feeling has arrived without announced itself as a projection. Most coaches who develop this capacity report that the first sign is usually physical: a quality of the feeling that does not match the room, a disproportionate intensity relative to the content, or the absence of a plausible personal origin.
The supervision function
Projective identifications that are not processed in supervision get carried to the next engagement. The coach who absorbed an Anger Transfer and never examined it arrives at the next session slightly pre-irritated at stakeholders who have done nothing yet. The coach who carried a Grief Transfer through three consecutive engagements without naming it begins to experience the work itself as inherently elegiac — as if something is always being lost.
Three coaches from the same organisation attend a supervision group. All three, without prior discussion, describe the same experience: a persistent feeling of being responsible for outcomes they have no authority over. They have each been preparing more thoroughly, checking in more frequently, writing handover notes nobody requested. The supervisor notes the pattern across all three reports. None of the coaches has a personal history that explains the feeling. All three are working inside the same client organisation. The organisation has a well-established pattern of projecting accountability downward — of creating the felt experience of responsibility in every external practitioner it touches, while keeping actual decision authority at a level the practitioners cannot reach.
The feeling of responsibility was not theirs. It was the organisation's. It had been put into them by a system that could not hold accountability at the level where decisions were actually made.
This is parallel process operating at the system level. The projective identification is not coming from a single team. It is coming from the organisation's structure — and it is arriving in every practitioner who enters that structure. Supervision that can notice the pattern across multiple practitioners is the only available instrument for reading it.
The ethical boundary
The goal of working with projective identification is to expand the team's contact with its own emotional experience — not to investigate personal history, not to conduct therapy, not to require any member of the team to disclose private feeling. The coach returns the material as an observation that opens inquiry. The team's meaning-making is its own. What the team does with the inquiry is entirely theirs. The coach creates the conditions; the team determines what to do with them. Van Beekum: "the relational consultant is challenged to implement the open and unpredictable nature of unconscious dynamics, without pretending that the process can be controlled."
The system's most honest signal
The coach who arrives at a session feeling fine and leaves holding the team's dread is not losing professional composure. They are inside a functional organisational process — one in which the group manages its emotional economy by distributing what it cannot hold into people who are willing to be present. The distribution is not conscious. It is not malicious. It is the system doing what systems do: finding available containers for what cannot yet be held at the source.
Most coaches have been taught to treat these feelings as noise — as personal reactions to be managed and set aside so that the professional work can proceed. This article argues the opposite: the feeling is the system's most honest available signal. It is more accurate than what the team says in retrospectives, more precise than what any survey or metric captures, and more immediate than anything that can be extracted through facilitated conversation. The coach who learns to hold it rather than suppress it, and to return it rather than enact it, is working at the deepest level of relational practice.
The capacity to work with projective identification depends on something even more foundational: the ability to arrive at a session without already knowing what is happening — without pattern-matching the team into a familiar category before the team has had a chance to show itself. That discipline, and what it makes possible that expertise cannot, is the subject of the next article in this series.
The team cannot feel what it has deposited in you. Your job is to feel it clearly enough to give it back.
Continue Exploring
Go deeper into the work
The Book
The Art of Creating Self-Organizing Teams
The full framework behind this article — contracting, team dynamics, and practical coaching tools for every stage of the journey.
Companion Toolkit
Resistance Radar & Resilience Scorecard
Practical tools for mapping resistance patterns and measuring whether interventions increased capacity — not just compliance.
TA for Agile
Co-creative TA in Agile Contexts
Ego states, psychological contracts, group imago, and the relational concepts that underpin this article — applied to real teams.