IF and WHEN: Decision-Making Strategies for Uncertain Outcomes

IF and WHEN — How to Plan for Contingencies and Deadlines

Overview

IF covers possible events that may or may not occur. WHEN covers timing for events that are expected to happen. Planning well separates contingency options (IF) from schedule commitments (WHEN), so you can prepare resources without overcommitting.

Step-by-step planning method

1. Define the core goal

   • State the outcome you want (deliverable, milestone, decision).

2. List IF cases (contingencies)

   • Identify what could prevent or change the plan (risks, dependencies, unknowns).
   • Use bullets; aim for 5–10 plausible scenarios.

3. Classify each IF by probability and impact

   • High/Medium/Low for probability.
   • High/Medium/Low for impact.
   • Prioritize contingencies that are high in either dimension.

4. Assign responses for each IF

   • Avoid: change plan to eliminate risk.
   • Mitigate: reduce probability or impact.
   • Accept: no action; monitor.
   • Transfer: outsource or insure.

5. Set WHEN triggers and deadlines

   • Define exact conditions that convert an IF into action (e.g., “If vendor misses 3 deliverables”).
   • Set firm dates for expected milestones and soft dates for contingent actions.
   • Use time buffers: add contingency padding (e.g., 10–25% of task duration) based on risk level.

6. Allocate resources and owners

   • Assign a single owner for each contingency response and each milestone.
   • Pre-commit minimal standby resources for high-probability/high-impact IFs.

7. Create monitoring and decision rules

   • Define metrics and check-in cadence (daily/weekly/monthly).
   • Use clear decision rules: who decides, by when, with what data.

8. Document fallback plans

   • Short, actionable steps to execute if a WHEN trigger fires.
   • Include contact lists, quick budgets, and step-by-step actions.

9. Communicate status and expectations

   • Share milestones and contingency plans with stakeholders.
   • Make IF/WHEN distinctions explicit in status reports.

10. Review and iterate

    • After each major milestone or triggered contingency, run a quick retrospective and update plans.

Practical examples

• Project launch:

  • IF: Key vendor delay (probability: medium, impact: high). WHEN trigger: vendor misses acceptance test by X date. Response: switch to backup vendor pre-vetted; allocate 2-week buffer.
  • WHEN: Launch date — firm. Actions tied to it: marketing rollout, customer notifications.

• Personal finance:

  • IF: Emergency expense >$2,000 (probability: low, impact: high). WHEN trigger: expense occurs. Response: use emergency fund (cover 3 months expenses), pause discretionary spending.
  • WHEN: Mortgage payment due on 1st each month — fixed; ensure auto-pay set.

Quick templates

• Contingency register (one-line per IF)

  • IF: [event] | Probability: [H/M/L] | Impact: [H/M/L] | WHEN trigger: [condition/date] | Owner: [name] | Response: [avoid/mitigate/accept/transfer]

• Milestone timeline

  • WHEN: [milestone/date] | Owner | Key deliverables | Buffer | Contingency link

Key principles (brief)

• Separate possibility (IF) from timing (WHEN).
• Make triggers explicit so decisions are objective.
• Pre-assign owners and minimal resources for fast response.
• Use buffers proportional to risk, not guesswork.
• Communicate clearly so stakeholders understand contingency limits.

If you want, I can convert this into a one-page contingency register template or a 30/60/90-day WHEN timeline for a specific project—tell me the project type and I’ll produce it.