People use the bedside terminal in short bursts, several roles on the same device, interrupted constantly. The question is what someone coming back to it has to work out again before they can carry on.

A machine working next to someone in care has to make its intention clear before it moves. Three things carry most of the weight: how it announces, how it asks, and how it stops.

Care that used to be written down becomes a workflow, and then the workflow starts dictating the care. We try to keep the record true to what happened without turning a nurse into a typist.

Years of measurement are only worth something if the person can see change rather than numbers. So the question is how that history is arranged, and how much it is allowed to claim.

Supply and demand balance themselves most of the time. The operator steps in rarely, and when they do it matters, so the design has to carry someone through long quiet stretches without dulling them for that moment.

The people running the plant did not design it, and the panel they run it from is small. It has to show what the machine is really doing, and make the safe move the obvious one.

Map data is built, versioned and localised long before anyone drives on it. Holding one design together across regions, vehicles and model years is a specification problem more than a screen problem.

Half the system is in the car and half of it is not, and nothing guarantees the link between them. What still works when it drops is the real design.

One account ends up holding devices from different years and different divisions that were never meant to meet. They need a shared idea of the place they are in, and each of them has to fit into it.

Three metres away with a remote in hand, and the same design has to work at four inches. The distance changes and the input changes, and the structure underneath has to survive both.

Hundreds of products inherit an interface from people they will never meet. The standard has to be exact enough to build from and general enough to outlast the model that prompted it.

Some people reach a system through a channel the designer never uses: a hand that cannot point, an eye that points instead, a screen nobody sees. We build that channel as a way in, not as a fallback.

One person is responsible for a whole bay of machines, and each one stops for its own reasons. A single screen has to say which machine needs someone, and why.

Product data outlasts the people who typed it in, and different departments come to it with different questions. One structure has to answer all of them without turning into a form.

Programming a robot, running it, and getting it back after something goes wrong are three different jobs at one console. Most of the work is making sure they never get mistaken for each other.