Sort what you know about a decision into four buckets so the gaps become obvious.
Use when 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.
Avoid when 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.
Score competing work on reach, impact, confidence and effort so the argument is about evidence.
Use when 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.
Avoid when 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.