Hidden information: what you need arrives late or stays buried
Aliases: delayed disclosure · buried terms · information hiding
What it is
Hidden information moves decision-critical information away from the moment of decision: the total price appears one step late, renewal terms sit inside a collapsed section, the key restriction is on page three. Its defining features are temporal and positional displacement — the information exists, is even compliantly "disclosed," yet is absent from the moment the user decides and the glance they decide with.
Why it happens
Decision quality is set by the information available at decision time; the total quantity on the page is irrelevant. Hidden information exploits two decay curves: attention decays with scrolling (below-the-fold content is expanded by a small minority), and information arriving late in a flow meets a decision already made — the user has clicked through several screens, sunk cost is accumulating, and the late disclosure rarely reverses anything. It is also the common carrier of the other classes: bury the fee (hidden information) and then make cancelling hard (obstruction) is the compound structure. The operational test is one sentence: "can the user see this piece of information, at the screen where they choose, without any extra action?" Information requiring expand, scroll, jump, or wait to see has been moved out of the decision moment — regardless of whether it was technically "disclosed."
Studying it
Price-presentation research is the direct evidence base: controlled comparisons of upfront total price versus drip pricing consistently show the latter raising final payment and suppressing comparison shopping; eye-tracking studies of disclosure position measure actual fixation rates on below-fold content; "post-hoc surprise" is proxied behaviourally by complaint and refund rates. Methodological caution: the regulatory standard ("was it disclosed") and the behavioural standard ("was it seen") differ enormously — compliance audits count existence, user research counts arrival, and the two reports cannot substitute for each other.
Where it stops holding
Information layering is legitimate: collapsed details are interface convention, and "not above the fold" is not automatically hiding — judgement must weigh the information's criticality for the decision and the availability of a summary layer as fallback. Reasonable temporal displacement exists (contract fine print at the end, with the key points up front on the confirmation page). And mobile space constraints make "everything up front" infeasible, turning the question into ordering: which information must be front-loaded, and by what priority — the answer ranks by decision criticality, not by legal-exposure anxiety.
Applying it
- Build a decision-critical information list: for every conversion screen, list the information without which the decision should not be made (total price, renewal terms, restrictions), and tag each item's first appearance in the flow.
- The front-loading rule: list items must appear on the screen where the irreversible choice is made, requiring no expansion of any kind.
- Verification: session-replay analysis — check whether real users' arrival at the critical information precedes their confirming click; arriving after means hidden-information residue, and the screen enters the fix queue.