There is a simple test for how an organisation really thinks about its technology, and it has nothing to do with the size of the IT budget. Watch what happens when a system fails at month-end.
In some organisations that failure becomes an IT ticket, which gets logged, prioritised against the backlog, and resolved when it is resolved. In others it is a board problem within the hour, because those organisations understand that the system is the business itself, wearing its work clothes.
Decoration and infrastructure
Technology as decoration is easy to recognise once you have the word for it. It is the transformation programme announced before the problem is defined, the dashboard nobody makes a decision from, and the platform chosen because of who else uses it rather than what it has to carry. Decoration is judged by how it looks in the annual report.
Infrastructure is judged by what happens when it stops. Payroll, reconciliation, order flow, the ledger. Nobody praises a bridge for standing, and nobody should need to praise a billing run for completing. The correct amount of attention infrastructure attracts in a good month is none.
What follows from taking this seriously
If a system is infrastructure, certain conclusions follow, and they are unglamorous ones.
- Boring reliability outranks interesting features, because a capability that works nine months in ten belongs on the risk register rather than in the brochure.
- Operations is a design input. Who runs this, with what skills, at three in the morning, is an architecture question that deserves an answer before anything is built.
- Failure deserves as much design attention as features. Month-end arrives on schedule, twelve times a year, and a system that cannot survive it was never finished.
- Accountability has to outlast the project, so whoever built the system should still be reachable, and still responsible, when it meets its hardest day.
Why we work this way
We choose to work with organisations that hold the board-problem view, and we build for them accordingly: specific advice, delivery we own, systems that keep working after we leave. That is a narrower promise than transformation, and it is one that can be kept.