Home  ›  Articles

Innovation Execution

When to Stop a Project: Kill Criteria for Innovation and Improvement Work

Deciding when to stop a project is easier when the stopping rules are agreed at approval. Set kill criteria, review on a fixed date against evidence, and choose one of three outcomes: stop, pause or scale.

Shannon Phillips

October 16, 2026

Two colleagues discussing a document across a table
Using Kwokka by UBT Kanban Board

Idea Management Software

KWOKKA by UBT™ collects ideas from employees across your organization and gives each one an owner and a defined path.

Book a Walkthrough

Key takeaways

Decide when to stop a project before it starts: agree the kill criteria at approval.

Review every project on a fixed date, against evidence the owner brings.

End each review with one of three outcomes: stop, pause or scale.

Treat a stop made on evidence as a sound decision, and thank the team that brought the evidence.

Record what was learned, and move the time to stronger work.

When to Stop a Project: Decide Before It Starts

Team Collaboration Icon

Definition

Kill criteria

Conditions agreed before a project starts that say when it will be stopped: the evidence that must be seen by a set date, and the limits on time or cost that must not be passed.

44%

of office workers started 2026 with projects that were at a standstill and still counted as active

1 in 3

or more of the employees surveyed fear that ending a project will be seen negatively

Why Stalled Projects Stay Open

Set Project Kill Criteria at Approval

Evidence

What Must Be Shown

A result the project must produce by a set date, such as a measured saving at one site.

Limits

What Must Not Be Passed

A ceiling on time, cost or people. When it is reached without the evidence, the project returns for a decision.

Fit

What Must Stay True

The conditions that justified the project: the strategy it supports, the need it meets, the sponsor. If one changes, the case is reviewed.

In practice. Write each criterion as one sentence: “If we have not seen [evidence] by [date], we stop.” Record it in the approval document, beside the owner’s name and the review date.

How to Write Kill Criteria People Will Act On

Instead of

Stop if the pilot does not go well

Review progress when there is time

Stop if the costs get too high

Try this

Stop if fewer than 30 of the 100 pilot users return in week four

Review on the first Tuesday of the third month

Return for a decision when spending reaches the agreed ceiling

Review on a Fixed Date, Against Evidence

1

Bring the evidence

The owner presents what was measured against each criterion. Results are kept separate from opinions and forecasts.

2

Compare it with the criteria

The reviewers read the conditions agreed at approval and state whether each one has been met.

3

Decide in the meeting

The named decision maker chooses one outcome before the meeting ends, and the decision is recorded with its reasons.

Three Outcomes: Stop, Pause or Scale

Stop

The Evidence Is Against It

The criteria were not met. The project is closed and its people move to other work.

Pause

The Conditions Are Not Right

The idea holds, but something outside it is missing: a system, a budget or a sponsor. The project is parked with a restart date and a condition.

Scale

The Evidence Supports It

The criteria were met. The project receives the people and budget for its next stage, with new criteria for the next review.

How to Stop a Project Without Blame

Key idea

A project stopped on evidence has answered the question it was funded to answer.

Record What Was Learned, and Move the Time

Idea management software

Idea Management Software That Takes Ideas to Results

KWOKKA by UBT™ collects ideas from employees across your organization, helps your team decide which ones to pursue, gives each one an owner and a defined path, and records what it delivered.

When to Kill a Project: The Decision in Four Steps

1

Set

Kill criteria agreed at approval

2

Review

A fixed date, against evidence

3

Decide

Stop, pause or scale

4

Record

What was learned, and where the time goes

Project review checklist

Kill criteria written at approval, each with its evidence and a date

A review date in the calendar and a named decision maker

Evidence presented against each criterion

One outcome chosen in the meeting: stop, pause or scale

The team thanked, and each person’s next work named

A closing note filed where future teams will find it

Limited-time Q4 offer

Innovation Process Certification at 50% Off

Your team can build this on a real problem in our two-day Innovation Process Certification, for up to 10 people. Alberta organizations that book by 30 November pay half our medium business price.

Frequently Asked Questions

How do you know when to stop a project?

What are project kill criteria?

When should kill criteria be set?

What is the difference between stopping and pausing a project?

How do you stop a project without blaming the team?

What should leaders do when there are too many projects at work?

About the author

Shannon Phillips, Co-Founder of Unbounded Thinking

Shannon Phillips

Co-Founder and Innovation Strategist

Designs structured innovation systems for enterprise organizations and helps leadership teams set priorities that reflect how the organization operates.

Start With a Free Individual Snapshot

The free Innovation Readiness Snapshot gives one person’s view of the same four areas in about five minutes, with a private summary of your results at the end.