Robin Avery
- Product Designer
- usable interfaces and service journeys
Studio profile
Robin Avery — Product Designer
Robin Avery is a Product Designer who cares most about the moment someone uses a product for real, without help, and still succeeds. Robin's focus is usable interfaces and service journeys, giving equal weight to the screen in front of a person and to everything that happens around it.
A studio combining strategy, engineering and commerce needs designers who can carry an idea from a whiteboard into a working product. Robin's role sits at that point of translation. On a Shopify Plus store it might mean an account area customers actually use; for a start-up in the incubation program it often means a first product simple enough to learn from.
With clients, Robin talks less about screens and more about people's circumstances. Who is in a hurry? Who is anxious about getting something wrong? What happens offline once the order is placed? Those conversations often surface operational details that change a design far more than any visual preference.
For Robin, usability and accessibility are the same commitment seen from two angles. Forms that explain themselves, generous touch targets, predictable navigation and language that doesn't assume expertise help people with disabilities and everyone else who is having a difficult day. Robin also resists adding features simply because they are possible.
Robin enjoys working with a client's front-line staff and with outside researchers, treating what they observe as primary evidence. Clients can expect to finish with products their customers find straightforward, a clearer view of their own service from the outside, and a team that has watched real people succeed.
Learn about the wider team, explore the studio services, or visit the contact page to start a conversation about your own product challenge and see how product design could help.
Designing a journey one decision at a time
People expect product designers to spend their days making screens look good. Robin spends more of them working out what someone needs to understand at each step. The starting point is a task rather than a page: booking a consultation, reordering a product, comparing two plans. What does the person know when they arrive, what must they decide, and what might make them give up?
Early work is rough on purpose. User flows and simple wireframes are tested with a few real users or, at the very least, walked through with the client’s customer service team, who know exactly where people get stuck. Only when the flow holds up does Robin move into high-fidelity design, using the system set by the design director and creative engineering lead. Polishing a flow that doesn’t work is the most expensive way to discover it doesn’t work.
Service journeys stretch beyond the interface. A checkout can be smooth while the confirmation email is useless and returns feel like a maze. Robin captures those touchpoints in a service blueprint, so the client can see which parts belong to marketing, operations or support. Handovers to engineering include annotated files, edge cases and acceptance criteria written together with the software engineer, leaving little to guesswork.
What a usability round usually reveals
- Labels that make sense internally but puzzle customers
- Steps that ask for information before explaining why
- Error messages that name the problem but not the fix
- Moments where people look for reassurance and find none
