Product Thinking Models

PEST, SWOT, AARRR, KANO, the Five Elements of UX—when to reach for which.

PEST, SWOT, AARRR, KANO, the Five Elements of UX—when do you reach for which? None of these models will hand you the answer. Their value is as a checklist, forcing you to fill in the side you hadn't considered.

The classic symptom of empty use: you fill in the four SWOT boxes and call it done. Nothing changes, no one looks at it twice. There's only one test for whether a model earned its keep this time—after using it, did your decision change? swot-wiki

Index them by stage, not by fame: reach for PEST and SWOT during research, KANO when ranking requirements, the Five Elements when debugging the experience, and AARRR when working on growth. Below we unpack the four most-used.

PEST and SWOT: the outside and yourself

PEST is a four-box scan of the outside world: Political, Economic, Social, Technological. Before committing to a direction, sweep the environment once so you don't put effort into an industry that's about to ebb. SWOT stitches the outside and yourself together: strengths and weaknesses inside, opportunities and threats outside. Its real value isn't how full the four boxes are—it's the cross-check of "do our strengths line up with the opportunities." If they don't, you're applying your strengths in the wrong place. Don't turn SWOT into a summary; turn it into a decision input. When the boxes are full, you must be able to answer "so what am I going to do." On timing: PEST fits a quarterly sweep of the environment, SWOT fits the moment before a major decision—not as wall decoration. Both fail when filled in for the sake of it; if no action follows, better not to fill them at all.

KANO: ranking needs

Sort needs into five categories: basic needs (their absence makes users angry, but their presence doesn't add satisfaction—login, payment), performance needs (the more, the better—search accuracy, loading speed), excitement needs (nobody expects them, but their presence delights—a small clever touch in a new feature), indifferent needs (no difference either way), and reverse needs (their presence actually hurts). KANO answers the question "if I add this feature, will users be more satisfied?"—fill the basic gaps first, then work on performance, and treat excitement features as surprises, not the daily menu. Among your pending requirements, missing one basic need is an incident, while missing an excitement feature goes unnoticed. That's the ranking. kano-wiki

The Five Elements of UX

Five layers from abstract to concrete: strategy (why), scope (what), structure (how information is organized), skeleton (how pages are laid out), and surface (what it looks like). Its biggest use is as a reminder: when something is wrong, look one layer up before endlessly reworking the surface. If you've changed the button three times and users still can't find it, the problem is probably not the button—it's the information architecture one layer down. If three rounds of recoloring change nothing, go back and ask whether the scope itself is wrong. Design flows top-down; debugging flows bottom-up.

AARRR

Acquisition, Activation, Retention, Revenue, Referral. It splits the user's full path—from arrival to departure—into five stages, to pinpoint exactly where they get stuck. Rising activation with falling retention, and a weak acquisition channel, are two completely different diseases. Don't prescribe one medicine for both. AARRR has a second use: picking metrics. Choose one core number per stage, and the whole team can agree on where the problem is now, instead of each person staring at their own dashboard. aarrr-wiki