> There's no mandated organizational standard for what exact tools to some, various teams have different levels of adoption and stacks > No org-wide/team-wide

> There's no mandated organizational standard for what exact tools to some, various teams have different levels of adoption and stacks > No org-wide/team-wide conventions for Claude Code Just for context, this pattern (different teams using different tools in different ways) is extremely normal within Amazon, and is intentional. These shouldn't necessarily be seen as a failure. Amazon likes to have multiple competing options they use for everything, and they constantly evaluate which option is best performing, like an A/B test. After a couple years they will pare away whatever performs worst, replacing it with a new option. This strategy definitely has it's disadvantages, but it is an intentional chosen pattern throughout the company. Source: I worked there for 5 years, and painfully/tearfully remember the transitions chime -> slack -> teams and workdocs -> quip -> confluence :')