Case Example 05 · Financial Technology
A fictional onboarding flow, audited
The error screen won’t say which detail didn’t match.
The screens
Gluebank · mobile onboarding · three screens, in the order a new customer sees them
Screen 1 · Welcome. You're almost there! Link your bank and schedule your first deposit, and we'll take care of the rest. Welcome to money that works as hard as you do1.
Screen 2 · Identity verification. We couldn't verify your identity. The information you provided did not match our records2. ^3 Your application has been placed under review4.
Screen 3 · Under review. Thanks for your patience. Reviews may take some time5. ^6 We'll notify you when a decision has been made. Need help? Contact support7.
The findings
Findings are ranked by the likelihood and seriousness of misunderstanding, missed action, or harm. They are numbered in the order they appear in the document. A caret (^) marks the place where something the reader needed is missing.
- Critical The reader is likely to act wrongly or fail to act.
- High The reader can act, but with avoidable confusion, cost, or delay.
- Medium The message weakens trust or consistency without blocking action.
The tone flips from celebration to case file. 1
Screen 1 is written by marketing. Screen 2 is written by compliance. The same person reads both, ninety seconds apart. The voice the customer met on Screen 1 is gone by Screen 2.
The customer cannot tell what failed. 2
"The information you provided did not match our records" names no field. Name, date of birth, address, Social Security number: the customer entered all of them and is told one is wrong. In this example, the verification provider has identified which one. Whether a screen may name the field is a decision for the security and fraud teams, because the detail that helps a customer fix a typo could also help someone using stolen information. The screen withholds the single fact that would let the person fix it.
The money question is not answered. 3
Screen 1 invited the customer to link a bank and schedule a deposit before verification finished. Screen 3 does not say whether that deposit will run, has run, or is on hold. A person who has just been told they cannot be identified is now unsure where their money is, and nothing on the screen addresses it.
"Under review" reads as suspicion. 4
A verification mismatch can come from a typo, a maiden name, a recent move, or a formatting difference. The screen's language belongs to fraud investigation, and a customer with a mistyped address has just been told they are a case.
Nothing says how long the review takes. 5
"Reviews may take some time" comes with no expected duration, no way to check status, and no action the customer can take to move it. The questions a reasonable person has at this moment go to support, or to a competitor.
The customer is made to wait for a decision they could resolve in a minute. 6
If the mismatch is a typo, the fastest path is letting the customer correct it. The flow removes that option and routes a one-minute fix through a review queue, which is slower for the customer and costlier for the company.
"Contact support" is a door with no handle. 7
The screen gives no hours, no channel, no expected response time, and no sign of whether a person or a bot will answer. For a customer whose deposit may be in flight, "Need help?" hands the company's problem to the person least equipped to solve it.
The cost of leaving it unchanged
Every customer who reaches Screen 2 is in the last step of a funnel the company paid to fill. Some may abandon on the spot and open an account elsewhere. Some may file a support ticket that a clearer screen would have prevented. Some, unsure whether their money moved, may call their bank to stop the deposit, which creates a second failure downstream. And the screen they saw is the one they would quote in a complaint or a review.
A proposed governed version
Clear language requires the institution to decide the facts the original leaves unresolved. The version below shows what the screens could say once those decisions have been made and approved.
For this fictional example, assume the verification provider has identified an address mismatch, the institution’s security and fraud teams have approved showing it and letting the customer correct it, and its own data supports the timing and the common causes stated.
Gluebank · the same three screens
Screen 1 · Welcome. Welcome. Two quick steps and your account is open: confirm your identity, then link a bank. We won't move any money until your account is open.
Screen 2 · One detail to check. The address you entered doesn't match the one on your ID. This is usually a typo or a recent move. Edit your address or upload a document showing your current address, and we'll re-check right away. Most people are through in under a minute.
Screen 3 · We're checking now. Thanks. We're verifying your address. Most checks finish within one business day, and we'll text and email you the moment it's done. No money will move while we verify your identity. Once that is done, you can link your bank and schedule a deposit. If you'd rather talk to a person, we answer the phone 8am to 8pm Eastern at 410-555-0170, and chat is staffed the same hours.
What this example shows
The original screens read as if three teams wrote them and no one read them in sequence. The governed version is written as one conversation, and it does something the original never does. It tells the customer what the company already knows: which field failed, whether money moved, how long the check takes, and who answers. Voice Governance means deciding those facts before the screen ships.