You spend half a day each month assembling the operations report.
You spend another half day distributing it, presenting it, and answering follow-up questions about it.
You receive almost no genuine feedback on what is in it. The leadership team reads parts of it, sometimes. The CEO refers to a specific page in a meeting once a quarter. The board scans the summary and moves on. Most of what you have produced is consumed politely, filed silently, and never genuinely engaged with by the people it was supposed to inform.
This is the most common pattern in operational reporting at growing Australian businesses. The report exists. The work to produce it is real. The decisions it is supposed to inform are mostly being made on other inputs, in other conversations, with the report serving as a record rather than as a tool. The COO produces it because the role requires it. The leadership team receives it because they should. Nobody is sure what would change if it stopped being produced.
This is fixable. The fix is not to produce a better-looking report. It is to fundamentally rethink what operational reporting is for, who it is genuinely serving, and how it should be structured to drive the decisions it was supposed to drive in the first place.
This post is the practical framework for that work. Built specifically for operations leaders at growing Australian businesses where the reporting effort has become disproportionate to the decision-making value it produces.
Why most COO reports are not working
Before getting to the framework, it is worth being honest about why operational reporting underperforms in most growing businesses. The causes are consistent.
The report serves too many audiences at once. The COO is producing a single report that is supposed to inform the board, the CEO, the leadership team, the operations team itself, and sometimes investors. Each of these audiences needs something different. A single document trying to serve all of them ends up serving none of them well, because the level of abstraction is wrong for almost every reader.
The format was inherited, not designed. The report looks the way it looks because that is how it has looked for the last three years. Nobody designed it for the decisions the leadership team is actually trying to make today. The format reflects the operational reality of two years ago, and the business has evolved past it.
The data is leading the narrative. The report is structured around what data is available, not around what decisions need to be made. Numbers come first. Commentary, if any, comes after the numbers. The reader has to assemble the picture themselves from the data, which is the COO's job, not the reader's.
Variance is reported without explanation. The report shows that the metric was X last month and Y this month. It does not explain why. The reader is left to guess, to ask questions in the next meeting, or to ignore the variance entirely. The opportunity for the report to drive a real conversation gets lost in the absence of interpretation.
There is no clear action point. The report describes the state of operations. It does not say what should be done about it. The reader finishes the report without knowing what the COO is asking them to do, decide, or change. The report becomes a passive document rather than an active driver of decisions.
The cadence is wrong. The report is monthly, because monthly is what most boards expect. By the time it is produced, distributed, and discussed, the underlying situation has moved on. The reader is responding to data that is already three to six weeks old, which makes the response less useful than it could have been.
Each of these is fixable. The fix is structural, not cosmetic, and the framework below addresses each of them in sequence.
Why a beautiful report is not the answer
Before the framework, a quick note on the most common response to a reporting problem, which is to invest in better visualisation. New BI tool. New chart library. New design template.
This rarely works in isolation. The format of the report is downstream of the design. The reason the report is not driving decisions is not that the charts are ugly. It is that the report is built around data rather than around the decisions the data is supposed to inform. A more beautiful version of the same broken structure will be a more beautiful version of the same broken structure.
The framework below is about the structure of the reporting itself. It can be implemented with any tool, including a plain document, and it works regardless of how the report looks. Once the structure is right, then it is worth investing in better visualisation. Not before.
The 6-part framework for operational reporting that drives decisions
This is the framework we use at ThinkSwift when we work with operations leaders whose reporting is consuming significant effort and producing little decision impact. It is built for the specific situation where the report exists, the data exists, but the connection between the report and the decisions has broken down.
Part 1. Identify the specific decisions the report should drive
The single most important move is to define, in writing, what decisions this report is supposed to inform.
This is a different exercise from listing what data the report should contain. Data is the input. Decisions are the output. Most reports start with the data because the data is easier to inventory. The right starting point is the decision.
For the COO of a growing business, the decisions that operational reporting should genuinely drive cluster into a few categories.
Resource allocation decisions. Where should we add capacity? Where should we reduce it? Where are we under-investing relative to the value being produced? Where are we over-investing?
Performance intervention decisions. Which team or function is underperforming and needs leadership attention? Which is over-performing and could be a model for the rest? What pattern of performance change is emerging that needs to be addressed?
Strategic prioritisation decisions. Are we on track for the operational goals set at the start of the quarter? Where are we ahead, behind, or off-track? What should change in the remaining time?
Risk decisions. What operational risks are accumulating? What needs to be raised at the board level? What requires management action in the next thirty days?
Investment decisions. What operational changes need budget? What is the return we are getting on the operational investments we have already made? Where should the next dollar go?
Each of these is a real category of decision the leadership team makes. The report's job is to make these decisions better. If the report is not structured around these decisions, it is structured around something else, and the something else is usually data.
The exercise is to write down, for your specific business, the five to seven decisions the operational report is genuinely supposed to drive. This document becomes the brief for the rest of the framework. Without it, the report design becomes a design exercise rather than a decision-support exercise.
Part 2. Separate the audiences and report differently to each
The second move is to recognise that one document cannot serve every audience well. Different audiences need different reports.
For most growing businesses, the operational reporting structure should include three distinct levels.
The leadership team weekly. A short, fast-moving document or dashboard that captures the operational health of the business this week. Three to five signals, a short narrative on what changed, a clear flag on anything that needs leadership attention. The cadence is weekly because the operational reality moves weekly. The format is short because the readers have limited time and need to absorb it in five minutes.
The CEO and leadership monthly. A more substantive document that captures the operational performance against the plan, the trend over the last three months, and the priorities for the next thirty days. This is where the analysis lives. Where the variance gets explained. Where the COO names what is working, what is not, and what should change. Twenty to thirty minutes of reading. Used as the agenda for a monthly operations review meeting.
The board quarterly. A high-level summary that captures the trajectory of operations over the quarter, the strategic implications, and any items that need board awareness or action. Brief enough to be read before the meeting. Structured around board-relevant decisions rather than operational detail.
Three documents. Three audiences. Three cadences. This is more work than producing a single document. It is also dramatically more effective, because each document is designed for the specific audience and the specific decisions they are making.
The discipline is to not let any one of these documents try to do the job of the others. The weekly is not a mini-monthly. The monthly is not a longer weekly. The quarterly is not an extended monthly. Each has a distinct purpose, audience, and structure.
Part 3. Lead with the narrative, not the data
The third move is to flip the structure of each report so that the interpretation comes first and the data supports it.
The standard pattern is to lead with numbers. Tables of metrics. Charts of trends. Then, often near the end, a paragraph of commentary. This makes the reader's job harder than it needs to be. They have to assemble the picture from the data, which is the COO's job, not theirs.
The better pattern is to lead with the narrative. Three to five sentences that capture what happened, what it means, and what should be done about it. Then the supporting data. Then the deeper detail for those who want it.
A practical structure for the front of each report.
The headline. One sentence that captures the most important thing the reader needs to know. "Operations is on track for the quarter, with one significant exception that needs leadership attention."
The summary. Three to five sentences that capture the state of the operation, the trajectory, and the key items for action or awareness.
The asks. A bulleted list of three to five specific things the report is asking the reader to decide, approve, or weigh in on. Not vague suggestions. Specific actions.
This front-end of the report is often half a page. It is also the part the reader actually reads. The rest of the report supports it. The reader who wants to go deeper can. The reader who needs only the summary gets what they need without having to search for it.
This is the single highest-impact structural change in operational reporting. It moves the report from "here is the data, you figure it out" to "here is what is happening, here is what I think we should do." The COO is doing the interpretive work the role is paid to do, rather than offloading it to the reader.
Part 4. Explain every variance
The fourth move is to commit, as a discipline, to never reporting a metric that has moved without explaining why it has moved.
If on-time delivery dropped from ninety-six percent to ninety-two percent, the report explains why. If the operational cost ratio improved by two percent, the report explains why. Every variance from the previous period or the plan gets a brief explanation alongside the number.
This is more work than just reporting the number. It is also the difference between a report that informs the reader and a report that creates questions for the reader to chase down later. The questions are going to come anyway. The COO can answer them in the report or in a follow-up email. Answering them in the report is dramatically more efficient and dramatically more useful.
The explanations do not need to be long. One or two sentences per variance is usually enough. "The drop in on-time delivery is primarily driven by the supplier issue with X, which is being addressed and should be resolved by the end of next week." That is what the reader needs to know, and it transforms the metric from a data point into an actionable piece of information.
A practical rule. If you cannot explain a variance in the report, the report is not ready. Investigate first, report second. A report full of unexplained variances is not a report. It is a document that says "here are some numbers, please ask me about them later."
Part 5. Include a clear set of asks in every report
The fifth move is to ensure that every report includes a specific list of what the COO is asking the leadership team to do, decide, or be aware of.
This is the action layer of the report. Without it, the report is a passive description of operations. With it, the report is an active driver of decisions.
The asks should be specific.
- "I am asking for the leadership team to approve the proposed change to the onboarding process, which is described in section three."
- "I am flagging that the customer success team is at capacity, and we will need to add a hire by Q3 if the pipeline holds. I am asking for input on whether we should start the hiring process now."
- "I am bringing attention to the increasing trend in support escalations, which I believe is related to the product change last month. I am asking for the product team's view on whether this is expected and what action should be taken."
These asks are not buried in the report. They are at the front. They are explicit. They are designed to drive the conversation in the operations review meeting and the decisions in the days that follow.
The asks also serve a second function. They make it clear, when the report is reviewed in three or six months, what the COO was asking for and what response was given. This creates an audit trail of operational decision-making that protects the leadership team's ability to learn from past decisions.
Part 6. Make the report a tool, not a document
The final move is the cultural one. The operational report needs to be treated as a tool for thinking and deciding, not as a document that gets produced and filed.
This shows up in how the report is used.
The report drives the meeting. The operations review meeting is structured around the report's asks and analysis, not around a separate agenda. The meeting is where the report's recommendations get debated and decided.
The report is iterated on. After the meeting, the COO captures the decisions that were made, the items that were deferred, and the questions that were raised. The next report responds to those. The report becomes a living conversation between the COO and the leadership team, not a static deliverable.
The report's effectiveness is measured. Periodically, the COO asks the readers what is working in the report and what is not. The format evolves based on the feedback. The report that worked at thirty employees is not the report that works at a hundred, and the design has to keep up.
This is the cultural work that turns reporting from a chore into a discipline. The businesses that do this work end up with reports that the leadership team genuinely engages with. The ones that skip it end up where most businesses end up. A monthly report nobody reads carefully, produced by a COO who is privately frustrated that the effort is not appreciated.
What the work pays back
The businesses that do this work end up with operational reporting that is genuinely shaping decisions. The leadership team responds to the asks. The decisions are made in the operations review meeting rather than informally afterwards. The board sees the operations function as a strategic contributor rather than a back-office function.
The businesses that skip this work end up with reports that consume significant effort and produce limited value. The COO is privately frustrated. The leadership team is making decisions on other inputs. The operations function is invisible at the board level because the reporting is not telling the right story in the right way.
The difference is structural. The reporting effort is roughly the same. The structure is what determines whether the effort produces decision value or just produces a report.
The bigger picture
Operational reporting is one of the most underestimated levers a COO has for elevating the operations function within the business. Done badly, it consumes effort and produces compliance. Done well, it shapes how the leadership team thinks about operations, drives the decisions that matter, and positions the operations function as a strategic contributor rather than a cost centre.
The six-part framework above is not complicated. It is also not the default in most growing businesses. The default is to produce a long, data-heavy, narrative-light report that everyone treats politely and almost nobody engages with deeply.
Identify the decisions. Separate the audiences. Lead with the narrative. Explain every variance. Include a clear set of asks. Make the report a tool, not a document.
Done consistently, this is the operational discipline that turns reporting from one of the most thankless tasks a COO does into one of the most leveraged. The report becomes the artefact through which the operations function influences the rest of the business. The COO becomes more effective because their thinking is being deployed where it can drive decisions, not buried in a document nobody reads.
The reporting work is going to happen regardless. The question is whether it produces a document that gets filed or a tool that gets used. The framework above is the difference between the two.
