Product Sense Interview Answer
Structure a product-sense interview answer—or real product decision—by narrowing users, stating a thesis, and defending an MVP with explicit tradeoffs.
Overview
Product Sense Interview Answer is an agent skill most often used in Validate (also Idea, Build pm) that walks through clarify-segment-thesis-MVP structure for product-sense questions and real scoping decisions.
Install
npx skills add https://github.com/deanpeters/product-manager-skills --skill product-sense-interview-answerWhat is this skill?
- Worked example: "How would you improve YouTube?" with condensed clarify-to-MVP path
- Forces narrow target user and one pain instead of treating the product as undifferentiated
- Ecosystem segmentation (viewers, creators, advertisers) with explicit player and intent choices
- Thesis-driven rationale linking market competition to recommendation vs satisfaction tradeoffs
- MVP selection earned through stated tradeoffs rather than feature laundry lists
Adoption & trust: 648 installs on skills.sh; 5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You face a vague "improve X" question or your own broad product idea and cannot narrow users, pain, or a defensible MVP without sounding like a feature list.
Who is it for?
Indie builders and PM-curious founders who want a repeatable product-sense framework before coding or when practicing structured interviews.
Skip if: Teams that already have approved PRDs and prioritized backlogs and only need engineering execution prompts.
When should I use this skill?
When answering or practicing product-sense prompts such as "How would you improve [product]?" or when you need clarify-rationale-goal-segmentation-MVP structure for scoping.
What do I get? / Deliverables
You produce a segmented, thesis-backed answer with an explicit MVP choice and tradeoffs you can reuse in interviews or a validate-phase scope doc.
- Structured product-sense answer outline (clarify, rationale, goal, segments, MVP)
- Documented tradeoffs supporting the chosen MVP
- Reusable segmentation map of ecosystem players
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Validate scope is the primary shelf because the walkthrough forces clarify-rationale-goal-segmentation-MVP discipline before you commit engineering effort. Scope subphase fits structured problem framing (clarify, segment, prioritize one pain) whether you are interviewing or scoping your own indie product.
Where it fits
Pick viewers vs creators and a viewing-intent slice before you commit to a content-product direction.
Turn a broad "improve our app" idea into one pain, a product goal, and an MVP with explicit tradeoffs.
Align the eng agent on thesis and prioritized segment so implementation stories map to the chosen MVP.
How it compares
Interview-grade product framing—not a landing-page layout skill or a code-review checker.
Common Questions / FAQ
Who is product-sense-interview-answer for?
Solo builders, PM interview candidates, and founders who need a clear clarify-segment-MVP script for open-ended product improvement questions.
When should I use product-sense-interview-answer?
Use it in Validate (scope) when narrowing an MVP; in Idea (audience) when picking a user segment and thesis; and in Build (pm) when translating product goals into prioritized bets.
Is product-sense-interview-answer safe to install?
It is primarily narrative guidance with no declared tool permissions; still review the Security Audits panel on this Prism page before adding third-party skill packs.
SKILL.md
READMESKILL.md - Product Sense Interview Answer
# Example: Improve YouTube **Prompt:** "How would you improve YouTube?" ## Why this is a strong example This example works because it does not treat "YouTube" as one giant undifferentiated product. It narrows the target user, picks one pain point, and earns the final MVP choice through explicit tradeoffs. ## Condensed Walkthrough ### 1. Clarify - Scope the product to the core YouTube viewing experience rather than Shorts, Music, or TV. - Clarify whether the focus is viewers, creators, or advertisers. - If the interviewer does not answer, assume the full ecosystem is in scope but commit to prioritizing one player. ### 2. Rationale - Online video is a massive attention market with intense competition. - The deeper issue is not just watch time; it is whether users feel their time was well spent. - YouTube's unique advantage is the breadth of creator supply across learning, entertainment, and niche content. - Thesis: recommendation quality is optimized for engagement more than intentional satisfaction. ### 3. Product Goal Help viewers consistently find content they are glad they watched, so that YouTube becomes a platform people choose intentionally rather than habitually. ### 4. Segmentation **Ecosystem players:** - Viewers - Creators - Advertisers - Talent managers / networks - Moderation and trust teams **Chosen player:** viewers **Primary dimension:** viewing intent - Goal-directed learning - Entertainment browsing - Deep-dive research **Chosen segment:** goal-directed learners **Secondary dimension:** expertise level - Beginners - Intermediate - Advanced **Chosen segment:** beginners **Persona:** Priya is a 28-year-old marketing coordinator using YouTube to learn practical work skills quickly. She cares about finding trustworthy, well-structured content without wasting time in low-signal recommendation loops. ### 5. Pain Points **Journey stages:** - Search - Selection - In-session learning - Follow-through **Key pain points:** - No clear starting point for a topic - Quality is hard to judge before clicking - Too many similar-looking tutorials - Old content outranks better current content - Recommendations pull the user off task - No structured progression from one concept to the next - No record of learning progress **Top pain point:** no structured progression - **Frequency:** shows up in almost every learning session after the first video - **Severity:** blocks the job to be done because skill-building requires sequence, not random adjacent content ### 6. Solution **Option 1:** Learning Paths that sequence the best beginner videos into a guided curriculum. **Option 2:** Intent-Aware Recommendations that hold the session to the user's stated learning goal. **Option 3:** Key Moments Index that lets users jump directly to the concept they need inside each video. **Comparison:** - Learning Paths: **High user impact** - directly solves progression. **High effort** - ranking, sequencing, and new UI. - Intent-Aware Recommendations: **Medium user impact** - reduces distraction. **Medium effort** - recommendation-system changes. - Key Moments Index: **Medium user impact** - improves efficiency inside videos. **Medium effort** - transcript and chapter labeling work. **MVP winner:** Learning Paths **Core features:** - Topic-based path of 5-8 sequenced videos - Progress tracking across sessions - "Continue learning" re-entry point **v1 exclusions:** - No quizzes - No creator-submitted path editing **Closing line:** "I'd focus on beginner goal-directed learners, specifically around the pain of no structured progression, and build Learning Paths as the first bet." ## What to notice - The goal is an outcome, not a feature - The segment is narrow enough to matter - The pain point is a user friction, not a missing capability - The final MVP is chosen after comparison, not announced from intuition alone --- name: product-sense-interview-answer description: Structure a spoken PM product-sense answe