Skip to main content

Master Cris, OKRs Planning Master (OPM-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: Strategic Planning (Robbie's) Intake and Dispatch
  • 01: Value Tree and Leading/Lagging Indicators
  • 02: Problem Statement and Pre-thesis Object
  • 03: Opportunity Solution Tree (OST)
  • 04: Solution Ideation + Selection + Structured Thesis
  • 05: Financial Sizing
  • 06: Initiatives and Dependency Map
  • 07: Investment Estimate and Execution Calendar
  • 08: ROI and Payback
  • 09: Thesis One-Pager
  • 10: Storytelling and Strategic Alignment
  • 11: Critiques Preparation
  • 12: Conclusion and Handoff

Phase 1: Customer & Problem Discovery​

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

Step 00: Strategic Planning (Robbie's) Intake and Dispatch​

Intro​

This step turns strategic planning (robbie's) intake and dispatch 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: Strategic Planning (Robbie's) outputs ingested; a single thesis candidate proposed; missing inputs clarified; ready to start Step 01..

Actions​

  • I translate the intent of Strategic Planning (Robbie's) Intake and Dispatch 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_thesis_plan: UPSERT planning state
  • c06_okrs_planning/00a_handover_packet_md: Normalized Strategic Planning (Robbie's) to OKRs Planning handover packet (markdown)
  • c06_okrs_planning/00a_handover_packet: Handover packet (HTML)
  • c06_okrs_planning/00b_intake_summary_md: Intake summary (markdown)
  • c06_okrs_planning/00b_intake_summary: Intake summary (HTML)

Step 01: Value Tree and Leading/Lagging Indicators​

Intro​

Here I collapse ambiguity around value tree and leading/lagging indicators 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 Value Tree & Metrics to reinforce the decision logic, so the result is repeatable and evidence-backed. Value trees connect outcomes to measurable signals and guide prioritization.

I also use UI System & Visual Design because it tightens the feedback loop and prevents drift. A UI system enforces consistency, accessibility, and velocity.

This step is complete only when the outcome is achieved: User: value tree built from OKR to lagging impact and leading indicators; thesis contribution validated..

Actions​

  • I translate the intent of Value Tree and Leading/Lagging Indicators 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​

  • c06_okrs_planning/01a_value_tree_md: Value tree and leading/lagging mapping (markdown)
  • c06_okrs_planning/01a_value_tree: Value tree and leading/lagging mapping (HTML)

Step 02: Problem Statement and Pre-thesis Object​

Intro​

This is where problem statement and pre-thesis object 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 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 Opportunity Solution Tree because it tightens the feedback loop and prevents drift. OST links outcomes to solution options to keep ideation grounded in evidence.

This step is complete only when the outcome is achieved: User: opportunity reframed into a customer problem statement with JTBD, barrier, and DOS outcome; ready for OST..

Actions​

  • I translate the intent of Problem Statement and Pre-thesis Object 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​

  • c06_okrs_planning/02a_problem_statement_md: Problem statement with JTBD, barrier, and DOS outcome (markdown)
  • c06_okrs_planning/02a_problem_statement: Problem statement (HTML)
  • c06_okrs_planning/02b_pre_thesis_object_md: Pre-thesis object (markdown)
  • c06_okrs_planning/02b_pre_thesis_object: Pre-thesis object (HTML)

Phase 2: Strategy & Solution Design​

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

Step 03: Opportunity Solution Tree (OST)​

Intro​

This step turns opportunity solution tree (ost) 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 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 Opportunity Solution Tree to reinforce the decision logic, so the result is repeatable and evidence-backed. OST links outcomes to solution options to keep ideation grounded in evidence.

I also use UI System & Visual Design because it tightens the feedback loop and prevents drift. A UI system enforces consistency, accessibility, and velocity.

This step is complete only when the outcome is achieved: User: single-outcome OST built; ready for ideation..

Actions​

  • I translate the intent of Opportunity Solution Tree (OST) 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​

  • mm_solutions_yaml: Single-outcome OST tree with solutions, scores, and statuses
  • c06_okrs_planning/03a_ost_md: Single-outcome OST with high-level solutions and scores (markdown)
  • c06_okrs_planning/03a_ost: OST summary (HTML)
  • c06_okrs_planning/03b_ost_mindmap: OST mindmap (Mermaid)
  • c06_okrs_planning/03c_ost_radial: Radial OST visualization (HTML)

Step 04: Solution Ideation + Selection + Structured Thesis​

Intro​

Here I collapse ambiguity around solution ideation + selection + structured thesis 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 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.

This step is complete only when the outcome is achieved: User: solution ideation completed; one solution selected; structured thesis drafted..

Actions​

  • I translate the intent of Solution Ideation + Selection + Structured Thesis 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​

  • c06_okrs_planning/04a_solution_[%sol_id%, hint='S01 (seq) + (a/b/c) (version)']_md: High-level solution ideation (markdown)
  • c06_okrs_planning/04a_solution_[%sol_id%, hint='S01 (seq) + (a/b/c) (version)']: High-level solution ideation (HTML)
  • c06_okrs_planning/04b_solution_selection_md: Solution selection decision (markdown)
  • c06_okrs_planning/04b_solution_selection: Solution selection decision (HTML)
  • c06_okrs_planning/04c_selected_solution_thesis_md: Structured thesis (markdown)
  • c06_okrs_planning/04c_selected_solution_thesis: Structured thesis (HTML)

Step 05: Financial Sizing​

Intro​

This is where financial sizing 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 UI System & Visual Design. A UI system enforces consistency, accessibility, and velocity. It belongs here because this step must create a defensible outcome, not activity.

This step is complete only when the outcome is achieved: User: sizing model built with data-backed baselines, scenarios, and impacts across the planning horizon..

Actions​

  • I translate the intent of Financial Sizing into clear, testable criteria.
  • I apply UI System & Visual 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​

  • c06_okrs_planning/05a_calc_rationale_assumptions_md: Calculation rationale and assumptions (markdown)
  • c06_okrs_planning/05a_calc_rationale_assumptions: Calculation rationale and assumptions (HTML)
  • c06_okrs_planning/05b_sizing_model_md: Sizing model (markdown)
  • c06_okrs_planning/05b_sizing_model: Sizing model (HTML)

Phase 3: Build Readiness​

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

Step 06: Initiatives and Dependency Map​

Intro​

This step turns initiatives and dependency map 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 UI System & Visual Design. A UI system enforces consistency, accessibility, and velocity. It belongs here because this step must create a defensible outcome, not activity.

This step is complete only when the outcome is achieved: User: initiatives list defined and a complete dependency map built with risk classification and mitigation..

Actions​

  • I translate the intent of Initiatives and Dependency Map into clear, testable criteria.
  • I apply UI System & Visual 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​

  • c06_okrs_planning/06_dependency_map_md: Dependency map (markdown)
  • c06_okrs_planning/06_dependency_map: Dependency map (HTML)
  • c06_okrs_planning/06b_thesis_card_md: Thesis card (markdown)
  • c06_okrs_planning/06b_thesis_card: Thesis card (HTML)

Step 07: Investment Estimate and Execution Calendar​

Intro​

Here I collapse ambiguity around investment estimate and execution calendar 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: assumptions validated; effort and uncertainty mapped; delivery paths simulated; execution calendar and investment plan finalized..

Actions​

  • I translate the intent of Investment Estimate and Execution Calendar 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​

  • c06_okrs_planning/07a_plan_assumptions_md: Execution plan assumptions (markdown)
  • c06_okrs_planning/07a_plan_assumptions: Execution plan assumptions (HTML)
  • c06_okrs_planning/07b_effort_matrix_svg_md: Effort vs Uncertainty matrix (markdown)
  • c06_okrs_planning/07b_effort_matrix_svg: Effort vs Uncertainty matrix (HTML)
  • c06_okrs_planning/07c_execution_strategy_options_md: Execution strategy options (markdown)
  • c06_okrs_planning/07c_execution_strategy_options: Execution strategy options (HTML)
  • c06_okrs_planning/07d_monte_carlo_path_selector: Monte Carlo path selector (HTML)
  • c06_okrs_planning/07e_execution_calendar_md: Execution calendar (markdown)
  • c06_okrs_planning/07e_execution_calendar: Execution calendar (HTML)
  • c06_okrs_planning/07f_investment_plan_md: Investment plan (markdown)
  • c06_okrs_planning/07f_investment_plan: Investment plan (HTML)

Step 08: ROI and Payback​

Intro​

This is where roi and payback 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 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: ROI assumptions validated; headline KPIs and YoY tables produced; payback confirmed..

Actions​

  • I translate the intent of ROI and Payback 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​

  • c06_okrs_planning/08a_roi_assumptions_md: ROI assumptions (markdown)
  • c06_okrs_planning/08a_roi_assumptions: ROI assumptions (HTML)
  • c06_okrs_planning/08b_roi_summary_md: ROI summary (markdown)
  • c06_okrs_planning/08b_roi_summary: ROI summary (HTML)
  • c06_okrs_planning/08c_roi_yoy_md: ROI YoY table (markdown)
  • c06_okrs_planning/08c_roi_yoy: ROI YoY table (HTML)

Phase 4: Execution & Handoff​

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

Step 09: Thesis One-Pager​

Intro​

This step turns thesis one-pager 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: one-pager produced consolidating thesis, indicators, ROI, and execution calendar..

Actions​

  • I translate the intent of Thesis One-Pager 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​

  • c06_okrs_planning/09_thesis_one_pager_md: Thesis one-pager (markdown)
  • c06_okrs_planning/09_thesis_one_pager: Thesis one-pager (HTML)

Step 10: Storytelling and Strategic Alignment​

Intro​

Here I collapse ambiguity around storytelling and strategic alignment 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.

This step is complete only when the outcome is achieved: User: narrative, infographic, diagnostic slide, and pitch deck created to align the thesis with strategic drivers and priorities..

Actions​

  • I translate the intent of Storytelling and Strategic Alignment 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​

  • c06_okrs_planning/10a_strategic_drivers_infographic: Strategic drivers infographic (HTML)
  • c06_okrs_planning/10b_diagnostic_slide: Pre-thesis diagnostic slide (HTML)
  • c06_okrs_planning/10c_pitch_deck: Pitch deck (HTML)
  • c06_okrs_planning/10d_storytelling_narrative_md: Strategic narrative (markdown)
  • c06_okrs_planning/10d_storytelling_narrative: Strategic narrative (HTML)

Step 11: Critiques Preparation​

Intro​

This is where critiques preparation 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 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: critiques readiness decided and critique training completed in interactive batches..

Actions​

  • I translate the intent of Critiques Preparation 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​

  • c06_okrs_planning/11a_critiques_readiness_md: Critiques readiness (markdown)
  • c06_okrs_planning/11a_critiques_readiness: Critiques readiness (HTML)
  • c06_okrs_planning/11b_critiques_training_md: Critiques training (markdown)
  • c06_okrs_planning/11b_critiques_training: Critiques training (HTML)

Step 12: Conclusion and Handoff​

Intro​

This step turns conclusion and handoff 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 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: full journey summarized with next-step handoffs and closure..

Actions​

  • I translate the intent of Conclusion and Handoff 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​

  • c06_okrs_planning/12_conclusion_handoff_md: Conclusion and handoff (markdown)
  • c06_okrs_planning/12_conclusion_handoff: Conclusion and handoff (HTML)

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.