An architect must change how several teams build without the authority to direct them. What works?

What works

1. Make the desired path the easiest path. A service template, a shared library, a paved road that is faster than the alternative. Teams adopt what saves them time; they route around what costs them time, regardless of policy. This is by far the highest-leverage intervention available and it requires no authority.

2. Bring evidence, not opinion. An incident, a measurement, a comparison from another team. Engineers argue with opinions and engage with data, and a claim backed by an incident report carries more weight than any amount of seniority.

3. Involve teams in the design. People implement designs they helped shape and resist designs handed to them. Slower in the meeting, far faster in adoption — and the resistance frequently contains information the architect did not have.

4. Solve a problem they have. Arrive with something that helps — a diagnosis, a tool, a working example — rather than a requirement. Credibility earned by usefulness transfers to the next conversation.

5. Find the teams who will go first. A working example inside the organisation is worth more than any external reference, and the second adopter is much easier than the first.

6. Escalate rarely and specifically. Authority used often stops working. Reserved for the small set of genuinely severe, irreversible cases, it retains its force.

What does not work

• Standards documents without tooling, which survive until the first deadline.
• Review as the enforcement mechanism, which becomes a queue that gets routed around.
• Mandates without a migration path, which produce compliance theatre and shadow implementations.
• Being right in public, which wins arguments and loses collaborators.

The uncomfortable truth about adoption

If teams are not adopting the approach, it is losing on a dimension the architect is not measuring — usually onboarding speed, flexibility for a legitimate case, or responsiveness to a needed capability.

The response is to find that dimension, not to escalate. Mandating an approach teams do not want produces compliance and drives the workarounds underground, where they are harder to see and support.