At BP, I had the exciting opportunity to redesign existing user journeys with a completely new research-backed design system. Except, the design system hadn’t been built yet, and I found myself needing components and patterns that hadn’t been created as I started tackling one particular journey: edit your payment card details. As a content-first designer, I believe effective content patterns are the backbone of any well-structured design system, so I found myself in our product guild meetings asking, do we use “continue” or “next” in our forms? What patterns do we have for when a user wants to edit their previous inputs? As no predefined solutions were available, I took the initiative to develop my own.
In collaboration with a design systems designer, content designer, and UX researcher, I used my squad’s “Edit card” journey to research and establish an Edit Pattern for BP’s new design system.
We set up an A/B inter-sample first-click test, where 50 participants engaged with two variants of the “Edit this card” page. Variant A had a detailed Edit CTA such as “Edit mobile payments,” whereas Variant B had a simple Edit CTA of “Edit.” The participants were given identical tasks and asked to select elements on the screen to complete these tasks.
Our results led us to set a research-backed pattern for content and interactions at BP. It also set a precedent for product designers taking ownership of design systems work in collaboration with other designers. This not only enhanced the user experience but also provided a framework for all future designers working on edit journeys.