The HoLiDySt Architecture
Whatever is in this book is what survived. The rest did not make the cut.
The Three Layers
HoLiDySt covers three interconnected layers of delivery management. Each operates at a different altitude, serves different stakeholders, and manages different types of decisions — but they form a single system.
Portfolio Management — Choosing the Right Investments
The portfolio layer sits at the top. It answers the strategic question: Are we investing in the right things?
Portfolio management is about selecting, balancing, and governing the organisation’s portfolio of transformation investments. It ensures that resources and funding flow to the initiatives that deliver the most strategic value, and that the portfolio is actively managed — not just selected once and left to run.
Key responsibilities: strategic alignment, investment prioritisation, resource allocation, enterprise risk management, and strategic benefits tracking.
The audience: CPOs, CIOs, CFOs, strategy directors, enterprise PMO heads.
Programme Management — Delivering the Transformation
The programme layer sits in the middle. It answers the execution question: How do we deliver this complex transformation?
Programme management is about orchestrating multiple projects, workstreams, and change initiatives to deliver transformational outcomes. It’s where strategy becomes reality — where the target operating model gets built, the solution gets deployed across countries, and the benefits get tracked and realised.
This is the most complex layer, because it requires simultaneous management of scope, governance, stakeholders, change, technology, finance, and risk across multiple geographies, cultures, and organisational structures.
Key responsibilities: programme lifecycle management, governance, benefits realisation, stakeholder engagement, change management, cross-workstream integration, and multi-country coordination.
The audience: programme directors, PMO leads, workstream leads, change managers, regional leads.
Project Management — Executing the Work
The project layer sits at the base. It answers the delivery question: How do we execute this specific piece of work effectively?
Project management is about delivering individual projects — technology builds, process redesigns, data migrations, training programmes — within the programme framework. Each project produces specific outputs that feed into programme outcomes.
Key responsibilities: project planning, delivery (waterfall, agile, or hybrid), team management, RAID management, quality control, and output handover.
The audience: project managers, team leads, delivery teams.
How They Connect
The layers aren’t independent silos — they’re a cascade:
- Downward: Portfolio decisions fund and prioritise programmes. Programme governance defines and oversees projects. Strategic objectives cascade from portfolio to programme to project.
- Upward: Project outputs feed programme outcomes. Programme outcomes deliver portfolio strategic benefits. Lessons learned flow upward and sideways to refine governance at every level.
A mature organisation has seamless governance across these three layers, avoiding duplicated work, conflicting priorities, and value leakage — the silent erosion of benefits that happens when nobody can trace a line from strategic intent to delivered output.
The Five-Volume Suite
HoLiDySt is packaged as five volumes, each with a clear purpose and audience:
| Volume | Title | Purpose |
|---|---|---|
| 1 | The Framework (you are here) | The compass, diagnostic, and navigation layer. Establishes the intellectual foundation, provides the maturity assessment, and helps you choose which volumes you need and how much rigour to apply. |
| 2 | Portfolio Management Playbook | Guides enterprise leaders in managing the portfolio of transformation investments — what to fund, what to stop, how to balance, how to track strategic value. |
| 3 | Programme Management Playbook | The main delivery methodology. End-to-end guidance for planning, executing, and sustaining large, multinational transformation programmes. |
| 4 | Project Management Playbook | Guides project managers in delivering individual projects within a programme context, covering waterfall, agile, and hybrid delivery methods. |
| 5 | Template & Artifact Library | The complete toolkit. Every template, organised by volume and phase, with instructions and worked examples. Also the specification for digital tool deployment. |
The Modularity Promise
Here’s the commitment: every volume works alone, and all volumes work together.
This means you can adopt HoLiDySt incrementally, based on your role, your needs, and your ambition:
- You’re a CPO managing an enterprise portfolio? Take Volume 1 (to assess maturity) and Volume 2 (Portfolio Playbook). You don’t need the rest yet.
- You’re a programme director brought in to deliver a multinational transformation? Volume 1 (to understand the approach) and Volume 3 (Programme Playbook). Maybe Volume 5 (Templates) for the tools.
- You’re a project manager inside a programme? Volume 4 (Project Playbook) and Volume 5 (Templates) might be all you need.
- You’re a head of PMO building enterprise-wide capability? Deploy the full suite — all five volumes — as an integrated methodology.
- You’re recovering a programme that’s gone sideways? Volume 1 (for a rapid health assessment) and the recovery chapter in Volume 3. Start there, expand as you stabilise.
No volume assumes you’ve read the others. But if you use the full set, the governance, language, benefits tracking, and maturity dimensions are all consistent — because they’re all built on the same framework you’re reading now.
Take the whole holiday, or just a long weekend. It scales to your ambition.
How the Volumes Integrate
When used together, the five volumes form a closed-loop system:
Strategic cascade (top-down): Portfolio strategy (Vol 2) → defines which programmes to fund → Programme methodology (Vol 3) → defines which projects to execute → Project delivery (Vol 4) → produces outputs using templates (Vol 5) → governed by the framework (Vol 1).
Value flow (bottom-up): Project outputs → Programme outcomes → Portfolio strategic benefits → reported to the board → informs next investment cycle.
Assessment loop: Volume 1’s maturity assessment identifies gaps → gaps point to specific chapters in Volumes 2, 3, or 4 → those chapters reference templates in Volume 5 → improvements are measured in the next assessment cycle.
Scalability loop: Volume 1’s categorisation framework (Chapter 6) determines programme size → size determines which templates in Volume 5 are mandatory versus optional → governance intensity in Volumes 2–4 scales accordingly.