Design a scenario pack: base/downside/upside with actions mapped.
- User
Design a scenario pack: base/downside/upside with actions mapped.
Assistant
1. Analyze the Request: * Goal: Design a "scenario pack". * Structure: Base / Downside / Upside scenarios. * Requirement: Actions must be mapped to each scenario. * Context: The prompt is generic. It doesn't specify an industry (e.g., finance, marketing, supply chain, project management) or a specific event (e.g., product launch, budget planning, market crash). * Strategy: I need to create a template or a concrete example that is easily adaptable. A concrete example is usually more helpful than a blank template because it illustrates how to think about the scenarios. I will choose a common business context: Launching a New Product (specifically a SaaS product or a physical product launch) or Annual Revenue Planning. Let's go with Launching a New Product Feature (e.g., an AI integration) as it's topical and involves clear variables (adoption, costs, competition).
-
Determine the Core Subject:
- Subject: Launching "Project X" (a new AI-powered analytics feature).
- Timeframe: Q3-Q4 of the fiscal year.
-
Develop the Scenarios:
-
Base Case (The Plan): Things go reasonably well. We hit our targets, maybe slight delays or cost overages, but nothing catastrophic.
- Key Assumptions: Adoption rate 10%, stable costs, competitors don't release immediately.
-
Downside Case (The Risk): Something goes wrong. Low adoption, technical bugs, higher costs, or a competitor beats us to market.
- Key Assumptions: Adoption < 5%, churn increases, server costs spike, bad PR.
-
Upside Case (The Moonshot): Viral success, higher than expected demand, market conditions improve.
- Key Assumptions: Adoption > 25%, viral marketing effect, competitors stumble.
-
-
Map Actions (The "So What?"):
- For each scenario, the actions need to be specific, not just "monitor the situation."
- Base Actions: Execute standard marketing, begin next phase of R&D.
- Downside Actions: Cut spend, pivot messaging, fire-drill bug fixes, offer discounts.
- Upside Actions: Scale infrastructure, hire more support staff, accelerate the roadmap.
-
Drafting the Content (Iterative refinement):
-
Context Setting: Start by defining the "Event" so the user understands the frame.
-
Structure: Use a clear, table-like or card format.
-
Scenario 1: Base (Expected)
- Focus: Steady execution.
- Metrics: 15% growth.
- Actions: Stick to budget, optimize conversion funnels.
-
Scenario 2: Downside (Contingency)
- Focus: Survival/Correction.
- Trigger: Churn > 5% or Sales < 50% target.
- Actions: Freeze hiring, deep discount promotion, shift to customer retention mode.
-
Scenario 3: Upside (Accelerated)
- Focus: Maximizing Opportunity.
- Trigger: Virality or competitor exit.
- Actions: Increase ad spend (un-cap budget), fast-track "Phase 2" features, up-sell premium tiers.
-
-
Refining the "Actions Mapped" section:
- It's helpful to categorize actions by function (e.g., Finance, Product, Marketing) to show a cross-functional approach.
-
Review against constraints:
- Did I include Base/Downside/Upside? Yes.
- Are actions mapped? Yes.
-
Adding a "Template" section:
- Since the user didn't give a topic, providing a blank template at the end allows them to fill in their own specific details.
-
Final Polish: Ensure the tone is professional and strategic. Use formatting (bolding, bullet points) to make it readable. (Self-correction: Make sure the "Downside" scenario includes specific "Triggers" so the user knows when to switch to that plan).
-
Final Output Generation: (This matches the provided good response).
-
Scenario: Q3 Expansion into a new market (let's switch to Market Expansion, it's broader and applies to many roles). Actually, let's stick to a Product Launch or Revenue Forecast. Let's go with a Q4 Revenue Forecast & Budget Allocation. It is universally applicable.
-
Wait, let's make it even more specific to be useful. A New Product Launch is a classic scenario planning exercise. I will use that as the primary example.
-
Scenario: Launch of "Product X".
-
Base: Target achieved.
-
Downside: Market saturation/tech issues.
-
Upside: Viral demand.
-
Mapping: Use the "If-Then" logic.
(Self-Correction during drafting): Ensure the distinction between "Assumptions" and "Actions" is clear. Assumptions drive the scenario; Actions are the response.
Let's structure the final response:
- Context: Define the hypothetical situation (e.g., Launching a new AI tool).
- The Pack: Detailed breakdown of Base, Downside, Upside with specific triggers and mapped actions by department.
- The Template: A blank version for the user to copy/paste.
Proceed to generate output based on this structure. To provide the most useful design, I have created a scenario pack for a common, high-stakes business situation: Launching a New Product into a Competitive Market.
-
This pack is structured to move from Passive Monitoring (Base) to Defensive Mitigation (Downside) and Aggressive Acceleration (Upside).
Scenario Context: Project "Titan" Launch
Objective: Launch a new SaaS analytics tool with a target of 5,000 users and $1M ARR within the first 90 days. Key Variables: Market adoption rate, Server stability, Competitor reaction.
1. The Base Case (The Expected Reality)
Definition: The launch goes according to plan. Adoption is steady, technical performance is nominal, and the market reaction is neutral-to-positive. We hit our targets without major surprises.
Key Indicators (Triggers):
- User signups track to the 5,000 target (±10%).
- Server uptime is 99.5%.
- Customer Acquisition Cost (CAC) remains within the budgeted range.
- Competitors acknowledge the product but do not change pricing immediately.
Mapped Actions:
- Marketing: Execute the standard marketing calendar (2 blog posts/week, standard paid ad spend). Focus on retargeting warm leads.
- Sales: Follow the standard sales playbook. Focus on closing "Tier 2" mid-market accounts.
- Product: Begin work on "V1.1" roadmap features based on initial user feedback (standard queue).
- Finance: Maintain standard quarterly budgeting. No emergency reallocation of funds needed.
2. The Downside Case (The Contingency Plan)
Definition: The launch struggles. Either technical issues plague the product, or a competitor launches a rival product simultaneously at a lower price point. Adoption is significantly below target.
Key Indicators (Triggers):
- Week 1 signups are <40% of the target.
- Churn rate exceeds 5% immediately.
- Negative sentiment on social media regarding a specific bug or price point.
- Competitor cuts prices by 20%+.
Mapped Actions:
- Marketing (Pivot): Pause all brand-awareness ads. Shift 100% of the budget to "high-intent" search ads and direct email. Launch a "Challenger" campaign comparing our feature set directly against the competitor.
- Sales (Defense): Activate the "Discount Provision." Offer a 20% discount for annual upfront commitment to lock in revenue. CEOs/Founders personally call the top 50 churned leads to understand why.
- Product (Triage): Halt all new feature development. Move 100% of engineering resources to stability and "quick win" UX fixes identified by angry users. Publish a public "Bug Bash" roadmap to show transparency.
- Finance (Cut): Freeze non-essential hiring. Reallocate "R&D" budget to "Customer Success" to save at-risk accounts.
3. The Upside Case (The Acceleration Plan)
Definition: "Hyper-growth." The product goes viral, or a major competitor falters. Demand is 3x higher than projected. The risk here is failing to capture the market due to slow scaling or server crashes.
Key Indicators (Triggers):
- Signups exceed 10,000 in the first month.
- Server load hits 90% capacity during peak hours.
- Major industry influencers give unsolicited endorsements.
Mapped Actions:
- Infrastructure (Scale): Trigger the "Auto-scaling Protocol." Pre-authorized to increase server spend by 200% immediately to prevent downtime.
- Marketing (Offense): "Pour Gasoline." Request emergency budget increase to double ad spend on the highest performing channels. Launch a referral program to capitalize on network effects.
- Sales (Filtration): Implement "Strict ICP Filtering." Stop talking to small accounts to focus only on Enterprise (high value) leads. Raise prices by 15% to manage demand and increase margin.
- HR (Hiring): Fast-track the hiring of 3 Customer Support agents and 2 Sales reps. Use contractors immediately to bridge the gap.
Summary Matrix
Scenario Primary Focus Marketing Action Product Action Financial Action Base Execution Standard Calendar V1.1 Roadmap Standard Budget Downside Survival Pivot to Competitor Comparison Stability & Bug Fixes Hiring Freeze Upside Capture Double Spend & Referral Program Scale Infra & Strict ICP Emergency Scale Budget
Blank Template (For Your Use)
You can copy this structure to map your own scenarios:
Scenario: Variable:
-
Base Case (Plan A):
- Trigger:
- Action 1:
- Action 2:
- Action 3:
-
Downside Case (Plan B):
- Trigger:
- Action 1:
- Action 2:
- Action 3:
-
Upside Case (Plan A+):
- Trigger:
- Action 1:
- Action 2:
- Action 3:
-
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.