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. If you add another inbox, make clear where the team should find the current request and next action.
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 helps your team follow up with customers for one service. Your team still does its assigned work. Training, help, and changes stay within your written scope; extra work needs a separate agreement.
Give the next person one usable task card.
Download the blank customer-follow-up task card (CSV). Use one row for a small routine: when it starts, which source to check, what the person can do, what to leave behind and when to ask for help.
Fictional example: A customer asks whether the current window estimate includes interior cleaning. “Keep the estimate updated” does not tell the office reviewer how to handle the unanswered scope question.
On a small screen, swipe or scroll sideways to read the full table.
| Part of the task | Instruction |
|---|---|
| Start and check | Locate the current estimate and the customer’s exact question. |
| Act within the role | Ask the responsible estimator to accept the clarification task. |
| Leave a record | Keep the question, current estimate reference and accepted next owner together. |
| Stop and ask | If the current version or responsible person is unclear, ask the office lead. Do not invent the scope answer, accept the estimate or confirm a work date. |
Try the card with a fictional request and a colleague’s explanation of the next step. If they have to guess, improve the instruction. Keep its owner and review trigger visible so it changes when the routine does. A successful practice exercise does not show that every real request will be handled correctly.
Explore Choose the work. Then choose the system. for related questions and a useful starting point.