The Expert Who Couldn't See the Team: What 'Not Knowing' Does That Frameworks Can't

The 20-minute diagnosis

Ten years of experience. A new team. Twenty minutes in, the coach knows what this is. They have seen it before. They proceed accordingly. Six weeks later, nothing has changed.

The team is a platform squad at a fintech. The coach identifies the pattern within the first session: dependency structure, manager over-functioning, team unable to self-organise. They have seen it fifteen times. The next four sessions are structured around the diagnosis. Interventions are chosen to fit the pattern. The dynamic is named with precision. The team follows the structure. The coach's working hypothesis is confirmed at every step.

At the six-week review, nothing has changed. The team is polite about it.

The coach had not misidentified the pattern. They had seen it accurately. They had also never quite seen the team.

The more experience a coach accumulates, the faster they pattern-match — and the more they risk seeing the pattern they know rather than the team in front of them. Expertise is not the problem. The reflex to deploy it immediately is.

The capacity to arrive without a diagnosis is not a beginner's limitation. It is an advanced practitioner's skill — one that requires more cognitive and emotional effort than pattern-matching, not less. Van Beekum (2006), following Bion: "not knowing is the state of mind in which the consultant enters the relationship with the client."

What 'not knowing' is and what it isn't

Not-knowing is not incompetence, passivity, or the pretence of having no experience. The practitioner who arrives without a diagnosis still has ten years of pattern recognition available. The difference is in their relationship to that knowledge: held loosely, as hypotheses to test, rather than as categories to sort the team into. The experienced practitioner who claims to "not know" while internally certain is performing not-knowing. That is not the discipline being described here.

Not-knowing is the deliberate suspension of the expert stance at the moment of contact. It is arriving at a session as if this team might be different from every team seen before — and being willing to discover in what way.

Bion described two things practitioners bring to sessions that prevent genuine encounter. The first is the weight of previous sessions, previous similar teams, previous similar problems — the accumulated pattern library that generates the 20-minute diagnosis. The second is the pull toward a particular outcome: the hope that the team will become self-organising, or will finally have the direct conversation, or will acknowledge the thing the coach has been naming. Both the weight of the past and the pull toward a preferred future make genuine encounter with the present team harder. Bion called these memory and desire, and argued that the practitioner's job was to eschew both when entering the relationship.

Van Beekum (2006): "It is the consultant's job to eschew memory and desire from the consultancy situation."

Not all knowing is the same kind. Observable data — what the team says, what the metrics show, what the declared norms are — can be gathered quickly and filed into a framework. The preconscious layer — the half-known truths visible in body language, in what changes in the room when a topic is raised — requires slower attention. The defended-against layer — what the team is organised against knowing — cannot be forced into a framework at all. It surfaces indirectly, over time, in ways that prior pattern cannot predict. The first kind of knowing benefits from expertise. The second and third require the capacity to wait.

The capacity to sit with organisational experience long enough for it to produce its own meaning — rather than immediately filing it into a known category — is what Bion called the alpha function. It is active, not passive. It requires more effort than pattern-matching, not less. The practitioner using it is doing something genuinely difficult: tolerating the discomfort of not yet knowing, in order to stay available to what is actually there.

The framework trap

Frameworks are not the problem. Over-application is. Frameworks provide structure, vocabulary, and the comfort of prior art. They allow practitioners to name what they see, communicate with colleagues, and organise their interventions. None of this is the problem. The problem is what happens to the coach's attention once the framework has been applied.

When a coach decides "this is a dependency structure" in the second session, something changes in their listening. They begin to hear the team through the framework. Evidence that fits the pattern is confirmation. Evidence that doesn't fit is explained away — as noise, as denial, as the pattern manifesting in a less familiar form. The team's actual signals — the things they say that are genuinely surprising, that don't fit any known pattern — are processed out of the picture.

The Agile practitioner's catalogue — dependency, impasse, lack of ownership, leadership misalignment — becomes the vocabulary through which teams are experienced rather than understood. Teams that have been coached extensively often know this vocabulary too. They give the expected answers. They perform the right language. The framework is confirmed at every step. The team does not change.

Van Beekum (2006): "Most management theories work from the assumption that this chaotic unconscious energy can be controlled, and many consultants collude with that idea." The colluding move is converting the unknown into the known prematurely — providing the comfort of a framework when what is actually needed is the discomfort of genuine inquiry.

Teams that have been worked with through frameworks often describe the experience as accurate but somehow empty — the coach correctly named the dynamic, the team correctly understood the name, and nothing moved. The framework and the team made contact. The coach and the team did not.

What 'not knowing' looks like in practice

Not-knowing is not a philosophical stance adopted before sessions and abandoned inside them. It is a set of specific practices built into how a coach prepares for, enters, and responds during the work.

The preparation release

Before each session, write down the working hypothesis from the previous one — then deliberately set it aside. Not suppress it. Write it somewhere retrievable after the session, then arrive without it. The question to hold: what did I think was happening — and what if I was wrong? This is not neutrality. It is the deliberate creation of cognitive space for something unexpected to arrive.

Curiosity without agenda in the opening

Tell me about your sprint organises the team's response around the coach's frame. What's present for you right now? leaves space for the team to determine what is relevant. Both are legitimate coaching questions. Choosing between them is choosing between mapping the team and encountering them. The first produces information. The second produces contact.

Following surprise rather than suppressing it

When the team says something that doesn't fit the existing pattern, the pattern-matching coach explains it away. The not-knowing coach stops. Surprise is the signal that the team is showing something the coach's previous working hypothesis did not predict — which means it is the highest-value moment in the session. Most coaches move past it in under ten seconds. The not-knowing practice is to stop at it and stay there.

The hypothesis held loosely

Not-knowing does not mean no hypotheses. It means forming them slowly, from accumulated observation rather than rapid pattern-match; holding them lightly enough to abandon when the team offers disconfirming data; and naming them to the team as tentative rather than as diagnoses. The language signals the difference: I've been noticing something that might mean nothing is a hypothesis. This is a classic dependency pattern is a framework. The first keeps the inquiry open. The second closes it.

Using physical and emotional data

Not-knowing opens the coach to the experience of the room. When the diagnostic frame is not already occupying the coach's attention, they can feel what the team is doing to the air — the unusual flatness, the quality of attention, the energy that appears or disappears when a specific name is mentioned. This is not mysticism. It is perceptual capacity that the diagnostic frame crowds out. The coach who arrives without a framework has more room to receive what the team is depositing.

When not-knowing is most valuable

Four moments when the discipline pays most: the first three sessions with any new team; when a familiar team does something surprising; when previous interventions have not moved anything despite being technically correct; and when the coach finds themselves more certain than the situation warrants. That last signal — unusual certainty — is the most important. It usually means the framework has closed off rather than opened the inquiry. The certainty is the symptom.

The black box of transformation

Organisational transformation is not fully controllable or predictable. Van Beekum (2006), drawing on Gutmann and Pierre, describes the "black box" inside any transformation process: the irrational elements that "at best may be observable in interactions — but at worst, appear to come from nowhere." The coach cannot open the box, explain its contents, or engineer what emerges from it. The most they can do is accompany the team through the phases of not knowing what is inside.

Most coaching frameworks implicitly promise to open the box. They offer explanations for why teams get stuck and procedures for getting them unstuck. The explanations are sometimes correct. The procedures sometimes work. What they cannot do is replace genuine contact between the coach and the team — the encounter that makes transformation available rather than engineered.

Van Beekum (2015): "The relational consultant is challenged to implement the open and unpredictable nature of unconscious dynamics, without pretending that the process can be controlled."

The coach who arrives without a diagnosis can accompany the team into genuine uncertainty. They are not slightly ahead with the answer. They are alongside, genuinely not knowing what will emerge. For many teams, this co-presence in the unknown is the most useful thing a coach can offer — not because it solves the problem, but because it demonstrates that the problem can be held without being immediately converted into a framework.

Van Beekum (2006), quoting Polster and Polster: "Once an organization is in full contact with internal and external process, there is no need to chase change, because it simply occurs." Not-knowing is one of the conditions that makes full contact possible. When the coach's expertise is suspended long enough for genuine encounter to happen, something moves that would not move if the encounter had been replaced by a technically correct intervention.

The development path

Not-knowing is not a disposition. It is developed — through reflective practice, supervision, and a deliberate willingness to be surprised. It also requires enough expertise to know when to suspend it. Not-knowing without experience is just uncertainty. Not-knowing with experience is a disciplined choice.

The coach with two years of practice who "doesn't know" simply hasn't yet built the pattern library. The coach with fifteen years of practice who chooses not to deploy their pattern library in the first three sessions is making a different move entirely. The discipline is only available to the practitioner who has something to suspend.

The supervision practice for developing not-knowing is not the standard session debrief — what worked, what didn't. That review produces pattern-maintenance. The more useful review asks: where did I decide I knew the answer before the team was ready to know it? Every session has these moments of premature closure. They are usually invisible at the time. Naming them in supervision builds the capacity to notice them in real time.

A second practice: after each session, ask a single question — what surprised me, and what did the surprise reveal? This review trains the practitioner to value what did not fit rather than what confirmed. Over time it produces a different quality of attention: arriving at sessions expecting to be surprised rather than expecting confirmation.

The development path for not-knowing is not a course or a certification. It is a practice of repeatedly choosing the harder thing: arriving at the next session having set aside what was concluded at the last one; staying at the moment of surprise rather than filing it; and trusting that genuine contact with the actual team — rather than with the team expertise predicts — produces something more durable than technically correct intervention.

The condition that makes reception possible

This series has examined what the coach receives from the system — the enactments, the undertow, the splits, the emotional projections. All of that reception depends on a prior condition: the coach's availability to receive. Not-knowing is that condition. The coach who arrives with the diagnosis already formed will confirm it. The coach who arrives genuinely open will encounter what is actually there.

Expertise is a tool. Like all tools, it is useful when the situation calls for it and limiting when deployed reflexively. The discipline of not-knowing is not the rejection of expertise. It is the decision about when to pick up the tool and when to put it down.

The final article in this series examines the retrospective — the ceremony designed for genuine contact between people that most often produces managed process instead. Not-knowing is one of the conditions that makes genuine contact possible. The next article examines the intersubjective conditions for the rest.

The team in front of you is not the team you have seen before. The work begins when you can hold that as genuinely true.