Commander's Intent Statement

By Gojko Adzic · Published 26 June 2026

A Commander’s Intent Statement is a concise and clear outline of the purpose for an initiative or a mission, complementing a specific execution plan by providing the wider context and the thinking behind the plan. The goal of a commander’s indent statement is to align everyone involved on the key objectives, and to ensure that people can use their own initiative and deviate from a specific plan if needed, but still achieve the ultimate goals.

Commander's Intent Statement based on Gary Klein's Seven Facets
Commander's Intent Statement based on Gary Klein's Seven Facets, helping people focus on the core objectives and stay within the constraints without overprescribing a solution

Applicability to software products

Commander’s intent statements are an excellent tool to set direction without over-specifying implementation for product features, especially when starting a new larger block of work. They help a team converge on what success looks like and why it matters before anyone commits to how the solution will be delivered, and challenge any potential solution design, offering better alternatives. By clearly communicating the purpose, intent statements can help facilitate the creation of more detailed mapping between goals and solutions, such as Opportunity Solution Trees and Impact Maps.

Particularly in the context of AI-assisted planning and development, commander’s intent becomes a critical tool allowing the agents to create and self-evaluate plans against objectives, helping to make sensible local decisions and choose between alternative implementations. A clear intent statement can be very useful to flag conflicts between a chosen plan and the reality of an existing codebase, and making trade-offs when planned instructions no longer make sense.

Origins of Commander’s Intent Statements

Various commander’s intent statement templates emerged from military and emergency services, particularly in the context of Mission Command, a military doctrine advocating “centralized intent and decentralized execution, allowing the force to take calculated and managed risks and learn, anticipate and adapt more quickly […] to exploit opportunities”. The idea gained wider adoption in NATO militaries in 1980s.

You can lose the ability to execute the original plan, but you never lose the responsibility of executing the intent.

Colonel Tom Kolditz, head of the behavioural sciences division at West Point, quoted in Made to Stick

Through the work of management theorist Karl Weick and research psychologist Gary Klein, the Commander’s Intent Statement was reframed as a general tool for aligning people around a shared purpose, and applied to business projects and company management. Chip and Dan Heath’s book Made to Stick in 2007 introduced this concept to a broader management audience, presenting commander’s intent as a way to frame goals that survive contact with messy, unpredictable reality.

“Finding the Core” statement

In Made to Stick, the authors provide a short two-item version of a Commander’s Intent Template, intended to “find the core” of the mission.

  1. If we do nothing else during the tomorrow’s mission, we must …
  2. The single, most important thing that we must do tomorrow is …

This kind of template is most useful for short-term immediate plans, and was taken from a guidebook of a combat simulation center.

Karl Weick’s Commander’s Intent Statement

Transitioning from military mission objectives to a business context, Weick proposed that commanders should present intent in the following order:

The final step provides an opportunity to provide feedback and resolve open questions. Using a PreMortem Exercise is a particularly good way of collecting the feedback on the intent and the plan at the same time.

Klein’s seven facets of Commander’s Intent

In Sources of Power, Gary Klein presents a review and analysis of several methods for communicating intent, and a review of various actual commander’s intent statements from the US military and emergency services, concluding that there are “seven facets” that intent statements usually address:

  1. The purpose of the task (higher-level goals)
  2. The objective of the task (the desired outcome)
  3. The sequence of the steps in the plan
  4. The rationale for the plan
  5. The key decisions that may have to be made
  6. Anti-goals (unwanted outcomes)
  7. Constraints and other considerations

Klein suggests that the seven facets should be used as a checklist, not as mandatory sections, and that individual points may not be necessary to include in some situations.

The art of describing your intent is to give as little information as you can. The more details you pack in, the more you obscure your main points. However, if you leave out an important consideration, you run the risk that the person will become confused at a critical decision point

– Gary Klein, Sources of Power

Klein specifically warns against including too many details about the resources (such as cost, specific timelines) because “a leader who specifies time and resources is micromanaging”.

Benefits of communicating intent

Klein lists the following benefits from communicating intent clearly:

Promoting independence seems to be the key aspect underpinning many other benefits in that list, and as Klein puts it “team members need less attention and monitoring”. Instead of communicating a sequence of steps to follow, the intent template allows participants to focus on the goal, decide themselves if they are making a mistake, and function on a higher level. Because of that, a commander’s intent statement should allow flexibility and not restrict people’s ability to adapt to changing conditions.