The interface is the argument
Every screen makes a claim about what matters. Most make it by accident.
A settings page with forty toggles is making an argument: that all forty are equally important and that you, the user, should decide each one. A settings page with four toggles is making a different argument: that someone already thought hard about the other thirty-six.
Interfaces are rhetoric. Size, order and position are claims. The biggest button says this is what you came for. The item at the top of a list says this matters most. The thing hidden in a menu says you probably will not need this. Users read these claims instantly, long before they read any text.
Accidental arguments
The trouble is that most interfaces make their arguments by accident. A feature lands at the top of the page because it was built most recently. A button is large because the component library's default is large. Over years, the screen becomes a transcript of the order in which things were shipped, not a statement of what the product believes.
Good design is largely the work of making those arguments on purpose. It means deciding, explicitly, what the one important thing on each screen is, and then letting everything else get quieter. That is a product decision disguised as a visual one.
Restraint is a position
Minimal interfaces are sometimes described as an aesthetic. They are better understood as a position: a willingness to say that some things matter less than others, and to accept the cost of being wrong about it.
Watch where people hesitate
The fastest way to find out what an interface is really arguing is to sit next to someone using it. Not a usability lab, just a real person doing their real job. Watch where their cursor pauses. Watch where they reach for a notebook, a spreadsheet or a colleague. Each hesitation is a place where the screen's argument and the user's reality disagree.
These moments rarely show up in analytics. A dashboard can tell you that a page was visited; it cannot tell you that the person on it was double-checking every number against a printout because they did not trust the system yet. Trust is built, or lost, in exactly those pauses.
Software built for operations teams makes this especially clear. When an approval sits in the wrong place in a list, a shipment waits. When a status label is ambiguous, someone phones someone else to confirm it. The cost of an accidental argument is measured in phone calls, and phone calls are invisible to the people who designed the screen.
An interface that refuses to choose is still arguing. It is just arguing that nobody was willing to decide.