Five questions to ask before you commit to a launch

Five questions to ask before you commit to a launch

Five questions to ask before you commit to a launch

Before committing significant launch resource, there are five questions worth answering with something better than internal conviction.

Before committing significant launch resource, there are five questions worth answering with something better than internal conviction.

Date

Date

/

Category

Category

Culture

Culture

/

Writer

Writer

Chris Johns

Chris Johns

Most organisations have a stage-gate process. A structured sequence of reviews designed to ensure that only viable concepts progress, and that resources are committed only when the evidence supports it.

Most organisations also find, in practice, that stage-gates are better at slowing things down than at stopping the wrong things. Concepts with powerful internal champions tend to pass. Concepts with weaker advocates tend to stall. The process filters for organisational momentum as much as commercial potential.

This is not an argument against structured process. It's an argument for the quality of the evidence that feeds into it. Stage-gates work when the inputs are good. They struggle when the inputs are ambiguous — which is most of the time.

Before committing significant launch resource, there are five questions worth answering with something better than internal conviction.

1. At what point in our process do we generate evidence of actual purchase behaviour?

Not intention. Not preference. Behaviour. If the honest answer is "at launch," the question is whether there's a way to move that evidence earlier — before the production run, before the retailer conversation, before the commitment is irreversible.

2. What would it take to stop this concept?

If the answer is genuinely unclear — if no plausible research output would cause the team to recommend stopping — the process is designed to validate, not to test. Those are different things, and they produce different results.

3. Is the concept that's progressing the most commercially promising, or the most internally supported?

These are not always the same. In organisations without strong external evidence, they diverge more than anyone is comfortable admitting. The question is whether you have data clear enough to tell the difference.

4. Which version of the product story makes consumers act, rather than just agree?

Internal teams optimise for the proposition they believe in. Consumers respond to the thing that solves a problem they actually have. These often diverge. Knowing which version of the truth about your product actually moves people requires testing it — not asking about it.

5. If this launch underperforms, what will the postmortem say?

It will almost certainly not say "the research didn't support it." It will say "distribution," "timing," "category headwinds." The question is whether, before the launch, you have evidence robust enough to make those explanations implausible — or whether you're relying on the hope that they won't be needed.

These questions don't require a particular research methodology or a specific tool. They require a willingness to seek genuinely disconfirming evidence before the commitment is made.

The organisations that do that consistently don't launch fewer products. They launch better ones.