Enough Isn't a Compromise: How to Know When a Concept Is Ready for Feasibility

Temperantia was the Roman goddess of moderation, one of four cardinal virtues. She's shown pouring wine and water together, mixing them in a specific ratio. Wine wasn't drunk undiluted in ancient Rome, so the image carried a practical meaning along with a moral one. Too little water and the wine is undrinkable. Too much and the wine is wasted. Her authority sits in knowing exactly where that point is, not in avoiding wine, not in avoiding water, in mixing them correctly.

A new product concept does not need to be fully proven before it moves forward, it needs 'just enough' evidence to hold, and no more. Most project teams in the life sciences tools sector get an idea through selection without much trouble. The struggle starts after, when the Product Manager (PM) has to turn a selected idea into something written down clearly enough for a reviewer to evaluate on its own terms. Too little evidence and the case does not hold together, but too much, and the PM has spent Feasibility-stage effort at a stage that does not need it yet. Both mistakes cost time and money.

The Gap Between Idea and Concept

The instinct is to reach for more formal inputs: a formal customer study, a requirements document, or a business case built on numbers the concept is too young to support. The evidence that helps to close the gap between product idea and concept is direct observation.

Cooper and Edgett's research across idea-generation methods found that ethnography, watching what a customer works around rather than asking what they want, produces the deepest insight into needs a customer hasn't put into words, and remains one of the least used methods, even among PMs who already know how to do it, because it's slower than a survey. That's the insight a concept statement is built on.

The Five-Part Concept Statement

A concept statement has five parts: (I) the target customer, (II) the problem or need, (III) the solution or form, (IV) the key benefit, and (V) the reason to believe. Each part is one sentence, and together the five carry just enough of what was observed to make the case. Here's what the PM's statement could look like for a spatial biology instrument:

1. Target customer: translational research cores and pharma discovery teams profiling tumour microenvironments.

2. Problem, observed directly: at two research cores, scientists were seen cutting a second, unplanned section from an irreplaceable FFPE block to run a proteomic assay after transcriptomic imaging was already complete, risking the block to get both readouts, a workaround nobody had listed as a stated need.

3. Solution: a single bench-top platform that co-registers transcriptomic and proteomic signal from the same tissue section in one imaging cycle.

4. Benefit: preserves precious samples by eliminating the second cut, cuts sample prep from roughly two weeks to three days, and removes the fear of losing an irreplaceable block to get both readouts.

5. Reason to believe: an academic core has already run a pilot showing greater than 90 percent spatial registration accuracy against sequential IHC and ISH.

The target customer, problem, and solution sentences come from what the PM observed directly. The benefit and reason-to-believe sentences are where the temptation to over-prove shows up, because those are the two a reviewer is most likely to test.

The Proof Ceiling

Confirm strategic fit before anything else, and do it with one question: does the target customer and problem already sit inside an arena the portfolio has committed to. If yes, write the concept statement. If no, that's a strategy conversation the PM cannot resolve alone, and no five-part statement resolves it either. A concept can clear every step below and still not move from concept to Feasibility if it fails this question, and no amount of evidence changes that. Once fit is settled, thinking ahead in two areas defines how much evidence the remaining parts actually need.

Highlight the one claim someone in the review meeting will actually challenge. Not every sentence needs defending. Usually, it's the benefit or the reason to believe that is the focus of the reviewer.

Recommend the piece of evidence that takes the least time and effort to get while still answering that specific claim. Not the whole idea, just that one sentence.

Gathering evidence for objections nobody has raised yet doesn't make the concept stronger. It's Feasibility-stage rigor spent before Feasibility exists to fund it, and it slows down the one thing a concept review is supposed to be fast at.

For the spatial biology example, the predictable challenge is whether the co-registration claim holds up outside one lab. The quickest answer to get isn't a multi-site validation study, that's Feasibility work. It's the pilot the academic core already ran, the same one sitting in the reason-to-believe sentence. That's the ceiling. A second site doesn't change the reviewer's decision. It only changes how comfortable the room feels.

For a hardware concept specifically, the ceiling sits lower than reagent or software teams expect. Tooling and manufacturing costs make the wrong kind of proof expensive fast, so the cheapest answer needs to be genuinely cheap, not just quick.

Write It Before It's Needed

Temperantia's mixture didn't need to be undiluted to be right. It needed to be correct for what it was for. A concept statement works the same way.

A concept statement isn't judged on how persuasive it sounds. It's judged on whether the five parts hold up, each with just enough evidence behind it.

The work: name the customer, quantify the benefit, and go see the workaround before writing down the problem it solves.