DORA 2025, Part 5. 7 DORA AI Capabilities: How Technical and Cultural Practices Strengthen AI Impact in Software Engineering

7 DORA AI capabilities: technical and cultural practices that help companies increase AI value in software development.

  • This chapter was prepared with the participation of
  • DORA AI Capabilities Model
  • AI capabilities
  • A clear and open company stance on AI use

About the Article and Authors

5.12.2025 This publication is an adapted translation of the "2025 State of AI-Assisted Software Development" report by Google Cloud and DORA. The original is available via the link. Reading time: 13 min. This chapter was prepared with contributions from: Kevin M. Storer, Ph.D. - user experience researcher, Google Cloud Derek DeBellis - quantitative user experience researcher, Google Cloud Nathen Harvey - DORA lead, Google Cloud

DORA AI Capabilities Model

  1. DORA has always aimed not only to describe the state of software delivery, but also to help organizations make data-driven decisions, especially in a rapidly changing environment of tools, practices, and technologies. AI is already transforming development dramatically.

  2. Rapid progress opens up new opportunities, but it also raises questions about how engineering practice should evolve to match the new conditions. This year, we went beyond simply analyzing who uses AI and how.

  3. We studied the conditions under which teams using AI achieve better results.

  4. The result is the first version of the DORA AI capabilities model.

  5. It includes seven organizational capabilities that increase the benefits of AI adoption.

  6. These capabilities cover both technical and cultural aspects.

  7. Our data show that systematic investment in these areas helps unlock the real potential of AI tools.

  8. As with the DORA Core Model, work on the AI model will continue.

  9. We will keep testing, refining, and expanding it with new research - and share updates with the DORA community.

7 AI capabilities: model overview

To build the model, the DORA team proposed a broad set of organizational capabilities that can amplify the impact of AI adoption. The foundation was 78 in-depth interviews, expert assessments, and previous DORA research. After discussion and prioritization, 15 candidate capabilities were included in the survey. Seven of them showed a sustained and statistically significant interaction with AI use.

When teams combined these capabilities with active AI use, AI's impact on key outcomes increased significantly. These seven capabilities became the core of the new model:

A clear and open company stance on AI use

Healthy data ecosystem

Internal data available for AI

Mature version control practices

Strong internal platforms

A clear and open company stance on AI use

- clear guidance for employees on how and under what conditions they can use AI tools at work.

This capability is built on four elements.

They reflect how employees perceive:

How expected and supported AI use is in their workplace.

How much the organization encourages AI experimentation.

How clear it is which AI tools are allowed.

How much the company's AI policy applies to their work specifically.

An organization with a clear AI stance creates an environment where: developers understand that using AI is normal and an expected part of the job; AI experimentation is supported; AI usage rules are transparent; and employees know which tools they can use and how company policy applies to their work.

This approach reduces uncertainty and helps use AI safely and effectively.

Our analysis shows that the positive effects of AI adoption increase only in organizations with a clear and transparent stance on AI use.

When such a position exists, the following is observed with high confidence:

Individual productivity gains are stronger.

Overall organizational performance gains are stronger.

AI's neutral effect on friction turns positive - the level of obstacles in the work decreases. With somewhat lower but still notable confidence, it is also clear that: AI's positive impact on software delivery speed becomes more pronounced.

Based on the interviews, developers regularly noted that they lacked clarity and understanding of the company's position on AI use.

This leads to two opposing effects:

Some employees act too cautiously and use AI less than they could, fearing they might break the rules.

Some teams apply AI too loosely, using it where it goes beyond acceptable bounds.

Both situations create risks for the organization.

That is why we previously emphasized that a clear and open company stance on AI helps build developer trust, reduces unfounded concerns about data privacy, and accelerates the scaling of AI tools across the organization.

New data confirm that when a company clearly states what is allowed, what is expected, and where the boundaries are, results improve. Importantly, this capability describes not the content of the policy itself, but its clarity and transparency for employees.

Each team and organization can define its own position based on role, industry, and data infrastructure.

But if that position is clearly defined and communicated to developers, the organization gets more value from adoption

AI in the development process. "Why did I not start working with AI earlier? Maybe because I did not understand how colleagues and leadership would see it. No one talked about it. So it did not feel like something I could be punished for. But I also did not understand how much it was encouraged, or whether they wanted us to keep using it. I did not want to do it in secret. We do have an AI policy, but it mostly covers what data can be shared from the standpoint of client confidentiality. Something like that.

I think if we had been more explicitly supported, I would have used AI more often - at least for routine tasks"

Healthy data ecosystem

By a "healthy data ecosystem"

we mean the overall quality of an organization's internal data

In the study, this measure is treated as a single factor across three criteria that reflect employees' perceptions: the quality of internal data sources; the accessibility of that data; and the degree of data fragmentation across teams and systems.

An organization with a healthy data ecosystem is one where data is high quality, accessible, and integrated. With a high degree of confidence, we can say that the positive effect of AI adoption increases in companies where the data ecosystem is mature. In such conditions, AI's impact on performance becomes much stronger.

It is commonly said that the quality of AI models is determined by the quality of the data they are trained on. In this case, the rule also applies at the organizational level: the better the internal data is organized, the more tangible the impact of AI.

If a company invests in building a high-quality, accessible, and unified data ecosystem, it gains a much greater boost in efficiency than from AI adoption alone.

Internal data available for AI

This refers to how well AI tools are connected to the company's internal data and systems.

The measure includes four aspects: employees see that AI tools have access to internal information; AI responses are grounded in context from internal data; developers regularly provide internal data to AI in their prompts; developers use AI to retrieve internal information.

An organization with AI-accessible internal data is an environment where employees understand that AI can see the needed data and can use and process it.

The study shows that the positive effect of AI adoption strengthens when AI has access to internal data. Then AI has a greater impact on individual productivity, and AI improves code quality more strongly. Tools trained on general knowledge already help, but real value emerges when AI can access data that reflects the company's context.

This implies:

  • organizations
  • that connect AI to their internal systems
  • AI delivers more value
  • the more the more
  • those who rely only on the capabilities of foundation models

To achieve a meaningful increase in productivity and quality, buying licenses alone is not enough - access is needed

AI and corporate data

Basically, that makes sense: if AI cannot see a company's data, how useful can it really be? "Many of my clients are not yet ready to use AI effectively. Their data is not even organized: it is scattered across the company, with no common storage standard. And for AI to actually work, a substantial amount of data engineering is needed to turn everything into a form the model can consume. Most companies have not even reached that stage yet"

Assess where AI can deliver impact in your process

Mature version control practices

- the foundation of high-performing engineering teams.

They provide a systematic way to manage changes in code and digital artifacts while preserving predictability and resilience. As the volume and speed of AI-generated code increases, the importance of these practices only grows.

The study shows a clear synergy between frequent commits, thoughtful rollback processes, and AI use: the better a team manages versions, the more AI improves their efficiency and quality. With high confidence, it was established that AI's positive effect strengthens when developers commit code frequently. In such conditions, AI's impact on individual performance grows.

We also found that AI's positive effect depends on how actively the team uses rollback mechanisms.

When teams frequently use rollback or revert, AI's impact on team performance becomes stronger.

A key element of mature version control is psychological safety.

The ability to return to a stable state at any time lets teams experiment more boldly and implement ideas faster. Simple, fast, and painless rollback is not a convenience - it is a requirement for speed and resilience.

At the same time, it is important to note: AI speeds up code creation, but increases the risk of instability.

We assume one reason is the increase in code batch sizes, which are harder to review well. So while rollbacks themselves do not directly reduce instability, their positive effect on AI team performance is likely tied to the ability to quickly undo changes when working with large amounts of code and the risks that come with that.

Working in small iterations

means that the team breaks changes into small, quickly verifiable pieces. In the study, this measure is based on three observations: how many lines of code usually go into the latest change; how many changes are bundled into one release; how much time a developer spends completing one task. A team that works in small iterations changes fewer lines of code at a time, combines fewer changes into one release, and completes tasks faster.

With high confidence, it is clear that the positive effect of AI use is stronger when a team works in small iterations. In such teams, AI's impact on product quality increases; AI's neutral effect on friction turns into a reduction in that friction.

There is also a downside: the individual productivity gain from AI decreases slightly if the team already works in small batches.

But overall, working in small iterations has a net positive effect.

This confirms the key point: AI increases the sense of personal productivity mainly by rapidly generating large amounts of code. And working in small iterations improves product quality and reduces friction, outweighing any possible small drop in individual gains.

Focus on users

shows how much the team takes into account the experience and needs of the product's end users.

This measure is built on three judgments: the team aims to create value for users; prioritizes their experience; and understands that business success depends on user satisfaction.

Teams with a strong user focus gain more value from using AI. In these teams, AI's positive impact on efficiency and performance becomes much stronger. Where that orientation is missing, AI's effect turns negative - the team performs worse.

The study emphasizes that a deep understanding of users, their goals, and their feedback amplifies the impact of

AI forms a unified product strategy and prevents risks. Without this approach, AI does not help the team - it can harm it. "That is why I have been here for five years - I feel like I am doing something truly meaningful and helping ordinary people. Even if it were for just one person, that would already mean a lot to me. And here I work for millions.

When I have a hard day or am in a bad mood, the thought that my work matters and that even a small feature will help hundreds of thousands of people this year really keeps me going and gives me the strength to continue."

"The real insight was that clinicians did not need new tools - they needed less noise. We thought value would come from giving doctors more advanced capabilities. The opposite turned out to be true: simplicity and unobtrusiveness became the main innovations. The hybrid AI + human model delivers higher accuracy, more empathy, and more trust than a fully automated approach" - IKS Health

Strong internal platforms

  1. Internal platforms refer to a set of shared capabilities available to different products and services within the company.

  2. Their job is to make these capabilities consistent and available across the organization.

  3. We assess internal platform quality using a single index: respondents indicate how many of 12 key characteristics their company's platform has. With a high degree of confidence, the data show that AI's impact on outcomes depends on internal platform quality. In companies with strong internal platforms, AI's positive effect on organizational effectiveness is amplified.

  4. There is a downside as well: AI's neutral effect on friction can turn negative - people feel more obstacles when working in organizations with strong platforms.

  5. However, the overall picture remains positive.

  6. High-quality platforms improve individual effectiveness through a consistent capability standard, while also setting boundaries - for example, by restricting tool usage through internal APIs with stricter security requirements.

  7. These platforms simultaneously expand access to the right tools and restrict access to undesirable ones.

  8. Until the industry develops a common set of best practices for AI tools, we assume that strong platforms most often play a protective role: preventing improper AI use.

  9. This may increase subjective friction for active AI users, but it does not necessarily worsen the organization's position. With that in mind, we believe that designing and maintaining high-quality internal platforms is a key capability for companies that want to successfully build software in an environment where AI is integrated into workflows.

Practical application of the DORA AI Capabilities model

To achieve real returns from AI in development, simply introducing new tools is not enough. The chapter's findings show that the greatest effect comes from a combination of technical and cultural conditions that the organization must deliberately build.

Practical recommendations based on DORA AI Capabilities

Clarify and communicate your AI policy Unclear AI usage rules reduce trust and slow adoption. Define the allowed use cases, tools, and limitations - and communicate them to teams. This will create a sense of safety, reduce friction, and increase AI's impact on efficiency and results.

Reduce task size. AI helps generate large amounts of code quickly, but task size matters more than speed. Working in small iterations improves product quality and reduces friction in AI teams.

Treat data as a strategic asset AI's impact increases sharply when the internal data ecosystem is healthy: data is high quality, accessible, and integrated. The better AI can use internal data, the greater its value to the business.

Connect AI to the company context AI tools should have access to internal documents, the codebase, and other data. This requires more than licenses - it requires integrations and engineering effort. Company-specific context makes AI noticeably more useful.

Build AI "safety nets" AI increases the volume and speed of change, which raises the risk of instability. Version control practices are your main protection mechanism. Build a culture of frequent commits, rollbacks, and experiments - this directly improves team performance.

Build your product strategy around the user. AI can increase individual productivity, but without a user focus the team can head in the wrong direction. Strong user orientation amplifies AI's positive impact and protects the team from mistakes in choosing goals.

Invest in internal platforms A strong internal platform amplifies AI's impact on organizational outcomes: it sets standards, provides consistent capabilities, and helps scale AI safely and consistently. To see how a platform becomes a foundation for productivity, resilience, and AI adoption - and why platform quality determines an organization's growth ceiling - move on to the sixth part of the study.

It explains how internal platforms have evolved from a set of tools into a strategic layer that shapes the developer experience, manages risk, and unlocks the value of next-generation technologies.

Discuss the article: DORA 2025, Part 5. 7 AI capabilities...

Send via: