There is a particular kind of meeting I have sat in many times — the kind where a leadership team is debating a strategic decision with real seriousness, genuinely trying to stress-test their thinking, and yet somehow the most important thing in the room goes unspoken for the entire two hours. Not because anyone is hiding it, but because nobody knows it is there. The assumption underneath the assumption is not a secret; it is something closer to wallpaper — so present, so load-bearing, so obvious to everyone in the building that it has ceased to register as a choice at all. This essay is about that layer, how to find it, and why the process of finding it is almost always the most uncomfortable and most useful thing a team can do together. I want to be specific about method, because vagueness is the enemy of this kind of work, but I also want to be honest about why the method gets skipped — and the answer there is less about time and more about what it costs to look clearly at what you have been taking for granted.
Why the first layer of assumptions is not the interesting one ¶
When people talk about challenging assumptions, they usually mean the explicit beliefs attached to a decision — the ones that, if you asked the team to write them down, they could produce in ten minutes on a whiteboard. We are assuming the market will grow. We are assuming our current customers will adopt the new format. We are assuming the regulatory environment stays roughly stable. These are real assumptions, and examining them is genuinely useful. But they are not where decisions break. Decisions break at the layer underneath — the beliefs that generate those assumptions, that make them feel reasonable enough to write down without embarrassment. The assumption that the market will grow is sitting on top of a quieter belief: that our model of what the market is for is correct. And that belief is sitting on top of something quieter still: that the people making this decision share a common picture of who the customer actually is. Nobody names that picture. It just sits there, doing its work.
What assumption mapping actually involves ¶
The practice I have found most useful is not a workshop exercise in the energetic, Post-it-covered sense — though it can live inside a workshop. It is closer to a structured conversation with a very specific discipline: you follow each stated assumption one level down, every time, until you hit something that feels almost too obvious to say aloud. That feeling of obviousness is the signal. When something feels too obvious to say, it means the group has stopped treating it as a choice and started treating it as a fact about the world. That is exactly the thing you want to make visible. The practical mechanics are simple. You take a decision the team is actually facing — not a hypothetical, not a practice scenario, but a live one with stakes — and you list every belief the decision depends on being true. Then, for each belief, you ask: what would we have to believe about the world, or about our organisation, for this to seem reasonable? You write that down. Then you ask again. You do this until the answers start to feel embarrassing in their simplicity, because simplicity at that depth is not naivety — it is bedrock.
The specific reason this step gets skipped ¶
I want to be precise here, because the usual explanation — that organisations skip assumption mapping because they are busy, or because nobody thought to do it — is too comfortable. The real reason is that surfacing the bedrock layer of belief is an act of exposure. It reveals not just what the team thinks, but how the team thinks, and more uncomfortably still, whose thinking has been shaping the room without attribution. When you follow the chain of assumptions down far enough, you almost always arrive at a model of the customer, the market, or the organisation that belongs to one or two people — often the most senior people — and that has been silently accepted by everyone else as empirical truth rather than perspective. Making that visible is not a neutral act. It changes the power dynamics of the conversation, at least temporarily, and it means that the person whose worldview has been functioning as a shared operating system now has to defend it as a point of view rather than simply inhabiting it as the room's default reality. That is uncomfortable enough that most teams, most of the time, find good reasons not to go there.
A concrete example of following the chain ¶
I worked with a team — professional services, mid-size, genuinely thoughtful people — who were deciding whether to expand into a new geography. The stated assumptions were sensible: the demand signals looked encouraging, they had relationships they could leverage, the margin profile of the new market resembled their existing one. We started the mapping exercise. Beneath 'the demand signals look encouraging' was 'our read of demand signals is reliable.' Beneath that: 'the indicators we use here translate to this different context.' Beneath that, and this is where the room got quiet: 'the problem we solve is universal rather than particular to the kind of client ecosystem we grew up in.' That last belief — that their offering addressed a human and organisational problem rather than a culturally specific one — had never been examined. It had been assumed so thoroughly that it had the texture of a law of physics. Once it was on the whiteboard as a sentence, three people in the room immediately wanted to push back on it, and the conversation that followed was more substantive than anything that had happened in the two hours before it.
How to hold the space when the bedrock appears ¶
The moment when a foundational assumption surfaces is delicate, and handling it badly is easy. The temptation is to treat the discovery as a verdict — as though finding that the team has been operating on an unexamined belief means the belief is wrong, or that the decision is now suspect. Neither follows. A belief can be foundational and unexamined and also substantially correct. The point of the exercise is not to invalidate anything; it is to convert an unconscious premise into a conscious one, so that the team is choosing to rely on it rather than simply never having noticed they were. The facilitation move I return to most often is to name the shift explicitly: we have just moved from assumption to operating premise, and now we get to decide whether we want to hold this consciously or examine it further. That framing takes the threat out of the moment. It also makes clear that examining a belief is not an attack on the person whose thinking it reflects — it is just the work.
What to do when you cannot map alone ¶
Some of the most important assumptions are invisible precisely because everyone in the room shares them — which means the mapping process needs at least one person who stands outside the shared context, or who has practised a particular kind of deliberate estrangement from it. This is one of the things an external perspective can genuinely offer, not as a consulting product but as a structural fact: someone who did not grow up in the organisation, or the industry, or the particular professional culture, will find the bedrock faster, not because they are smarter but because they have not yet learned to breathe the air. If you are doing this work internally, the closest substitute is rotating who runs the questioning — specifically, putting someone junior and relatively new in the role of following each assumption one level down and asking why it seems reasonable. The discomfort that creates is productive. It surfaces the implicit hierarchy of whose sense of the world counts as evidence.
On the ethics of making the invisible visible ¶
I want to end on something that does not often get said in discussions of strategic process: there is an ethical dimension to this work. When you map assumptions to their foundations, you are also mapping whose knowledge, whose experience, and whose version of reality has been given the status of organisational fact. Sometimes what you find is a founding team's early intuitions, calcified over years into doctrine. Sometimes it is a single leader's formative experience in a previous company, now functioning as universal principle. Sometimes — and this is the hardest kind — it is a structural bias that has been laundered through enough rounds of strategy that it no longer looks like a bias at all, just a reasonable way of framing the world. The assumption-mapping process does not resolve any of this on its own. But it makes it possible to see, and seeing is where agency begins. You cannot choose what you cannot name, and you cannot change what you have not yet recognized as a choice.
The work of mapping assumptions is not a workshop deliverable — it is a practice, something you return to each time a decision feels strangely resistant to examination, each time the room moves too quickly to consensus, each time a risk is dismissed with a phrase that begins "well, obviously." That phrase — well, obviously — is almost always a door. Behind it is something the team decided, long ago or very recently, to stop questioning. Which is not always wrong. But it should always be a choice.