Case Example 05 · Financial Technology

A composite onboarding flow, audited

The welcome is warm. The error screen is a locked door.

This is a demonstration. The screens below are a fictional composite modeled on language these companies ship every day. Names, figures, timelines, and policies are invented, and no engagement is implied. The method is the one we bring to client work, where every fact is supplied and approved by the responsible institution. Findings identify divergence from published standards and plain-language practice; they are not legal or compliance advice, and identity verification requirements are set by regulation and your compliance team.

Original · Findings · Rewrite

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 do.

Screen 2 · Identity verification. We couldn't verify your identity. The information you provided did not match our records. Your application has been placed under review.

Screen 3 · Under review. Thanks for your patience. Reviews may take some time. We'll notify you when a decision has been made. Need help? Contact support.

The findings

Critical

The customer cannot tell what failed.

"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. The company knows which one. The screen withholds the single fact that would let the person fix it.

Critical

The money question is not answered.

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.

Critical

No timeline, no status, no path.

"Reviews may take some time" is not a timeline. The screen offers no expected duration, no way to check status, and no action the customer can take to move it. Every question a reasonable person has at this moment goes to support, or to a competitor.

High

The register flips from celebration to case file.

Screen 1 is written by marketing. Screen 2 is written by compliance. The same person reads both, ninety seconds apart. The company's voice does not survive the transition to the one screen where the customer needs it, which is the pattern behind most of the failures we find.

High

"Under review" reads as suspicion.

Verification mismatches are mostly typos, 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. The exact tone the welcome screen promised against arrives on the next tap.

High

"Contact support" is a door with no handle.

No hours, no channel, no expected response time, no indication whether a person or a bot answers. For a customer whose deposit may be in flight, "need help?" is not an offer. It is the transfer of the company's problem to the person least equipped to solve it.

Medium

The customer is made to wait for a decision they could resolve in a minute.

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.

What it costs unfixed

Every customer who reaches Screen 2 is in the last step of a funnel the company paid to fill. Some abandon on the spot and open an account elsewhere. Some file a support ticket that a clearer screen would have prevented. Some, unsure whether their money moved, call their bank to stop the deposit, which creates a second failure downstream. And the screen they saw is the one they quote in the review, the complaint, and the tweet. The onboarding budget produced the traffic. The error screen decided what happened to it.

A 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.

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. Your scheduled deposit will not run until your account is open, so nothing has moved. 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 the method saw

The original flow is three screens written by three teams who never 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 it takes. Who answers. Voice Governance is the practice of deciding those facts before the screen ships, so the error state carries the same promise as the welcome.