INSIGHT, IT GOVERNANCE
Why most technology initiatives do not fail because of technology
In more than twenty years running IT I saw the same pattern: the projects that fall over do not fall over because of the tool. They fall over because of decisions taken without business judgment, and taken too late.
Technology is rarely the bottleneck. The judgment to decide is.
The symptom against the cause
When an initiative drifts, the conversation turns technical. But the cause usually sits earlier: a badly defined business objective, a prioritisation with no owner, a return nobody measured. It is easy to blame the ERP integration or the cloud migration, and the real failure happened months before, at the board table.
Most executive committees delegate the technology decision to their IT leaders, assuming it is a purely technical problem. That disconnect is fatal. A digital transformation initiative is, at its core, a business transformation initiative that uses technology as an enabler. If the business does not own the problem, technology will not solve it.
What a CIO would do differently
Start with the decision, not the platform: what outcome is being bought, how it will be measured, and who answers for it. The technology comes afterwards, and there is almost always more than one that works. A modern CIO orchestrates value, not servers. They demand a solid business case before evaluating vendors, and they make sure every technical milestone is tied to an operating or financial indicator.
Real IT governance is not bureaucracy to prevent mistakes. It is a structure for taking informed decisions in time: putting the CEO, the CFO and the CIO at the same table to define risk appetite and investment strategy.
Is this decision on your desk?
A first conversation costs nothing and usually clarifies whether the problem is the one you thought it was.
Schedule a strategic conversation
