A founder I worked with took a four-week break last summer for the first time in eleven years.
He'd hired a strong COO eighteen months earlier, the leadership team was experienced, and he genuinely believed the company would run fine without him. He told me, on the call before he left, that this was the test he'd been building toward for a decade. He came back tanned, rested, and ready.
He was back for three days before he realised something had broken.
The senior team had made decisions while he was away, which was the point. The decisions were reasonable, defensible, and slightly off in a way that took him a week to diagnose. The pricing on a major proposal had been negotiated lower than he'd have allowed. A junior hire had been signed off without the level of scrutiny he applied. A difficult client had been handled with more accommodation than the company's standards justified.
Each individual decision was fine. The pattern was the problem.
His culture didn't survive him being out of the room. It just deferred to whoever was in the room instead.
This is the most subtle failure mode I see in founder-led companies, and it almost always reveals itself the first time the founder genuinely steps back. Not the surface-level absence of a holiday or a flight. The real absence, where the company has to operate on its own internal compass for a meaningful stretch.
Most cultures fail this test. The failure is invisible until it isn't.
The mistake founders make is confusing culture with personality
Founders build culture from the front, by which I mean they walk into the office every day and the culture takes the shape of their presence, their priorities, their judgement, their tolerances. The team learns what's valued by watching the founder, and they learn fast.
This produces cultures that look strong from the inside, because everyone behaves consistently. They're behaving consistently with you, which is different from behaving consistently with a set of principles the company has actually adopted as its own.
The proof is what happens when you leave the room. A culture that depends on your presence isn't a culture. It's a personality cult with better branding, and the discovery usually comes too late to fix easily.
Patagonia is the cleanest example I know of a culture that genuinely survived its founder. Yvon Chouinard wasn't trying to build a company that depended on him. He spent decades building a company that operated from a clearly articulated set of environmental and operational principles, and when he transferred ownership to a trust in 2022, the company kept doing what it had always done because the principles were the company. Most founders aren't building that. They're building their own preferences, scaled.
The deeper mechanism is worth naming. Founders don't write down what they actually believe, because they don't realise they believe it. The standards live inside their judgement, applied in real-time, on a thousand decisions per quarter. A senior team that makes decisions in the founder's absence isn't applying a different set of standards. They're applying no codified standards at all, because the standards never existed outside the founder's head.
The Room Test
Most culture diagnostics are vague, asking questions about values and behaviours that produce answers nobody can act on. The Room Test is concrete, because the question it asks is binary.
I call this the Room Test, and the structure is built around three specific scenarios that reveal whether your culture has been codified or whether it lives in your presence.
1. The Decision Test (does the decision land in the same place without you?)
Definition. When the senior team makes a meaningful decision in your absence, does the outcome match what you would have decided, on the same evidence, more than 80% of the time?
Below 80%, the team is making decisions on their own internal compass, which is a mix of guessing what you'd want and applying their own preferences.
Above 80%, the standards have transferred, even if nobody can articulate them precisely.
Worked example. A founder ran this test for one quarter. He had his COO send him every meaningful decision she'd made without him, with the context she'd had at the time. He scored each one against what he'd have decided. The match rate was 61%. The 39% mismatch wasn't a competence issue. It was a codification issue. He spent the next quarter writing down his decision principles for the eight categories where mismatches kept happening, and the match rate moved to 87% over six months.
Trade-off. Writing down your decision principles is genuinely hard, because you've been making the decisions implicitly for years. The work of articulation feels slow, but the alternative is a permanent gap between your judgement and the company's judgement, which is a tax on every decision the company makes without you.
2. The Standards Test (does the work hold the same bar without you?)
Definition. When the team produces work in your absence, does it meet the same quality bar you'd have demanded if you'd been involved at every stage?
The honest answer is usually no, and the gap usually shows up in the details. Slightly looser proposals, slightly weaker hires, slightly more accommodation in client negotiations. None of it dramatic. All of it cumulative.
Worked example. A founder noticed that his team's proposal quality had drifted in the four weeks he'd been less involved in commercial work. He pulled six recent proposals, scored each against the standard he'd have demanded, and found that four of the six were 70-80% of his bar. The team had been holding 70-80% as "good enough" because nobody had explicitly told them what 100% looked like. He wrote a one-page proposal standards document with five examples of work at the bar and three at the bar and below. The next four proposals all hit 95%+.
Trade-off. Codifying standards means making explicit what you've been judging implicitly, and some of your team will resent the increased specificity. They've been operating on intuition and approval, and you're now asking them to operate on documented standards. The friction is real for the first six months, and the company that emerges from it is one that holds its own bar without you in the room.
3. The Pressure Test (does the team behave the same under stress without you?)
Definition. When something difficult happens in your absence, does the team handle it the way the company would want it handled, or does it default to whoever is most senior in the room?
This is the test that reveals culture most clearly, because culture is what happens under pressure, not what happens on a calm Tuesday. A team that defers to the most senior person under stress doesn't have a culture. It has a hierarchy.
Worked example. A founder was on holiday when a major client called the office threatening to cancel a £400K contract over a delivery issue. The team handled it. They handled it well, by his subsequent assessment. They saved the contract. Then he asked his three most senior team members, separately, what principle they'd applied in handling it. He got three different answers. The right outcome had emerged from three different reasonings, which meant next time it might not. He spent the next quarter codifying the company's approach to client crisis, and the principle now lives outside any individual.
Trade-off. Codifying pressure responses requires you to articulate values you've been holding implicitly for years, and some of those values will look smaller or more uncomfortable in writing than they felt in your head. The discomfort is the work. Values that can't survive being written down weren't really values. They were instincts, and instincts don't scale.
Why three tests and not one
The three tests catch different failure modes. The Decision Test catches the gap between your judgement and the company's judgement. The Standards Test catches the gap between your bar and the company's bar. The Pressure Test catches the gap between your principles and the company's principles.
A culture can pass one test and fail the others. Most founder-led companies pass the Decision Test on routine matters, fail the Standards Test in subtle ways, and fail the Pressure Test on anything serious. Running all three is how you find out which gaps actually matter, instead of guessing.
A culture is what happens when you're not there. Everything else is just management with good lighting.
What to do this week
Run the Decision Test for the next 30 days. Have your senior team email you, every Friday, a list of meaningful decisions they made that week without you. Just the decisions and the context, not asking for approval.
Score each one privately. Would you have made the same call on the same evidence? When the answer is no, write down why, in one sentence. After four weeks, the patterns in your "no" sentences are your codification list.
That list, expanded into one or two pages of decision principles, becomes the spine of a culture that survives without you. The work is slow, the work feels indulgent, and the work is the highest-leverage thing you can do as a founder once the company is past £3M of revenue.
Most founders never do it. The ones who do build companies that outlast them.
Here's the part of this work nobody tells you about. Codifying a culture isn't a writing exercise. It's an identity conversation. You're being asked to articulate what you actually believe, in a way the company can use without you, which means you're being asked to look at the implicit standards you've been holding for years and decide which ones are real and which ones are just personal preference scaled by accident.
That conversation is almost impossible to have alone. Your team can't have it with you, because they're the ones being asked to carry what you write down. Your friends can't have it with you, because they don't know the business well enough. Your spouse definitely can't.
That's the work we do inside Tomorrow's Potential. A group of founders at your stage, all looking at the same question from different angles, with permission to ask each other the things their senior teams can't.
