Department-led, IT-led or management-led? Split it three ways
Each model fails in its own way. Departments build silos, IT builds slowly and safely, management gets bogged down. What works, in our experience, is a split – management sets the rules and the money, the departments choose the jobs, and IT owns what the tools may touch.

What each model gets wrong
We've seen all three tried in companies between 20 and a few hundred people. Each one is good at something and fails somewhere predictable.
| Model | What it does well | How it fails |
|---|---|---|
| Each department leads | Picks jobs that matter to the people doing the work. Fast. | 5 versions of the same tool, 5 sets of rules, data in places nobody agreed to. Nothing gets shared. |
| Centralised through IT | Safe connections, one platform, proper access control. | Slow, because every request joins a queue. Builds what's tidy rather than what's valuable. The business stops asking. |
| Kept with management | Money and priority are clear. | Management has no time, so decisions wait weeks. Or management picks the jobs and they're the wrong ones, because nobody at the top does the work. |
The pattern is that each model is strong on one of three questions and weak on the other two. So split the questions, not the leadership.
Who owns which question
What are we allowed to do? That's management's. It means the rules: what data a tool may see, who checks output before it reaches a customer, who may build something that runs on its own, and how much money this quarter. Written on a page, revised quarterly. This is the part management shouldn't delegate and, in our experience, the part it most often does.
What's worth doing? That's each department's. The sales manager knows the quoting process wastes 4 hours a week, and nobody in IT does. The department picks the jobs, measures them before and after, and is responsible for whether its people use the result. A tool nobody uses is the department's failure, not the builder's.
What may it touch? That's IT's, or if you've no IT department, whoever administers your systems together with your outside provider. Connections to the CRM, the accounts package, the file store and the mailboxes go through one place, with one way of granting and removing access. This is where silos get prevented, because every tool connects the same way.
The three meet for an hour a month. Departments bring the jobs and the numbers, IT brings what's connected and what's been asked for, and management decides what the rules allow and what the money covers.
The small-company version
With 30 people you won't have three groups. You'll have an owner, a department head or two, and whoever runs the systems. The split still holds, it's just three hats on two or three heads. What matters is that the hats are named, so "can the assistant read the shared drive?" is a question for the systems hat, "is the quoting agent worth keeping?" is a question for the sales hat, and nobody's waiting on the owner for either.
When to centralise more than this
Pull more into the middle when the work touches regulated data, when a tool talks to customers in your name, or when more than one department wants the same thing. Those are the cases where 5 versions become dangerous rather than just wasteful. Keeping agents on one platform covers the practical side.