Product sense (58)
- Improve activation for a new personal finance app
- Design a product for new parents returning to work
- Design a product to prepare for a citizenship test
- Improve content discovery for a streaming service
- Build trust signals for first-time marketplace buyers
- Diagnose day-1 churn in a meditation app
- Order frequency drops in week 4 for grocery delivery
- Design a product for small landlords screening tenants
- Onboard switchers from a competitor
- Should a fitness app remove its free tier?
- Telehealth scheduling drop-off
- Design a college-application companion for high schoolers
- Reduce no-shows for at-home services
- Design a product for nurses changing hospitals
- Design a product for households tracking shared finances
- Design invoicing for freelancers
- Design a tool for renters disputing repairs
- Design investor updates for solo founders
- Help retirees stay socially connected
- Design for first-generation college applicants
- Recovery tracking for amateur athletes
- Bookkeeping for owner-operators
- Coordinate childcare across households
- Onboarding for prosumer creators
- Design a climate impact tracker for households
- Design financial literacy for teens
- Cut cart abandonment on luxury e-commerce
- Improve creator-to-fan response rates
- Reduce time-to-first-deploy for a dev tool
- Search relevance for a niche video catalog
- Reduce ticket re-opens on a B2B product
- Lift trial-to-paid for a productivity SaaS
- Improve listing quality on a peer-to-peer rental
- Lift review-completion on a hospitality marketplace
- Diagnose drop-off at 'import contacts'
- Diagnose week-2 churn for habit tracking
- SMB churn on a B2B product
- Identity-verification drop-off
- Country-specific checkout drop
- Drop-off on slow networks
- Wedge segment for a calendar product
- Underserved segment for an LMS
- Underserved segment for code review
- Two segments, one roadmap
- Pick the next country for a fintech
- Bootstrap supply on a niche labor marketplace
- Reduce off-platform leakage on a freelance marketplace
- Match quality on a tutoring marketplace
- Address fraudulent listings on a peer-to-peer rental
- Make a banking app usable for low-vision users
- Onboard users with limited tech literacy
- Adapt for low-bandwidth regions
- Design an AI-native travel planner
- AI tutor for adult language learners
- AI-native CRM for solo founders
- Add AI to meal planning without breaking trust
- Add paid plans to a free-only consumer app
- Ads vs. subscription for a content product
Execution (78)
- Choose metrics for a creator marketplace
- Diagnose a 12-point activation drop
- North Star for a B2B collaboration tool
- North Star for a music free tier
- A/B test a checkout redesign
- Conversion up, session length down
- Onboarding completion vs. day-7 retention
- Two segments, opposite signals
- Engagement drops a week after launch
- Retention up, ARPU down
- Input metrics for a creator's first 14 days
- Power and runtime for an A/B test
- Drop-off at 'add payment'
- North Star for a podcast platform
- North Star for a job-search product
- North Star for a clinic EHR
- North Star for a school-district product
- Rewriting a North Star at year five
- Input metrics for trial-to-paid
- Input metrics for week-1 retention
- Input metrics for content quality
- Input metrics for marketplace liquidity
- Pricing-page bounce
- Sign-up → first action funnel
- Drop-off at 'invite teammates'
- First A/B test on a small product
- Segment a small experiment
- Decide significance with a weak signal
- Long-running test got bumped
- Multi-cell test with four variants
- Interpreting a flat A/B
- Opposite-direction segments
- Primary up, guardrail down
- Suspecting a seasonality artifact
- Choose a minimum detectable effect
- Pre/post launch causal claim
- Diff-in-diff for a regional rollout
- Read a 4-week retention curve
- Paid vs. organic cohort divergence
- Define and track power users
- Search speed vs. result accuracy
- Engagement vs. wellbeing
- Short-term vs. long-term metrics
- Paid conversion vs. trust
- DAU jumped 8%, suspicious
- Paid traffic conversion fell
- Search CTR dropped
- Premium plan churn spiked
- Weekly business review for an app
- Exec dashboard for an AI product
- Operational dashboard for a marketplace
- Anomaly alerts for sign-ups
- Multi-touch attribution debate
- Pick the first events to instrument
- Find usage clusters in the data
- Daily ride volume in a mid-size city
- Streaming revenue in a country
- Prioritize 5 roadmap items
- Search query volume in a region
- Bug fixes vs. features in a 2-week sprint
- Storage cost for a cloud photo product
- Annual coffee consumption in NYC
- Gym memberships in a US state
- Daily Uber rides in San Francisco
- Annual flights from a major hub
- Holiday-day SMS volume
- Ad revenue per hour of TV
- Bandwidth cost of video calls
- Compute cost for an AI feature
- Database read volume for a social feed
- Three customers, one ask
- Tech debt vs. launch deadline
- Board member overrides your roadmap
- Three squads, shared dependency
- Pick the next quarter for an early-stage team
- Trim a 10-item backlog to 3
- Effort for a new analytics dashboard
- Effort for a multi-region launch
AI judgment (27)
- Design evals for an AI support assistant
- Eval framework for an AI code-review assistant
- When is human-in-the-loop required?
- Recovering from a viral bad answer
- Latency vs. cost vs. quality on AI chat
- Fallback when the model is uncertain
- Should a startup fine-tune on customer data?
- A new jailbreak goes viral
- Launch criteria for an AI sales assistant
- Evals for an AI K-12 math tutor
- Third-party model vs. self-host
- Eval framework for an AI search product
- Evaluate AI-generated UI components
- First-time-user trust for AI
- Fallback for AI image generation
- Undo for an AI agent action
- Smart routing between AI models
- Caching strategy for an AI assistant
- Lower quality to hit a cost bar
- Hallucinations in a legal AI
- Signal uncertainty to the user
- Label vs. watermark AI output
- Use synthetic data to train
- Design a beta for an AI feature
- Sunset an old AI model version
- Edge cases in AI moderation
- Onboard users to an AI feature
Behavioral (39)
- Tell me about a disagreement with engineering
- Influence without authority
- Biggest failure as a PM
- A time data changed your mind
- Prioritizing a roadmap with too many asks
- Conflict with a senior leader
- Pushed back on an executive request
- A hard deadline you missed
- Coached a struggling teammate
- Most measurable impact
- Raising an ethical concern
- Built consensus across three disagreeing teams
- Convinced engineering on a controversial direction
- Took ownership in ambiguity
- Drove a cross-functional plan with no mandate
- Held direction through shifting priorities
- Conflict with a co-PM on overlapping scope
- Disagreement with a designer on UX direction
- Pushed back on a legal or compliance ask
- Disputed an engineering estimate
- Disagreement with a peer PM on prioritization
- Worked with a passive-aggressive teammate
- A launch that failed
- A hire that did not work out
- A decision you reversed publicly
- Talked directly to a frustrated customer
- Built for a niche segment over loud asks
- Killed a feature based on user research
- Said no to a customer ask
- Worked through a re-org
- Ramped into a new team fast
- Took over a legacy product
- Partnered with sales or marketing
- Communicated bad news to leadership
- Wrote a strategy doc that landed
- Gave a presentation that did not land
- High-stakes call with limited data
- Time you over-invested
- Time you under-invested and regretted it
Strategy (25)
- Should a B2B SaaS product add an AI copilot?
- Build, buy, or partner: AI photo editor
- Pricing for a freemium developer tool
- Reposition against an upmarket competitor
- Bundle or charge separately for AI?
- Move down to SMB or stay enterprise?
- Pivot from feature to platform
- Cold-start strategy for a marketplace
- Moat for an AI-native note-taking app
- Acquire a community or build it
- Open-source a developer tool
- Build a platform from a single feature
- Sequence international expansion
- Vertical-specific product variant
- Unbundle a feature into a separate product
- Loyalty program for a SaaS
- Monetize a free distribution channel
- Build an ecosystem
- Defend against an open-source clone
- Pivot product positioning
- Disrupt an entrenched incumbent
- PLG vs sales-led for a new product
- Move from prosumer to enterprise
- Manage a declining product line
- Distribution partnership trade-offs
Technical (23)
- Plan a partner API launch
- Postmortem you led
- Microservices vs. monolith for a small team
- Batch vs. streaming for a metrics product
- Rate limits for a public API
- Migrate to a new identity provider
- SLOs for a payments product
- Versioning a public API
- Communicate a breaking API change
- GraphQL vs REST for a partner API
- Internal-only API or partner-grade?
- Webhooks vs polling design
- Pagination semantics
- Re-platforming roadmap
- When to require a tech spec
- Quarterly tech-debt budget
- Cross-team architecture review
- Scope a 1-week spike
- Set an error budget
- Build a postmortem culture
- Capacity planning for a launch
- Privacy-aware analytics design
- Migrate off a vendor dependency