Product & compliance

Disclosure screens under audit

Designers present the happy path. Auditors photograph the path a tired customer takes at 11 p.m. after a declined top-up. Those two journeys rarely share the same screenshots.

Person holding a smartphone showing an app interface

Count the taps to the number

If the fee amount appears only after three navigations, record that. Clarity is not only wording—it is reachability. Our Disclosure Walkthrough Lab scores both the language and the distance from the decision button.

Watch secondary surfaces

Chatbot answers, email footers, and help-center mirrors often contradict the in-app copy. An audit that ignores them will miss the version customers actually quote in complaints.

Capture state, not intention

Engineering intent lives in tickets. Customer state lives in the build that shipped. Photograph the build, note the app version, and freeze a test account so peers can reproduce the same screen.

Write findings without design insults

“Confusing” is not a finding. “APR appears after confirmation on build 4.2.1; prior step shows only monthly payment” is a finding. Product can argue priority; they cannot argue the screenshot.

← Back to desk journal