Not every troubled project has failed. Some simply continue for too long without a proper diagnosis.

Some projects are formally active, consume budget and report progress - while internally, confidence keeps declining. Impact falls short of expectations, friction increases, priorities shift, but the real cause remains unclear. This is where the Rescue Review starts: we distinguish symptoms from root causes and show what needs to be stabilised first before further implementation makes sense.

Relevant when:
• the project is formally running, but the expected impact is not materialising
• friction between business teams, IT or service providers is increasing
• priorities are becoming unclear
• confidence in the direction, control or outcome is declining
• an existing initiative needs to be reassessed from a difficult position

What we do in practice

We do not just look at status. We look at the actual causes of stagnation. In the Rescue Review, we analyse the situation independently, with a focus on impactand control.

Assess points of friction

Identify root causes

Evaluate control

Prioritise stabilisation

The goal is not to assign blame. It is to rebuild a reliable basis for the next decisions and implementation steps.

What you receive

The outcome is not more activity, but a reliable diagnosis and a realistic path back to impact and control.

Diagnosis of the project situation

Critical areas for action

Prioritised stabilisation

Decision-ready summary

Why companies involve us in situations like this

We are typically brought in when a project is still running, but no one can say with confidence why it is no longer holding up. In these phases, another internal alignment cycle rarely helps — and neither does theoretical strategy advice. What is needed is a vendor-independent, implementation-aware view of friction, root causes and priorities, without being tied to a specific tool, vendor or preferred solution. We focus less on abstract frameworks and more on realistic next steps that hold up from a business, organisational and commercial perspective.

Request a Rescue Review

In a short initial conversation, we clarify together whether a Rescue Review makes sense for your situation and which areas of friction should be assessed first.

Foto von Thomas Howert von inics

Thomas Howert

IT expert and project manager for over 15 years

FAQ — Common questions about the Rescue Review

Is a Rescue Review only for failed projects?

No. A Rescue Review is often most valuable before a project reaches the point of failure, while there is still enough substance, but direction, impact or control are slipping.

Is this about criticising ongoing external projects?

No. The goal is not to assign blame, but to provide a neutral assessment of why the project is not holding up and which adjustments could make it viable again.

Can implementation follow from this later?

Yes. The first step is to understand the situation properly, separate causes from symptoms and set priorities. If this leads to concrete implementation steps, we can support them directly or bring in suitable specialists from our network.

How is this different from a standard project review?

A standard project review often looks at status, budget and progress. The Rescue Review looks at impact, friction, root causes, control and realistic stabilisation.