The Executive Operating Review Template That Actually Drives Decisions (Not Just Recaps)

It's Sunday night, and I'm rebuilding the same deck I rebuilt last Sunday. Five browser tabs open across two monitors — the BI dashboard, the CRM, last week's deck, the shared doc where three people promised to drop their numbers and two of them didn't, and a Slack window where I'm asking the third where those numbers are. I paste a revenue figure into slide four. I reformat a chart on slide six because the source changed its column order again. By the time the deck looks like something the leadership team can walk into Monday morning, it's late, and I've built eight slides that all answer the same question: what happened last week.

Here's the part that took me embarrassingly long to notice. Every Monday we'd open that deck, walk through the eight "what happened" slides, and run out of time right around the moment we reached the slide that mattered — the one that asked what we were actually deciding this week. The decisions slide was always last, so it was always the casualty. I used to think the problem was discipline: we needed to talk faster, cut the small talk, get through the recap quicker. It wasn't discipline. It was the template. I had built a structure whose first eight slides were a museum tour of the past, and then acted surprised when the meeting behaved like a museum tour. You cannot out-discipline a template that has no room for the future in it.

The short answer

An executive operating review template is the recurring structure a leadership team uses to run its operating cadence — and a good one is built around decisions, not recaps. The four sections that matter: (1) the metrics that moved and why, (2) the decisions due this week, (3) the risks that changed since last time, and (4) the follow-ups still open from the last review. A template that only organizes "what happened" guarantees a backward-looking meeting; the sections that make a review useful are the ones about what happens next.

Why Your "Template" Is Really a Recap

Go look at whatever you currently call your operating review template. I'd bet most of it is reporting. A revenue slide. A pipeline slide. A product-velocity slide. A customer-health slide. Each one is a snapshot of a number as it stood at some point in the recent past. Useful information — but it's all the same shape: here is a thing that already happened, rendered as a chart.

The trouble with a recap-shaped template is that it quietly decides what the meeting is about before anyone walks in the room. If the structure in front of you is eight slides of past-tense reporting and one slide of "open items" at the end, the meeting will be eight parts looking backward and one part looking forward — and that's on a good day, when you reach the last slide at all. The template isn't a neutral container. It's a script, and people perform the structure you hand them. Everyone nods at the numbers, agrees they've seen the numbers, and leaves feeling informed — while the two or three things that are genuinely undecided or genuinely at risk never make it onto the table. The numbers are the setup. The decisions are the point.

There's a cost to getting this wrong that shows up in the strategy itself: 67% of well-formulated strategies fail due to poor execution, according to Harvard Business Review. Not because the strategy was wrong — because the operating cadence underneath it kept relabeling "we reported the numbers" as "we executed." A review built around recaps is one of the most common places that substitution hides. It feels like operating. It's mostly narrating.

The Four Sections That Actually Make a Review Useful

When I rebuilt our template, I inverted it. The recap didn't disappear — it got demoted. Here are the four sections, in priority order, which is to say in the order they should claim time in the room.

Decisions due this week. This goes first, not last. Before anyone presents a single chart, the room should see the list of decisions that need to be made in this meeting — the pricing call, the headcount trade-off, the go/no-go on the launch date. Putting it first does something structural: it tells everyone what the metrics are in service of. You're not reviewing pipeline for its own sake; you're reviewing it because there's a decision about sales capacity riding on it. Decisions-first reframes every number that follows as evidence rather than entertainment.

Risks that changed since last time. Not a static risk register — nobody reads those. What moved? Which risk got worse, which one resolved, which new one showed up that wasn't on anyone's radar last week. The delta is the signal. A risk that's been yellow for six weeks is background noise; a risk that went from green to red since Monday is the most important thing in the meeting, and your template should give it a place to be loud. We built Radar for exactly this reading problem — surfacing the initiative that slipped on day three, not the version of the news that reaches leadership on day thirty, so the risk that moved is the one the review actually opens on.

Open follow-ups from the last review. This is the section almost every template skips, and skipping it is why reviews feel like Groundhog Day. If the decisions and action items from last week don't show up at the top of this week's review with an owner and a status, they didn't really happen — they were theater. Carrying them forward, visibly, is the single highest-leverage change you can make to an operating cadence. It's the difference between a meeting that compounds and a meeting that resets to zero every week.

The metrics recap — kept short. The numbers still matter. But they go last, and they go fast. The recap's job is to ground the first three sections in reality, not to consume the hour. If a metric isn't attached to a decision due or a risk that moved, it doesn't need airtime; it can live in the pre-read. The discipline is brutal and worth it: a chart earns a spoken minute only if a human in the room has to do something about it.

That's the whole template, and it fits on one page or five slides — never more. Decisions due, each with an owner and a date. Risks that changed, each with the direction it moved and who owns the response. Open follow-ups, each with owner and status. Then the short recap: the three to five numbers that actually inform the decisions and risks above, each with a one-line "why it moved." Anything that doesn't connect to a decision or a risk goes in the pre-read, not the room. Companies that take execution seriously are roughly three times more likely to report above-average growth, according to research from PwC's Strategy& — and the mechanism is almost boringly concrete: whether the meeting where the leadership team operates is built to decide things, or just to describe them.

Get the Cadence Right: Weekly, Monthly, and Quarterly Aren't the Same Meeting

Here's a mistake I made for a long time: running the weekly, the monthly, and the quarterly at the same altitude. Same template, same level of detail, same kind of conversation — just at different intervals. It's why the weekly review kept collapsing into a status recap. If your weekly meeting tries to cover everything the monthly covers, it has no choice but to become a shallow tour of every number, because there's too much surface area and not enough time to go deep on anything.

The fix is to treat cadence as part of the template, not separate from it. The weekly operating review is the forward-looking, decision-and-risk meeting — short, sharp, about what we do in the next seven days. The monthly business review is a different altitude: performance against the plan, trends rather than this-week movement, the questions that need a month of data to even ask. The quarterly is higher still — the board-level look at whether the strategy itself is working. Different cadence, different altitude, different template. Collapse them and the weekly inherits the monthly's breadth without the monthly's time budget, and you're back to recaps.

Running each cadence at its own altitude is exactly what Rhythms' Playbooks is built to handle — the weekly operating review, the monthly business review, and the quarterly each run as their own recurring play, pulling the right depth of data for that altitude instead of forcing one template to do three jobs. The point isn't more meetings. It's that each meeting finally knows what it's for.

The Template Fixes the Structure. It Doesn't Fix the Prep.

I want to be honest about the limits of what a template can do, because this is where most "just use this template" advice quietly fails. A good template fixes the shape of the review. It does not fix the prep. You can reorder your slides so decisions come first and the recap comes last — and you'll still have someone (often the Chief of Staff, often on a Sunday) pulling those numbers by hand from five tabs, chasing the two people who didn't send their updates, and reformatting the chart whose source changed again.

And here's the trap: as long as prep is manual, the review stays backward-looking no matter how good the template is. All the human energy gets spent assembling what happened, so there's nothing left for what happens next. You can have the most decision-first template in the world and still walk into the room exhausted, having spent your whole Sunday in the past tense.

This is the part I'd been treating as just the cost of the job — and it's exactly what we built Rhythms' Reviews to remove. The data-gathering step, the manual pull from CRM and BI and Slack and last week's deck, the chasing — that's the work that should never have been a human's job. When the review assembles itself from the connected systems, source-grounded, the recap is already done, so the hour can go to the decisions. And the open follow-ups I said almost every template skips arrive already attached to the next review — last week's decisions, their owners, their status, at the top of this week's agenda without anyone reconstructing them from memory. That's what makes the next review start smarter than the last one. The team that built Ally.io and led Microsoft Viva Goals ended up focused on reviews for exactly this reason: goals don't die during planning, they die in the gaps between reviews, and the gaps are where manual prep quietly drops the thread.

We estimate up to 70% of management time gets consumed by "work about work" — the status-gathering, the deck-building, the re-communicating (a directional figure from working with operating teams, not a precise one). Review prep is the most visible instance of it. A template can't touch that number. Automating the prep can.

What I'd Tell Myself, Eight Slides Deep on a Sunday

I still care a lot about how an operating review is structured. I just don't spend my Sundays assembling one anymore, and the template I use now would be almost unrecognizable to the version of me pasting revenue figures into slide four at 10pm. The slides flipped. The recap that used to be the whole deck is now the last thing we look at, fast, if we say it out loud at all. The decisions that used to be the slide we never reached are the first thing on the page.

If your review still opens with what happened and ends, if you're lucky, with what you're deciding, you don't have a discipline problem. You have a template problem, and underneath it, probably a prep problem. Fix the order first — it costs nothing and you can do it before your next meeting. Then ask the harder question: who's spending their Sunday assembling the past so the room can spend Monday discussing it. Because the first time a review shows up already built — decisions on top, last week's follow-ups already carried forward, the recap quietly handled — you stop wondering how to run the meeting better and start wondering why you ever thought building the deck was your job.

If you're still the human API assembling the deck every week, try Rhythms for free at rhythms.ai.

Frequently Asked Questions

What should an executive operating review template include?

Four sections: the metrics that moved (with the "why," not just the number), the decisions due this week, the risks that changed since the last review, and the open follow-ups carried forward from last time. The recap of what happened should be the shortest part, not the whole deck. If your template is mostly past-tense reporting with an "open items" slide tacked on the end, it will produce a backward-looking meeting no matter how disciplined the room is.

How often should you run an executive operating review?

Weekly or biweekly for the operating review itself, layered under a monthly business review and a quarterly board review. The mistake most teams make is running all three at the same altitude — same template, same depth — so the weekly degrades into a status recap instead of a decision forum. Keep the weekly short and forward-looking, let the monthly handle performance against the plan, and reserve the quarterly for whether the strategy itself is working.

What's the difference between an operating review and a business review?

The operating review is the higher-frequency, forward-looking meeting about the decisions and risks facing the team this week or this month. The business review is the lower-frequency, broader look at performance against the plan over a longer window. Different cadence, different altitude, different template. Trying to run them as the same meeting is why so many weekly reviews feel like a shallow tour of every metric.

Why does review prep take so long, and how do I cut it?

Because the data lives in a dozen systems — CRM, BI, project tools, Slack, last week's deck — and someone assembles it by hand every cycle. The fix isn't a longer meeting or a tighter template; it's automating the data-gathering so the prep produces itself and the human time goes to the decisions instead. If you're spending more than a few minutes of human effort per cycle, the prep is in the wrong place: the time a leadership team spends on a review should go almost entirely to judgment, not to pulling numbers and reformatting charts.