Why Good Decisions Still Fail Under Review
Why Good Decisions Still Fail Under Review
The Problem
A professional follows every rule covered so far in this series. The decision is sound. The ERA record exists: evidence, reasoning, alternatives, all written down close to the moment of decision. The four gaps from Article 02 are closed: timing, memory, audience, language.
And the review still goes badly.
This happens more than most professionals expect, and it causes real confusion, because everything that was supposed to work, worked. The missing piece is not inside the decision-maker's control in the way the earlier steps were. It lies in three structural weaknesses that sit between a well-prepared defence and the person judging it.
These weaknesses are not about preparation. They are about mismatches between how the decision was framed and how the review is conducted. Understanding them in advance is the only way to prepare for them.
Why It Matters
When a well-prepared decision still fails review, professionals often draw the wrong lesson. Some conclude that defence habits do not work, and quietly stop using them. Others conclude that the decision itself must have been flawed, and lose confidence in judgment that was actually sound.
Both conclusions are wrong, and both are costly. The real lesson is narrower and more useful: evidence, reasoning, and alternatives protect a decision from being misunderstood as careless. They do not automatically protect it from three separate structural risks that exist independently of how well the decision was recorded.
Recognising these risks changes how a professional prepares for review. Instead of only strengthening the record of the decision, they also check the record against the specific standard, scope, and outcome framing the reviewer is likely to apply. This second layer of preparation is what the SBO model provides.
Core Framework: The SBO Model
Three structural weaknesses explain most review failures that happen despite good preparation.
Standard Mismatch — the decision-maker applied one standard for what counts as sufficient evidence or sound reasoning; the reviewer applies a different, often unstated, standard.
Boundary Conditions — the decision operated inside real constraints, such as budget, time, or authority limits, that the reviewer does not know about unless they are stated explicitly.
Outcome Anchoring — the reviewer judges the decision by how it turned out, rather than by the quality of the process at the time it was made, especially when the outcome disappointed.
Together, these form the SBO model: Standard, Boundary, Outcome. A well-recorded decision that ignores all three risks still walking into a review unprepared, because the record answers questions the decision-maker expected, not the ones the reviewer actually asks.
Framework Components
1. Standard Mismatch
Every reviewer carries an internal standard for what counts as enough evidence, enough comparison, and sound reasoning. This standard is rarely stated out loud, and it often differs sharply from the standard the decision-maker used.
A researcher may feel that two supporting sources are sufficient for a methodological choice. A supervisor reviewing that choice may expect four. A manager may feel that one structured interview round justifies a hiring decision. A senior leader reviewing that decision may expect a documented second-round comparison. Neither standard is objectively correct. The mismatch itself is the risk.
The only defence against standard mismatch is to ask, before the review happens, what standard the specific reviewer is known to apply, based on past reviews, written guidelines, or direct conversation. Where that standard is unknown, it is safer to over-document slightly than to assume your own standard will be shared.
2. Boundary Conditions
Every real decision happens inside constraints: a fixed budget, a tight deadline, limited authority, incomplete information available at the time. These constraints shape what counts as a reasonable choice, but they are often left unstated, because the decision-maker lived inside them so completely that stating them feels unnecessary.
A reviewer who does not know the boundary conditions will judge the decision against an unconstrained ideal, which is a standard nobody could have met. A hiring decision made under a two-week deadline looks very different from the same decision judged as if six weeks had been available. A budget decision made with authority capped at a fixed limit looks very different from the same decision judged as if unlimited funds existed.
Stating boundary conditions explicitly, as a short, specific list, is not an excuse. It is necessary information the reviewer needs to apply a fair standard.
3. Outcome Anchoring
Outcome anchoring is the tendency to judge the quality of a decision by how it turned out, rather than by the quality of reasoning available at the time it was made. This bias is extremely common, and it affects careful, fair-minded reviewers as much as anyone else.
When an outcome disappoints, a reviewer's attention shifts naturally toward finding fault in the original decision, even when the process was sound and the disappointing result came from a factor nobody could have predicted. Left unaddressed, this bias punishes good process whenever luck runs unfavourably.
The defence against outcome anchoring is to separate process and outcome explicitly in the record itself, stating clearly what was known and controllable at the time of the decision, and naming the specific external factor that affected the outcome afterward. This does not guarantee a fair hearing, but it gives the reviewer the information needed to judge process and outcome as two different things.
Practical Application
Consider a project manager who selects a lower-cost vendor over a more established one, based on a reasonable evaluation of quotes, references, and delivery timelines. The vendor later underperforms on one deliverable, for reasons unrelated to the original evaluation, such as a shortage affecting an unrelated supplier.
Without SBO preparation, the review focuses almost entirely on the outcome: "The vendor underperformed, so the choice was wrong." This is outcome anchoring, and without a prepared defence, it is difficult to resist in the moment.
With SBO preparation, the manager enters the review having already separated process from outcome in the written record: the evaluation criteria used at the time, the boundary condition that only three vendors met the budget ceiling, and the specific external factor, unrelated to the original evaluation, that caused the later underperformance. The manager has also checked, in advance, what standard of evidence this particular review committee typically expects, and matched the record to it.
The decision and the outcome have not changed. The preparation against standard mismatch, missing boundary conditions, and outcome anchoring has changed the entire character of the review conversation.
The same pattern applies to academic supervisors reviewing a change in research direction, funding panels reviewing a resource allocation choice, and admissions committees reviewing a subject or institution choice that did not produce the expected result. In each case, the decision can be excellent, the ERA record can be complete, and the review can still go badly, unless standard, boundary, and outcome are addressed directly.
Terminology
Standard Mismatch — a difference between the evidence standard used by the decision-maker and the standard applied by the reviewer.
Boundary Conditions — the real constraints, such as budget, time, or authority, that shaped what counted as a reasonable choice at the time.
Outcome Anchoring — the tendency to judge a decision by its result rather than by the quality of the process at the time it was made.
Review Standard — the specific, often unstated, threshold of evidence and comparison a given reviewer expects.
Process-Outcome Separation — the explicit practice of distinguishing what was controllable at decision time from what happened afterward due to external factors.
Template
Review Readiness Check
Decision: [state the decision in one sentence]
Likely reviewer: [who will review this, and what standard have they applied before?]
Standard check: [does your evidence meet that known standard? If unknown, document generously]
Boundary conditions: [list the real constraints that shaped this decision: budget, time, authority, information available]
Outcome separation: [state what was controllable at decision time, and name any external factor that affected the result afterward]
Checklist
☐ Have you identified the standard this specific reviewer is likely to apply?
☐ Have you listed the real constraints you were working under, not left them implied?
☐ Have you separated what was controllable at decision time from what happened afterward?
☐ Have you named any external factor that affected the outcome, without using it as an excuse?
☐ If the outcome was disappointing, have you prepared to discuss process and outcome as two separate questions?
FAQ
Is naming boundary conditions the same as making excuses?
No. An excuse is offered after a problem to avoid responsibility. A boundary condition is stated as context the reviewer needs to apply a fair standard, regardless of outcome.
How do I find out what standard a reviewer applies if it has never been written down?
Look at past reviews of similar decisions, ask a colleague who has been reviewed by the same person, or ask the reviewer directly what they expect to see.
What if the outcome really was caused by a mistake in my decision?
Then the honest response is to say so clearly. SBO is not a tool for avoiding accountability; it is a tool for making sure good process is not punished for bad luck.
Does this replace the ERA model from Article 01?
No. ERA builds the content of the decision record. SBO prepares that record against the specific risks a review introduces.
Can outcome anchoring work in your favour?
Yes. A good outcome from a weak process can be praised unfairly. Naming process and outcome separately protects against both directions of this bias.
Related Topics
What Makes a Professional Decision Defensible?
The Difference Between Making a Decision and Defending One
The Evidence Gap Behind Weak Professional Decisions
How to Separate Facts, Assumptions and Judgments
Continue Next Week
Next week's article looks closely at the evidence layer itself, examining the specific gap between the evidence professionals believe they have and the evidence that actually survives review.
About the Author
Nabal Kishore Pande
Independent Researcher & Author | Abroad & Ahead
Researcher and author working across decision systems, research frameworks, execution intelligence, scholarship preparation intelligence, and global career mobility.
He develops evidence-based frameworks, reusable research systems, and practical decision models that turn complex information into structured action. His published work covers scholarship funding, educational access, decision governance, research production, professional portability, and international career mobility.
Research Identity
ORCID: 0009-0007-3325-9966
Connect & Explore
LinkedIn: linkedin.com/in/nabal-kishore-pande-05400b372
Leanpub: leanpub.com/u/nabalkishorepande
ScienceOpen: scienceopen.com/user/nabal-kishore-pande
Comments
Post a Comment