11.1 Designing Implementation Plans: Projects, Programs and Governance

11.1 Designing Implementation Plans: Projects, Programs and Governance

Executive Summary: A strategy that stays on paper is only a wish list. Implementation turns strategic themes into funded initiatives with owners, timelines and measures. This section explains how to design an implementation plan, distinguishes projects, programs and portfolios, and sets out the governance, project-management tools and status reporting that keep strategic initiatives on track.

From Strategy to Action

Leadership teams often spend most of their energy on analysis and choice, yet the gap between knowing what to do and doing it—the knowing–doing gap—is where many strategies fail. Implementation is iterative: plans are made, executed, monitored and adjusted as results and the environment change.

Designing the Implementation Plan

An implementation plan translates each strategic theme into initiatives and specifies:

1. Objectives and scope: what each initiative will deliver and what it will not.
2. Ownership: an executive sponsor who is accountable and a manager responsible for delivery.
3. Time-phased resources: people, budget and capacity by period, recognising that the same experts are often needed by several initiatives.
4. Milestones and dependencies: the sequence of work, including what must be finished before other work can start.
5. Risks: the main risks and their treatment (Section 10.2).
6. Measures: the KPIs and targets that show progress and benefits.
7. Communication and change management: who needs to know what, and how resistance will be addressed (Section 12.3).

Sequencing matters. Quick wins build credibility; dependencies set the critical order; and the organisation's capacity to absorb change limits how many major initiatives can run at once.

Projects, Programs and Portfolios

The Project Management Institute distinguishes three levels:

Example: a health insurer's strategic objective is to double digital self-service within three years. That objective is managed as a program ("Digital Member Experience"). Its projects might include a new mobile app, automated claims processing, and a staff retraining project. Each project has its own manager, budget and deadline; the program manager ensures they fit together, do not compete for the same resources and collectively deliver the benefit.

Governance of Strategic Initiatives

Strategic initiatives need governance that is separate from business-as-usual budgets, or they are crowded out by day-to-day pressures:

• Executive sponsors with authority to remove obstacles.
• A steering committee that makes go, stop and change decisions at stage gates.
• A program or project management office (PMO) that sets standards, tracks progress and reports.
• Ring-fenced funding released against milestones.
• Clear tolerances for cost, time and scope, beyond which decisions must be escalated.

Reporting status: the program report card

A program report card gives executives a quick view of many initiatives, usually with a traffic-light (RAG) status:

Core Project Management Tools

• The triple constraint: scope, time and cost are linked, and quality depends on all three; changing one affects the others.
• Work breakdown structure: divides the project into manageable deliverables and tasks.
• Gantt chart and critical path: show the schedule; the critical path is the longest chain of dependent tasks, and any delay on it delays the whole project.
• Risk and issues registers: record threats and problems with owners and actions.
• Change control: requires approval before scope changes are made, preventing scope creep.
• Benefits realisation plan: defines how and when the promised benefits will be measured after delivery.

Practical Illustration: Managing Upward

A newly appointed CFO is asked to lead a strategic project to analyse the effect of removing slow-selling product lines on total store sales, while still doing her full-time job. Applying project discipline, she first agrees the scope and the decision the analysis must support, then negotiates resources (an analyst and data access), sets milestones and a reporting rhythm with the managing director as sponsor, and records the risk that her own time is the binding constraint. Without these steps the project would drift behind her daily responsibilities.

Common Implementation Pitfalls

• Launching too many major initiatives at once, so that the same scarce experts are overcommitted.
• Treating strategic projects as extras to be done "when time allows" alongside full-time jobs.
• Measuring activity (meetings held, tasks completed) instead of benefits delivered.
• Allowing scope to grow without formal change control.
• Continuing failing projects because of the money already spent (the sunk-cost trap described in Section 13.5).

The Finance Professional's Role

CPAs build the business cases that justify initiatives, set up the cost tracking and benefits measures, challenge optimistic schedules and budgets, and report honestly when an initiative should be stopped.