What is an Executive Operating Review & How to run it?

The Review That Wasn't

For months, I was convinced we were running an executive operating review. Every Monday morning, the leadership team was in the room, coffee in hand, half of them still reading the pre-read I'd sent at 11pm Sunday. There was a deck. Each function had a slot. The CFO would correct someone's pipeline number in the first ten minutes, we'd nod through the acknowledgment of three or four risks, assign the action items, and leave.

Then came the third consecutive Monday where the same pipeline risk appeared on the agenda. Same language. Same slide position. We acknowledged it, assigned it to someone who had already been assigned it the week before, and moved on. When I went to build the following week's deck, I realized I had no record anywhere of what we'd actually decided. The action items lived in my notes. The risk was going to appear again next Monday as though we were seeing it fresh.

Nothing had moved. Not because the team didn't care — they did. Because there was no mechanism to close the loop. I was the mechanism. I was the one who remembered what was said last week, who pulled the right numbers from the right systems before anyone else arrived, who held the institutional memory of our operating cadence in a folder on my desktop and in my own head.

What we were running was a status update with executive attendance. Not a review. The difference sounds semantic. It isn't.

The Short Answer

An executive operating review is a recurring leadership meeting — weekly or monthly — structured to inspect what's actually happening in the business, surface what's at risk, make decisions, and track follow-through. Unlike a status update (where each function reports out) or a strategy review (where long-term priorities are debated), an executive operating review is operational: it covers what changed since the last review, what's off-track, what decisions are waiting, and what happens next. The most effective versions are grounded in live data from the tools where work happens — not in a manually assembled deck — and they carry decisions forward into the next review automatically.

What an Executive Operating Review Actually Is

That definition is narrower than most teams use, and the narrowness is the point.

An executive operating review is not a planning offsite — the conversation about next year's priorities belongs somewhere else. It's not an all-hands update on company direction. It's not a deep-dive into any one function's roadmap. It is an operational ritual: inspect, decide, follow through, carry forward. Those four elements, in that order, every time.

Three things separate a real EOR from everything else that calls itself one. First, it runs on live data — not on a deck that was accurate as of Thursday. Second, it produces decisions with named owners and timelines, not acknowledgments and intentions. Third, it carries those decisions into the next review automatically, so the meeting has institutional memory that doesn't depend on any single person in the room.

Most leadership teams are running two of the three. Almost nobody is running all three consistently. That's where execution slips — not from lack of effort but from lack of infrastructure.

What Most Companies Are Running Instead

A 2024 McKinsey survey found that only 44% of executives say their company's leadership meetings regularly produce clear decisions. That means more than half of all executive time spent in leadership meetings produces something other than decisions. Which means it produces theater.

The theater looks familiar. Each function presents an update. The CEO asks a few questions. Risks are flagged and acknowledged. Action items are assigned — usually to whoever is closest to the problem, sometimes to whoever talked most. The meeting ends. The deck is filed. Next week, someone builds a new one from scratch, the same risks appear, and the action items from last week aren't on the agenda because they were never put anywhere that would surface them.

This is the status-update trap. The meeting is structured around reporting — each function gets a turn — instead of around decisions that need the room's collective judgment. It looks like oversight. It performs alignment. But it doesn't compound, because it has no memory.

The failure isn't discipline. Reminding people to "come better prepared" or "be more decision-focused" doesn't fix this. The meeting's structure determines what the meeting produces. A structure optimized for reporting will produce reports. If you want decisions, the structure has to be built for decisions. That's an infrastructure problem.

The Three Infrastructure Problems That Break Most EORs

When I trace the operating review failures I've seen — and the ones our customers describe before they start running them in Rhythms — they almost always lead back to the same three places.

The data isn't current when the meeting starts.

The pre-read was assembled by a person from a collection of exports, spreadsheets, and Slack messages that were accurate as of some earlier point in the week. By Monday morning, something has changed. The pipeline number is different. The customer escalation has new information. The product team sent an update Friday night. None of that is in the deck. The first fifteen minutes of the review are spent resolving which number to believe — which means the first fifteen minutes are wasted before the first decision.

This is the structural gap Reviews in Rhythms was built to close. The pre-read generates from live Salesforce, Jira, Slack, and HubSpot data — not from someone's Sunday evening. The agenda reflects what actually changed, not what the deck-builder had time to find.

Decisions made in the review disappear after the meeting.

Someone owns the action. Someone else has a note. The Chief of Staff has a mental model. None of these overlap perfectly, and none of them are surfaced automatically in next week's review. The decision was made. It just wasn't captured anywhere the operating cadence could find it.

This is why the same risks appear in three consecutive meetings. Not because nobody is working on them — often someone is — but because the review has no memory. It restarts from scratch every Monday. Every piece of institutional knowledge about what was tried, assigned, or resolved lives in people's heads instead of in the system.

There is no thread connecting one review to the next.

A real operating review answers "what did we decide last week and what happened?" before it covers anything new. That question is where accountability lives. If you can't answer it in two minutes, you don't have a review — you have a weekly reset.

Reviews that compound work differently. Last week's decisions aren't historical record — they're active questions. Did this happen? If not, why? What does the team need to move it forward? The meeting gets smarter over time because it's building on itself. That's the difference between a cadence and a loop.

What Changes When the Review Runs on Live Data

The night before the old Monday review, I was building. Pulling exports, checking Slack for updates, chasing numbers, reconciling the version of the pipeline that the CRO had sent with the version that was in the system. By the time I sent the deck at 11pm, I had spent four hours doing work that a data pipeline could do better.

The night before a review that runs on live data, I'm reading. The pre-read is there when I sit down. My job is to look at it — to find the story in what changed, to notice the risk that the data doesn't name but that I recognize from a conversation earlier in the week, to flag the question the exec team is going to ask before they ask it. That's an hour of editing. It's a different job. It's a better use of the thing I'm actually there to provide.

Up to 70% of management time gets consumed by work about work — coordination overhead, status-chasing, context-assembly that surrounds the actual decisions. Review prep is where that tax is most concentrated and most visible. When you remove the manual assembly step, you don't just get the hours back. You change what happens in the hours that remain.

The meeting changes too. When the pre-read is grounded in live systems, the first fifteen minutes stop being a negotiation about which numbers are correct. The room starts on the actual work — the decision calls, the risk discussions, the cross-functional judgment the team is assembled to provide. That's a different meeting.

The Three Review Packages Worth Knowing

The operating review loop — prepare, inspect, decide, follow through, carry forward — applies to every recurring leadership ritual, not just the executive weekly. The data, the attendees, and the specific questions differ by team. The underlying discipline doesn't.

Rhythms ships three starter packages, each built for a specific leadership context.

The Executive Operating Review is the weekly or monthly leadership cadence. Pre-read generated from cross-functional sources, agenda grounded in what changed, decisions captured, follow-ups surfaced in the next review. Who it's for: CEO, COO, Chief of Staff.

The Customer Health Review is for CS and RevOps teams running a recurring inspection of renewal risk, expansion opportunities, and customer escalations. Connected to CRM, CS platform, and product analytics — the review runs off live customer data, not off a spreadsheet someone updated yesterday.

The Pipeline Review is for sales and revenue leadership — forecast, deal risk, pipeline movement, and next actions, pulled automatically from the tools where deals actually live. The CRO and RevOps leaders who run this review stop building the pre-read and start running the inspection.

Same underlying operating ritual. Three configurations for the three places leadership teams spend the most review time — and where the infrastructure gap is most costly.

For years, I believed the value I brought to Monday's meeting was the deck.

I got good at building it. I knew which data sources were reliable by Friday afternoon and which I'd have to chase Sunday morning. I developed a system for reconciling the four versions of the pipeline number that inevitably existed by end of week. I could turn eight disconnected inputs into a coherent forty-slide narrative in about four hours, and by the time I walked into that room, I knew it better than anyone.

What I didn't see — for a long time — was that I was running a preparation service for a meeting that had the shape of a review but none of the infrastructure.

The deck had no memory. The decisions left the room in people's heads. The risks appeared next week as if they'd never been raised. My value wasn't to the review. It was to the ceremony around the review. I was the elaborate workaround for a structural problem nobody had named.

When the infrastructure closed — when the pre-read built itself from live data, when decisions got captured and surfaced automatically in the next meeting — the Monday ritual became something it hadn't been before: a review. Not the performance of one. An actual one.

That shift is available to every leadership team running the version of the meeting I used to run. It's not a discipline change. It's not a better agenda template. It's infrastructure.

If you're still the human API for your organization, try Rhythms for free at rhythms.ai.

Frequently Asked Questions About Executive Operating Reviews

What is an executive operating review and how is it different from a status meeting?

A status meeting is structured around reporting — each team or function gives an update on what they've been working on. An executive operating review is structured around decisions: what changed, what's at risk, what decisions are waiting, and what was decided last time and whether it happened. The distinction matters because a status meeting produces information; an operating review produces accountability. Most leadership teams are running status meetings in the format of operating reviews, which is why the same risks keep appearing week after week without ever being resolved.

What should an executive operating review agenda include?

Every executive operating review agenda should answer five questions in order: What changed since the last review, grounded in live data? What is at risk right now? What was decided last time and did it happen? What decisions are waiting for this room's input? What will we decide today, and who owns it with what timeline? The pre-read should make the first two questions answerable before anyone walks in. The 60-minute meeting should be spent almost entirely on questions three through five — which is where the value of having the room together actually lives.

How do you prepare for an executive operating review without spending hours on a deck?

Stop building the deck by hand. Preparation for an effective operating review is a data-retrieval problem — pulling the right metrics from the right systems and organizing them into a coherent pre-read. That's work a connected system should do. When the pre-read generates automatically from live tools, the Chief of Staff's job shifts from assembly to editing: reading the output, identifying the story in the data, flagging what the system can't see. That's twenty minutes of judgment work, not four hours of retrieval work. The retrieval is the part you can give back. The interpretation is the part that's actually yours.

How often should a company run an executive operating review?

Weekly is the right cadence for most mid-to-large SaaS leadership teams — and the reason is compounding. A review that runs weekly builds institutional memory: decisions made last Monday surface this Monday, risks flagged two weeks ago either resolved or escalated. Monthly is too slow; a month is enough time for a slipping initiative to become a crisis you're managing instead of preventing. Quarterly is planning, not operations. The weekly cadence is what gives the review its power — not the meeting itself, but the thread connecting each meeting to the one before it.