Journeys and prototype
We establish the user journey, information hierarchy and key screens before working on decorative details.
Clear from the first
interaction.
We design interfaces for websites and digital products. We bring user journeys, content and visual language into a system that is easy to use.
When it helpsDoes this sound
Does this sound
like your task?
You need a new product design, improvements to an existing interface or a coherent system to replace disconnected screens.
Scope of work
What’s included.
Visual direction
We choose typography, colour, graphics and rhythm. The brand’s character supports the content.
System and handover
We work through components, states and responsive behaviour. We document interactions so development can start from clear decisions.
Beyond the process.
A clear outcome.
Agreed designs and components with descriptions of the main states and behaviour. The number of screens and handover format fit your team and task.
Can we commission design only?
Yes. We can handle design separately and prepare material for your development team. We discuss constraints, required states and the working arrangement in advance.
How do you estimate cost and timing?
We first discuss the task, source material and constraints. Then we agree on scope, stages, an estimate and the approval process. If the scope changes, we discuss the effect on budget and schedule before proceeding.
Can you update an interface while keeping our brand identity?
Yes. First, we establish which brand elements should stay and what makes the product difficult to use. Structure and components can change without replacing the whole visual identity.
How does a prototype differ from a finished design?
A prototype helps test the screens, structure and sequence of actions. A finished design specifies typography, colour, graphics and component states. We agree the depth of each stage around the task.
Will mobile screens be included?
Responsive behaviour is part of the design process. We agree on devices and key journeys, then define how navigation, components and content placement change across screen sizes.
What will the development team receive?
An agreed set of designs, components and notes on interface behaviour. We clarify loading, error and empty states, along with other important journeys. The handover format is agreed with your team.
Does a small product need a design system?
It does not always need a large, separate system. A library of recurring components and core rules is often enough. We choose a scope that supports the product’s growth without adding unnecessary work.