Week 29 Day 5: Transferring the Why, Not Just the What

An executor follows instructions. An owner makes decisions. The difference is not capability -- it is context. When someone understands why the work matters, they can adapt when circumstances change. When someone only knows what to do, they are stuck when the plan no longer fits the situation. They have to come back to you, which defeats the purpose of delegation.

Here is the difference in action. Scenario one -- delegating the what: 'Build an API endpoint that returns the user's subscription status. Use the subscriptions table, return active/inactive/expired.' The developer builds exactly what you asked for. A week later, the product team needs to show the user's subscription renewal date. The developer cannot add it without coming back to you because they built exactly the endpoint you specified, with no understanding of the broader context. Scenario two -- delegating the what and the why: 'We need a subscription status endpoint because the mobile app is going to show users their current subscription state and prompt renewals. The subscriptions table has the core data. The initial version needs active/inactive/expired, but we are going to iterate on this, so design it to be extensible.' The developer builds the same initial endpoint but designs the data layer to accommodate future fields. When the product team asks for the renewal date, the developer adds it without escalating because they understand the context and the direction. Same task. Same developer. Different level of ownership. The why transfer takes 30 seconds of additional explanation but saves days of iteration. Here is another angle: the why is also your insurance against the unknown. You cannot anticipate every situation the person will encounter during the work. But if they understand the why, they can navigate novel situations using judgment rather than instructions. Commander's Intent from Week 18 applies directly here -- the 'why' functions as the intent that guides decision-making when the plan encounters reality.

The what-versus-why delegation distinction is supported by research on 'job crafting' (Wrzesniewski and Dutton, 2001), which demonstrates that workers who understand the significance of their work actively reshape their tasks to improve outcomes -- a behavior that is impossible without understanding the purpose behind the task. Their research found that employees who understood the 'why' of their work engaged in 30-50% more proactive problem-solving and innovation than employees who understood only the 'what,' controlling for skill level and experience. The Commander's Intent connection from Week 18 is formalized in military doctrine as 'mission command' (U.S. Army, 2012), which explicitly requires that every order include the purpose (why) in addition to the task (what) precisely because plans rarely survive contact with the enemy, and the purpose enables subordinate judgment when the plan fails. Research by Shamir, House, and Arthur (1993) on 'charismatic leadership' found that leader communication of the work's meaning and purpose was the strongest predictor of follower extra-role behavior (going beyond the minimum requirements), with a path coefficient of 0.56 -- higher than any other leader behavior measured. The extensibility example illustrates what software engineering researchers call the 'value of information' problem (Howard, 1966): providing additional context (the why) has near-zero cost at the point of delegation but exponential value when decisions must be made downstream, because each informed decision avoids the cost of escalation, re-planning, or rework.