Product Sense Quiz

Needs Improvement 🧯

Your choices suggest you may be optimizing for the loudest signal (stakeholder pressure, surface-level appeal, or “feels right” reasoning) rather than for user value and measurable outcomes.

Don’t worry—this quiz is intentionally tricky. The good news is that with a more disciplined decision process (evidence first, clear success metrics, and explicit tradeoffs), your product judgment can improve quickly.

• Prioritization: Try anchoring on impact to the largest user pain first, not internal preference or “most features.”
• Onboarding & research: Move from vague feedback to observation and funnel/drop-off analysis, then prototype and test.
• Tradeoffs: Use “smallest version that validates value” when uncertainty is high, and avoid waiting for perfect certainty.
• Metrics interpretation: When conversion rises but retention drops, investigate expectation mismatch or intent quality before declaring success or failure.

Getting There 👍

You’re showing some product instincts—especially around connecting decisions to user outcomes—but your reasoning sometimes skips the hardest step: interpreting signals correctly and prioritizing the highest-leverage work.

This level looks like you can choose the “right direction” occasionally, yet you may still rely on incomplete evidence or under-specify what success actually means.

• Prioritization: Compare options using impact, confidence, effort, and alignment—don’t let effort alone or feature count drive the call.
• Workflow & architecture: When balancing MVP vs. richer workflows, define the core user problem and set boundaries for what can expand later.
• Customer-specific requests: Discuss alternatives and look for patterns that serve broader use cases before overbuilding for a single account.
• Decision under constraints: Make a reversible bet with success metrics and a learning plan instead of waiting for certainty.

Good Judgment 👏

Your decisions generally reflect solid product sense: you consider users, metrics, and tradeoffs rather than treating every request as equally urgent or equally solvable.

At this level, the main gap is consistency—pushing your reasoning further into “why this metric, why now, and what would change your mind?”

• Evidence & ambiguity: When users can’t explain needs, observe behavior and translate it into a job-to-be-done, then prototype multiple solution paths.
• Metric tradeoffs: If downstream retention drops, treat it as a hypothesis to test (expectations, intent mismatch, lifecycle fit), not as noise.
• Roadmap selection: Use structured comparison (impact/confidence/effort/alignment) rather than speed alone or internal advocacy.
• Engineering constraints: Choose the smallest version that validates user value, while planning intentional expansion points.

Excellent 🏆

Your answers consistently demonstrate strong product judgment: you prioritize user value with evidence, interpret metrics in context, and handle tradeoffs with clarity rather than fear.

You also show the ability to make high-stakes decisions under uncertainty by designing learning loops—shipping reversible bets, defining success criteria, and iterating based on what the data reveals.

• Prioritization: You pick work that targets the highest-frequency pain and the biggest user impact, not the loudest voice or the easiest task.
• Research translation: You move from “vague feedback” to observation, funnel analysis, and prototyping—turning ambiguity into testable hypotheses.
• Tradeoff framing: You choose MVP boundaries thoughtfully and resist overbuilding while still respecting long-term extensibility.
• Metric reasoning: You investigate causal explanations when metrics conflict (conversion vs. retention) and avoid simplistic conclusions.

Challenge for next level: Keep sharpening your ability to articulate assumptions explicitly—what you believe is true, how you’ll test it, and what outcome would force a change in direction.