03 — How we work
How we work
- Motive finds the reason.
- Motive shapes the system.
- Motive puts it in motion.
- Motive measures what moved.
The moving sentence on the home page is the short version. This is what each stage actually decides, what you will see while it happens, and where the boundary between evidence and judgement sits.
The same structure governs every record this studio publishes: a reason, a move, a result, and the evidence behind them. The process is simply that structure, run forwards.
The four stages
Jump to any one.
- 01Find the motiveThe uncomfortable question comes first: what has to change for this to have been worth doing? Every record on this site opens with that answer, under the heading Reason.
- 02Shape the systemStructure, hierarchy, language and interface — decided before anything is decorated. Most of the value is created here, and it looks the least impressive.
- 03Put it in motionBuild and choreography together. Motion is specified alongside the component, never bolted on afterwards, and every transition has to justify what it teaches.
- 04Measure what movedWhat came out of it, stated in the record: the result, the state of the work, and no figure the project itself cannot support.
01
Find the motive
The uncomfortable question comes first: what has to change for this to have been worth doing?
- What is decided
- The reason the project exists, stated in plain language before anything is designed — along with the audience it must work for and the constraints nobody wants to say out loud.
- What you will see
- A short written brief you can disagree with: the reason, the move we propose, and what would count as a result. Every published record on this site opens with exactly that answer, under the heading Reason.
- The evidence boundary
- The reason is agreed with you, not invented for you. Where a checkable number exists it is written down; where none does, the record will say so rather than promise one.
02
Shape the system
Structure, hierarchy, language and interface — decided before anything is decorated.
- What is decided
- What the pages are, what each must say first, and how a visitor moves between them. Most of the value is created here, and it looks the least impressive.
- What you will see
- The structure and the working copy before any styling: real sentences in real order, so the argument can be judged before it is dressed.
- The evidence boundary
- Decisions are recorded with their reasons, and what was rejected stays in the record. The archive shows the working, not just the answer.
03
Put it in motion
Build and choreography together — motion is specified alongside the component, never bolted on afterwards.
- What is decided
- How the interface behaves: every transition justified by what it teaches, one coordinated motion runtime rather than scattered effects, and reduced motion designed as its own complete state.
- What you will see
- The real pages as they are built, on a staging address, rather than mock-ups and a reveal at the end.
- The evidence boundary
- Motion never carries meaning on its own. Anything an animation says, the still page says too — that is a design rule this site itself is built under, and its checks are public in the repository.
04
Measure what moved
What came out of it, stated in the record.
- What is decided
- What is reported: the result, the state of the work, and no figure the project itself cannot support.
- What you will see
- A record you can check — the same reason from stage one, the move that was made, the result, and where the evidence lives. Shortfalls stay in it.
- The evidence boundary
- A project that cannot support a figure does not get one. Its record prints the state of the work instead — a designed answer, not a blank.
The evidence boundary is the part most studios leave out, so it is stated at every stage rather than summarised once.
Every stage above is visible in the published records: reason, move, result, evidence.