The structural cause is hard to see from the inside

Most founders running scale-ups know roughly what's wrong. Ask one in a quiet moment what the recurring pattern in their company has been over the last few quarters and they can usually name it within three sentences. The hire that didn't take. The leadership team friction that won't quite resolve. The decision that always seems to come back to their desk no matter who's nominally responsible for it.

The diagnostic isn't the gap. Founders see the symptoms clearly. What's hard is the next step — naming the structural choice that's producing the recurring symptoms. And that step is hard for a specific, almost inevitable reason.

The structural choice that produces the symptom was made earlier in the company's life. Most often it was made by the founder, sometimes deliberately and sometimes not. The choice was right at the time it was made; that's why it survived to become structural. Over the months and years since, it has been worn into the shape of the company. The team adapted to it. The hires made under it learned to operate within it. The processes and norms built on top of it assumed it as foundation.

By the time the founder is asking why does the same problem keep coming back, the structural choice is no longer something the founder reads as a choice. It's how the company works. It's invisible the way the layout of your apartment is invisible — the kind of thing you would only notice if someone pointed it out, and even then you might not see why it matters.

The literature on tacit assumptions

Edgar Schein's work on organisational culture, going back to the 1980s, made this concrete in a way that's still under-used. Schein distinguished three layers of culture: artifacts (what you can see — the office, the rituals, the visible behaviours), espoused values (what people say they believe — the values poster, the strategy doc, the all-hands speeches), and underlying assumptions (the unstated, often unconscious beliefs about how things work, what's important, what's possible). He argued that the deepest layer drives behaviour more than the espoused values do, but is much harder to surface. People genuinely cannot articulate what they believe until they are confronted with someone who believes something different.

In the structural-choices framing, the underlying assumptions are what the early structural choices were built on. The decision-rights pattern wasn't designed; it accreted from the founder's personal preferences about who should be in which conversations. The information-flow architecture wasn't planned; it emerged from how the founder happened to communicate when the team was small. These aren't visible as designs because they were never deliberately designed.

Chris Argyris's distinction between espoused theory and theory-in-use is the same insight in a different vocabulary. The espoused theory is what we say we do. The theory-in-use is what we actually do — observable in our behaviour, often inconsistent with the espoused theory, and almost never directly visible to the actor. Argyris's classic finding is that even when people are explicitly shown the inconsistency between their espoused and their actual behaviour, they tend to defend the espoused version and continue acting on the theory-in-use.

Donald Schön extended this in The Reflective Practitioner (1983), focusing on what he called knowing-in-action: the tacit, fluent expertise that experienced practitioners deploy without being able to articulate. The expert acts skillfully but cannot fully explain what they're doing or why. The skill lives in patterns of attention and judgment that are not consciously accessible.

Karl Weick's work on organisational sensemaking — particularly Sensemaking in Organizations (1995) — adds a further layer. Weick argued that organisations don't have meaning that gets discovered; they have meaning that gets enacted through what people pay attention to and how they categorise it. Once a particular sense-making pattern becomes habitual, it becomes the lens through which everything else gets read. The lens itself becomes invisible.

Putting these together: the operating structure of a company is a tacit, accreted artifact. It was never fully designed. Most of its load-bearing parts were never written down. The people who live with it daily can describe its symptoms (problems keep coming back) but cannot easily articulate its design (why those problems are coming back). The structure is operating on them faster than they can think about it.

Why this matters for structural work

This is what makes the structural work fundamentally different from other kinds of operating help. A fractional executive coming in to take a function off the founder's plate does not need to surface the tacit structure — they just operate within it. A consultant delivering a methodology doesn't need to surface it either — they import their methodology and apply it on top. The work I do is to make the tacit structure visible to the founder so that the founder can choose what to keep and what to change. The diagnostic is not the answer; it's the act of producing the picture from which an answer becomes possible.

This is also why pattern recognition from outside is so disproportionately useful. An outside operator who has watched the same kinds of structural choices stop fitting in fifteen other companies arrives with cognitive distance. The patterns that feel like just how things work to the people inside are foreground patterns to someone looking in. The work isn't to bring an external methodology — it's to use external eyes to find the load-bearing parts of the company's tacit operating logic.

There is a parallel here with something physicians have known for a long time. The clinician doesn't make their patient healthy; the clinician produces a picture of what's actually happening so that the patient can take action. The diagnostic is the load-bearing artifact. Treatment without diagnosis is just hope.

How long it takes

The first two to three weeks of any engagement I run are spent producing this picture. Six to twelve interviews, sometimes more, with the founder and across the team. A read of the past few quarters of internal documents — anything that captures decisions, post-mortems, retros, planning artifacts — looking for moments where the structure failed to do what it was implicitly expected to do. By the end, I can usually see the structural pattern that connects the recurring symptoms.

Until that picture exists, anything anyone proposes — including the founder — is solving the surface, not the design. With the picture, the founder can decide what's worth changing. Without it, the same problem returns wearing different clothes every quarter.

The diagnostic is the most underrated leverage point in scale-up work. Founders typically resist it because it doesn't feel like progress; the fires are still burning, and producing a written document feels indulgent compared to fighting them. But the diagnostic is what turns the fires from a list of separate problems into a coherent structural pattern. With that pattern named, the choices become tractable. Without it, every decision is a guess about what might help, and most guesses don't.

References

• Schein, E. H. (2010). Organizational Culture and Leadership (4th ed.). Jossey-Bass.
• Argyris, C. (1976). Single-loop and double-loop models in research on decision making. Administrative Science Quarterly, 21(3), 363–375.
• Schön, D. A. (1983). The Reflective Practitioner: How Professionals Think in Action. Basic Books.
• Weick, K. E. (1995). Sensemaking in Organizations. Sage Publications.