- 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"