Eight weeks to a P3O
A retail bank has committed to a regulator that it will have a 'central change office' in 8 weeks. It has 5 projects, a £180m change budget, no service catalogue, no P3O business case and 4 seconded staff who have never worked in a P3O. The CIO is sponsor and wants 'full services from day one', including assurance, benefits, resource management, reporting and tooling. The bank's change maturity is low; project managers use spreadsheets. The deadline is fixed. You are asked to advise the implementation approach, the minimum viable service set and how success should be measured in the first 90 days.
1. Map the 8 weeks to the P3O implementation lifecycle. What must be done before go-live, and what can be deferred?
Read the worked answer
Use the P3O implementation lifecycle: Identify, Define, Establish, Operate and Close/review. In eight weeks, complete Identify and Define, and only part of Establish. Identify: vision, scope, stakeholders, mandate and a light business case with baseline metrics and success criteria. Define: model, service catalogue v1, governance, roles, processes, reporting and blueprint. Establish: appoint or borrow an experienced P3O manager, train the four secondees, set up a pilot, publish service levels and go live with a limited service set. Defer full tooling, full benefits management, full resource management and a complete assurance programme. Operate begins after go-live but with a review gate at 90 days. Do not skip Define to meet the deadline; that is how 'full services from day one' becomes an unstable office. The regulator commitment is about a functioning office, not a complete catalogue.
2. Define a minimum viable service set and sequence it, given low maturity and four inexperienced staff.
Read the worked answer
Minimum viable services: portfolio and project reporting from existing spreadsheets; risk and issue escalation; change control for the top five projects; assurance reviews for the highest-risk projects; a service request desk; and a single source of portfolio data. Sequence: first reporting and data quality, then risk and change, then risk-based assurance. Benefits tracking starts with benefit profiles for the top five projects, not all. Resource management starts with critical roles. Tooling: use the existing spreadsheet and one reporting template; do not buy a tool in eight weeks. The four secondees need buddying from an experienced P3O analyst and clear service owners. Publish 'what we do not do yet' to manage expectations.
3. What success measures and governance would you set for the first 90 days to avoid a false start?
Read the worked answer
Success measures for 90 days: report timeliness and data quality, decision latency at portfolio board, number of risks escalated and actions closed, assurance coverage of high-risk projects, service request turnaround, customer satisfaction and cost per report. Governance: a P3O steering group chaired by the CIO with business and finance representation, meeting fortnightly for the first 90 days; a P3O manager with clear authority; a review gate at 90 days with stop/continue criteria. Avoid measuring 'services launched' or 'templates produced'. Also track adoption by project managers and whether decisions change. If the office is not used, the regulator commitment is not met in substance.