Understand the situation
We learn what the business is trying to achieve, who the experience is for and what evidence already exists.
Working outputA shared brief, audience needs, content inventory and practical constraints.
How a project runs, from brief to handover.
Five stages, each ending in something you can review. The depth and pace of each stage follow the brief.
Direction, interface and code develop together.
A shared direction becomes an experience, an interface and a working system. Each layer is developed with the others in view.
Scroll to open the layers. Then choose an angle, or take control of the assembly below.
Opening the spatial study…
Find the organizing idea
We develop the identity and experience around a useful central idea. The direction is judged against the brief.
Working outputAn experience direction, information architecture and design principles.
Make the structure tangible
We build layouts, interactions and spatial studies that can be tried. Questions become easier to answer when the work is visible.
Working outputA working prototype with the main journeys, states and content relationships.
Build with the details intact
The design becomes a responsive implementation. Data, validation, motion, materials and readable alternatives are connected.
Working outputA reviewable website or product with working behavior.
Check, refine and hand over
We test the main tasks on relevant devices, inspect accessibility and performance, and document the parts that need maintaining.
Working outputA verified release candidate, deployment plan and practical handover.
Each review ends with a decision.
Reviews focus on the brief and the decisions in front of us. We agree what is in scope, what is needed from the business and what the next milestone should prove.
Begin with a briefWho does what during a project
What we bring
- A clear recommendation with the reasoning behind it.
- Reviewable work at agreed milestones.
- A record of decisions, open questions and dependencies.
- Early visibility when scope, timing or effort changes.
What we need from you
- Business context and access to the relevant material.
- A person who can bring feedback together and approve decisions.
- Accurate content and confirmation of usage rights.
- Timely review against the objective we agreed.
Questions about the process
How do we choose a direction?
We compare the work against the brief: the audience, the intended impression and the task it needs to support. Feedback is more useful when it describes what feels right or wrong and why.
What happens when the scope changes?
We describe the change, its effect on time and cost, and the options for handling it. The revised scope is agreed before the additional work starts.
How does launch work?
We review a release candidate, check the main journeys and agree content, domain access and the launch window. Handover includes the practical information needed to operate the work.
What happens after launch?
We agree who owns maintenance, content and performance reviews. Where ongoing work is part of the engagement, the next cycle starts from observed behavior and business priorities.