Review boards apply their full published standard to every proposal, including those that challenge the established roadmap, so challengers clear the same bar the roadmap did.
Borderline: whether this move is justified depends on the situation, and only the person in it can judge.
An example
Grid data was the chief architect's worry. At a regional electric company, the chief architect chaired the review board that approved every technology project, and after a spring storm the customer operations team proposed a self-service outage map that would pull data from the grid systems the board had spent three years stabilizing. The chief architect thought the proposal underestimated the load. The board's published standard required a load model and a cybersecurity assessment for anything touching grid data, and the grid modernization projects had met it. The chief architect asked for both in one written request, with a review date six weeks out. The customer team's load model showed the map would need a separate copy of the data. The board approved a revised design with the copy, and the app launched that winter, four months later than first proposed.
Why it works
Every requirement a gate imposes costs a proposal time and money, so holding a challenger to the full standard makes it costlier and, as its window narrows, worth less. Roadmap work that already meets the standard clears easily by comparison. The gate's authority comes from its procedures being real and applied evenly, so its decisions stick. It works when the board's approval is mandatory, its standard is published, and executives trust its judgment.
The thinking behind it
Oliver E. Williamson Oliver Williamson's Markets and Hierarchies: Analysis and Antitrust Implications (1975) holds that bounded rationality and opportunism expose every arrangement to hazards, and that organizations build safeguards, such as reviews and approvals, against them. A review gate is one such safeguard, and its authority depends on being applied to everyone. Holding a challenger to the published standard draws on that legitimacy, and applying the standard selectively would spend it.
Ronald H. Coase Ronald Coase's The Problem of Social Cost (1960) argues that when reaching agreement is costly, the cost of negotiation, more than the merits, decides what happens. Every requirement a gate imposes adds to the cost of getting a proposal approved. Asking for everything at once, with a date, keeps that cost to what the standard really requires, so a proposal that clears the gate does so on its merits.
When it fits
Gatekeepers whose approval is mandatory, and who believe a challenger's proposal carries risks the established roadmap does not, are the ones placed to use it. It needs a published standard, a record of applying it to everyone, and the technical credibility to defend each requirement.
How to use it well
Apply the published standard, all of it and nothing beyond it.
- Ask for every requirement at once, in writing, so the proposer can plan.
- Give a review date and keep it.
- Explain each requirement in terms of the risk it addresses.
- Publish cycle times for every proposal, the roadmap's included.
When the proposer meets the standard, approve promptly, with conditions if needed. A gate earns the right to be strict by being predictable: the same standard, the same clock, and the same answer for the roadmap's projects and for the challenger's.
What it costs and where it backfires
Strict gates slow good ideas along with bad ones, and teams that feel blocked will look for sponsors who can approve around you. A reputation for blocking innovation sticks to a review board. The clean form ends at selectivity: inventing new requirements for one faction's proposals, re-reviewing what already passed, or applying standards the roadmap was never held to is retaliation dressed as process.
When it is used on you
Find an executive sponsor with budget authority who can approve outside the gate, and collect cycle times for every proposal the gate has reviewed. Push for a fixed clock on reviews, and build momentum outside the gate through a pilot or a customer commitment.