01 · The problem
A whiteboard cannot leave the room
Deliveries into the cold warehouses were tracked on a whiteboard with post-it notes. It worked in the narrow sense that the information existed somewhere. It failed in two expensive ways.
The board was in a room. Managers had to be standing at it to know what was happening, which kept them separated from the teams and the product they were responsible for.
Product sat. When a delivery's status lived on a note only one person had looked at, items stayed outside cold storage past their window. In a food business that is not an inconvenience, it is a safety violation.
The legacy system was a physical object that needed constant babysitting.
02 · What changed
Put the state of the warehouse in a manager's hand
LinOS moved dock scheduling into a responsive web app. The scheduling grid held every door and every delivery window; a door detail carried the trailer and task information sitting behind each slot.
The goal was never to digitize the whiteboard. It was that a manager holding the current state of the warehouse can stand at the dock, with their team, and manage product, deliveries and people at the same time, instead of walking back to a room to find out what is true.
03 · Designing for the floor
Legible from a few feet away, in a cold building, in a hurry
The user group was stable. The same management staff used this every day, which removed the usual onboarding problem and let the interface assume some familiarity.
What it could not assume was proximity or attention. This is a physical job on a clock, so the requirements were blunt:
- Large touch targets, because it is used standing up and in motion, on whatever screen is to hand.
- Status readable at a glance from several feet away, not on close inspection.
- Structure that explains itself, because nobody stops to study a screen while a trailer waits.
Employee-facing tools get a fraction of the design attention customer-facing products do, and they deserve the same discipline. This is where I started designing for operators, a thread that ran forward into the call center and servicing portals I later built at BorrowWorks.