Skip to main content

Master Clay, Outcome-Driven Innovation Strategist (ISM-C)

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: Intake & Initialize
  • 01: Job Executor Persona (MVS + MSP Sides)
  • 02: JTBD Statement & Dimensions (Per Job Executor)
  • 03: JTBD Job Map (JMS)
  • 04: Consumer DOS (No Scores)
  • 05: Competitor Analysis (Consumer DOS)
  • 06: Consumer DOS Scored (Scoring + Visibles)
  • 07: Consumer Opportunity Landscape (Viz)
  • 08: Roadmap Clustering (Consumer)
  • 09: Roadmap Prioritization (Consumer)
  • 10: Consumption Jobs (PLG)
  • 11: Consumption JMS
  • 12: Consumption DOS (No Scores)
  • 13: PLG Benchmarks
  • 14: PLG DOS Scored (Scoring + Visibles)
  • 15: PLG Opportunity Landscape (Viz)
  • 16: Roadmap Clustering (Consumption)
  • 17: Roadmap Prioritization (Consumption)
  • 18: Executive Summary
  • 19: Conclusion

Phase 1: Customer & Problem Discovery​

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

Step 00: Intake & Initialize​

Intro​

This step turns intake & initialize 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 Persona & Empathy Modeling. Persona and empathy modeling define who we must delight first and why. It belongs here because this step must create a defensible outcome, not activity.

This step is complete only when the outcome is achieved: User: Persona/Context established, Initial hypothesis captured, User Proficiency detected..

Actions​

  • I translate the intent of Intake & Initialize into clear, testable criteria.
  • I apply Persona & Empathy Modeling 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​

  • c02_innovation_strategy/00_intake_summary_md: Intake Summary (MD sister)
  • c02_innovation_strategy/00_intake_summary: Intake Summary (HTML)
  • mm_odir_yaml: UPSERT path: mm_odir_json.researches[]. Initialize root scope object only; do not modify prior data.

Step 01: Job Executor Persona (MVS + MSP Sides)​

Intro​

Here I collapse ambiguity around job executor persona (mvs + msp sides) 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 Opportunity Solution Tree. OST links outcomes to solution options to keep ideation grounded in evidence. 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: Most Valuable Side (MVS) set as mm_job_executor and all MSP job executors defined in mm_job_executors_json..

Actions​

  • I translate the intent of Job Executor Persona (MVS + MSP Sides) into clear, testable criteria.
  • I apply Opportunity Solution Tree 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_job_executors_json: All MSP job executors with persona profiles and empathy maps. Drives all loops and aggregation.
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/01_job_executor_profile_md: Job Executor Profiles (MD)
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/01_job_executor_profile: Job Executor Profiles (HTML) - aggregate all MSP sides
  • mm_odir_yaml: UPSERT path: mm_odir_json.researches[].jtbd[].job_executors[]. Append-only. Include executor profiles + empathy maps per MSP side.
  • mm_confidence_log_json: Append-only confidence log for this step.

Step 02: JTBD Statement & Dimensions (Per Job Executor)​

Intro​

This is where jtbd statement & dimensions (per job executor) 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.

This step is complete only when the outcome is achieved: User: JTBD statement + dimensions defined per job executor..

Actions​

  • I translate the intent of JTBD Statement & Dimensions (Per Job Executor) 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​

  • mm_jtbd_json: JTBD Data Structure. MSP: one JTBD per job executor.
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/02_jtbd_md: JTBD (MD sister, full HTML content embedded)
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/02_jtbd: JTBD Statement & Dimensions (HTML) - aggregate all job executors
  • mm_odir_yaml: UPSERT path: mm_odir_json.researches[].jtbd[]. Append-only per executor JTBD.
  • mm_confidence_log_json: Append-only confidence log for this step.

Step 03: JTBD Job Map (JMS)​

Intro​

This step turns jtbd job map (jms) 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 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.

This step is complete only when the outcome is achieved: User: JMS table (Universal + Domain) defined per JTBD and per job executor..

Actions​

  • I translate the intent of JTBD Job Map (JMS) 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​

  • mm_jtbd_json: JTBD Data Structure with JMS. One JMS table per job executor.
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/03_solution_journey_jtbd_md: JTBD Journey (MD sister, full HTML content embedded)
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/03_solution_journey_jtbd: JTBD Core Statement + JMS Table (HTML) - aggregate all job executors
  • mm_odir_yaml: UPSERT path: mm_odir_json.researches[].jtbd[].jms[]. Append-only.
  • mm_confidence_log_json: Append-only confidence log for this step.

Step 04: Consumer DOS (No Scores)​

Intro​

Here I collapse ambiguity around consumer dos (no scores) 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.

This step is complete only when the outcome is achieved: User: Consumer DOS generated per JMS/JTBD/job executor without scores..

Actions​

  • I translate the intent of Consumer DOS (No Scores) 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​

  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/04_user_needs_dos_table: Consumer DOS Table (Markdown) - one table per job executor
  • mm_consumer_dos_json: Consumer DOS data (no scores yet).
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/04_user_needs_dos_md: Consumer DOS (MD sister, full HTML content embedded)
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/04_user_needs_dos: Consumer DOS (HTML) - narrative + tables
  • mm_odir_yaml: UPSERT path: mm_odir_json.researches[].jtbd[].jms[].dos[]. Append-only, no scores yet.
  • mm_confidence_log_json: Append-only confidence log for this step.

Phase 2: Strategy & Solution Design​

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

Step 05: Competitor Analysis (Consumer DOS)​

Intro​

This is where competitor analysis (consumer dos) 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 Desired Outcome Statements. DOS expresses success in the user's language so we can prioritize based on outcome gaps. It belongs here because this step must create a defensible outcome, not activity.

This step is complete only when the outcome is achieved: User: Competitor/alternative solutions appended for each Consumer DOS..

Actions​

  • I translate the intent of Competitor Analysis (Consumer DOS) into clear, testable criteria.
  • I apply Desired Outcome Statements 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_consumer_dos_competitors_json: Competitor arrays per Consumer DOS (append-only).
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/05_competitive_analysis_md: Competitive Analysis (MD sister, full HTML content embedded)
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/05_competitive_analysis: Competitive Analysis (HTML) - aggregate all job executors
  • mm_odir_yaml: UPSERT path: mm_odir_json.researches[].jtbd[].jms[].dos[].competitors[]. Append-only with timestamps.
  • mm_confidence_log_json: Append-only confidence log for this step.

Step 06: Consumer DOS Scored (Scoring + Visibles)​

Intro​

This step turns consumer dos scored (scoring + visibles) 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 Desired Outcome Statements. DOS expresses success in the user's language so we can prioritize based on outcome gaps. It belongs here because this step must create a defensible outcome, not activity.

This step is complete only when the outcome is achieved: User: Consumer DOS scored with opportunity levels..

Actions​

  • I translate the intent of Consumer DOS Scored (Scoring + Visibles) into clear, testable criteria.
  • I apply Desired Outcome Statements 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​

  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/06_user_needs_dos_scored_table: Consumer DOS Scored Table (Markdown) - one table per job executor
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/06_user_needs_dos_scored: Consumer DOS Scored (HTML) - headers sortable
  • mm_consumer_dos_json: Consumer DOS data with scores (s_score/opp/oz/ozl).
  • mm_odir_yaml: UPSERT path: mm_odir_json.researches[].jtbd[].jms[].dos[]. UPSERT s_score/opp/oz/ozl only.
  • mm_confidence_log_json: Append-only confidence log for this step.

Step 07: Consumer Opportunity Landscape (Viz)​

Intro​

Here I collapse ambiguity around consumer opportunity landscape (viz) 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 Hypothesis framing & decision gating. We turn raw intent into testable bets and set decision criteria before moving forward. It belongs here because this step must create a defensible outcome, not activity.

This step is complete only when the outcome is achieved: User: Consumer opportunity landscape visualization generated..

Actions​

  • I translate the intent of Consumer Opportunity Landscape (Viz) into clear, testable criteria.
  • I apply Hypothesis framing & decision gating 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_consumer_opp_landscape_data: Opportunity landscape chart data for Consumer DOS.
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/07_consumer_opp_landscape_viz: Consumer Opportunity Landscape (HTML) with OZL filters
  • mm_confidence_log_json: Append-only confidence log for this step.

Step 08: Roadmap Clustering (Consumer)​

Intro​

This is where roadmap clustering (consumer) 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 Desired Outcome Statements. DOS expresses success in the user's language so we can prioritize based on outcome gaps. It belongs here because this step must create a defensible outcome, not activity.

I layer Outcome-Driven Roadmapping to reinforce the decision logic, so the result is repeatable and evidence-backed. ODI roadmaps prioritize outcomes first so sequencing optimizes value and learning.

This step is complete only when the outcome is achieved: User: Consumer DOS clustered into themes for roadmap..

Actions​

  • I translate the intent of Roadmap Clustering (Consumer) into clear, testable criteria.
  • I apply Desired Outcome Statements 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​

  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/08_outcomes_roadmap_odir_md: Consumer Roadmap Clustering (MD sister, full HTML content embedded)
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/08_outcomes_roadmap_odir: Consumer Roadmap Clusters (HTML)
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/08_outcomes_roadmap_odir_table: Consumer Roadmap Cluster Table
  • mm_odir_yaml: UPSERT path: mm_odir_json.researches[].jtbd[].dos[].cluster.
  • mm_confidence_log_json: Append-only confidence log for this step.

Step 09: Roadmap Prioritization (Consumer)​

Intro​

This step turns roadmap prioritization (consumer) 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 Outcome-Driven Roadmapping. ODI roadmaps prioritize outcomes first so sequencing optimizes value and learning. It belongs here because this step must create a defensible outcome, not activity.

This step is complete only when the outcome is achieved: User: Consumer roadmap prioritized with rationale..

Actions​

  • I translate the intent of Roadmap Prioritization (Consumer) into clear, testable criteria.
  • I apply Outcome-Driven Roadmapping 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​

  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/09_outcomes_roadmap_odir_md: Consumer Roadmap Prioritization (MD sister, full HTML content embedded)
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/09_outcomes_roadmap_odir: Consumer Roadmap Prioritization (HTML)
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/09_outcomes_roadmap_odir_table: Consumer Roadmap Prioritization Table
  • mm_odir_yaml: UPSERT path: mm_odir_json.researches[].jtbd[].dos[].prioritization.
  • mm_confidence_log_json: Append-only confidence log for this step.

Phase 3: Build Readiness​

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

Step 10: Consumption Jobs (PLG)​

Intro​

Here I collapse ambiguity around consumption jobs (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 Product-Led Growth & Consumption Chain to reinforce the decision logic, so the result is repeatable and evidence-backed. 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: Consumption Jobs (8 JTBDs) defined per job executor..

Actions​

  • I translate the intent of Consumption Jobs (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​

  • mm_consumption_jobs_json: Consumption Jobs per executor (8 jobs).
  • mm_odir_yaml: UPSERT path: mm_odir_json.researches[].consumption_jobs[]. Append-only.
  • mm_confidence_log_json: Append-only confidence log for this step.

Step 11: Consumption JMS​

Intro​

This is where consumption jms 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 Product-Led Growth & Consumption Chain to reinforce the decision logic, so the result is repeatable and evidence-backed. 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: Consumption JMS per JTBD/job executor defined..

Actions​

  • I translate the intent of Consumption JMS 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​

  • mm_consumption_jms_json: Consumption JMS per job executor and per consumption job.
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/11_growth_journey_plg_md: Consumption JMS (MD sister, full HTML content embedded)
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/11_growth_journey_plg: Consumption JMS (HTML) - aggregate all job executors
  • mm_odir_yaml: UPSERT path: mm_odir_json.researches[].consumption_jobs[].jms[].
  • mm_confidence_log_json: Append-only confidence log for this step.

Step 12: Consumption DOS (No Scores)​

Intro​

This step turns consumption dos (no scores) 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 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: Consumption DOS generated per JMS/JTBD/job executor without scores..

Actions​

  • I translate the intent of Consumption DOS (No Scores) 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​

  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/12_product_led_growth_dos_table: Consumption DOS Table (MD) - one table per job executor
  • mm_consumption_dos_json: Consumption DOS data (no scores yet).
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/12_product_led_growth_dos_md: Consumption DOS (MD sister, full HTML content embedded)
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/12_product_led_growth_dos: Consumption DOS (HTML)
  • mm_odir_yaml: UPSERT path: mm_odir_json.researches[].consumption_jobs[].jms[].dos[]. Append-only, no scores yet.
  • mm_confidence_log_json: Append-only confidence log for this step.

Step 13: PLG Benchmarks​

Intro​

Here I collapse ambiguity around plg benchmarks 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 Desired Outcome Statements. DOS expresses success in the user's language so we can prioritize based on outcome gaps. It belongs here because this step must create a defensible outcome, not activity.

I layer Product-Led Growth & Consumption Chain to reinforce the decision logic, so the result is repeatable and evidence-backed. 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: Benchmarks identified per Consumption DOS..

Actions​

  • I translate the intent of PLG Benchmarks into clear, testable criteria.
  • I apply Desired Outcome Statements 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_consumption_benchmarks_json: Benchmarks per Consumption DOS (append-only).
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/13_plg_benchmarks_md: PLG Benchmarks (MD sister, full HTML content embedded)
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/13_plg_benchmarks: PLG Benchmarks (HTML)
  • mm_odir_yaml: UPSERT path: mm_odir_json.researches[].consumption_jobs[].jms[].dos[].benchmarks[]. Append-only with timestamps.
  • mm_confidence_log_json: Append-only confidence log for this step.

Step 14: PLG DOS Scored (Scoring + Visibles)​

Intro​

This is where plg dos scored (scoring + visibles) 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 Desired Outcome Statements. DOS expresses success in the user's language so we can prioritize based on outcome gaps. It belongs here because this step must create a defensible outcome, not activity.

I layer Product-Led Growth & Consumption Chain to reinforce the decision logic, so the result is repeatable and evidence-backed. 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: Consumption DOS scored with opportunity levels..

Actions​

  • I translate the intent of PLG DOS Scored (Scoring + Visibles) into clear, testable criteria.
  • I apply Desired Outcome Statements 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​

  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/14_product_led_growth_dos_scored_table: Consumption DOS Scored Table (MD) - one table per job executor
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/14_product_led_growth_dos_scored: Consumption DOS Scored (HTML) - headers sortable
  • mm_consumption_dos_json: Consumption DOS data with scores (s_score/opp/oz/ozl).
  • mm_odir_yaml: UPSERT path: mm_odir_json.researches[].consumption_jobs[].jms[].dos[]. UPSERT s_score/opp/oz/ozl only.
  • mm_confidence_log_json: Append-only confidence log for this step.

Phase 4: Execution & Handoff​

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

Step 15: PLG Opportunity Landscape (Viz)​

Intro​

This step turns plg opportunity landscape (viz) 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 Product-Led Growth & Consumption Chain. The consumption chain maps adoption moments so growth and retention are designed, not hoped for. It belongs here because this step must create a defensible outcome, not activity.

This step is complete only when the outcome is achieved: User: PLG opportunity landscape visualization generated..

Actions​

  • I translate the intent of PLG Opportunity Landscape (Viz) into clear, testable criteria.
  • I apply Product-Led Growth & Consumption Chain 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​

  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/15_plg_opp_landscape_viz_md: PLG Opportunity Landscape (MD sister, full HTML content embedded)
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/15_plg_opp_landscape_viz: PLG Opportunity Landscape (HTML) with JTBD + OZL filters
  • mm_confidence_log_json: Append-only confidence log for this step.

Step 16: Roadmap Clustering (Consumption)​

Intro​

Here I collapse ambiguity around roadmap clustering (consumption) 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 Desired Outcome Statements. DOS expresses success in the user's language so we can prioritize based on outcome gaps. It belongs here because this step must create a defensible outcome, not activity.

I layer Product-Led Growth & Consumption Chain to reinforce the decision logic, so the result is repeatable and evidence-backed. The consumption chain maps adoption moments so growth and retention are designed, not hoped for.

I also use Outcome-Driven Roadmapping because it tightens the feedback loop and prevents drift. ODI roadmaps prioritize outcomes first so sequencing optimizes value and learning.

This step is complete only when the outcome is achieved: User: Consumption DOS clustered into PLG themes for roadmap..

Actions​

  • I translate the intent of Roadmap Clustering (Consumption) into clear, testable criteria.
  • I apply Desired Outcome Statements 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​

  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/16_plg_roadmap_odir_md: Consumption Roadmap Clustering (MD sister, full HTML content embedded)
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/16_plg_roadmap_odir: PLG Roadmap Clusters (HTML)
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/16_plg_roadmap_odir_table: PLG Roadmap Cluster Table
  • mm_odir_yaml: UPSERT path: mm_odir_json.researches[].consumption_jobs[].dos[].cluster.
  • mm_confidence_log_json: Append-only confidence log for this step.

Step 17: Roadmap Prioritization (Consumption)​

Intro​

This is where roadmap prioritization (consumption) 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 Product-Led Growth & Consumption Chain. The consumption chain maps adoption moments so growth and retention are designed, not hoped for. It belongs here because this step must create a defensible outcome, not activity.

I layer Outcome-Driven Roadmapping to reinforce the decision logic, so the result is repeatable and evidence-backed. ODI roadmaps prioritize outcomes first so sequencing optimizes value and learning.

This step is complete only when the outcome is achieved: User: Consumption roadmap prioritized with rationale..

Actions​

  • I translate the intent of Roadmap Prioritization (Consumption) into clear, testable criteria.
  • I apply Product-Led Growth & Consumption Chain 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​

  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/17_plg_roadmap_odir_md: Consumption Roadmap Prioritization (MD sister, full HTML content embedded)
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/17_plg_roadmap_odir: PLG Roadmap Prioritization (HTML)
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/17_plg_roadmap_odir_table: PLG Roadmap Prioritization Table
  • mm_odir_yaml: UPSERT path: mm_odir_json.researches[].consumption_jobs[].dos[].prioritization.
  • mm_confidence_log_json: Append-only confidence log for this step.

Step 18: Executive Summary​

Intro​

This step turns executive summary 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 Hypothesis framing & decision gating. We turn raw intent into testable bets and set decision criteria before moving forward. It belongs here because this step must create a defensible outcome, not activity.

This step is complete only when the outcome is achieved: User: Executive Summary and Appendix created..

Actions​

  • I translate the intent of Executive Summary into clear, testable criteria.
  • I apply Hypothesis framing & decision gating 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​

  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/18_executive_summary_md: Executive Summary (MD)
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/18_executive_summary: Executive Summary (HTML)
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/18_executive_summary_appendix: Project Variables Appendix
  • mm_odir_yaml: UPSERT path: mm_odir_json.researches[]. No data changes; reference-only output.
  • mm_confidence_log_json: Append-only confidence log for this step.

Step 19: Conclusion​

Intro​

Here I collapse ambiguity around conclusion 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 Handoff & Continuity. Explicit handoff preserves continuity and prevents context loss. It belongs here because this step must create a defensible outcome, not activity.

This step is complete only when the outcome is achieved: User: Process completed..

Actions​

  • I translate the intent of Conclusion into clear, testable criteria.
  • I apply Handoff & Continuity 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​

  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/19_conclusion_md: Conclusion (MD sister)
  • c02_innovation_strategy/{{mm_session_scope}}/{{mm_job_executor}}/19_conclusion: Conclusion (HTML)
  • mm_odir_yaml: UPSERT path: mm_odir_json.researches[]. No data changes; reference-only output.
  • mm_confidence_log_json: Append-only confidence log for this step.

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.