Written when we learn something, not on a content schedule. Mostly architecture, interface decisions and the parts of delivery nobody demos.
Most rewrites trace back to three choices made in the first fortnight. Here is how we pressure-test them before writing code.
Loading, empty, error and disabled are most of the hours a user spends with your product. We design them first.
How we build an evaluation harness in week one so quality is a number rather than an opinion.
The seventh stage of our process is the one most engagements never reach, and the reason products stop improving.
Dual-write, one workflow at a time, and a rollback that stays available until the last site is across.
Tell us what you are building. We will tell you what we would do first.
