Skip to main content

Research before assumption

UX and product design

Research, prototype and design clearer journeys around what people need to do.

When experience is the constraint

A feature can work technically and still fail the person using it.

UX and product design is useful when a journey is confusing, people abandon an important task or a team is debating solutions without evidence. We find the point of friction, understand its context and make the proposed change tangible enough to test. Qern helps product teams understand where people struggle and design a clearer way through. From Canberra, working nationally, we combine user research, journey design, interaction design, prototyping and usability testing so decisions are grounded in behaviour rather than opinion.

This may be the right fit when

  • People cannot complete an important flow without support.
  • A feature is available but adoption or successful use remains low.
  • Different teams hold different assumptions about what users need.
  • A new experience needs validation before a full build begins.

What the work can cover

Evidence, flow and interaction.

The method follows the decision the team needs to make. Research is only useful when it changes the product, and design is only useful when it can be understood, tested and built.

User research

Plan and conduct focused research that reveals goals, behaviours, constraints and the language people actually use.

Journey and flow design

Map the steps around an important task, remove avoidable friction and make responsibilities and system responses clear.

Interaction design

Define how screens, controls and states work together, including keyboard, responsive and accessibility behaviour.

Prototyping

Create a realistic enough model to test the difficult parts before the team commits to production engineering.

Usability testing

Observe people attempting key tasks, identify the barriers and turn the findings into prioritised design decisions.

Move from opinion to observable evidence.

The process starts with the decision at hand, then uses the lightest research and design work that can resolve it.

  1. Frame

    Define what needs to be learned.

    Agree on the audience, journey and decision so research is focused rather than broadly exploratory.

  2. Research

    Understand behaviour in context.

    Use interviews, review or usability sessions appropriate to the question and available access.

  3. Design

    Turn findings into a clearer journey.

    Shape flows and interactions around the evidence, including the states that are often missed between ideal screens.

  4. Test

    Check the design before building.

    Put the prototype in front of people, watch the important tasks and refine the decisions that do not hold up.

The design stays close to delivery.

Qern brings product design and engineering judgement into the same work. That keeps a prototype grounded in real constraints and helps the build preserve the reasoning behind the design.

You work directly with the person doing the work. Findings are explained plainly, trade-offs remain visible and the output is shaped for the next decision rather than a presentation deck.

Product strategySet the product direction and priorities before resolving the detailed experience.Custom web application developmentTake a validated journey into an accessible, maintainable engineering build.

Frequently Asked Questions

What is the difference between UX design and product strategy?

Product strategy decides what should be built, for whom and in what order. UX and product design works out how the chosen product or feature should behave so people can understand and use it.

Does Qern design interfaces or only conduct research?

Qern can take the work from focused research through journey design, interaction design and prototypes. The appropriate mix depends on the decision and whether an existing product or build team is already in place.

Can Qern improve an existing product?

Yes. Existing products provide useful evidence: current journeys, support questions, analytics and observable usability problems. The work can focus on one critical flow or a broader product experience.

What does usability testing involve?

Usability testing asks representative people to attempt realistic tasks using a product or prototype. The goal is to observe where the experience helps or obstructs them, then prioritise changes based on impact.

Start a conversation

Start a ux and product design conversation.

You do not need a finished brief. Tell us what you need from ux and product design and where you are stuck.

Step 1 of 3
First, a little about you.