User
Write something
This weeks case study: build a dashboard for a GTM SaaS
You’ve just been asked to build a new dashboard for a GTM SaaS tool. Sales, marketing, and CS all want visibility, and leadership wants one view that tells the whole revenue story. Constraints: You get one dashboard. Get the metrics right before people start building habits around it (good or bad). Discussion prompts: 1. What 3 to 5 metrics make the cut, and why those over the dozen other things people will ask for? 2. Who’s the primary audience? Does the answer change if it’s built for the CRO vs. a frontline AE? 3. What’s one metric you’d deliberately leave off, even knowing someone will push back on that?
📋 This Week’s Case Study: The Roadmap Nobody Agrees On
The Scenario: You’re 6 weeks into a new PM role. Three requests are competing for next sprint: - Sales wants a bulk export feature. Two enterprise deals are “blocked” on it (per your AE). - Support wants a fix for a permissions bug. It’s generating repeat tickets but no churn yet. - Your eng lead wants to pay down tech debt in the same area both features touch. You have capacity for one. Everyone thinks their thing is obviously the priority. The Prompt: Walk through how you’d actually decide. Not just which one you’d pick, but how you’d get three stakeholders to trust the call, especially six weeks in when you don’t have credibility built up yet.
0
0
📋 This Week’s Case Study: The Roadmap Nobody Agrees On
📋 This Week’s Case Study: The Complaint Everyone’s Ignoring
The Scenario: You’re the PM for a project management tool used by small agencies. Over the past three weeks, support tickets mentioning “can’t find my old files” have quadrupled. Nobody flagged it as urgent because each ticket gets resolved individually (a support rep manually helps the user search). Churn hasn’t moved. NPS hasn’t moved. But your Head of Support pulls you aside and says “something’s off, I just can’t prove it yet.” The Prompt: What do you do in your first week with this signal? Walk through how you’d investigate it, what you’d look for, and what “worth building something” would actually look like versus “not yet.” How to Approach It: 1. Clarify the signal. What’s actually being reported? Don’t assume “search is broken.” Find the pattern underneath the pattern. 2. Size it. A quadrupling of a small number can still be a small number. What would make this matter? 3. Decide, don’t default. Not every spike needs a roadmap slot. What’s the smallest next step that tells you more? What a Strong Reply Includes: - A guess at what you’d actually go look at first (tickets, session recordings, a specific report) - One hypothesis for what’s really going on, not five - One honest answer to “and if it turns out to be nothing?”
0
0
This week’s challenge: DAUs are flat. New signups aren’t the problem.
Scenario: you’re the PM for a habit-based learning app (think Duolingo). Signups are growing steadily month over month. Daily active users have been flat for two quarters. Leadership wants a fix, fast. Three ways to approach it: A. Ship a bigger streak/reward system. Gamification drives daily habits, so double down on what already works B. Dig into the data first. Segment new users from existing ones, find exactly where the drop-off happens before proposing anything. C. Talk to users. Run a handful of interviews with people who signed up and stopped opening the app, find out why in their own words. Drop your pick and your reasoning below. No wrong answers
Poll
Cast your vote
0
0
PM Case study: You just joined as the PM on a habit-tracking app.
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.
0
0
PM Case study: You just joined as the PM on a habit-tracking app.
1-14 of 14
powered by
Stef The PM
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.
Build your own community
Bring people together around your passion and get paid.
Powered by