Making Software Health a Habit Across a Huge Engineering Org

At a company Amazon’s size, engineering practices drift. Coding standards, merge habits and CI/CD hygiene varied widely from team to team, which created bottlenecks that slowed delivery and made software quality hard to measure, let alone improve.

The challenge

Help developers and their managers understand what “healthy” looks like, with clear thresholds and best practices, and make better software hygiene a company-wide standard rather than an engineering aspiration.

What I did

• Started with research. I gathered code snippets and BI queries from across the organization to find where team sprints were getting stuck.
• Validated the fixes with the experts. I worked with technical program managers on improvements to merge frequency, code hygiene and CI/CD practices.
• Told real stories. With program managers, content strategists, designers, subject-matter experts and internal communications, I published case studies from teams including Alexa, Devices and pipeline leadership.
• Built a rhythm, not a campaign. A content series and runbook tied into operational health meetings made software health reviews repeatable.
• Supported the shift to AI tools. Webinars and learning sessions helped teams through the transition.
• Drove the change management. I coordinated stakeholders on thresholds, messaging and rollout timing.

What changed

Teams saw fewer blocked pipelines across thousands of CI/CD workflows, saving hundreds of hours of troubleshooting. Deployment frequency and code hygiene improved, and Slack engagement showed developers actively using the program’s content.

What I took away

Standards stick when they show up in the meetings teams already have, backed by stories from teams they recognize.