An IT department org chart has a problem no other department's has: half its work is requests from everybody else, so the chart has to show both what the team is organised into and who the rest of the company should ask. Drawn as one, it looks like a hierarchy and answers neither question well. This page draws it at three sizes with the service boundary marked, so the chart works for the team and for the people queuing at it. The span arithmetic is unchanged: about seven to a manager, and a second layer once a group passes that.
Three people: no structure, a rota and a queue
One IT manager and two engineers, with the useful part of the chart being who covers the service desk this week rather than who reports to whom. At this size the chart's job is to publish the queue's owner. A three-box hierarchy tells the company nothing they did not know; a line saying support requests go here answers the question that generates most of the department's contact.
Eight people: support, infrastructure and applications
Three groups appear in the same order almost everywhere: service desk, infrastructure, and applications or business systems. At eight people that is one manager and three small groups, a span well inside seven. Security is usually a hat somebody wears rather than a seat, and the chart should say whose hat it is, because an unowned security responsibility is the most common gap on an IT chart.
Eighteen people: leads, security and a change boundary
Each group gets a lead, security becomes a seat, and somebody owns change management. Eighteen people across three leads and a head is a span of about five, which is where most IT departments sit. The dotted lines start here too: the applications lead into finance for the ERP, security into legal for compliance. Each is a standing relationship worth drawing rather than leaving to habit.
Questions people ask about it department org chart
Should security report into IT?
In a company under a few hundred people, usually yes, with a dotted line to whoever owns risk. Above that it separates, and the chart should show the change when it happens.
Where does the service desk sit?
Its own group, whatever the size. Folding it into infrastructure is how ticket response quietly becomes the lowest priority in the department.
Do we put on-call on the chart?
Not the rota, but the owner of it. The rota changes weekly; the accountability does not.