The Architecture of Reasoning

The problem is not intelligence

Most teams that make poor decisions are not lacking in intelligence. They are not careless, inexperienced, or poorly motivated. They are full of smart, capable people who genuinely want to do good work.

And yet the same patterns repeat themselves, across industries, across company sizes, across cultures. Priorities shift without explanation. Good ideas stall in committees. Leaders ask for honest input and receive polished consensus. Teams align on a plan and then quietly pull in different directions.

The problem is not intelligence. It is architecture.

What AI revealed

When I started working seriously with large language models, I expected to find a new kind of tool. What I found instead was a mirror.

The way a well-designed prompt produces clear, useful reasoning — and the way a poorly designed one produces confusion, hedging, and hallucination — maps almost perfectly onto the way human teams behave under different structural conditions.

Give a language model ambiguous goals and no constraints, and it drifts. Give it clear context, defined roles, and explicit reasoning steps, and it performs with surprising precision. The model has not changed. Only the architecture around it has.

The same is true of teams.

A new lens for human systems

The Architecture of Reasoning uses the discipline of prompt engineering as a lens for understanding how humans reason, communicate, and decide — individually and together.

This is not a book about AI, though AI is part of the story. It is a book about the hidden structures that shape how we think, how we communicate, and how we make decisions under pressure.

It draws on systems thinking, cognitive science, organisational design, and two and a half decades of working with engineering teams, founders, and leaders across small businesses, agencies, and the public sector.

The dual architecture

The central argument of the book is simple: every organisation has two architectures.

The visible architecture — the org chart, the meeting cadence, the documented processes — is the one that appears in handbooks and onboarding decks.

The invisible architecture — the unspoken assumptions, the patterns of communication, the structural pressures that shape what people say, what they omit, and what they decide — is the one that actually runs the organisation.

Most leadership effort goes into the visible architecture. Most problems live in the invisible one.

The book offers a practical framework for identifying, understanding, and redesigning the invisible architecture — not by overhauling culture in the abstract, but by changing the specific structures and conditions under which reasoning happens.

Why this matters now

We are in a moment of unprecedented complexity. AI is changing the nature of knowledge work. Organisations are being asked to move faster, decide better, and adapt more readily — often with less certainty than before.

In this environment, the quality of your team's reasoning is not a soft concern. It is a strategic one.

The teams that will navigate this moment well are not necessarily the ones with the best technology or the most experienced people. They are the ones who have built the conditions for clear thinking, honest communication, and sound collective judgment.

What this book gives you

• A framework for diagnosing the structural causes of poor team decisions
• Practical tools for improving reasoning quality at the individual, team, and organisational level
• A new way of thinking about communication, context, and clarity — drawn from the discipline of prompt engineering
• Real examples from two and a half decades of working with teams across industries and growth stages

Who this is for

This book is for leaders, founders, and senior practitioners who suspect that the problems in their teams are not people problems — they are system problems.

It is for anyone who has sat in a meeting where the decision made was obviously wrong, and wondered how it happened.

It is for the engineering leader who knows their team is capable of more, but cannot quite put their finger on what is getting in the way.

It is for the founder who has hired well, built something real, and is now watching the organisation slow down as it scales.

The shift

The shift this book is trying to create is not a new methodology or a consulting framework. It is a change in how you see.

Once you can see the invisible architecture — once you understand the structural conditions that produce drift, misalignment, and poor decisions — you cannot unsee it. And once you can see it, you can change it.

That is the work.

Coming soon

The Architecture of Reasoning is currently in development. Early access is available for those who want to read along as the book takes shape — including draft chapters, working frameworks, and the occasional dead end.