Implementation 8 min read Updated September 2026
How to roll out a system without disrupting the routine
Rollouts fail for almost the same reason every time: everything is launched at once, in a busy period, with nobody inside the organization leading it. The order below makes it possible to go live gradually, one process at a time.
1. Start with one painful process
The first process to go live should be the one everyone agrees is painful: attendance, exits or maintenance. An early success in one process buys cooperation for all the rest.
2. Map the structure and the roles
Before anything is configured, map it: which frameworks and groups exist, who holds which role in each, what requires approval and who sees what. An inaccurate map creates double work later.
3. Data and permissions before training
Data and permissions come before training, not after. A staff member who logs in for the first time and sees their real group learns in five minutes. Someone who logs into an empty environment does not come back.
4. Train by role, not everyone together
A single session for the whole staff wastes the time of most people in the room. A counselor needs three actions, a director needs to know where the overall picture is, a guard needs one screen. Training by role takes less time and sticks.
5. Pilot with one group, then expand
A two week pilot with one group reveals what mapping does not. After a small correction, expanding to the rest is mostly technical, and whoever leads it already has staff who have worked in the system.
Want an implementation plan for your organization? In one session we map the structure and propose a go live order.
Book a demo 