> Source: https://brendanlevin.com/insights/how-to-build-an-operating-rhythm/ > A standing operating cadence moves work through your team without you pushing every piece. Here is exactly how to build one that holds when you step back. For founders, owners, and operators # How to Build an Operating Rhythm for Your Business By Brendan Levin. 20+ years scaling businesses, from teams of 8 to 600 and budgets from startup to $100m. An operating rhythm is a standing weekly cadence of short, structured meetings that walk the numbers and surface what is stuck. **Without it, the founder is the rhythm.** Set one all-hands metrics review, one team leads check-in, and a clear rule for when something escalates versus gets resolved without you. See [how this fits the wider operating model](/insights/what-is-a-founder-operating-system/). Key takeaways - Without a standing cadence, you are the cadence, and work stalls the moment you step away. - Three meeting types cover almost everything: a weekly metrics review, a leads sync, and an async blocker log. - The cadence only works if you define what resolves without you before the meeting happens. - A rhythm installed into the business holds when you are out; a rhythm held in your head does not. ## Why 'just meet more often' does not fix the problem Most founder-led businesses already have meetings. What they do not have is a cadence with a defined purpose, a defined owner, and a defined output. The founder sits at the centre, fields questions, makes calls, and the meeting ends when their energy runs out. That is not a rhythm. That is a recurring dependency. The real problem is structural. Work routes back to you not because your team is slow, but because no one has been given a clear lane to resolve things inside. [If your business stalls when you step away](/insights/why-does-my-business-stall-when-i-step-away/), a denser meeting schedule will not fix it. A well-designed cadence will. A working operating rhythm has three properties: it runs on a fixed day and time every week regardless of what else is happening, it surfaces blockages rather than just reporting status, and it resolves most things without pulling you into the detail. If your current meetings do not do all three, they are adding overhead, not removing it. ## The three-meeting cadence that actually moves work You do not need a complex system. You need three recurring slots, each with a specific job. First, a weekly metrics review with the full team or full leadership group. Fifteen to twenty minutes. You look at the same four to six numbers every week: the ones that tell you whether the business is moving or stuck. No slides, no narrative, just the numbers and one question per number: what changed and why? This meeting is not for updates. It is for early warning. Second, a team leads check-in, also weekly, thirty minutes maximum. Each lead brings one thing that is stuck and one thing that moved. The rule is simple: if something can be resolved below you, it gets resolved below you before this meeting. You are not there to unblock everything. You are there to remove the one or two things only you can remove, and to notice patterns in what keeps surfacing. - Weekly metrics review: 15 to 20 min, fixed numbers, same format every week, no narrative prep required. - Team leads check-in: 30 min max, one blocker per lead, most resolved before the meeting starts. - Async blocker log: a shared doc or channel where anything smaller than a defined threshold gets logged and resolved without a meeting at all. ## The escalation rule that makes the cadence hold A cadence without an escalation rule collapses back to the founder within two weeks. People default to the path of least resistance, and if that path is asking you, they will ask you. Write one rule and share it before you launch the cadence. A working version looks like this: any spend decision under $2,000, the owning person acts and tells you after in the blocker log. Any spend decision between $2,000 and $10,000, the lead approves and flags it in the weekly check-in. Anything above $10,000, or anything with a legal or reputational dimension, comes to you before it moves. The numbers will vary by business. The structure does not. This is not about trust. It is about removing ambiguity. When the threshold is clear, the person does not need to ask. When they do not need to ask, the work moves. [Setting decision rights by threshold](/insights/how-to-set-decision-rights-in-your-business/) is what separates a cadence that holds from one that dissolves the first time you travel. ## What a working cadence looks like week one versus week eight The first week will feel slower than just doing it yourself. That is expected. You are trading short-term speed for a structure that runs without you. By week four, most of the escalations that used to come to you during the week will get resolved in the check-in or below it. By week eight, the rhythm runs whether you are in the room or not. The honest test: take a full week away with no contact. What stalls is what still runs on you. If the metrics review still happens, the blocker log still moves, and the leads still resolve their own stuck items, the cadence is working. If everything waits for you, the structure is not installed yet. Week What you typically see **Week 1 to 2** Escalations still come to you between meetings. People are testing whether the threshold is real. **Week 3 to 4** Most sub-threshold decisions resolve without you. The check-in gets shorter. **Week 5 to 8** The cadence runs on its own day regardless of your schedule. Blockages surface early instead of late. **Week 8 onward** You step out for a week and the metrics review still happens. Work does not stall. ## When the cadence is not enough on its own A well-built cadence does a specific job: it moves work through the team on a predictable rhythm. It does not replace clear direction (the single outcome the team is organised around this year) or defined decision rights (who can decide what without involving you). Those three pieces work together. A cadence without direction gives people a meeting but no shared compass. Decision rights without a cadence mean the right people never compare notes. [Getting the business to run without you](/insights/how-to-get-my-business-to-run-without-me/) requires all three to be installed in the business, not held in your head. If you are not sure which piece is missing, the [free Founder Dependency Diagnostic](/executive-diagnostic) maps where your week actually goes and shows what still runs on you. ## The difference between an advisor installing this and you figuring it out alone You can build this yourself. The concepts are not complicated. What takes time is diagnosing which meetings to cut, which numbers to track, and where the real escalation thresholds sit for your specific business. Founders who try to design this alone often build a cadence that reflects how they wish the business worked rather than how it actually works today. An operating advisor does this as a defined structural engagement: audit what exists, identify where the dependency lives, design the cadence and decision thresholds for your actual business, install them, and hand them back to you owning them. That is different from a fractional COO who runs the rhythm on an ongoing basis, or [coaching](/insights/executive-coaching-vs-operating-advisory/), which develops you as a person rather than rebuilding the structure of the business. If you want to understand what a deeper structural engagement looks like, the [Operating Audit](/operating-audit) is the paid next step. If you are not sure where your operating rhythm is breaking down, the free Founder Dependency Diagnostic maps where your week actually goes and shows what still runs on you. [Take the free diagnostic](/executive-diagnostic) ## Common questions How often should a small business operating cadence meet? Weekly is the right default for a business of 8 to 50 people. Monthly is too slow to catch blockages early. Daily standups add overhead without adding signal unless the team is actively fighting a specific crisis. One weekly metrics review and one weekly leads check-in cover most of what a founder-led business needs. What numbers should I track in my weekly metrics review? Pick four to six numbers that tell you whether the business is moving or stuck. For most B2B businesses that means something in the pipeline (new qualified opportunities this week), something in delivery (work completed or at risk), something in cash (runway or collections), and one leading indicator specific to your model, such as proposals sent or demos booked. The exact numbers matter less than tracking the same ones every week so you can see a trend. What is the difference between an operating rhythm and a founder operating system? An operating rhythm is one component of a wider operating system. The operating system covers Direction (the single outcome the team is organised around), Decisions (who has the right to decide what), and Delivery (the cadence that moves work). The rhythm is the Delivery piece: the standing meetings, metrics review, and escalation rules. It does not do the job of the other two on its own. My team already has weekly meetings. Why is nothing changing? Meetings without a defined purpose, a fixed format, and a clear rule about what resolves inside the meeting versus outside it tend to become status reports. Status reports tell you what happened. A working cadence surfaces what is stuck and resolves it. Check whether your current meetings have an explicit escalation threshold. If people still bring you everything in the meeting, the threshold has not been set yet. How long does it take to build a working operating cadence? The structure itself can be designed and launched in a week. Getting the team to trust it and resolve things below you typically takes four to eight weeks of consistent repetition. The most common failure point is the founder breaking their own escalation rule in week two because it feels faster to just answer the question. That one decision resets the clock. Should I hire a COO to run the operating rhythm for me? Hiring a senior operator into a business with no operating structure relocates the dependency onto them at a senior cost. If they leave, the work routes straight back to you. The honest question is whether you have a structure gap or a staffing gap. If the cadence, decision rights, and direction do not yet exist in the business, build the structure first. Then decide what you still need to hire. Related: [what is a founder operating system](/insights/what-is-a-founder-operating-system/) · [why does my business stall when i step away](/insights/why-does-my-business-stall-when-i-step-away/) · [how to get my business to run without me](/insights/how-to-get-my-business-to-run-without-me/) · [how to set decision rights in your business](/insights/how-to-set-decision-rights-in-your-business/) · [signs your business is too dependent on you](/insights/signs-your-business-is-too-dependent-on-you/) · [operating advisor vs fractional coo vs hiring a coo](/insights/operating-advisor-vs-fractional-coo-vs-hiring-a-coo/) · [more insights](/insights).