The standard explanation is skill or tooling configuration. But after working closely with development teams through this transition, a clearer picture emerges. What separates high-performing teams from the rest isn't the tools they use. It's how they use them.
In this article, we explore why the same AI tools produce such different outcomes across teams and what leaders need to put in place to move from dysfunction to genuine partnership with AI. Because the real barrier to artificial intelligence adoption isn't technical. It's psychological.
Three generations of software engineering
To understand why AI adoption produces such uneven outcomes, let's trace the evolution of software development practice.
- Software engineering 1.0: The code-centric era. Traditional development placed the developer at the centre. Engineers wrote code and built software applications with support from tools that facilitated analysis, compilation, and quality testing. Responsibility and focus were both squarely on the individual. Output was code, and skill was measured in code.
- Software engineering 2.0: The AI-assisted era. The current era introduced AI-powered assistants — GitHub Copilot being the most prominent example. These tools augmented the conventional process with code generation, intelligent suggestions, and autocomplete. The promise was transformative. The outcomes, however, have been inconsistent. This is where most organisations sit today.
- Software engineering 3.0: The intent-first era. Software Engineering 3.0 shifts emphasis from code to developer intent. This term was first articulated by Hassan et al. (2024) from Queen's University's Software Analysis and Intelligence Lab. Rather than asking "How do I write this?", developers ask "What do I want to achieve?" — and collaborate with AI to find the solution. Development happens through interactive dialogue. The developer leads the artificial intelligence partners.
The technology for Software Engineering 3.0 already exists. The architecture is understood. The research is published. What holds organisations back is not a product gap. It is a psychological one.
The pattern behind the gap
When teams using identical AI tools produce radically different results, the explanation runs deeper than training or configuration. The real differentiator is behavioural — and it maps with striking precision onto a psychological model first described by psychiatrist Stephen Karpman in 1968.
Karpman’s Drama Triangle identifies three roles in a dysfunctional cycle: the Victim, the Rescuer, and the Persecutor. Each role feels productive from the inside. Collectively, they produce stagnation. The pattern is well-documented in organisational psychology. It is also, it turns out, a near-perfect description of how many teams currently relate to AI tools.
Related Insights
The breadth of knowledge and understanding that ELEKS has within its walls allows us to leverage that expertise to make superior deliverables for our customers. When you work with ELEKS, you are working with the top 1% of the aptitude and engineering excellence of the whole country.
Right from the start, we really liked ELEKS’ commitment and engagement. They came to us with their best people to try to understand our context, our business idea, and developed the first prototype with us. They were very professional and very customer oriented. I think, without ELEKS it probably would not have been possible to have such a successful product in such a short period of time.
ELEKS has been involved in the development of a number of our consumer-facing websites and mobile applications that allow our customers to easily track their shipments, get the information they need as well as stay in touch with us. We’ve appreciated the level of ELEKS’ expertise, responsiveness and attention to details.
