The IT Velocity Paradox: Why Your Transformation Is Slower Than Before

The Story: Transformation That Slows You Down

A large government contractor (50,000+ employees) made a critical decision: After years of treating IT as a cost center, they realized smaller, nimbler competitors were delivering solutions faster and better. They needed to compete. They needed speed. They needed IT to be an enabler, not a brake.

So they hired a Chief Digital Officer.

New vision. New direction. New promise of transformation. On paper, everything was supposed to change.

But here's what actually happened.

When I Started, I Got Four Projects

Three of them made it through their Approval of Work (AOP) process. Got business cases approved. Got presented to leadership.

Then, during the presentation, we discovered: one project had no funding.

So we had to stop, find funding sources, have meetings with finance, delay the project by weeks — before we even started.

We worked on two more business cases. Same problem. No funding defined, even though they went through AOP.

This should have been caught during the AOP process. Should have been part of annual operations planning.

But here's why it wasn't: Everyone is in meetings all day. They don't return emails. They don't show up to coordinate on budget discussions. So it takes weeks to identify a funding source that should have been locked in months earlier.

$6 Million in Undefined Spend

We started reviewing the entire IT portfolio: roughly 100 projects across the organization.

When we did the deep dive with IT Finance to understand what's actually being tracked and spent:

We found a project with $6 million in spend that was never even defined in the portfolio management system.

$6 MILLION. Just... missing from the books.

The VP of IT didn't know about it. Finance couldn't account for it. Yet the money was somehow being spent.

This is portfolio management completely broken. The AOP process completely broken. The company doesn't even know what it's spending money on.

Estimation Disasters

On another project, the scoping was drastically underestimated — we're talking months of error.

The effort to implement was way bigger than planned. Delivery date moved. Three times. Each time by months.

Why? The people providing estimates (internal staff, plus Infosys and HCL) didn't provide accurate information. There was no validation. No accountability for accuracy. So estimates were optimistic guesses.

Compliance Ignored Until Crisis

One project: CMMC (Cybersecurity Maturity Model Certification) compliance.

The company needed federal CMMC certification or lose hundreds of millions in government contract revenue.

They knew about this requirement for 10 months.

And did nothing until the very last minute.

It took an outside consultant to actually flag it and start working on compliance positioning — just to save the company from massive revenue loss.

Procurement Process: The Invisible Bottleneck

After business cases got approved and projects were ready to execute, the next wall was procurement.

To bring in vendors (Infosys, HCL, external consultants), you had to create purchase requisitions. Sounds simple. It's not.

The procurement process has six finance approvers in the workflow. Every requisition has to pass through all six.

But the workflow is broken:

• Wrong approvers included: Requisitions get routed to approvers who shouldn't be approving them, causing rejections and resubmissions
• Incorrect charge codes: Projects have the wrong charge code assigned, and you don't find out until the last approver in the chain — meaning you restart the entire workflow
• Approvers don't respond: People in the approval chain are in meetings, overloaded, or just don't prioritize reviewing requisitions

Real example: Two purchase requisitions for vendors. Three weeks elapsed. Still not approved. One required a complete restart because the last approver discovered the charge code was wrong — one week of delay alone.

Projects that were ready to execute were stuck waiting for vendor contracts. Weeks of "approved project ready to start" became "waiting on procurement."

This is a process problem layered on a communication problem. The workflow design is broken. People don't communicate upfront about charge codes. Approvers don't respond. So projects slip from "ready to execute" to "stuck in procurement" — another invisible delay that nobody talks about in transformation announcements.

The People Problem

Everyone is focused on their own stuff. They're in a ton of meetings. They don't respond to emails. There's little accountability for responsiveness or coordination.

It's a tough environment to drive transformation.

And here's the thing: You can hire a CDO. You can declare new direction. You can say 'we're going to move faster and compete better.' But if you don't fix the people, the processes, and the accountability... nothing changes. You just add frustration to dysfunction.

The IT Velocity Paradox

What This Costs

Why This Happens

Breaking Out of the Paradox

Here's the hard truth: Transformation Theater is seductive because it creates the appearance of change without requiring the hard work of actual change.

Hiring a CDO is visible. Declaring new direction is visible. But fixing portfolio governance? Changing people's accountability structures? Making people respond to emails and coordinate? That's invisible hard work. Yet it's the invisible work that determines whether transformation actually succeeds.

You Need Clarity

The first step is understanding what's actually broken. Not what you think is broken, but what IS broken. That's where an IT Assessment comes in.

An assessment reveals:

Then transformation can actually work, because you're fixing real problems, not just adding a CDO on top of dysfunction.

Related Reading