What Is an Executive Operating Review — And Is Yours Actually One?

An executive operating review is a recurring leadership meeting that connects strategic priorities to current operational reality. Unlike a quarterly business review or a status update, an EOR is built around live data from every function — not self-reported slide decks — and it exists to produce decisions and follow-through, not just alignment. The test is simple: after your leadership meeting, can you trace every major decision to a specific piece of data, and is someone accountable for every open item before the next session begins?

I ask that question because I spent years running a meeting I was certain qualified — and it didn't. It had the name, the calendar hold, the right people. It just wasn't a review.

Here is what it actually looked like. Tuesday, 9 a.m., the weekly leadership review. By the time everyone sat down, I had already spent most of Sunday assembling the pre-read — revenue from the CRM, delivery status from Jira, a customer escalation summary one of the CS leads had Slacked me Friday at 4 p.m., a finance tab someone updated by hand. The deck was accurate, more or less, as of about 48 hours earlier. Then the CEO would ask a question the deck didn't answer — "are we actually going to hit the enterprise number, or is that one deal carrying the quarter?" — and the room would go quiet, and someone would say they'd look into it and circle back. They rarely did. The next Tuesday, we started over.

I ran that meeting something like forty-seven times before I let myself admit the obvious. It was a report-and-nod session wearing a review's clothing. And the part that took me too long to see was this: the meeting wasn't the broken thing. The infrastructure around it was. No amount of better facilitation, tighter agendas, or sharper slides would have fixed it, because the problem lived upstream of the room.

The Meeting That Looks Like a Review (But Isn't)

Most leadership teams believe they run an executive operating review. Almost none of them do. What they run is a status update with better production values.

The tell is in what the meeting produces. A real review produces decisions, owners, and follow-through. A status meeting produces information transfer and a vague sense of alignment that evaporates by Thursday. If you sat in the back of most "weekly leadership reviews" and wrote down every decision made, then checked a week later whether anything happened, you'd find the honest answer is usually: not much. People left informed. They didn't leave committed.

This is not a discipline problem, and it's not a people problem. The leaders in that room are sharp and busy and well-intentioned. The problem is structural — which is the whole point I'd missed for forty-seven Tuesdays. A meeting can only be as good as the inputs it runs on and the mechanism that carries its output forward, and in most companies both of those are held together by one overworked human doing it manually. I used to joke that my title should have been Status Update Aggregator. It stopped being funny around review number thirty.

There's a reason this matters beyond any single Tuesday. Research going back to Kaplan and Norton's work in Harvard Business Review has consistently found that the majority of organizations fail to execute the strategy they set — more recent surveys put the figure at roughly two-thirds. That gap doesn't open during the annual planning offsite. It opens in the fifty-some weekly meetings between offsites. Every week the operating cadence fails to convert reality into a decision, the distance between the plan and the work grows another inch.

What an Executive Operating Review Actually Is

An executive operating review is defined by what it produces, not by its name, its frequency, or its attendee list. Strip away the calendar invite and the slide template, and an EOR is the place where strategic priorities meet current operational reality and a decision comes out the other side.

Three things distinguish it from the meeting most teams actually run.

First, it runs on live data from every function — pipeline from the CRM, delivery from project tracking, customer health from CS and support tools, financial actuals from finance systems — and that data is system-generated, not self-reported. The distinction is load-bearing. A pre-read built from Slack messages and a manually updated spreadsheet isn't grounded in reality; it's grounded in whoever compiled it, filtered through what they had time to chase down. Self-reported data is, by its nature, a negotiation. Live data is just true.

Second, it is built to decide, not to inform. Every agenda item exists because it requires a judgment call from the people in the room. If an item is purely informational — here's what happened, no decision needed — it belongs in an async update, not in the most expensive hour on the executive calendar. An EOR that spends forty minutes on things everyone could have read in advance is just an expensive newsletter.

Third, it has memory — and this is the one that actually separates an operating review from every other meeting on the calendar. A real review inherits the context of the last one: the decisions made, who owned them, what was supposed to happen by now, what's still open. The meeting doesn't start from zero. It starts from "here's where we left it, and here's what moved." Memory is what turns a series of disconnected weekly meetings into a single, compounding operating cadence — where each session is accountable to the last and the team stops relitigating decisions it already made. Most leadership meetings have no memory at all, which is why they feel like Groundhog Day with new slides.

When I describe a review that arrives already prepared — pre-read generated from live sources, the right risks surfaced, prior decisions carried forward — I'm describing what we built Rhythms' Reviews to do. Not because the deck is prettier, but because the conversation is different when nobody in the room is quietly wondering whether the numbers are current.

The Pre-Read Is Where It Lives or Dies

If you want to know whether a team's operating review is real, don't watch the meeting. Look at how the pre-read gets made.

This is the part nobody talks about, because it happens in the dark — usually on a Sunday, usually performed by one person stitching together six or eight or twelve sources into something coherent. And here's the structural trap: a pre-read built by manual collection is incapable of producing a real review, no matter how good the meeting itself is. The data is stale by the time it's compiled. It's incomplete, because the person building it can only chase what they know to chase. And it's shaped — consciously or not — by the assembler's sense of what matters and what's worth a hard conversation.

The cost of this is larger than it looks. Up to 70% of management time gets consumed by what researchers call "work about work" — the status-gathering, deck-building, update-chasing layer that sits between strategy and execution. Review prep is where that tax is most concentrated and most visible. I wasn't analyzing the business on those Sundays. I was performing data entry with a deadline.

The shift that mattered for me wasn't a better template. It was moving the pre-read from something a person assembles to something the system generates. When the agenda is grounded in live data pulled automatically from the tools where work already happens, the Chief of Staff stops being the data collector and becomes what they were actually hired to be — the person who reads the data and frames the decision. That's the role Playbooks was built to take over: the recurring prep ritual runs as a background process, not as someone's lost weekend.

I'll be honest about the limits here, because the reader has heard every AI promise and discounted most of them. Gartner found that only 11 to 14% of enterprise AI agent pilots reach production at scale. The ones that survive aren't the ones promising to make autonomous decisions — those fail the trust test on contact. The ones that survive do the unglamorous, verifiable work: pulling the right data, assembling the pre-read, surfacing the risk. Preparation is exactly the kind of work AI can be trusted with, because a human still reads the output and makes the call.

The Gap Between Reviews Is Where Strategy Goes to Die

The failure mode of most leadership meetings isn't the meeting. It's the six days and twenty-three hours between meetings.

Think about what happens to a decision made in a Tuesday review. Someone agrees to own it. The meeting ends. And then that decision has to survive a week of competing priorities, fading memory, and the absence of any system tracking whether it actually moved. By the next Tuesday, half the open items from last week are unresolved, nobody quite remembers who owned what, and the team relitigates decisions it already made. The review starts fresh every week because it has no choice — there's no connective tissue holding one session to the next.

This is the quiet reason strategy erodes. Not because leadership stopped caring about it, but because the operating cadence has no memory and no early-warning system. An initiative slips on day three, but nobody surfaces it until it's a day-thirty problem in next month's review — by which point it's no longer a course-correction, it's a postmortem. The Chief of Staff is almost always the last to know, because they only see what makes it into the pre-read.

We built Radar for exactly this gap — to scan the connected tools continuously and flag the off-track initiative on day three, so it lands in the room while it's still a decision and not yet a disaster. An operating review with memory and an early-warning layer is a fundamentally different instrument than a weekly meeting that resets to zero. One compounds. The other just recurs.

What Changes When the Infrastructure Works

The change isn't that the meeting gets shorter, though it does. The change is what the meeting becomes capable of.

When the pre-read generates itself from live data, when risks surface before the meeting instead of during it, and when last week's decisions and owners are sitting right there in this week's session, the hour stops being about catching up and starts being about deciding. The CEO asks the hard question, and the answer is on the screen, current as of this morning, because nobody had to chase it. Open items don't evaporate, because the system is carrying them forward whether or not anyone remembers to. The Chief of Staff walks in having spent zero Sundays building anything — and walks out as the person who shaped the decisions, not the person who compiled the inputs.

That's the real shift, and it's less about software than about what the role was supposed to be all along. The people who run executive operating reviews were never hired to be the human API between twelve disconnected tools. They were hired to make the leadership team effective. The infrastructure either lets them do that job or quietly conscripts them into a different one.

I still have strong opinions about how a leadership review should run — what belongs on the agenda, how decisions should be captured, why most pre-reads are twice as long as they should be. I just don't spend my Sundays assembling them anymore. And the question I asked at the top of this piece — can you trace every decision to data, and is someone accountable for every open item before next week — is one I can finally answer yes to. Not because I got more disciplined, and not because we found a better meeting format. Because the meeting was never the broken part. We finally fixed the infrastructure underneath it.

If you're still the human API holding all the threads together, try Rhythms for free at rhythms.ai.

Frequently Asked Questions

What is the difference between an executive operating review and a quarterly business review?

A QBR is a periodic, often client- or board-facing meeting that reviews performance over the previous quarter — it looks back and communicates. An executive operating review is an internal leadership cadence, usually weekly or monthly, designed to surface operational reality in real time and produce decisions. The two differ in almost every dimension that matters: the prep process, the data sources, the agenda structure, and the output. A QBR reports on what happened. An EOR decides what to do now.

How often should an executive operating review be held?

Most high-performing leadership teams run a weekly EOR at the executive level, with a deeper monthly version that adds financial and strategic context. The exact frequency matters less than the consistency. A review that runs on a reliable cadence with the same structure compounds in value, because prior decisions and follow-through are built into every subsequent session. An irregular review, no matter how thorough, keeps starting from zero.

What data should be included in an executive operating review?

An EOR should pull live data from every function: revenue pipeline from the CRM, operational metrics from project tracking, customer health signals from CS and support tools, financial actuals from finance systems, and the open risks and decisions carried over from the prior session. The critical requirement is that the data be system-generated, not self-reported. A pre-read assembled from Slack messages and a hand-updated spreadsheet isn't an operating review — it's a trust-and-verify meeting wearing the label.

Who runs the executive operating review?

Typically the Chief of Staff or COO owns the EOR infrastructure — agenda design, pre-read preparation, decision capture, and follow-through tracking — while the CEO chairs the meeting itself. In an AI-powered EOR, most of the preparation work (data pulling, pre-read generation, risk flagging) is handled by the system. That shifts the Chief of Staff's role from data collector to decision facilitator, which is the more valuable use of the seat.

How is an executive operating review different from a status update meeting?

A status update tells you what happened; an executive operating review tells you what to do next. Status meetings are backward-looking and exist to transfer information. EORs are forward-looking and exist to make decisions. The structural difference is concrete: an EOR has an explicit decision log, an owner for every open item, and a mechanism for carrying unresolved items into the next session. A status update has none of these — which is why so many teams hold one every week and wonder why nothing changes.