Favorite App: New Feature Design
Choose a consumer app you genuinely admire and propose two new features that would improve its value. Be specific enough that Product, Design, Engineering, and Data could align on a v1.
Constraints & Assumptions
-
Choose an app you know well and can discuss from both user and technical perspectives.
-
Propose two features with clear target personas, user journeys, feasibility, and metrics.
-
Keep v1 pragmatic; separate must-have launch scope from future extensions.
-
Address privacy, performance, platform constraints, and guardrails.
Clarifying Questions to Ask
-
Should I choose a consumer app, enterprise app, marketplace, social product, or media product?
-
Should the features optimize acquisition, activation, engagement, retention, monetization, or creator value?
-
How deep should I go on technical feasibility versus product strategy?
-
Are AI-powered features acceptable, or should I focus on non-AI product improvements?
Part 1 - App and Product Context
Name the app, explain why you admire it, and identify the user or business opportunity behind the two features.
What This Part Should Cover
-
The app's core job to be done and why it succeeds today.
-
The user segments and pain points the proposed features address.
-
Why these features fit the product's strategy and current user behavior.
Part 2 - Feature 1
Describe the first new feature.
What This Part Should Cover
-
Target persona, end-to-end journey, v1 scope, and explicit exclusions.
-
Backend services, data flow, storage, APIs, client constraints, and privacy considerations.
-
Primary metric, secondary metrics, guardrails, and validation plan.
Part 3 - Feature 2
Describe the second new feature.
What This Part Should Cover
-
Target persona, end-to-end journey, v1 scope, and explicit exclusions.
-
Technical feasibility across backend components, data pipelines, mobile or web constraints, and content or safety requirements.
-
Metrics, experiment design, rollout, and risk mitigation.
Part 4 - Prioritization and Rollout
Compare the two features and recommend which to ship first.
What This Part Should Cover
-
Impact, confidence, effort, dependencies, and risk.
-
Launch sequencing, A/B testing, phased rollout, and operational readiness.
-
How to learn quickly without harming existing users.
What a Strong Answer Covers
-
Feature ideas grounded in real user needs rather than novelty.
-
Practical technical feasibility and platform constraints.
-
Metrics and guardrails that reveal whether the features create durable value.
-
A clear prioritization decision.
Follow-up Questions
-
Which feature would you build first and why?
-
What would make you kill the feature after launch?
-
What user segment might be harmed or annoyed by the feature?
-
How would you reduce privacy risk?
-
What engineering dependency is most likely to delay v1?