Google Cloud's DevOps Research and Assessment (DORA) 2025 report, built on survey responses from nearly 5,000 technology professionals and more than 100 hours of interviews, has one line I keep coming back to. AI's primary role in software development is that of an amplifier. It magnifies the strengths of high-performing organizations and the dysfunctions of struggling ones.
That is a different claim from the usual one. It says the tool does not have a fixed effect. A team with clear ownership, fast feedback, and a healthy codebase gets faster. A team with unclear ownership and a slow pipeline gets more of what it already had, faster.
I think that reframes the adoption conversation for managers. The question stops being which tool and becomes which of our existing habits the tool is about to amplify. The report's answer is a set of organizational capabilities, and I read it as a checklist for the organization, not for the editor.
In my view the honest first step before a rollout is to write down what the team already does well and what it quietly tolerates, because both are about to get louder.
What would an amplifier make louder on your team right now?
Photo source: https://photos.robertstowe.com/new-mexico