Rollout, adoption and handover: making sure the old sheet really retires
Adoption fails when the new system is one more screen on top of old habits. Design for the daily tasks, set a retirement date and hand over everything in writing.
- Design from five daily tasks per role.
- A fact entered once removes the reason to keep a private sheet.
- Set a retirement date for the old record.
- Hand over accounts in your name from day one.
- We have not measured adoption on any build.
Quick answer
People use a system when it lightens their day. Write down the five daily tasks per role, show each role only its own screens, enter each fact once, test on a busy day and set a date when the old sheet stops being the record. Then hand over accounts, code, secrets and a tested restore, with maintenance in its own document.
Adoption in five moves
- Watch three people work. Write down each role’s five most frequent tasks.
- Show each role only those tasks.
- Make each fact get entered once.
- Test with real users on a busy day.
- Set a retirement date for the old record, and a champion per role.
On our clinic-queue platform each role sees only its own work. Reception has one login and a tab per doctor. Check-in and emergency walk-ins belong to reception. Doctors start and end their own consultation, and calling a patient in never changes the queue. An emergency walk-in goes in right after the consultation in progress and the rest renumbers. Alerts go out only when a position moves meaningfully. This is design intent. We have no real front-desk usage yet, so we have not measured adoption. Detail: will my team actually use the new system.
Handover in one list
Accounts and domains in your name, code in your organisation, environments and release steps, a list of secrets and who holds them, a tested restore, documentation, alerts, third-party services with renewal dates, a shadow period, and an exit plan. For a marketplace client we produced a full handover checklist and scoped a monthly retainer with explicit limits. Their details are under an NDA. Keep maintenance and new development in separate documents. Checklists: handover and maintenance.
Role-based screens are overkill for three people doing the same job, and no design fixes a process that was already broken. Fix the definitions first.
Next chapter: Tech and go-to-market together.
More by GarunaCDX
Keep going with the next handbook.
Chapter-by-chapter guides from the engineers who build these systems for clients.
