The article recounts a platform team's struggle to impose compliance in a rapidly scaling, multi‑team AWS environment. With 15 teams and roughly 80 engineers, the organization faced mounting operational overhead, compliance chaos, and developer friction as self‑hosted tools and ad‑hoc policies broke deployment pipelines. By migrating to a multi‑account structure with AWS Organizations and replacing custom tooling with native services, the team reduced complexity and improved security.

A phased tagging strategy—starting with visibility via AWS Security Hub, followed by soft enforcement through real‑time Slack notifications, and finally hard enforcement with Service Control Policies—demonstrated how to balance governance with developer productivity. The approach emphasizes informing teams before enforcing rules, using automated detection to surface missing tags, and gradually tightening controls only after teams understand the value. Lessons highlight the importance of clear purpose, empathy, and champion empowerment to turn compliance from a source of friction into a collaborative effort, a model applicable to any internal governance initiative across cloud‑native organizations.