7d • General discussion
2 kinds of product decisions
There are two kinds of product decisions. Ones that are correct and ones that get adopted. The best teams know those aren’t the same thing and plan for both.
The Correct Decision answers: does this solve a real problem? Is the UX sound? Does it ship on time?
The Adopted Decision answers: does this fit inside how users already think and move? Is the behavior change we’re asking for smaller than the value we’re delivering? Would someone who’s half-paying attention still get it?
Most product processes are very good at the first one. Almost none of them formally account for the second.
A quick check I run before anything ships:
1. What does the user do today, step by step?
2. Which of those steps does the new thing replace?
3. How many new decisions does it introduce that didn’t exist before?
4. Is the value obvious before the user has learned the new behavior, or only after?
If the answer to #4 is “only after,” you have a retention problem waiting to happen, not an adoption problem.
0
0 comments
2 kinds of product decisions
powered by
skool.com/stef-the-pm-3369
Break into PM or level up in it. Community and courses built for where you actually are in your product career. Free to join.
Suggested communities
Powered by