It usually starts with good intentions. A new strategic priority. A regulatory deadline. A promising technology. An executive request that can’t wait. Before long, the IT portfolio is packed with initiatives that all feel important, and suddenly, everything is a priority. This is the quiet reality in many organisations today: too many IT initiatives running at the same time, stretching teams thin and quietly eroding value. The problem isn’t ambition. It’s overcommitment.
When Everything Is a Priority, Nothing Really Is. Most IT leaders can list dozens of active initiatives at any given moment – system upgrades, cloud migrations, security improvements, data platforms, compliance work, automation, innovation pilots. Individually, each initiative makes sense. Collectively, they create a delivery environment where:
- Teams are constantly context-switching
- Critical work moves slowly despite long hours
- Dependencies pile up and block progress
- Delivery dates become estimates, then aspirations
- The uncomfortable truth is this: adding more initiatives doesn’t increase throughput. It usually reduces it.
Overcommitment rarely shows up as a single dramatic failure. Instead, it shows up in subtle but damaging ways.
Slower Delivery Across the Board – When people are split across too many initiatives, progress stalls everywhere. Work gets started, paused, restarted, and finished much later than expected. The organisation feels busy, but outcomes arrive slowly.
Declining Quality and Rising Rework – Rushed handovers, incomplete testing, and rushed decisions become normal. Defects surface later, creating rework that consumes even more capacity.
Burnout Disguised as “High Performance” – Extended periods of overload lead to exhausted teams. Productivity drops, engagement fades, and experienced staff quietly disengage or leave.
Lost Strategic Value – Initiatives that were meant to create competitive advantage end up delivering partial benefits; not because they were wrong, but because they were never given the focus they needed.
If overcommitment is so damaging, why is it so common? A few patterns show up repeatedly:
- Governance focuses on approval, not capacity – initiatives are approved individually, without a portfolio-level view
- Saying “yes” feels safer than saying “not now” – especially when requests come from senior stakeholders
- Success is measured by activity, not outcomes – how much work is underway, not how much value is delivered
- Capacity is treated as elastic – teams are expected to “find a way”
- None of this is malicious. It’s structural.
High-performing IT organisations don’t do more. They do less deliberately. This doesn’t mean abandoning innovation or slowing down the business. It means making clear, disciplined choices about where focus lives right now.
Some practical shifts that make a real difference are:
- Limit Work in Progress at Portfolio Level – Just as Agile teams limit WIP, portfolios need explicit limits. If a new initiative starts, something else must slow down or stop.
- Sequence Instead of Parallelise – Many initiatives don’t need to run at the same time to deliver value. Sequencing work often delivers outcomes faster than spreading effort thinly across everything.
- Make Capacity Visible – When leaders can clearly see team capacity, dependencies, and constraints, trade-off conversations become easier and more rational.
- Redefine What “Priority” Means – A true priority is something that gets first call on people, funding, and decision-making. If ten initiatives are labelled top priority, the label has lost its meaning.
Managing overcommitment isn’t a tooling problem. It’s a leadership one. It requires moving from asking “Can we add this?” To asking “What must we stop or delay to make this successful?”. That single question changes the conversation from optimism-based planning to reality-based delivery.
Busy IT teams are not the same as effective IT teams. If your organisation feels constantly stretched but struggles to see meaningful outcomes land, the issue may not be execution – it may be too much work in motion. Sometimes, the fastest way to deliver more value is to commit to less. If you’re seeing the symptoms of overcommitment in your IT portfolio, it may be time to step back and rethink how initiatives are prioritised, sequenced, and governed – before the cost becomes impossible to ignore.