What I cannot yet hold: Symmathesy and the ground of learning

The problem with transmission models of learning is not that they are inefficient. It is that they misrepresent what learning actually is — and in doing so, they produce a particular kind of learner.

When knowledge is treated as content that exists independently of relationship and can be transferred intact from one mind to another, the learner's role is fundamentally passive. The question is not what can we discover together but what do you need to be given. Over time, and at scale, this produces organisations structurally oriented toward receiving: receiving strategy from consultants, receiving findings from evaluators, receiving direction from leadership. The capacity to generate understanding from within their own living complexity does not atrophy from lack of intelligence. It atrophies from a model of learning that has never asked it to be exercised.

The deeper damage is epistemological. The organisation loses confidence in its own knowing. Knowledge that cannot be presented in the form transmission models recognise — in reports, recommendations, frameworks, findings — becomes invisible to the organisation itself. The relational texture of its practice, the transcontextual intelligence distributed across its connections, the things that frontline workers know in their bodies before they can put them into language: none of this survives the journey through a transmission-oriented learning structure intact. It is not that the organisation fails to value this knowledge. It is that the model through which the organisation understands learning has no container for it.

This is not a failure of individuals or of intent. It is what the model produces. And it is what makes symmathesy not merely a richer theory of learning but a genuinely different account of where intelligence lives and how it moves — one with direct consequences for what a practitioner working from it is actually doing in a room.

To work from symmathesy is not to apply a framework. It is to reorient toward a different understanding of what is happening in any encounter between a practitioner and an organisation — and of what the practitioner's presence is doing to what can happen there.

The practitioner is not outside the system observing it. The practitioner is a context the system is learning in relationship with. The quality of that relationship is not peripheral to the work; it is constitutive of it. What the organisation becomes capable of learning is partly a function of what the relationship between practitioner and organisation makes it possible to think — which means the practitioner's own relational and epistemic condition is always in play, always part of what is producing the results, whether or not it is acknowledged as such.

What the practitioner attends to shifts fundamentally from this position. Not: what does this organisation need to know or do? But: what is this organisation becoming capable of holding in relationship that it could not hold before — and what in its current structure is preventing it from holding more? The inquiry is into conditions rather than deficits, into capacity rather than performance, into what is trying to emerge rather than what has failed to appear.

What counts as progress shifts with it. The legible outputs of a conventional engagement — reports produced, frameworks adopted, action plans developed — are not unimportant, but they are surface. The substantive question is whether the organisation's capacity for mutual learning is genuinely developing: whether parts and whole are beginning to co-evolve, whether intelligence is moving across connections rather than pooling in designated roles, whether the organisation is becoming capable of learning from its own living complexity in real time rather than at the remove of a commissioned process.

The practitioner's own learning becomes diagnostic in this frame. If I leave an engagement knowing more or less what I knew coming in — if the encounter has not changed something in how I understand the problem, the organisation, or the work itself — something in the partnership has not been mutual. My development is not incidental to what is happening; it is evidence about the quality of what has actually been happening. A partnership that produces growth in the organisation and leaves the practitioner unchanged is not, by this account, a symmathetic partnership. It is a conventional engagement conducted with warmer intentions.

This reorientation is more demanding than it sounds, because it requires holding genuine uncertainty about what is developing while maintaining enough clarity of attention to perceive it. It also requires resisting the pull toward premature coherence — the temptation to organise what is emerging into a legible account before it has fully emerged. In a symmathetic engagement, the practitioner's capacity to remain in genuine not-knowing is not a limitation to be managed around. It is part of what makes the space safe enough for genuine inquiry.

“An inquiry the practitioner has already privately resolved is not a shared inquiry, however skilfully it is conducted.”

I want to try to name three tensions that this orientation produces in practice — tensions that I have not found resolvable, and that I have come to think are not supposed to be.

The first is between expertise and mutuality.

The practitioner brings real diagnostic capacity: accumulated pattern recognition, theoretical frameworks, experience of what organisational development looks like at different stages and in different conditions. This is not incidental to the work. It is part of what makes the partnership worth having. The client has not engaged a practitioner in order to think alongside someone who knows nothing useful.

But symmathesy requires that this capacity not foreclose the client's own inquiry. The moment the practitioner's expertise becomes the organising intelligence of the engagement — the thing that names what is happening and determines what it means — the mutuality collapses. The organisation is returned to the position of receiving, and the learning dynamic that the engagement was designed to cultivate is replaced by a more sophisticated version of the transmission model the whole practice is organised against.

The tension is not resolvable by withholding expertise or performing ignorance. Both are dishonest, and both deprive the partnership of something real. What the tension actually requires is a specific discipline: offering diagnostic perception as a contribution to shared inquiry rather than as a finding that closes the question. The difference is not rhetorical. It lives in how the practitioner holds their own knowing — with enough confidence to offer it and enough genuine openness to have it revised, extended, or contradicted by what the organisation knows that the practitioner does not.

This is harder in practice than in principle, because the structural pull is always toward demonstration. The practitioner's expertise is what the client has engaged them for, and there is a real and understandable pressure — from the client, from professional norms, from the practitioner's own need to be useful in recognisable ways — to be usefully expert in forms the client can identify as valuable. Resisting that pull without abandoning what is being pulled toward requires a kind of sustained double attention that does not become easier with practice. It remains genuinely effortful.

The second tension is between evaluation and witnessing.

A practice that takes developmental evaluation seriously must track development — must maintain a continuous portrait of what the organisation is becoming capable of, notice what is shifting and what is not, perceive the difference between genuine threshold movement and the sophisticated performance of it. This is not optional. Without it the practitioner is simply present, which is not enough.

But the act of tracking can distort what is developing. When the practitioner is assessing — holding the organisation against a developmental model, marking movement and stasis — they introduce a quality of attention that changes the relational field. The organisation begins, often without knowing it, to perform development rather than undergo it. The portrait becomes something the organisation is managing rather than something it is genuinely moving through. The act of observation has changed what is being observed in ways that make the observation less accurate at the same moment it feels most rigorous.

This is the observer problem at the level of practice. The practitioner cannot step outside the system to observe it neutrally, and the pretence of doing so produces worse information than honestly acknowledging the entanglement. Witnessing — attending with genuine presence to what is actually happening, without immediately organising it into an evaluative frame — produces something different and often something more useful. But it is not assessment, and the practice requires both. The organisation needs to be witnessed and it needs to be tracked, and these are not always compatible modes of attention in the same moment.

What the tension requires is not a synthesis but a movement between modes — and an honesty about which mode is operating at any given moment that most professional relationships do not naturally support. The practitioner who cannot tell the client "I am assessing right now, and that is changing what I can see" is not in a fully honest symmathetic relationship with them.

The third tension is between what the work requires and what organisational reality makes available.

Genuine cultivation operates on a timescale that organisational and commercial realities do not naturally accommodate. The developmental movements I have described are not sequential milestones that can be planned toward or scheduled. They emerge when conditions are genuinely prepared, which cannot be reliably timed. The preparation itself takes longer than most engagement models are designed to sustain, and the most important developments tend to occur in the gaps between formal contact rather than during it.

The organisations that most need this work are often operating inside accountability structures that require demonstrable progress at intervals that cultivation logic cannot satisfy. Funders want outcomes at reporting milestones. Boards want evidence of movement at quarterly meetings. The pressures that shape what organisations can invest in are real, structurally reinforced, and not going away. Pretending otherwise is not cultivation. It is a fantasy of ideal conditions conducted at the client's expense.

The tension cannot be resolved by refusing to work within these constraints. That is not honest about the conditions under which the work actually happens, and it would make the practice available only to organisations with unusually long time horizons and unusually tolerant accountability structures — which is to say, almost no organisations. Nor can it be resolved by simply accepting the constraints. That produces a practice that uses cultivation language while operating on implementation logic — which is a more insidious problem than straightforward consulting, because it misrepresents itself to the client and, eventually, to the practitioner.

What it actually requires is a transparency about this tension that most professional service relationships are not designed to support. An honest conversation, early and explicitly, about what the work needs and what the context makes available, and what that gap means for what is genuinely possible. This conversation is itself a cultivation practice — it is the first instance of the kind of honest inquiry the work is designed to develop. But having it does not make the tension disappear. It simply puts both parties in honest relationship with it, which is the only ground on which something real can be built.

Each of these tensions is a tension in practice — in what the practitioner does, how they hold their attention, how they navigate competing demands in real conditions with real clients. But underneath them is something that is not a practical tension. It is a question about formation.

Symmathesy, taken seriously, is not only a theory of how systems learn. It is a claim about what the practitioner must be in order to work from it genuinely. Not what they must know or what methods they must have command of, but what they must be capable of in themselves — what quality of presence, what relationship to their own not-knowing, what capacity to be genuinely changed by what they encounter rather than enriched by it at a safe remove.

The question I am most genuinely inside at this stage of the work is this: whether what symmathetic practice requires at this level is something that can be developed through disciplined attention and sustained reflection — or whether it requires a more fundamental reorientation of how the practitioner holds themselves in relation to the world, one that cannot be approached incrementally but only arrived at, if at all, through the kind of threshold crossing that the practice describes in organisations.

Put differently: can you cultivate the capacity for symmathetic practice, or does the attempt to cultivate it from within existing frameworks simply produce a more sophisticated version of what you already are? Does the practitioner need to undergo something — not learn something, not develop a competency, but actually undergo a reorientation that changes what they can perceive — before the work can be what it claims to be?

I am not asking this rhetorically. The three tensions I have described are all, at some level, expressions of this deeper question. The expertise-mutuality tension is partly a question about whether I have genuinely relinquished the need to be the organising intelligence, or whether I have developed a more refined version of it that presents better. The assessment-witnessing tension is partly a question about whether I can actually be present to what is happening rather than to my model of what is happening. The timescale tension is partly a question about whether I am genuinely inside cultivation logic or performing it.

These are questions about formation, not about method. And I name them here because they seem worth sitting with honestly — and because the people most likely to know whether they are answerable, and how, are those that have been living inside the framework long enough to have found out.