Measuring success
Feature counts, module lists, integration matrices — procurement measures everything except the thing the company is buying. One question matters: how much business value does the system create?
What gets measured today
Business software is bought through counting. The RFP with four hundred rows of features to check off. The comparison matrix scoring vendors per module. The demo evaluated screen by screen, as if screens were the deliverable. Every one of those numbers measures the vendor's output — how much software exists — and not one measures the buyer's outcome.
The method selects for the wrong winner with mechanical reliability. The system that checks the most boxes is the one built to check boxes: broadest, most generic, most padded with capabilities that exist to survive procurement. The system that would actually move the company's numbers loses on row count.
The only metric
How much business value does the system create? Hours returned to people who were doing synchronization work. Errors that stopped happening. Decisions made a week earlier because the number was already on screen. Customers kept because nothing fell between systems. That is the entire scoreboard.
The honest objection: feature lists are at least objective, and value is fuzzy. True — and it concedes the game. Objective-and-irrelevant loses to approximate-and-true every year you renew a license for a module nobody has opened. Fuzzy measurement of the right thing beats precise measurement of the wrong one.
Measure like an engineer
Taking measurement seriously is a culture, and cultures show themselves in public. Ours: state the method, publish the numbers, publish the runs that went wrong alongside the ones that went right — because a measurement you would only publish when it flatters you is marketing wearing a lab coat.
We hold our own architecture decisions to that standard, in the open, on our own systems.
The benchmark itselfValue is the spec
Start every system decision from the value question and the rest of this document follows from it: one connected system, adapted to the business and the individual, assembled from proven blocks, changed continuously. Each principle is what the answer looks like from a different angle.
Everything else is secondary. Not unimportant — secondary.