Let’s be honest: your flagship transformation programme is bleeding. You’ve spent millions, the "Red" status reports are piling up like traffic tickets, and your board is losing patience.
Your first instinct? Call the big guys. The global logos. The firms that charge $4,000 a day for an "Associate Partner" who hasn't seen a codebase or a real-world deployment since the 2010s.
You think you’re buying safety. In reality, you’re paying the Junior Tax IT consulting surcharge. You are subsidizing the training of 24-year-old MBAs to "learn" your complex enterprise environment on your dime.
At Dark Consultancy, we don't do slide-deck theatre. We do programme rescue consulting for leaders who are tired of paying for pedigrees and ready to pay for outcomes. Here are the seven mistakes you’re making right now, and how to stop the bleeding.
1. You Hired the Logo, Not the Team
This is the ultimate corporate security blanket. You hired a "Big Four" or a "Tier One" firm because "nobody ever got fired for hiring them."
Wrong. People get fired when the $50M SAP migration or the Cloud Modernization project fails anyway, despite the premium logo on the letterhead.
The Mistake: You signed a contract based on the grey-haired partner who sold the deal, but your daily reality is a fleet of juniors who spend 40 hours a week making the PowerPoint slides look "on-brand" instead of fixing the broken CI/CD pipeline.
How to stop it: Demand to see the CVs of the people actually doing the work, not the "Engagement Lead" who visits once a month. If the team doesn't have at least 10 years of hands-on execution experience in regulated environments, you're paying a Junior Tax.
2. You’re Stuck in the "Discovery" Loop
Failing programmes love "Discovery." It feels like progress. You have workshops, Miro boards, and sticky notes everywhere.
The Mistake: Six weeks into your "rescue," the consultants are still "gathering requirements" and "mapping stakeholders." They are documenting the fire while the building is burning down. This is classic Junior Tax IT consulting behavior, juniors need months to understand the context that a senior operator understands in three days.
How to stop it: Insist on a Delivery Diagnostic. This shouldn't take months. It should take two weeks. You need a "no-BS" assessment of what is broken, why it’s broken, and a tactical roadmap to fix it. If they can’t show you a path to a "Green" status within 30 days, they aren't rescuing you; they’re squatting.
3. You’re Measuring "Activity" Instead of "Velocity"
Consultants are great at being busy. They attend every meeting. They send long email summaries. They create 80-slide decks for the Steering Committee.
The Mistake: Confusing motion with progress. In programme rescue consulting, the only metric that matters is delivery velocity. Are the features shipping? Is the data migrating? Is the risk actually decreasing?
How to stop it: Throw away the RAG (Red-Amber-Green) reports that are based on "sentiment." Move to automated, data-driven dashboards. If your consultants can't show you real-time deployment metrics or burn-down charts that actually move, they are just professional observers.
4. You’re Treating a People Problem Like a Tech Problem
Most "failed" tech projects are actually failed human systems.
The Mistake: You bring in "experts" to fix the architecture, but they ignore the fact that your DevOps team and your Security team haven't spoken in six months. Or, worse, the consultants create a "Shadow PMO" that adds more friction to the people actually writing the code.
How to stop it: True programme rescue requires senior leadership involvement. You need people who can walk into a room of disgruntled VPs and recalibrate expectations. Juniors can't do this. They don't have the "scars" or the authority to challenge a toxic culture.
5. You’re Ignoring the "Hard" in Hardware and Software
Many consulting firms have pivoted so far into "Strategy" that they’ve forgotten how things actually work.
The Mistake: Your rescue plan is high-level and abstract. It talks about "synergies" and "digital-first mindsets" but doesn't mention the legacy API that’s bottlenecking the entire platform.
How to stop it: You need Product Engineering & Technical Enablement. Your rescue team should be able to look at your code, your cloud architecture, and your data pipelines. If they can’t talk to your Lead Architect without a translator, they are part of the problem.
6. You Have "Soft" Governance
When a project is failing, the governance usually becomes a theatre of politeness. Nobody wants to be the "bad guy."
The Mistake: The steering committee meetings are polite updates rather than brutal sessions of "Why aren't we moving?"
How to stop it: Implement an Execution Roadmap. This is a contract of accountability. It defines who is responsible for what, by when, with zero ambiguity. Senior consultants who have been in the trenches know that "clear is kind." If your consultants are too "consultant-y" to tell you the hard truth, fire them.
7. You Forgot the Exit Plan
The goal of a rescue is to… well, rescue the project and then leave.
The Mistake: The rescue team becomes a permanent fixture. They build a dependency where your team can't function without them. This is how a 6-month rescue turns into a 3-year "partnership" that drains your budget.
How to stop it: The "Scale & Delivery" phase of a rescue must include a knowledge transfer and a decommissioning plan for the consultants. At Dark Consultancy, our success is measured by how quickly you don't need us anymore. We build the capability, we stabilize the platform, and then we hand you the keys.
The Manifesto: Stop Paying the Junior Tax
The "Junior Tax" is the hidden cost of enterprise failure. It’s the delta between what you pay for (Senior Expertise) and what you get (Junior Effort).
In 2026, with the speed of Platform Modernization, you cannot afford to have your project be a classroom for a junior team. You need an execution-first mindset. You need people who have delivered at scale in regulated environments and aren't afraid to get their hands dirty.
Actionable Next Steps for CIOs:
- Audit the CVs: Look at the LinkedIn profiles of the "on the ground" team from your current consulting partner. If the average experience is under 5 years, you are paying the Junior Tax.
- Kill the Decks: For one week, ban PowerPoint. Ask for a live demo or a technical status report from the repo. Watch how many consultants panic.
- Get a Diagnostic: If you aren't sure where you stand, get an independent, Delivery Diagnostic.
The bottom line: Strategy is easy. Execution is hard. Rescuing a failing execution is the hardest job in the enterprise. Don't send juniors to do a senior's job.
FAQ: Programme Rescue Consulting
What is "Junior Tax IT consulting"?
It is the inefficiency and hidden cost incurred when large consulting firms staff high-stakes enterprise projects with inexperienced, junior-level consultants while charging senior-level rates. The client ends up paying for the time it takes the juniors to learn the industry, technology, and business context.
How do I know if my project needs a "Rescue"?
Key indicators include persistent "Red" status reports, missed milestones, high turnover in the project team, declining stakeholder trust, and a growing gap between the "strategy slides" and the actual technical output.
How long does a typical Programme Rescue take?
A professional rescue starts with a 2-week Delivery Diagnostic, followed by a 4-8 week stabilization phase. The total duration depends on the scale, but you should see measurable velocity improvements within the first 30 days.
Is Programme Rescue only for technical failures?
No. Many rescues focus on governance, vendor management, or organizational alignment. However, in modern enterprise, the technical and organizational are usually inextricably linked.
Ready to stop the bleeding?
Contact Dark Consultancy today for a no-nonsense Delivery Diagnostic.
About the Author
Kunal Patel is the CEO of Dark Consultancy, where he works with enterprise and public-sector leaders to rescue failing programmes, strengthen delivery governance, and reduce execution risk across high-impact transformation initiatives. His focus is practical: helping organisations move from stalled plans and unclear accountability to measurable delivery progress. Kunal’s experience spans enterprise technology modernisation, digital delivery execution, cloud and platform transformation, and complex programme recovery in environments where failure is not an option. He is known for an execution-first approach that prioritises delivery truth, senior accountability, and business outcomes over slide-deck consulting. Through Dark Consultancy, he advises CIOs, CTOs, programme sponsors, and transformation leaders on how to stabilise troubled initiatives, re-baseline around value, and build the governance and engineering discipline needed to deliver with confidence.