Concept Screening: How to Shortlist Product Ideas Before a Full Test
A worked refill-idea matrix shows how to compare rough directions, handle missing evidence and decide what to develop or investigate next.
Concept screening compares rough product ideas so a team can decide which to develop, which need more work and which to set aside. It comes before the effort of turning every idea into a complete offer for a fuller concept test. Imagine a household-products team with three refill ideas and enough development budget for two: a vote for the best-looking sketch could remove a useful direction before anyone understands it.
A useful screen gives each idea a fair description, exposes the assumption most likely to stop it working and assigns a next action. The result might be one candidate to develop, another to investigate and a third to hold. Filling every place on the shortlist isn't the objective. Spending the next part of the budget for a clear reason is.
The shortlist is a decision about the next investment
Ideas arrive at screening meetings in different states. One has an attractive mockup, another is a sentence, and a third depends on a supplier nobody has spoken to. Ranking all three on appeal mixes the value of the idea with its presentation and the work already spent on it.
Agree what the screen can approve before looking at reactions. For example: choose up to two directions for offer development, fund a brief investigation where an important fact is missing, and set aside a route when evidence shows that a critical requirement can't be met. A place on this shortlist approves preparation and investigation. A launch needs a much fuller case.
The decision also needs an owner. Product, research and operations colleagues may see different problems in the same idea. Record who makes the call, what evidence supports it and what would cause the team to reopen it. That makes a hold useful instead of letting it become an idea that quietly disappears.
Give the ideas comparable starting cards
An early card needs enough detail to explain the direction:
- Audience and occasion: who faces the situation, and when?
- Problem and current alternative: what are they trying to do, and what do they use or do now?
- Benefit and mechanism: what would change, and how would the idea deliver it?
- Critical unknown: what must be true for this direction to be worth developing?
Match the amount of detail and visual finish. If the mechanism is missing, leave an explicit gap instead of writing a feature the team hasn't proposed. Keep the differences that define the ideas, too. A mail service and a lobby station require different routines; making their cards artificially identical would hide the choice.
These cards are shorter than the complete descriptions used in a concept study. At this stage, the team needs to see what each direction is and which question deserves attention first.
A concept screening matrix for three refill ideas
Consider a hypothetical team exploring ways for apartment residents to replace cleaning supplies without storing several bulky containers. The cards, constraints and decisions below are illustrative planning inputs, not findings from customers or a Sapien study.
Mail-back refills: concentrated refills arrive by mail, and residents return empty containers in the same package. The proposed benefit is less storage, with a container-return task added to the routine.
Lobby refill station: residents refill their bottles at a station in their building. The proposed benefit is access close to home, dependent on permission to install and maintain the station.
Compact refill pouch: residents buy a small concentrate pouch and mix it in a bottle at home. The proposed benefit is compact storage, with preparation left to the resident.
The matrix makes the team's starting knowledge visible:
Direction | Screening record |
|---|---|
Mail-back | Buyer and occasion: Apartment resident replacing supplies New task for the resident: Return empty containers Critical gap: Viable return process and fit with the resident's routine Decision now: Investigate logistics and the return task |
Lobby station | Buyer and occasion: Apartment resident replacing supplies New task for the resident: Visit the station with a bottle Critical gap: Building access and maintenance responsibility Decision now: Hold development while checking access |
Compact pouch | Buyer and occasion: Apartment resident replacing supplies New task for the resident: Prepare the refill at home Critical gap: Technical safety and usability of preparation Decision now: Prepare the offer, subject to product checks |
The pouch has a defined development task: write the offer and identify the preparation requirements the product team must resolve. The mail-back direction needs a workable return process before its promise is complete. The station needs a building partner and an owner for maintenance. Those are three different assignments, even though all three ideas address the same storage problem.
Suppose a building operator agrees to host and maintain a small station trial. Access is no longer an unanswered assumption, so the station may join the pouch in offer development. If access remains unavailable within the team's trial window, the hold remains. The matrix changes because a specific condition changes, rather than because someone finds a more persuasive headline.
A weighted score can help when several viable directions compete for limited capacity. Define the criteria, weights and meaning of each rating first, then check whether reasonable changes in the weights alter the shortlist. If two candidates are effectively tied, name the unanswered question that would separate them. Safety, required permission and an impossible delivery requirement belong outside that tradeoff: an attractive benefit can't cancel a condition the offer must meet.
A score that changes with the weights needs a closer look
The refill matrix identifies different work for each direction. If the team later uses weighted scoring to choose between viable candidates, keep the original permission, safety and delivery checks outside the score. The station doesn't become ready because an appealing benefit offsets the missing building agreement.
For a later screening round with one development place available, assume the mail-back and pouch directions have cleared the minimum requirements for the next step. The ratings below are invented decision-model inputs, not findings about residents, product safety or logistics. Their purpose is to show whether a shortlist depends on the team's tradeoffs.
Use two criteria with explicit low and high anchors: storage benefit, from no useful reduction to a substantial reduction in the space needed for this task; and routine fit, from an added task residents are unlikely to complete to a task that fits their existing routine. For a real decision, agree the intermediate meanings and evidence behind each rating before scoring. The sum assumes a value scale with consistently interpreted intervals, rather than a simple ranking of good, better and best. Don't give a blank source an arbitrary middle rating.
Direction | Storage-benefit rating, 0–5 | Routine-fit rating, 0–5 |
|---|---|---|
Mail-back | 4 | 2 |
Compact pouch | 3 | 4 |
Suppose the agreed value tradeoff assigns 60% of the weight to the defined storage-benefit range and 40% to the routine-fit range. Mail-back scores (4 × 0.60) + (2 × 0.40) = 3.2. The pouch scores (3 × 0.60) + (4 × 0.40) = 3.4.
Now check an alternative preference: 80% storage benefit and 20% routine fit. Mail-back scores 3.6 and the pouch 3.2. The ordering reverses. The underlying ratings haven't changed; the importance assigned to moving across each defined range has.
Weights should reflect those ranges, rather than colleagues voting on which criterion name sounds most important. The Government Analysis Function's MCDA guide explains swing weighting and sensitivity checks. Its approach asks decision-makers to value the move from worst to best on each criterion, with those extremes defined. This example uses assumed weights to demonstrate the calculation, not a completed stakeholder exercise.
The reversal identifies the next conversation. If the team has a settled business reason to prioritize storage over routine fit, document it. If the tradeoff remains disputed, don't announce a robust winner from the first set of weights. Check the preference and the uncertain ratings before allocating the development place.
The practical evidence request might be to understand whether returning containers fits residents' routines, or whether either direction actually reduces the storage burden being targeted. Give that work an owner and a limit. A full quantitative concept study isn't automatically the cheapest way to resolve an early operational uncertainty.
Keep the initial ratings, sources, weight ranges, changed ordering and final reason beside the shortlist. Where the decision flips under credible assumptions, report it as sensitive. Where a mandatory condition is still unresolved, leave the direction on hold regardless of its calculated total. The score organizes a tradeoff; the record explains why the business should spend its next effort.
A confusing card and an unsuitable idea need different repairs
Someone reading “automatic refills for your building” might imagine a subscription, a staffed delivery or a machine. If the team means a self-service station, the reaction may concern an offer it never intended. Ask what the reader thinks they would receive and what they would need to do before explaining the card. A material misunderstanding calls for a clearer version and another check.
A clear description can reveal a different problem. A resident may understand the station perfectly and already have an easy refill option on the way to work. More explanation won't create a reason to switch. The team needs to investigate the occasion, audience or benefit. If the return operation proves unworkable within the business's constraints, it may be time to stop that route rather than collect more favorable reactions to it.
Missing evidence needs its own label. No agreement with a building operator is different from a refusal; no customer research is different from evidence that customers reject the idea. Keep the unknown visible so the next assignment addresses it.
The evidence should answer the blocking question
Not every uncertainty needs a full concept study. GOV.UK's alpha guidance describes using just enough of a prototype to investigate the riskiest assumptions. It also points teams toward the people responsible when a solution depends on another service. For the station, conversations with building operators may be more useful initially than a polished customer comparison.
Existing research, support records and purchase information can help describe the current problem. Check their coverage: recent records from current customers may still miss residents who don't buy from the company. Exploratory interviews can help explain routines and confusing language. Observing an appropriate prototype addresses a different question, such as whether someone can complete the proposed task.
Sapien builds simulated audiences from consumer and research information, runs research with them and helps interpret the findings. For an early screen, that can support exploring descriptions, likely objections and differences between intended audiences. Agree the audience, source coverage and alternatives with our team before the study. Our comparisons with human research help you inspect the evidence closest to the task; a simulated explanation isn't an interview with a real resident or a test of the physical refill product.
Keep a compact record for each direction: card version, audience, evidence source and date, important gap, decision, next owner and the observation that would change the call. When sources conflict, retain the disagreement and identify which question remains open. A missing answer shouldn't become a zero in the matrix.
The next test starts with a complete offer
A shortlisted direction is ready for offer development when the team can name the buyer and occasion, explain the benefit and mechanism, identify the current alternative and describe a plausible delivery route. Critical technical or permission checks may still govern whether the team can proceed to a trial.
The fuller test needs the terms a buyer would judge: what they receive, how they use it, where it is available and what it costs. Our product concept statement template shows how to turn a rough direction into that card. Our concept testing guide then connects the complete offer to an audience, research question and next investment.
For the pouch, the product team needs to settle the contents and preparation requirements before people can assess a realistic offer. Product safety and performance need their corresponding checks. The research team can then choose whether it needs an independent reaction to each offer or a choice among alternatives; our concept testing methods guide explains that distinction.
A useful shortlist keeps the next question attached
The strongest output from screening is a set of assignments the development team can act on. Investigate whether the return routine works. Secure a building partner. Resolve the pouch's product requirements. The shortlist then tells the team where to spend its next effort and why, while leaving a clear route back for an idea whose main obstacle can be removed.
If your team has several early directions competing for development time, book a Sapien demo to work through which audience reactions a modeled screen could explore and which feasibility questions your team needs to answer first.
