Focused execution / PRACTICAL GUIDE

Define stop criteria while optimism is still high

Agree meaningful stop signals, decision authority and a responsible exit before sunk effort makes an experiment harder to reconsider.

AI-assisted drafting · Illustrative examples · Editorial approach
Contents of this guide
THE SHORT ANSWER

Stop criteria name conditions that should trigger reconsideration of an initiative, along with who decides and how existing commitments will be handled. Set them before substantial effort is spent. The criteria should make disappointing evidence safe to report and distinguish stopping expansion from abandoning responsibilities.

01

Connect the rule to the uncertainty

Begin with why the initiative is exploratory. Perhaps you do not know whether a customer problem is important, a partner can contribute or the delivery effort is manageable. Choose stop signals that bear on that uncertainty. A general instruction to stop if things go badly provides little guidance when everyone interprets “badly” differently.

Use conditions that can be observed within the test. A time or effort limit can protect capacity, but explain what decision follows when the limit is reached. The team might stop, seek an explicitly approved extension or narrow the question. Avoid thresholds chosen for their tidy appearance when the evidence cannot support that precision.

02

Agree authority before incentives become tangled

Name who can call a review and who makes the continuation decision. Include a route for people to raise concerns without having to prove that the entire initiative has failed. Operational, safety or legal concerns may require immediate specialist handling rather than waiting for the planned business review.

Discuss the incentives around reporting. If owners believe stopping will be treated as personal failure, they may soften the evidence or redefine the target. Make the purpose explicit: limiting exposure and learning what deserves more commitment. An experiment can be well executed and still show that the underlying opportunity should not be pursued.

03

Plan a responsible exit with the participants

List commitments already made to customers, partners and staff. Stopping an exploratory expansion does not automatically end those obligations. Agree how promised feedback, payments, support or data handling will be completed. Where contracts or other consequential requirements apply, involve appropriate qualified support.

Describe the operational steps of an exit, including communication and any fallback. The easiest moment to identify them is often before people depend heavily on the new arrangement. Check whether the trial is truly reversible for those affected. A decision that is cheap for the supplier to reverse can still create significant disruption for a customer.

Include who will communicate the decision and what participants need to know to adjust their own plans. A clean internal closure is incomplete when affected partners are still waiting for a promised next step.

04

Use the criteria without hiding new information

During the initiative, compare evidence with the agreed signals. Preserve unexpected effects and changed conditions. A criterion may become inappropriate because the context genuinely changed, but revise it explicitly with the decision authority rather than quietly moving the boundary to protect the original plan.

At review, explain whether the signal was reached, what remains uncertain and why continuing or stopping is justified. Record extensions as new commitments with a question and limit. Avoid extending automatically because the team has already invested effort. Past work can inform what is learned, but it does not make additional work worthwhile on its own.

PUT IT IN CONTEXT

Fictional example: an exploratory partnership has an end

A fictional scenario to explain the method, not a customer result or a market benchmark.

A fictional business explores a partnership for six weeks, limiting the trial to a defined amount of staff effort. The primary question is whether the two organisations can identify a shared customer problem worth testing. Both agree that general networking activity alone will not justify expanding delivery work.

By the review, they have held useful conversations but cannot describe a specific problem or suitable participant group. They decide to stop the expansion effort and complete the feedback summary promised to each other. Contact details and shared material are handled according to their agreement. The team records what it learned without describing the exploration as a failed relationship. These invented conditions illustrate a responsible stopping decision, not a universal six-week rule or a prediction about partnership value.

TAKE THIS INTO YOUR NEXT CONVERSATION

A practical next-step checklist.

  • Tie each stop signal to a consequential uncertainty.
  • Name review and continuation authority in advance.
  • Set time or effort boundaries with a clear decision path.
  • Plan how existing participant commitments will be completed.
  • Record extensions explicitly rather than moving the boundary silently.

Common questions.

Do stop criteria mean we must stop automatically?

Some safeguards require immediate action, while exploratory business criteria may trigger a review. State the distinction in advance so people know which response is required.

What if a promising signal appears just before the limit?

Assess it against the original question and the cost of further learning. An extension can be reasonable when explicitly authorised with a new boundary, rather than granted because optimism returned.

Further reading & source context.

These primary references provide background. They are not evidence for the fictional example above and do not endorse AccelerateLink.

Found an error or a missing qualification? Send an editorial correction.

FROM READING TO YOUR NEXT MOVE

Find my next move.

Use a practical tool to turn this idea into a clearer starting point.

Find my next move