- Challenge
- Technology delivered without an operable organisational capability
- Assumption
- Installation and project completion represented value
- Decision
- Test ownership, supportability and realised outcomes
- Consequence
- Dependency and operating friction survive the deployment
A purchase order does not create capability. Neither does installation. Capability appears when the organisation can operate, support, explain and improve the technology without depending on the original sales story.
Many failing projects are not obviously broken. The tool exists. The dashboard loads. The vendor can point to a deployment milestone. But the environment has not changed in the way the business expected. The same workarounds remain. The same escalation paths exist. The same uncertainty appears when something fails.
This distinction matters because technology can make an organisation look modern while leaving the actual operating model untouched. The organisation now has more components, more contracts and more interfaces, but not necessarily more control.
For a decision-maker, the test begins after go-live: can the internal team operate the platform, can the promised benefit be measured, and can the organisation change direction without returning to the original supplier for every material decision?
Praetorian starts with the gap between technology present and capability realised. That gap is where waste, frustration and stalled value usually live.
Engineering response
- Deployment is not adoption.
- Ownership must be designed, not assumed.
- Value is proven by changed behaviour, not installed components.
Read the engineering principles behind this work →
Confidentiality: Engineering Notes are based on real engagements. Client identities, timelines and identifying details may be changed to protect confidentiality. The engineering decisions and lessons remain representative of the work undertaken.