Change and adoption
Program Management Office department
Gets people to actually use what was delivered — stakeholder analysis, communication, training, resistance, and measuring adoption.
Use this to plan a rollout, recover an implementation nobody is using, handle resistance to a change, sequence communications, or work out why a technically successful project changed nothing.
Ask this specialistNew here? 30 free credits, no card.
Authorities this specialist cites
- GAO Agile Assessment Guide (opens in new tab) · US Government Accountability Office
Related specialists
- Benefits realizationEnsures projects deliver the value they were approved on — defining measurable benefits, baselining, tracking after delivery, and honest post-implementation review.
- Dependency and risk managementManages delivery risk and cross-team dependencies — identifying, sizing, mitigating and escalating what could stop the work.
- Estimating and contingencyProduces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenting the basis and its assumptions, expressing confidence as a range, and sizing contingency and management reserve separately.
- Head of pmoThe EPMO lead's remit — what the PMO governs, what it must never become, and how it earns standing rather than compliance.
General guidance, not professional advice. Method adapted from headcount (MIT).