PRIME PRODUCTS · MISSION CONTROL
AI-first transformation · by TPL · vanos.tpl.one

Docs / 08-transformation/02-program/_index

Program Management — Index

Hub for the Prime Products AI-transformation program-management area — charter, governance, WBS, roadmap, KPIs, change plan, risk register.

type: index updated: 2026-07-03 owner: kotsalidis

02-program — Program Management

This folder holds the operating machinery of the 12-month Prime Products Ltd AI transformation (ADR-004): what we committed to (charter), how we steer (governance), what gets done and when (WBS, roadmap), how we know it works (KPIs), how people come along (change & training), and what could derail it (risks). Program months M1–M12 start ~September 2026 (assumption — to confirm at kickoff). Strategy context lives in 01-strategy; discovery instruments in 03-discovery.

Documents

DocumentTypeWhat it answers
project-charter.mdcharterWhy the program exists, scope, objectives, sponsors, success criteria.
governance-model.mdgovernanceWho decides what — steering committee, roles, escalation, cadence.
work-breakdown-structure.mdplanFull task decomposition across 13 phases with owners, dependencies, deliverables.
roadmap-12-month.mdplanMonth-by-month M1–M12 view: activities, decision gates, milestones.
kpi-framework.mdframeworkHow success is measured, by layer, with baselines and M6/M12 targets.
change-management-and-training-plan.mdplanAdoption: communication, champions, training, policies, resistance handling.
risk-register.mdregisterLiving risk log — scored, owned, mitigated; reviewed monthly at steering.
_index.mdindexThis page.

How the pieces relate

  • WBS is the master decomposition; the roadmap projects it onto the calendar; both trace decision gates back to the governance model.
  • KPI framework targets feed the monthly board pack and are displayed on Mission Control.
  • Change plan and risk register are the two living documents — updated after every steering meeting; everything else changes only via a logged decision.
  • Department-level detail lives in 04-departments; validated needs are registered as REQ-NNN in 02-Requirements.