How We Design
We don't design from answers.
We design from questions.
The work starts before the first frame in Figma. It starts with understanding the problem, the people, the context, and the opportunity.
From there, we explore.
We make.
We test.
We question.
And we keep refining until the idea becomes clear enough to stand on its own.
There is no fixed formula.
But there is a rhythm to the way we work.
Understand
Before designing anything, we need to understand what we're designing and why.
We look at the business, the audience, the existing product, the market, the technology, and the constraints around the project.
We talk to people.
We look at what already exists.
We identify assumptions.
We ask questions that might change the brief.
The goal isn't to collect information.
It's to find the thing that matters.
Explore
The first idea is rarely the best one.
So we explore.
Different structures. Different visual languages. Different interactions. Different ways of solving the same problem.
Exploration gives us something important: comparison.
It helps us understand not only what works, but why it works.
We don't explore endlessly.
We explore until a direction earns our confidence.
Make
Ideas become useful when they become tangible.
We move quickly from thinking to making — sketches, wireframes, prototypes, visual studies, working interfaces.
The fidelity changes depending on the question we're trying to answer.
Sometimes a rough sketch is enough.
Sometimes we need something that feels almost real.
We choose the simplest artefact that can teach us something.
Share early
We don't disappear for weeks and return with a finished answer.
We share work while it is still becoming.
Early feedback creates better conversations because there is still room to change the direction.
We explain the thinking behind decisions, not just the decisions themselves.
And we expect the work to change.
Feedback is not approval.
It is part of the design process.
Refine
Once the direction is right, we go deeper.
Hierarchy becomes sharper.
Interactions become more considered.
Typography becomes precise.
Motion finds its rhythm.
Edge cases become part of the experience.
This is where craft takes over.
The goal isn't to add more detail.
It is to make every detail feel inevitable.
Build together
Design doesn't end when engineering begins.
We work closely with developers throughout the process, because implementation is part of the design.
Technical constraints can reveal better solutions.
A prototype can reveal a new possibility.
A developer can challenge an assumption that would otherwise survive until too late.
We believe the best work happens when everyone is solving the same problem together.
Test against reality
A design can look convincing and still fail.
So we put it in front of people, devices, content, and real constraints whenever possible.
We test the things that matter.
Can people understand it?
Can they use it?
Does it behave as expected?
Does it still work when things go wrong?
The closer the work gets to reality, the less we rely on assumptions.
Know when it's done
Perfection is an infinite project.
We stop when the work has achieved what it needs to achieve — when another round of refinement would add less value than it costs.
That requires judgment.
We don't chase completion for its own sake.
We chase the point where the idea is clear, the experience is coherent, and the work is ready to exist in the world.
We design by making decisions, not by filling screens.