top of page

The Moment Recognition Starts to Feel Like Diagnosis

Writer: Andrew Mallaband
Andrew Mallaband
Aug 14
4 min read

Updated: Oct 19

Black background with white text: "More messaging adds detail. It doesn't add momentum." Curved lines on right. Button: "Why we started building Storylines."

A pattern can feel true before its explanation has earned the same confidence.


I was recently involved in a discussion about an organisation that had become harder to manage as it grew.


The details here are anonymised and combine elements from several conversations, but the movement in the room was familiar.


People were describing decisions taking longer, teams explaining the same priorities differently, work being repeated and experienced leaders spending more time translating between parts of the business.


None of those observations was new on its own.


Then someone said:


“We have outgrown the way we make sense of the business.”


The room changed.


Several people nodded. One person connected the phrase to a recent planning cycle. Another linked it to a customer issue. A third said it explained why responsibilities that once felt obvious were now being negotiated repeatedly.


For a moment, several separate frustrations formed one recognisable pattern.


That mattered.


Something that had been vague was now visible enough to discuss.


Then the conversation moved again.


“If that is the problem, we need to redesign the operating model.”


Ownership, structure and a transformation programme were soon being discussed.


I could feel the relief in the room. We had gone from a collection of frustrating experiences to an explanation that appeared to connect them.


My instinct used to be that this was exactly what a useful conversation should do. Once the pattern had been recognised, the next step was to explain it and begin solving it.


But something no longer fitted.


The phrase had helped us recognise what the organisation felt like.


It had not yet shown why it felt that way.


When the pattern clicks


Recognition can be a powerful moment.


A phrase suddenly connects experiences that had previously seemed separate. People no longer have to argue that something is happening. The condition becomes part of the group’s shared reality.


That is genuine progress.


In the recent articles, I have been exploring recognition as the point where a general pattern becomes relevant to someone’s own situation. Recognition is not understanding, and it is not simplification. It opens a question that can now be examined seriously.


The difficulty is that the emotional force of that moment can make the question feel further advanced than it is.


When several people say, “That explains what we have been seeing,” two different things may be happening at once.


The pattern has become recognisable.


An explanation has begun to feel true.


Those are not the same achievement.


The confidence moves faster than the evidence


In the discussion, “we have outgrown the way we make sense of the business” was a useful description of the condition.


It could also support several explanations.


Perhaps the operating model had genuinely become unsuitable.


Perhaps the strategy had become harder to interpret as the business expanded.


Perhaps informal coordination had once worked because a small number of experienced people carried the context between teams.


Perhaps customer needs, product complexity and internal process had changed at different speeds.


Several of those explanations might have been connected. One might eventually have been better supported than the others.


But the room had not yet done that work.


The confidence created by recognising the pattern was beginning to transfer to the first explanation that fit it.


That is the distinction I have become more careful about.


Recognition establishes relevance.


Diagnosis makes a different claim.


It says not only that a condition is real, but that we understand what is producing it well enough to shape action around that account.


An explanation does not become a diagnosis merely because it is familiar, coherent or immediately useful.


It still has to earn its confidence.


The explanation starts changing the organisation


This matters because explanations do not remain in the conversation for long.


If the diagnosis is an outdated operating model, attention moves toward structure, decision rights and ownership.


If it is unclear strategy, the response may be different.


If it is accumulated process, changing customer expectations or capability gaps, different work follows again.


None of those responses is necessarily wrong.


The first explanation may turn out to be correct. A group also cannot examine every possibility indefinitely before acting.


But once an explanation begins directing investment, measures, ownership and change, its uncertainty becomes operationally important.


A plausible account can quickly become the reason a programme exists.


The programme then generates its own momentum. New roles are created. Workstreams begin. Measures are chosen. Progress starts being reported against the explanation that authorised the work.


At that point, returning to the original observation becomes harder.


The organisation may become more committed to the diagnosis before it has become more certain that the diagnosis is right.


Diagnosis does not require perfect certainty


I do not think the answer is to remain in observation indefinitely.


Organisations have to decide. Leaders often have incomplete evidence. Delay can create its own cost and confusion.


A useful diagnosis does not need to remove every uncertainty before action begins.


But it should make a different kind of discipline visible.


What evidence supports this explanation rather than simply the pattern?


What other causes could produce the same visible condition?


What would we expect to observe if our explanation were wrong?


Which parts are well supported, and which are still working assumptions?


Those questions do not guarantee the right answer.


They do stop the confidence of recognition being borrowed without examination.


A framework can help organise what people are seeing. A familiar label can help a group talk. An early diagnosis can provide a useful direction.


But none of those things creates evidence by itself.


What had actually been achieved


Looking back at the discussion, I do not think the phrase was misleading.


It had achieved something important.


It had connected several experiences and made a previously diffuse condition easier to see.


The group had recognised that growth had changed the way the organisation experienced itself.


That recognition deserved to be preserved.


What it did not deserve was to be treated as proof of one cause.


The question had become visible.


It had not yet been answered.


That is the point I now try to hold for a little longer when a phrase suddenly makes everything seem to fit.


Not to weaken the recognition.


Not to prevent action.


But to ask what the explanation has actually earned.


Earlier in the series


Recognition Comes Before Understanding — verified live link pending.


Recognition Is Not Simplification — verified live link pending.


When Everyone Agrees on the Problem — But Not on What It Means — publication and live-link readback pending.

Comments


bottom of page