The 90-Day Reporting Deadline: Value Chain Under Pressure
A payments firm must submit new transaction reports to a regulator in 90 days. The work touches 11 teams. A 40-page plan was approved six weeks ago, but no one can say which team owns the end-to-end flow. Design and transition requires a six-week change approval; the vendor that supplies the reporting engine is on a 30-day release cycle; deliver and support already has a 200-ticket backlog. The plan activity has produced weekly status reports that are 92% complete, but two critical data mappings are unresolved. The architecture team says the reporting engine must be replaced; the vendor says a configuration change is enough. The audit committee wants evidence of control. The programme manager is considering bypassing the change approval to meet the deadline. The regulator has said late submission will be treated as a serious breach.
1. Map the regulatory reporting change to the ITIL service value chain activities and identify two points of value leakage.
Read the worked answer
Plan: define regulatory scope, approve the 40-page plan, and set the 90-day deadline. Engage: manage the regulator, audit committee, architecture team and reporting-engine vendor. Design and transition: resolve data mappings, design controls, and obtain change approval. Obtain/build: configure or replace the reporting engine with the vendor. Deliver and support: run the reports, handle defects and the existing 200-ticket backlog. Improve: learn from delivery and adjust.
Value leakage point one: design and transition has a six-week approval and two unresolved data mappings, so the plan's 92% status is misleading - percentage complete is an output, not an outcome. Value leakage point two: obtain/build has no clear decision owner between architecture and vendor, so the build may start late or on the wrong option. Deliver and support's backlog also competes for the same people. The plan reports activity, not flow. A value stream view would show the critical path is data mapping and change approval, not the weekly status report.
2. The programme manager is considering bypassing change approval to meet the deadline. Advise on the governance response.
Read the worked answer
Bypassing change approval is not the right response. Governance in the service value chain ensures that activities are aligned with organisational direction and that risks are controlled; the audit committee explicitly wants evidence of control. A bypass would create regulatory and audit risk and would not reliably speed delivery, because unresolved data mappings remain. The better response is to use change enablement properly: risk-assess the regulatory change, delegate authority to a programme-level change authority, pre-approve standard configuration changes, and create an emergency change path for critical fixes with retrospective review. The six-week approval should be challenged as a process constraint; if it cannot handle a 90-day regulatory deadline, that is a process improvement. The change freeze and vendor cycle should be considered in the change schedule. If the programme manager needs an exception, it should be documented and approved by the appropriate authority, not taken informally. This keeps control while improving flow.
3. Which value chain activity should own the end-to-end flow, and why is 'plan' not automatically the answer?
Read the worked answer
The value chain is a set of interacting activities, not a linear sequence with a single owner. Plan sets direction and priorities, but it does not design data mappings, configure the vendor engine or run reports. If plan owns the flow, it can produce status reports while the critical work remains unresolved - exactly the 92% complete symptom. End-to-end ownership should sit with a value stream owner or programme product manager who has authority across design and transition, obtain/build and engage, and who is accountable for the regulatory outcome. That person uses plan for scope and governance, engage for the regulator and audit, design and transition for controls, and obtain/build for the vendor. The improve activity should feed lessons back. The value chain activity that does the work changes along the flow; ownership of the outcome should not. This is think and work holistically applied to the value chain.