Vertical layout and conversion
Strategy and Design
2026
Researcher and Designer

Project info
How a vertical collapse layout beat the legacy multi-step flow, was roadmapped for Q1 2027, and was adopted by Bill Pay and shipped in Q4 2026.
Role | Team | Method | Participants |
|---|---|---|---|
UX Researcher / Designer | Money Movement | Unmoderated usability benchmark (Optimal Workshop) | 35 completed |
————
01.
The Problem
The legacy consumer international wire flow splits a large amount of information across a multi-page step flow. The intent was manageable chunks, but the structure created friction.
Key information was easy to miss. Only 25% of participants found the wire cutoff time clear, and half rated it unclear. Many said they never saw it.
Send limits were findable, but not reliably. 65% found them easy to locate, while 25% found them very difficult.
Users had to waste time filling out the wire recipient info to find out their limits were maxed. The way the flow had been designed from a backend perspective meant that the user would not be able to know their limits until the last step before submitting the wire.
Users were abandoning the flow. a small percentage of customers who start a domestic or international wire in production never complete it.
————
02.
The Hypothesis
A single-page layout of vertically stacked containers that expand and collapse as the user progresses would improve clarity and confidence. Status affordances (current, complete, missing) would keep users oriented without forcing page changes.
We expected clearer information and the ability to edit earlier steps would reduce abandonment and increase the number of wires users complete.

————
03.
Approach
I ran two unmoderated usability studies with the same task (an international wire transfer) and the same four measures: findability of send limits, cutoff time clarity, perceived speed, and visual appeal. Both used post-task Likert ratings plus open-ended feedback.
Study 1, legacy multi-step flow: 20 completed participants
Study 2, vertical collapse prototype: 15 completed participants
————
04.
Results
The vertical layout matched or beat legacy on three of four measures.
Measure (% rating 4–5) | Legacy | Vertical Collapse |
|---|---|---|
Findability of send limits | 65% | 74% |
Cutoff time clarity | 25% | 40% |
Visual appeal | 65% | 73% |
Perceived speed | 80% | 73% |
Auto-populated fields and a clear step layout drove the findability gains, and participants described the design as clean and low in distractions.
What this means for completion: The usability study shows the vertical layout improved the things that cause users to stall: finding send limits, seeing cutoff times, and staying oriented. Fewer points of confusion should translate into fewer abandoned wires in production, which makes completion rate the key metric to track after launch.
————
05.
What the Data Told Me to Keep Working On
Cutoff time remains the top pain point in both designs. Subtle inline text doesn't work. It needs a persistent, high-contrast element such as a banner or countdown. Given that the research is conducted with non-customers, it would be something I would want to then test with actual customers to get a better understanding for our specific product.
Orientation matters. Legacy's progress bar likely explains its slight speed-perception edge, so the final design combines the collapse layout, a step indicator, back-navigation, and inline validation.
————
06.
Impact
Product: The PM and lead developer put it on the Q1 2027 roadmap.
Engineering: The developer noted the new flow reduces the API calls needed throughout the experience.
Cross-team: After I presented to the money movement segment, the Bill Pay team ran the same methodology on their Add a Bill flow, found the same result, and shipped it to production in Q4 2026.
Business: The legacy flow has a drop rate in production. The vertical layout targets the causes of that drop-off, and post-launch completion tracking will measure the lift.
————
07.
What I Learned
Using the same method on a different flow showed the pattern held up beyond my own project. It also showed that evidence is the fastest route to alignment, because both teams moved quickly once they saw the data.