Week 19 Day 4: When You Must Specify the How (and When You Must Not)

Commander's Intent does not mean never specifying the how. It means being deliberate about when you do. There are three situations where specifying the approach is appropriate: safety-critical work where the wrong method has catastrophic consequences, compliance-driven work where the method is legally mandated, and crisis response where speed matters more than optimization. In every other situation, specify the what and why and leave the how to the team.

Here is a decision framework for when to specify the how. Ask three questions about the task. First: 'If the team chooses the wrong approach, is the consequence reversible?' If yes, let them choose. The learning from a recoverable mistake is worth more than the efficiency of your prescribed approach. Second: 'Does the approach have regulatory, legal, or safety implications?' If yes, specify the approach -- or at minimum, specify the constraints tightly enough that compliance-violating approaches are excluded. Third: 'Is time pressure so severe that exploration would cost more than it returns?' If yes, specify the approach -- but acknowledge explicitly that you are doing so because of time pressure, not because you do not trust the team's judgment. This distinction matters because the team interprets your behavior. If you specify the how without explanation, they hear 'the leader does not trust us.' If you specify the how with 'we are in a time crunch and I need us to converge fast -- here is the approach I want us to take, and after the crisis we can discuss alternatives,' they hear 'the leader is making a tactical decision.' Same action, completely different interpretation. The explanation does not slow you down. It preserves the trust that lets you move fast next time.

The three-situation framework maps to Snowden and Boone's (2007) Cynefin decision framework. Safety-critical and compliance-driven work falls in the 'obvious' or 'complicated' domains where cause-and-effect relationships are known and best practices or expert practices apply -- justifying process specification. Crisis response falls in the 'chaotic' domain where action must precede analysis. The majority of knowledge work falls in the 'complex' domain where cause and effect can only be determined in retrospect, making process specification inappropriate because the 'right' approach cannot be known in advance. The reversibility test draws on what Bezos (2015) calls 'Type 1 and Type 2 decisions': Type 1 decisions are irreversible and warrant careful specification, while Type 2 decisions are reversible and should be made quickly with minimal control. The research on how teams interpret leader behavior aligns with Attribution Theory (Weiner, 1985), which demonstrates that people attribute motives to observed behavior, and that the same behavior (specifying the how) is interpreted differently depending on the attributed motive (distrust versus time pressure). Detert and Burris (2007) found that leader behaviors interpreted as controlling reduced employee voice by 34%, while identical behaviors interpreted as supportive had no negative effect on voice -- confirming that the explanation changes the psychological impact without changing the action.