Hands busy. One fact needed.
Picture someone standing at a bench with dirty hands and a phone in their pocket. They want one fact, fast, or they want to record one change without opening a spreadsheet.
- asked
- how many pallets are left on line two
- answer
- 14 pallets, counted ten minutes ago
- said
- mark line two cleaned
- read back
- line 2 cleaned at 15:20 — confirm?
Confirmed by Sam · kept in the shift record
Illustrative example · one fact asked, one change recorded
The situation
Most operational software is designed for the person entering data, not the person doing the work. The result is a system that is accurate whenever somebody sits down later and remembers, which is to say a system that is accurate about the past and wrong about the present.
How this usually goes
The person doing the work is the person least able to use the software while doing it.
Data entry is deferred to the end of a shift, so the record is a reconstruction.
The workaround is a notebook, a photo, or a message to someone at a desk.
Nobody blames the design, because the design is invisible and the person is not.
What happens here
Voice, phone, or controller, with every write confirmed and logged.
1. Asking is cheap
A question in plain language, spoken or typed, returns one fact rather than a screen to navigate. The interaction is sized for someone who has fifteen seconds and one free hand.
2. Names are treated as a lookup problem
People say what things are called on the floor, not what they are called in the database, so the system reconciles vocabulary rather than requiring the person to learn its own.
3. Structured parts stay structured
Where the work has a real vocabulary, such as a location code or a machine identifier, the system understands it precisely instead of guessing from context.
4. Every write confirms
A change is read back before it is committed, in the words the person used, because a misheard quantity that silently becomes a record is worse than no record.
5. Every write is logged
Who recorded what, when, through which surface, and what was confirmed. A convenient path into the record is not an unaccountable one.
The wider point
Interaction is not one surface. Voice, a controller, a wearable, a camera, and a screen are all ways of expressing intent, and the system is built so that intent arrives the same way regardless of which one produced it. That is what allows the easy path and the audited path to be the same path.