Lakhlani International
Research

Proceed, Revise or Stop: How to Make Staged Decisions on an Early-Stage Idea

The hardest decision in innovation is rarely whether to start. It is whether to continue. Money has been spent, people are invested and the evidence is mixed. Without an agreed way to decide, teams tend to drift: extending a project because stopping feels like failure, or abandoning it because of one discouraging result.

Lakhlani International's Research & Innovation page ends its method with a clear step: recommend proceed, revise or stop decisions with a rationale. It also lists a staged way to decide whether to proceed, revise or stop among the problems it addresses. This article explains how to build such a decision process, in a form any team can adopt.

Why decisions need to be staged

Early-stage ideas carry several uncertainties at once. Staging breaks the commitment into steps, each with a defined question and a decision. At each gate, you ask whether the evidence justifies the next, larger commitment.

The idea is not new. Technology readiness scales, such as NASA's nine-level Technology Readiness Levels, describe how technologies progress from basic principles to operational use, with different evidence expected at each level. The scale comes from aerospace and needs adapting elsewhere, but it illustrates the principle: the evidence needed to move forward depends on the stage, and the cost of being wrong rises with each step.

The three outcomes

Define them before you start.

What each decision means

  • →Proceed. The evidence meets the agreed criteria; commit to the next stage. Typical trigger: key assumptions supported and remaining risks acceptable.
  • →Revise. The idea has potential, but a specific element needs to change. Typical trigger: evidence supports part of the idea, and a segment, price, design or scope needs adjusting.
  • →Stop. The evidence does not justify further investment. Typical trigger: key assumptions failed, and the cost of more evidence exceeds its likely value.

A fourth category often appears: inconclusive. Treat it as a prompt for a narrower, cheaper test, not as permission to continue indefinitely. If another round of testing would not change the decision, or costs more than the decision is worth, that is a reason to stop or to decide on judgement.

Set criteria before you test

The single most useful discipline is to write the decision rule before seeing the results. For each gate, record:

  1. The decision at stake. What commitment depends on this gate?
  2. The key assumptions tested. Which ones, and in what order?
  3. The evidence that would support them. For instance, a number of customers committing at a stated price, or a technical measure reaching a defined threshold in realistic conditions.
  4. The evidence that would weaken them.
  5. The decision for each result. Proceed, revise or stop, and what each would mean.
  6. The decision-maker and the date.

The capability page frames these as evidence criteria and a validation plan, and its deliverables include a decision brief outlining options and next experiments.

A decision grid

A simple grid keeps the discussion grounded.

Rows for a decision review

  • →Feasibility. Question: does it work in realistic conditions? Score the evidence from 1 to 5, then note what the score rests on.
  • →Desirability. Question: do target users want it, shown by behaviour or commitment? Score the evidence from 1 to 5, then note what the score rests on.
  • →Viability. Question: do the economics work at realistic volumes? Score the evidence from 1 to 5, then note what the score rests on.
  • →Strategic fit. Question: does it fit our capabilities and goals? Score the evidence from 1 to 5, then note what the score rests on.
  • →Cost to continue. Question: what does the next stage cost, and what is at risk? Score the evidence from 1 to 5, then note what the score rests on.
  • →Alternatives. Question: what else could we do with the same resources? Score the evidence from 1 to 5, then note what the score rests on.

Scores are judgements. Their value lies in showing where the evidence is thin and where team members disagree.

Record negative and inconclusive findings

The capability FAQ says a credible process records negative and inconclusive findings as well as positive results. There is a research reason for this. Daniele Fanelli's 2010 study of the scientific literature found large differences between fields in how often papers report positive results. Using a sample of papers across disciplines, he found the odds of a positive result were about five times higher in psychology and psychiatry, and in economics and business, than in space science, and he links this to bias. The lesson for an internal project is that positive results get noticed and negative ones get forgotten, unless the process insists on recording them.

A useful decision log has one line per test: the question, the method, the result, the interpretation, the alternative explanations considered and the decision. It lets a later team avoid repeating a failed test and lets leaders see how the idea changed.

Guard against common traps

  • →Sunk cost. Past spending is not a reason to continue. Ask what the next stage would cost and what you now know.
  • →Moving goalposts. Changing the criteria after seeing results turns a test into a ritual.
  • →Over-reading small samples. Say how many data points you have and how confident you are.
  • →Alternative explanations. If a test succeeded, could something else explain it, such as a friendly sample? The page asks for alternative explanations to be documented alongside findings.
  • →Escalation by default. Each extension should require a fresh decision.
  • →Fear of stopping. Stopping at the right time is a successful outcome, because it frees resources for better ideas.

An illustrative scenario (hypothetical)

Consider a hypothetical company testing a new service model for small clients. Before the pilot, the team writes the criteria: proceed if at least a defined share of pilot clients renew at the proposed price and delivery cost stays under a threshold; revise if clients value the service but delivery cost exceeds the threshold; stop if few clients renew.

The pilot results show strong renewal but delivery cost well above the threshold. The decision is revise: redesign delivery to cut cost and run a second, smaller pilot with defined criteria. The decision log records the result, the alternative explanation that early clients may have been unusually enthusiastic, and the next experiment. This scenario is invented for illustration and does not describe any client.

When an outside view helps

Internal teams often find it hard to make or accept a stop decision. An independent synthesis of the evidence, limitations and options can make the decision easier to take. Lakhlani International's capability includes a synthesis of findings, uncertainties and limitations, and a decision brief. It does not promise that every idea will be taken forward.

If you would like to structure a staged decision, the Research & Innovation capability sets out what an engagement covers. For the preceding steps, the articles on feasibility versus demand and on writing a hypothesis register cover them in turn.

Research & Innovation

A synthesis of findings, uncertainties and limitations, and a decision brief with a proceed, revise or stop recommendation.

Explore the capability

Feasibility is not demand

How to separate the three tests and start with the assumption that is riskiest and cheapest to check.

Read the previous article

Hypothesis register and validation plan

Templates for the research question, the register, evidence criteria and the decision brief.

Read the templates guide

Contact Lakhlani International

For help structuring a staged decision, start with a conversation.

Go to contact

Frequently asked questions

What is a proceed, revise or stop decision?

It is a staged decision made at a defined point, based on evidence against pre-agreed criteria. Proceed means commit to the next stage, revise means change a specific element and test again, and stop means end investment.

How do I set decision criteria for an early-stage idea?

Identify the key assumptions, define what evidence would support or weaken each, and write the thresholds and the decision for each outcome before testing. Record who decides and by when.

What should I do if the results are inconclusive?

Decide whether a narrower, cheaper test could change the decision. If so, run it with clear criteria. If not, or if more evidence costs more than the decision is worth, decide on the available evidence.

Why record negative results?

Because positive results get more attention and negative ones are forgotten. Recording both prevents repeating failed tests, supports better decisions and gives an honest picture of what was learned.

Are technology readiness levels useful outside aerospace?

They can be, as an illustration of staged evidence, but the definitions come from aerospace and need adapting. Use them as inspiration, not as a literal standard.

Is stopping a project a failure?

Not necessarily. If the evidence shows the idea will not work or will not pay back, stopping early protects resources. It is a successful outcome of a well-run process.

References

  • →NASA. Technology Readiness Levels. https://www.nasa.gov/technology/technology-readiness-levels/
  • →Fanelli, D. "Positive" Results Increase Down the Hierarchy of the Sciences. PLOS ONE (2010). https://pmc.ncbi.nlm.nih.gov/articles/PMC2850928
  • →Lakhlani International. Research & Innovation capability page. https://lakhlaniinternational.com/capabilities/research-innovation

Related articles

Research

Preparing for an Applied Research Partnership in India: A Brief Template and What the 2025 RDI Scheme Signals

Mayank N Lakhlani

Indian businesses and founders considering research and innovation work have had a new public policy to watch since mid-2025. This article explains what the Research Development and Innovation Scheme says on its face, what is not yet clear from the public sources reviewed here, and how to prepare a clear brief for any research partnership, whether or not public financing is involved.

Read article→

Research

How to Write a Research Question, Hypothesis Register and Validation Plan

Mayank N Lakhlani

Most research projects that disappoint were never really designed. They started with a topic ("explore the market for this"), collected material and ended with a long document that did not settle anything. The cure is to design the research around a decision before collecting any evidence.

Read article→

Research

Technical Feasibility Is Not Market Demand: Why Promising Ideas Fail When They Are Tested Late

Mayank N Lakhlani

A team spends a year proving that something can be built. The prototype works, the benchmarks are strong and the demo impresses visitors. Then the product reaches customers and the response is polite indifference. Nothing was wrong with the engineering. The question the engineering answered was not the question that decided the outcome.

Read article→

Research

What Is Applied Research and Innovation Consulting? How It Differs from Basic Research and Product Development

Mayank N Lakhlani

Many new ventures start with a strong belief: a technology that should work, a market that should want it, a way of operating that should be cheaper. Belief is a fine place to begin and a poor place to commit large budgets. The gap between "should" and "does" is where applied research earns its keep.

Read article→

Enjoyed this article?

Explore more ideas, research, and perspectives from the Knowledge Hub — or start a conversation with us.