How to run a weekly operating cadence.
A practical weekly operating review for service businesses: commitments, blockers, exceptions, decisions and follow-up in thirty minutes.
A cadence that works
A narrated companion to this article, created with the photographs and visual language of Emerson North.
Read video transcript
An operating dashboard cannot run a meeting for you. A useful weekly cadence asks four questions: What did we promise? What is blocked? Who owns the next decision? When will the client hear from us? Spend less time narrating every task and more time resolving the exceptions. Before the meeting ends, record the decision, the owner, and the date. The value is not in another chart. It is in a rhythm the team can keep. Emerson North. Ideas worth putting to work.
A weekly operating cadence is a small set of questions a team answers on a reliable schedule. It keeps promises, blockers and decisions in view without turning every meeting into a tour of the dashboard.
Review commitments due soon, work that lacks an owner, decisions waiting for approval and recurring exceptions. End each discussion with a named action and date, then write the decision into the shared record.
What an operating cadence is for
Most teams already have meetings. The missing piece is often a consistent way to move work through them. A useful cadence brings exceptions to the people who can decide, makes the next action visible and checks whether last week's decisions were carried out.
It is not a substitute for daily coordination. Dispatchers still dispatch, clinicians still schedule and account managers still speak with clients. The weekly review looks across those streams to find work that is stuck between them.
Start with a single owner for the meeting and one shared record. The owner prepares only the exceptions, not a slide deck of everything the company did. Participants arrive ready to decide or supply a missing fact.
A practical 30-minute agenda
Five minutes: promises. Which commitments to clients or partners are due in the next two weeks? Identify any whose owner or date is unclear. Ten minutes: blockers. Which work cannot move because a decision, person or resource is missing? Ten minutes: exceptions. Which issue repeats often enough to suggest a process problem? Five minutes: close. Read back decisions, owners and dates.
The meeting should not solve every technical detail live. If a decision requires research, assign the research and the date for a decision. The record should say that the issue remains open, rather than burying it in an informal follow-up.
Each week begins with the previous week's open commitments.
Write decisions where the work lives
Meeting notes can become another isolated document. Record each outcome with the job, client or project it affects. Include what changed, who decided, who acts next and when the client will hear. A person who missed the meeting should be able to open the work record and understand the next step.
For example, “discussed staffing” is not a decision. “Operations lead will confirm weekend coverage by Wednesday; account manager updates the client on Thursday” is. It converts conversation into a responsibility the team can follow.
Keep a short decision log for issues that cut across many jobs: a pricing rule, an approval threshold or a change in service policy. Link the rule back to the work that prompted it. That history helps new managers understand why the company chose the rule.
Choose measures that lead to action
Start with a few signals: client commitments completed on time, work awaiting a decision, reopened jobs caused by missing information and accounts with no clear next step. A measure belongs in the meeting only if a participant can act when it changes.
Do not let the chart become the goal. A decline in reported exceptions can mean that work improved, or that people stopped reporting them. Ask for a small sample of actual jobs to interpret the number. Compare the record with client feedback and staff experience.
When a signal repeatedly shows the same failure, change the handoff that produces it. When it is stable and no longer helps decisions, retire it. A good cadence is short because it is selective.
How to launch the cadence without adding bureaucracy
- Pick a recurring time that frontline leads can reliably attend.
- Agree on four questions and one place to record decisions.
- Run the meeting for four weeks before adding new metrics.
- Ask which agenda item produced a useful decision and which could be handled elsewhere.
- Keep the meeting only if the work moves more clearly afterward.
Software can surface the right commitments and history, but the team must use that visibility to make choices. Emerson North builds the operating rhythm and Emerson platform together because each makes the other more useful.
Published by Emerson North, an Atlanta operating company that runs, builds and owns businesses. Examples, workflow diagrams and editorial images are illustrative and do not describe client results.