Any time we talk with a founder, COO, or functional leader at a growing company about their IT Drag Score, a familiar pattern shows up: they’re confused about why simple work takes more effort than it should.
They describe strong teams, reasonable tools, and clear goals. Yet projects stall in handoffs.
That gap has a name: IT drag.
The Isidore Group defines IT drag as the friction your systems create in the normal flow of work.
For example, you see it when a new hire joins and spends their first days asking for access instead of contributing to outcomes. Or you see it when a manager keeps a shadow spreadsheet because the “official” system is too slow, too messy, or too hard to trust.
Individually, each of these moments is easy to ignore. Someone helps out. Someone finds a workaround. The task gets done.
But collectively, they define how your company operates.
IT Drag is the steady accumulation of small delays and extra steps that sit between your people and the work they’re trying to do.
If you’re responsible for revenue, operations, or a key function, this blog is for you. Keep reading to take your IT Drag Score in 30 seconds and make that friction visible.
TL;DR
The Isidore Group defines IT drag as the friction between how your business needs to work and how your technology actually supports it. It shows up through access delays, unclear ownership, tool confusion, scattered files, shadow spreadsheets, and repeated workarounds.
- Score 0–1 means your IT model is mostly staying out of the way. Keep a light monthly review across access, renewals, tool usage, support requests, and admin permissions so small gaps do not become normal.
- Score 2–3 means early operational drag is forming. Look for repeat patterns like slow access requests, tools people avoid, unclear processes, or workflows that depend on one person knowing the workaround.
- Score 4–5 means IT is taking too much leadership time. Review your software stack, system ownership, access process, documentation, support model, renewals, and security responsibilities before the friction becomes a larger operating issue.
- Score 6 means the business has likely outgrown its current IT structure. This calls for a full review of tools, access, ownership, security, documentation, support paths, and future growth needs.
If your IT Drag Score is higher than expected, The Isidore Group can help you find where IT drag is slowing the business down and build a clearer, more scalable IT structure.
Take the IT Drag Score
Think about the last 30 days.
Give your business 1 point for each statement that applies:
- A new hire waited more than 24 hours for the right system access.
- A manager asked for a new tool because the current process felt too slow.
- A software renewal needed approval, but no one could clearly explain its value.
- A client-facing task slowed down because files or updates lived in too many places.
- A key process depended on one person knowing the workaround.
- A security or access question reached leadership because ownership was unclear.
Now add up your score.
What Your Score Means and What to Do Next
0–1: Your IT model is staying out of the way
This is a strong position.
Your systems are not creating obvious friction in the day-to-day flow of work. People can usually access what they need, understand which tools to use, and get support without pulling leadership into every small decision.
However, that does not mean everything is perfect. It means the business is not losing meaningful time to avoidable IT issues.
At this stage, IT is doing what it should: supporting the team without becoming the center of attention.
What to do when your score is 0–1
The biggest risk at this stage is complacency. When systems feel fine, no one checks them until something starts to slow down. That is how small gaps become normal.
A practical move is to run a light monthly review across:
- New hire access setup
- Software renewals coming in the next 60–90 days
- Tools with low usage
- Repeated support requests
- Admin access and permissions
- Any process quietly owned by one person
It can be a simple 30-minute review with the right people.
The point is to keep visibility before friction builds. Growing companies often create IT drag slowly through small decisions: one extra tool, one unclear owner, one undocumented workaround. Keeping those things visible protects the momentum you already have.
2–3: Your team is starting to feel IT drag
This is the stage where IT drag becomes noticeable, but not painful enough to force immediate action.
The important thing to understand here is that IT drag at this level rarely looks like an IT crisis. It usually looks like lost time, unclear ownership, duplicated work, and quiet frustration.
What to do when your score is 2–3
Find the repeat issues first.
Do not start by buying another tool. Start by asking where the business is losing time.
Ask your team:
- Where do system-related requests slow down most often?
- Which tool do people avoid using?
- Which process feels unclear or inconsistent?
- Where are people using spreadsheets because the main system is not trusted?
- Which task depends too much on one person knowing the workaround?
- What access request takes longer than it should?
Then group the answers into patterns.
Usually, a score of 2–3 points to one of four issues:
- Access is not clear enough
- Tool ownership is not defined
- Processes are not documented
- Teams are using workarounds because systems feel slow or unreliable
Once you know which pattern is showing up, fix that first.
For example, if access is the issue, create a clear starter, mover, and leaver process. If tool confusion is the issue, assign one owner for each core system. If people are keeping shadow spreadsheets, review why the official system is not trusted.
At this stage, the fixes are usually manageable. The value comes from acting before those workarounds become part of the company’s operating rhythm.
4–5: IT is taking too much leadership time
This is where IT drag starts becoming expensive.
The problem is no longer just that tools are slow or processes are unclear. The bigger issue is that leadership is being pulled into decisions and problems that should already have a clear path.
That is poor use of leadership attention.
Every hour spent on avoidable IT friction is time not spent on strategy, clients, revenue, people, or growth. This is usually the point where the business has outgrown informal ways of working.
What to do when your score is 4–5
Run a structured IT review.
At this level, quick fixes will not be enough because the issue is usually connected across systems, ownership, and process.
Review the full operating picture:
- What tools are being used across the business
- Which tools overlap or duplicate each other
- Who owns each business-critical system
- How access is requested, approved, changed, and removed
- Where files, client updates, and reporting should live
- Which support requests keep repeating
- Which security decisions keep reaching leadership
- Which renewals are coming up and whether each tool still earns its place
- Which processes are undocumented or dependent on one person
The practical shift here is ownership.
Every core system should have:
- A named business owner
- A clear admin owner
- A defined access process
- A support path
- A renewal decision-maker
- Basic documentation for how the system is used
This removes unnecessary decisions from leadership and gives the team clearer ways to work.
A score of 4–5 does not always mean the company needs a full technology rebuild. But it does mean the current setup needs more structure. The business should not rely on memory, favors, and individual workarounds to keep daily work moving.
6: Your business has outgrown its current IT structure
A score of 6 is a serious signal.
It means IT drag is showing up across every major area: access, tools, renewals, files, workarounds, and security ownership.
At this point, the issue is that the structure itself is no longer keeping up with the business.
The company may still be functioning, but it is functioning with too much hidden effort.
This is where IT drag becomes a scaling risk.
The business can keep growing, but the current structure will make that growth harder than it needs to be.
What to do when your score is 6
Treat this as an operating model problem.
And again, do not start with “Which tool should we replace?” Start with “How should technology support the way this business now works?”
The review should cover:
- Full software and systems audit
- Access process for starters, movers, and leavers
- Admin permissions and security ownership
- File storage and single source of truth
- Support process and escalation paths
- Documentation for key workflows
- Software renewals and unused tools
- Tool ownership across departments
- Security risks, passwords, permissions, and user access
- Future growth needs over the next 12–24 months
At this stage, the business needs a clearer structure.
That may mean consolidating tools, removing systems that no longer serve the business, documenting key workflows, assigning proper owners, tightening permissions, and building a support process that does not depend on leadership.
The real work is designing an IT model that matches the company’s current size, speed, and complexity.
That is the difference between fixing symptoms and building a structure that can support the next stage of growth.
Reduce IT Drag Before It Becomes the Way Work Gets Done
The companies that scale well do not wait for systems to break down. If your IT Drag Score showed more friction than expected, The Isidore Group can help you review your current setup and create an IT structure that supports the way your business needs to operate next. Contact us
