Nothing gets briefed twice
The people who argued about the scope are the people who write the security rules and draw the icon. There is no document whose only job is to carry an intention between teams, and no meeting where the intention gets lost anyway.
No account layer
You talk to whoever is building it. When something is a bad idea you hear that in the reply, not three weeks later in a change request.
One head holds the whole system
The schema, the failure modes, and the reason a screen looks the way it does all fit in the same mind — which is why the twentieth screen still resembles the first, and why a change to the data model does not quietly break the artwork.
We kept the load-bearing half of a heavy process
The parts of a heavy release process that are genuinely protecting the product — deny-by-default rules, a deadline on every call, a regression suite that drives the real camera on-device — we kept. The parts that existed because an organisation was large, we did not.
The trade, stated plainly. This is one team building one thing properly. If what you need is a large parallel effort staffed next week, that is a different kind of company and we will say so in the first reply — rather than take the work and subcontract it.
