Raising a real safety concern through the formal channel, on a project one's own faction opposes, lets the delay that follows do the work an argument could not.
Borderline: whether this move is justified depends on the situation, and only the person in it can judge.
An example
The fab manager at a semiconductor plant had opposed automating wafer transport between two process bays since the business case first appeared, because it moved headcount out of his area, and he had lost the argument on cost. Three weeks before the capital window closed, his process engineers walked the vendor's transport design and found a real pinch point near the bay doors. The fab manager filed it through the formal hazard process, with photographs and the relevant standard, and asked for the mandatory engineering review. The review took twelve weeks and confirmed the hazard. The vendor redesigned the guard, the project missed the window, and the next year's capital round reopened the cost case with the fab manager's revised staffing numbers on the table.
Why it works
Documented safety concerns make accepting delay easier, because nobody can be punished for responding to one. It makes the project look worse, since its returns are framed as ordinary and economic while the hazard is framed as a matter of injury. And it makes pressing forward costlier, because overruling the concern creates a written record that will be dug up if anything ever goes wrong. It works best in regulated industries and cultures shaped by past incidents, when the hazard is specific and the return contested, and when the person raising it is credible on safety. It weakens each time the same person flags only projects they oppose.
The thinking behind it
Jonathan Baron Omission and Commission in Judgment and Choice (1991) describes omission bias: people judge harm caused by failing to act as less bad than the same harm caused by acting. A sponsor who overrules a safety flag acts, and any later injury is that sponsor's commission. Pausing the project is an omission, so delay feels safer to everyone, which is why a documented safety concern stops projects that a cost argument could not.
George A. Akerlof The Market for "Lemons": Quality Uncertainty and the Market Mechanism (1970) shows that when one side knows the true quality and the other cannot tell, the uninformed side discounts every claim, honest ones included. Decision-makers who cannot judge a hazard themselves must trust the person raising it. Flags that land only on opponents' projects teach them to discount all of that person's flags, and that is the price of flagging selectively.
When it fits
Projects you oppose that carry a real, specific hazard, in an organization with formal safety governance. You need the expertise or the people to document the hazard properly, a record of taking safety seriously on every project, and acceptance that the review may clear the project.
How to use it well
Verify the hazard first. Have qualified people inspect it and document it against the relevant standard.
- File it through the formal channel, never through a side conversation or a meeting ambush.
- Ask for the review the process requires, and nothing beyond it.
- Raise real hazards on projects you support too. A record of flagging only your opponents' work destroys your credibility.
- Accept the review's finding, including a finding that the risk is minor.
Use the time the review buys to make your substantive case, with numbers, for when the project comes back.
What it costs and where it backfires
Your credibility as a safety voice is the asset you are spending. Flags that land only on projects your faction opposes start to look political, and once that pattern is named your real concerns will be discounted too, which is a safety cost for everyone. The move stays legitimate only while the hazard is real and stated at its true size. Inventing a hazard, overstating one, or timing a flag to block work while hiding that you accept the same risk elsewhere falsifies the safety record.
When it is used on you
Route your projects through safety governance from the start and document the hazard review early. Fix real issues quickly and in writing, avoid arguing in public that a concern is overblown, and keep a factual log of who raises flags on which projects.