Every organization knows this feeling. You invest in strategy. You cascade goals through OKRs or Balanced Scorecards. You communicate relentlessly. Town halls, dashboards, alignment sessions.
And still, Harvard Business Review research found that 67% of well-formulated strategies fail due to poor execution.
The conventional explanations: poor communication, lack of alignment, insufficient accountability. So organizations communicate more, align harder, hold people more accountable.
Nothing changes.
What if the problem isn't how well you cascade goals - it's where you stop?
Consider an orchestra. The conductor has a clear vision for the symphony. Every musician is aligned - they know the piece, they've seen the score, they understand what the conductor wants to achieve. But nobody has their individual part. They know the destination. They don't know their notes. The result isn't music. It's noise.
This is exactly what happens in most organizations. Goals cascade beautifully from the top. Alignment looks good on paper. But nobody has translated those goals into what each role must actually produce.
The Cascade That Stops Short
Here's how organizations typically translate strategy: Organization goals flow to department goals, which flow to team goals, which flow to individual goals.
This is what OKRs do. What Balanced Scorecards do. What Hoshin Kanri does. All sophisticated frameworks for cascading goals down through the organization.
But they all share an implicit assumption: existing roles can absorb new objectives. The cascade moves goals to goals to goals - then stops, expecting task-based job descriptions to somehow produce strategic outcomes.
Gartner finds 67% of employees don't understand their role in new growth initiatives. Not because they weren't told the goals. Because nobody translated those goals into what their role must actually accomplish.
The cascade is incomplete. It aligns people to objectives without redesigning their roles to produce those objectives.
The Evidence Hiding in Plain Sight
Gallup's Q01 - the foundational question in their engagement survey - asks employees whether they know what's expected of them at work. Only 30% can say yes. This single metric predicts engagement, performance, and retention better than almost any other factor.
McKinsey research shows organizations with strong role clarity are five times more likely to achieve successful strategy execution. Not five percent more likely. Five times.
Yet the response to execution failure is almost always the same: communicate better, cascade more clearly, create alignment sessions.
These solutions assume the problem is information transfer. But role confusion persists even in organizations with robust communication practices. The problem isn't that people don't know the goals. It's that nobody translated goals into redesigned roles with outcomes and success metrics.
The False Split Between Strategy and Execution
Strategy scholar Roger Martin challenges the assumption that strategy and execution are separate activities. His argument: both involve making choices under uncertainty, competition, and constraints.
The traditional model treats executives as "brains" (strategy) and employees as "hands" (execution). This creates what Martin calls "choiceless doers" - people handed tasks to complete rather than outcomes to achieve.
The implication for role design is profound. If execution equals strategy, then every role must be designed as a strategic choice-making instrument - not a list of tasks to complete. Task-based job descriptions create the very choiceless doers that guarantee execution failure.
When you cascade goals to task-based roles, you're asking people to execute strategy without giving them the architecture to make strategic choices at their level.
What the Missing Step Actually Looks Like
The complete cascade requires one more translation: Strategic goals must connect to what must be accomplished to achieve them, which must connect to roles redesigned around those outcomes with concrete success metrics.
Harvard's Robert Simons developed the Job Design Optimization Tool to address exactly this gap. His framework asks four questions of every role: What outcomes is this role accountable for achieving? What resources does this role control to achieve them? Who must this role influence to succeed? What support can this role expect?
Research applying this framework shows roles designed around these questions significantly outperform traditional job structures in driving strategic execution. The tool explicitly rejects designing roles around tasks - it mandates designing roles around business outcomes first.
Meta-analysis reveals that outcome accountability produces 48% better performance than process accountability for complex strategic work. Task-based roles lock people into process mode - checking boxes. Outcome-based roles create ownership of results.
Why Organizations Skip It
If role redesign is the missing link, why does everyone skip it?
Because it's hard. Traditional role redesign is laborious, expensive, and slow. Rewriting job descriptions across an organization takes months and costs six figures in labor. HR doesn't have bandwidth. Managers don't have frameworks. The work competes with urgent tactical demands - and tactical always wins.
So organizations default to alignment theater. Another OKR cascade. Another town hall. Another communication initiative. These feel like progress. They're easier than redesigning hundreds of roles.
The barrier isn't awareness. It's effort. Organizations know roles matter. They just can't do the work at scale.
The Competitive Divide
Some organizations will keep cascading goals to task-based roles. They'll communicate harder, align more rigorously, and wonder why execution still fails.
Others will complete the cascade - translating strategic objectives all the way down to outcome-focused roles with success metrics that make accountability possible.
The difference isn't execution discipline. It's execution infrastructure.
Strategy without role clarity is aspiration. Strategy with role clarity is architecture.
The question isn't whether your organization has strategic goals. It's whether you've built the roles to achieve them.