Skip to content
03 / Practice

Design

Ideas turned into distinctive digital experiences, through a balance of clarity, usability and visual identity.

An arrangement of paper grids, material swatches and geometric design tools.
01

User interface design

The surface, decided properly: type scale, density, colour and every state a component can be in — hover, focus, error, empty, loading.

  • Interface systems
  • State design
  • Editorial layout
Figma
02

User experience design

Flows, structure and the decisions that make software feel finished. Designed against real content, because real content is what breaks a layout.

  • Flow design
  • Information architecture
  • Usability review
03

Product design

Design that starts at what the product is for. Scope, sequence and interface decided together rather than handed between disciplines.

  • Concept design
  • Feature definition
  • Design critique
04

Design systems

A component library, tokens and the rules that keep them alive in production — so the tenth screen costs less to design than the first.

  • Design tokens
  • Component libraries
  • Documentation & guidelines
Figma
05

Prototyping & interaction design

Motion and interaction prototyped early, so behaviour is agreed while it is still cheap to change and implemented to a budget the device can hold.

  • Interactive prototypes
  • Motion specification
  • Browser review
06

Graphic design & brand visuals

Identity work and digital assets for software companies: a mark, a type system and the rules that keep both consistent inside the product.

  • Brand visuals
  • Digital assets
  • Guidelines
How it runs

The same sevenStages.

The same sequence runs whether the engagement is four weeks or four quarters. Only the depth of each stage changes.

01

Discover

Business goals, users, workflows, constraints and the existing system. We write down what is true before proposing anything.

02

Strategize

Scope, sequence and the technical direction. Architecture and stack are decided here, after the problem — never before it.

03

Design

Flows and interfaces designed against real content and reviewed in the browser, with data model and interface moving together.

04

Build

Short cycles and working software each time. Frontend, backend, data and infrastructure are built as one system, not four.

05

Test

Automated coverage where it pays, security and performance checks, and structured sessions with the people who will use it.

06

Launch

Deployment, migration and the handover of a system your own team can operate, with monitoring in place before release.

07

Grow

Measurement, iteration, new capabilities and scaling. Most of a product’s real life happens here.

Start with theProblem, not thedeliverable.

Describe what is in the way. We will say which practice it belongs to.