Almost every large technology initiative first lands on a desk in IT or in a business unit. Usually it stays there. That is the first mistake — and rarely the cheapest.
The reflex is understandable. A new system, a new tool, a new platform sounds like technology, so like IT. Yet the real decision is almost never technical. It reads: which capability do we want to build as a company, and are we willing to move the organization for it? That is a business decision. Whoever delegates it downward has already misjudged it.
Why middle management prefers to keep it in-house
In the companies where I have seen this, the cause was rarely ill will, but isolation. The more the board is involved, the more questions come — uncomfortable ones too, sometimes ones you cannot answer on the spot. That is read as an attack, where it would be a hardening of your own solution. And where communication between the board and the unit heads freezes, global programs stay departmental solutions at their core. The backing you urgently need from the top does not arrive, because the layers below shield off every honest look inside.
The number where it becomes visible
There is an uncomfortable regularity: without secured backing from the top, sooner or later every project metric turns red. Timelines slip, budgets run out of hand, the scope is missed — and in the end everyone blames everyone. The reason is not a technical one. Neither IT nor the business unit has the organizational force to carry a group-wide change against day-to-day operations. For large change, top-down is simply without alternative in a corporation. Accountable, nonetheless, remains only one person: the program lead.
What boards systematically underestimate is their own role in organizational change. Priorities form at the top — markets, cost, partnerships. Whoever wants to contribute from an indirect function has to step into the wind as well. I have watched it twice at the same point: both programs had their best phase only once the board visibly stood behind them.
For you that means: on your next large technology decision, examine the line-up first, then the system. Is the board visibly behind it? If not, you have not delegated an IT task, but a business risk.
