About the studio
A studio for the second draft.
We are senior engineers, designers, and writers who believe software is too important to be improvised. We work in small groups, on a small number of projects, with a written record of everything that matters.
Write, Record & Play was founded on the conviction that most software fails for human reasons: unclear briefs, missing context, decisions made in meetings that no one wrote down. We organised the studio around the opposite defaults.
Our name describes how we work, in order. We write the system before we build it. We record the decisions that shape it. And we keep it playing long after the original team has moved on.
Principles
Three sentences we keep returning to.
- 01
Write before you build
Every system begins as a memo. The discipline of writing forces the decisions that drawings hide.
- 02
Record what you decide
Design documents, decision logs, and recorded walkthroughs outlive any single contributor.
- 03
Play the long game
We staff for systems that will be maintained for years, not announced at a launch event.
A short history
How we got here.
- Origins
Three engineers, one shared frustration with the cost of undocumented systems.
- Practice
A studio formed around writing-first engineering — memos before mocks, docs before deployments.
- Today
A distributed group of senior practitioners taking on a small number of long-form engagements at a time.
The team
Small on purpose.
The studio is intentionally small. We staff each engagement with senior practitioners who carry the work from discovery through handover. There is no escalation chain, because there is no chain.
Specialist collaborators — security, accessibility, infrastructure — join projects where the work calls for them, by name, not by allocation.