Enthusiasts, Pragmatists, and the Cautious Shape AI Work in Software

Software Developer Archetypes shape AI adoption in the enterprise

Introduction

AI for software development is here, practical, and professionalized. Developers are writing code with it, testing systems with it, and learning how it fits into building applications.

A recent study of 147 professional developers sheds light on how that work is taking shape. The research reveals distinct, stable patterns in how developers use AI, how they perceive its impact on productivity and quality, and how organizational context shapes those experiences. Our research identifies three distinct archetypes that describe how AI use is structured inside teams: Enthusiasts, Pragmatists, and Cautious developers.

Three Developer Archetypes

The three empirically distinct developer archetypes occupy stages in a technology diffusion process. Enthusiasts are similar to early adopters, Pragmatists are the early majorities, while the Cautious are the late majority and some laggards.

Enthusiasts: Proving AI Tools Work

Enthusiasts are the vanguard of AI use in software development and are at the forefront of a broader trend: nearly 75% of all developers surveyed report an improvement in perceived code quality attributable to AI coding tools. They score highest on usage breadth, optimism, strategic outlook, and satisfaction with current code quality. They report strong productivity gains and view the current generation of AI tools as successful. They manifest the “Virtuous Adoption Cycle”: high usage leads to high perceived productivity, which in turn reinforces their belief that AI is actively improving their work.

What most clearly differentiates Enthusiasts is policy support. Nearly 60% report explicit AI coding policies in their organizations—the highest of any group. In these environments, AI use is legitimate, visible, and normalized. Policy functions less as restriction and more as a marker of organizational maturity, formalizing practices that have already demonstrated value.

Significantly, they adopt ahead of endorsement, essentially proving the “proof of concept” for the rest of the company.

Pragmatists: Scaling What Works

The quality-driven Pragmatists represent the critical middle. They are optimistic about AI’s potential but hold it to a high standard. Interestingly, they are often the most discerning about code quality—they use AI to move faster but are among first to point out hallucinations or subpar output. They are responsive to organizational policy and abide by clear rules. This group holds the highest intent to increase AI usage.

Pragmatists are the most consequential group for the future. Their current AI usage is moderate yet they match Enthusiasts in optimism and strategic outlook.

Pragmatists typically operate in environments where AI policy exists but is still evolving. More than a quarter report formal policy support—much more than the Cautious, but well below Enthusiasts. This creates a productive tension: enough legitimacy to engage seriously, enough skepticism to evaluate quality rigorously. 

In terms of the diffusion of innovation, Pragmatists are the early majority and, despite lower policy prevalence than Enthusiasts, report the highest intent to increase usage because AI is diffusing through their organizations. They adopt once success is visible and organizational signals are credible, then drive scale.

Cautious Developers: Lack of Early Adopters Stymies Use

The Cautious group reports the lowest usage. Their concern levels are not meaningfully higher than other groups. 

What stands out instead is policy absence. Only about 5% of Cautious developers report any AI policy support. Yet developers’ intent is determined by frequency of tool use and ease of integration. 

The Cautious remain trapped outside this process. Lacking Enthusiasts (i.e., early-adopter) examples, they don’t see signals that kick start experimentation. They never accumulate the usage frequency that drives intent. Their low adoption is not the cause of their organizations’ policy absence; rather, is a symptom of organizational lethargy in AI adoption.

Thus, organizations seeking to increase adoption should recognize that Policy formalizes maturity that must be won through early-adopter success and demonstrated efficacy. The path to adoption runs through Enthusiasts proving that tools work, organizations responding with governance, and then risk-averse populations recognizing the signal to follow.

In this sense, caution is not an individual disposition. It is an organizational signal.

Developers Surveyed

%

Developers Reporting Improvement in Code Quality

%

Enthusiasts with Policy Support

%

Cautious Developers with Policy Support

Policy Shapes Archetypes

One of the most important insights from the research is how policy actually functions in AI adoption. Our analysis shows that intent is driven by frequency of use and ease of integration. But policy determines who gets the opportunity to build that experience in the first place.

For Enthusiasts, policy marks maturity—codifying success after the fact. For Cautious developers, policy acts as a gate, legitimizing experimentation and lowering perceived risk. This dual role explains why policy clusters so strongly with Enthusiasts and is nearly absent among the Cautious.

Where policy is explicit and enabling, Enthusiast behavior emerges and persists. Where policy is partial, Pragmatist behavior dominates. Where policy is absent, Cautious behavior is reinforced.  Moreover, AI use in coding is already widespread. AI use in testing lags and represents a huge opportunity to gain further productivity and quality improvements.

The Organizational Opportunity

Our archetypes align closely with classical diffusion of innovations theory. Enthusiasts resemble innovators and early adopters. Pragmatists align with the early majority. Cautious developers correspond to later adopters who require both peer evidence and organizational legitimacy.

Organizations that want AI usage to deepen need:

  • Clear expectations
  • Shared standards
  • Explicit ownership

Empower the Enthusiasts and they will drive change.

Key Features of AI Adoption

Enthusiast Approach

Enthusiasts are in the vanguard of AI adoption, experimenting and validating cutting-edge tools to enhance productivity and code quality. They thrive in environments with strong policy support, driving innovation and setting benchmarks for others.

Pragmatist Strategy

Pragmatists focus on scalability and quality, adopting AI tools that have proven their worth. They balance optimism with critical evaluation, ensuring that AI integration aligns with organizational goals and standards.

Cautious Perspective

Cautious developers proceed with AI adoption carefully, without early adopters or policy support. They require clear examples of success and organizational endorsement to fully engage with AI technologies.