Judging
How work runs, and how you can judge it
We do not publish awards or client counts. Instead, here are the stages we follow and the criteria you can hold us to.
- Clarify
Agree the problem, who it is for and what is out of scope. Written down and shared.
- Shape
Rough structure or wireframes first. Cheap to change, so we change them here.
- Build in slices
Small working pieces you can try, rather than one reveal at the end.
- Check
Test against the criteria below, on devices and browsers agreed with you.
- Release & hand over
Go live, then hand over access, notes and source you own.
Quality criteria
Accessibility
Keyboard reachable, visible focus, labelled form fields, sensible contrast, respect for reduced-motion settings.
Clarity
Every screen should have one obvious main action and wording a new user understands.
Ownership
You hold the accounts, domains and repositories. Nothing locked to us.
Honesty
Problems raised as soon as we see them, with options, not after the deadline.
Privacy
Collect only the data the product needs; tell users plainly what happens to it.
Maintainability
Readable code and notes so the next person is not starting blind.
Self-check: is a supplier meeting these?
Tick what you have actually seen from a supplier (including us).
0 of 5 seen.