Week 19 Day 1: Tell Them Where to Go, Not How to Get There

Week 18 introduced Commander's Intent -- the what and why without the how. This week goes deeper into why removing the 'how' is not just a communication technique but a fundamental leadership principle. When you tell someone how to do their work, you cap their contribution at your level of imagination. When you tell them what needs to happen and why, you unlock their full capability -- which in many cases exceeds yours.

I learned this lesson from a junior engineer who was better at her job than I was at mine. I had assigned her a performance optimization task with detailed instructions: profile the database queries, add indexes to the three slowest tables, implement query caching with a 30-second TTL. She followed my instructions precisely. The performance improved by 15%. The next month, a similar problem arose and I was on vacation. Without my instructions, she approached the problem from scratch. She discovered that the performance bottleneck was not the database at all -- it was an N+1 query pattern in the application layer. She restructured the data access layer, eliminated the N+1 pattern, and performance improved by 400%. My instructions had not just limited her approach -- they had directed her to the wrong problem. My 'how' was based on my assumption about the cause. Her fresh analysis, unconstrained by my assumption, found the actual cause. This is the tax that over-specification levies on every team: the leader's assumptions become the team's constraints.

The principle of outcome specification over process specification has deep roots in management theory. McGregor's (1960) Theory Y posits that workers are inherently motivated and capable of self-direction when given clear goals, contrasting with Theory X's assumption that workers require constant direction and control. Research by Oldham and Cummings (1996) on creative performance found that autonomy in method (how to do the work) was the single strongest predictor of creative output, even more than domain expertise or intrinsic motivation. The N+1 query example in level_2 illustrates what Argyris (1991) calls the difference between 'single-loop learning' (optimizing within the existing frame -- making the database faster) and 'double-loop learning' (questioning the frame itself -- asking whether the database is the real problem). Over-specification locks teams into single-loop learning because the leader's instructions define the frame. Removing the 'how' enables double-loop learning by allowing the team to redefine the problem. Research by Amabile (1998) in the Harvard Business Review specifically identifies 'freedom in how to approach the work' as one of six conditions for organizational creativity, finding that specifying ends while leaving means open produced the highest creative output across industries.