People & Organization
The humans behind the systems.
Most mid-sized IT teams were built for the company as it was, not as it is. That gap shows up as key-person risk, as capable people stretched past their experience, and as a sourcing model that is mostly an accident of history. None of it is a performance problem; it is a design problem.
The Friday resignation question is not hypothetical. If one departure would stop the business, that is an operational risk sitting outside every register your board reviews.
What good looks like at your size
We score against this benchmark, meaning what a well-run company of 50 to 500 employees should reasonably have in place, rather than against theoretical perfection.
The team is sized for the company you are now
Roles and capabilities match current scale and the next two years of the business plan, rather than the shape the team grew into years ago.
No single point of human failure
Critical processes are documented and at least two people can execute them. Passwords, vendor relationships, and institutional history are not held in one head.
The sourcing split is deliberate
What stays in-house and what goes to providers was decided on purpose and is revisited, rather than settled by whoever handled an emergency once.
People have somewhere to go
Development paths exist, retention risk is known, and the team is not held together entirely by loyalty to one manager.
Technology has a seat at the table
Someone with the standing to shape decisions represents technology in business planning, before commitments are made rather than after.
What we typically find
Patterns common enough to name. None of them indicate a bad team. They are what happens when a company grows faster than the decisions that shaped its technology.
One genuinely irreplaceable person
They hold the credentials, the vendor relationships, and the history of every decision. Everyone knows it. The risk has been tolerated because addressing it feels like a vote of no confidence.
A capable manager stretched past their experience
Someone promoted for being excellent at the operational job, now being asked for executive judgment on eight-figure decisions, without support or a peer to test thinking against.
Outsourcing decided by accident
The provider owns a function because they picked it up during a crisis years ago, and it has never been reviewed against what it costs or who should own it now.
No documentation because there is no slack
The team has been at capacity for years. Documentation is always the thing that will happen after the current urgent work, which never ends.
Attrition into a premium rehire
Good people leave for progression that does not exist internally, and the replacement costs more, knows less, and takes a year to reach the same effectiveness.
How we assess it
Where a document does not exist, that is itself a finding, and we say so plainly rather than treating the gap as an obstacle.
- Internal IT capability against what the company actually needs
- Key-person risk: what only one individual knows how to do
- Sourcing model: what belongs in-house versus with providers
- Skills and development paths for the team you already have
- Organization chart, roles, and tenure for everyone who touches technology
- A skills inventory measured against current needs and the business plan
- Review of documentation, runbooks, and credential management practices
- Confidential working sessions with team members and with their internal customers
- Turnover history, current open roles, and compensation benchmarks where relevant
Questions the readout answers
If our IT lead resigned Friday, what breaks Monday?
Are we staffed for the company we were, or the one we are becoming?
What this domain contributes to your report
- A key-person risk map with specific, practical mitigation steps
- Capability gaps ranked against what the business plan requires
- A recommended sourcing model: what belongs in-house, what belongs with providers, and why
- Development and retention actions that can start immediately
How this domain is scored
Every domain is scored 0–10 on the same scale, so the scorecard shows you where to look first rather than a single undifferentiated grade.
Something here can hurt the business now. These findings lead the roadmap.
Functioning, but behind where a company of your size and stage should be.
In good shape. Worth maintaining rather than investing further right now.
A genuine strength, and often something to build on elsewhere.