Product management skill
Detect
Detect is what happens after launch: following through, then checking adoption and retention to see who tried it and who came back.
Launch and follow-through
Ask yourself: Think of your last release. Who knew it was coming, and what did you do in the week after?
- MissingSales, support and customers hear about changes once they're already live.
- TryingHeadline launches get organised. Everything else just goes out.
- DoingEach release has someone responsible, early notice for the people it affects and a check-in afterwards.
- OwningYou run launches for your area end to end, and the business is never caught out.
Adoption and retention
Ask yourself: For the last thing you shipped or finished, who used it, did they keep using it, and how do you know?
- MissingYou find out how things went only if someone tells you. Who used it, and whether they came back, isn't something you check.
- TryingYou look at usage when a launch is big or someone asks. The numbers usually come from someone else, and they rarely change what you do next.
- DoingBefore you ship, you decide what good adoption looks like. Afterwards you check who used it and who came back, and can show a recent example where that changed your next step.
- OwningAdoption is your number. You set the target, track it after every release, share what worked and what didn't, and decide what happens next because of it.
Practice questions
A feature launched last month. How do you know if it worked?
- Count how many tickets shipped
- Check adoption, retention and satisfaction against your targets
- Ask the team how they feel about it
Best answer: Check adoption, retention and satisfaction against your targets. Shipping isn't the finish line. TARS tells you whether people used it, came back and liked it.
Where are you on detect, and across all nine? Find your PM level in two minutes, free.
Check your level