IT organisation and roles
By Redaktion techport.ai, IT-Beratung · Last updated on
In many mid-sized companies IT consists of a few people who do everything: user support, servers, network, projects, purchasing, data protection questions and, on the side, explaining why the printer will not print. That works as long as nothing bigger happens. It stops working when the company grows, when someone leaves, or when a project is meant to run alongside daily business.
Organisation here does not mean hierarchy. It means that tasks are named, that every important task has a deputy, and that it is clear who decides on which question. That can be achieved with three people.
How you notice it
- When one particular person is on holiday, decisions and incidents wait.
- Departments do not know who to approach with which request.
- Projects stall because the same people have to keep operations running.
- Decisions about systems are made wherever someone has time, not where the responsibility sits.
Why this happens
IT teams in the mid-market grow along people, not along tasks. Whoever was there first does what came first and keeps it. New tasks land with whoever touched them first. Over the years a pattern emerges that nobody designed, that works in the heads of those involved and is written down nowhere. It only becomes visible when one of those people is unavailable or when external requirements demand a named owner.
How we go about it
- Record the tasks. We list which tasks actually occur, from user support through permissions and backups to contract renewals and project work, and who does them today. This regularly reveals tasks that nobody owns.
- Cut the roles. We bundle tasks into a small number of roles that fit the size of the company and name an owner and a deputy for each. That includes the role of system owner in the departments, which is often forgotten in IT organisation.
- Define decision paths. We clarify which decisions are operational, which need alignment and which are reserved for management, using value thresholds and examples rather than abstract rules.
- Secure the knowledge. We document the tasks so a deputy can take them over and set up a recurring date on which the state is reviewed. Without that last step the order falls apart within a year.
What you gain
- A company in which holidays and illness are not an exceptional situation.
- Departments that know where to turn and therefore rely less on word of mouth.
- A basis for deciding which tasks you buy in and which stay in house.
From our projects
When recording tasks, two groups almost always appear that were previously invisible. The first are activities one person has done on the side for years without them appearing in any job description, frequently permission management and licence administration. The second are tasks that formally sit with the provider but are actually done in house because it is quicker. Neither is a problem until someone is unavailable or an auditor asks who is responsible. We document both groups first because they carry the greatest risk and the smallest change effort.
Häufige Fragen
At what size does a company need its own IT leadership?
It is less the number of employees that decides than the number of systems and the dependence on operations. Rule of thumb: as soon as more than two people work in IT, or more than one central system carries revenue, you need a named lead with time for steering. That role can initially be part time or filled externally.
What is a system owner and why do we need one?
That is the person in the department responsible for content, rules and further development of a system, while IT is responsible for operations and technology. Without this role IT decides on business questions it cannot judge, and every change becomes an alignment exercise.
Let us talk about IT organisation and roles
In a thirty minute first call we work out where your biggest lever sits and whether we are the right people for it.
Further reading
Back to the field IT Strategy and Steering