By Warren Jonas, ICF PCC · Executive Coach · 20+ years founding, exiting and coaching scaling businesses

The founder I'm about to describe had done the work.

He'd named the North Star. He'd committed to it for the year. His board had signed off. His team knew where they were going. Every senior leader could tell you, without checking the deck, what the twelve-month picture looked like. He'd built two years of coaching, one full offsite, and three whiteboard sessions into getting to this point.

And nine months in, he was miles behind where he'd said he'd be.

Not because the strategy was wrong. Not because the team was bad. Both were good. He kept telling himself both were good.

The boat was rowing hard. It just wasn't moving.

That's the E pillar. Execution. And it's the one that fools most founders — because when you don't have it, the effort is still there, the meetings are still there, the roadmap is still there, and nothing about the surface tells you why the shore isn't getting closer.

Three scenes from the same problem

Monday morning, 09:00. The senior team meets every Monday. Two hours. Everyone shows up. The agenda is decided in advance. Decisions get made — some of them good. Then Wednesday, someone asks about a decision from last Monday. Nobody quite remembers what was agreed. The person who was supposed to own it thought someone else was. The person who 'someone else' turns out to be is on holiday. It gets pushed to next Monday. Next Monday, they make new decisions. Same shape. He's been running this meeting for two years. He thinks it's the operating rhythm. It's actually the operating theatre.

A senior hire, six months in. Sarah is his Head of Operations. Out of a company doing three times his revenue, took a pay cut for the mission, works Saturdays. Warm, sharp, respected. He hired her to fix the delivery problem. Six months in, delivery isn't fixed. Sarah is exhausted. Every project she picks up has three other people involved who don't have clear roles. Her calendar is full of meetings called by other people. The founder tells himself she's still ramping. She isn't. She's drowning in a system that has no owners, only participants.

His own week. Forty-seven open loops in his notes. Three hours of deep work on Tuesday morning. Everything else — reactive. Slack, email, a call that could have been a message, a meeting he didn't need to be in but was invited to, an escalation from Sarah about a decision she needs him to make. He gets home at 8pm on a Wednesday and realises he didn't move a single strategic thing that day. He tells himself it was an unusual week. It wasn't. It was Tuesday, Wednesday and Thursday of every week for the last quarter.

What the coach saw

He'd been in the coaching room for about six weeks by the time the pattern crystallised.

It wasn't a strategy problem. He knew that. He'd checked twice. It wasn't a team problem. His team was better than the team he'd had at his last company. It was, the coach said gently, an execution problem — which is a specific thing, and different from what most founders think it is.

'Say you rowed for six months and moved five metres. Would you row harder?'

'Probably. What else is there to do?'

'You could look at the oar.'

The founder looked at the oar. There was nothing wrong with it.

'You could look at the water.'

He looked at the water. Slow current. Not helping, not blocking.

'You could look at whether the eight people in the boat are pulling at the same beat.'

He hadn't looked at that.

Rowing versus moving

Watch an eight-person rowing crew and you'll see something that looks like effort — big shoulders, hard breathing, oars biting deep into the water. But what actually moves the boat isn't the effort. It's the rhythm — eight people pulling at the same exact beat, someone counting, someone watching the water rather than their own oar.

Take any one of those things out and the effort goes up while the speed goes down. You can watch it happen. Boat that was moving cleanly starts to churn foam. Same effort. Less movement.

Rowing is effort. Moving is what happens when the effort has structure. Most founders confuse the two.

There's a line Patrick Lencioni put in The Five Dysfunctions of a Team twenty years ago that everyone's read and almost nobody uses. He said:

'If you could get all the people in an organization rowing in the same direction, you could dominate any industry, in any market, against any competition, at any time.'— Patrick Lencioni, The Five Dysfunctions of a Team (2002)

Most founders read that line, nod, put the book down. Then they don't build the system that lets it be true. Execution is that system. It's what turns Lencioni's sentence from a good quote into an actual business.

The system that turns strategy into shipped work

Execution isn't harder work. Execution is a system with four specific pieces. When any of the four is missing, the boat rows hard and moves slowly.

Piece one: rhythm. A weekly cadence where the team commits to small things and shows up seven days later to say whether they did them. Not a status meeting. Not a big-picture strategy meeting. A rhythm — every Monday morning, or every Friday afternoon, the same shape. Commitments named at the start. Same commitments checked at the end of the next one. Anything not done gets a reason attached — not an excuse, a reason — and either gets re-committed or dropped. The rhythm doesn't have to be elaborate. It has to be religious. Miss it once and the team learns the rhythm is optional. Miss it three times and there is no rhythm.

Piece two: ownership. Every commitment has one name against it. Not two. Not 'the team.' Not 'we.' One. If you can't name one person who is going to be red or green next week on a given item, you don't have a commitment. You have a hope. Most execution problems in scaling companies are ownership problems dressed up as capability problems. Sarah wasn't drowning because she wasn't good enough. She was drowning because the projects she was working on had no clear single owner — which meant she was implicitly owning them, along with everyone else who was implicitly owning them, which is the definition of nobody owning them.

Piece three: accountability. Someone in the room who can look you in the eye and ask 'did you do the thing you said you'd do?' without any ego about the answer. Usually the founder can't do this to themselves. Which is why founders who scale fastest almost always have someone — a coach, a mentor, a chair, a co-founder they trust — in the accountability seat. Not to judge them. To ask the question, weekly, without agenda.

Piece four: commitment. Watch most senior leadership meetings and you'll see something strange happen. People talk. They debate. They surface concerns. Then they walk out — and none of them have actually agreed to the same thing. Lencioni called this the Absence of Commitment. Everyone in the room thinks they've discussed something. Half of them think they've decided it. The other half think they're still deciding. The following week, they come back to talk about it again — because nobody actually walked out with a commitment. The fix is tiny but religious: at the end of every commit-and-check meeting, each person says out loud what they've committed to for the next seven days. In their own words. Ninety seconds per person. That ninety seconds is the difference between a meeting that decides and a meeting that just talks.

Rhythm + ownership + accountability + commitment. That's the system. Every founder who scales fast has some version of it. Every founder who plateaus has broken or never built one of the four.

What the founder confused it with

He'd been trying to fix execution by adding. More meetings. Better tooling. A project management system he'd rolled out in Q2 that nobody used properly. A new senior hire (Sarah) he was hoping would solve it. A daily standup he'd tried for three weeks and quietly killed. A sprint model he'd read about in a book.

None of them worked because none of them addressed the three pieces. All of them added surface complexity while leaving the rhythm-ownership-accountability triangle broken. Execution is not fixed by adding. It's fixed by picking three habits and holding them religiously for six months.

Most founders don't have the patience for that. They want the system that fixes execution to be as exciting as the strategy that named the destination. It isn't. The system that fixes execution is boring. That's the whole point.

The compounding power of micro-changes

Most founders think execution is a step-function. Build the perfect system, ship the perfect roadmap, hire the perfect COO, and suddenly the boat is moving at four knots instead of two. It never works like that.

Execution improves by micro-change. One percent better this week than last week. A slightly clearer commit meeting. One extra hour of deep work carved out on Tuesday. A single project reassigned to a clearer owner.

None of those matter on their own. Two years of them, compounded weekly, and the business is unrecognisable.

The trap is that micro-changes are boring. Founders looking for the transformation moment miss the small changes because they don't feel like transformation. But the founders who scale fastest are the ones who committed to being one percent better every week for a hundred weeks — not the ones who tried to be a hundred percent better once.

The rhythm is the mechanism. Every weekly meeting is a chance to make one small adjustment. Over a year, that's fifty adjustments. Over three years, a hundred and fifty. That's how a decent execution engine becomes a great one — not from a rebuild, but from a hundred and fifty small refinements nobody outside the boat would notice.

Cadence isn't just structure. Cadence is the discipline that lets you keep doing what's working and quietly evolve what isn't. It's how you learn from every week without needing a review, an offsite or a reorg.

A proven starting framework — Death by Meetings

If the rhythm-ownership-accountability-commitment system is the what, one of the cleanest how frameworks I've seen founders adopt is Patrick Lencioni's Death by Meetings (2004).

Lencioni proposes four meeting types, each with a distinct job. Most companies collapse them into one weekly two-hour 'leadership meeting' that ends up doing none of them well. The framework instead separates the four:

You don't have to adopt every layer at once. Most founders benefit from starting with the weekly tactical done properly (which is 80% of the value) and adding the monthly strategic later.

The reason this framework works isn't because Lencioni is clever. It's because each meeting type does one job, and stops doing the other three's jobs badly. If you're picking one structural framework to adopt this year, this is the one I'd start with.

Why the right tools matter more than you think

There's a specific reason SaaS platforms are useful for execution, and it isn't the feature list.

Every good SaaS platform is a piece of the world's best practice in a box. The company that built it has watched thousands of teams try to solve the same problem — running weekly rhythms, tracking commitments, holding accountability, prioritising a roadmap — and encoded the patterns that work into the product.

When you adopt the tool, you're not just getting features. You're borrowing execution discipline you didn't have to invent.

A good project management tool enforces ownership because it makes the 'assignee' field mandatory. A good OKR platform enforces commitment because it demands specific measurable outcomes, not vague intentions. A good CRM enforces cadence because it prompts follow-ups on a schedule you don't have to remember. The tool holds the discipline so the founder doesn't have to.

This is why 'we don't need software, we have a good spreadsheet' is almost always a mistake at fifteen people and above. The spreadsheet gives you flexibility. What you actually need is constraint. The tool that constrains you is doing the execution work — quietly, every day, without needing anyone to enforce it.

Pick your tools deliberately. Adopt them fully. Then let them do the boring parts of execution so you and your team can focus on the parts only you can do.

Two patterns I see, twenty years in

Pattern one: the founder who can't stop adding. Almost always a first-time founder or a serial founder who scaled to £2-5m before. Believes speed is strength. Adds priorities every week — usually because a Monday-morning idea felt inspired, or a competitor announced something, or a customer asked for something and it seemed doable. Team of 15 has 47 things on the roadmap. Every one of them defensible in isolation. Every one of them slowing every other one down. The tell isn't the roadmap. The tell is what happens in the commit meeting. This founder shows up with three commitments — and by the end of the meeting has added two more, because 'wait, actually, we should also...' Every week. The commitments never get done because they never stop being added to. The fix isn't more speed. It's picking three things and refusing to add a fourth for a quarter.

Pattern two: the founder who over-plans. Opposite failure mode, same root cause. Perfect roadmap. Beautiful OKRs. Cascaded objectives that reach four levels deep. Zero rhythm to execute against them. The plan sits in a document. The team looks at it once a quarter. Nothing ships weekly because there's no weekly. The fix isn't more planning. It's less planning and more rhythm. Cut the OKRs by 70%. Kill three of the four cascades. Put a weekly 30-minute commit-and-check meeting in place. Watch what happens.

Both patterns have the same coach + mentor answer. Both take about eight to twelve weeks to shift once the founder actually commits.

Why it's a coach + mentor job

This is one of the pieces of work where the coach + mentor combination is particularly valuable. A pure coach can hold the space for the founder to see they are the bottleneck. That's important — most founders don't see it. They see the team, the tooling, the market. They don't see that the execution system reflects the founder's own patterns of prioritisation and follow-through, and always will.

But naming the problem is only half the work. The other half is knowing what execution rhythm actually works at the scale you're at. A weekly cadence looks different at 15 people vs 40 vs 100. The right meeting length changes. The right level of detail in commitments changes. The right way to hold accountability without breaking psychological safety changes.

That's the mentor part. Someone who has seen fifty execution engines up close, at different scales, and knows which patterns tend to hold water. Coach helps the founder see themselves. Mentor tells them what shape of rhythm is likely to work for the next twelve months, at their current headcount, in their sector. Together, the founder can build the discipline in weeks instead of quarters. And once built, it compounds — because rhythm + ownership + accountability, once real, run themselves.

What changed for the founder

He didn't add anything. He killed the two-hour Monday. Replaced it with a 45-minute Monday commit meeting (each senior leader names their three commitments for the week) and a 45-minute Friday check (each of them reports red/amber/green, with a reason).

He named one owner for every project on the roadmap. Then he cut the roadmap. Any project without a single clear owner got killed or paused. From forty-seven items to eleven.

He put me — his coach — in the accountability seat for himself. Every Friday for fifteen minutes, I asked him: what did you say you'd move this week, and did you move it? First month, he was red more often than green. He hated it. He kept going. By month three, the pattern shifted. By month six, his own team's rhythm had started to mirror his. The boat started moving.

Not because the strategy changed. Not because the team changed. Because the rhythm got built.

The E in N-E-S-W

The North Star is the destination. Execution is how the boat actually gets there. E comes after N because there is no point building an execution engine if you don't know which shore you're rowing to. But E comes before S (Self-Awareness) and W (Winning), because until you're actually executing, you can't see your own patterns — and you certainly can't win anything.

Most founders skip E and go straight to hiring, or to fundraising, or to the next strategy pivot. That's the mistake. Execution is the second pillar for a reason: it's the discipline that turns everything else into results. If your team is rowing hard and the boat isn't moving, you don't have a team problem. You have an execution system problem. That's the work. That's the second thing.

Ready to build the rhythm that ships?

If any of this landed — if your team is rowing hard and you can't quite explain why the boat isn't moving — book a 30-minute call. Confidential, no obligation. We'll spend the half hour looking at your rhythm, your ownership, and your accountability, and naming which of the three is breaking.

Book a 30-Minute Call →

Frequently asked questions

What's the difference between strategy and execution?

Strategy is naming where you're going and why. Execution is the system that gets you there. Strategy is a decision (the shore you're rowing to). Execution is a discipline (the rhythm, ownership and accountability that turns that decision into shipped work every week). Most founders spend 80% of their time on strategy and 20% on execution. The founders who scale fastest do the opposite once the strategy is set.

Why do most founders fail at execution?

Three reasons: (1) They think execution is about working harder rather than building a system. So they add effort instead of building rhythm. (2) They don't hold ownership tight enough. Commitments get made to 'the team' instead of one named person, and diffusion of responsibility takes over. (3) They can't hold themselves accountable — nobody in the room asks them 'did you do the thing you said you'd do?' without ego, so their own commitments drift. Fix any one and things improve. Fix all three and the boat starts moving.

What's the single most important execution discipline?

Weekly rhythm. If you can only pick one thing, pick a 30-minute weekly meeting where every senior leader names three commitments for the week and reports red/amber/green on the previous week's three. Same time, same shape, every week, no exceptions. Everything else — ownership, accountability, prioritisation — flows out of that discipline. Miss the meeting once and the team learns it's optional. Miss it three times and there is no rhythm.

How much time should a founder spend on execution vs strategy?

Once the strategy is set for the year, roughly 70% execution / 20% people / 10% strategy. Most founders invert that — 70% strategy, because strategy is more exciting and easier to intellectualise. That's the trap. Strategy doesn't ship anything. Execution ships everything. The founders who scale fastest are usually the ones who resist the urge to keep re-strategising and instead put their energy into the boring weekly discipline of moving the boat.

What's the right meeting rhythm for a scaling team?

The single best framework I've seen founders adopt is Patrick Lencioni's Death by Meetings four-tier structure: daily check-in (5-10 min), weekly tactical (45-90 min, commit-and-check), monthly strategic (2-4 hours, deep on 1-2 issues), quarterly off-site (1-2 days). Most companies collapse all four into one two-hour weekly meeting that does none of them well. Separating them fixes it.

Can a coach help with execution — or is this a job for a COO?

Both, and they do different things. A COO builds and runs the operational engine — the systems, the tools, the processes. A coach works on the founder's relationship with the engine — where they're the bottleneck, where they're adding without thinking, where they're avoiding accountability. Most scaling businesses need both, and usually in that order: coach first (to see the pattern), COO second (to build the machine). Some founders try to hire a COO to solve what is actually a coaching problem. It rarely works.

What tools should I use for execution?

Fewer than you think, adopted more deliberately than you probably are. Every good SaaS platform for execution — project management, OKRs, CRM — is a piece of the world's best practice in a box. You're not just buying features; you're borrowing discipline. The mistake most founders make is either using a spreadsheet at fifteen people (flexibility becomes chaos) or adopting six tools shallowly. Pick one project management tool, one commit/check tool, and one CRM if you're customer-facing. Adopt them fully.

About this essay

Who wrote it: Warren Jonas — ICF PCC accredited executive coach, Henley Business School trained, serial founder with 20+ years building and exiting businesses across technology, consumer goods, financial services and professional services. Currently Board Advisor / Non-Executive Director across multiple UK and international scaling businesses.

How it was written: Drawn from real coaching engagements with founders scaling from 10 to 100 people. The Monday-morning founder is a composite of several clients — details changed, patterns real. Edited and polished with editorial support; core insights and story choices are Warren's.

Why it exists: Because execution is the second-most common gap I see in founder coaching engagements — after North Star. And the one that, when fixed, changes team morale and business trajectory faster than anything else.

Further reading

Compass Coaching™ is a registered trade mark of Jonas Partners Limited (UK00004036049). Compass Coach™ is the AI delivery platform for the methodology, available at compass-coach.co.uk.