It’s very rare for an organization to set out to make decision-making slow. But over time, they’ll tend to find that they add review steps because something went wrong, a cost was underestimated, a risk was missed, or a project was approved with unclear ownership, then drifted.
So with the best intentions, the organization adds more process: more templates, meetings, sign-offs, and questions before anything can move forward. Unfortunately, despite those noble aims, the result is often frustrating, as decision-making becomes slower, but not necessarily any better. Teams find themselves spending more time preparing for approval, while leaders still struggle to understand the request, owner, assumptions, and follow-through.
Fast decision-making doesn’t mean removing accountability, and accountable decision-making doesn’t mean just tacking heavyweight process onto every request. The better goal is to make decisions clear enough to move quickly and accountable enough to stand up to scrutiny, with ownership, proportionate evidence, appropriate approval paths, visible assumptions, and usually at least a simple tracking plan.
Why process slows decisions down
Decision-making often slows down when process is used as a substitute for clarity. For example, a team may be asked to complete a large template because leaders want confidence. But if that template doesn’t clarify the decision, options, evidence, risks, or outcome, all it really achieves is creating more work.
You’ll see the same problem happening in approval meetings; a request reaches a committee, but the discussion becomes circular because key questions are unresolved. What decision is being made? Who owns the outcome? What evidence supports it? What assumptions matter? How will success be measured later?
When these questions are unclear, the process expands, the request gets sent back, and the decision may officially be “under review,” but really it’s stuck in ambiguity.
Speed comes from reducing that ambiguity.
The difference isn’t just about decision size, but about how they’re approached; a lightweight decision can move quickly when the owner, rationale, outcome, and next step are clear, but a larger investment can still move efficiently when evidence, financials, risks, and approval route fit the decision.
The issue isn’t whether process exists, but whether it improves the decision.
Give every decision a clear owner
No matter the company size or structure, something holds true: accountability becomes weak when ownership is shared too broadly.
Many decisions involve multiple contributors; finance may review numbers, legal may check contractual risks, IT may validate feasibility, while senior leaders may approve the investment. Yet despite those varied stakeholders it doesn’t change the fact that the decision still needs a clearly named owner.
That’s not to say that the owner needs to make every call alone. Their role is to make sure the decision is prepared properly, the right people are involved, assumptions are visible, and follow-through happens after approval. Without that clear owner, decisions tend to become easy to support, yet difficult to manage.
A useful owner should be able to explain the problem being addressed, the outcome being pursued, the recommended option, the remaining uncertainty, and what happens after approval.
However, this doesn’t need to become weighed down by bureaucracy. For smaller decisions, ownership may be captured in a few fields. For larger decisions, it may sit alongside financial modeling, risk assessment, review, and tracking.
The principle remains the same: every decision should have someone accountable for moving it from request to outcome.
Match evidence and approval to the decision
One of the easiest ways to slow down decision-making is to ask every request to meet the same standard of evidence. A low-cost operational improvement shouldn’t need the same analysis as a multi-year strategic investment. At the same time, a major investment shouldn’t be approved on enthusiasm, anecdotes, or a high-level slide.
Fast, accountable decision-making depends on proportionate evidence.
For smaller decisions, the evidence may be simple: the problem, expected benefit, cost or resource requirement, and obvious risks or dependencies.
For larger decisions, the evidence should be more rigorous: options considered, financial impact and assumptions, scenario modeling, key risks, success measures, and tracking approach.
The goal isn’t to create a bigger document, but to give approvers the right level of confidence for the decision.
And the same principle should be applied to approval paths; some decisions just need a simple manager review, some need finance input, some need cross-functional approval, while some need executive sponsorship because the decision affects strategy, risk, budget, or multiple teams.
Problems tend to arise when the approval path is either unclear or disproportionate. If a small decision needs too many sign-offs, speed disappears, while if a large decision bypasses the right scrutiny, accountability disappears. A practical approval path should make clear who reviews the decision, what each reviewer checks, and what standard the decision must meet before it moves forward.
That avoids turning every reviewer into a general critic, and lets them focus on their area of expertise: finance can focus on financial logic, legal on contractual risk, operational leaders on feasibility, and executives on prioritization.
Speed improves when approval becomes a route, not a maze.
Make assumptions visible
Uncertainty itself isn’t a problem, as almost all decisions contain uncertainty, the problem is when that uncertainty is hidden.
A decision may look strong because the financials appear positive, the timeline looks achievable, or the benefits sound compelling. But those conclusions often depend on assumptions that haven't been tested.
For example, adoption may be higher than expected, implementation may take longer than planned, internal capacity may be constrained, or benefits may arrive later than the costs.
If these assumptions aren’t visible, the decision may well move quickly at first, but it will then slow down later when the challenges of the real world emerge.
Accountability improves when assumptions are clearly separated from evidence. The key distinction between the two is that:
🔍 Evidence is what the team knows or can support
💭 Assumptions are what the team believes, estimates, or expects
Both can be useful, they just shouldn’t be treated the same way, used interchangeably, or wrongly thought of as substitutes for each other.
Making assumptions visible helps approvers decide whether they’re comfortable with the uncertainty. It also gives the organization something to revisit later, so it can learn whether the original decision logic was sound.
The answer isn’t to wait until everything is known; it’s to move with clarity about what’s known, what’s assumed, and what needs to be watched.
Keep accountability after approval
Many organizations put significant effort into getting a decision approved, but they then lose discipline once approval is granted. The decision becomes a project, purchase, initiative, or workstream, and with the original rationale sitting hidden away in a long forgotten slide deck, the assumptions often won’t be revisited, and the expected outcomes not tracked.
That is where accountability often fades.
Even a fast decision should still leave behind a simple tracking plan. It doesn’t need to be complicated, but it should clarify the approved outcome, delivery owner, benefits to track, assumptions to revisit, and signals that the decision may need adjustment.
The main intention is to create a bridge between approval and outcome. It also helps leaders see patterns across decisions, because if decision data is structured consistently, organizations can understand what has been approved, where value is expected, where initiatives overlap, and whether outcomes are being achieved.
Tools like KangaROI are useful here because they keep the decision, evidence, approvals, assumptions, outputs, and tracking plan connected. The value isn’t in just producing a business case or approval package, but in preserving the decision logic so that the organization can manage what happens next.
Practical ways to keep speed and accountability together
Organizations shouldn’t think that they need to choose between fast decisions and responsible decisions. What they need is a lighter, clearer way to govern decisions based on size, risk, and importance. A practical approach is to:
🎯 Define the decision before creating documents or slides
👤 Name one accountable owner for preparation and follow-through
⚖️ Match evidence requirements to the size and risk of the decision
✂️ Separate evidence from assumptions
🛤️ Use approval paths that fit the decision
📌 Capture the expected outcome before approval
📊 Create a simple tracking plan for what happens after approval
🧭 Review decision data across teams to spot risks, duplication, and progress
As we've seen several times already, the key is proportion. Small decisions shouldn’t be buried under unnecessary process, while large decisions shouldn’t rely on loose narratives and optimistic assumptions.
The right structure actually helps both sides, as teams move faster because they know what good looks like, while leaders make better decisions because they can see the rationale, risk, ownership, and expected outcome.
Conclusion
Decision-making slows down when organizations add process without improving clarity. More meetings, templates, and sign-offs may create the appearance of control, but they don’t automatically improve accountability.
Fast, accountable decision-making starts with clarity. What decision is being made? Who owns it? What evidence supports it? What assumptions matter? Who needs to approve it? What outcome is expected? How will progress be tracked?
When those questions are answered at the right level of rigor, decisions can move quickly without becoming careless.
Speed and accountability aren’t opposites; they work together when decisions are structured clearly enough to approve, deliver, track, and learn from.
