Ask ten managers what's broken about how their company makes big calls and nine will blame the process. Not enough data. Too many stakeholders. A framework nobody actually opens. Hand them a cleaner framework and watch the same decision still show up three months late, made by whoever happened to be in the room, using data that's already gone stale.
The framework was never the bottleneck. The timing was.
This is a guide to strategic decision making that skips the decision-tree templates you've already seen (they're fine, by the way) and goes after the actual gap: most organisations have no fixed appointment for the decisions that matter most. We'll cover what actually counts as a strategic decision, why the standard tools rarely fail on their own terms, and a simple way to give big calls a slot in the cadence you already run, instead of waiting for them to become emergencies.
What counts as a strategic decision (and what doesn't)
A strategic decision is any call that changes the direction of the business, is expensive to reverse, and can't be made by one person acting alone. Whether to shut down a product line. Whether to double headcount ahead of a funding round that hasn't closed yet. Whether to walk away from your biggest customer because they're eating margin. Compare that to a tactical decision, like which ad headline to run this week: reversible in a day, contained to one team, no lasting exposure if it's wrong.
Three things distinguish a genuinely strategic decision:
- It's expensive or slow to undo once it's made.
- It plays out over quarters, not days.
- Getting it wrong touches more than one team's numbers.
If a decision doesn't clear those three bars, it isn't strategic. Treat it as an operational call and stop debating it in the leadership meeting.
The frameworks were never the bottleneck
Search 'strategic decision making' and you'll get a stack of decent frameworks: SWOT, cost-benefit matrices, decision trees, RAPID (who Recommends, who Agrees, who Performs, who has Input, who Decides). All of them work fine as analytical tools. None of them tell you when to actually sit down and use them.
That's the quiet flaw in almost every piece of decision-making advice out there. It assumes the moment to decide has already arrived, obviously, and all you need is a better way to think once you're in the room. In practice, the harder problem sits earlier: nobody agreed in advance whose job it is to notice the moment, or when the room is even supposed to happen.
The real problem: strategic decisions don't have an appointment
When was the last strategic call your company made on schedule, rather than under pressure?
Tactical decisions get made constantly because they're baked into someone's daily job. Strategic decisions don't have that luxury. A market shifts, a channel stops working, a competitor makes a move, and there's no standing slot on anyone's calendar for 'decide whether we still believe in this bet'. So one of three things happens instead:
- It gets punted to the next quarterly offsite, by which point the data that should have driven the call is three months stale.
- It gets made in a hallway conversation by whoever's loudest or most senior, with none of the people who'd actually catch the flaw in the room.
- Nobody decides anything, and the default becomes doing nothing, which is itself a decision. Just an unowned one, made by inertia instead of a person.
Picture a 90-person SaaS company watching customer acquisition cost creep up on its main paid channel for two months straight. Everyone's noticed. Nobody's called it.
The channel keeps burning budget at the old rate because reallocating spend feels like a decision that needs 'a proper conversation', and a proper conversation needs a slot that doesn't exist. By the time it finally gets raised, three more months of budget have gone to a channel everyone already knew wasn't working.
Ad hoc decisions vs decisions on a cadence
The difference between a company that makes strategic calls well and one that doesn't usually isn't intelligence or data access. It's whether the decision has a home.
A simple structure for surfacing decisions on a cadence
- Define the trigger conditions in advance. Agree, before anything goes wrong, what counts as a signal worth acting on: an outcome that's red for two check-ins running, an initiative blocked past its window, or an assumption behind a bet that's just been disproven.
- Name the owner before the moment arrives. 'The team will decide' is how strategic decisions die. One person's name against the call, agreed ahead of time, not negotiated in the moment.
- Use the meeting you already have. Don't invent a new ritual for this. Give strategic decisions a standing slot inside the check-in or StratOps review your team already runs.
- Bring a recommendation, not a blank question. Whoever owns the decision shows up with a view and the data behind it, not an open floor for debate from scratch.
- Record the decision and the reasoning. Write down what was decided and why, so the next review can check it against what actually happened instead of re-litigating the whole thing from memory.
A worked example
Back to that SaaS company with the creeping CAC.
Under a cadence-based approach, the trigger was already defined: two consecutive red check-ins on the paid-channel efficiency outcome.
When the second one landed, the decision didn't need a new meeting, it showed up on the agenda of the marketing lead's existing weekly review, with her name already against it as owner.
She came with a recommendation (cut the channel budget by 30 percent and reallocate to the channel that had been quietly outperforming for a month) rather than an open question for the room. The decision and the reasoning were logged. Four weeks later, the next review checked the call against what actually happened, rather than starting the whole debate over from nothing.
Common mistakes
- Waiting for perfect data. Strategic decisions rarely come with certainty attached; waiting for it is usually just avoidance with better manners.
- Deciding by committee. A group can inform a decision. It shouldn't own it. Someone's name needs to be on the call.
- Treating 'no decision yet' as neutral. It isn't. It's a decision to keep doing what you're already doing, just without anyone admitting they made it.
- Not tying the decision to a future review point. Without one, the same call gets re-opened every quarter as if it were new.
Where this fits into your cadence
This is exactly what an OKR software or StratOps cadence is for: not just tracking whether numbers are green or red, but giving strategic decisions an actual home. Tools like Tability are built around that check-in rhythm already, so when an outcome goes red two check-ins running, or an initiative sits blocked past its window, the decision doesn't need a new meeting invented from scratch. It shows up in the same review where you'd have noticed the problem anyway.
If you're building this cadence into your own team, StratOps (the function that owns strategy execution end to end) is where it usually lives, sitting on top of the OKRs your teams already track, the cascading goals that connect company bets to team work, and the weekly check-in meetings that surface problems early enough to act on them.
If your team keeps having the same strategic conversation every quarter without ever quite deciding, Tability is built to fix that: a place where check-ins, outcomes and the decisions they trigger live together, so the moment to decide finds you instead of the other way round. Sign up free or book 30 minutes with us and we'll show you what that looks like for your team.
.png)
.jpg)
