From SWOT to Growth Bets: A Repeatable Way to Decide

Most strategy exercises produce a good SWOT and a mediocre roadmap. The gap isn't a lack of insight, most teams have plenty of that. It's the absence of a repeatable way to turn scattered observations into a short list, and the short list into one funded bet.

Where strategy work actually breaks down

The SWOT itself is rarely the problem. The problem is what happens after it: four quadrants of accurate, well-researched observations, followed by a jump straight to a roadmap that funds whichever idea had the loudest sponsor in the room. Gartner's research reflects this gap directly, only 43% of executives rate their organization as highly effective at assessing its own ability to execute a strategy once it's set. The analysis is rarely the weak link. The translation from analysis to a ranked, resourced decision is.

Framework 1: The SWOT Cross, from observations to five ranked bets

Rather than present a SWOT grid and stop, cross each pair of quadrants deliberately. Strengths against Opportunities asks what you attack with what you already have. Strengths against Threats asks what you defend. Weaknesses against Opportunities asks what you'd need to build to capture a trend you're currently unequipped for. Weaknesses against Threats asks what you mitigate before it compounds.

Worked example. Take a mid-size B2B software company. Its SWOT, stripped to the essentials:

• Strengths: high retention among existing enterprise customers; a proprietary usage-data asset; strong brand trust within its core base.
• Weaknesses: limited presence outside its home region; a thin, mostly inbound sales motion; an ageing core product experience.
• Opportunities: a clear adjacent need for an analytics layer its product doesn't yet serve; a fast-growing geography with low current penetration; an underserved mid-market segment.
• Threats: a well-funded new entrant targeting the same core customers; a large platform bundling a similar capability for free; slowing growth industry-wide in its core category.

Crossing these produces more candidate moves than any team can fund at once. Forced down to five, each named as a specific action with the KPI that will show whether it's working:

Five priorities are close to the ceiling before budget and attention quietly re-fragment back to funding everything a little, which is the same as prioritizing nothing.

Framework 2: Market Attractiveness x Right-to-Win, deciding which bet goes first

Not all five priorities compete for budget the same way. The two defensive ones, the multi-year contracts and the product modernization, get funded directly against the risk they offset. There's no "market" to size for a retention play. The three growth bets, the analytics module, the mid-tier product, and the geography entry, are a genuine three-way competition for the same expansion budget, and that's where scoring earns its place.

Score each on two axes, each built from weighted criteria rather than one gut-feel number:

Market Attractiveness: market size (30%), growth rate (25%), channel/distribution fit (25%), timing, how much runway before the window closes (20%).
Right-to-Win: existing assets and momentum (35%), execution ease (25%), brand and trust fit (20%), capital efficiency (20%).

Worked calculation, for the analytics module: scored 3 on size, 4 on growth, 4 on channel fit, 4 on timing, gives Market Attractiveness = (3 × .30) + (4 × .25) + (4 × .25) + (4 × .20) = 3.7. Scored 5 on assets, 4 on ease, 5 on brand, 4 on capital efficiency, gives Right-to-Win = (5 × .35) + (4 × .25) + (5 × .20) + (4 × .20) = 4.55.

Run the same math for all three:

Scoring the three growth bets. The analytics module lands in the fund-first quadrant; the geography entry is high-attractiveness but low-right-to-win, sequenced rather than funded or dropped.

This is where the framework earns its keep, in sequencing, not discarding. The analytics module scores high on both axes and gets funded first. The geography entry scores highest of the three on market size alone, the biggest expansion opportunity on paper, but weakest on right-to-win: no local presence, no local brand, nothing built yet. That's not a reason to kill it. It's a reason to sequence it: close the specific right-to-win gap first, in this case through a local hire or a distribution partnership, then rescore it next quarter rather than funding it on the size of the market alone. The mid-tier product sits in the queue behind both, revisited at the next planning cycle or folded into the analytics rollout if capacity allows.

This doesn't have to be slow

A common reason teams skip structured prioritization altogether is the reasonable worry that it will slow a decision down. It doesn't have to. The value here isn't in exhaustive analysis, weeks of workshops and decks, it's in asking the same four questions and applying the same weighted criteria every time, so a fast decision is still a consistent one. A day session with the SWOT Cross and a back-of-envelope score on each axis beats a three-week deck that still ends in a gut call, because the one-day version can be repeated, defended, and revisited three months later to see whether the calls still hold. The discipline is in using the same lens every time, not in how long any single pass takes.

Run the same methodology again each quarter to check progress, flag roadblocks, and decide whether anything needs to shift. Again a one-day session, with key leaders preparing their inputs a day in advance.