Leadership requires one methodology across all new initiatives as a stated standard, so the favored approach spreads quickly and proposals that skip it have to justify the exception.
Borderline: whether this move is justified depends on the situation, and only the person in it can judge.
An example
Clients would soon buy digital models of their assets along with design work, the chief executive of an engineering services firm was convinced, and his project teams would not build the skill unless made to. In his first quarter he published a standard: every new initiative above $500,000 would include a digital twin component or a written case for an exception, decided by the investment committee within two weeks. He set up a small central team to help project directors scope the twin. In the first year, the committee approved nine exceptions, including a corrosion-specialist hire in the water group, and published the reasons. By the second year the firm had won three contracts that required digital models, two of them from clients that had never bought from it before.
Why it works
Stating a standard makes the favored approach look better: proposals that use it are fast-tracked and featured as part of the strategy. Skipping it becomes costly, because the proposer must make a written case and stand out as the exception. The standard spreads the methodology faster than persuasion one project at a time, and it builds the organization's skill by repetition. It works when the leader controls budget and approval, the methodology fits most of the work, and the exception process is real enough that a bad fit can escape.
The thinking behind it
Jeffrey Pfeffer Power as structural position, from Power in Organizations (1981): power comes largely from control of resources, information, and the decision process. A leader who sets the rules for approval controls the decision process for every initiative, which is why a standard spreads where persuasion stalls. The same control makes the exception process matter: without it, the standard becomes a gate only the leader can open.
Robert B. Cialdini Commitment and consistency, from Cialdini's Influence (1984): small early commitments make larger later ones easier to obtain. Every proposal that includes the method is a small written commitment to it by its author, and repeated across a firm those commitments build real adoption. The same principle produces a false signal, because compliance written into proposals looks like conviction, so leaders should measure use separately from citation.
When it fits
Leadership teams betting the company's direction on a capability that only spreads through practice fit this move. You need control of the approval process, a methodology that genuinely applies to most of the work, people who can help teams adopt it, and the patience to run an exception process honestly.
How to use it well
Publish the standard: what it covers, the threshold, and how exceptions are decided. A rule people can read is easier to accept than one they discover when a proposal comes back.
- Fund help for teams adopting the method, so compliance does not mean a weaker proposal.
- Run the exception process quickly and publish the reasons for each decision.
- Measure what the method adds, separately from the projects it rides on.
- Narrow the standard where the results show it does not fit.
Count the work the method changed, and ignore how often it is cited.
What it costs and where it backfires
Teams forced to bend sound proposals around the method will resent it, and the work slows wherever the fit is poor. Counting adoption can fool you, because forced citations look like consensus. Stay honest about fit and results. Returning proposals indefinitely without stating the rule, punishing exceptions the process allows, or reporting the method's spread as proof of its value when the add-ons go unused turns a standard into a tax, and the organization ends up worse at its work while looking more aligned.
When it is used on you
Under a mandated method, use the exception process and make your case in writing, with the cost of the add-on and what it would deliver. Where the method fits poorly, say so in specific terms. Tie your proposal to results the leader needs, since results pressure leads patrons to accept work that skipped the method.