Shift
2023
Deliverables
User Flows · Wireframes · Prototypes · High-Fidelity UI · Component Library · Developer Handoff
Industry
E-commerce · Education · Consumer Mobile
Tools
Figma
Each department sold different products with different prices, formats, and buying behaviors, and each wanted their own way of presenting them. The students didn't care about any of that. They wanted to find a course, understand what it costs, and buy it without friction. The design challenge was building one system flexible enough to absorb every department's catalog without fragmenting into five different experiences, on a 7-week timeline.
The payment flow. The original policy allowed one credit card, period. During the project we heard directly from students that this was a real barrier: course prices were high enough that many people needed to split the cost, and a single-card limit was killing purchases at the final step. We changed the strategy. I designed the checkout to support payment across two credit cards, plus debit and local payment methods. That meant redesigning the entire payment stage, handling split amounts, validation per card, and failure states when one card goes through and the other doesn't. It made the checkout more complex to build but removed the single biggest obstacle between a student and a purchase. That decision came from listening, not from a brief. It's the part of this project I'd defend in any design review.
This was an agency delivery, so I don't have access to post-launch metrics. What shipped: a complete mobile commerce experience covering browsing through checkout, a component system flexible enough that departments could run their own storefronts without design drift, and a payment flow rebuilt around how students actually pay rather than how the institution preferred to charge. All delivered within the 7-week timeline.
Seven weeks meant no room for exploration theater. I mapped the full purchase journey across every storefront context first, identified where product types genuinely needed different treatment versus where consistency should win, and built the component system around that line. Client presentations happened every sprint, and the student feedback that reshaped the payment flow came out of those cycles. Handoff documentation was structured enough that the dev team built without back-and-forth.
