The most expensive thing a small team can do is build the wrong system well.
A short defence of restraint, and the discipline of saying no early so the rest of the work can be done seriously.
Read noteJournal
Field notes from the studio.
Brief, considered writing on building software, systems, and experiences that hold up after launch. Published when there’s something worth saying, not on a schedule.
Architecture as documentation: building systems future engineers can read.
Names, seams, and structure are the first place a future engineer should look. Notes on writing systems that explain themselves.
Read noteWhy luxury digital still feels cheap, and what fixes it.
Most premium brands lose the texture of the in-person experience the moment a customer opens the website. Six small reasons, and how to address them.
Read noteThe first version that can stand in front of users.
The difference between a prototype and a real first release — and why most early-stage products fail to make the jump.
Read noteWhen spreadsheets stop being a tool and start being a constraint.
The signal that an operating model has outgrown its tools — and why the next system should be designed around the workflow, not the workflow around the system.
Read noteCalm by default: working without theatre.
A short note on how the studio operates — and why deliberate calm is the most productive setting for serious work.
Read noteBegin
Have a question that should be a note?
If something here is useful, or something is missing, we’d like to hear about it.