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.
Strip a problem back to what must be true, then rebuild — instead of copying what exists.
Use when Use it when an industry's costs or practices have been stable for a long time without obvious justification, when you are entering a field as an outsider and lack the incumbents' assumptions, or when repeated incremental attempts have all failed and the problem may be framed wrongly.
Avoid when Avoid it for routine decisions — it is slow, effortful, and analogy is right most of the time. It is also a common vehicle for arrogance: reasoning from first principles while lacking domain knowledge tends to rediscover why the convention exists, expensively. If experts cannot explain why a practice exists, that is worth investigating; if they can, listen.