01
Clarity over complexity
If we cannot explain the design in a sentence, it is not ready. Complexity is allowed when the domain demands it — never as a display of cleverness.
Principles we can be held to.
Values are useless as posters. These are the rules we use when a decision is uncomfortable.
02
Build for the long term
Someone else will own this. We write, name, and document as if they are already on the team. Short-term shipping that strands the next year is a failure.
03
Design before decoration
Type, flow, and states before colour. Motion that explains, not entertains. A beautiful screen that cannot be built is unfinished work.
04
Engineering with discipline
Tests on the expensive paths. Observability as a feature. Reviews that can say no. Speed that comes from a system, not from skipping the floor.
05
Communicate directly
Bad news early. Estimates with ranges. No account-layer translation. If we are wrong, we say so and propose the next honest step.
06
Own the outcome
A ticket closed is not a product shipped. We stay with launch, the first failures, and the handover. Credit is shared; responsibility is named.
Start a project
Tell us what you are building.
A short note is enough. We will come back with questions, not a pitch deck.