You just joined as the PM on a habit-tracking app. In week one, the data team flags something: people who signed up in the last two months are completing fewer habits by their second week than users did six months ago. Same onboarding. Same features. Something has slipped. Here's your context and constraints: - Signups are steady, so this isn't a top-of-funnel or marketing problem. - You get one small engineering fix this sprint. Not three. One. - Nobody on the team has talked to a churned user in months. This is the kind of open-ended question a real PM interview throws at you. There's no single right answer. The whole game is how you think. So: how would you figure out what's going on, and where would you start? Walk us through your approach in the comments. I'll post how a strong PM would structure it on Wednesday.

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.

In 2018, Snapchat shipped a major redesign. The logic was sound. Stories from friends were getting buried next to Stories from celebrities and brands. Discovery was a mess. They separated the two sides: left for people you know, right for media and publishers. Within weeks, a petition to revert it hit 1.2 million signatures. Kylie Jenner tweeted that she didn’t use Snapchat anymore and the stock dropped 6% in a day. Daily active user growth stalled for the first time. Snapchat’s CEO Evan Spiegel doubled down publicly. He said the confusion was the point. That it would take time. That the right call isn’t always the comfortable one. He wasn’t entirely wrong about the reasoning. He was wrong about the cost. ——————————————— Here’s your case challenge this week: You’re the PM on this project the week after launch. The data is ugly. Leadership is split. Half the team thinks you just need to hold the line and let users adjust. Half thinks you ship a rollback immediately. What do you do? Option A: Hold. The redesign solves a real structural problem. User backlash at this scale is almost always loudest in week one. You give it 60 days and measure retention, not noise. Option B: Partial rollback. You revert the friend/media separation but keep the UX improvements underneath. Give users back the familiar structure while preserving the real gains. Option C: Full rollback, full reset. The scale of the reaction tells you something fundamental broke. You go back to what worked, study what users actually do, and redesign from their behaviour up instead of from principles down.