The craft · practical guide Grows out of manual 06, Scope your own project Published craft page

Practical guide

When to change or stop a project.

Money already spent can make a project hard to stop. Review what remains: the useful result, the cost to reach it and the commitments you would need to close. Use four questions and an illustrative example to compare stopping, reducing or continuing the work.

UseWork the tool now
FormatOn-page review guide
ForThe midpoint decision
Use the review questions Read the manual it comes from
Two people working through a project question, evidence, work and next check.

Why review

The next commitment needs its own reason.

The original plan may still be worth finishing. Or new facts may justify a smaller version or a stop. Compare the remaining work and its expected value, including the obligations and costs of changing course.

You do not have to wait for a literal midpoint. Review when a material assumption, requirement, cost or delivery condition changes.

Four review questions

Write the case for the next move.

01 · Current position

What is actually complete?

Compare the work with the agreed completion checks. Record spending, remaining commitments, usable outputs and gaps.

02 · New evidence

What changed?

Identify a changed requirement, failed assumption or new constraint. Distinguish evidence from discomfort about work still to do.

03 · The choice

Stop, reduce or continue?

Compare the remaining effort, useful result and consequences of each option. Name who can approve the change.

04 · Follow-through

What happens after the call?

Assign closure or delivery tasks, protect required records and communicate changed commitments. Set the next check if work continues.

Who can use it

For the sponsor and people doing the work.

Bring the current brief, delivery evidence and remaining commitments into the review. Include the people who will use the result. The sponsor retains the decision and should hear disagreements before approving more work.

Illustrative example

A customer order form.

Imagine a project to collect complete order information and transfer it into the delivery system. The form works, but the automatic integration is unfinished. These are fictional alternatives, not client outcomes.

Continue: if the integration is still needed, remaining work is understood and the users can test acceptance, approve that work with a named owner and limit.

Reduce: if an agreed manual transfer serves the current volume, consider releasing the form with that process. Record the ongoing manual cost and the conditions for revisiting automation.

Stop: if the company has adopted another system that makes the form unnecessary, compare reuse and closure options. Resolve supplier and customer commitments before ending the work.

Use the evidence

Stopping is not automatically the clever answer.

The review can justify continuing.

A difficult phase is not proof that a project is wrong. Check whether the result remains useful and achievable, and whether stopping creates greater cost or harm. Use appropriate specialist advice for technical, contractual or regulated obligations.

Back to the manual →
Get another view when
  • The facts and the progress report disagree.
  • Nobody can explain the remaining work.
  • A decision is being deferred to protect a reputation.
  • The team cannot agree what completion means.

When the work is live

Need an outside view on the project?

Stan reviews each request for fit. All corporate work starts with an inquiry and is quoted separately. Stan confirms the people, stakes, scope, and fee in writing before work starts. This page provides a review structure; any engagement addresses the actual project under an agreed scope.

Discuss the project

Work with me · $1,500/month 1:1 business work · Request scope