Leadership
We have notpublished this yet.
The team will be introduced as it comes together, and not before. In the meantime, here is the thing most people are actually asking when they open a leadership page: how decisions get made, and who is accountable for them.
How decisions work
- Product decisions sit with product teams
- Each product owns its own architecture, roadmap and technical choices. Nobody at the organisation level approves a release.
- Shared foundations are decided once, in the open
- Identity and the design foundation are the two things everything depends on, so changes to either are argued at the organisation level rather than per product. That is the trade for not rebuilding them eight times.
- Standards are written down, not remembered
- Engineering standards, the security baseline and the domain architecture exist as documents that products are held to, and a register is kept of where those documents and the code disagree.
- Claims are separated from evidence
- A roadmap entry may not be presented as a shipped capability — including on this website, where the rule is enforced by the code that renders the pages rather than left to whoever writes the copy.
If you would want to lead work here, say so.
There is no open process. There are conversations. Tell us what you have shipped that you are proud of and which part of the portfolio you would want to work inside.