Approval is a governance decision; implementation is an operating discipline
Organisations frequently invest considerable time in developing strategies, transformation plans, project proposals and investment programmes.
The document is approved. The launch meeting is held. Responsibilities are discussed.
Several months later, progress is difficult to verify.
The problem is not always the quality of the strategy. It is often the absence of an execution architecture capable of converting the approved direction into coordinated action, timely decisions and measurable outcomes.
Good strategies commonly fail after approval for the following reasons.
The strategy has not been translated into an executable portfolio
Strategic objectives are often expressed in broad terms such as:
- · Expand into new markets.
- · Improve operating efficiency.
- · Raise capital.
- · Develop strategic partnerships.
- · Launch new products.
- · Strengthen governance.
- · Deliver major projects.
These objectives must be converted into defined initiatives.
Each initiative should have:
- · A clear outcome.
- · An executive owner.
- · A workstream leader.
- · Deliverables.
- · A budget.
- · Dependencies.
- · Milestones.
- · Performance measures.
- · Risks.
- · Decision requirements.
- · A completion definition.
Without this translation, teams may interpret the strategy differently and pursue disconnected activities.
Accountability has been assigned in name but not in authority
An individual may be described as responsible for an initiative without possessing the authority, resources or information required to deliver it.
Effective accountability requires clarity regarding:
- · Who recommends.
- · Who approves.
- · Who executes.
- · Who provides specialist input.
- · Who controls the budget.
- · Who resolves cross-functional disputes.
- · Who receives performance reports.
- · Who is accountable for the final outcome.
Where several executives share nominal ownership, effective ownership may belong to no one.
Dependencies have not been identified
Implementation programmes rarely consist of independent activities.
A product launch may depend on regulatory approval, technology completion, staff recruitment, procurement and customer onboarding.
A capital programme may depend on corporate restructuring, financial modelling, governance changes, adviser appointments and data-room preparation.
When dependencies are not mapped, one delayed workstream can prevent several others from progressing.
The implementation plan should therefore identify the critical path and determine which decisions or deliverables must occur before subsequent activities can begin.
The budget has not been aligned with the strategy
A strategy without an approved resource plan remains an aspiration.
Management should determine:
· The cost of implementation.
· The source of funding.
- · The timing of expenditure.
- · Internal staffing requirements.
- · External advisory requirements.
- · Technology requirements.
- · Procurement lead times.
- · Contingency.
- · The cost of delay.
- · The cost of stopping an initiative.
Strategic initiatives should be integrated into budgeting and cash-flow planning rather than treated as activities outside the organisation’s financial controls.
Governance meetings focus on reporting rather than decisions
Implementation meetings often become lengthy descriptions of activity.
A decision-oriented governance meeting should focus on:
- · Progress against agreed milestones.
- · Decisions required.
- · Material variances.
- · Risks that have changed.
- · Dependencies that are delayed.
- · Issues requiring escalation.
- · Corrective actions.
- · Changes to scope, cost or timetable.
- · Benefits achieved.
Reports should distinguish between activity completed and outcome delivered.
Problems are escalated too late
Teams may delay escalation because they expect the issue to be resolved informally or fear that reporting a problem will be viewed as failure.
This allows small issues to become material implementation constraints.
A disciplined escalation framework should define:
- · What constitutes a reportable issue.
- · The maximum time an issue may remain unresolved.
- · Who has authority to resolve it.
- · What information is required.
- · How decisions will be documented.
- · When the board or executive committee must be informed.
Escalation should be treated as a control mechanism rather than a sign of weak performance.
Performance measures do not reflect the strategic outcome
A project can complete many activities without delivering the intended commercial benefit.
For example:
- · A platform may be launched without achieving adoption.
- · A partnership may be signed without generating revenue.
- · Capital may be raised without delivering the stated milestones.
- · A facility may be constructed without becoming operational.
- · Staff may be recruited without improving delivery capacity.
Implementation reporting should therefore track both milestones and benefits.
Relevant measures may include:
- · Revenue generated.
- · Costs reduced.
- · Cash released.
- · Customers acquired.
- · Capacity created.
- · Licences secured.
- · Projects completed.
- · Service levels improved.
- · Capital deployed.
- · Risks reduced.
- · Implementation milestones achieved.
Building execution accountability
An institutional implementation framework should contain the following components.
1. Implementation mandate
A formal statement of:
- · The approved strategy.
- · The implementation period.
- · The expected outcomes.
- · Governance authority.
- · Reporting requirements.
- · Material constraints.
2. Initiative portfolio
A complete list of approved initiatives, ranked by strategic importance, urgency, resource requirement and dependency.
3. Workstream charters
Each workstream should define:
- · Scope.
- · Deliverables.
- · Owner.
- · Team.
- · Budget.
- · Milestones.
- · Dependencies.
- · Risks.
- · Required decisions.
- · Completion criteria.
4. Decision-rights matrix
The matrix should identify which matters are:
- · Delegated to management.
- · Reserved for the executive committee.
- · Reserved for the board.
- · Subject to shareholder approval.
- · Subject to regulatory or third-party consent.
5. Integrated implementation plan
The plan should connect all workstreams through:
- · Sequencing.
- · Critical-path analysis.
- · Resource allocation.
- · Procurement requirements.
- · Financial requirements.
- · Decision deadlines.
- · Interdependencies.
6. Performance dashboard
A typical structure may include:
The dashboard should report:
- · Milestone status.
- · Budget status.
- · Benefits achieved.
- · Material risks.
- · Decisions outstanding.
- · Issues requiring escalation.
- · Actions due.
- · Responsible owners.
7. Governance cadence
- · Weekly workstream reviews.
- · Fortnightly implementation reviews.
- · Monthly executive steering meetings.
- · Quarterly board-level performance reviews.
- · Immediate escalation of defined critical matters.
The precise cadence should reflect the scale and risk of the programme.
8. Change control
Material changes to scope, cost, timetable or expected outcomes should be documented and approved.
Uncontrolled change can make it impossible to determine whether the original strategy has been delivered.
The role of a Commercial Implementation Office
A Commercial Implementation Office provides a central mechanism for coordinating strategic initiatives across management, finance, operations, advisers, contractors and other stakeholders.
Its responsibilities may include:
- · Translating strategy into implementation workstreams.
- · Establishing project and programme governance.
- · Coordinating interdependent activities.
- · Maintaining the integrated implementation plan.
- · Monitoring milestones and commercial outcomes.
- · Preparing decision papers.
- · Managing issue and risk registers.
- · Supporting procurement and contractor coordination.
- · Tracking budgets and benefits.
- · Escalating material implementation constraints.
- · Maintaining an auditable record of decisions and changes.
The office does not replace executive accountability. It creates the structure through which accountability can be exercised.
From approved strategy to measurable progress
A strategy should not be judged by the quality of its presentation or the seniority of those who approved it.
It should be judged by whether the organisation:
- · Makes the required decisions.
- · Mobilises the necessary resources.
- · Resolves implementation constraints.
- · Maintains accountability.
- · Delivers measurable commercial and institutional outcomes.
NCDF Commercial perspective
NCDF Commercial supports businesses, project sponsors and institutions in establishing implementation offices, programme governance, workstream accountability, commercial reporting and delivery coordination.
Client management remains responsible for corporate decisions, approvals and operational performance unless a separate documented mandate expressly provides otherwise.