v/h

Technology for
everyday life.

The v/h journal / Visual note

Test the utility where it will be used

The room shouldn't need to be arranged around the device.

For a utility that uses a camera, a shadow across the work area could change what it can see. Asking the owner to find the right lamp each time would add work to an ordinary task.

A useful development check would keep the task fixed while changing one condition at a time. Try it beside a window, in evening light, and with the object turned a different way. Record the result and every adjustment the person has to make.

If the device needs consistent lighting, we should account for it in the physical design. A built-in light or a different viewing angle may be part of the solution. A larger model still has to work with the information the device can actually capture.

For v/h, the local agent and the object around it need to be designed together. The owner should be able to use a new capability in an ordinary setting with familiar controls.

The camera example is illustrative. Our first utility is still in development, and dependable use in ordinary conditions is a requirement we have to prove.

An ivory v/h logo on charcoal. The headline reads Test it where it will live. A red rule separates three prompts: Change the light. Turn the object. Count requests for help. The footer reads A proposed check during development, with vh.do. All lettering uses Neue Montreal.

Keep reading

Make the task status clear after the beep