Week 38 Day 1: Strategy Means Nothing Until It Changes What People Do on Monday

Every organization has a strategy. Most organizations also have a gap between the strategy and what people actually do. The strategy says 'focus on enterprise customers' but the team is still spending 60% of its time on features for small accounts. The strategy says 'improve reliability' but the team is still prioritizing new features over infrastructure investment. The strategy is clear. The behavior has not changed.

Here is why strategy fails to change behavior, and how to fix each failure mode. Failure mode one -- abstraction gap: the strategy is stated in terms too abstract to act on. 'Become the market leader in cloud security' is a strategy statement. But no individual contributor can translate 'become the market leader' into their work on Tuesday afternoon. The fix: decompose the strategy into team-level objectives (from Week 37's translation framework), and decompose team-level objectives into individual behaviors. 'Become the market leader' becomes 'achieve feature parity with top three competitors on these five capabilities' becomes 'this week, build the SSO integration that closes our biggest competitive gap.' Each level of decomposition makes the strategy more concrete and more actionable. Failure mode two -- incentive misalignment: the strategy says one thing but the incentive structure rewards another. The strategy says 'quality' but the team is measured on velocity. The strategy says 'long-term customer relationships' but the sales team is compensated on quarterly bookings. People follow incentives, not strategies. The fix: audit your incentives (metrics, recognition, promotions, performance reviews) and ensure they align with the strategy. If the strategy is quality, measure quality. If the strategy is relationships, measure retention. Failure mode three -- capacity conflict: the strategy requires new behavior but the team's capacity is fully consumed by existing behavior. The strategy says 'invest in platform reliability' but the feature backlog is so large that there is no time for reliability work. The strategy requires additional capacity that does not exist. The fix: the strategy must explicitly state what the team will stop doing to create capacity for the new behavior. A strategy without a 'stop doing' list is incomplete because it assumes infinite capacity. Failure mode four -- signal confusion: leadership says one thing but does another. The strategy says 'long-term thinking' but the executives react to every quarterly earnings miss with a short-term pivot. The team watches what leadership does, not what leadership says. The fix: the leader must visibly model the strategic behavior, especially when it requires short-term sacrifice for long-term gain.

The strategy-behavior gap is documented by Kaplan and Norton (2001) in 'The Strategy-Focused Organization,' where they found that 95% of employees in a typical organization are unaware of or do not understand the company's strategy, and that only 25% of managers have incentives linked to strategy. Their research concluded that the primary cause of strategy failure is not bad strategy but bad execution -- specifically, the failure to translate strategic intent into operational behavior. The abstraction gap is formalized by Hambrick and Cannella (1989) in their 'strategy implementation' framework, which identifies 'strategy specificity' as the strongest predictor of implementation success: strategies stated in concrete, behavioral terms (what people should do differently starting Monday) were implemented 3x more often than strategies stated in abstract, aspirational terms (what the organization should become). The incentive misalignment failure is an instance of what Kerr (1975) called 'the folly of rewarding A while hoping for B' -- one of the most replicated findings in organizational behavior. His research demonstrates that behavior reliably follows incentives rather than stated intentions, and that organizations that fail to align incentives with strategy produce employees who rationally optimize for the rewarded behavior (velocity) rather than the desired behavior (quality). The capacity conflict is documented by Repenning and Sterman (2001) in their 'capability trap' model, which demonstrates that organizations cannot implement new strategies without explicitly freeing capacity from existing activities, because knowledge workers' time is zero-sum: every hour spent on existing work is an hour unavailable for strategic work.