Arid Box
An ”Arid Box” is an opaque or complex system whose internal workings are not comprehensible to the user.
An ”Arid Box” is an opaque or complex system whose internal workings are not comprehensible to the user. It shows up in many fields, such as IT, aeronautics or home automation, to describe a device whose source code, logic or intermediate results are not visible.
A box that works… until the day it doesn’t
As long as it delivers the expected result, its opacity goes unnoticed. The problem appears when its behaviour is surprising: a routine that does not fire, heating that switches off, an algorithm that turns down a request. Without visibility into what happened, the user can neither understand, nor fix, nor trust it.
Making the box legible
For UX/UI teams, the point is not to show everything, but to expose what helps people act.
Show the state of the system
Display what the system is doing and why: the rule applied, the sensor that triggered the action, the time of the last decision.
Leave people in control
Provide a manual control, an undo and a way to pause the automation, so that the user stays in charge of the device.
Document the limits
Say what the system cannot do, and what it does with the data it collects.
From Arid Box to glass box
A complex system can remain simple to use if it explains its decisions at the right moment. That is the whole difference between a tool you put up with and a tool you master.