LEARN. PRACTICE. GROW.Concept and mechanism
Stakeholder mapping should include people affected by change even when they are not assigned to the project. In a banking service, shift operators, functional users, technical teams, and investment owners can need different information. The board decides funding; RUN needs to diagnose faults and escalate. Communication is more than sending everyone the same file. Define needs, owners, channels, and timing, and confirm understanding of actions and decisions. In an international team, an opportunity to contribute in writing before a meeting can reveal constraints missed in a rushed call.
Guided application
Adoption also needs planned work. If the new workflow is installed but people still use spreadsheets, investigate needs, capabilities, and process obstacles. Involve representatives in design and rehearsals. Co-creation does not mean accepting every request; it helps reveal options and conflicts before stabilizing the solution. An emailed runbook does not demonstrate autonomy. Ask another operator to perform diagnosis using test data, observe gaps, and correct instructions. This evidence connects people readiness to operational acceptance criteria.
Before go-live, representatives from two shifts identify an alert and follow escalation in a rehearsal. The project records results, corrects contacts, and confirms coverage.
Common pitfalls
Confusing distribution with understanding; excluding shift users; treating resistance only as personal attitude; assuming installation means adoption.
Related topics: Justification, organization, and sustainability · Plan products and demonstrate quality
Acceptance needs people capable of using and operating what was delivered.
Reference: PRINCE2 7 Foundation syllabus · PRINCE2 Project Management Version 7