Strategy & Execution
Why Good Ideas Get Stuck Between Strategy and Execution
Strategies rarely fail because teams lack ideas. The harder work is translating an objective into decisions, ownership, sequenced work, and visible progress.
Most organizations do not have an idea shortage. They have a translation problem. A goal can make perfect sense in a leadership meeting and still become vague by the time a team is expected to deliver it.
Strategy describes direction. Teams still need executable work.
Statements like 'improve the customer experience,' 'modernize operations,' 'grow digital revenue,' or 'use AI to become more efficient' can be valid strategic priorities. They are not yet projects.
Execution begins when the organization translates that direction into outcomes, decisions, ownership, constraints, sequencing, and work that can actually be completed.
The gap between those two levels is where many good ideas slow down.
1. The desired outcome is still ambiguous
Teams can work very hard on the wrong interpretation of a goal. Before building a project plan, I want to know what will be meaningfully different when the work succeeds.
That answer should be more specific than completing a deliverable. Launching a portal, implementing a platform, or creating a campaign may be part of the work, but the outcome is the business change those deliverables are supposed to create.
- What are we trying to change?
- For whom?
- How would we recognize that it improved?
- What are we intentionally not trying to solve?
2. Decisions are disguised as tasks
A surprising amount of project delay comes from work being assigned before key decisions have been made. A team cannot finalize the workflow if nobody has decided which exceptions are allowed. A developer cannot build the right integration if system ownership is unresolved. A marketer cannot optimize the customer journey if the desired action is still being debated.
When a task repeatedly stalls, I look for the decision hiding underneath it.
3. Everyone is involved, but ownership is unclear
Cross-functional work requires participation from multiple groups, but participation and ownership are not the same thing.
Someone needs to own the outcome. Individual workstreams need owners. Decisions need decision-makers. Subject-matter experts need to know when they are advising rather than approving.
Without that clarity, the safest behavior is often to schedule another meeting.
4. The project plan becomes a list instead of a sequence
A long task list can create the appearance of structure while hiding dependencies. Good execution requires understanding what must happen first, what can happen in parallel, which decisions unlock other work, and where the highest uncertainty sits.
I prefer identifying the smallest meaningful sequence that reduces uncertainty and creates momentum. That may be a prototype, a process map, a technical spike, a customer test, or a decision session before a larger build begins.
5. Feedback arrives too late
Teams often spend too long polishing work before putting it in front of the people who can challenge the assumptions. The result is a large review near the end of the project, when changes are expensive.
A healthier cadence creates smaller checkpoints. Show the workflow before building it. Validate the information architecture before designing every page. Test the integration before depending on it for the rest of the launch.
The purpose of a checkpoint is not ceremony. It is to discover that you are wrong while being wrong is still inexpensive.
A simple translation framework
When a strategic priority needs to become executable work, I find it useful to move through six layers. The exact artifacts can vary; the questions are what matter.
- Outcome: What should be different when this succeeds?
- Decisions: What must be decided before the work can move?
- Work: What needs to be created, changed, tested, or removed?
- Owners: Who owns the outcome, each workstream, and key decisions?
- Cadence: How will the team surface progress, risks, and decisions?
- Evidence: What will tell us that the work created the intended result?
Execution is not the less strategic part of strategy
The work between strategy and delivery is sometimes treated as administrative: project plans, meetings, tickets, documentation, status updates. Those things can become bureaucracy when they are disconnected from decisions.
Used well, however, they are how an organization turns intent into coordinated action. The valuable part is not the artifact. It is the clarity the artifact creates.
Good execution keeps asking the same question: what needs to become clearer for the next meaningful piece of work to move?