When projects stall, restore the ability to decide.

01Name the blocker accurately

“We are not making progress” is a symptom. Sort the open issues by cause:

• Decision: Two require­ments conflict, but nobody has decided which takes priority.
• Capacity: Someone is assigned to several initi­atives and cannot deliver the promised work.
• Dependency: Another team or supplier needs to deliver something first.
• Unclear brief: People disagree on what “finished” means.
• Technical or business problem: An assumption was wrong; the planned solution does not work under actual conditions.

A capacity gap needs a resource decision. An unresolved require­ment needs a decision about the substance. More pressure does not reliably solve either. Record evidence, an owner and the next clarifying action for every blocker.

02Bring the brief up to date

Read the original project brief in light of what you know today. Is the expected benefit still relevant? Which assump­tions no longer hold? Which outcomes are firm commit­ments, and which are wishes?

Distin­guish three things: costs already incurred, effort required from today and remaining benefit. Past effort alone does not justify further spending. Equally, a delay does not auto­matic­ally make a project worthless.

Compare at least these options: continue, reduce scope, pause and stop. Document the consequences for customers, employees, operations and contrac­tual commit­ments. Seek legal support for contrac­tual consequences where needed.

03Assign decisions instead of passing tasks around

A task plan shows who is working on something. It does not neces­sarily show who has authority to resolve a conflict. For the key open questions, define who prepares the decision, who makes it, who must be consulted and when an answer is needed.

This is a simplified illus­tration, not a client case. It also shows that a limited launch is only workable if the exception can be managed in practice. “We will do it later” is not a sufficient decision.

04Make the next milestone verifiable

Choose an outcome that resolves the most important uncer­tainty or delivers a useful part of the benefit. “The business team checks three complete test cases and confirms the results” is more useful than “Imple­ment­ation is 80 per cent complete”.

This milestone needs reserved capacity, satisfied prerequis­ites, an owner and acceptance criteria. Keep new require­ments under control: put them on a visible list and assess them against time, cost and benefit. Do not let them slip unnoticed into the agreed scope.

Start each short status meeting with four questions: What is demon­strably finished? What is blocking progress? Which decision is needed? Has the forecast changed? An honest forecast is more useful than an unchanged traffic light nobody believes anymore.

05A restart on one page

Record the agreement and have the project sponsor confirm it:

1. Objective: Which benefit are we pursuing from today?
2. Scope: What is included and what is explicitly deferred?
3. Status: Which outcomes have been checked, rather than merely reported?
4. Blockers: What prevents the next delivery?
5. Decisions: Who decides what, and by when?
6. Capacity: Who is actually available?
7. Milestone: What will be accepted, when and against which criteria?
8. Reas­sess­ment: Which deviation triggers a fresh decision about scope or continu­ation?

A restart is more than an optimistic new date. It is a new agreement that can be checked. Our project management consulting helps make the situation trans­parent and translate that agreement into ongoing delivery management.