Dubai · United Arab EmiratesBoutique growth & operations · investment partner
← All perspectives Operations · May 2026

An operating rhythm that survives the founder

Many businesses run beautifully as long as the founder is in the room, and stall the moment they are not. Here is what actually needs to be in place for that to stop being true.

You can usually tell within a week whether a business has an operating rhythm or is simply being run, day to day, by one person's judgement. The test is not how good the leadership meetings look. It is what happens when that person is unreachable for five days. In businesses without a rhythm, things quietly stop. Decisions wait. Numbers do not get reviewed. Work that was promised slips, because nobody else had the authority, or the information, to keep it moving.

This is not a founder problem in the sense of a personal failing. It is what happens by default in any business that has grown faster than its decision-making has been deliberately redesigned. Early on, the founder personally touching everything is the correct operating model: it is fast, and there is no one else with the context to do it better. The trouble starts when that same model is still running two or three years after the team has grown well past the point it should have changed.

What an operating rhythm actually is

Stripped of the jargon it usually gets dressed in, an operating rhythm is three things working together: a short, predictable cadence of reviews; numbers that the whole leadership team trusts without having to ask where they came from; and decisions written down as belonging to a named person, not to whoever is in the room when the question comes up.

None of that requires new software or a change in headcount. Most businesses already have the raw material. What is usually missing is the discipline of running the same cadence every week regardless of how busy it is, and the willingness to let someone other than the founder own a decision all the way through, including the version of it that turns out to be wrong.

The signs it is missing

  • Meetings happen, but nothing changes after them. Reviews exist on the calendar, but decisions still get remade informally afterwards, usually by the same one or two people.
  • The same question gets a different answer depending on who asks. That is usually a sign the decision was never actually assigned, only ever made ad hoc.
  • Things stall the moment the founder is on holiday. Not because the team is not capable, but because nobody else has been given the authority, or the numbers, to act without them.
  • The leadership team can recite activity but not results. They know what everyone has been doing. They are less sure whether it moved the numbers that matter.

What to put in place

Start smaller than feels sufficient. A rhythm that survives contact with a busy quarter beats an elaborate one that quietly stops running after six weeks.

  • One owner per number. Every metric the leadership team actually cares about should have exactly one named person accountable for it, not a function or a team.
  • A short weekly review. The same day, the same short list of numbers, the same length of time. Long enough to see what changed, short enough that it survives a busy week.
  • A dashboard the room trusts. It does not need to be sophisticated. It needs to be the same numbers, from the same source, every single week, so the conversation is about what to do rather than whether the figures are right.
  • Decision rights written down. A short, explicit list of what each leader can decide alone, what needs a conversation first, and what genuinely needs the founder. Most businesses are surprised how much can move to the first category.
The founder's job in a working rhythm is to set direction and remove blockers, not to personally approve everything that moves. If every meaningful decision still needs them in the room, the rhythm has not actually changed anything yet.

The test that matters

Ask what would genuinely break if the founder had no phone signal for a full working week. A specific, honest answer to that question, not a reassuring one, is usually the clearest brief for what still needs to be built. Most businesses find the list is shorter than they feared, and that fixing it is less about new process and more about finally letting someone else own the decisions they were already capable of making.

Where this leads

An Operating System Build puts the roles, the cadence, the dashboard and the decision rights in place, sized to the business as it actually is today rather than a template built for a much larger one.

Start a conversation
More perspectives Jul 2026

Finding the one constraint that is holding back growth

Mar 2026

Entering the UAE: what changes on the ground

WhatsApp