You are sitting in another decision meeting.
This is the third one on the same topic.
The first meeting surfaced the issue. The second pulled in more data. The third was supposed to be where you decided, except that someone has now raised a new question that requires more analysis, and the meeting is being rescheduled for next week. Three weeks have passed since the issue first appeared. The business has continued to operate on the old assumption while the leadership team has been preparing to decide on the new one. Nothing has happened, except the production of more reports, more slides, more analysis, all of which point in roughly the same direction the first meeting did.
This pattern is the most expensive operational habit in growing Australian businesses in 2026. The CEO will tell you the business is data-driven. The reality is that the business is data-paralysed. Every decision now requires a fuller analysis than the previous one. Every analysis surfaces a new question that requires further analysis. The leadership team is increasingly informed and decreasingly decisive, and the cost of the delay is invisible because it does not show up in any single report.
Research has repeatedly linked faster decision-making to higher performance. McKinsey analysis has found that decision velocity correlates with outperformance, particularly during periods of volatility. Recent industry research has shown that organisations optimising for decision velocity see materially faster time-to-market and higher revenue growth than those focused on decision quality alone. But few growing businesses have a framework for actually doing this. They have data. They have meetings. They do not have a structured way of turning the data into decisions at speed.
This post is the practical framework for that work. Built for operations leaders at growing businesses who have moved past the "we need more data" stage and are now in the "we need to actually decide things" stage.
Why most data-rich businesses are decision-poor
Before getting to the framework, it is worth being honest about why this gap exists. The causes are consistent.
More data has not produced more clarity. The amount of data available to leadership teams in 2026 is dramatically larger than it was five years ago. The amount of clarity has not increased at the same rate. More data means more questions, more nuances, more edge cases. Without a framework for what is decision-relevant and what is not, the additional data slows decisions rather than accelerating them.
Every decision is being treated as a high-stakes decision. The leadership team applies the same rigorous analytical process to a five-thousand-dollar process change as to a five-hundred-thousand-dollar capital investment. The careful approach for the second is wasted on the first. The team is exhausted from over-analysing decisions that did not need the analysis, and slow on the ones that did.
Nobody is explicitly the decider. Multiple people contribute to the decision. Nobody has been told that they own it. So the decision sits, because no individual has the authority to make it, and no group has the discipline to converge.
Analysis has become a substitute for judgement. When the data does not produce a clear answer, the response is to do more analysis. Sometimes this is appropriate. Often, it is a way of avoiding the harder work of making a judgement call with imperfect information. The leadership team is more comfortable commissioning a study than making the call, and the meeting culture rewards thoroughness over decisiveness.
The cost of the delay is invisible. When a decision takes three weeks instead of three days, the team feels productive (they are working) and informed (they have data). The cost of those three weeks (lost opportunity, continued operation on the old assumption, frustrated team members waiting for direction) is real but is not measured. So the slow-decision pattern persists because nobody has named what it is actually costing.
Each of these is fixable. The fixes are structural, not cultural. The framework below addresses each in sequence.
Why "make decisions faster" is not the answer by itself
Before the framework, a quick note on the most common response to slow decision-making, which is to tell people to decide faster.
This rarely works in isolation. Without changing the structure that produces slow decisions, the team that has been told to move faster will either continue moving at the same pace or move faster in a way that produces worse decisions. The instruction without the structural support is not a solution. It is a complaint.
The framework below changes the structure. It separates decisions by type, assigns ownership clearly, defines what good information looks like for each decision, and builds the operating rhythm that produces faster decisions without sacrificing the quality of the ones that matter most.
The 5-part framework for making faster decisions with data
This is the framework we use at ThinkSwift when we work with leadership teams whose decision velocity has slowed below what the business needs. It is built for the specific situation where the data is available, the team is capable, and the friction is in how decisions are being structured.
Part 1. Classify decisions by reversibility
The single most important move is to classify every decision by whether it is reversible or not.
This framing comes from Amazon's "one-way door versus two-way door" model, and it is the foundation of fast decision-making. The principle is simple. Some decisions are hard to reverse and have large consequences if they go wrong. These deserve careful analysis. Most decisions are easily reversible and have manageable consequences. These should be made fast, with good-enough information, and adjusted if needed.
The mistake most leadership teams make is treating every decision like the first category. Every decision gets the same deliberate, multi-meeting analytical process. The result is that the slow careful process designed for high-stakes irreversible decisions consumes the bandwidth that should be spent on the daily flow of reversible ones.
A practical exercise. List the next ten decisions on your leadership team's agenda. For each one, ask two questions. How hard is it to reverse if we get it wrong? How big is the cost of being wrong?
The answers will surprise you. Most of the decisions on the agenda are reversible with limited downside. They should be made in a single meeting, with the data available, in under thirty minutes. The minority that are genuinely irreversible and high-stakes deserve the careful analysis the team has been applying to everything.
Once this classification becomes routine, the speed of decision-making increases dramatically, because the team stops over-investing in low-stakes decisions and starts having the bandwidth to give appropriate care to the high-stakes ones.
Part 2. Define decision rights for each category
The second move is to assign explicit ownership for each category of decision.
We covered this in detail in our post on reducing manager dependency, and the principle applies at the leadership level too. Every decision needs a named decider. Not a committee. Not a consensus. A single person who is explicitly accountable for making the call.
For most leadership teams in growing businesses, the assignment looks something like this.
Operational reversible decisions. Decided by the operations lead, in consultation with the relevant function, without leadership team review. Examples: process changes, workflow adjustments, tool changes that are below a threshold cost.
Operational irreversible decisions. Recommended by the operations lead, decided by the COO or CEO, with leadership team input. Examples: significant hiring decisions, major vendor changes, structural reorganisation.
Strategic reversible decisions. Decided by the CEO, with leadership team input. Examples: campaign launches, pilot programmes, short-term experiments.
Strategic irreversible decisions. Decided by the CEO with board input, after careful analysis. Examples: major acquisitions, product strategy pivots, significant capital investments.
This assignment is written down. It is shared. It is referenced when a decision is about to be made. The team knows, before the meeting starts, who is going to make the call.
This is the single move that prevents the most common failure mode in leadership decisions, which is the meeting that ends with general agreement and no specific decision. With explicit decider assignment, every meeting ends with a clear answer to "and who is going to act on this?"
Part 3. Define what good data looks like for each decision
The third move is to specify, in advance, what data is enough to make each category of decision.
The instinct in most leadership teams is to want more data. More data feels safer. More data shows rigour. More data delays the moment of having to make the call.
The discipline is to define, before the data is requested, what the minimum set of data is that would let the decision be made. Not the maximum. The minimum.
For reversible operational decisions, the minimum data set is usually three to five signals. The trend over the last quarter, the comparison to plan, the leading indicator, and the cost-benefit estimate. That is usually enough to make the call.
For irreversible operational decisions, the minimum data set is larger but still bounded. Add the risk analysis, the alternatives considered, and the impact of being wrong. Still bounded. Still focused on what is genuinely decision-relevant.
For strategic decisions, the minimum data set is more extensive but still defined. The principle is the same. Before the data is requested, the team specifies what would be enough to decide.
This is harder than it sounds. The instinct is to leave the question open and let the analysis expand until it produces certainty. The discipline is to close the question in advance, gather the bounded data set, and decide on it.
A practical rule. If you find yourself wanting "just one more analysis" before deciding, ask whether that analysis would actually change the decision. If the answer is "probably not, but I would feel more confident," you are in analysis-as-comfort-blanket territory, and the decision is being delayed for no genuine reason.
Part 4. Build decision SLAs
The fourth move is to set explicit time limits on how long decisions of each type should take.
This is the discipline move. Without time limits, decisions expand to fill the available time, which is usually weeks. With time limits, the team learns to converge faster, because they know the meeting is the meeting where the decision happens, not a stop along the way to another meeting.
A practical SLA structure for most leadership teams.
Reversible operational decisions. Decided within twenty-four to forty-eight hours of being raised. Often in the next standing meeting. Often by the named decider directly without a meeting.
Irreversible operational decisions. Decided within one to two weeks. The first meeting frames the decision and the data needed. The second meeting decides. No third meeting unless something material has changed.
Reversible strategic decisions. Decided within two to four weeks. Following the same pattern. First meeting frames, second meeting decides.
Irreversible strategic decisions. Decided within four to eight weeks. With deliberate, careful analysis. With explicit checkpoints. With a clear deadline.
These SLAs are not arbitrary. They are tight enough to force discipline and generous enough to allow for the appropriate level of care. The team that uses them consistently learns to make decisions at a pace dramatically faster than the team that lets every decision take whatever time it takes.
When a decision is at risk of breaching the SLA, the response is not to extend it. The response is to escalate, or to make the call with the information available, or to explicitly classify the decision differently if the original classification was wrong. The SLA is the forcing function. Without it, the slow-decision pattern reasserts itself.
Part 5. Build the learning loop that improves future decisions
The final move is the one that compounds. After significant decisions are made, the team reviews them. Not to assign blame. To learn.
The structure is simple. Three to six months after the decision was made, the team revisits it. What was decided? What was the reasoning? What actually happened? What worked? What did not? What would we do differently next time?
This is not a long exercise. Thirty minutes per significant decision is usually enough. The output is documented and added to the team's collective memory of how decisions actually play out.
The reason this matters is that decision-making is a skill the team is developing. Each decision provides evidence about what kinds of analyses were useful, what was over-analysed, what was under-analysed, where the team's intuition was right, where it was wrong. Without the learning loop, this evidence is lost. With it, the team gets measurably better at making decisions over time.
This is the part of the framework that turns decision velocity from a one-off improvement into a compounding capability. The first quarter of using this framework produces faster decisions. The fourth quarter produces faster and better decisions, because the team has been learning systematically from the decisions they have made.
What the work pays back
The businesses that do this work end up making decisions at a pace that competitors cannot match. The reversible decisions get made fast, freeing leadership bandwidth for the irreversible ones. The irreversible ones get made with appropriate care, but in defined timeframes. The team learns from each decision, and the quality of decision-making compounds.
The businesses that skip this work end up in the meeting-velocity trap. The leadership team is busy. The decisions are slow. The data is abundant. The business is moving more slowly than it should, and the cost of the delay is invisible because it does not show up in any single metric.
The difference is structural. The framework above does not require more analytical capacity. It requires the discipline to classify decisions correctly, assign ownership, bound the data, set the time limits, and learn from outcomes. Each of these is operationally available to any growing business. Few of them have built them into their default operating mode.
The bigger picture
Fast decision-making with data is not about cutting corners or trusting intuition over evidence. It is about applying the appropriate level of analysis to each decision, assigning clear ownership, bounding the data, holding the team to time limits, and learning from the outcomes.
The five-part framework above is not complicated. It is also not the default in most growing businesses. The default is to apply careful, multi-meeting analysis to every decision, with unclear ownership, expanding data requirements, no time limits, and no systematic learning. This is the recipe for being data-rich and decision-poor, which is where most growing Australian businesses currently are.
Classify decisions by reversibility. Define decision rights for each category. Specify the minimum data for each. Build decision SLAs. Run the learning loop.
Done consistently, this is the operational discipline that turns data abundance into decision velocity, and decision velocity into competitive advantage. The business decides faster than its competitors, learns faster than its competitors, and adapts faster than its competitors. None of this requires more data than you already have. It requires the structural discipline to use the data you have in a way that produces decisions, not just analysis.
The leadership teams that build this discipline pull ahead measurably over twelve to twenty-four months. The ones that do not stay in the meeting-velocity trap, busy and analytical and slow, while the businesses around them keep making moves. The difference is the framework, applied consistently, until it becomes how the leadership team operates by default.
That is what good data-driven decision-making actually looks like in 2026. Not more analysis. Better-structured analysis, applied to a clearer view of which decisions deserve it, with explicit ownership and explicit time limits, producing decisions at the pace the business actually needs.
