Decision guide · IT org design

Org design is a decision, not an inherited org chart.

Structure, reporting line, and which functions stay internal are choices-most organizations never make them on purpose. They just grow around whoever was hired first.

Frame the structure question

The first hire's job description becomes the whole department.

Most IT structure is inherited rather than designed. The first hire covers whatever was urgent that year. The next hire fills the next gap. Ten years later, the shape of the function reflects a sequence of individual hiring decisions-not a deliberate view of which functions the organization actually needs, where they should sit, and who they should report to.

That inherited shape is not automatically wrong. It becomes a problem when it silently stops fitting: when one generalist is quietly covering security, infrastructure, and applications at once, or when IT reports somewhere that no longer matches the decisions leadership actually needs it to make.

Not the same question

This is a structure decision: which functions and roles exist, and where they sit. It is different from who decides what once the structure exists-see the IT operating model-and different from which forum meets when-see governance and cadence.

Function by function

Every function outgrows its first shape eventually.

Function	Common early shape	Signal it has outgrown that shape	Common blind spot
Helpdesk and end-user support	A generalist or the newest hire covers it alongside other duties.	Response time and ticket volume outpace one person's attention.	Treating a full inbox as a hiring problem instead of a structure decision.
Infrastructure and security	Bundled into the same generalist role or a single MSP relationship.	Compliance, incident, or vendor obligations need a named accountable owner.	Assuming "someone handles it" without anyone able to name who.
Applications and data	Owned informally by whoever originally set the system up.	Multiple departments depend on decisions no one is authorized to make.	A workaround or a single spreadsheet quietly becomes permanent infrastructure.
Strategy and vendor governance	Absent, or handled ad hoc by whichever leader is loudest that quarter.	Renewals, roadmap, and budget decisions repeat without a consistent view.	Mistaking a vendor's account manager for independent technology judgement.

Structure lenses

Six questions before the next hire or contract.

CentralizationShould this function live in one place, or embedded per business unit or location?
Reporting lineDoes IT report to finance, operations, or the chief executive-and what mandate does each imply?
Internal, contracted, or fractionalPer function: does this need a permanent hire, a vendor, or fractional cover?
Span and team shapeHow many people or relationships can one role realistically coordinate?
Growth-stage fitThe shape that worked at twenty people rarely still fits at eighty.
Redesign triggerWhat evidence-not discomfort alone-says the current shape no longer works?

Working process

Design before you hire, not after.

Inventory functions and owners
List every function actually in play today, including the ones covered by "whoever has time."
Test centralization per function
Some functions genuinely benefit from being embedded; others do not. Decide function by function.
Decide the reporting line
Match the reporting line to the mandate IT actually needs to carry out its decisions.
Sequence the change
Restructuring and re-platforming at the same time makes both harder to evaluate honestly.

Helpdesk sourcing - internal, MSP, or hybrid - is one function this structure decision has to place

Hypothetical pattern

One capable generalist becomes the whole IT department

A ten-person startup's first technical hire is capable and well liked. Five years and eighty employees later, that same person still personally covers helpdesk, infrastructure, security, and vendor relationships-not because it was ever decided that way, but because no one revisited the shape as the organization grew around it.

See how that concentration gets priced

Next step

Bring the structure nobody has redesigned since the first hire.

A focused brief can turn an inherited shape into a deliberate one, function by function.

Build the structure brief

The first hire's job description becomes the whole department.

Inventory functions and owners

Test centralization per function

Decide the reporting line

Sequence the change

One capable generalist becomes the whole IT department

Bring the structure nobody has redesigned since the first hire.

Get IT decisions made, and made to stick.

Related services