Week 18 Day 5: What Happens When Plans Fall Apart but Intent Is Clear

When a plan fails and the team does not know the intent, they stop. They escalate. They wait. This is rational behavior -- without understanding what they are trying to achieve, they cannot improvise safely. When a plan fails and the team knows the intent, they adapt. They find another route to the same destination. They make decisions in real time. This is also rational behavior -- with clear intent, the original plan becomes one option among many, and the team can evaluate alternatives against the intent rather than against the plan.

Here is a real example of intent-driven adaptation. A team was building a customer-facing reporting feature with a hard deadline tied to a product launch event. The plan was to use a third-party analytics service for the backend. Three days before the deadline, the analytics service had a major outage and announced it would take a week to restore full functionality. If the team had been given a plan ('use this service, build this integration'), they would have been stuck. The plan was impossible. But the Commander's Intent was clear: 'Give customers visibility into their usage data by launch day because the sales team has been promising this feature in every deal for six weeks. Accuracy within 24 hours is acceptable. Real-time is ideal but not required.' With that intent, the team pivoted in hours. They pulled usage data from the application logs, built a simple aggregation pipeline, and delivered a basic but functional reporting view that met the 24-hour accuracy constraint. It was not the elegant solution they had planned. But it delivered on the intent. The sales team had what they needed. The customers had visibility. The third-party integration was completed the following week as an upgrade. Without Commander's Intent, the team would have escalated, the deadline would have slipped, and the sales team would have been left making excuses.

The plan-failure adaptation pattern is central to what Clausewitz (1832) called 'friction' in warfare -- the accumulated effect of small uncertainties, errors, and disruptions that cause real-world execution to diverge from theoretical plans. Clausewitz's observation that 'no plan survives first contact with the enemy' is the foundational insight behind Commander's Intent doctrine. Research by Weick (1993) on the Mann Gulch wildfire disaster demonstrated that groups with strong shared understanding of intent ('we need to survive') were able to improvise adaptive responses to plan failure, while groups fixated on the original plan ('we need to build a firebreak here') continued executing a failed strategy until it was too late. Klein's (1998) research on recognition-primed decision-making shows that experts in dynamic environments make 80-95% of their decisions through pattern recognition rather than analytical comparison, and that this pattern recognition depends on understanding the goal (intent) rather than memorizing the procedure (plan). The reporting feature example illustrates what Eisenhardt (1989) calls 'strategic decision-making in high-velocity environments' -- the ability to make fast, high-quality decisions under time pressure, which her research found depends on having 'real-time information,' 'simultaneous alternatives,' and 'clear strategic intent.' The team had all three because the Commander's Intent provided the evaluative frame.