You already know: strategy and portfolios (Technical leadership); decision-making and TCO (Engineering judgment); design docs and decision records (Technical writing); gateways, eval pipelines and platform components (D10, D17).
Why this matters for Atlas. The largest wins at staff level come from changes that many teams must adopt: a shared platform, a common standard, a migration off an old system. These fail far more often from adoption than from technology: the platform is fine but nobody moves to it, or 80% migrate and the last 20% linger forever, so the organization pays for both. This lesson covers how to build influence without authority, when a platform pays off, how to drive adoption, and how to run migrations to completion.
1. Influence without authority
The question. How do you get teams that don't report to you to change what they do?
Start from nothing. Influence comes from credibility (a track record of good calls and hands-on understanding), relationships (knowing each team's goals and pressures before you need something), and alignment (framing the change in terms of their goals, not yours). Practical moves: talk to each affected team individually before any big meeting (no surprises); find the team with the most pain and make them the first, successful adopter; make the right path the easy path (templates, migration scripts, docs); and get explicit sponsorship from leadership for organization-wide changes, so priorities can be traded rather than piled on. Track who's affected and where they stand: