Hand on your heart, are you doing as much product discovery as you should?

If there's a gap, you're not alone. I've worked with teams skipping product discovery because they "don't need it" or "don't have time for it" since their backlog is already full of things the business asked for, the users, or tech debt. I've worked with PMs who want to do discovery "right" and therefor never get started, and I've seen seasoned PMs using the same tools and methods who could use a little inspo to generate new ideas.

I've organized 40+ tools and frameworks by validation type: understanding the problem, testing value and usability, confirming technical feasibility, checking business viability, and prioritizing what comes next. Start with your question, find the category and pick a tool and try it out!

UNDERSTANDING THE PROBLEM

(What's the problem we are trying to solve?)

• Jobs to be Done (JTBD) - understand customer motivations and the context around their goals
• Impact Mapping - connect features to business outcomes and strategic goals
• Opportunity Solution Tree (Teresa Torres) - visually map customer opportunities to desired outcomes
• Wardley Mapping - understand technology evolution and strategic positioning in your market
• Assumption Mapping - identify and rank the riskiest assumptions your team is making
• Problem Interviews - uncover real customer pain through structured conversations
• Experience Mapping - map the current customer journey including emotions and pain points
• 5 Whys - repeatedly ask "why" to dig deeper and find root causes
• BAPO (Business → Architecture → People → Organisation) - align business goals with technical architecture and organizational design

VALIDATING VALUE & USABILITY

(Will customers buy/use it? Can they figure out how to use it?)

Feedback Artifacts:

• Prototypes (low to high fidelity) - simulate the solution to gather user feedback
  • Paper prototypes - hand-drawn sketches for ultra-fast, low-cost testing
  • Clickable prototypes - interactive mockups built in tools like Figma, v0.dev, or Lovable
• Landing pages / Smoke tests - gauge customer interest before building anything
• Concierge MVP - manually deliver the service to validate demand and learn requirements
• Pre-orders / Waitlist - test willingness to pay by asking for commitment

User Feedback Methods:

• Usability testing with prototypes - watch users attempt tasks to identify confusion and friction
• A/B tests (for existing products) - compare two versions with real users to measure impact
• Design sprints - 5-day structured process from problem definition to tested prototype
• Continuous interviewing - weekly customer conversations to stay connected to their reality
• Surveys (with prototypes) - gather quantitative feedback on concepts or designs
• Card sorting - understand how users mentally organize and categorize information
• Beta programs - limited release to early users for real-world feedback
• Customer advisory boards - ongoing structured feedback from key customers

VALIDATING FEASIBILITY

(Can we build it?)

Technical Validation:

• Proof of Concept (POC) - build something minimal to test technical viability
• Technology spike - time-boxed technical research to reduce uncertainty
• Performance testing - validate the system can handle expected load and scale
• Data modeling - design the database structure and validate it supports required features
• API contract testing - define and test API agreements before full implementation
• Technical feasibility matrix - score features by technical complexity versus value
• Dependency mapping - identify what needs to be built or exist first
• Architecture diagrams (i.e. C4 model in Mermaid, Excalidraw, paper) - visualize system structure and component relationships
• Request for Comments (RFC) - written technical proposal shared with team for feedback and alignment

VALIDATING BUSINESS VIABILITY

(Does it work for our business?)

Understanding Impact - Models:

• Cost of Delay (CoD) - quantify the economic impact of delaying this work
• Opportunity cost analysis - quantify what other work you can't do if you do this
• Weighted Shortest Job First (WSJF) - prioritization formula: Cost of Delay ÷ Job Duration
• Revenue projections - estimate expected business impact (can use non-monetary units like users, retention, etc.)

Strategic Validation:

• Competitive analysis - understand alternative solutions and how you can differentiate
• Porter's Five Forces - assess market attractiveness and competitive intensity
• SWOT analysis - analyze internal Strengths/Weaknesses and external Opportunities/Threats
• Legal/compliance review - validate you can legally do this in target markets
• Stakeholder interviews - confirm internal teams will support and adopt this
• Go-to-market feasibility - validate sales and marketing can successfully execute
• Partner validation - confirm required partners and vendors will support this approach

PRIORITIZATION & DECISION MODELS

Scoring/Ranking:

• RICE (Reach, Impact, Confidence, Effort) - scoring framework
• ICE (Impact, Confidence, Ease) - simpler scoring framework
• Impact vs Effort matrix - 2×2 visual prioritization matrix
• Kano Model - categorize features as must-haves, performance features, or delighters
• MoSCoW (Must, Should, Could, Won't) - simple bucketing method for requirements
• Weighted scoring - define custom criteria and weights specific to your context

​
​