You’re already in the hole. Your $50M digital transformation is stalling, the board is asking uncomfortable questions, and your internal team is burnt out. So, you do the "responsible" thing: you bring in a big-name consulting firm to handle the programme rescue consulting.
But three weeks in, that sinking feeling in your gut returns. Instead of momentum, you’re getting more slides. Instead of clarity, you’re getting more "alignment workshops."
In the world of failed IT programme recovery, not all help is helpful. In fact, many traditional consulting models are incentivised to keep the "diagnostic" phase running as long as possible while billing you for the privilege of training their new recruits.
If you recognise any of these 10 signs, your rescue consultant isn't saving your programme, they’re just measuring the depth of the water while you drown.
1. You’re Paying the "Junior Tax" (Again)
We’ve all seen it. The partner sells the engagement with a world-class CV, but the day the work starts, they vanish. In their place is a team of shiny-shoed associates who haven't seen a server room in their lives.
This is the Junior Tax in IT consulting. You are effectively paying premium rates to educate their staff on your industry. If your "recovery experts" spend more time asking you how your business works than telling you how to fix it, you’re paying the tax.
2. They’ve Been "Assessing" for 3 Months with No Roadmap
A rescue shouldn't feel like an archaeological dig. If your consultants have been "interviewing stakeholders" for 90 days and haven't produced a single delivery milestone, you don't have a rescue; you have a residency.
Real recovery requires an execution-first mindset. At Dark Consultancy, we believe you can't assess in a vacuum. We use a 14-Day Delivery Diagnostic to identify the rot and move straight into an Execution Roadmap. Anything longer is just billable filler.
3. Their "Diagnostic" is Actually a Sales Deck for Phase 2
Look closely at the findings. Are they pointing to specific technical bottlenecks, or are they high-level observations that conveniently require a 12-month "Transformation Support" package to solve?
If the diagnostic doesn't give you actionable steps you could take without them, it’s not a diagnostic, it’s a sales pitch dressed up in a PDF.
4. They Prescribe Before They Diagnose
On the flip side, beware the consultant who arrives with the answer on Day 1. "You need to move to SAFe," or "This is a cloud architecture issue."
If they haven't looked at your code, your deployment pipelines, or your governance logs, they aren't rescuing your programme; they’re selling you their playbook. Every failed programme is failing for unique reasons, usually a mix of technical debt and delivery governance failure.
5. You’re Seeing "Watermelon Status" Reports
Is the consultant telling you everything is "Green" or "Amber" while the project is clearly on fire? This is Watermelon Status, green on the outside, red on the inside.
If your rescue consultant is papering over the cracks to keep the peace with stakeholders, they are making the eventual explosion much worse. A true rescue partner tells you the ugly truth, even when it’s uncomfortable for the CIO to hear.
6. They Avoid the "Technical Grit"
Many rescue consultants are "slide-deck consultants." they are great at reporting on the disaster, but they won't get their hands dirty in the CI/CD pipeline or the legacy codebase.
A failed IT programme recovery often fails at the execution layer. If your consultants aren't talking about technical debt, architectural bottlenecks, or release velocity, they are just rearranging the deck chairs on the Titanic.
7. Their Playbook is a Template
"Our proprietary 5-step methodology" is often code for "A template we use for everyone from retail banks to government agencies."
Enterprise environments, especially regulated public sector programmes, have specific constraints. A generic playbook ignores the nuances of your specific delivery environment, leading to a "recovery" that looks good on paper but fails in production.
8. No "Skin in the Game"
If the programme fails again in six months, does the consulting firm lose anything? Usually, they’ve already moved on to the next client.
Signs of a lack of accountability include vague "Definition of Done" criteria and contracts that focus on "reasonable endeavours" rather than business outcomes. You need a partner who measures success by your delivery outcomes, not their hours billed.
9. The Recovery is "Meeting-Centric"
If your calendar is now 80% "Recovery Workstreams" and your engineers are complaining they have even less time to actually code, your consultant is killing your productivity.
A rescue should remove friction, not add it. If the solution to a delivery stall is more meetings about the stall, the consultant has become part of the overhead.
10. They Ignore the Culture Rot
A failing programme usually has a failing culture, low morale, fear of speaking up, and "hero culture." If your consultant only focuses on the JIRA board and ignores the fact that your best developers are looking for the exit, the "rescue" won't stick.
The hidden cost of the empty chair is real. A true rescue involves stabilising the team just as much as the technology.
Moving Beyond the "Consultancy Trap"
The reality is that most CIOs and CTOs don't need a 3-month assessment. They need to know why delivery has stopped and exactly what levers to pull to start it again.
This is why we built Dark Consultancy differently. We don't send juniors. We don't hide behind 200-page slide decks. We lead with execution.
Our 14-Day Delivery Diagnostic is designed to cut through the noise. We look at your governance, your architecture, and your execution model to give you a "no-filter" view of why your programme is failing, and a roadmap to fix it.
Stop the Bleeding
If your current "rescue" feels like a slow-motion car crash, it’s time to change lanes. Don't let the "Junior Tax" and "Watermelon Reporting" sink your career alongside the programme.
Book a Programme Rescue Audit with Dark Consultancy today.
FAQ
Q: How do I know if I’m paying a "Junior Tax"?
A: Look at the day-to-day interactions. If your team is spending more time explaining basic technical or business concepts to the consultants than receiving strategic advice, you are paying for their training.
Q: Is a 14-day diagnostic really enough for a $100M programme?
A: Yes. A diagnostic isn't about solving every bug; it’s about identifying the systemic failures in governance, architecture, and leadership that are causing the stall. You can find the rot in 14 days; fixing it takes longer, but you need the right map first.
Q: My consultants say we need a "cultural transformation" before we can ship code. Is that right?
A: Culture follows delivery, not the other way around. Winning (delivering) is the best way to fix a broken culture. If they want to spend six months on "culture" without shipping a single feature, they are stalling.
Q: What is the most common reason for IT programme failure?
A: Usually, it’s a "delivery gap": the space between high-level executive strategy and the reality of technical execution. Governance often fails to bridge this gap, leading to Watermelon Status.
About the Author
Kunal Patel : CEO & Founder, Dark Consultancy
Kunal Patel founded Dark Consultancy after two decades leading technology and transformation programmes across the public sector, financial services, defence, and energy industries. He has directly managed programme recovery engagements for government agencies, development finance institutions, and regulated enterprises across the US, Middle East, South Asia, and Southeast Asia ; ranging from $5M platform migrations to $200M+ enterprise transformation portfolios. Kunal is a recognised practitioner in delivery governance for regulated environments and holds PMP and PRINCE2 Practitioner certifications. He leads every new client engagement personally and remains accountable throughout the programme lifecycle. Connect with Kunal on LinkedIn