Week 48 Day 6: Planning Is Essential, Plans Are Useless

The monthly roadmap review takes 30 minutes. Check the milestones: are we on track? What has changed in the business context? Do the three priorities still make sense? If something needs to change, change it explicitly -- update the document, communicate the change, and explain the reasoning. The worst outcome is an unchanged roadmap that no one follows.

Here is the monthly review process and the discipline of adaptive planning. The monthly review has four questions. Question one -- milestone check: for each priority, are the milestones on track, at risk, or missed? On track means the milestone will be met by the target date with no intervention needed. At risk means the milestone will be missed without corrective action, but corrective action is possible. Missed means the milestone date has passed and the milestone condition is not met. For at-risk milestones, identify the corrective action and assign accountability. For missed milestones, ask: is this a delay (we will hit the milestone later) or a scope issue (we defined the wrong milestone)? The answer determines whether you adjust the timeline or redefine the milestone. Question two -- priority validation: has the business context changed in a way that affects the priority order? Common triggers: a major customer escalation, a competitor move, an organizational restructure, or new information about the technical landscape. If the context has changed enough to warrant a priority change, make the change explicitly. Do not let priorities drift implicitly -- that produces the worst of both worlds (the team is confused about what matters, and the original priorities are no longer being protected). Question three -- trade-off review: check the trade-off list. Has anything on the trade-off list become urgent enough that it should replace one of the current priorities? If so, which priority does it replace? This forces the discipline of trade-offs to be maintained even when urgency pressure increases. You cannot add a fourth priority -- you can only swap. Question four -- team health: is the pace sustainable? Are any individuals overloaded? Is the team's energy increasing, stable, or declining over the quarter? This question connects back to the sustainable pace principles from Week 42. A roadmap that burns out the team is a failed roadmap even if the milestones are met. The adaptive planning mindset means holding two things simultaneously: commitment to the plan (we will execute against these priorities until we have clear evidence that they should change) and willingness to adapt (when the evidence is clear, we will change the plan rather than stubbornly executing against outdated priorities). The discipline is knowing which state you are in: are you facing a temporary difficulty that requires persistence, or a genuine change in context that requires adaptation? The default should be persistence. Most mid-quarter pressure to change priorities is driven by urgency, not importance. The roadmap exists to protect important work from urgent distractions. Only change the plan when the business context has genuinely shifted -- not when someone is anxious about a short-term issue.

Eisenhower's distinction between plans and planning aligns with Mintzberg's (1994) research on 'the rise and fall of strategic planning,' which demonstrated that the primary value of planning is not the plan itself (which is quickly outdated) but the 'strategic thinking' that the planning process produces -- the shared understanding of priorities, trade-offs, and decision criteria that persists even when the specific plan changes. The monthly review implements what Sull and Eisenhardt (2015) call 'simple rules for strategic agility' -- the practice of maintaining a small number of clear priorities while adapting tactics based on emerging information. Their research across 150 companies found that organizations that combined stable strategic priorities (reviewed quarterly) with adaptive tactical plans (reviewed monthly) outperformed both rigid planners (who maintained outdated plans) and reactive organizations (who changed direction frequently based on short-term signals). The 'swap, not add' discipline for priority changes addresses what behavioral economists call 'the planning fallacy' (Kahneman and Tversky, 1979) -- the systematic tendency to underestimate the time, cost, and effort required for future tasks. The swap discipline prevents planning fallacy from compounding: without it, mid-quarter priority additions accumulate without corresponding priority removals, which overcommits the team and guarantees that some priorities will fail. Research by Buehler, Griffin, and Ross (1994) found that the planning fallacy is amplified in group settings because group optimism exceeds individual optimism, making the swap discipline especially important for team roadmaps.