
Operating Cadence
Part of Startup meeting and reporting routines
Designing a weekly operating review
A weekly operating review should identify the few changes that need a decision.
undefined
Design the weekly operating review around a shared pre-read, an ordered discussion and a clear close. Share routine progress beforehand so the meeting can focus on unresolved actions and exceptions that need attention or a decision.
Book the review as a 30-minute weekly meeting and circulate the one-page report at least a few hours before it starts, so questions arrive while owners can still gather evidence (hellodeck.ai). Hold team-level reviews on the Monday so the leadership review can run Tuesday morning with everyone prepared (fishmanafnewsletter.com).
Design the weekly pre-read around exceptions
Start the page with the meeting date, purpose, goals, key attendees and process. Keep open action items visible so the team can check progress before discussing new issues.
Lay the pre-read out as a one-page scorecard: metric, this week, target, previous week, status and owner (hellodeck.ai). List only the items outside the expected range as exceptions, and mark each as needing a decision, an owner or continued watching (hellodeck.ai).
For each current priority, show the intended outcome, latest measure or milestone, change since last week, owner and concise risk. Include the date and source of figures, and label any estimated metric.
Five to nine metrics is enough for most small teams, spanning revenue, customers, delivery, cash, people and the few initiatives that matter now (hellodeck.ai). Every metric needs a definition and an owner (hellodeck.ai).
For an exception that needs a decision, state the decision required, the options and a recommendation. A red status on its own does not tell the group what it needs to decide.
Circulate every figure before the meeting so the room never sees a number for the first time, because discussing pre-read data spends the same time and produces decision-makers (fabricloop.com). Full financial analysis belongs in the monthly report rather than the weekly review (hellodeck.ai).
Use Atlassian’s Weekly Team Updates to share routine progress asynchronously, using a written message or video. The play points to Week Ahead and Weekly Wrap templates and lists 15 minutes of prep and a one-minute run for the update.
Routine Updates vs. Exception-Based Discussion
- Routine ProgressShared asynchronously via pre-read (e.g., Atlassian’s Weekly Team Updates template)
- Exception FocusOnly items outside expected range discussed in live meeting; require decision, ownership, or monitoring
Run the weekly review and leave with a record
Run the meeting in 30 minutes: five minutes on the headline and material data corrections, 10 minutes on red and yellow scorecard items, 10 minutes to decide the two or three open issues, and five minutes to read back owners, deadlines and the wider message (hellodeck.ai). Put detailed project status in the project system and bring it in only when an exception needs context (hellodeck.ai).
Open by stating the purpose, goals and process, then review unresolved actions from the prior week. Discuss the highest-impact exception first, using the page rather than narrating routine numbers that participants can already read.
Define clear roles: a meeting owner and a rotating note-taker who records decisions (experimental.beehiiv.com). Without clear roles, the review becomes a free-for-all with everyone putting their own spin on what happened (experimental.beehiiv.com).
Work through the remaining exceptions in priority order. If an item is informational, assign someone to write an update; if it needs an absent specialist, agree who will obtain their input and by when.
The source identifies cadence mismatch when strategic questions invade weekly tactical meetings while urgent operational issues wait for quarterly offsites (bizgrowthaxel.com).
At the close, record each decision’s choice, reason, owner and effective date. For a blocked item, note the missing evidence and when the team will return to it.
Review the review itself every quarter in a 30-minute session, and cut any metric that no longer drives a decision; one team cut 60% of the metrics it tracked this way (experimental.beehiiv.com). Long reviews usually spend their time sharing updates instead of deciding, which is the failure mode to watch for (experimental.beehiiv.com).
In Atlassian’s Weekly meeting notes template, use /decision to record decisions and /action item to assign tasks. Its /task report macro displays unchecked actions across meetings; check off completed items so open actions remain clear for the next review.
The answer to meeting overload is not eliminating cadence but designing it deliberately (bizgrowthaxel.com). Keep a one-page cadence calendar that specifies when each planning layer is reviewed, who takes part and what decisions are made (tryhamster.com).



