Skip to main content
GullySystem
A practical guide

Staff still avoid the software: retrain or change the setup?

Ganesh HSStrategy and Technology, GullySystem
Practical advice · 5 min read

In this guide 6 sections
The short answer

Test the setup before booking more training. If the main task takes longer than paper, one required field blocks the save or the mobile screen is a shrunk desktop page, change the configuration first. Retrain only when the task is sound and staff simply do not know it.

Run three quick tests before booking a trainer

More training feels responsible, but it fixes only one cause. Staff who avoid a system are often doing something sensible. They avoid a tool that costs them time. Run three tests this week before you spend anything.

Pick your busiest operator and watch them for an hour, ideally during the evening rush when shortcuts matter most. Do not coach. Count the clicks, the waits and the moments they reach for a notebook, a calculator or a carbon copy pad.

The tests below take a day in total.

  • Time the main task on paper and in the software
  • Find the field that stops a save
  • Open the mobile screen on a real phone

Does the main task take longer than paper?

Time a counter bill on paper. Then time it in the software, with the same operator. If paper takes forty seconds and the screen takes two minutes, no workshop will change behaviour. Staff will keep the notebook. The data gets entered later, or never.

Look at why. Typical causes are a customer search that needs the full name and three screens for a simple sale. Others: a product list sorted alphabetically instead of by what sells, and a print preview dismissed every time.

Remove steps first. Every click counts. A shortcut that saves ten seconds, multiplied by hundreds of bills, changes a day. Barcode scanning, a default customer for walk in sales and a saved print template are the usual wins.

Is one field blocking the save?

Ask staff which message they hate most. It is often a mandatory field that nobody has the answer for: a tax category, customer address, vehicle number, supplier invoice date. They type a dash or a dummy value to get through, and the data becomes useless anyway.

Check the required fields against what the person has in hand at that moment. A field the counter cannot know should be optional, or filled later by the back office. Defaults help, such as today’s date and the usual payment mode.

Count how often the same filler value appears in a report. Dummy text is evidence. Sort the customer table by phone number, and a column of 9999999999 says everything.

Is the mobile screen a shrunk desktop screen?

Hand the app to a delivery driver or a field technician. Ask for a proof of delivery photo and a signature, nothing else. If they must pinch, zoom and scroll sideways to see a job, the screen was never designed for a thumb. They will phone the office instead.

A usable mobile view shows five items at most: the job, the address, a call button, a photo upload and a status change. Everything else belongs on the desktop. Check it in sunlight and with one hand. That is where it is used. A button that sits under the thumb of a gloved driver beats a menu that looks tidy.

If the mobile design is poor, training will not help. Ask the vendor for a reworked screen.

When training is the right answer

If the billing task is quick, the fields make sense and the screen works, then the gap is knowledge. Look for who is stuck: new joiners, one shift, one branch. A targeted session for that group works better than a repeat of the full course.

Keep it short. Build it around their own tasks, with real invoices from last week. Two sessions of forty minutes beat one full day, and the second one can cover only what people got wrong in between. Follow with a champion beside them for two days.

Start with the stopwatch. Time one task today, write the result on a sheet and decide from the number.

Retrain or reconfigure test sheet

Worksheet in three test blocks. The first records the main task time on paper against the software, by operator. The second lists required fields with the filler values found in reports. The third notes the mobile screen check: taps needed, scrolling, readability outdoors. A final row records the verdict.

Open a blank worksheet to print

Questions owners ask

How do I know staff are avoiding the system and not just slow?

Compare records with real activity. Receipts keyed in batches, notebooks still on the desk and spreadsheets that get updated first are signs of avoidance.

Can I ask the vendor to change the setup?

Yes. Field rules, defaults, menu order and mobile layouts are usually configuration. Bring your timings and the filler values as evidence, and ask for a date.

What if staff resist even after the fixes?

Then the issue is habit or incentive. Make the system the only source for reports, approvals and payouts, and have managers use it in meetings.

Is a refresher course ever wasted?

It is wasted when the setup is the cause. After the setup is fixed, a short refresher on the changed screens is worth it.

Browse all guidesBack to top ↑
Next step

Have a specific situation to work through?

This article covers the general case. Tell us what you’re actually dealing with and we’ll respond directly.

Share Your Requirements