A unit facing a company-wide standard argues its real local differences with evidence, accepts the standard where those differences do not apply, and invites comparison on everything else.
Borderline: whether this move is justified depends on the situation, and only the person in it can judge.
An example
A family-owned food-service distributor had bought a competitor whose warehouses picked orders 30 percent faster with zone picking, and the new vice president of supply chain wanted the method in all six of the parent's warehouses. The northern region's manager believed two of his constraints would break it: rural routes averaging eleven stops per truck against a company average of thirty, and a building whose racking could not be reconfigured without a $2 million retrofit. He wrote a two-page list of the requirements the method failed to meet, with route data and an engineer's estimate, and proposed adopting zone picking in his main building's dry-goods section, where neither constraint applied. The vice president visited, accepted the point on racking, and disputed the routes. They agreed a three-month pilot measured on picks per hour.
Why it works
Showing real local differences makes keeping the local practice look better where it fits, and makes defending it cheaper, because the case rests on evidence. The standard's benefits are shown to miss the specific conditions, and imposing it there becomes costlier, since the sponsor must answer documented requirements. Inviting comparison on the rest keeps the argument credible. Genuine, measurable differences, a sponsor without local operating knowledge, and a unit that can show what would go wrong give it strength; uniqueness that cannot be written down gives it none.
The thinking behind it
Oliver E. Williamson Oliver Williamson's The Economic Institutions of Capitalism (1985) describes asset specificity: investments specialized to a particular setting lose value outside it, such as knowledge of one firm's systems or customers. A warehouse built around rural routes and fixed racking has specific assets, which is why a standard designed elsewhere can cost more there. Williamson also explains the sponsor's suspicion, since claims about specificity are easy to make and hard to check.
William Samuelson Status Quo Bias in Decision Making (1988), by William Samuelson and Richard Zeckhauser, found that options framed as the status quo were chosen disproportionately often, partly because of transition costs. A unit defending its practice starts with that advantage. Writing the requirements down and accepting a pilot is how the defender shows the case rests on evidence, and how a sponsor tests whether it does.
When it fits
Consider it when a standard is coming that you believe would damage results in your unit, the reasons are specific to your conditions, and you can document them. It needs data, a willingness to adopt the standard where it does fit, and credibility with the sponsor.
How to use it well
Write the requirements down. A list the sponsor can check beats any claim of being different.
- Attach evidence for each: data, costs, an engineer's estimate, customer commitments.
- Name where the standard does fit, and offer to adopt it there first.
- Propose a bounded pilot with agreed measures and a decision date.
- Invite the sponsor to visit and see the conditions for themselves, ideally on a normal working day.
Accept the result of the comparison. A unit that wins one exception on evidence keeps its credibility for the next.
What it costs and where it backfires
You commit to the evidence: if the pilot shows the standard works, you adopt it. Earlier exceptions make every new one look like a habit, so ask for few. The line is protection dressed as difference. Claiming uniqueness you cannot document, inflating the costs of change, or using local customer or regulator relationships to threaten the sponsor moves from argument into misstatement and threats.
When it is used on you
Ask for the requirements and metrics in writing, before granting any exception, when every benchmark meets 'our situation is different' and no list ever appears. Bring examples of the practice adapted in similar settings, propose a bounded pilot, and grant exceptions only with a sunset date.