Make the record true, then let it act.
A business decision is only as good as the record it was taken from. Our mission is to give an organisation one record it can trust, and then let intelligence act on that record inside limits a person set — in that order, because the reverse produces confident answers drawn from a fractured source.
One mission·One vision·Four things we will not do
Mission
Give every operating business one record it can trust, and intelligence that can act on it without anyone losing control of what happens next.
Two halves, and the order matters. Without the first, the second is a machine for producing plausible answers from bad data. Without the second, you have a filing cabinet with a search box.
Vision
Software that runs the operation, rather than software the operation has to be run around.
The measure is not how much of the day is spent in the system. It is how much of the day the system removed — the reconciliation nobody has to do, the approval that did not need chasing, the question that already had an answer attached to it.
What follows from that, in practice.
Each of these is a design rule with something on the site that depends on it. They are not aspirations; if we broke one, a page would have to change.
Four things we will not do.
A mission statement that costs nothing is decoration. These each cost us something specific, which is how you can tell they are real.
How we would know we were wrong.
The useful version of a mission is one with a failure condition attached. These are ours.
- The record is not trusted
- Somebody still keeps a private spreadsheet to check the system against. If that spreadsheet survives go-live, we did not finish.
- The agent is switched off
- Not because it was wrong, but because nobody could tell what it would do next. That is a scoping failure, and it is ours.
- The programme slipped quietly
- A wave moved and the customer found out afterwards. Waves move; finding out afterwards is the defect.
- The export was never tested
- An exit right nobody has exercised is a claim, not a right. It should be run at least once during the programme.
The rest of the company, in the same words.
Next step
The commitments, with the implementation attached.
Security, deployment, and pricing are where these stop being statements.