UI/UX Design
From blank canvas to production-ready — research, design, handoff.
Product design is the discipline between strategy and engineering: the work of understanding what users need, deciding what to build, and specifying it clearly enough that developers can build it exactly right. We run end-to-end product design engagements — starting with user research and finishing with a pixel-perfect, developer-ready Figma file that includes every state, every breakpoint, and every interaction annotation. No gaps for developers to guess, no inconsistencies that break on screen three. The output is a product that works as well as it looks.
What's included
- User research & Jobs-to-be-Done mapping
- Information architecture & site map
- Low-fidelity wireframes & user flow validation
- High-fidelity UI with full design system
- Interactive prototype for stakeholder sign-off
- Developer-ready Figma handoff with annotations
How we deliver
- 1User research synthesis & insight report
- 2Information architecture & flow diagrams
- 3Wireframes validated with real users
- 4Hi-fi design files with responsive states
- 5Interactive prototype (Figma or Framer)
- 6Handoff specs with component annotations
5–8
user interviews before the first wireframe
100%
of prototypes usability-tested before handoff
40%
avg task completion rate increase post-redesign
0
handoffs without a developer walkthrough session
Technologies we use
- Figma
- FigJam
- Framer
- Maze
- Hotjar
- Notion
- Storybook
- Zeroheight
Why Origin for Product Design
Research before Figma — every time
We don't open a design tool until we understand users. Research isn't a phase we skip when the timeline is tight — it's the input that makes everything else faster.
User advocacy in every stakeholder review
When stakeholder opinion conflicts with user evidence, we present the research. Design decisions are traceable to user needs, not committee preference.
Every state designed, every breakpoint covered
Loading, error, empty, hover, focus — every component state is in the handoff file. Developers never guess. Implementations match designs.
Industries we serve
SaaS & Productivity
Complex workflows, dashboard products, B2B platforms
Consumer Apps
Retention-focused UX, social products, lifestyle apps
Healthcare
Clinical interfaces, patient-facing apps, WCAG-compliant design
Fintech
Trust-building design, transaction flows, regulatory UI
E-Commerce
Product discovery, checkout UX, conversion optimisation
EdTech
Learner engagement, content interfaces, assessment tools
“Every other agency presented mood boards. Origin presented user research findings. That told us everything we needed to know about who we were working with.”
Frequently asked questions
- How is your product design process different from just producing visual designs?
- We don't open Figma until we understand what users actually need. The process starts with research — interviews, analytics review, competitor analysis — then moves through information architecture and wireframes before any visual design begins. By the time we're applying colour and typography, the decisions about what to show, where to put it, and why have already been validated. Visual design on a wrong structure is expensive to fix; we fix the structure first.
- How much user research is typically included?
- For a standard product design engagement, we run 5–8 user interviews, a competitive UX analysis, and a review of any existing analytics or support data you have. Interviews are 45–60 minutes and focused on job-to-be-done, not feature requests. We synthesise findings into an insight report before any design work begins. If you have a larger research budget, we can run broader surveys or moderated testing sessions alongside the interviews.
- Do you design for mobile and desktop at the same time?
- Yes, with a deliberate sequencing. We design mobile-first for most consumer and B2C products — the constraints force clarity about what's essential. For complex B2B tools and dashboards, we start with the desktop view where the information density is higher, then adapt to mobile. We always deliver responsive designs for both breakpoints, not a desktop design with a footnote saying 'also make it work on mobile'.
- How do you handle stakeholder feedback that conflicts with what users actually need?
- With evidence. When a stakeholder wants to add a feature that user research suggests will go unused, we show the research. When there's genuine uncertainty, we suggest a usability test rather than a debate. Our job is to be the user's advocate in the room — we do that respectfully, but we don't abandon research findings to avoid awkward conversations.
- What does developer-ready handoff actually look like?
- A Figma file where every component is named, every spacing value is a token, every text style maps to a named style, every interactive state is designed (hover, focus, loading, error, empty), every responsive breakpoint is covered, and every non-obvious interaction has an annotation. We do a live walkthrough with the development team and stay available during implementation for questions. 'We couldn't build this' should never come up.