Chapter 24: Building the Implementation Roadmap - From Strategy to Action

Chapter 24: Building the Implementation Roadmap - From Strategy to Action

Video: Recommendation & Implementation That Seals the Win: Make It Realistic, Visual & Unforgettable

Learning Objectives

By the end of this chapter, you should be able to:

• break a strategy into actionable steps
• sequence implementation logically
• establish realistic timelines
• assign responsibility
• distinguish short-, medium-, and long-term actions
• build an implementation roadmap that demonstrates feasibility

Why This Matters

Implementation is often one of the highest-weighted parts of a case competition scorecard. And for good reason. Anyone can recommend: "Launch a new strategy." The difficult part is explaining how it actually happens.

Teams should show clear steps, realistic timelines, named responsibilities, and KPIs, rather than simply saying that "management" will execute the plan.

Discover Your Mad Skills Principle

If you can’t explain how, it gets done, you don’t have a complete recommendation.

Start With the End

Begin with: What must be true for this strategy to succeed? Then work backwards. For example:

Desired outcome à Capabilities required à  Major initiatives à Implementation steps à Owners à Timeline à KPIs

This creates a much stronger implementation plan than simply listing activities.

The Implementation Framework

For each major initiative, answer:

• What? What needs to happen?
• Why? Why is this step necessary?
• Who? Who owns it?
• When? When will it happen?
• How? What resources or capabilities are required?
• How Much? What will it cost?
• How Will We Know? What KPI or milestone indicates success?

Three Horizons

A simple way to structure timing is:

Short Term: Immediate actions.

Examples:

• • • approve project;
    • appoint project team;
    • conduct detailed research;
    • begin pilot.

Medium Term: Build and launch.

Examples:

• • • develop capability;
    • launch pilot;
    • train employees;
    • establish partnerships.

Long Term: Scale and optimise.

Examples:

• • • expand;
    • refine;
    • automate;
    • measure long-term impact.

The time horizon should reflect the case at hand. Don't invent arbitrary "Year 1, Year 2, Year 3" timelines if the case requires something much faster.

Ownership

Avoid: "Management will implement the strategy." Management isn't a person. Identify the responsible group. For example:

• CEO;
• CFO;
• VP Marketing;
• HR;
•  IT;
• Operations;
• external partner;
• new hire;
• project team.

Your source material specifically warns against making the CEO responsible for everything.

Implementation Dependencies

Some actions cannot happen until others happen. For example: Hiring technical talent may need to happen before Build technology, which may need to happen before Launch product. Understanding dependencies makes the implementation plan more credible.

Visualising Implementation

A Gantt chart or simple roadmap can be extremely effective. Show:

• major initiatives;
• timing;
• owners;
• dependencies;
• milestones.

Keep it simple, with visual implementation timelines with clear dates, responsibilities, and costs where possible.

Coach's Lens

Ask yourself: Could someone actually run the project from our slide? If the answer is no, the plan is probably too vague. You don't need to provide every operational detail. The judges should be able to visualise the organisation moving from: Today to Desired Future State.

Common Mistakes

• Vague Actions
• "Improve operations" isn't an implementation step.
• Unrealistic Timelines
• Don't claim you can transform an organisation overnight.
• No Ownership
• Someone must be responsible.
• No Dependencies
• Implementation steps don't happen independently.
• Too Much Detail
• You are not writing a project management manual.

Mad Skills Drill

Take your recommendation. Create a six-step implementation plan. For each step, identify:

What / Who / When / Cost / KPI

Then remove one step. Can the strategy still work? If yes, perhaps that step wasn't essential.

Chapter Summary

A strong implementation roadmap turns strategy into a sequence of realistic actions. The judges should be able to see: What happens first, what happens next, who is responsible, and how the organisation gets to the desired outcome.

Key Takeaways

✓ Start with the desired outcome.

✓ Work backwards to required actions.

✓ Sequence activities.

✓ Assign owners.

✓ Use realistic timelines.

✓ Make dependencies visible.

✓ Keep the roadmap visual.

Looking Ahead

Even the best implementation plan can encounter problems. The next question is: What could prevent this strategy from succeeding?