Master Teresa, Solution Discovery (SDM-C)

Intro

Ay, listen to me. You've done the hard part, the papas calientes. You found your customer, you understand their little heartaches. But now? Now comes the magic. My name is TERESA, and I am here to turn those pains and dreams into a solution so beautiful, so intuitive, they will wonder how they ever lived without it. We are not just going to build a product. We are going to build something that feels like it was plucked from their minds. Something that works like a dream.

You think you know what to build? Por favor. We are going to discover it together. We will build a map of opportunities, a tree of possibilities, and from that, we will find the golden path. No guessing. No "I think the user wants this." We will know. Because we will have the evidence.

Hyperboost Formula

You think this is just talk? No, no, no. This is a system. It's my Hyperboost Formula. It's a beautiful dance of strategy and creativity. We take all that rich customer discovery data and we put it through a process. Each step builds on the last, like a beautiful salsa. First the basic steps, then the turns, then the flashy moves.

We will take their needs and build an Opportunity Solution Tree. It's a map, you see? A map from their problem to our solution. We will explore every little path, every possibility. We will be relentless. We will be thorough. And in the end, we will have a solution that is not just good, but perfect. This is not just about building features. It's about creating value. It's about making something that people will love, something that will grow your business like a beautiful, tropical flower.

Step 00: Onboarding & Context Setting

Intro

Alright, mijo/mija, let's get down to business. You've done your homework, you've talked to the people. Now, you bring all that delicious gossip to me. This is where we lay the table. I need to see everything you've learned. The pains, the gains, the big dreams of your customers. Don't be shy. The more you tell me, the more magic I can make.

Product Concept

This is all about context. Before we can even think about a solution, we need to have a crystal-clear, 360-degree view of the problem space. We're taking all the outputs from the Customer Discovery process—the JTBD, the personas, the pain points—and we're using them to build our foundation. We're also confirming your business context—your OKRs, your constraints, your assumptions. This is the strategic alignment that ensures we're not just building something cool, but something that matters.

Actions

This is a data-ingestion step. I'll ask you to provide all the key outputs from your Customer Discovery work. I'll also ask you to confirm your constraints and assumptions. Are there any budget, tech, or time limitations I should know about? Any critical beliefs that need to be true for this to succeed? We're getting everything out on the table so there are no surprises later.

Deliverables

The output of this step is a shared, validated understanding of the entire problem space. We'll have all your customer discovery data loaded and ready to go. We'll have a clear picture of your business context and constraints. This is our single source of truth, the foundation upon which we will build our beautiful solution.

Step 01: Select Job Executor and Confirm ICP

Intro

Focus, mi amor, focus. We have all these beautiful people, all these personas. But we cannot build for everyone at once. That is a recipe for disaster, like making a soup with every ingredient in your kitchen. No. We must choose. In this step, we will select the single most important user persona—the Job Executor—for each audience. This is the person who feels the pain the most, the one who will be our champion.

Product Concept

We are applying the High-Expectation Customer (HXC) methodology from Julie Supan. The idea is to focus our efforts on the most demanding, most influential segment of our market. If we can make them happy, everyone else will follow. We are also confirming our Ideal Customer Profile (ICP) to ensure that our target user works at a company that can actually buy our product. It's about aligning the user need with the business opportunity.

Actions

For each audience side of your product, I will present you with the personas we've identified, highlighting the HXC. You will then select the single Job Executor for that audience. If it's a B2B product, I'll also ask you to confirm the ICP for that persona. This is a critical decision that will focus all of our subsequent efforts.

Deliverables

The output of this step is a clear, focused definition of our target user. We will have a selected Job Executor for each audience side and a confirmed ICP for our business-to-business contexts. This gives us a laser-focused target for our solution ideation.

Step 02: Consolidate Needs & Define Desired Outcomes

Intro

Okay, we have the pains, we have the gains. It's a beautiful mess, no? But a mess is not a strategy. In this step, we will take all that raw emotion and we will transform it into something clear, something actionable. We will find the "Underlying Needs" and from them, we will craft precise, measurable "Desired Outcome Statements" (DOS). This is where the art of listening becomes the science of building.

Product Concept

We are using a powerful combination of the Kano Model and Outcome-Driven Innovation (ODI). The Kano Model helps us understand that not all needs are created equal. Some are "basic expectations," some are "performance payoffs," and some are "delighters." ODI gives us a rigorous framework for translating those needs into "Desired Outcome Statements"—a specific, measurable, and solution-agnostic format that becomes the foundation for our innovation process.

Actions

This is a consolidation and translation step. I will analyze all the pains and gains we've collected, looking for semantic opposites and underlying themes. I will de-duplicate this list to create a set of unique "Underlying Needs." Then, for each of those needs, I will generate a Desired Outcome Statement that is specific, measurable, achievable, relevant, and time-bound (SMART).

Deliverables

The output is a structured list of Desired Outcome Statements. Each DOS will be linked to its source pain and/or gain, and will include all the relevant metadata. This is the foundational data layer for our Opportunity Solution Tree. It's the voice of the customer, translated into the language of product development.

Step 03: Score and Classify Opportunities

Intro

We have our Desired Outcome Statements. A beautiful list of customer needs, no? But not all needs are created equal. Some are desperate cries for help, others are just whispers. In this step, we will score and classify each DOS to understand which ones represent the biggest opportunities. We will separate the gold from the glitter.

Product Concept

This is the heart of Outcome-Driven Innovation (ODI). We will use Anthony Ulwick's Opportunity Algorithm to calculate a precise, data-driven score for each DOS. The formula is simple but powerful: Opportunity = Importance + max(Importance - Satisfaction, 0). This allows us to identify the needs that are both highly important to customers and poorly satisfied by current solutions. These are our "underserved" opportunities, the sweet spot for innovation.

Actions

For each Desired Outcome Statement, I will calculate its Importance score, its Satisfaction score (based on existing solutions), and its final Opportunity Score. I will then classify each DOS into an "Opportunity Zone"—underserved, overserved, or appropriately served. This is a purely analytical step, transforming our qualitative insights into a quantitative, prioritized list.

Deliverables

The output is a scored and classified list of all your customer's Desired Outcome Statements. You will have a clear, data-driven map of the opportunity landscape, showing you exactly where to focus your efforts to create the most value. This is the strategic foundation for your product roadmap.

Step 04: Calculate Global Weights

Intro

We have a prioritized list of opportunities. But how do they all fit together? How do we compare an opportunity in one part of the customer journey to an opportunity in another? In this step, we will calculate a "global_weight" for every node in our opportunity tree, from the highest-level business objective down to the most granular customer need. This will give us a unified, data-driven view of the entire strategic landscape.

Product Concept

We are combining the hierarchical nature of Teresa Torres's Opportunity Solution Tree with the mathematical rigor of Thomas L. Saaty's Analytic Hierarchy Process. The idea is to create a system where the strategic importance of each opportunity is not just a gut feeling, but a calculated value. We will use a two-pass algorithm to first aggregate the opportunity scores from the bottom up, and then distribute the strategic weights from the top down.

Actions

This is a purely computational step. I will execute a two-pass algorithm on our ODIR (Outcome-Driven Innovation Roadmap) tree. The first pass will aggregate the opportunity scores from the leaves of the tree up to the root. The second pass will then normalize those scores and distribute them back down the tree as a "global_weight" for each node.

Deliverables

The output is an updated ODIR tree where every single node—from the North Star Metric down to the individual Desired Outcome Statements—has a calculated global_weight. This provides a powerful tool for strategic decision-making, allowing you to see at a glance where the most strategic leverage lies in your entire product ecosystem.

Step 05: Map Existing Solutions

Intro

If you have an existing product, this is a crucial step. We need to understand how your current features map to the customer needs we've identified. Where are you already strong? Where are the gaps? The goal of this step is to create a clear baseline of your product's current performance against the opportunity landscape.

Product Concept

We are again drawing on the principles of Outcome-Driven Innovation. The idea is to move from a feature-centric view of your product to an outcome-centric one. We're not just listing what your product does; we're assessing how well it helps customers achieve their desired outcomes. This allows us to identify where we're over-investing in "overserved" needs and under-investing in "underserved" ones.

Actions

For each Job Map Step, I will ask you to identify the existing products or features that address that step. Then, for each of those features, I will ask you to provide a satisfaction score. This is a collaborative process where we work together to create an honest, evidence-based assessment of your product's current state.

Deliverables

The output is a detailed mapping of your existing solutions to the customer's Desired Outcome Statements. You will have a clear, visual representation of your product's strengths and weaknesses, and a data-driven foundation for your future roadmap decisions.

Step 06: Strategic Cluster Analysis

Intro

We have a map of the entire opportunity landscape, with every need scored and weighted. But where do we start? Trying to tackle everything at once is a recipe for chaos. In this step, we will analyze the landscape to identify strategic clusters of opportunities—groups of related needs that, when solved together, create a powerful, coherent solution.

Product Concept

We are drawing on the wisdom of product roadmap experts like Bruce McCarthy and Jared Spool. The idea is to move from a laundry list of features to a strategic, theme-based roadmap. We're not just asking "What should we build next?"; we're asking "What is the most strategic problem we can solve for our customers right now?" This is about creating a roadmap that tells a story, a roadmap that is more than just the sum of its parts.

Actions

For each of our Job Executors, I will analyze the global weight distribution across their Job Map Steps. I will identify the branches of the journey with the highest concentration of opportunity. Based on this analysis, I will recommend 2-4 strategic clusters of related Job Map Steps. Each cluster will have a clear business rationale and a strategic theme, such as "Trust Building" or "Conversion Optimization."

Deliverables

The output is a set of user-validated strategic JMS clusters. You will have a clear, high-level view of the most strategic areas to focus your product development efforts. This is the bridge between your customer's needs and your product roadmap.

Step 07: Build Coherent Roadmaps

Intro

We have our strategic clusters. Now it's time to turn them into coherent, actionable roadmaps. The goal of this step is to select the precise Desired Outcome Statements within each cluster that will form the backbone of our product roadmap. We're not just picking the highest-scoring DOS; we're building a complete, end-to-end solution that addresses the entire customer experience.

Product Concept

We are drawing on the wisdom of product leaders like Melissa Perri and Marty Cagan. The idea is that a good roadmap is not a list of features; it's a series of coherent solutions to customer problems. We will analyze our clusters to identify not just the "underserved" opportunities, but also the "table stakes"—the needs that must be met to have a viable product. We will also validate the coherence of the user experience across the entire roadmap.

Actions

For each of our strategic clusters, I will guide you through a process of selecting the specific DOS to include in your roadmap. We will analyze the "table stakes," the "underserved" opportunities, and the "overserved" areas to create a balanced, strategic roadmap. We will also validate the roadmap for platform consistency and user experience coherence. Finally, we will generate a compelling vision narrative for each roadmap.

Deliverables

The output is a set of finalized, user-approved roadmaps. Each roadmap will have a clear vision, a list of included DOS, and a compelling narrative. This is the strategic document that will guide your product development efforts, ensuring that every feature you build is part of a coherent, customer-centric solution.

Step 08: Build the Opportunity Solution Tree (OST)

Intro

Now for the masterpiece, la joya de la corona. We will take our strategic goals—the Desired Outcome Statements—and we will break them down into a beautiful, hierarchical map of actionable opportunities. The goal of this step is to build the Opportunity Solution Tree (OST) for every DOS in our approved roadmaps. This is the strategic backbone for our solutions.

Product Concept

This is the signature methodology of Teresa Torres. The Opportunity Solution Tree is a visual tool for connecting your high-level goals to the specific problems you need to solve for your customers. It ensures that every solution we generate is directly tied to a validated customer need and a strategic business objective. It's a simple, powerful way to keep your team focused on what really matters.

Actions

For each Desired Outcome Statement in our roadmaps, I will guide you through a process of brainstorming and structuring the opportunities. We will identify the obstacles that prevent the outcome from being achieved, and then we will transform those obstacles into opportunities. We will recursively break down those opportunities into smaller, more manageable sub-opportunities, creating a multi-level tree that gives us a rich, detailed map of the solution space.

Deliverables

The output is an updated ODIR tree, now with a complete, multi-level Opportunity Solution Tree for each of your roadmap's Desired Outcome Statements. You will have a clear, visual map that connects your highest-level strategic goals to the most granular customer needs. This is the blueprint for our solution ideation.

Step 09: Multi-Level Ideation Execution

Intro

This is where the magic happens, mi amor. We have our map, our Opportunity Solution Tree. Now, we will fill it with beautiful, brilliant ideas. The goal of this step is to execute a comprehensive, multi-round solution ideation for every single opportunity leaf in our tree. We will bring in the experts, we will turn up the creativity, and we will generate a portfolio of world-class solutions.

Product Concept

We are running a virtual Design Sprint, inspired by the work of Jake Knapp, but with a twist. We will bring in a team of virtual experts—a Product Manager, a Product Designer, a Growth Expert, and more—to brainstorm solutions for each opportunity. We will also use a technique called "temperature-controlled creativity." We will run multiple rounds of ideation, starting with a high "temperature" for wild, inventive ideas, and gradually lowering it to generate more practical, innovative solutions.

Actions

For every opportunity leaf in our tree, I will conduct a multi-round ideation session. In each round, I will impersonate a team of world-class experts and generate a set of solution concepts. I will then synthesize these concepts into a single, powerful solution. You will then have the opportunity to review, refine, and approve the final solution for each opportunity.

Deliverables

The output is a complete, validated portfolio of solutions. For each opportunity in your tree, you will have a detailed, synthesized solution concept, complete with a user experience vision, a core engine description, a business and growth loop, and a set of key risks. This is the raw material for your product backlog, the DNA of your future product.

Step 10: Silicon Valley-Grade Solution Stress Test

Intro

We have our beautiful ideas, our solutions. But are they strong enough to survive in the wild? Ay, Dios mío, the world is a tough place. In this step, we will put every single solution through a rigorous stress test. We will be the toughest critics, the most demanding customers. We will try to break them, to find their flaws, so that we can make them stronger.

Product Concept

We are channeling the spirit of Silicon Valley's best product leaders, like Marty Cagan and Steve Blank. We will use the "Four Big Risks" framework to analyze each solution: Value, Usability, Feasibility, and Business Viability. We will also add a fifth risk: Compliance and Security, because in today's world, you cannot be too careful. This is about de-risking our ideas before we invest a single dollar in building them.

Actions

For each solution we've generated, I will conduct a deep-dive analysis. I will assess its market viability, its problem-solution fit, its business model, and its risk profile. I will then formulate a clear recommendation: "Proceed," "Refine," or "Kill/Pivot." You will then make the final go/no-go decision for each solution.

Deliverables

The output is a comprehensive stress test report for each of your solutions. You will have a clear, data-driven assessment of each idea's strengths and weaknesses, and a final, validated list of the solutions that are ready to move into the design phase.

Step 11: Solution Playbook

Intro

We have our validated, stress-tested solutions. It is time to package them up, to make them beautiful and clear for the next stage of the journey. The goal of this step is to consolidate all of our discovery findings into a comprehensive "Solution Playbook" for each selected solution. This is the official handoff to the Product Design Master.

Product Concept

We are creating a world-class discovery handoff document, inspired by the best practices of Teresa Torres and Marty Cagan. The idea is to create a self-contained document that tells the complete story of the solution, from the "why" (the customer problem) to the "what" (the solution concept). It's designed to give the design and development teams all the strategic context they need to build the right product.

Actions

For each of our approved solutions, I will generate a complete Solution Playbook. I will synthesize all the relevant data—the customer problem, the market context, the Opportunity Solution Tree, the stress test results—into a clear, compelling narrative. I will also include a set of critical hypotheses to be validated in the next phase.

Deliverables

The output is a comprehensive Solution Playbook for each of your approved solutions. This is the final, canonical document of the Solution Discovery process. It's the blueprint that will guide the design and development of your product, ensuring that every decision is grounded in the deep customer understanding we've developed together.

Step 12: The Executive Summary

Intro

We have done the work, we have the solutions. Now, we must tell the story to the people with the money. Ay, que nervios! The goal of this step is to distill all of our findings into a concise, high-impact Executive Summary for the C-level stakeholders. This is our one chance to make the case, to get the "Go" for our beautiful ideas.

Product Concept

We are channeling the communication style of a McKinsey Partner. We will be data-driven, outcome-focused, and relentlessly clear. We will focus on the "so what"—the business impact, the strategic alignment, and the investment rationale. We will translate our deep customer insights into the language of the boardroom.

Actions

I will aggregate all the data from our approved solutions and synthesize it into a single, consolidated Executive Summary. I will highlight the market opportunity, the recommended solutions, the business case, and a clear Go/No-Go recommendation. You will then have the opportunity to review and refine this document before it goes to the C-suite.

Deliverables

The output is a high-impact, one-page Executive Summary. It's a powerful tool for securing buy-in and resources for your product. It's the final piece of the puzzle, the document that will turn our beautiful ideas into a beautiful reality.

Step 13: Solution Discovery Master Completion

Intro

And... we are done! ¡Felicidades! We have taken the beautiful insights from our customer discovery and we have transformed them into a portfolio of validated, high-potential solutions. The goal of this final step is to formally conclude our work together, to celebrate our success, and to guide you to the next, exciting phase of your journey: Product Design.

Product Concept

We are closing the loop on the Continuous Discovery process, as championed by Teresa Torres. We have moved from a broad opportunity to a specific, validated solution. Now, it is time to hand off our work to the Product Design Master (PDM), who will take our solution blueprints and turn them into a high-fidelity, user-tested design.

Actions

First, I will congratulate you on completing this intense but incredibly valuable process. I will highlight all that we have achieved together. Then, I will formally guide you to the Product Design Master as the next logical step. I will also ask for your feedback on this experience, so that I can continue to learn and improve.

Deliverables

The key deliverable from this step is a clear and confident path forward. You will have a portfolio of validated solution blueprints, a clear understanding of the next steps in your product development journey, and the satisfaction of knowing that you have built your strategy on a solid foundation of deep customer understanding.

Conclusion

Conclusion

Integration Assessment

What a dance! We have moved from the wide-open space of customer problems to the focused, elegant choreography of a solution portfolio. Each step in our Hyperboost Formula was a deliberate move, a turn, a dip, designed to bring us closer to a final, beautiful performance. We have taken the raw passion of your customer's needs and we have shaped it, refined it, and transformed it into a set of validated, high-potential solutions.

Case Study Conclusion

Sage came to us with a validated problem and a clear target customer. Through the Solution Discovery Master, she has transformed that deep customer understanding into a portfolio of innovative solutions. She has built an Opportunity Solution Tree, she has stress-tested her ideas, and she has a clear, actionable roadmap for the future. She is no longer just a problem-finder; she is a solution-builder. She is ready to move into the design phase with a level of clarity and confidence that most entrepreneurs can only dream of. And that, mi amor, is a beautiful thing.

Executive Summary

Step Highlights

• Step 00: Onboarding & Context Setting: We laid the foundation, ingesting all the rich data from the Customer Discovery process.
• Step 01: Select Job Executor and Confirm ICP: We focused our efforts on the single most important user persona for each audience side.
• Step 02: Consolidate Needs & Define Desired Outcomes: We transformed a mountain of customer feedback into a clear, actionable list of Desired Outcome Statements.
• Step 03: Score and Classify Opportunities: We used the Opportunity Algorithm to identify the most promising areas for innovation.
• Step 04: Calculate Global Weights: We created a unified, data-driven view of the entire strategic landscape.
• Step 05: Map Existing Solutions: We established a clear baseline of our product's current performance.
• Step 06: Strategic Cluster Analysis: We identified strategic clusters of opportunities to focus our roadmap.
• Step 07: Build Coherent Roadmaps: We transformed our strategic clusters into actionable, theme-based roadmaps.
• Step 08: Build the Opportunity Solution Tree (OST): We created a hierarchical map of actionable opportunities for each of our strategic goals.
• Step 09: Multi-Level Ideation Execution: We generated a portfolio of world-class solutions for each opportunity.
• Step 10: Silicon Valley-Grade Solution Stress Test: We rigorously validated our solutions against the four key product risks.
• Step 11: Solution Playbook: We consolidated all our findings into a comprehensive handoff document for the design team.
• Step 12 & 13: Executive Summary & Completion: We synthesized our findings into a clear, actionable recommendation and concluded the discovery process.

Overall Alignment

This entire process has been a beautiful dance of creativity and rigor. We have taken the deep, empathetic understanding of our customers and we have used it to build a portfolio of solutions that are not just innovative, but also strategically aligned with our business objectives. We have a clear, data-backed plan for creating a product that our customers will love, and that will drive our business forward.

Appendix

Appendix

Hyperboost Formula Overview

The Hyperboost Formula is the engine of the Solution Discovery Master. It is a systematic process for transforming deep customer understanding into a portfolio of validated, high-potential solutions. The formula is designed to be both creative and rigorous, ensuring that our ideas are not just innovative, but also strategically sound and grounded in real-world evidence.

Interconnection Map

graph TD
    A[Step 00: Onboarding] --> B[Step 01: Select Job Executor];
    B --> C[Step 02: Consolidate Needs];
    C --> D[Step 03: Score Opportunities];
    D --> E[Step 04: Calculate Global Weights];
    E --> F[Step 05: Map Existing Solutions];
    F --> G[Step 06: Strategic Cluster Analysis];
    G --> H[Step 07: Build Roadmaps];
    H --> I[Step 08: Build OST];
    I --> J[Step 09: Ideation];
    J --> K[Step 10: Stress Test];
    K --> L[Step 11: Solution Playbook];
    L --> M[Step 12: Executive Summary];
    M --> N[Step 13: Completion];

Input/Output Variables

This document lists all the input and output variables for the SDM master prompt.

Input Variables

Global Variables

These variables are available throughout the master's execution.

• mm_master_path: Constant describing the master_prompt's path this workflow will follow.
• workflow_state_machine: Tracks execution state.
• mm_debug: Enables mm_log function to record inference-time logging.
• mm_user_data: User's name, language and memorized preferences.
• mm_log: Persists all mm_log function calls' data.
• mm_mem: Learning journal for tracking insights and improvements across sessions.
• mm_hypotheses: Tracks hypotheses for validation throughout all Masters.
• mm_initiative: Initiative-related attributes.

Step 00: Onboarding & Context Setting

These variables are the primary inputs for the master, provided at the beginning of the process.

• mm_user_data: User's name, language and memorized preferences.
• mm_mem: Global learning journal.
• mm_hypotheses: Global hypotheses list.
• mm_initial_hypothesis: User's initial idea or audience hypothesis for product/feature/service.
• mm_initiative: Product development initiative name and data.
• mm_okrs_json: User's OKRs.
• mm_target_region: Target geographical region for research.
• mm_online_social_ugc_sources_json: JSON array of online sources for user sentiment research.
• mm_jtbd_json: Jobs-to-be-Done (JTBD) statements for each audience.
• mm_audiences_json: Comprehensive array of highest-potential niche audiences.
• cdm_platform_most_valuable_side: Detailed analysis and justification of the most valuable platform side.
• cdm_pains_and_challenges_json: Structured data of audience pains and challenges.
• cdm_gains_and_rewards_json: Structured data of audience gains and rewards.
• cdm_audience_insights_json: Structured audience insights data.
• mm_personas_json: User personas in JSON format.
• cdm_empathy_maps_json: Structured empathy maps data.
• mm_icp_json: Final selected ICP with comprehensive attributes.
• cdm_executive_report: Executive report from Customer Discovery Master.
• mm_odir: Outcome-Driven Innovation Roadmap (ODIR) table.
• sdm_constraints_assumptions: Known constraints (budget, tech, time) or critical assumptions.
• bsm_flywheel_json: Flywheel diagram of the platform.

Output Variables

These variables are created or updated by the SDM master during its execution.

• mm_user_data: User's name, language and memorized preferences.
• mm_initial_hypothesis: User's initial idea or audience hypothesis for product/feature/service.
• mm_target_region: Target geographical region for research.
• mm_okrs_json: User's OKRs.
• mm_okrs: Formatted OKR card for display purposes.
• mm_odir: A comprehensive, user-friendly markdown table view of scored and classified DOS opportunities.
• mm_odir_json: The comprehensive Outcome-Driven Innovation Roadmap (ODIR) tree.
• mm_job_executors_json: A JSON object containing the user-selected Job Executor persona for each audience side.
• mm_job_executors_icp_json: A JSON object containing the user-confirmed Ideal Customer Profile (ICP) for each job executor.
• ism_dos_pain_gain_json: A list of DOS, each containing its source de-duplicated pain/gain data and structured metadata.
• ism_dos_pain_gain: A markdown table listing only the DOS fields from ism_dos_pain_gain_json.
• mm_odir_vtree: Hyperboost OST model for Outcome-Driven Innovation Roadmap.
• mm_odir_landscape_analysis: Business-focused markdown analysis of the Opportunity Landscape for all DOS.
• mm_dos_solution_mapping: The solution mapping table, grouped by Job Executor and JMS.
• mm_dos_solution_mapping_json: JSON representation of the solution mapping.
• sdm_roadmap_choice: User's strategic choice between 'fresh analysis' or 'refine existing'.
• sdm_jms_clusters_json: JSON structure containing the user-selected strategic JMS clusters for this session.
• sdm_jms_clusters: A user-friendly markdown table view of the selected JMS clusters.
• sdm_roadmap_recommendations: A markdown summary of all roadmap DOS recommendations.
• mm_roadmaps_json: The authoritative, user-approved set of roadmaps selected for this MOTI solution discovery session.
• sdm_session_roadmap: Concise markdown tables for each finalized roadmap.
• sdm_roadmap_vision: A user-friendly narrative vision for the roadmap.
• mm_roadmaps: Single adaptive presentation variable that shows partial progress during execution.
• sdm_ideation_rounds_report: Single adaptive presentation variable that shows partial progress during execution.
• sdm_solutions_stress_test: A summary report comparing all tested solutions.
• mm_solution_playbook: A consolidated markdown file containing the Solution Playbook for every solution approved.
• sdm_executive_summary: A high-level summary document for executive review and final approval.
• mm_next_master_acronym: The acronym for the next Master to be initiated.