Learning objectives
By the end you can:
- Build a two-axis transformation roadmap (time horizons crossed with initiative lanes (quick wins, structural moves, people & capability)) sequence initiatives against real dependencies, including scarce-resource dependencies invisible on a logic-only plan, and compute the program's critical path.
- Design and reconcile a KPI cascade from a program's north-star target down through workstream contributions to team-level leading indicators, distinguishing a leading indicator from the lagging metric it predicts, and catching a vanity metric that has no line of sight to the target.
- Build and maintain a risk register: score each risk's expected-value exposure (probability × impact), apply a pre-agreed RAG threshold rule rather than a gut call, and choose correctly among mitigation (lowers probability), contingency (lowers impact if the risk lands), and acceptance (a named owner, a named trigger).
- Design a program governance architecture: a three-tier cadence (Steering Committee, Working Group, PMO/Transformation Office) with explicit decision rights, applying RACI (CN7.01's tool) to the recurring calls a transformation must make, and recognize "governance theater," a body that meets on schedule and decides nothing.
- Design and run a working session and a steering committee, build a decision-oriented, time-boxed agenda; pre-wire a contentious decision before the room sees it; facilitate a stuck debate to a structured, criteria-scored decision; and produce minutes and actions that are actually tracked to closure.
- Map stakeholders on a power/interest grid, layer a current-sentiment read on top (champion, neutral, skeptic, blocker), and choose the right influence strategy per quadrant, distinguishing managing up (the sponsor, the steering committee, the client's own leadership) from managing down and across (workstream leads, the delivery team, and the frontline whose behavior the KPI cascade actually depends on).
- Lead the engagement team through a multi-month program: extend CN0.02's delegation, QC, and SBI-feedback disciplines to a matrixed team competing with business-as-usual demands, quantify a capacity gap the moment it opens, and choose honestly among adding capacity, extending the timeline, and de-scoping, never silent overtime, never a silent slip.
- Diagnose "governance theater" and the boxes-and-lines trap applied to delivery (a RACI, a risk register, or a steering committee that exists on paper and changes nothing in practice) and name the specific correction.
- (Productivity objective, R10.) Use AI to draft first-pass roadmap scaffolds, risk-register templates, SteerCo pre-reads, and stakeholder-map drafts from raw notes, while keeping every schedule commitment, every risk judgment, and every read of a real stakeholder's politics fully in your own hands.
The duality, stated once (R10). Objectives 1–8 are the understanding objective the mastery gate rewards, you earn this node by building a roadmap, a cascade, a risk register, and a governance plan correctly by hand, and by reasoning through a facilitation or stakeholder scenario without a tool. Objective 9 is the productivity payoff you keep afterward: AI drafts a competent-looking scaffold in seconds, a roadmap template, a risk register with plausible-sounding rows, a SteerCo pre-read, and none of that drafting speed is worth anything if you cannot tell a scaffold that fits your actual program from one that is merely well formatted. A tool can format a risk register. It cannot know which risk is real, who the sponsor actually trusts, or what a stakeholder's silence in last month's meeting really meant.