Principles
Rules for travelling in uncertain country.
These principles apply to every engagement. If one must bend, we say so first and write down why.
- Say what is known and what is not
- Findings are labelled as tested, inferred or assumed. Estimates are ranges with their assumptions visible.
- Test the dangerous assumption first
- We sequence work by risk, not by what is most enjoyable to build.
- You own the summit
- Repositories, design files, store accounts, domains and hosting are in your name from day one.
- Increments you can hold
- A working build every fortnight during active development, with a short written note.
- Accessibility is the floor
- WCAG 2.2 AA, tested with keyboards and screen readers, and an honest accessibility statement.
- Security basics, always
- Individual accounts with two-factor authentication, secrets outside code, dependencies kept current, minimal personal data.
- No manipulation
- No dark patterns, false urgency, hidden opt-outs or invented social proof.
- Know when to turn back
- If the evidence says an idea should not be built, we will tell you, even when it ends our engagement.
Hold us to them.
Ask about any of these in your first conversation. We would rather be questioned early than trusted blindly.