Craft: standards and outcomes
Craft
What we mean by doing it properly, written down so you can hold us to it.

In design
- Accessible by default: keyboard use, readable contrast, sensible focus and plain language.
- Tested with real users before it is built, not after.
In engineering
- Maintainable, documented code in your repository.
- Automated tests for core behaviour; manual test notes for the rest.
- No secrets in code; dependencies kept current.
In publishing
- Release notes for every release, written for users.
- Help content reviewed whenever the feature it describes changes.
In training
- Materials built from real tasks and screens.
- Feedback gathered after each session and acted upon.
Outcomes we work towards
People complete their first important task without asking for help. Support questions fall rather than rise after a release. Your team can maintain and extend what we leave behind.
We do not publish invented metrics or testimonials; we will agree how to measure these outcomes with you.