Comparing by fit
Two ways of thinking, side by side. There is no winner here — read across each row and choose the one that fits your situation.
Product
Score competing work on reach, impact, confidence and effort so the argument is about evidence.
By 6days
Strategy
Sort what you know about a decision into four buckets so the gaps become obvious.
By 6days
When to use — RICE Prioritisation
Use it when you have many comparable candidates competing for one team's capacity, when prioritisation has become political and you need a neutral vocabulary, or when you need to explain to stakeholders why their request did not make the cut without it being personal.
When to use — SWOT Analysis
Use it early, when a group needs to pool what it collectively knows before choosing a direction — entering a market, responding to a competitor, or opening annual planning. It is most valuable when the people in the room hold different pieces of the picture and have never assembled them in one place.
When not to use — RICE Prioritisation
Avoid it for work that is not discretionary — security fixes, legal obligations and keeping the service up do not get scored, they get done. It handles strategic bets badly: anything genuinely new scores low on confidence and reach by construction, so a team that follows RICE mechanically will optimise itself into small safe increments forever. It also cannot see dependencies or sequencing.
When not to use — SWOT Analysis
Avoid it when you need a decision rather than an inventory: SWOT ranks nothing and will not tell you what to do. It rewards confident assertion, so it degrades badly in rooms with a strong seniority gradient. And it is a snapshot — for anything fast-moving it dates quickly, and a stale SWOT presented as current is worse than none.
Every roadmap has more candidates than capacity, and the selection usually goes to whoever argues best — the loudest stakeholder, the most recent customer escalation, the executive's pet idea. The team cannot articulate why one item beat another, so the decision cannot be revisited when things change, and everyone suspects, often correctly, that the process is political rather than analytical.
A team knows a great deal about its own situation, but the knowledge is scattered across people and half-remembered conversations. When a decision arrives, discussion circles: someone raises a threat, someone counters with a strength, and nobody can tell whether the group has covered the ground or simply argued loudly. What is missing is not intelligence but a shared inventory.
RICE scores each candidate on four factors and combines them into a single number: reach (how many people it affects in a period), impact (how much it moves the thing you care about, per person), confidence (how much you trust your own reach and impact estimates) and effort (person-time to deliver). Multiply the first three, divide by effort. The output is deliberately crude. Its value is not the ranking but the conversation the scoring forces: confidence makes the team say out loud how much of the case is guesswork, and comparing two items usually reveals that a disagreement about priority was really a disagreement about an estimate.
SWOT sorts everything you know into four buckets along two axes: helpful versus harmful, and internal versus external. Strengths and weaknesses are things you control. Opportunities and threats come from outside and will happen whether or not you act. The value is less in the four lists than in what the sorting exposes — an empty quadrant usually means a blind spot rather than an absence, and a strength that maps onto no opportunity is a capability you are not using. Treat it as a structured inventory that sets up a decision, never as the decision itself.
Decide what 'impact' means before scoring anything — activation, retention, revenue, support load. Without one agreed metric, scores are not comparable and the whole exercise produces a number that means nothing.
Count how many users or events this touches per quarter, using real numbers wherever they exist. Reach is the factor most amenable to evidence, and grounding it prevents the whole score from floating free of reality.
Use a deliberately blunt scale — massive, high, medium, low, minimal — rather than pretending to precision you do not have. False precision here creates unearned confidence in the ranking.
Discount for how speculative your estimates are. This is the factor that does the real work: it stops a thrilling idea with no evidence from outranking a modest one with data, and it makes the team admit which is which.
Not specified
A two-by-two matrix. The horizontal axis runs from Internal on the left to External on the right; the vertical axis runs from Helpful at the top to Harmful at the bottom. Top-left: Strengths — Things you control that help you, Capabilities, assets, relationships. Top-right: Opportunities — Outside forces you could exploit, Openings in the market or moment. Bottom-left: Weaknesses — Things you control that hurt you, Gaps, constraints, liabilities. Bottom-right: Threats — Outside forces that could hurt you, Competitors, regulation, shifts.
Worked example — RICE Prioritisation
Two candidates. A bulk-export feature: reach 400 users/quarter, impact 1 (medium), confidence 80%, effort 2 person-months — score 160. A redesigned onboarding flow: reach 3,000 new signups/quarter, impact 2 (high), confidence 50% (the evidence is one small study), effort 6 — score 500. Onboarding wins by roughly three to one, which surprises the room because export is what customers ask for by name. The disagreement resolves to a single input: the sales lead thinks onboarding's confidence should be 20%, not 50%. At 20% the ranking flips. Now the team knows exactly what to go and find out, which the argument alone would never have produced.
Worked example — SWOT Analysis
A regional logistics firm considers opening a second depot. Strengths: dense driver network, 20-year customer relationships. Weaknesses: ageing fleet, no software team. Opportunities: a competitor has just exited the region. Threats: fuel costs, an incoming emissions rule. Crossing the quadrants does the real work — the driver network against the competitor's exit argues for moving now, while the ageing fleet against the emissions rule says the depot must not be funded by deferring fleet replacement. The four lists alone would have said neither.
The scoring model was developed and published by the team at Intercom in the mid-2010s to prioritise their own roadmap, and was shared openly rather than commercialised. It sits within a much older tradition of weighted scoring in project selection; its contribution is the specific inclusion of a confidence discount, which is what distinguishes it from earlier value-over-effort schemes.
SWOT emerged from corporate planning research in the United States around the 1960s, and is often associated with work done at Stanford Research Institute in that period. Attribution to any single author is disputed, and the framework has been reshaped by decades of practice since. It is best treated as a common inheritance of business planning rather than anyone's proprietary method.
Estimate total person-months across all functions, not just engineering. Compute the scores, then interrogate the ranking — where the number offends someone's intuition, find out which input they disagree with. That argument is the actual output.
Name precisely what you are analysing and over what period. 'Our company' is too broad to produce anything useful. 'Our position in the mid-market segment over the next eighteen months' gives every later item a test for relevance. Most weak SWOTs fail here, not later.
List strengths and weaknesses — the things within your control. Push for specifics with evidence attached. 'Strong brand' is a comfortable phrase that survives because nobody checks it; 'we win 60% of head-to-head deals against our closest competitor' can be argued with, which is what makes it useful.
List opportunities and threats — forces that exist independently of you: regulation, competitor moves, shifts in what customers expect, technology, cost of capital. The discipline is to record them as they are rather than as you would like them to be.
A quadrant with nothing in it is a signal about your attention, not about reality — teams under pressure routinely produce no weaknesses. A quadrant with thirty entries means you have not prioritised. Both are findings worth more than the lists themselves.
Pair items deliberately: which strength lets you take which opportunity? Which weakness leaves you exposed to which threat? This is where a SWOT stops being a list and starts producing candidate actions. Carry only the pairs into the decision, not the raw inventory.