An architect must get several teams to adopt a shared approach and has no authority over any of them. What actually works?

What works

• Make the desired path the easiest path. A template producing a compliant, observable, deployable service is adopted because it is fastest. This is the single most effective mechanism available and it requires no authority at all — it changes what the easiest behaviour is rather than trying to change behaviour.
• Solve a problem the team already has. Adoption follows value, and a proposal that makes someone's week easier does not need persuasion.
• Go first, with one team, and produce evidence. A working example with a measurable outcome is more persuasive than any document, and it converts the argument from "should we" to "should we do what they did".
• Talk to the people whose objection would block it, before circulating anything. Most objections are predictable, and one raised privately and incorporated makes the objector a contributor while the same objection raised publicly makes them an opponent.
• Give credit away. An architect who is seen to be building their own influence is resisted; one who makes other teams successful is invited in.

What does not work

• Mandates without the means. A standard with no paved road is an aspiration, and teams will diverge reasonably because they need to ship.
• Escalation as a first move, which wins the instance and loses the relationship — after which every subsequent conversation is adversarial.
• Being right in a document. Correctness is necessary and nowhere near sufficient.
• Volume of communication. Repeating a position more often does not change a team's incentives.

The asset being spent

Credibility, which is finite and is earned by being right about things that mattered and by being useful. An architect who has helped teams solve real problems has credit to spend on the occasions when they need to say no; one who has only issued opinions does not.

Spend it on the small number of decisions where inconsistency genuinely matters — identity, data classification, the audit record, integration contracts — and devolve the rest visibly, which itself builds the credit.

The uncomfortable truth

Persistent bypass is a product signal, not a compliance failure. When teams route around a shared approach, it is slower, harder or less capable than the alternative for their case — and the response that works is to fix that, not to escalate.