--- title: "Make Operations Review Meetings Drive Decisions, Not Status" url: "https://cooinsider.com/qa/make-operations-review-meetings-drive-decisions-not-status/" author: "COO Insider" published: "2026-09-28" updated: "2026-09-28" --- # Make Operations Review Meetings Drive Decisions, Not Status ## Make Operations Review Meetings Drive Decisions, Not Status Operations review meetings should produce clear decisions, not long status updates. This article shares practical ways to focus agendas, assign owners, and turn discussion into action. It also includes insights from experts in the field on making every meeting more effective. ### Require Recommendations and Named Owners Our ops reviews used to be glorified status updates. Everyone read their slide, nodded, moved on, and nothing actually got decided in the room. The single change that fixed it: we stopped letting anyone present a problem without also presenting a recommendation. If you walk in with a metric that's off, you walk in with what you think we should do about it, even if you're wrong. That one rule turned the meeting from "here's what happened" into "here's what we're doing about it." I run Simply Noted; we build the machines that write real handwritten notes for businesses. I have 6 patents pending, and I'm a former NFL player, so I've sat through more useless film review sessions than I care to admit. Same lesson applies. When ownership of a decision isn't assigned before the meeting ends, it dies in the group chat. Now every open item leaves the room with one name attached and a date. Meetings dropped from 45 minutes to under 20, and honestly, people stopped dreading them. Rick Elmore, Founder/CEO, Simply Noted (simplynoted.com) *— [Rick Elmore](https://www.linkedin.com/in/rick-elmore), CEO, Simply Noted* --- ### Make Proposers Own Experiments The single change that made our meetings decisive was ownership. Whoever proposes an experiment owns it from start to finish and presents the results the following week. At Eprezto we run a weekly growth review based on data. If you bring an idea, you are not just suggesting it, you are signing up for it. You run it, you measure it, and next week you come back with what happened. That changes the conversation in the room. People only propose things they are willing to own, so the list of ideas gets more serious. And the meeting stops being about who is working on what, because the owner is already clear. The time goes to looking at real results and deciding what to keep, what to change, and what to stop. The weekly rhythm matters as much as the rule. A result that comes back next week still feels connected to the decision that started it. A result that comes back two months later is just another update. I would add that this is a habit, not a policy you announce once. Culture comes from doing it every single week, not from a slogan on a wall. *— [Louis Ducruet](https://www.linkedin.com/in/louis-ducruet-35ab8531), Founder and CEO, Eprezto* --- ### Frame Agenda Items as Decisions When our operations reviews started feeling like everyone just taking turns reading from a dashboard, I knew something had to change. Nobody was deciding anything. We were just... reporting. The fix wasn't complicated, but it required some discipline upfront. Every agenda item now has to arrive pre-classified. Not as a topic, but as a decision that needs to be made. Before anyone walks into the room, they know exactly what we're choosing between and who owns the outcome when we leave. If someone can't frame their agenda item as a decision, it doesn't make the meeting. It goes in Slack. That single shift transformed everything. When people know they're accountable for a specific outcome before the meeting starts, they stop showing up with raw data and start showing up with a recommendation. The conversation moves faster because we're not spending 15 minutes establishing context. We're debating options and committing. The other thing that helped enormously was assigning a decision owner for each item before the meeting, not during it. When everyone knows Sarah is the decision-maker on the content budget question, the discussion stays focused. We're not all lobbying for authority. We're advising someone who has to commit. We also killed the "any updates?" portion entirely. If it's just an update, it gets written down and distributed beforehand. The meeting time is protected for things where human judgment and debate actually matter. Our ops reviews went from 90 minutes of performance theater to 40 minutes of real movement. People leave knowing what they decided, what they own, and what happens next. That's it. The single change? Requiring every agenda item to be written as a decision statement with a named owner before the invite goes out. Everything else followed naturally from that. *— [Jason Bland](https://www.linkedin.com/in/jason-bland-89a5679), Co-Founder, Custom Legal Marketing* --- ### Ban Slides and Name DRIs I banned PowerPoint from our ops meetings at my fulfillment company in 2019 and our average meeting time dropped from 90 minutes to 35. People thought I was insane. Here's what was happening. My warehouse GM would spend 20 minutes walking through slides showing pick rates, order volume, accuracy metrics. Everyone nodded. Nobody decided anything. We'd end with "let's circle back next week" on the same three issues we'd been discussing for a month. I realized we were performing competence instead of solving problems. The single change that fixed it: I required every agenda item to come with a proposed decision and a DRI (directly responsible individual) named before the meeting started. If you couldn't articulate what decision needed to be made and who would own the outcome, it didn't make the agenda. Status updates went into a shared doc everyone read beforehand. First meeting after this change was chaos. People showed up expecting to present and had nothing prepared for actual decision-making. But by week three, something clicked. My ops director came in with "Decision needed: approve $47K for two new pack stations or accept 15% longer processing times through Q4. I recommend we approve. Here's why." We discussed for eight minutes, I asked two questions, we decided, meeting moved on. The other thing that helped was standing meetings. Literally standing. When your lower back starts hurting you stop talking in circles. What really changed wasn't the format though. It was forcing people to own outcomes before walking into the room. When you make someone put their name next to a recommendation, they do the thinking beforehand instead of workshopping it live with ten people. At Fulfill.com now, every partner call follows this same structure. We're not there to brainstorm, we're there to decide and move. The best meetings are the ones where someone leaves with homework and everyone else leaves knowing exactly what changed. *— [Joe Spisak](https://www.linkedin.com/in/spisakjoe), CEO, Fulfill.com* --- ### Foster Collaborative Group Decisions What I like to do is make these meetings more collaborative. Instead of the meetings just being me giving my team updates and sending them on their way, or employees giving an update of their current progress and then simply leaving it at that, we make sure that we are talking things through. These meetings are a space to ask questions, pitch ideas, and make decisions as a group. It doesn't necessarily make the meetings shorter, but I would definitely say that it makes the meetings more purposeful and beneficial to everyone. I'm also big on collaboration when it comes to making decisions because it helps prevent tunnel vision, so that's one of the biggest benefits for me. *— [David Joles](https://www.linkedin.com/in/davidjoles5863), Chief Operating Officer, PURCOR Pest Solutions* --- ### Open With the First Disagreement If you can guess what each person is going to say before they say it, you are running a newsletter with a calendar invite. That was our operations review for most of last year. Every update got read aloud to a room that had already read it. Nobody here shares a building and there are 60 of us. The review is the one hour where the whole business is visible in one place. The single change was putting the numbers in a document the day before and opening on the first disagreement. Nothing gets read out now and an item does not close until one name is attached to it out loud. Some meetings exist because nobody trusts the written record. The agenda is the easier half of that problem. The review runs 25 minutes. Our finance lead said the first short one felt abrupt. *— [Sagar Agrawal](https://www.linkedin.com/in/sagar-agrawal-qubit), Co-founder, Qubit Capital* --- ### End Each Item With Commitment When our operations review meetings started feeling like status updates, the biggest change I made was requiring every agenda item to end with a decision, an owner, or a clearly defined next action. In a plating operation, there are always updates to share—production schedules, quality issues, equipment, customer deadlines—but simply reporting them doesn't move the work forward. I remember a meeting where we spent too long discussing a recurring production delay until I finally asked, "Who owns fixing this, and what are we doing before the next meeting?" That question turned a circular discussion into an actual commitment. Now, routine updates can be shared beforehand, while meeting time is reserved for exceptions, problems, and decisions that require multiple people. That single shift made our meetings shorter because people come prepared to resolve issues rather than narrate what happened during the week. If an agenda item doesn't require a decision or ownership, it probably doesn't need meeting time. *— [Dawn Stutzman](https://www.linkedin.com/in/dawn-stutzman-b7474154), Owner, Stutzman Plating* --- ### Attach Owners Before Agenda Entry Most meetings turn into status updates because nobody decided beforehand what actually needed a decision. So the agenda fills up with reports instead. Running a lean team, that problem showed up fast for us. With a small group, you feel the wasted time immediately. The instinct is to fix the meeting itself, run it tighter, add a timer, cut people off. But that doesn't work. The problem is upstream. So we stopped letting agenda items in without a named owner attached. Every item had to have one person responsible for bringing a decision, not a summary, not an update, an actual decision. I remember one meeting where we spent forty minutes going back and forth on a product call that should have taken ten. Nobody owned it walking in, so everybody weighed in and nobody moved it forward. After that, we added one rule: no item hits the agenda without a name next to it. When people know they own something before they walk in, they show up prepared. That ten minutes of prep before the call is what cuts the meeting itself in half. I haven't gone back since. *— [Nikhil Pai](https://www.linkedin.com/in/nikhilpi), Founder, Chronicle Technologies* --- ### Move Updates to Written Pre-Reads The one change that fixed this for us: nobody reports anything in the meeting that could have been sent in writing beforehand. If it's a number, it goes out in advance. The meeting is only for things that need a decision. I run Green Planet Cleaning Services in the Bay Area. Our reviews had drifted into exactly what you're describing — a round-robin where each person narrated their week, everyone nodded, and we left with nothing actually resolved. The tell was that I could have skipped the meeting entirely and lost no information. What we do now is simple. Anything that's a status update gets written down and shared ahead of time. The meeting opens with one question: what decision are we making today, and who owns it after this call? If nobody can name a decision, we cancel. We've cancelled plenty. Cancelling a meeting because there's nothing to decide is not a failure — it's the system working. The second thing that made it decisive was requiring a name and a date on every outcome before we move to the next item. Not "we should look into the scheduling issue" — "this specific person is fixing the Tuesday route by the 20th." Ownership assigned to a team is ownership assigned to nobody. I learned that the expensive way, watching the same operational problem reappear in three consecutive meetings because everyone assumed someone else had it. The third: I stopped opening. When the owner speaks first, everyone else calibrates to what I said instead of telling me what's actually happening, and the meeting becomes a performance of agreement. Now the people closest to the work speak first, and I go last. The quality of what I hear changed immediately, and the honest problems surfaced weeks earlier than they used to. Net effect is shorter meetings with fewer people in them and more things actually getting fixed. The best proxy I've found for whether a review meeting is working is what comes out of it, not what goes into it — if the output is a list of owned decisions with dates, it earned the hour. If the output is shared awareness, it should have been an email. *— [Marcos De Andrade](https://www.linkedin.com/in/marcosdeandrade), Founder & Owner, Green Planet Cleaning Services* --- ### Adopt Decision-Only Pre-Read Agendas Our operations reviews turned into status theatre when every tool owner read aloud what the dashboard already showed. The single redesign that made them shorter and decisive was a pre-read rule plus a decision-only agenda. Forty-eight hours before the meeting, each owner posts written status. In the room we only discuss items that need a yes, no, or budget call, and every decision leaves with a name and a date. If nobody needs a decision, we cancel the meeting. Status updates that survive as narration get pushed back to async. That change cut the standing hour down to about twenty-five minutes on a good week and stopped the habit of deferring hard calls to "next time." It also exposed how much of our stack was noise. When the agenda forces a kill-or-keep decision on dormant licences in the room, utilisation improves because ownership is public. Meetings became places where money and responsibility move, not where people perform busyness. *— [Christopher Coussons](https://www.linkedin.com/in/chriscoussons), Director, Visionary Marketing* --- ### Reserve Meetings for Exceptions Ban status from the room. Anything that can be read gets sent out beforehand, and the meeting opens only on the items where somebody has to make a call. That's the single change. The pull toward status is strong in my work, because cleaning teams are spread across a lot of different homes at once. A review turns into a roll call of who finished what and which turnover ran long. Nobody needs a live meeting to hear that. It fits in a message. So the agenda is exceptions only, like a turnover that keeps running over or a supply that keeps running out. Each one gets written as a question the room has to answer, such as whether to change the time we allow for that size of home, yes or no. Every item ends with a named owner and a date, said out loud and written where everyone can see it. If nobody will take the name, the item wasn't ready, and it goes back instead of drifting into next week. The meeting gets shorter because most items never make the agenda. The ones that do are the ones that need a person. The next review opens with those names. *— [Carolyn Vasquez](https://www.linkedin.com/in/carolyn-vasquez-42a51a44), Founder, Ready Rental Cleaning* --- ### Limit Agendas to Three Decisions Ops reviews turned into status theatre until we banned verbal updates that already lived in the calendar. The single change was a standing agenda with three decisions only: open holds against the $47 deposit, overdue rewrites after 60-minute visits, and anything blocking the Texas-during-appointment rule on The Functional Medicine Process: What to Expect at https://www.interlinkedwellness.com/process. Each item needs a named owner before we leave the room. Meetings got shorter because reading aloud was cut. Ownership either happens live or the item stays open with a name and a due time, not a vague next week. *— [Anna Evans](https://linkedin.com/in/anna-evans-msn-aprn-fnp-c-78b1582a8), Founder, Interlinked Wellness* --- ### Use Live Files as Agendas Ops reviews stopped being status theater when we brought the live exception or closing file into the meeting, decided on that file, and ended only after ownership was assigned. Verbal updates about deals that already lived in the product got banned. Someone shares the screen on the stuck transaction, the room names the blocker, and a person leaves with the next action before we hang up. You cannot afford a meeting that re-narrates dashboards. The single change was treating the file as the agenda. Meetings got shorter because reading aloud was cut, and decisive because ownership is a name on the deal, not a vague follow-up. *— [Dane Maxwell](https://www.linkedin.com/in/dane-maxwell-b7105b5b), Founder, Paperless Pipeline* --- ### Build Decision-Ready One-Page Packets Our ops reviews used to read like a tour of every open tab. I redesigned them around decisions only. Each agenda item must arrive with a proposed choice, a named owner, and the Shopify or pack-out number that makes the choice real. Updates that need no decision move to a written note before the meeting. The room is for yes, no, or a dated deferral. The single change that shortened meetings was a one-page pre-read limited to Creatine Gummies from $25, Saffron Sleep X from $31, London pack-out capacity, and the roughly 10 customer calls a month that flag issues. We walk those lines, decide, and stop. Status theatre ate an hour. Decision-ready packets take about twenty minutes and leave the small DTC team with clear owners. *— [Neill David Watson](https://www.linkedin.com/in/neilldavidwatson), Founder, APMZEE* --- ### Bring Decisions and Accountable Owners When operations review meetings start feeling like status updates, I redesign them around exceptions and decisions, not reporting. The single change that made our meetings shorter and more decisive was requiring every issue brought into the room to come with a clear decision needed and one person responsible for the next action. On one project, we were spending too much meeting time reviewing what each crew had already completed, information everyone could have read beforehand. We moved those updates out of the meeting and used the time to address an unresolved waterproofing issue that was holding up the next phase of work. Within minutes, we agreed on the corrective approach, assigned responsibility, and set a deadline. My rule now is simple: if an item doesn't require a decision, escalation, or commitment from someone in the room, it belongs in the written update, not the meeting. *— [Bryan Peralta](https://www.linkedin.com/in/bryan-peralta-54a550178), Owner, Stucco Contractor Pro* --- ### Project a Live Decision Log Operations reviews degrade into status updates when the agenda is organized by team rather than by decision. I inherit the same failure in nearly every operating cadence I am brought into. Each owner reports, nobody is accountable for a choice, and the meeting produces information instead of direction. Rewrite the agenda as a list of pending decisions with a named owner and a default action for each. Circulate the status in writing beforehand and treat anything already written as read. Reserve the room for items where the choice is still open and the cost of delay is real. The single change that works is a decision log projected on screen for the whole meeting. Every item closes as decided, deferred with a date, or dropped, and the log carries forward. Decision discipline is what separates a review from a briefing. Make the decision the unit of work, not the update. *— [Kamyar Shah](https://www.linkedin.com/in/kamyarshah), Fractional COO, World Consulting Group* --- ### Separate Reports From Decisions A meeting that only shares information is a document pretending to be a conversation. In dispute resolution outside court, I have watched reviews become round-robins where each person reports and nothing moves. The status turned into the whole meeting, and the decisions kept slipping to next week. Once I saw the pattern, I rebuilt the room around one job, choosing what happens next. The single change that worked was moving every status update into a written pre-read sent the day before. People arrive having read the numbers, so the hour goes to the few calls that actually need the group. Each item now ends in a decision, a named owner, and a date, written down in the room. That structure cut our reviews roughly in half and made the outcomes real. The deeper fix was separating reporting from deciding, because the two need different energy. A common situation is a review where several people update, everyone nods, and no one leaves accountable. I would rather spend ten minutes on a real decision than forty on a tour of dashboards. The test I use is simple, if an item carries no decision, it does not need the room. Reports go in writing, questions go in the room, and owners leave with dates. Treat the meeting as your most expensive recurring cost, because a room of senior people is exactly that. Shorter reviews are the sign that decisions are finally happening where they should. *— [Kanchan Gupta](https://www.linkedin.com/in/kanchangupta), C-Founder and COO, CADRE ODR* --- ### Review Only Off-Track Work The single change I'd make is reviewing only what's off track. Everything on pace gets a line in a shared document and no airtime. Think about halftime in football. Coaches skip replaying every snap. They find the two or three things losing the game and fix them before the team heads back out. An operations meeting works the same way. When every item gets equal time, the problems that need a decision get squeezed into the last five minutes. In fundraising, that might mean passing over the events that are on track and spending the whole meeting on the one sponsorship package that isn't selling. The group can decide right there whether to reprice it, simplify the tiers, or bundle it differently, and someone leaves owning that call. The meetings get shorter on their own, because a healthy week gives you less to discuss. The format also rewards people for flagging trouble early, since raising a hand is how an issue gets help. When people aren't worried about being blamed for a problem, they're more likely to bring it up early, and the meeting can focus on fixing it. *— [Scott Shirley](https://www.linkedin.com/in/scottshirley), Founder & CEO, Pledge It* --- ### Turn Operational Problems Into Decisions In towing, a meeting has very little value if everyone simply explains what happened during the week. We already know which jobs were completed. What matters is identifying what repeatedly slowed us down or created unnecessary difficulty. The most useful change is turning operational issues into decisions. Instead of saying, "We had trouble accessing this car park," the discussion becomes, "What information should dispatch collect next time before we send a truck?" Then one person owns the change. That distinction makes meetings much more practical. A difficult recovery might lead to a change in the questions we ask customers, how we allocate trucks or what information drivers receive before arriving. My rule is that an operational problem should leave the meeting with either a decision, an owner or a reason why nothing needs to change. Otherwise, we are just retelling the week. *— [Joshua Harrison](https://www.linkedin.com/in/joshua-harrison-582874419), Founder, Underground Towing & Salvage* --- ### Focus Each Meeting on One Trade-Off Most teams run operations reviews as a read-ahead-then-confirm exercise, which means the real work happens in Slack before anyone sits down. You're just documenting decisions that already landed offline. The shift that actually worked for us was inverting the agenda. Instead of "here's what happened, approve it," we walked in with a single unresolved constraint and one person owning the decision in real time. Not a prepared answer, a live trade-off call. One meeting, DeLonghi team wanted faster QR code deployment but couldn't hire faster. We had to choose: delay the contract three months, or pull one person from maintenance. That decision took 22 minutes because everyone could see the cost and the person making the call wasn't hiding behind a pre-written slide. The operational cost was specific enough that it forced clarity. When you name the delay or the lost margin out loud, the decision becomes about trade-offs you can actually measure, not about who has the loudest opinion. We went from 90-minute status reviews to 40-minute decision meetings, same attendees, because there was no room for recirculation. The single change: one unresolved question per meeting. Not ten. One. If you can't name the trade-off in a sentence, the meeting isn't ready to happen yet. The prep work just moves earlier, to whoever is designing the question, not to whoever is attending it. *— [Siim Kostabi](https://www.linkedin.com/in/siim-kostabi), CEO, Pageloot* --- ### Require Owners to Read Back Decisions The year we grew fast, our reviews turned into status theater. The owner says the decision out loud before we move on, naming what they're doing, by when, and who they'll tell. I ran admissions before I ran a center. It's like if you're doing something and then you come together to do something and the owner says it back in one sentence and the loop is closed, the owner can then say it in their own words and not have the person running the meeting summarize it. It's borrowed from clinical handoff where the nurses read back a verbal order to close the loop. We just talked near a decision for nine minutes. The readback gives them a reason to think. What goes on the agenda is the exception, not the routine. We've cut the ops review in half, keeping only the thing that broke or the thing about to break on the agenda. It was the fix, not the agenda, but if they can't say it cleanly, we didn't actually decide anything, and it gave us a good sense for how many times "we are aligned" meant three people holding three different versions of the plan. I used to fill silence because silence felt like disengagement. Silence is not disengagement. Silence is thinking. So now I wait. Census? Staffing? We don't need to hear about census and staffing. *— [Michael Schaub, MHA](https://www.linkedin.com/in/michael-schaub-mha), CEO, Aura Recovery Center* --- ### Cap Decision Agendas at Three Lines Ops meetings turned into status theatre when everyone read the Shopify dashboard aloud. The redesign was a pre-read rule plus a decision-only agenda: three lines max, each needing a yes, no, or date. We stopped recounting yesterday's orders and started deciding next week's PO for The Doux and who covers the weekday inbox. In The UK Wash-Day Report 2026, wash days sat 4.8 days apart. Meetings that end with a decision protect that rhythm. Meetings that end with a round of updates do not. *— [Emma Rusby](https://www.linkedin.com/in/emma-rusby), Director, Zenvy Beauty* --- ### Limit Attendance to Essential Participants I redesigned operations reviews by limiting attendance to only the people directly involved in the agenda items so decisions and ownership happen in the room. If an issue affects only one or two people, I address it with them separately rather than in the full meeting. That single change eliminated broad status updates, shortened meeting time, and made it clear who must act. I also keep recurring meetings on the calendar but cancel them the day before if they are not needed to protect time for higher priorities. *— [Seth Berge](https://www.linkedin.com/in/seth-berge-16512b66), Founder, CEO, Regenerative Revival* --- ### Assign Decision Owners Before Meetings Status reporting becomes expensive when the people who can act are listening to information they could have read beforehand. We replaced the opening round of updates with a written pre-read that identified only exceptions, missed commitments, customer risk, inventory exposure, or decisions needed. The single change was assigning one named decision owner to every issue before the meeting began. That person arrived with a recommendation, the tradeoffs, and a deadline. The group could challenge assumptions, then decide or explicitly defer with a reason. In an online furnishings business, a delayed choice can affect merchandising, fulfillment, and customer expectations at once. Naming ownership converted discussion from collective observation into an operational commitment. *— [Todd Harmon](https://www.linkedin.com/in/todd-harmon-6823202), Founder & Owner, BathGems* --- ### Enforce Exception-Only Pre-Reads As an Industrial Project Manager, I view operations reviews as diagnostic sessions, not reporting exercises. When meetings devolve into status readouts, it usually means the team is managing the agenda instead of managing the process. To redesign these meetings for true ownership, I implement an "Exception-Only" reporting structure rooted in Lean methodologies. Routine operational data, such as baseline Overall Equipment Effectiveness (OEE) or standard logistics tracking, shifts to an automated dashboard for asynchronous review before the meeting. If a metric is within acceptable control limits, it is off-limits for discussion. When an out-of-bounds variance occurs, the area owner doesn't just report the drop; they must bring a root-cause hypothesis and two proposed corrective actions. This shifts the room's dynamic from passive listening to active problem-solving. The single most impactful change that made our meetings significantly shorter and more decisive was the "Pre-Read Requirement." I eliminated presenting raw data live. Because all stakeholders review the dashboard before walking in, the meeting starts immediately at the point of friction, focusing exclusively on critical bottlenecks and the specific resource allocations needed to unblock them. *— [Akhilesh Korpe](https://www.linkedin.com/in/akhilesh-korpe), Industrial Project Manager I, Smith Seckman Reid Inc* --- ### Related Articles - [Make Recurring Operations Meetings Drive Action, Not Status](https://cooinsider.com/qa/make-recurring-operations-meetings-drive-action-not-status) - [How COOs Set an Operating Cadence That Drives Accountability in Operations](https://cooinsider.com/qa/how-coos-set-an-operating-cadence-that-drives-accountability-in-operations) - [Keep Distributed Operations Aligned Without Meeting Overload](https://cooinsider.com/qa/keep-distributed-operations-aligned-without-meeting-overload)