Show one task from beginning to end
Start with a familiar request, such as an estimate waiting for a reply. Show where the record appears, how the person knows it is theirs and what to update after acting. Keep the example within the work the team is actually expected to do.
A feature tour can be useful later. At the beginning, the important question is “What do I do next?” Give people a short routine they can repeat.
Make the everyday routine small
- Start: check the agreed place for assigned work.
- Act: carry out the appropriate next step.
- Update: record the outcome and the next responsible person.
- Escalate: flag missing information, unavailable staff or work outside scope.
- Close: leave the next shift a current record rather than a private memory.
Decide when the team checks the queue and what takes priority. Do not add another inbox without explaining which place is authoritative for this path.
An adoption problem may be a design problem
Fictional example: a team keeps writing estimate updates in a group chat. The new system has a status field, but nobody can tell whether “pending” means waiting for the customer or waiting for the estimator.
The answer may be clearer states and an agreed place for the next action, not another reminder to “use the system.” Ask the people doing the work what makes the update difficult.
Use a short teach-back
Give a colleague a fictional request and ask them to show where it goes, identify its owner and describe the next action. Then change one fact: the owner is unavailable, the customer asks a new question or the appointment moves.
If the routine breaks, note the exact point. Improve that instruction or handoff before expanding training. Keep the feedback about the process rather than blaming people for unclear design.
Review the routine after it meets real work
Look at repeated exceptions, duplicate updates and missing ownership. Select one improvement and explain what changed. Do not mistake sign-in activity for correct follow-through or staff satisfaction.
BusinessOS can support an agreed customer path, but your team still carries out its assigned work. Training, support and changes need to stay within the written scope; additional work should be agreed separately.