Spes was the Roman goddess of hope, and Rome honored her with several temples. The Romans drew a clear line between Spes and Fides, the goddess of good faith. Fides was a quality that lived inside a person, so you could practice it. Spes came from outside, from the gods. You could welcome hope, but you could not train it or hold it accountable.
Hope sometimes shows up at the decision Gate looking like a plan: a forecast built on a handful of enthusiastic interviews, or a beta site that confirmed what the team already believed (confirmation bias). Hope is not a strategy (yes, a well-worn phrase, but stick with me), and the Gate review is where that difference should surface.
Stage-Gate® was designed to replace aspiration with an orderly way to develop and bring new products to market. In many new product development (NPD) processes, most decision Gates check whether the Product Manager's (PM's) and R&D's deliverables exist, not whether anyone tried to prove the information in the deliverables wrong.
Most PMs prepare for a Gate by stacking up evidence that supports their recommendation. The skeptic in the room is rarely moved by more of the same. What moves a skeptic is evidence that answers their objection, gathered from their side of the table. B.R.A.C.E.D. is a set of six thinking lenses that helps the PM find that evidence before the Gate.
Why life science tools teams confuse hope with evidence
Life science tools PM and R&D teams rarely lack data and evidence for a claim. The struggle is deciding which evidence matters, and which assumptions need testing before they harden into requirements or launch claims. In research use only (RUO) markets, the evidence often comes from small buyer populations, well-intentioned key opinion leaders (KOLs) and a few dozen interviews, which makes a reliable pattern hard to find.
When that evidence goes unchallenged, the cost shows up late. A requirement written to satisfy three KOLs, rather than the target market, becomes a claim the field team cannot support, or a feature that adds months to development.
The Gate checklist will not catch an untested assumption, because every deliverable is present. The PM catches it by asking the skeptic's questions before the skeptic does. That is the job of B.R.A.C.E.D.
B.R.A.C.E.D.: six thinking lenses for any decision Gate
I developed B.R.A.C.E.D. to make that kind of thinking explicit. It works inside the Stage-Gate® process and names six thinking lenses a PM applies to pressure test the evidence and recommendation for any decision Gate. It also differs from a premortem (Klein, 2007), where the team imagines the project has already failed and lists the reasons why. A premortem is usually a single session. B.R.A.C.E.D. asks six specific questions, from different perspectives, at every Gate, while the answers can still change the plan.
Each lens looks at the recommendation from a different angle and comes with the question it asks.
| Letter | Thinking lens | The question it asks |
|---|---|---|
| B | Boundary Testing | Where does this claim or decision stop being true? |
| R | Reversal from Stakeholder | Who would reject this, and what is their best argument? |
| A | Assumption Surfacing | Which untested assumption matters most? |
| C | Counter-Hypothesis | What else explains what we are seeing? |
| E | Disconfirming Evidence | What would prove us wrong, and have we looked for it? |
| D | Decision with Trade-offs | What are we giving up by choosing this? |
| The Gate check: if you cannot answer two or more of these in one sentence that would hold up in front of the stakeholder from R, pressure test again. | ||
Different Gates call for different lenses
Every Gate has a skeptic, and one or two of the B.R.A.C.E.D. lenses usually matter most. Here is what that looks like at each Gate.
Feasibility Gate. You want to move a spectral flow cytometer concept forward. Its big promise is "easy panel design." Your R&D lead asks: easy for whom? Use Assumption Surfacing. Find out who actually designs the panels. If it is a core facility specialist, not a graduate student, bring that answer and define "easy" for that user.
Development Gate. You want approval to develop a qPCR master mix that completes a run in 40 minutes instead of 90. Your VP of Sales says customers are happy with the current one. Use Reversal from Stakeholder. The VP is hearing from the customers who stayed. The answer to the objection sits with the ones who left: the deals your sales team logged as lost to a competitor's faster mix.
Launch Gate. You want to launch a sequencing library prep kit that claims to work with very small amounts of starting DNA. Your head of Field Applications expects customers to use even less than you tested. Use Disconfirming Evidence. Ask what result would prove the claim wrong: failed libraries at the smallest amounts customers are likely to use. Test those amounts before launch. If the kit fails, change the claim before the datasheet goes to print.
Lifecycle management. Sales wants a price cut on an ELISA kit because "we keep losing on price." Your finance director asks why margin should drop. Use Counter-Hypothesis. Read the notes in the CRM on lost deals and ask what else explains the losses. If customers were missing validation data for their sample type, bring that. The gap was in what they get compared with the next-best alternative, so a price cut would not have won those deals.
In each case, the skeptic hears an answer to their own objection, built from their side of the table.
Honor Spes, then bring the evidence
You can welcome hope, but you cannot hold it accountable at a Gate; however, you can hold your evidence accountable. The B.R.A.C.E.D. thinking lenses give you evidence from the skeptic's side of the table, so the recommendation stands up when someone pushes on it.
Who will be the skeptic at your next Gate, and what evidence will they ask for? Start there.
FAQs
My VP wants a recommendation, not six more questions. How do I use B.R.A.C.E.D. without slowing the decision Gate?
The VP still gets a recommendation. B.R.A.C.E.D. happens while you prepare it, so the meeting itself does not get longer. You also do not need all six lenses at every Gate; pick the two or three that fit the decision. The recommendation then arrives with answers to the objections you expected. In the Development Gate example, the VP of Sales hears the answer to "customers are happy with the current one" before the debate starts.
What if I have no budget to collect disconfirming evidence?
Most disconfirming evidence can be captured on a low budget if you look at the data in your CRM and speak with Sales or Field Applications Scientists. For your win/loss review, call five accounts that chose a competitor. A PM launching a new product can learn more from notes on ten lost deals than from another survey of existing customers.
What if the skeptic at my Gate is my own VP?
Then start with the Reversal from Stakeholder lens, from your VP's seat. Write down the objection you expect, in their words, and decide what evidence would answer it. Share the Disconfirming Evidence threshold with them before the Gate, so the test is one you agreed on together. In the Development Gate example, you could review the lost-deal notes with the VP of Sales before the Gate. If the evidence is shared, so is the conclusion.
