Scenario · Troubled Programme Reset
Troubled Programme Reset
MBT · Much Before Transformation (MBT) editorial team
Published 2026-10-06
Search intent: Problem-solving · Last reviewed 2026-10-06 · Next review 2027-04-06
Short answer
A troubled programme reset is the point where an HR transformation or technology programme is behind plan, over budget or failing to deliver expected outcomes, and leaders need to decide what to change before continuing. Confirming the scenario requires separating visible delivery symptoms from the underlying causes, which often sit in scope, governance, design decisions or readiness rather than in the delivery team alone.
Definition
A troubled programme reset describes a mid-flight or post-go-live situation in which an HR programme has materially deviated from its intended timeline, cost or outcomes. The scenario is defined by the need to re-establish an evidenced view of what is wrong before re-planning, so that the reset addresses causes rather than repeating the same pattern under a new plan.
Why it matters
When programmes stall, the instinct is often to add resources, change delivery partners or compress scope. Without a diagnosis, these actions can treat symptoms while leaving the original causes in place. A structured reset helps sponsors decide whether to continue, re-scope, pause or re-sequence, and protects both the investment already made and the organisation's confidence in HR-led change.
Business symptoms
- Repeated re-baselining of the timeline without a clear explanation of the causes
- Design decisions reopened late in the programme
- Testing or parallel runs reveal data, payroll or process issues not seen earlier
- Low adoption or high use of workarounds after go-live
- Sponsors and delivery teams describe the programme's status differently
- Local or country teams report that global design does not fit statutory or operational reality
Common challenges
- Establishing an objective view of status when stakeholders hold different narratives
- Distinguishing delivery execution issues from upstream design or scope issues
- Maintaining business continuity while the programme is being reset
- Rebuilding sponsor and stakeholder confidence
- Re-sequencing work that depends on unresolved governance or operating model decisions
Root causes
- The programme started before the underlying problem and target operating model were agreed
- Decision rights and governance across HR, IT and business units were unclear
- Data quality, process variation or statutory requirements were underestimated at the outset
- Change and adoption capacity was not assessed against the planned pace
Framework
| Evidence to look for | Likely source | How to interpret it |
|---|---|---|
| Re-baseline history and stated reasons | Programme governance records | Repeated re-baselines with changing reasons suggest unresolved upstream causes |
| Late-reopened design decisions | Design authority logs | Frequent reopening indicates unclear decision rights or an unagreed target model |
| Defects by category in testing | Test management records | Clusters in data or statutory areas point to readiness gaps rather than build quality |
| Post-go-live workaround levels | Service desk and manager feedback | High workaround use signals adoption or fit issues |
Business impact
- Continued spend without corresponding progress toward outcomes
- Operational and compliance risk if payroll or core HR processes are affected
- Reduced employee and manager trust in HR systems and processes
- Loss of executive confidence in future transformation proposals
Target outcomes
- An evidenced, shared view of what is wrong and why
- A clear decision on whether to continue, re-scope, pause or re-sequence
- Root causes addressed in the reset plan, not only delivery symptoms
- Governance and decision rights clarified for the remainder of the programme
Transformation approaches
- Run an independent diagnostic tracing programme symptoms to root causes
- Separate technology, process, data, governance and operating model causes
- Re-confirm the problem statement and target outcomes with sponsors
- Re-sequence the plan so that prerequisites are resolved before dependent work resumes
Technology implications
Technology is considered last, after the problem and target outcome are agreed. These are capability areas to evaluate, not product recommendations.
- Evidence-based programme diagnostics
- Governance and decision-rights review
- Data and process readiness assessment
- Adoption and change impact assessment
Assessment questions
- 01Can the programme's original problem statement and target outcomes still be stated clearly?
- 02Which issues are execution-related, and which stem from earlier design or scope decisions?
- 03Are decision rights for design choices clear and respected across regions and functions?
- 04Have data, payroll and statutory requirements been validated in every in-scope country?
- 05Is adoption being measured, and what do workaround levels indicate?
Examples
Illustrative examples — not claims about any named organisation
- A multi-country core HR programme repeatedly delayed in testing may find that local statutory payroll requirements were not captured in the global design.
- A programme that went live with low adoption might discover that managers were not consulted on process changes that affected their daily work.
MBT perspective
MBT approaches a reset as a diagnostic question, not a delivery-management exercise. Symptoms are traced through the seven-level hierarchy to their causes, every finding carries its evidence basis, and contested views between stakeholders are disclosed rather than silently resolved. Where root causes sit in governance, structure or operating model, MBT states that a re-plan alone will not fix them. MBT does not assess or name delivery partners or vendors.
Key questions people ask
- Is a reset the same as replacing the delivery partner?
- No. Changing partners may sometimes be part of a decision, but a reset starts by diagnosing causes, which often sit outside the delivery team.
- Should the programme pause during a reset?
- It depends on the diagnosis. Some work can continue safely while dependent work is paused until prerequisites are resolved.
- Does MBT assess vendors or delivery partners?
- No. MBT is vendor-neutral and focuses on problem causes, capabilities and readiness rather than named providers.
- Who owns the reset?
- HR leadership with the programme sponsor, supported by finance, IT and the affected business and country leaders.
Sources
- Employment Outlook
OECD
Background on organisational and technology change affecting work.
- World Employment and Social Outlook
International Labour Organization
Context on work organisation during structural change.
Explore this scenario for your organisation
MBT researches your company and geography, then offers scenarios as possibilities to confirm or reject before any roadmap is built.