I turned a fragmented purchase journey into a shared system, helping the team increase e-commerce conversion by 17%.
S / SITUATION
One customer could encounter different fields, validation rules and error messages depending on the platform. Separate squads had built each checkout, so each new requirement multiplied decisions, implementation and QA.
An anti-fraud requirement made that fragmentation a business constraint. Billing address was required on desktop, optional on responsive web and absent in the app. Patching each flow would preserve the same maintenance problem.
T / TASK & OWNERSHIP
My responsibility was to make the divergence visible, agree on what should be shared with Product and Engineering, and translate that agreement into an implementable field architecture. The goal was a predictable purchase experience that could absorb new requirements without three separate redesigns.
A / ACTIONS & DESIGN DECISIONS
Fields, states and reusable validation patterns.
Local payment, market and legal requirements.
Problem framing
I compared every step across the three surfaces and documented 23 divergence points. That changed the discussion from a visual preference to a concrete prioritization problem: which differences created friction, compliance risk or repeated work?
Systems thinking
I resolved 17 points into shared behavior and kept six differences explicit for market, payment or legal needs. A component library covered field states and edge cases, including keeping the order summary usable when the iOS keyboard appeared. Consistency meant predictable rules, with room for context.
Scope & delivery
I scoped the work around the checkout foundation and documented the behaviors engineering needed to implement. Desktop, responsive web and native app moved in phases. Payment integration remained a separate system; the app team had a migration path rather than an immediate replacement.
R / RESULTS & BUSINESS IMPACT
E-commerce conversion increased 17% in the 30 days following consolidation. The shared architecture also gave Product and Engineering one reference for future requirements. My contribution connected the audit, design decisions and delivery; the commercial result belongs to the cross-functional team.
Post-launch observation on e-commerce; not an isolated attribution to a single design change.
Naming the exact differences made alignment possible. A design system creates business value when it reduces repeated decisions and makes exceptions understandable.
I would extend the audit to adjacent purchase moments and combine funnel data with qualitative research to understand why behavior differs across surfaces.
