Transparency and usability are in tension; full disclosure makes the interface unusable

What it is

Every generated result carries a full model card: training data, limits, version, evaluation table. The card is longer than the result; the send control is pushed off the first screen. Transparency and usability are in tension; full disclosure wrecks the interface. This is not a value judgement that one ought to be a bit less transparent. It is that one screen cannot finish both jobs at full size.

Full disclosure makes the lookup job the only job. Send, compare, and edit have nowhere to happen.

Why it happens

The interface’s main task occupies layout, steps, and time. Disclosure is another task. Do both at full size and the main task’s completion falls: controls cannot be found, people quit before finishing the read, they scroll at the wrong level. The tension is resources, not “users hate knowing.”

If law or an organisation defines “full” as an appendix on every interaction, the product will make the appendix a wall that pops every time. On the compliance ledger the wall is transparency; on the use curve it is dropout. Layered disclosure (short by default, long on demand, complete in the archive) admits the tension; it is not laziness.

Studying it

Three densities: full disclosure every time, layered, almost none. Measure main-task completion, time, rate of opening the appendix on purpose, and whether a key limit can still be found afterwards. Independent variables: density, complexity of the main task, device width. Dependent variables: completion, point of abandonment, detection of the limit.

Completion collapsing while detection of the limit does not rise means full disclosure is hurting usability and not buying more being-informed.

Where it stops holding

A one-shot high-stakes confirmation (a transfer, a signature) can and should carry disclosure at full size, because the main task then is the confirmation. High-frequency low-stakes acts cannot. Paper or a file bundle is not limited to one screen, so the tension weakens. This entry is about the interface not fitting. Whether detail is understood, and whether it crowds a key sentence, are other faces of capacity.

Applying it

• On high-frequency acts, leave only the shortest limit that concerns this act. Full model cards and data statements go in settings or a document centre, not pinned to every result.
• When “full” is required, carry it in a one-shot confirmation flow, not a permanent sidebar.
• Measure who opens the appendix. If almost no one does, full disclosure is hurting people who are not consuming it.
• Check: whether send or adopt is still on the first screen, and the completion gap on the main task before and after filling disclosure. A drop in completion and near-zero appendix opens means the tension has already been won by the wrong side.

Related

• Same group: L5.05.1 Excess technical detail does not produce understanding · L5.05.2 Transparency must serve the user's next decision · L5.05.3 Information that cannot be acted on is noise · L5.05.4 Transparency is sufficient only if the user can change the next action from it · L5.05.5 Excess detail crowds out attention needed for key information · L5.05.7 Transparency does not necessarily produce trust; exposing complexity can lower it · L5.05.8 Different roles should receive different depths of explanation, not the same text
• Nearby: L5.02 Local and Global Explanations · L5.01 Types of Explainability · L1.02 Expressing Capability Boundaries
• Search terms: transparency-usability tension · full disclosure · layered disclosure