A founder finishes a Traction implementation. Vision-Traction-Organizer on the wall. Level-10 meetings every Monday. A scorecard the team genuinely reads. Quarterly off-sites. A leadership team that’s developed real muscle and confidence over eighteen months.
He’s still working sixty-hour weeks. Still the bottleneck on every meaningful decision. Still hasn’t taken a real fortnight off in years. The business runs more smoothly than ever, and he’s as trapped as he was at the start.
The implementation didn’t fail. It did exactly what it was designed to do. It just wasn’t designed to fix the thing that was actually wrong with him. EOS works on the business. He needed work on the founder. Different job, different room.
The two jobs that get bundled together
Founder development splits into two distinct jobs that get treated as one. The first is identity work: how the founder spends their time, what only they can do, what they should stop doing, who they’ve become to the team. The second is systems work: vision, people, data, issues, processes, meeting cadence, the scorecard. Different formats are built for each. The shared marketing vocabulary hides the difference.
Identity work is internal. It’s about what the founder uniquely contributes, what they hold onto for reasons that aren’t really about value, and what an honest week of their time looks like. It’s slow, often uncomfortable, and produces decisions about how the founder shows up rather than diagrams on the wall.
Systems work is external. It’s about how the business runs without continuous founder intervention: who decides what, what gets measured, when meetings happen and what they’re for. It produces frameworks, scorecards, accountability charts, and visible structure. It’s faster to point at and easier to invoice for.
Both are legitimate. Both produce real results. They don’t substitute for each other.
What founder identity work actually looks like
Strategic Coach has run since 1989 on a single premise: most founders spend a substantial part of their week doing things only they think they have to do. The work is to identify what only you should do (Sullivan calls it “unique ability”), redesign your time around it, and let go of the rest. Quarterly three-day workshops, a coach you keep through multiple programmes, and a peer cohort sit alongside the methodology.
Independent founder coaches do similar work in different shapes: monthly or biweekly sessions, structured around the founder’s own situation rather than a fixed methodology. The common thread is that the work is on you, not on the org chart. What you delegate. What you stop. What you reframe about your role. Why the third hire never quite worked out. Why you can’t take a holiday without checking in.
When this kind of work fails, it’s usually because the founder wanted answers about the business and got asked questions about themselves instead. When it succeeds, the founder reorganises their week, hands off something they’d been quietly insisting only they could do, and the team grows into the space.
What business systems work actually looks like
EOS, codified in Gino Wickman’s Traction (2012), runs on five domains: vision, people, data, issues, and processes. Implementation is two to three years with a certified implementer who facilitates quarterly off-sites and supports monthly leadership-team rhythms. Scaling Up (Verne Harnish) runs a similar pattern at larger scale on talent, execution, cash, and strategy. Both produce visible structure: scorecards, accountability charts, weekly meeting agendas, ninety-day rocks.
This work targets the leadership team and the operating rhythm of the business. Done well, it gives the team a shared language, clear decision rights, and a cadence that holds without the founder pushing it. The business gets more predictable. Information moves through the right meetings rather than through the founder’s inbox. Leaders start making decisions in their domains instead of escalating.
Done badly, it produces a beautiful set of frameworks the team performs at the implementer’s visit and quietly bypasses the rest of the time. The most common failure mode is implementing because someone said you should, without genuine leadership-team buy-in. The result is structure that’s technically correct and operationally hollow.
Where peer-advisory and fractional executives sit
Peer-advisory groups (Vistage, EO, YPO) sit between the two jobs. They develop founder capability through peer learning, lateral perspective, and accountability, but they don’t primarily work on either business systems or founder identity. They give you a room to think out loud, with people who’ve lived their own version of your problem. Useful, often valuable, but not a substitute for either of the two main jobs.
Fractional executives sit somewhere different again. A fractional COO or CFO implements business systems and takes direct responsibility for outcomes in their domain. They build the operating rhythm, the cash discipline, or the sales engine. They don’t typically develop founder capability. The founder gets capacity off their plate, not coaching about how they show up.
That can be exactly right. It can also leave the founder still trapped. If the bottleneck was identity (the belief that only you can do this was the wrong belief, not the wrong reality), bringing in fractional capacity gives the founder a more efficient version of the same constraint. The fractional COO now does the thing the founder shouldn’t have been doing in the first place. The founder still hasn’t done the work on themselves.
Diagnose: is this you, or is this the business?
The question that decides which job to start with is one sentence: when you watch your business, is the limit in you or in the team and the systems? If your team is doing fine and you’re the constraint, identity work first. If you’re personally fine and the team can’t ship, systems work first. If both are limits, both jobs need doing, and the order matters.
The bad orderings are predictable. Systems work first, when the founder is the actual bottleneck, produces a more efficient version of the same trap. The team gets better at running their meetings, the founder still holds every meaningful decision, and the business gets nicer to be in without becoming any less dependent on its owner.
Identity work first, when the team is genuinely broken, produces a calmer founder watching a slow-motion crash. The founder gets clear on what they should and shouldn’t be doing, but the team doesn’t have the capability or structure to take on what’s being handed to them. The founder ends up either reabsorbing the work or watching things degrade.
The good order is whichever bottleneck is actually upstream. For most established founders past £1.5m revenue, in my experience, identity work is usually upstream, because the team’s lack of capability is often a downstream effect of the founder still doing too much. But not always. Diagnose first.
What to do for twenty minutes tonight
Take a piece of paper. Write down the three things in your business that have you most worried right now. For each, ask one question: is this thing broken because of how I show up, or is this thing broken because the team or the system around it can’t carry it? Underline whichever is more honest.
If two of the three are about you, the next conversation is with someone who does identity work: a founder coach, a Strategic Coach intake, or a long walk with a partner or peer who’ll ask the questions back to you. If two of three are about the team and the systems, the next conversation is with an EOS implementer or Scaling Up coach. If it’s a clean split, you probably need both, and the order is whichever bottleneck blocks the other from improving.
The mistake to avoid is the one that costs eighteen months and a five-figure invoice: assuming the right next move is whichever format is most familiar in your network. The work that fixes the bottleneck is the work that’s aimed at the bottleneck. Naming yours, on paper, in twenty quiet minutes, is the cheapest hour of consulting you’ll ever buy.
