Agentic AI Transformation: Prioritizing People Over Tools
Jen St-Pierre outlines the critical shift from tooling rollouts to human transformation in agentic AI adoption. Leaders must redefine roles, metrics, and psychological safety to secure developer commitment and drive strategic value.
Agentic AI is fundamentally reshaping software development, yet the primary barrier to success is human adaptation, not technological capability. Jen St-Pierre, SVP at Dell, argues that organizations treating AI as a simple tooling rollout invite resistance and instability, whereas those framing it as a human transformation secure commitment and competitive advantage. The shift moves developers from code generation to orchestration, dissolving traditional barriers to captive knowledge and requiring a redefinition of value creation.
The People Transition Imperative
Historical shifts from DevOps to cloud adoption reveal a consistent pattern: technology advances faster than people, triggering cycles of excitement, skepticism, fear, and eventual productivity. AI disrupts the "protected" nature of coding, creating tension around job security. Leaders must recognize that AI does not eliminate developers but elevates their operational level. This elevation feels destabilizing before it becomes empowering, placing change management at the core of the strategy. Treating AI as a leadership challenge rather than an IT initiative is the differentiator between stalled adoption and durable transformation.
Five Operational Pillars for Success
Successful organizations execute five operational necessities. First, establish a shared understanding of the "why," framing AI as a driver for market acceleration and strategic problem-solving rather than mere productivity or cost reduction. Second, define a clear future state that answers critical questions: what will work look like, what is rewarded, and what disappears? Specificity, such as targeting 80% agentic code generation and shifting reviews to design validation, reduces uncertainty. Third, align role clarity with capability building; strategy shifts require redefined roles and explicit training to prevent anxiety. Fourth, cultivate psychological safety, validated by Google's Project Aristotle, to allow experimentation and candor without retribution. Fifth, reinforce through structure and metrics, replacing legacy measures like lines of code with assessments of architectural quality, business outcomes, and token economics.
Leadership Accountability and Career Evolution
Executives must model adoption by using tools visibly, rewarding imperfect experimentation, and narrating the transformation continuously. Career paths must be explicitly redefined to address developer concerns about growth and mastery. If leadership fails to answer these questions, top talent will self-assign answers and leave. The window to lead this transition intentionally is immediate; organizations that rehumanize engineering by focusing on direction and meaning will thrive, while those that ignore the people dimension risk obsolescence.
Key insights
-
AI shifts the unit of work from coding to orchestration, dissolving barriers to captive knowledge. This elevates developer value but creates destabilization that requires intentional change management.
Impact: Organizations that fail to manage the people transition risk resistance, talent attrition, and organizational instability despite technological adoption.
-
Treating AI as a tooling rollout yields compliance, while treating it as a human transformation yields commitment. The framing of adoption as strategic elevation versus cost reduction dictates emotional response.
Impact: Strategic framing reduces fear and accelerates adoption by aligning developer interests with market acceleration and problem-solving opportunities.
-
Legacy metrics like lines of code accelerate bad behaviors in an AI context. New metrics must focus on architectural quality, business outcomes, and token economics.
Impact: Overhauling metrics ensures incentives reinforce desired agentic behaviors and prevents teams from optimizing for outdated quantitative measures.
-
Psychological safety is the top predictor of team effectiveness, enabling experimentation and candor without retribution. This is critical for AI adoption where mistakes are inevitable.
Impact: Cultivating safety shifts defect detection left in conversations, reduces risk, and fosters a culture where developers actively explore AI capabilities.
-
Leadership must model adoption, reward experimentation, and maintain emotional presence. Career paths must be explicitly redefined to address concerns about growth and mastery.
Impact: Visible leadership engagement and clear career pathways retain top talent and demonstrate genuine organizational commitment to the transformation.
Action items
-
Audit current developer metrics and replace legacy indicators like lines of code with measures of architectural quality, business impact, and token economics.
Impact: Aligns incentives with agentic workflows and prevents the acceleration of outdated behaviors that hinder strategic value creation.
-
Define a clear future state for engineering roles, specifying what work will look like, what is rewarded, and what processes will disappear within 12 months.
Impact: Reduces uncertainty and resistance by providing developers with a concrete vision of their evolving responsibilities and success criteria.
-
Implement training programs that build capabilities for strategic problem-solving, system thinking, and AI validation to support new role expectations.
Impact: Ensures developers have the skills required for elevated roles, bridging the gap between strategy shifts and individual capability.
-
Establish psychological safety mechanisms that encourage experimentation, allow for mistakes, and protect developers from reputational risk when using AI tools.
Impact: Accelerates learning and adoption by creating an environment where teams can safely explore AI capabilities and surface issues early.
-
Leaders should visibly use AI tools, reward imperfect experimentation, and continuously narrate the transformation to demonstrate commitment and emotional presence.
Impact: Models desired behaviors, builds trust, and reinforces the cultural shift required for durable organizational change.
Quotes
“AI does not eliminate developers. It changes what they spend their time on, what fills their day, how they add value, and where their judgment is going to get applied.”
“People don't resist the change itself. What they resist is the uncertainty of what that change means for them, that they can't see the picture of where you're going.”
“AI will generate code. Humans are going to generate the direction. AI is going to accelerate execution. And humans are going to define the meaning behind what we build.”