Find the next step in a stalled digital project
Before adding people, tools or deadlines, establish what is actually preventing progress. A short, honest review can turn a vague concern into a useful decision.
Reconstruct the current situation
Ask the people doing the work to show the latest working version, the current priorities and the last decision that changed the plan. Separate observed facts from explanations and assumptions. A status report is useful, but a real workflow often reveals more.
Choose one piece of work and trace it through the team. Where does it wait? Which question keeps returning? Where does responsibility become unclear? Record the examples without starting with blame.
Illustrative situation: a feature moves between development and review for weeks. The bottleneck may be an unclear acceptance decision, not coding speed. Show one rejected example and ask what would have made it acceptable.
A checklist to reuse
- What works today, demonstrated rather than reported?
- What has changed since the original plan?
- Which decisions remain unresolved?
- What do users currently do instead?
Name the type of blocker
An unclear goal needs agreement about the outcome. A technical uncertainty needs a bounded experiment. Too much parallel work needs a priority decision. Missing ownership needs someone empowered to decide. These are different problems and should not receive the same remedy.
Discuss one blocker at a time. Write a sentence stating what cannot move, why you believe that is the case and what evidence would change your mind. Avoid turning a plausible explanation into a proven cause.
A checklist to reuse
- Is the outcome clear enough to accept or reject work?
- Does the team have the skills and access needed?
- Are dependencies and decision owners explicit?
- Is work starting faster than it is being finished?
Choose one bounded intervention
Select a step that reduces the most important uncertainty. Set a time boundary, a responsible person and a decision the result will support. A short review with the right decision-maker may be more useful than reorganising the whole project.
Keep the intervention reversible where possible. Pause a competing task, test one integration or agree one acceptance example. Make sure the people affected understand what changes and for how long.
A checklist to reuse
- One blocker, one owner, one intervention
- A result that can be inspected
- A date to review the result
- A clear decision to make afterwards
Leave with a decision, not another status document
Record what you will continue, change or stop. Preserve the reasoning so the team does not reopen the same discussion without new evidence. State what remains unknown and who will investigate it.
Check whether the intervention improved actual work. If it did not, review the original explanation instead of simply extending the deadline. Bring in an external perspective when the team cannot resolve a disagreement or needs specialist help to test an assumption.
A checklist to reuse
- A one-page current-state summary
- The next decision and its owner
- A small action the team can start now
- Evidence to review at the next check-in
Sources and upkeep
These sources inform the guidance above. The examples and checklists are modeleven’s editorial recommendations, not promises of results. Sources reviewed 8 September 2026.