Tell me about convincing teams to adopt an architecture decision

Use the STAR structure.

Situation. Several teams each integrated with a payment provider in their own way, which caused duplicated code and inconsistent error handling. I proposed one shared payments service.

Task. Get the teams to adopt it voluntarily, even though they had to change working code and feared losing control.

Action. I began by interviewing each team about their pain points and constraints. I wrote a short decision record with the problem, options considered, trade-offs and my recommendation, and shared it for comments before any meeting. I built a small prototype with one willing team to prove the value, and made the migration incremental with a clear support path. When a team raised a valid concern about latency, I changed the design.

Result. Four teams migrated within two quarters, and incident counts for payment errors fell.

The lesson: involve people early, show evidence, stay open to feedback, and make adopting the decision easier than ignoring it.