Order point-of-sale devices online
B2B Web design, E-commerce, FinTech
Existing Elavon SMB customers who:
Insight:
This project was about more than UI work, it focused on digitizing and simplifying a sales experience for users with varying levels of tech comfort.
Building on research-based personas, I mapped the user journey and tasks needed to order a POS device.
Initially, requirements for this project were unclear (e.x., branding, payment methods, number of products). I designed exploratory screens to start conversations and surface open questions and gaps.
Impact:
These early designs helped uncover user and business needs, such as gaps in the purchase flow and unclear pricing, which accelerated cross-functional alignment and drove requirement clarity.
After refining the requirements, I created a Figma prototype, developed a usability testing plan, and conducted an unmoderated usability test via UserZoom.
Participants:
16 SMB customers
Key Measurements:
Task success and qualitative feedback
Research Objectives:
Success Criteria:
I refined the designs based on usability testing and team critiques, then partnered with developers to annotate key details for smooth, accurate implementation.
Note: See links for Figma prototypes.
After finalizing the UX for the talech Terminal flow, new business requirements required a full redesign.
New requirements:
Where should users select connection type and quantity without overwhelming them?
I evaluated the product page and landing page but found both would become too complex with added inputs.
I reviewed Toast, Stripe, Square, Home Depot, and Nordstrom. While none had the exact same challenge, I pulled inspiration from how they handled price clarity, order summaries, and product descriptions.
Initially, I explored multiple UI directions and created prototypes with annotations explaining trade-offs.
Initial explorations prototypeFrom those initial explorations, 2 options were the most viable - make all selections on 1 page, push selections to the cart page.
I ran an unmoderated usability test (15 participants via UserZoom) to determine which design resonated with users.
Results:
Option 2 was clearest, with 93% of users rating it “very clear”. However, Option 1 also had high clarity (60%).
Option 1: Make all selections on 1 page.
Question: Is it clear that the user can mix and match connection types?
Option 2: Make all selections in the cart page.
Question: Is it too jarring for the user to land directly in the cart?
I moved forward with Option 2, but a new challenge arose: enforcing the 5-device limit.
I designed 2 approaches:
I chose error messages based on team feedback that the dynamic selectors would be good for preventing errors but would make errors difficult to recover from. Additionally, we were under time constraints and the dynamic selectors would have taken significantly more time to develop.
Fine-tuning selections prototypeDue to complexities configuring the connection types on the backend, we were made aware that we needed to change the design again.
New requirements:
Based on these new requirements and very limited amount of development time, I removed the cart page from the flow entirely. This streamlined the flow and allowed for quick implementation.
Final design prototype
After the MVP release, the plan is to begin discovery to help inform how to position software offers in the marketplace in a way that customers will understand.
This was a project with a quick turnaround time and was the first project I worked on at Elavon, so there was a steep learning curve.
Various constraints proved to be a good opportunity to solve some complicated problems. The team also lost our Product Manager in the middle of the project, so it was a great opportunity to heavily collaborate with the Product Owner and Software Developers to make sure we were building what we should when we should.
With the new requirements I advocated for a 2 week design sprint before the developers started on the implementation, so I had to iterate and test very quickly. To help avoid last minute changes in requirements, our team learned that we need to more proactively communicate what we’re planning to implement with the backend team we have dependencies on.
If you like what you see and want to work together, get in touch!