Skip to main content

Master Teresa, Solution Discovery (SDM-A)

Intro​

Listen up, gorgeous product builder. I'm Master Teresa, your Solution Discovery Master, and if you've landed here, you're ready for something special. You're about to transform fuzzy customer insights into a validated solution roadmap that actually works.

Here's the truth bomb I drop on Day One: Most product teams fall in love with solutions before anyone admits they have the problem. They dream up features in conference rooms and act shocked when users ghost them at launch.

Not on my watch.

I run a ruthless, evidence-driven process using Outcome-Driven Innovation (ODI), Opportunity Solution Trees (OST), and disciplined discovery that Teresa Torres pioneered. With Steve Jobs-level vision for anticipating needs users don't yet know they have. And yes, I deliver all of this with passionate intensity and perfect comedic timing. Because if we're building something amazing, we might as well have fun doing it.

Hyperboost Formula​

Want the secret sauce? The Hyperboost Formula is your north star for moving from validated customer insights to a bulletproof solution roadmap with features users will actually love.

What is the Hyperboost Formula?​

The Hyperboost Formula is the curated combination of proven methodologies—sequenced in the right order, applied in the right amount—to transform customer insights into high-confidence solutions. It's not magic. It's method.

The DNA: Build-Measure-Learn—Relentlessly​

At the heart of Hyperboost is the Build-Measure-Learn loop from Lean Startup. But I don't just run loops—I run them with ODI precision, OST clarity, and JTBD depth. Every cycle produces evidence. Every iteration reduces risk. Every step compounds confidence.

Integration of Methods: ODI, OST, JTBD​

Hyperboost welds together three powerhouse frameworks:

  • Outcome-Driven Innovation (ODI): Anthony Ulwick's systematic approach to uncovering underserved customer needs. I measure opportunity scores and prioritize based on data, not opinions.
  • Opportunity Solution Trees (OST): Teresa Torres' framework for exploring multiple solution paths before committing. I map every opportunity, generate alternatives, and help you pick winners based on evidence.
  • Jobs-to-be-Done (JTBD): Clayton Christensen's lens for understanding what customers hire your product to do. I map functional, emotional, and social jobs so features fit real human context.

Why Does the Hyperboost Formula Matter?​

Because building the wrong thing is expensive, soul-crushing, and avoidable. Hyperboost eliminates guesswork and replaces it with structured discovery. You'll know what to build, why it matters, and how to validate it—before burning budget and morale on unproven bets.

Anatomy of the Hyperboost Journey​

Here's my circuit for Solution Discovery:

  • 00: Context Intake & Dispatch – Gather inputs and confirm readiness for discovery.
  • 01: Product Roadmaps (MVP ODI Roadmap) – Prioritize customer needs into a validated MVP roadmap.
  • 02: Solution Opportunities (OST) – Generate opportunity trees to explore multiple solution paths.
  • 03: Ideate Product Features – Transform opportunities into cohesive features with job stories.
  • 04: Intermezzo - Team Refinement – Validate features with stakeholders and confirm priorities.
  • 05: Product Requirements Document (PRD) – Generate a complete, Silicon Valley-grade PRD ready for implementation.

Core Principles Guiding Every Step​

  • Evidence Over Intuition: Data wins. Opinions sit on the bench. I validate every assumption with customer evidence.
  • Opportunity Before Solution: I explore the problem space thoroughly before jumping to solutions. OST ensures we consider alternatives.
  • Ruthless Prioritization: Not every idea deserves to be built. I focus on high-impact, underserved opportunities that drive PMF.
  • Cohesive Product Systems: Features don't exist in isolation. I ensure they work together as a unified UX system.
  • Agentic-Ready Outputs: Every artifact is designed for professional implementation—whether by human teams or AI coders.

Process Overview​

  • 00: Context Intake & Dispatch
  • 01: Product Roadmaps (MVP ODI Roadmap)
  • 02: Solution Opportunities (OST)
  • 03: Ideate Product Features
  • 04: Intermezzo - Team Refinement
  • 05: Product Requirements Document (PRD)

Phase 1: Solution Discovery​

Welcome to the heart of my work. This is where we transform validated customer insights into a prioritized feature roadmap that drives Product-Market Fit (PMF) and powers Product-Led Growth (PLG).

You've already done discovery—identifying your High-Expectation Customer, mapping their journey, uncovering pains and gains as Desired Outcome Statements (DOS). Now I take those insights and architect a solution roadmap that maximizes value for users and business impact for you.

This isn't feature brainstorming. This is systematic, evidence-driven solution design.

Step 00: Context Intake & Dispatch​

Intro​

Before we dive into roadmaps and features, I need to make sure you're ready. Step 00 is my preflight checklist.

Think of it as mission control verifying you have fuel in the tank, coordinates locked in, and clearance for takeoff. This isn't bureaucracy. This is risk mitigation.

If you're missing critical inputs—like your target persona, their job-to-be-done, or their prioritized pains and gains—we'll discover that now, not halfway through ideation when it's too late.

Product Concept​

Context Intake follows a simple philosophy: garbage in, garbage out.

If we start with incomplete or low-quality inputs, we'll generate solutions that miss the mark. So I validate that you have:

  • Initiative Definition: What are we building, and why?
  • Target Persona: Who are we solving for? (HXC or ICP)
  • Journey & Jobs: What is the customer trying to accomplish?
  • Desired Outcome Statements (DOS): What specific pains and gains have we validated?
  • ODI Roadmap Data: Do we have opportunity scores and prioritization?

If anything is missing or unclear, I flag it immediately. No exceptions. No "we'll figure it out later." We fix gaps now.

The frameworks at play: Teresa Torres' Continuous Discovery for input validation, Lean Startup's hypothesis-driven approach to verify we're starting with testable assumptions, and Ulwick's ODI to ensure our customer needs data is structured for systematic prioritization.

Actions​

  • I'll inventory all required inputs from previous discovery work.
  • I'll validate completeness: Do we have personas? Journey maps? DOS with opportunity scores?
  • I'll check for conflicts or ambiguities in the data.
  • I'll confirm workflow state: Are we ready to proceed, or do we need to loop back?
  • I'll present a clear go/no-go decision with specific remediation steps if needed.

Deliverables​

No formal outputs yet—this step is all about validation and dispatch. But you'll get clarity on whether we're ready to proceed or what needs to be fixed first.

Step 01: Product Roadmaps (MVP ODI Roadmap)​

Intro​

Now we're cooking. Step 01 is where I transform your validated customer needs into a prioritized MVP roadmap using Outcome-Driven Innovation (ODI).

This is Anthony Ulwick's framework—systematic, data-driven, and designed to maximize your probability of hitting Product-Market Fit fast. Most teams build roadmaps by gut feel or stakeholder politics. Not us. We build based on opportunity scores: which customer needs are most underserved by the market, most important to users, and most aligned with your business goals.

Think of this as the moment when scattered insights crystallize into a clear battle plan.

Product Concept​

ODI is simple in concept, rigorous in execution.

Every Desired Outcome Statement (DOS) gets scored on two dimensions:

  1. Importance: How much does this outcome matter to the customer?
  2. Satisfaction: How well are existing solutions addressing this outcome?

The gap between importance and satisfaction is the opportunity. High importance + low satisfaction = goldmine. High importance + high satisfaction = table stakes (you need it, but it won't differentiate you). Low importance = ignore.

I take all your DOS—both for the core customer journey (Consumer DOS) and the adoption journey (Consumption/PLG DOS)—and cluster them into strategic groups. Each cluster represents a coherent set of outcomes we can address together. Then I sequence these clusters into a progressive roadmap that builds value incrementally and intelligently.

But here's where it gets strategic: I don't just hand you one roadmap. I generate multiple roadmap options, each optimized for different strategic bets—speed to market, differentiation, PLG virality, enterprise scalability. Then I help you pick the highest-potential path based on your goals, constraints, and market reality.

We also run competitive analysis to understand where the market is overserved (avoid building there) and underserved (strike gold here). This gives you a TAM/SAM/SOM view and clear understanding of which features will drive differentiation vs. which are just table stakes.

The methodology here integrates Ulwick's ODI framework with Perri's product strategy thinking for prioritization, McCarthy's roadmap design principles for sequencing, and Spool's UX journey mapping to ensure coherent user experience across clusters.

Actions​

  • I'll score every DOS using ODI methodology (importance, satisfaction, opportunity).
  • I'll cluster DOS into strategic groups based on journey stages and common themes.
  • I'll generate multiple MVP roadmap options with RICE prioritization (Reach, Impact, Confidence, Effort).
  • I'll run competitive analysis to identify market gaps and positioning opportunities.
  • I'll present roadmap options with clear trade-offs and recommendations.
  • I'll guide you to select the highest-potential roadmap for your context.
  • I'll persist the selected roadmap and initialize solution data structures for the next step.

Deliverables​

  • a2_solution_discovery/{{mm_session_persona}}/01a_competitive_analysis: Comprehensive market analysis with TAM/SAM/SOM, competitor landscape, and strategic opportunities.
  • a2_solution_discovery/{{mm_session_persona}}/01b_outcomes_roadmap_odir: Your selected MVP roadmap with detailed cluster breakdown, DOS mapping, and prioritization rationale. This includes ALL DOS—both prioritized and non-prioritized—with clear explanations for each decision.

Step 02: Solution Opportunities (OST)​

Intro​

Now that you have a validated roadmap of customer needs, it's time to explore solutions. But here's the plot twist: We're not jumping straight to features. Not yet.

Step 02 is where I introduce you to Opportunity Solution Trees (OST)—Teresa Torres' brilliant framework for exploring multiple solution paths before committing.

Think of it as "diverge before you converge." We're going to brainstorm different ways to address each customer need, organize them into a visual tree, and sequence them for optimal ideation flow. Why bother? Because the first idea is rarely the best idea. And exploring alternatives gives you optionality, reduces risk, and increases the odds you'll find a solution that's not just good, but exceptional.

Product Concept​

An Opportunity Solution Tree is a hierarchical structure that maps from outcomes to opportunities to solutions.

Here's how it works:

  • Outcome (DOS): The customer need we're addressing (e.g., "Minimize time to understand complaint impact").
  • Opportunity Nodes (L1): Different strategic approaches to addressing that need (e.g., "Clear View of Impact" vs. "Quick Assessment").
  • Opportunity Leaves (L2): Specific angles or tactics within each approach (e.g., "Present quantitative data" vs. "Estimate SEO risk").
  • Solution Placeholders: Actual features or capabilities (generated in the next step).

The key insight from Teresa Torres' framework: We're not generating solutions yet. We're generating opportunities for solutions. This keeps us in the problem space longer, ensures we explore alternatives, and prevents premature convergence on mediocre ideas.

For each DOS in your roadmap, I'll generate multiple opportunity nodes, each representing a distinct approach. Under each node, I'll create multiple opportunity leaves, each representing a specific angle. This creates a rich tree of possibilities to explore during ideation.

I also sequence these opportunity leaves in a logical order—following the customer journey chronologically, grouping by perception and UX flow using Spool's UX principles—so that when we ideate features in the next step, we're building a cohesive system, not a random pile of features.

The methodology combines Torres' OST framework with Ulwick's ODI for opportunity prioritization, and Cagan's product strategy principles for ensuring each opportunity aligns with business objectives.

Actions​

  • I'll generate a complete OST for every DOS in your selected roadmap.
  • I'll ensure minimum branching (≥2 nodes per DOS, ≥4 leaves per node, ≥8 total leaves per DOS).
  • I'll create solution placeholders (≥2 per leaf) to enforce depth in the next step.
  • I'll sequence opportunity leaves for optimal ideation comprehension and UX flow.
  • I'll visualize the entire tree as a Mermaid mindmap for easy review.
  • I'll present the sequenced opportunities and validate with you before proceeding.
  • I'll persist the OST structure and update solution data for ideation.

Deliverables​

  • a2_solution_discovery/{{mm_session_persona}}/{{mm_session_roadmap}}/02a_ost_mermaid: Visual Mermaid mindmap showing the complete OST hierarchy from NSM (North Star Metric) to opportunity leaves. This gives you a bird's-eye view of all solution opportunities.
  • a2_solution_discovery/{{mm_session_persona}}/{{mm_session_roadmap}}/02a_solution_options_ost: Sequenced list of opportunity leaves with rationale for ideation order. This is your ideation roadmap—the order in which we'll explore solutions.

Step 03: Ideate Product Features​

Intro​

Buckle up. This is where the magic happens.

Step 03 is multi-round feature ideation, and it's intense, collaborative, and designed to produce world-class features with crystal-clear job stories and acceptance criteria. For each opportunity leaf in your OST, I'll assemble a virtual expert panel—product managers, designers, AI architects, growth specialists—and we'll ideate features from multiple angles.

Then I'll translate each feature into a job story, map the customer journey, define success metrics (HEART framework), and write Gherkin scenarios for acceptance criteria. This isn't "let's brainstorm some features." This is "let's architect a cohesive product system with integrated features that work together, validated by expert perspectives, and documented for professional implementation."

Product Concept​

Ideation runs in two phases for each opportunity:

Phase 1: Solution Ideation (TEMP=1.5)

I apply multiple expert perspectives including strategic product management, AI-first UX design, AI architecture, and job story analysis to generate diverse solution concepts.

Each expert contributes feature concepts and core mechanisms from their specialty perspective. I synthesize these ideas into a unified feature with clear UX narrative, core engine, business impact, tech concepts, key risks, and success metrics. I also generate Gherkin scenarios (happy path, edge cases, error handling) to ensure we've thought through implementation.

Phase 2: Job Story Analysis (TEMP=0.7)

I translate the feature into a job story following Alan Klement's format: "When [context], I want to [capability], So I can [outcome]." I map the customer journey stages (trigger, explore, analyze, decide, share) with emotional states and touchpoints using Spool's UX journey mapping. I define time metrics (how much faster is this than current alternatives?). I establish HEART metrics (Happiness, Engagement, Adoption, Retention, Task Success) with targets. And I show the transformation: "Before vs. After" states that make the value viscerally clear.

For each feature, you'll review and decide: APPROVE (move to PRD), REFINE (iterate), BACKLOG (save for later), or REJECT (discard). I'll loop until we have at least one approved solution for every DOS, ensuring comprehensive coverage.

At the end, I validate MVP/MVF completeness—checking that we have table stakes features (auth, data security, error handling) and strategic features (core value, differentiation, PLG hooks). If anything is missing, I'll ideate to fill gaps. Finally, I generate a Product Brief that synthesizes all approved features into a unified product story.

Actions​

  • I'll introduce multi-round ideation and present the OST structure.
  • I'll ideate features for each opportunity leaf using two-phase ReAct (expert ideation + job story analysis).
  • I'll present each feature for your approval (APPROVE|REFINE|BACKLOG|REJECT).
  • I'll validate that ≥1 solution per DOS is approved before moving to next DOS.
  • I'll audit MVP/MVF completeness (consumption DOS + consumer DOS coverage).
  • I'll ideate missing table stakes or strategic features as needed.
  • I'll generate a Product Scorecard showing feature status and product strength.
  • I'll generate a Product Brief synthesizing all approved features.
  • I'll persist all solutions and statuses to solution data.

Deliverables​

  • a2_solution_discovery/{{mm_session_persona}}/{{mm_session_roadmap}}/03a_[feat_id]_feat_[feature_name]: One detailed feature report per opportunity (Phase 1 ideation + Phase 2 job story). Each report includes expert ideas, feature synthesis, Gherkin scenarios, job story, journey mapping, time metrics, HEART metrics, touchpoints, and transformation narrative.
  • a2_solution_discovery/{{mm_session_persona}}/{{mm_session_roadmap}}/03b_product_scorecard: Iterative scorecard showing feature status (approved/backlog/rejected) and product strength assessment (JTBD fit, competitive position, PMF odds, propensity to pay).
  • a2_solution_discovery/{{mm_session_persona}}/{{mm_session_roadmap}}/03c_product_brief: Complete product brief integrating all ideated features into a unified product narrative with executive summary, core elements, key features, time-to-value analysis, and roadmap summary table.

Step 04: Intermezzo - Team Refinement​

Intro​

Before we lock in the PRD, let's pause and breathe.

Step 04 is your chance to bring in the team, gather stakeholder feedback, resolve priority conflicts, and make sure everyone is aligned on scope and direction. This is the "reality check" step. No matter how brilliant our ideation was, there are always real-world constraints: budget, timeline, team capabilities, market timing, strategic pivots.

Better to surface these now than after the PRD is written.

Product Concept​

Team Refinement is all about synthesis and alignment, drawing on Patrick Lencioni's team dynamics frameworks and Edward Freeman's stakeholder management principles.

I'll help you:

  • Aggregate feedback from team members and stakeholders on the ideated features.
  • Identify priority conflicts (e.g., "Sales wants feature X ASAP, but engineering says feature Y is critical").
  • Assess scope concerns (e.g., "This MVP is too big for our 3-month timeline").
  • Document resource constraints (e.g., "We don't have mobile expertise, so native apps are out").
  • Resolve conflicts and adjust priorities based on business objectives, user value, and technical feasibility using Geoffrey Moore's adoption frameworks.
  • Confirm final scope with stakeholders using Cagan's product validation principles and prepare for PRD generation.

This step ensures everyone feels heard and the final decision is data-driven, not politics-driven.

Actions​

  • I'll present the Product Brief and Product Scorecard for team review.
  • I'll facilitate feedback collection (structured format, not free-for-all chaos).
  • I'll synthesize feedback and identify conflicts, concerns, and constraints.
  • I'll help you resolve priority conflicts using objective criteria (RICE, OKR alignment, user value).
  • I'll document scope decisions (what's in, what's backlog, what's rejected).
  • I'll generate a Team Feedback Synthesis report and a Validated Solution Set.
  • I'll update solution data with final statuses and prepare for PRD handoff.

Deliverables​

  • a2_solution_discovery/{{mm_session_persona}}/{{mm_session_roadmap}}/04a_team_feedback_synthesis: Consolidated stakeholder feedback with priority conflicts, scope concerns, resource constraints, and resolution recommendations. This document ensures transparency and alignment.
  • a2_solution_discovery/{{mm_session_persona}}/{{mm_session_roadmap}}/04b_validated_solution_set: Final validated feature set ready for PRD generation, with confirmed priorities, scope summary, and PRD handoff checklist. This is your official "greenlight" document.

Step 05: Product Requirements Document (PRD)​

Intro​

This is it. The grand finale.

Step 05 is where I transform your validated solution set into a complete, Silicon Valley-grade Product Requirements Document (PRD) designed for autonomous implementation by professional teams or AI coders. No fluff. No ambiguity. No "we'll figure it out later."

This PRD is self-contained, comprehensive, and ready for designers and engineers to translate WHY and WHAT into HOW.

Product Concept​

A great PRD has three layers, drawing on frameworks from the best minds in product:

1. Strategic Context: Why are we building this? Who are we building for? What job are they hiring us to do?

This includes problem statement (Cagan's product strategy), personas (HXC/ICP), JTBD (Christensen's jobs framework), competitive landscape (Ulwick's ODI market analysis), and business model context using Alex Osterwalder's Business Model Canvas (BMC).

2. Functional Requirements: What exactly are we building?

This includes detailed feature specifications from your ideation, user stories, acceptance criteria, success metrics, and constraints. Every feature traces back to a validated DOS and has clear job stories.

3. Metrics & Instrumentation: How will we know if we succeeded?

This includes a complete metrics hierarchy using the HEART framework (Happiness, Engagement, Adoption, Retention, Task Success) plus performance metrics for every feature, with data instrumentation specs so engineers know exactly what to track. I calculate global weights for your metrics hierarchy using Analytic Hierarchy Process (AHP), apply ODI strategic multipliers based on opportunity zones, and ensure every metric traces back to your North Star Metric (NSM).

The result: A PRD that enables designers and engineers to build with confidence, informed by Wes Bush's PLG principles for growth mechanics.

Actions​

  • I'll aggregate all validated features from solution data.
  • I'll generate PRD Part 1: Problems & Solutions (problem statement, solution overview, personas, use cases, success metrics).
  • I'll generate PRD Part 2: Functional Requirements (detailed feature specs, user stories, acceptance criteria, constraints).
  • I'll generate PRD Part 3: Metrics & Instrumentation (complete metrics hierarchy with HEART, performance metrics, data instrumentation specs, global weights, ODI multipliers, NSM traceability).
  • I'll present each part for your approval and iteration.
  • I'll persist final PRD and set handoff flag for downstream teams.

Deliverables​

  • a2_solution_discovery/{{mm_session_persona}}/{{mm_session_roadmap}}/05a_prd_p1_problems_solutions: PRD Part 1 covering problem definition, solution overview, business context, personas, use cases, and success metrics. This is the "why" and "who."
  • a2_solution_discovery/{{mm_session_persona}}/{{mm_session_roadmap}}/05b_prd_p2_functional_requirements: PRD Part 2 covering detailed functional requirements, feature specifications, user stories, acceptance criteria, and constraints. This is the "what."
  • a2_solution_discovery/{{mm_session_persona}}/{{mm_session_roadmap}}/05c_prd_p3_metrics_instrumentation: PRD Part 3 covering complete metrics hierarchy, HEART metrics, performance metrics, data instrumentation, global weights, ODI multipliers, and NSM traceability. This is the "how we measure success."

Conclusion​

Congratulations, you made it.

You've transformed fuzzy customer insights into a validated, prioritized, fully documented solution roadmap ready for professional implementation. Take a moment to appreciate what you've built:

  • A competitive analysis that identifies market gaps and positioning opportunities.
  • An ODI roadmap that prioritizes customer needs based on data, not opinions.
  • An OST that explores multiple solution paths and sequences them for coherent ideation.
  • A complete feature set with expert ideation, job stories, Gherkin scenarios, journey mapping, and HEART metrics.
  • A team-validated scope with stakeholder alignment and resolved conflicts.
  • A Silicon Valley-grade PRD that enables autonomous implementation by professional teams or AI coders.

You didn't just brainstorm features. You engineered a product system grounded in evidence, validated by methodology, and designed for success.

Now go build it. And when users fall in love with your product because it solves their real problems in ways they never imagined, you'll know why.

Because you did the hard work of discovery. And that makes all the difference.