.jpg?width=1280&name=PM%20Uncertainty%201920x1024%20(1).jpg)
The Room That Wants Certainty You Cannot Give It
You have been in this position: the phase gate review is two weeks out, and the room you are about to walk into contains at least one stakeholder who will treat every unanswered question as evidence of insufficient preparation. So, you prepare for every question. You run more customer conversations. You pull more market data. You refine the deck until the uncertainty is, if not gone, at least invisible. And somewhere in that process, you stop asking whether you are managing uncertainty well and start asking whether anyone will notice it is there.
That is the wrong question. And it is one of the most common failure modes in the life sciences new product development (NPD) process.
Marketing strategist Mark Schaefer put it clearly at The Uprising, his annual retreat for marketing leaders: “Uncertainty is not a problem. It’s not the flaw. It’s the system.” He was talking about marketing, but the same logic applies with equal force inside a phase gate. Uncertainty is not what your gate review is trying to eliminate. It is the condition your gate review is trying to navigate.
The teams that fail at phase gates are not the ones with too many open questions. They are the ones where the open questions have nowhere to live in the presentation.
Three Types of Uncertainty. Three Different Responses.
Schaefer’s framework, which he built on the work of philosopher Thomas Morris and the poet John Keats, begins with a distinction that most phase gate packages collapse entirely: not all uncertainty is the same kind, and treating it all as one problem is what sends phase gate reviews sideways.
Objective uncertainty is the world as it actually is, independent of what you know or feel. At MS2 for a new HPLC column platform, you do not have long-term column lifetime data under real-world customer conditions, and you are not supposed to. That is not a gap; that is an NPD project timeline.
Schaefer’s prescription: release it. You cannot control it, and holding on to it as a source of anxiety is a choice, not a necessity.
Epistemic uncertainty is what you do not know because you have not asked the right questions yet. A team developing a new automated western blot system for pharma quality control may have strong VOC on throughput and reproducibility and no data at all on how procurement actually works in a regulated GMP environment. The gap is not that the data is unavailable. It is that no one thought to look.
Schaefer’s point here is reassuring: this type of uncertainty resolves itself when you ask the right questions with enough patience to wait for the answer.
Subjective uncertainty is the fog inside you: self-doubt, imposter syndrome, the sense that everyone else in the room knows something you do not.
Schaefer is explicit that this is the one type that is a choice. “Do we succumb to this and wither, or do we embrace it and move on and learn?”
At a gate review, subjective uncertainty is not just something the PM feels. It is something the committee can read in the room, which makes it the type most likely to determine whether a well-evidenced project gets approved or deferred.
The strategic error is treating all three with the same response. Most gate teams respond to objective uncertainty with panic (generating evidence that cannot yet exist), to epistemic uncertainty with avoidance (hoping no one asks the question they have not answered), and to subjective uncertainty with performance (hiding the fog rather than naming it). Schaefer’s three-move framework reverses all three.
Three Moves That Change the Gate Review
Move 1: Reframe the Situation (For Subjective Uncertainty)
The first move is not about changing your data. It is about changing what the review is evaluating. Most gate reviews are implicitly structured around a question the PM did not write: “Has this team proven enough to justify continued investment?” That question puts uncertainty on trial. Reframing replaces it with: “Has this team demonstrated disciplined management of what is knowable at this stage?” That rewards the practice of distinguishing what you know from what you are still finding out, and creates space for objective uncertainty without penalizing the team for having it.
In practice: open your gate package with a one-page uncertainty map before presenting your data. Not as an apology. As a framework. Show the committee what is knowable at MS2, what is not yet knowable until MS3, and where your evidence sits in that structure. You are not hiding the gaps. You are naming them with precision.
Note on terminology: the uncertainty map is not a risk register. A risk register lists threats and mitigations within the known universe of your project. An uncertainty map distinguishes between types of unknown before assigning any response at all. The committee cannot evaluate your mitigation plan for objective uncertainty, because the data does not exist yet. But they can agree that its absence is appropriate for this stage. That agreement is what the uncertainty map makes possible.
Move 2: Follow the Fear (For Epistemic Uncertainty)
The second move is what Schaefer calls the courage dividend: “the good things that happen when you just say, I am afraid and I am going to do it anyway.” And it compounds. Every time you act before you feel ready, the return grows.
There is a neurological basis for this. Research from Stanford’s neuroscience program found that the brain’s fear and courage responses operate through adjacent but distinct circuits: the amygdala processes threat, while the medial prefrontal cortex governs executive function and overrides fear responses when activated. When teams deliberately surface the questions they have been avoiding, they are building the neural wiring that makes the next act of courage easier. (Source: Stanford Medicine, 2018.)
In gate preparation, this is the move almost no team makes. The questions that derail a gate review are almost never the ones already in the risk register. They are the questions the team was quietly hoping no one would ask. This is where a synthetic customer panel earns its place.
A synthetic customer panel is a structured simulation of decision-relevant customer conversations, built from existing VOC data, persona frameworks, and market intelligence. It does not replace primary research. It forces the team to construct the strongest possible objection to their own commercial position before a gate committee does.
A concrete example: at MS2 for a new automated sample preparation system targeting pharma QC labs, the team’s VOC supported strong demand for throughput improvement. When they built the panel around their most resistant buyer persona, a QC lab manager in a regulated GMP environment, one objection surfaced immediately: method revalidation cost. In regulated environments, revalidating an analytical method can run $200K to $500K per method. That finding did not kill the project. It shifted the value proposition from “improve throughput” to “reduce total cost of validation” before the gate, not after it. That is the courage dividend.
A note on field team input: VOC from FASes, sales, and application specialists belongs in your gate package. The synthetic panel is not a replacement; it is the structure that forces the team to turn that field insight into the buyer’s strongest counterargument.
Move 3: Control Your Inputs (For Objective Uncertainty)
The third move is about the quality of evidence you do control. Objective uncertainty, the data that cannot exist yet, gets released. But the data that can exist has a standard entirely within the PM’s authority to raise. At MS2, that means VOC with named personas and documented willingness-to-pay ranges, not directional impressions from field conversations. A competitive analysis that acknowledges where competitors are stronger. A risk register that demonstrates you have already thought harder about failure modes than the committee has.
“Content informs. Questions and uncertainty transform us.” — Mark Schaefer, The Uprising
The discipline of choosing better inputs is not just about this gate package. Each cycle you run this way, the questions get sharper, the evidence structure gets cleaner, and the committee’s experience of your work changes.
The table below maps each uncertainty type to the specific action it calls for at MS2:
Stop Trying to Make Uncertainty Disappear
The gate reviews that stall are almost never the ones with too many open questions. They are the ones where the open questions had nowhere to live in the presentation.
Schaefer’s core argument at The Uprising was that uncertainty is not the enemy of great work. It is the life force of it. Reframe the review, follow the fear, and control your inputs: not as three separate techniques, but as one underlying discipline. Stop treating uncertainty as evidence of unreadiness. Start treating it as the condition that makes good product management possible.
The Romans Already Knew This
Every April 25th, the Romans stopped everything.
Farmers left their fields. The city held its breath. A procession wound out through the Porta Lavernalis to a sacred grove on the Via Claudia, where offerings were made at the shrine of Robigus, the deity of grain blight.
Robigus was not a god you prayed to for good harvests. The Romans had other deities for that. Robigus was the one you honored because blight could not be prevented. It could only be managed. The rust fungus that turned wheat stalks red and hollow was as certain a feature of the agricultural year as planting and rain. The question was never whether it would come. The question was whether you had done enough, with discipline and ritual, to keep it from destroying everything.
No offering guaranteed a perfect harvest. The Romans knew this. The Robigalia was not an act of optimism. It was an act of structured acknowledgment: here is the uncertainty we cannot eliminate; here is the discipline we bring to contain it. The procession ended not with a declaration of victory, but with a return to work.
Product managers have been running their own version of the Robigalia for as long as phase gates have existed. The ceremony is the gate review. The offering is the evidence package. The discipline is the uncertainty map, the synthetic panel, the courage to ask the question you were hoping to avoid.
The Romans did not call Robigus an enemy. They called him a reality. That is the reframe.
Q: How do I present an uncertainty map without looking like I do not have my project under control? ▼
This concern reflects a misread of what experienced gate committees actually evaluate. A reviewer who has been through multiple NPD cycles does not expect certainty at MS2. They expect evidence that the team knows what they do not know. Open your gate package with a single-page uncertainty map that categorizes open items by type (objective, epistemic, subjective) and shows the resolution plan for each. Frame it as: “Here is where we are in the evidence curve, and here is what we will have resolved by the next gate.” That is not vulnerability. That is program management.
Q: Is the uncertainty map just a risk register with a different name? ▼
No, and the distinction is worth explaining to your committee if you introduce the tool. A risk register documents threats and mitigation plans. It lives entirely within the known universe of your project. An uncertainty map asks which type of uncertainty each open item is before assigning any response. Objective uncertainty gets released, not mitigated. Epistemic uncertainty gets a structured question, not a risk response. Subjective uncertainty gets a framing decision, not a data request. A committee that conflates the two is still inside the “certainty performance” frame. The map is the tool that moves them out of it.
Q: What if my synthetic customer panel surfaces a finding that threatens the commercial case?▼
Surface it anyway. The purpose of the panel is to stress-test assumptions before a gate committee does it with higher stakes and less time to respond. If the panel surfaces a real constraint, you have two options: design a primary research sprint to test whether it is real, or reframe the commercial case around what the constraint reveals. The pharma QC example in this post is a good model: the method revalidation cost finding did not kill the project. It reoriented the value proposition. That reframe happened before the gate, not because of it.
Q: How do I handle a gate committee member who interprets any uncertainty as insufficient preparation?▼
Manage that stakeholder before the gate, not during it. Book a thirty-minute pre-read conversation to walk them through your uncertainty map and evidence structure. The goal is not to convince them. It is to give them the language to process your uncertainty framing before they encounter it in a room full of their peers. People who feel surprised by ambiguity become adversarial. People who have been briefed in advance become curious. You cannot control how a committee member thinks about uncertainty. You can control when they first encounter yours.
