Nonprofit implementation guide
Guide 6: Prepare people and go live
Build adoption around changed work, protected staff time, and a staffed support path.
Describe the change by role
For each affected role, state what people stop doing, begin doing, decide differently, and need to understand. Explain why the change matters and which parts remain unsettled.
Involve frontline staff and people affected by services when appropriate, safe, and purposeful. Participation should have a clear decision boundary and should not expose protected information.
Practice real tasks
Use role-based practice with safe examples, job aids, accessibility needs, supervisor reinforcement, and time for questions. A feature tour does not show that a person can complete accountable work.
Name the launch support channel, triage owner, severity rules, office hours, escalation path, and what belongs with the software vendor, consultant, administrator, or business owner.
Stabilize before expanding
Monitor adoption, exceptions, backlog, record quality, support demand, service continuity, and unresolved risk during a defined stabilization period. Do not add optional scope merely because the project team is still assembled.
Use the stabilization review to accept the operating model, extend targeted support, correct defects, or pause further change.