Design thinking

First. champions the thinking behind the building.

These aren't principles written for a pitch deck. They're baked into every interaction — the hints, the scoring, the order of operations, the copy.

01

Empathise before you execute

The fastest path to the wrong solution is skipping research. Even 20 minutes with a real user surfaces assumptions that invalidate weeks of work.

02

Requirements are a design artefact

A well-written brief isn't a constraint on creativity — it's the foundation that makes creativity defensible.

03

Define success before you define features

If you can't state a 10% improvement in plain numbers, you don't have a requirement. You have a preference.

04

The edge case is the real case

Error states and empty states are often the first thing new users see. Design them with the same rigour as the happy path.

05

Scope is a design decision

Every feature you add is a feature your user must understand. Subtraction is the hardest and most valuable design skill.

06

Output follows outcome

The interface is the last thing you design. First you define the outcome — what does success look like? — then the output follows.

Start with First →