How to create optimistic, baseline, and conservative plan variants for your Key Results — and switch between them instantly when conditions change.
The Paroblem with Single-Point Plans
Every OKR plan is a prediction. It says: given what we know today, here’s how we expect progress to unfold across the quarter. The trouble is that “what we know today” changes. And a plan that embeds a single prediction about the future is fragile by design — the moment the prediction is wrong, the entire plan becomes an artifact of a world that no longer exists.
Scenario planning addresses this fragility by building multiple predictions in advance. Instead of one plan, you create three: an optimistic variant (things go better than expected), a baseline variant (things go roughly as expected), and a conservative variant (things go worse than expected). Each variant has its own distribution curve, its own incremental targets, and its own implicit story about what the quarter will look like.
The value of scenario planning isn’t in predicting which scenario will happen — none of them will unfold exactly as designed. The value is in pre-thinking the plan modifications. When a signal appears in week three that says “the optimistic case isn’t materializing,” the team doesn’t need to figure out what the new plan looks like. They switch to the baseline variant. The thinking was done upfront.
Scenario planning is pre-computed plan modification. Instead of modifying on the fly when signals appear, you’ve already done the analysis. The signal triggers a switch, not a scramble.
The Three-Scenario Model
Keep it simple. Three scenarios are enough for most KRs. More than three creates analysis overhead without meaningfully improving decision-making. Fewer than three doesn’t give you enough range.
Optimistic (Best Case)
This scenario assumes that key uncertainties resolve favorably. The dependency ships on time. The product launch lands well. The market is receptive. Capacity is fully available. The plan is more front-loaded and more aggressive than baseline.
-
Typical target: 110–130% of the baseline target.
-
Typical shape: Front-loaded or steep S-curve. The optimistic plan assumes early momentum that carries through the quarter.
-
Trigger to activate: First two to three check-ins significantly exceed baseline plan (more than 15% above for two consecutive periods).
Baseline (Expected Case)
This is your default operating plan. It reflects the team’s honest assessment of what’s achievable given current conditions, known risks, and realistic capacity. This is the plan that lives in Profit.co and that check-ins are measured against.
-
Typical target: 100% of the committed target.
-
Typical shape: The distribution shape that best matches the KR’s execution dynamics (S-curve, back-loaded, step function, etc.).
-
Trigger to activate: This is the default. No trigger needed unless you switched to another scenario and conditions revert.
Conservative (Downside Case)
This scenario assumes that one or more key risks materialize. The dependency slips. The product launch underperforms. A key resource is unavailable. The plan is more back-loaded and the total target is reduced.
-
Typical target: 70–90% of the baseline target.
-
Typical shape: Back-loaded or plateau-and-ramp. The conservative plan assumes slower early progress and a compressed delivery window.
-
Trigger to activate: First two to three check-ins significantly miss baseline plan (more than 20% below for two consecutive periods), or a specific risk event materializes.
Building Scenario Variants in Practice
Creating three scenario variants sounds like three times the planning work. It’s not. If you build the baseline plan properly, the other two variants are 10-minute derivations.
Step 1: Build the Baseline Plan
This is your normal planning process. Set the KR, define the From/To range, choose the distribution shape, and customize the plan in Profit.co. This is the plan that goes live.
Step 2: Define the Key Uncertainties
For each KR, identify the one to three uncertainties that most affect the plan’s achievability. These are the variables that distinguish the optimistic case from the conservative case.
| KR | Key Uncertainty | Optimistic Resolution | Conservative Resolution |
|---|---|---|---|
| Grow trial conversion to 14% | New onboarding flow launch date | Launches on time (Mar 1). Full month of impact. | Delayed to Mar 15. Only two weeks of impact. |
| Close $8M in new ARR | Enterprise pipeline quality | Pipeline converts at 25% (historical high). | Pipeline converts at 15% (historical low). |
| Hire 8 engineers by Q2 end | Offer acceptance rate | 6 of 8 offers accepted on first round. | Only 4 accepted. Two positions require second search. |
| Reduce churn to <3% | Key account health | Top 5 at-risk accounts retained. | 2 of 5 at-risk accounts churn in month 2. |
Step 3: Derive the Optimistic Variant
Take the baseline plan and adjust for the optimistic resolution of each uncertainty. In Profit.co, this is a quick AI-assisted exercise:
-
Open the baseline plan in Modify Plan.
-
Tell the AI: “Create an optimistic variant. Assume [the onboarding flow launches on time]. Increase the March ramp by 20%. Set the total target to [optimistic number].”
-
Review the preview. Note the key differences from baseline: where the curve is steeper, which months carry more weight.
-
Record the variant in your scenario planning document. You’re not saving this as the active plan — the baseline stays active. The optimistic variant is stored as a reference for quick switching later.
The easiest way to store the variant is to screenshot the plan table preview or note the per-period targets in a simple spreadsheet. When the time comes to switch, you’ll paste these values into Profit.co using the AI import.
Step 4: Derive the Conservative Variant
Same process, opposite direction:
-
Open the baseline plan.
-
Tell the AI: “Create a conservative variant. Assume [the onboarding flow is delayed to Mar 15]. Reduce March targets by 30%. Set the total target to [conservative number].”
-
Review. Note the key differences.
-
Record the variant alongside the optimistic one.
The total effort for creating all three variants: about 15 minutes per KR. Build the baseline in your normal planning time. Derive the other two in 5–7 minutes each using the AI assistant. For a team with 10 KRs, that’s about 2.5 hours of scenario planning for the entire quarter.
Scenario Triggers: When to Switch
The most critical element of scenario planning is defining the trigger conditions in advance. A trigger is a specific, observable condition that tells you it’s time to switch from one scenario to another. Without pre-defined triggers, scenario planning is just intellectual exercise — three plans that sit in a drawer until the QBR.
Designing Good Triggers
A good trigger is specific, measurable, and time-bound. Compare:
| Bad Trigger | Why It’s Bad | Good Trigger |
|---|---|---|
| “If things aren’t going well.” | Subjective. Different people will interpret this differently. No clear threshold. | “If check-in actuals are >20% below baseline plan for two consecutive periods.” |
| “If the launch is delayed.” | Binary but lacks specificity. How delayed? One day? Three weeks? | “If the launch date moves past March 10 (more than 10 days from original).” |
| “If pipeline is strong.” | Vague. Strong compared to what? | “If pipeline conversion exceeds 22% by the end of month 1 (vs. 18% baseline assumption).” |
Trigger Timing
Triggers should be evaluatable at each check-in. The weekly check-in is the natural evaluation point: enter the number, compare to plan, check the trigger conditions. If a trigger fires, the scenario switch happens during that same check-in session — not at the next team meeting.
Most triggers will be evaluated and not fired. That’s fine. The value is in having the switch ready when it’s needed. A trigger that fires at check-in #4 and results in a plan switch within 30 minutes is infinitely better than a gradual realization at check-in #8 that the plan has been wrong for a month.
Executing the Scenario Switch
When a trigger fires, the switch from the active plan to the appropriate variant should take under two minutes. Here’s the execution workflow:
-
Trigger fires at check-in. The KR owner recognizes that the trigger condition for the conservative (or optimistic) variant is met.
-
Open Modify Plan and the AI panel.
-
Paste the variant’s values from the scenario planning document, or tell the AI: “Switch to conservative variant. Reduce the To target to [X]. Redistribute with a back-loaded shape: [monthly breakdown].”
-
If the switch involves a target change, the inline From/To editing handles it. If only the distribution changes, the AI reshapes the curve.
-
Review the preview. The diff view shows old baseline values struck through, new variant values in blue.
-
Apply and save. Document in the check-in note: “Scenario trigger fired: [condition met]. Switched from baseline to conservative variant. New Q1 target: [X]. Rationale: [brief explanation].”
If the plan is hierarchical, cascade the change to child plans using the propagation rules.
The scenario switch is not a meeting. It’s a check-in action. The KR owner sees the trigger, executes the switch, and documents it — all within the check-in workflow. If the switch requires a target change that affects the hierarchy, the communication protocol described in the dependency framework applies: notify downstream teams within 24 hours.
Scenario Planning at the Hierarchical Level
Scenario planning becomes especially powerful in hierarchical OKR structures. When a parent KR has three scenario variants, the cascade to child KRs creates a coherent organizational response to changing conditions.
Top-Down Scenario Cascade
When the CEO switches the company-level revenue KR from baseline to conservative, the reduced target cascades proportionally to department-level KRs. Each department’s plan automatically adjusts. The VP of Sales sees a reduced Q2 allocation; the VP of Marketing sees a revised pipeline expectation. The cascade preserves the distribution shape at each level while scaling the absolute values down.
This is massively more efficient than having each department independently assess the impact of the conservative scenario. The parent switch is a single action; the cascade is automatic.
Bottom-Up Scenario Signals
The reverse also works. If three out of four department-level KRs have switched to their conservative variants based on their own triggers, the aggregated bottom-up view will show a gap with the company-level baseline plan. This gap is a signal to the CEO: the organization’s ground-level assessment has shifted, and the company-level plan may need to follow.
This bottom-up signal is more reliable than any single top-level analysis because it’s grounded in the collective assessment of teams closest to execution. When multiple teams independently trigger conservative scenarios, the probability that the company baseline is still valid drops significantly.
Common Scenario Planning Mistakes
| Mistake | Why It’s Harmful | The Fix |
|---|---|---|
| Creating scenarios but no triggers | Without triggers, switching is a judgment call that gets deferred. The conservative plan exists but is never activated until the QBR. | Define specific, measurable triggers during the scenario creation process. No trigger = no scenario. |
| Making the conservative case too conservative | If the conservative target is 40% of baseline, it feels defeatist. Teams resist switching because it feels like giving up. | Conservative should be 70–90% of baseline. It’s a realistic downside, not a catastrophe. Save the catastrophe scenario for enterprise risk management, not OKR planning. |
| Making the optimistic case the baseline | Setting the baseline at the stretch number and calling it “expected.” The conservative variant then becomes what the baseline should have been. | The baseline should be your honest best estimate — not the number you’d be proud to hit, but the number you actually expect to hit. Optimistic is the proud number. |
| Maintaining scenarios for every KR | Creating three variants for 50 KRs is 150 plans to track. The overhead kills the value. | Only create scenarios for KRs with significant uncertainty — typically 20–30% of KRs. Operational KRs with stable trajectories don’t need scenarios. |
| Never switching back to baseline | The team switches to conservative in week 4 and stays there even when conditions improve in week 8. | Triggers should work both ways. If the conservative trigger fires at week 4, the baseline trigger should be evaluatable at every subsequent check-in. If conditions revert, switch back. |
The Scenario Planning Template
Here’s a lightweight template for documenting scenario variants for a single KR. Fill this out during your quarterly planning session, store it alongside the KR in Profit.co, and reference it at each check-in.
| Element | Optimistic | Baseline | Conservative |
|---|---|---|---|
| Target (To value) | [Optimistic number] | [Baseline number] | [Conservative number] |
| Key assumption | [What goes right] | [What we expect] | [What goes wrong] |
| Distribution shape | [e.g., front-loaded] | [e.g., S-curve] | [e.g., back-loaded] |
| Monthly breakdown | [Jan/Feb/Mar split] | [Jan/Feb/Mar split] | [Jan/Feb/Mar split] |
| Switch trigger | [Specific condition] | [Default — no trigger] | [Specific condition] |
| Trigger evaluation point | [Which check-in #] | [—] | [Which check-in #] |
| Cascade impact | [List affected child KRs] | [—] | [List affected child KRs] |
Keep this template to one page per KR. The goal is a quick-reference document that a KR owner can scan at check-in time to evaluate triggers and, if needed, execute a switch in under two minutes. If the scenario documentation requires more than one page, it’s too complex to be operational.
When Scenario Planning Is Worth the Effort
Scenario planning has a cost: the upfront time to build variants and define triggers. That cost is worth paying for KRs that meet one or more of these criteria:
-
High uncertainty. The KR depends on assumptions that could plausibly resolve in multiple ways. If the most likely outcome has less than 60% probability, scenario planning adds value.
-
High consequence. The KR is financially material, strategically critical, or visible to the board. A miss on this KR has outsized organizational impact.
-
Long lead time to modify. If the plan modification for a downside scenario is complex (target reduction, hierarchical cascade, resource reallocation), pre-building the variant saves days of reactive scrambling.
-
Multiple teams affected. If a scenario change on this KR cascades to three or more teams, the coordination cost of a reactive modification is high. Pre-defined variants with pre-communicated triggers reduce the coordination to a single announcement.
For KRs that don’t meet these criteria — stable operational metrics, low-uncertainty deliverables, single-team scope — the baseline plan with the 72-Hour Rule for reactive modifications is sufficient. Don’t scenario-plan everything. Scenario-plan the things that keep you up at night.
The Speed of the Switch Is the Point
The value of scenario planning isn’t in the quality of the scenarios. It’s in the speed of the switch. An organization that takes two weeks to recognize a downside signal and another two weeks to build a revised plan has lost a month. An organization that pre-built the conservative variant and defined the trigger can switch in 30 seconds at check-in time.
That month of difference is the difference between a team that’s been executing against a wrong plan for four weeks and a team that’s been executing against the right plan since the signal appeared. Same reality. Dramatically different outcomes.
You can’t predict the future. But you can pre-compute your response to the three most likely versions of it. That’s scenario planning for OKRs: not prediction, but preparation. Not three plans, but three speeds of response.
Pre-build your plan variants. Switch in seconds.
Profit.co’s AI assistant makes creating scenario variants a 5-minute exercise and switching between them a 30-second action. Build your response before you need it. Start your free trial.