Why staff go back to the paper register after an app launch

A register line takes seconds. Date, name, item, quantity, initials. The app version often wants a login, a menu, a search box, a dropdown, a keyboard, a confirm button and then a success popup that must be dismissed.

Stand beside a counter clerk for one busy hour and count the taps for the five most common entries. If the app needs double the effort of the register, staff drift back to paper by the second week, whatever the manager says.

Trim each screen to the fields that matter. Keep the last used branch, product or customer as the default, and add a repeat button for the entry that the same clerk makes forty times a day.

A goods-inward screen asks for the supplier invoice number, batch code and expiry date. The driver at the gate holds a delivery note that carries none of them. The clerk writes the line on paper and plans to key it in later. Later never comes.

Required fields that staff cannot know at the point of entry are the most common reason an app is bypassed. Mark them optional, or allow a pending status with a reminder sent to the person who can supply them. Do not block the save.

Walk through each mandatory field and ask who knows the answer, and when they know it. If the answer is “accounts, tomorrow”, the field belongs on a later screen. Not here.

At launch, head office sent an announcement. Nobody was told to check usage on Friday. Two weeks on, three counters are back on paper and the branch manager still assumes that everything is entered in the app.

Name one owner per branch, ideally the shift supervisor or the accounts clerk who reads the register at close. The job is small. Open the usage report each morning, ask why entries are missing, and pass a short issue list to the developer every week. Without this role the app has no pulse.

Give the owner a visible number, such as app entries today against register lines today, written on a board by the door. A figure everyone can see beats a circular nobody reads.

Sessions often go to branch managers, who rarely make the entries. The counter clerk, the picker and the night supervisor learn from a colleague who learned from another colleague, so mistakes travel along with the shortcuts.

Train by task, not by menu. Hand each role a card with its three daily jobs, shown as screenshots, in the language staff actually speak. Run the session at the counter, in a quiet half hour, on the devices they really use.

Then keep a floor walker around for the first week, sitting with each shift once. Questions asked at the shelf get answered in seconds. Questions saved for a meeting never get asked.

Collect the paper registers still in use. Sort their columns into three piles: those the app already holds, those it lacks, and those nobody reads. The last pile is waste in both formats, so drop it.

Pick one counter and rebuild its main screen in the register’s column order, so it reads left to right as the paper did. Test it with the clerk before it reaches any other branch.

Retire the paper on a stated date, not by neglect. Keep the old register in a locked drawer until the first month-end closes without a single gap, then archive it.