In this guide 6 sections
Place a support person at each point where work happens, such as the counter, the stores and the accounts desk. Log every stumble on a shared sheet, fix small things the same evening and sort faults from unfamiliarity daily. Taper the cover as the week progresses.
Monday: stand where the work happens
On the first day, put one helper at the billing counter, one in the stores and one at the accounts desk. They stand beside staff, not in a back room. Distance kills help. A person with a headset in an office is too far from the stumble.
Each helper carries a laminated cheat sheet of the ten commonest tasks for that role, such as a credit note, a stock transfer or a petty cash voucher. They touch nothing unless asked. Hands off the keyboard. Their job is to watch, answer in a sentence and write down what went wrong.
Keep the old system readable but locked from new entries. Staff who can slip back to it will do so by lunch. Lock it. Print the day’s opening stock, pending orders and customer balances from it, so the first morning starts from a clean, agreed position.
- Counter: billing, returns, payment modes
- Stores: receipts, issues, stock transfers
- Accounts desk: vouchers, bank entries, ledgers
- Owner or project lead floats between all three
Log every stumble on one sheet
Use a shared sheet that every helper can open on a phone. Columns: time, person, task, what happened, screen name and a status. Skip opinions. Skip guesses. Write the observed fact, such as customer search took two tries because the phone number was entered with a space.
Tag each line when the helper is unsure: question, bug, slow, missing report or wrong data. The tags matter more than the details on day one. Patterns first.
A helper who fixes things silently hides the pattern. Log first, then help.
Tuesday and Wednesday: fix small things that evening
After closing, the project lead and the vendor sit down with the sheet for thirty minutes. Anything that takes an hour or less goes in that night: a renamed field, a default tax code, a reordered menu, a printer layout. Staff arrive on Wednesday to a screen that is already better.
Announce each change in a short note on the group chat, because people believe the project listens when they see their complaint gone by the next morning. That belief carries the remaining days.
Anything larger goes on a separate list with an owner and a date. Do not promise a week for a change that needs a month. Say so. Then name a stopgap, such as a printed price list taped beside the terminal.
Thursday: tell a design fault from unfamiliarity
By Thursday the sheet has a hundred lines. Sort them. If one task trips several people, or an expert from the vendor stumbles too, it is a design fault and the setup changes. If it trips only new joiners and the fix is a sentence, it is unfamiliarity and belongs in training.
A quick test helps. Count the steps against the old system. More steps? Redesign it. Same or fewer? Practise it.
Do not retrain a team on a screen that is genuinely awkward. Fix the screen. Then show people the change in five minutes at the start of the shift, standing at their own terminal.
Friday: taper the cover and set the week two plan
Pull helpers back from the quiet points and leave them at the busiest, then reduce the sheet review to once a day. Walk the floor. Ask staff which task still feels slower than the old way.
Close the week with a thirty minute review of the top ten items by count. Read them aloud, with the helper who saw each one standing in the room. Assign each one to the vendor, to training or to a process change, with a date. Agree who answers phones next week. Name the vendor engineer on call. State the hours covered.
Book the next review for the following Friday before you leave the room.
Go live week support log
Printable and shared sheet. The first block is a day by day roster showing where each helper stands. The second is a stumble log with time, person, task, screen, tag and fix status. The third is an evening fix list with owner, change made and announcement sent.
Open a blank worksheet to printQuestions owners ask
How many support people do we need?
One per busy work point, plus one floating lead. A small shop might need three people in total. A multi branch operation needs the same pattern at each location.
Should we run the old system in parallel?
Keep it readable for reference and lock it for new entries. Running both for new work doubles the effort and gives staff a reason to avoid the new one.
Who should be the support staff?
Trained champions from your own team, backed by the vendor’s people. Staff ask a familiar face faster than a stranger from outside.
When does go live support end?
When the daily log falls to a handful of lines and nobody asks for help at the counter. For most teams that is the second or third week.