How the work is planned
The whole platform is written down before it is built: 87 items, each recording what it is for, what it depends on, and what it is waiting on from outside the team. Twelve of those items are waiting on somebody else, and they are named as such rather than started and stalled. Nothing is scheduled by guesswork and nothing is begun twice.
The governing document
One document sets how the platform is written, in a fixed order of priority: confidentiality first, then correctness and honesty about it, then simplicity, then delivery. Where a rule can be checked automatically it is, and where it cannot be the document says so rather than implying the rule is enforced.
Where the work starts
The security core and vessel identity come first. Everything else attaches to them, and both are considerably cheaper to settle now than to correct once a book is loaded.