From Experimentation to Shared Knowledge: Luca Rossi on AI Adoption in Engineering Teams

?

๐ŸŒ€ Luca Rossi

LinkedIn Author

Author of Refactoring.fm โ€ข I write about making software and working together, to 150K+ engineers

In a recent LinkedIn post, ๐ŸŒ€ Luca Rossi discusses the evolving landscape of Artificial Intelligence (AI) adoption within engineering teams, shifting from a focus on individual experimentation to the critical need for shared knowledge and consolidated tool usage.

Luca Rossi begins by acknowledging the potential of AI, noting his past advocacy for a bottom-up approach where engineers are given AI budgets for experimentation. However, he indicates a pivot in his perspective, suggesting that the current stage of AI adoption necessitates a different strategy.

“For a long time I have said “just give engineers AI budget and make them experiment bottom up” โ€” which makes sense, but I think we are past the point where people just need to “experiment”.”

Rossi highlights that individual AI adoption rates are remarkably high, exceeding 90%. This widespread personal use, while a positive sign of engagement, presents a new challenge for team-level advancement. The focus, according to Rossi, must now shift towards collective learning and building shared knowledge bases.

The Evolution of AI Strategy in Engineering

The core of Rossi’s argument centers on the transition from individual exploration to collaborative integration. He posits that while empowering engineers to experiment freely was a valid initial strategy, the maturity of AI tools and their adoption means that teams can no longer rely solely on isolated efforts to progress.

From Individual Experimentation to Team Synergy

As ๐ŸŒ€ Luca Rossi points out, the high percentage of individual AI adoption signifies that engineers are already comfortable and proficient with various AI tools on a personal level. The next logical step for teams seeking to “level up” is to harness this individual expertise for collective benefit.

“Individual AI adoption is >90%, so to level up as a team we now need to share learnings and create team knowledge.”

This emphasis on sharing learnings is crucial for fostering a cohesive and efficient engineering environment. Without a structured approach to knowledge sharing, teams risk fragmented understanding and duplicated efforts, even with high individual adoption rates.

Consolidating Tools and Limiting Fragmentation

A significant aspect of Rossi’s updated perspective involves the strategic management of AI tools within an organization. He suggests that to effectively build team knowledge and avoid inefficiencies, a better understanding and control over the tools being used is necessary.

The Importance of a Coherent Toolset

According to ๐ŸŒ€ Luca Rossi, maintaining a clear overview of the AI tools utilized by the team is paramount. This awareness allows for the identification of overlaps, redundancies, and opportunities for standardization. Limiting fragmentation, in Rossi’s view, is key to maximizing the impact of AI across the entire team, rather than allowing it to remain a collection of individual, disconnected experiments.

“And to do that it makes sense to keep a better grasp of what tools are being used, and limit fragmentation.”

By advocating for a more consolidated approach to AI tool adoption and a deliberate strategy for sharing insights, ๐ŸŒ€ Luca Rossi provides a timely perspective on how engineering teams can move beyond basic adoption to achieve true AI-driven synergy and enhanced productivity.

📝 About This Content

This article is based on insights shared by ๐ŸŒ€ Luca Rossi on LinkedIn.

📅 Originally posted on April 7, 2026 | View original post on LinkedIn โ†’