Thinking out
loud — in public.

Every organisation has a recurring problem. The one that gets solved in Q1 and returns in Q3. The conversation that happens in every leadership meeting but never quite resolves. The hire that was supposed to fix it, didn't, and was followed by another hire with the same brief.

Leaders describe these problems in human terms — the wrong people, the wrong attitude, insufficient skills, poor culture. And sometimes that's true. But more often, the recurring problem is structural. It keeps coming back because the intervention keeps being applied to the symptom rather than the cause.

Here is the structural pattern that generates most recurring problems: a gap in one area of the organisation is being compensated for by an adjacent area working harder than it should. The compensation is invisible — it looks like commitment, it looks like high performance, it looks like a team that just gets things done. Until it doesn't anymore.

The intervention is almost never in the gap. It is in the thread adjacent to it — the one that's working too hard to cover what's missing.

The accounts team that always catches finance errors is compensating for a weak handoff in operations. The founder who answers every client email directly is compensating for an unclear client communication thread. The manager who works weekends before every board meeting is compensating for a structure that doesn't give leadership what it needs without extraordinary effort.

When you remove the compensating thread — when the over-performing team burns out, when the founder steps back, when the manager leaves — the gap becomes visible suddenly. It feels like a crisis. It was always there.

The fix is not to find a replacement for the compensating thread. It is to close the gap the compensation was covering. That requires seeing the whole — which is exactly what recurring problems prevent you from doing, because they consume the attention you would otherwise use to look further out.

Name the thread that is working hardest in your organisation right now. Then ask what it would stop working on if the gap it's covering were closed. That is where the structural intervention lives.

There is a version of complexity that organisations are proud of. The intricate process. The nuanced decision-making framework. The deep institutional knowledge that only certain people possess. This complexity feels like sophistication — like evidence that the organisation is doing something hard and doing it well.

It is usually neither. It is usually the accumulated weight of decisions that were never revisited, processes that were built for a context that no longer exists, and knowledge that was never made explicit because nobody had the time or the tools to do so.

I spent years working in accessibility — designing environments and information systems that could be navigated by anyone, regardless of cognitive load. The core insight from that work is simple and applies everywhere: if something is hard to navigate for someone with a high cognitive load, it is hard for everyone. We just don't notice the difficulty until it becomes a crisis.

What you leave out matters as much as what you include. A business that can be explained on one page is not a simple business. It is a well-designed one.

The organisations that scale well are not the ones with the most sophisticated systems. They are the ones where the most important information is the most accessible. Where a new person can understand the whole quickly. Where decisions don't require institutional memory to make — because the institutional memory has been made explicit, structured, and shareable.

This is what the one-page fabric map is for. Not to reduce the complexity of the business — complexity is often real and necessary. But to make the structure of that complexity visible, so that the people inside it can navigate it, act on it, and build on it without needing to carry the whole map in their heads.

If your organisation cannot be explained on one page without losing something essential, the problem is not the business. It is the map. Build a better map.