Skip to main content

Master Steve, Customer Discovery (CDM-A)

Intro​

Strap in. You are here for evidence, momentum, and outcomes that can survive scrutiny. I am your Master guide. I move fast, but I only move on proof. Sage is the case study threading this manual, and Dani is the user signal that keeps every step honest.

Hyperboost Formula​

What is the Hyperboost Formula?​

Hyperboost is the operating system I use to move from intent to validated action. It is the curated fusion of proven frameworks, sequenced in the exact order and applied in the right amount.

The DNA: Build-Measure-Learn—Relentlessly​

Every step is an experiment with a hypothesis, a signal, and a decision. If we cannot measure reality, we do not move forward.

Integration of Methods: Lean Startup, Empathy, and AI​

  • Lean Startup: Ruthless validation before investment.
  • Customer Empathy: Real pain beats internal opinions every time.
  • AI Acceleration: Machines handle grunt work so humans decide with clarity.

Why Does the Hyperboost Formula Matter?​

Because velocity without proof is just fast failure. Hyperboost forces evidence into every step so risk shrinks as speed increases.

Anatomy of the Hyperboost Journey​

This is a stepwise engine where each output becomes the next input. I do not skip gates; I compress ambiguity until the next decision is obvious.

Core Principles Guiding Every Step​

  • Evidence over ego: proof beats preference.
  • Traceability: every artifact links to a decision.
  • Velocity with control: fast, but never blind.
  • Autonomy ready: outputs must be executable without context loss.
  • Ruthless clarity: ambiguity is a defect, not a feature.

Process Overview​

  • 00: Idea Gathering
  • 01: Find Your Product/Business Idea
  • 02: Check if Idea is Worth It (POA)
  • 03: OKRs, Target Region & Profile Setup
  • 04: Target Niche & Dream Customer (HXC/ICP)
  • 05: Customer Journey (JTBD & Job Map)
  • 06: Customer Pain/Gain Analysis (DOS)
  • 07: How Users Adopt, Engage & Share (Consumption Chain/PLG)

Phase 1: Discovery & Alignment​

This phase compresses ambiguity so the next move is defensible and fast.

Step 00: Idea Gathering​

Intro​

This step turns idea gathering into a decision that can survive contact with reality. Sage uses this moment to translate ambition into a concrete move. Dani is the signal that keeps the outcome grounded in real user behavior.

Product Concept​

I apply Divergent Ideation & Hypothesis Capture. We collect raw ideas without judgment so we can frame the right hypothesis before validation. It belongs here because this step must create a defensible outcome, not activity.

This step is complete only when the outcome is achieved: User/ctx: idea/new/existing/continue; autodetect ctx; route→min effort; ready next step.

Actions​

  • I translate the intent of Idea Gathering into clear, testable criteria.
  • I apply Divergent Ideation & Hypothesis Capture to generate the core artifact for this decision.
  • I pressure-test the result against real constraints and user evidence.
  • I document the decision trail so downstream steps stay aligned.

Deliverables​

  • a1_customer_discovery/00_my_idea: User prod/svc/biz idea, OR niche to help, OR ask Master support finding winning idea
  • mm_initiative: init&proj ctx: name&strategic attrs

Step 01: Find Your Product/Business Idea​

Intro​

Here I collapse ambiguity around find your product/business idea so every next move has proof behind it. Sage relies on this step to remove blind spots before momentum accelerates. Dani is the proof check that stops us from building for ourselves.

Product Concept​

I apply Market Scanning & Opportunity Scoring. We scan demand signals and score opportunities so the best hypothesis is selected, not guessed. It belongs here because this step must create a defensible outcome, not activity.

I layer Solution Ideation & Synthesis to reinforce the decision logic, so the result is repeatable and evidence-backed. Structured ideation turns validated outcomes into coherent solution options.

This step is complete only when the outcome is achieved: User: discovered or refined compelling product/feature idea w/ clear market potential OR explored alternative solution angles for existing hypothesis.

Actions​

  • I translate the intent of Find Your Product/Business Idea into clear, testable criteria.
  • I apply Market Scanning & Opportunity Scoring to generate the core artifact for this decision.
  • I pressure-test the result against real constraints and user evidence.
  • I document the decision trail so downstream steps stay aligned.

Deliverables​

  • support/master_{{ai_agent.name}}/a1_customer_discovery/01_product_ideas_md: Top 20 biz/feature ideas w/ disruption potential OR alternative angles same problem (source markdown for HTML rendering)
  • a1_customer_discovery/01_product_ideas: Top 20 biz/feature ideas w/ disruption potential OR alternative angles same problem
  • a1_customer_discovery/00_my_idea: User-selected prod/feature opp hypothesis w/ rationale

Phase 2: Design & Build Readiness​

This phase compresses ambiguity so the next move is defensible and fast.

Step 02: Check if Idea is Worth It (POA)​

Intro​

This is where check if idea is worth it (poa) becomes a defensible call instead of a guess. Sage treats this step as the guardrail that keeps the journey honest. Dani is the reality anchor that keeps this step from drifting into theory.

Product Concept​

I apply Solution Ideation & Synthesis. Structured ideation turns validated outcomes into coherent solution options. It belongs here because this step must create a defensible outcome, not activity.

I layer Product Opportunity Assessment to reinforce the decision logic, so the result is repeatable and evidence-backed. POA stress-tests value, usability, feasibility, and viability before we invest.

This step is complete only when the outcome is achieved: Validated high-potential product/feature opportunity aligned w/ goals&product context OR identified alternative paths to pursue same vision.

Actions​

  • I translate the intent of Check if Idea is Worth It (POA) into clear, testable criteria.
  • I apply Solution Ideation & Synthesis to generate the core artifact for this decision.
  • I pressure-test the result against real constraints and user evidence.
  • I document the decision trail so downstream steps stay aligned.

Deliverables​

  • support/master_{{ai_agent.name}}/a1_customer_discovery/02_opportunity_assessment_poa_md: prod opp Assessment w/ strategic analysis + loving mentor guidance (source markdown for HTML rendering)
  • a1_customer_discovery/02_opportunity_assessment_poa: prod opp Assessment w/ strategic analysis + loving mentor guidance
  • mm_initial_hypothesis_alts: Hypothesis context alternative sol angles exploration (Option 2)

Step 03: OKRs, Target Region & Profile Setup​

Intro​

This step turns okrs, target region & profile setup into a decision that can survive contact with reality. Sage uses this moment to translate ambition into a concrete move. Dani is the signal that keeps the outcome grounded in real user behavior.

Product Concept​

I apply OKR design. OKRs translate ambition into measurable outcomes that prevent drift. It belongs here because this step must create a defensible outcome, not activity.

I layer Agentic Build Operations to reinforce the decision logic, so the result is repeatable and evidence-backed. Operational prompts ensure coders execute with context and quality gates.

This step is complete only when the outcome is achieved: User has defined clear OKRs, target research region and profile, ready to begin systematic product dev process.

Actions​

  • I translate the intent of OKRs, Target Region & Profile Setup into clear, testable criteria.
  • I apply OKR design to generate the core artifact for this decision.
  • I pressure-test the result against real constraints and user evidence.
  • I document the decision trail so downstream steps stay aligned.

Deliverables​

  • No explicit deliverables are emitted at this step.

Step 04: Target Niche & Dream Customer (HXC/ICP)​

Intro​

Here I collapse ambiguity around target niche & dream customer (hxc/icp) so every next move has proof behind it. Sage relies on this step to remove blind spots before momentum accelerates. Dani is the proof check that stops us from building for ourselves.

Product Concept​

I apply OKR design. OKRs translate ambition into measurable outcomes that prevent drift. It belongs here because this step must create a defensible outcome, not activity.

I layer Persona & Empathy Modeling to reinforce the decision logic, so the result is repeatable and evidence-backed. Persona and empathy modeling define who we must delight first and why.

This step is complete only when the outcome is achieved: User: validated target niche(s) per audience (single/per platform side) w/ highest OKR/PMF potential, confirmed HXC Persona(s) as Job Executor(s) w/ full psychological/behavioral analysis (Empathy Map per audience), biz solutions include optimal ICP, ODIR tree initialized w/ audience branch(es).

Actions​

  • I translate the intent of Target Niche & Dream Customer (HXC/ICP) into clear, testable criteria.
  • I apply OKR design to generate the core artifact for this decision.
  • I pressure-test the result against real constraints and user evidence.
  • I document the decision trail so downstream steps stay aligned.

Deliverables​

  • a1_customer_discovery/{{mm_session_persona}}/04a_niche_analysis: Top 3 niches per audience side for initiative success
  • a1_customer_discovery/{{mm_session_persona}}/04b_selected_niche: Selected niche(s) per audience
  • a1_customer_discovery/{{mm_session_persona}}/04c_ideal_user_hxc: HXC(s) per audience
  • a1_customer_discovery/{{mm_session_persona}}/04d_ideal_company_icp: If biz sol,rec the most opportune ICP (Ideal cust Profile),where the selected HXC persona works for,increasing the chances of biz success
  • mm_odir_yaml: ODIR tree initialization w/ audience(s),niche(s),HXC(s). JTBD/JMS/DOS added in subsequent steps

Phase 3: Delivery & Handoff​

This phase compresses ambiguity so the next move is defensible and fast.

Step 05: Customer Journey (JTBD & Job Map)​

Intro​

This is where customer journey (jtbd & job map) becomes a defensible call instead of a guess. Sage treats this step as the guardrail that keeps the journey honest. Dani is the reality anchor that keeps this step from drifting into theory.

Product Concept​

I apply Jobs-to-be-Done & Job Map. JTBD clarifies the true user job, and the Job Map structures it into steps we can improve. It belongs here because this step must create a defensible outcome, not activity.

I layer Persona & Empathy Modeling to reinforce the decision logic, so the result is repeatable and evidence-backed. Persona and empathy modeling define who we must delight first and why.

This step is complete only when the outcome is achieved: User: defined JTBD statement(s) w/ 3 dimensions (Functional, Personal, Social) per audience + Job Map Steps (6-8 JMS) per audience, ODIR tree populated w/ JTBD + JMS branches.

Actions​

  • I translate the intent of Customer Journey (JTBD & Job Map) into clear, testable criteria.
  • I apply Jobs-to-be-Done & Job Map to generate the core artifact for this decision.
  • I pressure-test the result against real constraints and user evidence.
  • I document the decision trail so downstream steps stay aligned.

Deliverables​

  • a1_customer_discovery/{{mm_session_persona}}/05_solution_journey_jtbd: JTBD statement(s) + Job Map per audience
  • mm_odir_yaml: ODIR tree update: add JTBD + JMS per audience

Step 06: Customer Pain/Gain Analysis (DOS)​

Intro​

This step turns customer pain/gain analysis (dos) into a decision that can survive contact with reality. Sage uses this moment to translate ambition into a concrete move. Dani is the signal that keeps the outcome grounded in real user behavior.

Product Concept​

I apply OKR design. OKRs translate ambition into measurable outcomes that prevent drift. It belongs here because this step must create a defensible outcome, not activity.

I layer Jobs-to-be-Done & Job Map to reinforce the decision logic, so the result is repeatable and evidence-backed. JTBD clarifies the true user job, and the Job Map structures it into steps we can improve.

I also use Desired Outcome Statements because it tightens the feedback loop and prevents drift. DOS expresses success in the user's language so we can prioritize based on outcome gaps.

This step is complete only when the outcome is achieved: User receives detailed Customer DOS evaluation across Job Map Steps, extracted from pain/gain research, ranked by OKR impact + Opp Score to guide ODI Roadmap for product dev priorities.

Actions​

  • I translate the intent of Customer Pain/Gain Analysis (DOS) into clear, testable criteria.
  • I apply OKR design to generate the core artifact for this decision.
  • I pressure-test the result against real constraints and user evidence.
  • I document the decision trail so downstream steps stay aligned.

Deliverables​

  • mm_odir_yaml: Complete ODIR tree w/ complete audience branch down to all DOS nodes
  • a1_customer_discovery/{{mm_session_persona}}/06_user_needs_dos: PM artifact: Complete JTBD journey mapping w/ complete custs' Desired Outcomes Statements (DOS) analysis per Job Map Step (JMS)

Step 07: How Users Adopt, Engage & Share (Consumption Chain/PLG)​

Intro​

Here I collapse ambiguity around how users adopt, engage & share (consumption chain/plg) so every next move has proof behind it. Sage relies on this step to remove blind spots before momentum accelerates. Dani is the proof check that stops us from building for ourselves.

Product Concept​

I apply Jobs-to-be-Done & Job Map. JTBD clarifies the true user job, and the Job Map structures it into steps we can improve. It belongs here because this step must create a defensible outcome, not activity.

I layer Desired Outcome Statements to reinforce the decision logic, so the result is repeatable and evidence-backed. DOS expresses success in the user's language so we can prioritize based on outcome gaps.

I also use Product-Led Growth & Consumption Chain because it tightens the feedback loop and prevents drift. The consumption chain maps adoption moments so growth and retention are designed, not hoped for.

This step is complete only when the outcome is achieved: User: full catalog of DOS across all seven consumption jobs (Acquire|Activate|Onboard|Support|Engage|Expand|Advocate) w/ Job Map Steps, opp scores, benchmarks serving as strategic foundation for developing PLG strategies, habit-forming mechanisms, automation frameworks, viral loops, self-service experiences, AHA moments, retention systems. CDM-A HANDOFF: Ready for SDM-A..

Actions​

  • I translate the intent of How Users Adopt, Engage & Share (Consumption Chain/PLG) into clear, testable criteria.
  • I apply Jobs-to-be-Done & Job Map to generate the core artifact for this decision.
  • I pressure-test the result against real constraints and user evidence.
  • I document the decision trail so downstream steps stay aligned.

Deliverables​

  • a1_customer_discovery/{{mm_session_persona}}/07a_growth_journey_plg: PM artifact: Consumption chain jobs sol persona/ICP w/ Job Map Steps PLG strat
  • mm_odir_yaml: Complete ODIR tree w/ added consumption outcomes branch PLG strat
  • a1_customer_discovery/{{mm_session_persona}}/07b_product_led_growth_dos: PM artifact: Consumption DOS statements PLG strat w/ success metrics
  • mm_odir_yaml: Complete ODIR tree w/ consumption outcomes branch PLG strat

Conclusion​

We end with a handoff-ready body of evidence and artifacts you can execute without guesswork. If Sage can act with confidence and Dani would still trust the outcome, the system did its job.