The adoption playbook · free · no email
Go-live is when
the adoption work
starts.
The first four weeks decide whether the new system becomes the way work gets done or another tool people work around. This playbook gives you the week-by-week plan, the role-level training bar, the SOP template, and the Friday adoption tracker.
5 chapters · one sitting
Works with any system
SOP template · printable
Weekly tracker · printable
Chapter 01 · the dip
Why usage falls after launch.
Go-live day feels like the finish line. The data is in, the training happened, the first job runs clean, and everyone is briefly careful. Then week two arrives. Productivity dips as old habits fight new workflows: the S-curve every team rides after any real change. The dip is not a sign the system failed. It is the predictable cost of replacing muscle memory, and pretending it will not happen is how systems die.
Because the death is never dramatic. Nobody announces a rollback. A spreadsheet reappears “just for now.” Dispatch slides back into text threads. The data splits between two homes, neither is trusted, and within a few weeks the system is an expensive failure with a ribbon on it: live, paid for, and empty.
What separates the teams that climb out is not better software. It is structure through the dip: adoption run like a project instead of a hope. Usage measured from the logs, task completion per role, every wobble caught the week it starts, and a clear bar: every required role reaches the workflow-completion target written in the blueprint. The change frameworks underneath this playbook are Kotter and ADKAR, if your ops lead wants to check the homework; the chapters that follow are those ideas translated into field moves.
Most rollouts get support until go-live day, and the dip starts after the truck leaves. Plan the first month like it is part of the project, because it is the part that decides the outcome.
The dip, anatomized · weeks 1 to 4 after go-live · illustrative pattern, not measured data
Chapter 02 · the survival plan
The first four weeks, week by week.
Field advice, not theory: what breaks, the early warning, what to watch, and the one move that matters, for each of the four weeks after any go-live.
Week 1
The small breaks
What breaks
Small things, loudly: logins, permissions, and the one workflow that does not match how the work actually happens.
Early warning
Busy roles create workarounds because they have no slack to learn while doing.
What to watch
Every complaint, written in one list and triaged daily. Unlogged week-one friction becomes week-two folklore.
The move · Fix the small stuff the same day. The speed of the first fixes decides how much patience you get for the rest of the month.
Week 2
The valley
What breaks
Patience. The old way was faster for whoever had mastered it, and the new way is still slow in their hands.
Early warning
Veteran users reopen old tools because the old way is still faster for them.
What to watch
The first quiet workarounds: a side spreadsheet, a dispatch text thread, a paper ticket riding in a truck again.
The move · Name the dip out loud in the Monday meeting: it is normal and it is temporary. Then retire old access where it is safe to, so persisting is easier than reverting.
Week 3
The fork
What breaks
Consistency. Half the team is in the system, half works around it, and the data splits into two homes nobody fully trusts.
Early warning
A manager accepts work completed outside the system, teaching the team the workflow is optional.
What to watch
Task completion per role, and where managers get their numbers: from the system, or by asking people.
The move · Route everything through the system. If it is not in there, it did not happen. And leaders pull every report from the system, visibly.
Week 4
The habit
What breaks
Nothing, loudly. That is the trap: the leftover gaps stop being noticed and start being permanent.
Early warning
A role rarely logs in or keeps completing the same task late.
What to watch
The roles that never log in, and the tasks that always finish late. The weekly tracker in chapter 05 exists for this.
The move · Re-train the outliers role by role, on their real work. Keep named support owners active through the first four weeks after go-live.
Chapter 03 · the training bar
Attendance is not training.
A role is trained when the person can run their own week in the system, on your real data, unassisted. Not when they sat through a demo. Before you call training done, each of these people should be able to do their whole list with someone watching and nobody helping.
Role 01
The office manager
- Take a new call from first ring to booked job without leaving the system.
- Turn a closed job into a sent invoice the same day.
- Run the receivables list and send a day-31 reminder from the job record.
- Answer “where is that job” without calling anyone.
On real jobs and real data · no generic demos
Role 02
The field lead
- Open the day's jobs on a phone and see what changed since yesterday.
- Close a job with photos and notes so the office needs no callback.
- Flag extra work or a change from the field, the day it happens.
- Check tomorrow's schedule without a phone call.
On real jobs and real data · no generic demos
Role 03
The owner
- Read the week from one screen: sold, scheduled, completed, invoiced, collected.
- Approve an estimate or an invoice from a phone.
- Pull the receivables aging without asking anyone.
- Go a full week without personally relaying job information.
On real jobs and real data · no generic demos
Your operation may add roles: a dispatcher, a controller, a production manager. The bar stays the same shape: name the four things that role must do unassisted, and do not sign off until they can.
Chapter 04 · the SOP template
The shortest form the role can use during real work.
SOPs are what survive turnover. The go-live binder nobody opens is not one; a sheet the team actually reaches for is. Write one per role for the workflows that changed, using three rules:
- Start with one page, one owner, one trigger. Split a procedure when separate roles, triggers, or exception paths make one sheet hard to use.
- Written by the person who does the work, edited by their manager. Never the other way around.
- Reviewed when the workflow changes, not on a calendar.
Prints two sheets: this template and the chapter 05 tracker · nothing is sent anywhere
Standard operating procedure
One page · one owner · one trigger
SOP title
Name the procedure, verb first.
Owner
One role, not a person's name.
Trigger · the moment this starts
“When a job closes in the field”, not “weekly”.
Steps · who does what, in order
- 1.
- 2.
- 3.
- 4.
- 5.
Exception rule
When this does not apply, who decides, and where they note why.
Where this lives / last reviewed
The place the team actually looks.
Chapter 05 · the weekly tracker
You cannot manage the dip by feel.
Twenty minutes every Friday, three lists, same order. Usage comes from the logs, task completion from the records, and reversion signals from walking around. Adoption is measured, not assumed.
Usagefrom the logs
- Did every role log in this week, not just the office?
- Which roles did not complete their required workflows this week? Is that gap improving or repeating?
- Are logins trending up or down against last week?
Task completionfrom the records
- Jobs closed in the system versus jobs you know finished in the field.
- Invoices sent from the system versus written anywhere else.
- Estimates recorded in the system before they went out.
Reversion signalsfrom walking around
- A spreadsheet reappeared “just for now.”
- Dispatch slid back into text threads.
- Paper tickets are riding in trucks again.
- Someone asked a person for a number the system already shows.
The rule that keeps this honest: if a role still misses its workflow-completion target at week four, treat it as a training or design problem before a people problem. Re-train first, redesign the workflow second, and only then have the harder conversation.
One screen you trust is the goal. The tracker is how you earn it.
Print the tracker with the SOP template above and run it on paper if that is what your Friday looks like. The point is the ritual, not the medium: the week the tracking stops is the week the reversion starts.
30 minutes · no deck
Want this adoption plan built into your rollout?
This playbook works with whatever system you run. If you want it built in, we train each role on real data, document the changed workflows, and track adoption through the first month. The whole method is here.
