UX / UI Design

Our approach

We design digital products people can actually use — websites, apps, portals and the interfaces inside them. That covers the whole customer experience rather than the visual layer alone: what someone is trying to do, the steps between them and doing it, and the design decisions that remove friction from those steps.

Most projects that arrive described as a design problem turn out to be a structure problem. A beautiful interface over a confusing model is still confusing, which is why we start with the journey and the content before the surface.

Customer experience design

Customer experience is the whole path someone takes with you, and the digital product is usually the part where it succeeds or fails. The work that shapes it:

Research with actual users. For MUK Haircare, competitor research and customer interviews surfaced the real pain point — a lack of clear usage directions — which is what drove a content-forward experience with how-to videos through the product journey rather than a straight catalogue.

Journey mapping. Following a person end to end, including the steps that happen outside your product. For GPSL that meant remapping the user journey to make high-priority content findable, because the problem was navigation rather than aesthetics.

Workshops with the people who know. Sitting with the internal teams who handle the requests, the complaints and the exceptions. They know where the process actually breaks.

Prototypes before code. Wireframes and high-fidelity designs that let people react to something concrete while it is still cheap to change. For the SES content portal, discovery produced wireframes for core journeys and mid-fidelity designs before anything was built.

UI design and design systems

A design system is what stops a product drifting as it grows, and it is the deliverable that keeps paying after we leave.

For Skin Check Champions our scope was UX and UI specifically, after the charity restructured delivery around its own engineering and product teams: workshops, mapped user flows, high-fidelity mobile-first designs, a component library and design-system documentation, handed over in Figma for their team to build against — specified to WCAG 2.1 AA from the start.

For Safeproud, a strong design system steps administrators through form creation without overwhelming them — a problem we saw across every other form builder we reviewed.

Accessibility is part of design

Colour contrast, focus states, target sizes, heading structure and keyboard paths are design decisions, not a pre-launch audit. Building them in costs a fraction of retrofitting them, and for anyone selling into government, education or financial services it is a procurement gate rather than a preference. See accessibility and WCAG compliance.

What we solve

• Products that look finished but confuse the people using them
• Interfaces that grew feature by feature until nothing is where anyone expects
• Design that falls apart the moment a new page or state is added
• Teams shipping inconsistent work because there is no system to build against
• Accessibility discovered late, when it is expensive

What’s included

Discovery and stakeholder workshops, user research where the risk justifies it, journey mapping and information architecture, wireframes and high-fidelity design, component libraries and design-system documentation, prototypes, and handover in Figma your team can build from.

We are based in Sydney and work with organisations across Australia. Where a project needs build as well as design, the same team carries it through — see website development and app development.