Week 18 Day 2: Commander's Intent -- The What and Why, Not the How

Most leaders over-specify the how and under-specify the what and why. They say 'use this framework, follow this process, deploy it this way' -- but they never say 'here is what success looks like and here is why it matters.' The result is a team that can follow instructions perfectly but cannot adapt when circumstances change. Commander's Intent flips this. It gives the team maximum clarity on the outcome and maximum freedom on the approach.

Here is the structure I use to write Commander's Intent for any project or task. Part one -- the what: state the desired end state in one or two sentences. Not the deliverable -- the outcome. Not 'build a dashboard' but 'give the sales team real-time visibility into pipeline health so they can prioritize their outreach without waiting for the weekly report.' Part two -- the why: explain why this outcome matters right now. Not the general business case -- the specific, time-sensitive reason. Not 'because data-driven decisions are important' but 'because we are losing three deals per week to competitors who respond faster, and the sales team cannot respond faster without real-time data.' Part three -- the constraints: name the non-negotiable boundaries. 'Must integrate with the existing CRM. Must not require the sales team to learn a new tool. Must be live within two weeks.' Notice what is missing: technology choice, design approach, architecture decisions, implementation details. Those belong to the team. Your job is to define the box -- what it is, why it matters, what the walls are. Their job is to fill it. This is not abdication. It is the highest form of delegation because it requires you to be clearer about intent than you have ever been.

The two-component structure (what and why) aligns with what Sinek (2009) popularized as 'Start with Why' but predates his work by decades in military doctrine. The deliberate omission of 'how' reflects what Hackman (2002) calls 'setting the direction without micromanaging the journey' -- one of five conditions for team effectiveness in his research across diverse organizational contexts. McChrystal et al. (2015) in 'Team of Teams' describe how Commander's Intent enabled Joint Special Operations Command to execute 17 raids per night across Iraq -- a tempo impossible under centralized decision-making -- by ensuring that every team understood the strategic objective well enough to make tactical decisions autonomously. The constraints component maps to what Snowden and Boone (2007) call 'enabling constraints' in their Cynefin framework -- boundaries that focus creative energy rather than restricting it. Research by Amabile (1996) on creativity in organizations demonstrates that moderate constraints actually increase creative output compared to complete freedom, because constraints provide a framework within which to innovate. The distinction between deliverable and outcome in the 'what' component reflects what Drucker (1954) formalized as 'management by objectives' -- defining success by results rather than activities.