Systems that go live and then go unused are common. The cause is design, not willingness. When entry increases and nothing comes back, no system holds.
Count how many times an operator must touch the screen to finish one operation.
02
Strip out what a machine signal can supply
Quantity, start and end times, equipment state — anything the machine already knows should not be typed.
03
Give the operator something back
Put next-operation visibility, current drawings and material location on the same screen.
04
Trial it on the floor and fix it
Place the terminal at the real work position and use it for a few days.
Why projects stall here
The question most often skipped in entry design is "what does the operator get out of this?" Managers get data; operators get more work. Left as it is, that asymmetry produces entries filled in for form's sake.
Data filled in for form's sake is worse than none. The numbers exist, so analysis happens — on numbers that do not match reality.
Procedure
Following the order matters more than perfecting each step.
STEP 01
Count the taps
Count how many times an operator must touch the screen to finish one operation. Past three, redesign. Gloved hands, bright light and narrow aisles are part of the constraint.
STEP 02
Strip out what a machine signal can supply
Quantity, start and end times, equipment state — anything the machine already knows should not be typed. Let people enter only what the machine cannot know.
STEP 03
Give the operator something back
Put next-operation visibility, current drawings and material location on the same screen. It should be a screen people come to in order to check, not only to enter.
STEP 04
Trial it on the floor and fix it
Place the terminal at the real work position and use it for a few days. Mounting height, glare and movement patterns only surface here, not in a meeting room.
Common mistakes
Patterns that recur in implementation discussions.
Common mistake
Putting the office screen on the floor
The floor stands, wears gloves and looks briefly. Information density and touch targets have to differ completely.
Common mistake
Pushing exception handling onto operators
More choices requiring judgement means slower entry and more errors. Handle exceptions on the supervisor screen.
Common mistake
Putting every function on one screen
An operator needs only the current task. With too many items, finding the right one takes longer than the entry itself.
Common mistake
Deciding placement last
A terminal off the movement path does not get used. Position matters as much as the screen.
Checklist
Confirm these are in place before starting.
Entry is three taps or fewer per operation
Anything obtainable from a machine is collected automatically
A lookup function useful to the operator is on the same screen
Touch targets and text size suit floor conditions
Terminal placement sits on the actual movement path
A floor trial has been run and changes made
Tools for this stage
The procedure is the same without any product. These shorten the steps.
Designing shop-floor data entry — frequently asked
Questions that come up during evaluation.
Kiosk or tablet?
A fixed kiosk suits work done at one position; a tablet suits frequent movement. Look at the movement pattern first.
Operators find logging in tedious
Badge tags or barcodes replace it. Username and password entry is the first procedure a floor abandons.
How do we reduce entry errors?
Narrow the choices, replace typing with scanning, and warn immediately on out-of-range values. Blocking at entry beats validating later.
What if the floor resists the change?
Designing with a few early users and letting them explain it to others works well. Introduced purely as an instruction from above, it stays a formality.
Sources and standards
Terms and procedures on this page follow the public standards and official sources below. Figures are as of each source's publication date.
ISO 9241-110:2020, Interaction principlesDialogue principles such as suitability for the task, self-descriptiveness and error tolerance that shop-floor screens should follow.