Your 2027 commercial plans will be approved in the next six weeks. In almost every organization I have watched go through this, nobody in the room will say out loud what would make it wrong.
That omission is not a failure of rigor. The plan will be detailed, the numbers will be defensible, and the people presenting it will have done serious work. The omission is structural, and it has a specific and expensive consequence. This is where revisit triggers come in
Approval is not the hard part
All plans get approved. That is what the process is for. The hard part arrives eight months later, when one of the assumptions underlying the plans turns out to be wrong, and the organization has to decide what to do about it.
At that point a plan with no named failure condition cannot be reversed on evidence. There is no agreed standard against which the new information can be measured, so the conversation becomes a contest between people rather than an assessment of facts.
What happens instead is that the plan gets abandoned on politics; usually, two quarters late. Usually by someone who was not in the original room and therefore carries no institutional cost in walking away from it. And usually after the organization has spent another two quarters of budget executing against an assumption that stopped being true.
The tell that this is happening in your company
Ask when a plan was last formally reversed rather than quietly deprioritized. If nobody can name an instance, your organization does not reverse plans on evidence. It waits for them to become obviously untenable, which is considerably more expensive and takes considerably longer.
What a revisit trigger actually is
One sentence, written into the plan document rather than agreed in the room. If by a named date a named condition has not been met, we stop and rebuild the assumption underneath it.
Three components, and all three matter.
The assumption that carries the most weight
Not every assumption. The one that, if wrong, breaks most of the plan. Everyone on your leadership team already knows which one this is, and if you ask them individually, they will name the same one. It does not get said in the room because challenging it reads as challenging the plan.
The condition that would prove it wrong
Specific and measurable. Not “if adoption is slower than expected” but “if the first two territories have not produced X qualified opportunities by 31 March.” The vaguer version is unfalsifiable, which means it will never fire.
The date, the owner, and where it is written
A named date, a named individual, and a location inside the document itself rather than in a side conversation or a set of minutes. The person who has to act on this in March is frequently not the person who was in the meeting in October. If the trigger only exists in the memory of the room, it does not exist.
Why this is a reversibility problem, not a forecasting problem
The instinct when plans go wrong is to conclude that the forecasting was poor and to invest in better forecasting. That is usually the wrong diagnosis. The forecast was an estimate, and estimates are wrong. What failed was the mechanism for responding to being wrong, which is a different system entirely and considerably cheaper to build. This is the same evidence and reversibility logic that should govern any commercial decision: the question is not how confident you are, but what it costs to change your mind and when that cost rises.
Plans reviewed in March, on a named condition, costs a quarter of misdirected spend. The same plans abandoned in September costs three quarters plus the organizational credibility of whoever was defending it.
The lineage, and why naming it helps
This is not a new idea and presenting it as one would be a mistake. It sits close to the premortem technique developed by Gary Klein, published in Harvard Business Review in 2007, which asks a team to assume the project has already failed and to generate the plausible reasons why. Klein’s point was that prospective hindsight makes it safe for people who have reservations to voice them, because the failure is stipulated rather than predicted.
A revisit trigger is the operational residue of a premortem. The premortem surfaces the reasons the plan might fail. The trigger converts one of them into a written condition with a date attached, so that the insight survives the meeting.
Most organizations that run premortems do not do this second step, which is why the exercise feels valuable in the room and produces nothing three months later.
Running this on a 2027 commercial plan, specifically
Four assumptions are worth checking in almost every MedTech and healthcare commercial plan going into 2027.
That the buyer finds you the way they did last year
Most plans carry an unstated assumption about how buyers discover and evaluate. If a meaningful share of your category’s buying questions are now answered before anyone is contacted, every traffic and lead assumption in the plan inherits that shift. This is written up separately in the piece on plan assumptions and buyer search behaviour.
That the adoption curve resembles the last launch
Launch plans routinely inherit the adoption curve of the previous product in the portfolio, adjusted for optimism. Where the buyer, the workflow, or the reimbursement position differs, that curve is not transferable and nobody has written down that it was borrowed.
That the commercial hires will be productive on schedule
Ramp assumptions are the most consistently optimistic numbers in commercial planning and the least frequently reviewed against actuals. A trigger here is cheap to write and unusually likely to fire.
That the competitive position is stable
Plans are built against a competitive picture that is fixed at the moment of writing. A named condition around a specific competitor action converts a monitoring activity into a decision point.
The objection, and the answer
The predictable objection is that this introduces bureaucracy, or that naming failure conditions signals a lack of confidence to a board.
On bureaucracy: the artifact is three sentences per plan. It is shorter than the agenda of the meeting it sits inside.
On confidence: the opposite is closer to true. A leadership team that can name the condition under which it would change course reads as one that has stress-tested its own thinking. A team that cannot name one reads as a team that has not looked. Boards with any experience of a bad plan recognise the difference immediately, and the ones that do not will recognise it after their next bad plan.
What to do before the plan locks
One. Ask each member of your leadership team privately which assumption would break the most of the plan. Compare the answers. The convergence will be higher than you expect.
Two. Write the trigger for that one assumption. Condition, date, owner. Three sentences.
Three. Put it in the plan document, not the appendix and not the minutes.
Four. Put the trigger on the gate template so that next year naming it is the process rather than an act of dissent. This is the step that makes it survive you.
One assumption, not all of them. Ninety minutes. It is the cheapest reversible decision available to you this quarter and the window closes when the plan locks.
Frequently Asked Questions
What is a revisit trigger?
A revisit trigger is a condition named in advance which, if met, requires a decision or plan to be formally reopened. It has three parts: the assumption carrying the most weight, the specific measurable condition that would prove it wrong, and a named date and owner recorded in the plan document itself.
Why can a plan without a revisit trigger not be reversed?
Because there is no agreed standard against which new information can be measured. The conversation becomes a contest between people rather than an assessment of evidence, so the plan is typically abandoned late and on political grounds rather than reversed on evidence.
How is a revisit trigger different from a premortem?
A premortem surfaces the plausible reasons a plan might fail. A revisit trigger converts one of those reasons into a written condition with a date and an owner, so the insight survives the meeting. Most organizations run the first step and skip the second.
Which assumption should carry the trigger?
The one that, if wrong, breaks the most of the plan. Leadership teams asked individually usually name the same assumption, but it goes unsaid in the room because challenging it reads as challenging the plan.
Does naming a failure condition signal a lack of confidence to a board?
Generally the opposite. A team that can name the condition under which it would change course reads as one that has stress-tested its thinking. A team that cannot name one reads as a team that has not looked.
When should a revisit trigger be written?
Before the plan is approved. Once the plan locks, the trigger becomes an amendment rather than a condition, and amendments require a case that the original decision was wrong, which is a much harder argument to make.
Where should the trigger be recorded?
In the plan document itself, not in an appendix or meeting minutes. The person who has to act on it may not have been in the room, and a trigger that exists only in the memory of a meeting does not exist.
How much time does this add to planning?
Roughly ninety minutes for one assumption. The written artifact is three sentences; shorter than the agenda of the meeting it sits inside.
EXTERNAL CITATIONS
• Gary Klein, Performing a Project Premortem, Harvard Business Review, September 2008