Right-Sizing the Methodology

Transformation · No. 6
2026

Whatever is in this book is what survived. The rest did not make the cut.

Why One Size Never Fits All

A global ERP migration across 40 countries and a department automation pilot in one office are both “transformation programmes.” But treating them the same way — same governance, same templates, same stage gates, same reporting cadence — is a recipe for either crushing the small initiative under unnecessary bureaucracy or leaving the large one dangerously under-governed.

HoLiDySt is designed to scale. This chapter tells you how.

The Programme Classification Model

We classify initiatives using three dimensions:

Size (Primary Driver)

Category	Countries / Regions	Budget (€/$)	Stakeholders Impacted	Typical Examples
VL (Very Large)	20+ (Global)	> 100M	> 5,000	Global SAP S/4HANA migration, global banking platform
L (Large)	10–20	50M–100M	1,000–5,000	Multi-region ERP, CRM deployment
M (Medium)	3–10	20M–50M	300–1,000	Regional finance transformation
S (Small)	1–3	5M–20M	100–300	Country-specific ERP or HR/payroll project
XS (Extra Small)	Single country or department	< 5M	< 100	Departmental automation, pilot digital project

Transformation Type (Modifier)

Indicates the primary nature of change, which activates domain-specific templates and guidance:

• Process-led: Operating model redesign, standardisation — emphasises Change Management templates.
• Technology-led: New system implementation (ERP, CRM, Data Platform) — emphasises Technical Build templates.
• Organisational Change-led: M&A integrations, restructuring — emphasises Governance & Stakeholder templates.
• Digital Innovation-led: AI, automation, analytics, capability building — emphasises Agile, Innovation templates.

Complexity (Secondary Driver)

Level	Description
High	Multiple legacy systems, complex integrations, high localisation, strong regulatory impact
Medium	Moderate integrations, partial localisation, some regulatory considerations
Low	Standalone system, minimal integrations, standard processes

Scoring Approach

To categorise your programme:

Size Score: XS = 0, S = 1, M = 2, L = 3, VL = 4

Complexity Score: Low = 0, Medium = 1, High = 2

Total Programme Score = Size Score + Complexity Score

Score	Category
0–1	XS
2–3	S
4–5	M
6	L
7+	VL

This provides flexibility when size and complexity diverge. A single-country programme with high regulatory complexity and multiple legacy system integrations could score as M rather than S — which means more governance, not less.

The Type modifier then activates additional templates relevant to the transformation nature, without changing the base category.

Template Selection Rules

Three rules determine what’s mandatory and what’s optional:

1. Size = Primary: Determines the base set of mandatory templates.
2. Complexity = Secondary: Upgrades some optional templates to mandatory if complexity is high.
3. Type = Modifier: Activates additional domain-specific templates.

What this means in practice:

• VL, Technology-led, High Complexity: 95% of templates mandatory. Full RAID framework, all gate reports, complete governance suite. You need everything because everything can go wrong.
• M, Process-led, Medium Complexity: Many design and change templates mandatory; fewer deep technical artefacts required.
• XS, Digital Innovation-led, Low Complexity: Lean template set. Vision, Charter, minimal governance. Enough structure to stay on track without drowning in process.

A department pilot doesn’t need monthly Steering Committee meetings — but it still needs a sponsor who shows up.

Template Selection Matrix

The complete mandatory/optional grid for all templates by programme size:

Phase 0 — Initiation

Template	VL	L	M	S	XS
Vision Statement	M	M	M	M	M
Programme Charter	M	M	M	M	M
Preliminary Business Case	M	M	M	M	O
Stakeholder Analysis Matrix	M	M	M	M	O
Initial RAID Log	M	M	M	M	O
Programme Organisation Chart	M	M	M	M	O
Governance Framework / SteerCo ToR	M	M	M	O	O
High-Level Benefits Map	M	M	M	O	O
Mobilisation Plan	M	M	M	O	O
Initiation Gate Report	M	M	M	O	O

Phase 1 — Discovery & Design

Template	VL	L	M	S	XS
Country Current State Report	M	M	M	O	O
Heat Map	M	M	M	O	O
Global Process Map	M	M	M	O	O
Technology Landscape Diagram	M	M	M	O	O
Future State Blueprint & TOM	M	M	M	O	O
Gap Analysis	M	M	M	M	O
Opportunity Prioritisation Matrix	M	M	M	O	O
Benefits Realisation Plan	M	M	M	O	O
KPI Framework	M	M	M	O	O
Benefits Dependency Map	M	M	M	O	O
Transformation Roadmap	M	M	M	M	O
Change Impact Assessment	M	M	M	O	O
Readiness Assessment Heat Map	M	M	M	O	O
Design Gate Report	M	M	M	O	O

Phase 2 — Build & Pilot

Template	VL	L	M	S	XS
Solution Build Documentation	M	M	M	O	O
Data Migration Plan	M	M	M	O	O
Solution Architecture Diagram	M	M	O	O	O
Localisation Requirement Matrix	M	M	O	O	O
Test Plan	M	M	M	M	O
Test Execution Report	M	M	M	O	O
QA Sign-off Checklist	M	M	M	O	O
Pilot Country Selection Matrix	M	M	O	O	O
Pilot Plan	M	M	M	O	O
Pilot KPI Tracking	M	M	M	O	O
Pilot Execution Report	M	M	M	O	O
Lessons Learned Register	M	M	M	M	O
Updated Deployment Strategy	M	M	M	O	O
Training Toolkit	M	M	M	O	O
Pilot Gate Report	M	M	M	O	O

Phase 3 — Rollout & Deployment

Template	VL	L	M	S	XS
Country Deployment Plan	M	M	M	O	O
Country Readiness Assessment	M	M	M	O	O
Wave Deployment Calendar	M	M	O	O	O
Post-Wave Review Report	M	M	O	O	O
Training Schedule	M	M	M	M	O
Communication Pack	M	M	M	M	O
Change Champion Network Report	M	M	O	O	O
Adoption Tracking Report	M	M	M	O	O
Go-Live Readiness Checklist	M	M	M	M	O
Cutover Plan	M	M	M	O	O
Contingency Plan	M	M	M	O	O
Hypercare Support Plan	M	M	M	O	O
Benefits Tracking Report	M	M	M	O	O
Executive Dashboard	M	M	M	O	O
Deployment Gate Report	M	M	M	O	O

Phase 4 — Embed & Optimise

Template	VL	L	M	S	XS
Stabilisation Report	M	M	M	O	O
Benefits Realisation Dashboard	M	M	M	O	O
Continuous Improvement Register	M	M	M	O	O
Knowledge Transfer Plan	M	M	M	O	O
Lessons Learned Register	M	M	M	M	M
Programme Closure Report	M	M	M	M	M
Closure Gate Report	M	M	M	O	O

Cross-Phase / Governance

Template	VL	L	M	S	XS
Stage Gate Readiness Checklist	M	M	M	O	O
Master RACI Matrix	M	M	M	M	O
RAID Management Framework	M	M	M	O	O
Communication Plan	M	M	M	M	O
Decision Log	M	M	M	M	O
PMO Dashboard	M	M	M	O	O
Governance Meeting Pack	M	M	M	M	O

M = Mandatory | O = Optional

Type and complexity modifiers then add or remove templates from the base. For example, a Technology-led programme automatically includes Solution Architecture and Data Migration templates as mandatory, regardless of size.

How to Use This

1. Score your programme (Size + Complexity = Category, note Type).
2. Use the Template Selection Matrix to identify your mandatory template set.
3. Apply complexity adjustments (upgrade optional templates to mandatory if you scored High complexity).
4. Apply type modifiers (activate domain-specific templates).
5. Review with PMO for final approval before programme initiation.

Scaling Governance, Not Just Templates

Right-sizing isn’t only about templates — it’s about governance intensity:

Element	VL / L	M	S / XS
Steering Committee	Monthly, full membership	Bi-monthly or quarterly	Quarterly or sponsor-only reviews
Programme Board	Bi-weekly	Monthly	As needed
Stage Gates	All 5 gates, formal review	Gates 0, 2, 4 (combined where appropriate)	Gate 0 and Gate 4 minimum
Reporting	Weekly PMO dashboard	Bi-weekly status reports	Monthly summary
RAID Reviews	Weekly	Bi-weekly	As needed
Benefits Reviews	Monthly	Quarterly	Post-closure only

The principle is consistent: enough governance to maintain control and transparency, not so much that it becomes the transformation’s biggest overhead.