Whose Story Is It? Working Agile with AI
By IMA Worldwide Change Management Practitioners | AIM field research across agile and AI transformation programs.
In agile teams adopting AI tools, 60-65% of practitioners report confusion about accountability and authorship when AI generates user stories, acceptance criteria, or sprint plans. This tension highlights a critical challenge: as AI becomes an active participant in agile workflows, the question of who owns the narrative and who is accountable for change outcomes becomes increasingly complex.
Every AI project has a story. Typically, the narrative is dominated by technology. The product roadmap, sprint reviews, capability demos, and vendor presentations focus on technical achievements. Systems and algorithms are the protagonists, while the humans impacted by AI are often sidelined or absent. Agile AI change management addresses this narrative imbalance by centering people in the story and providing a structured approach to ensure the story concludes with genuine adoption, not just technical delivery.
This article explores the narrative challenges in AI projects, the strengths and limitations of agile methodologies in this context, and how Accelerating Implementation Methodology (AIM) for AI transformation offers the change management infrastructure agile teams need to deliver AI initiatives that change behavior, not just code.
The Narrative Problem in AI Projects
AI adoption statistics reveal a persistent gap between technical delivery and behavioral change. According to industry research, over 70% of AI projects fail to achieve full adoption within organizations, often due to insufficient focus on human factors. This adoption gap underscores the narrative problem: technology dominates the story, while the people affected are afterthoughts.
When the Story Belongs to the Technology
In most AI projects, the technology team controls the narrative. Project language centers on model accuracy, training data, API integration, and inference latency. Milestones and success criteria are technical. Employees whose workflows and roles will change receive minimal attention, often limited to a user acceptance testing slot late in the project and a brief training session before go-live.
This approach results in AI capabilities that are technically delivered but behaviorally ignored. Studies show that only 30% of employees fully adopt new AI tools when human factors are neglected, leading to underutilized investments and missed business value. Implementing a structured AI change management strategy is essential to bridge this gap effectively.
Reclaiming the Human Narrative in AI Transformation
Reclaiming the human narrative means rewriting the project story from the outset to prioritize people—their needs, concerns, capabilities, and adoption of new workflows—as central design constraints. Before the first sprint planning session, teams must ask: whose behavior must change for this AI initiative to succeed? What are these individuals currently doing? What must they do differently? What will motivate and enable them to change?
These questions are critical and require change management expertise alongside engineering skills. IMA Worldwide and Peacock Hill Consulting emphasize that addressing these human factors early increases adoption rates by up to 50%, significantly improving project outcomes.
Agile Methods Meet AI Reality
Agile methodologies offer strengths for AI change management but also face limitations without integrated change management. Understanding these dynamics is essential for successful AI transformation.
What Agile Gets Right About AI Change
Agile’s iterative, incremental approach aligns with AI systems that evolve over time. Its emphasis on working software over documentation translates to prioritizing actual behavioral change over extensive training materials. Agile values responding to change over following a fixed plan, which suits the adaptive nature of AI implementations.
The principle of continuous improvement—regular retrospectives, rapid feedback loops, and willingness to adjust—is closely aligned with AIM’s approach to ongoing adoption monitoring and reinforcement. Organizations operating in agile environments often find AIM integrates naturally with their workflows. For more insights, see McKinsey on AI and agile teams and Reinforcement in Change Management.
Where Agile Falls Short Without Change Management
Agile frameworks optimize software delivery, not organizational behavior change. The definition of done focuses on software functionality, not adoption. Product owners are typically technical or product professionals, not change management practitioners. Velocity metrics measure development productivity, not adoption progress.
Without a deliberate change management layer, agile AI teams deliver technically functional systems that fail to change intended behaviors. Sprints complete, backlogs clear, products ship—but adoption gaps persist. Harvard Business Review highlights these challenges in Agile at Scale. IMA Worldwide and Peacock Hill Consulting provide change management consulting to bridge this gap.
The models are ready. Your people may not be. Find out in about 4 minutes.
The Accountability Problem When AI Joins the Sprint
When AI tools generate user stories, acceptance criteria, or sprint plans, many agile teams face confusion about who owns the narrative and who is accountable for adoption outcomes. IMA Worldwide’s Accelerating Implementation Methodology (AIM) highlights that without explicit ownership and accountability structures, AI-generated outputs risk becoming black boxes that disconnect technical delivery from human adoption.
AIM advocates for clear role contracting and narrative ownership embedded from sprint zero, ensuring that change agents and executive sponsors share responsibility for the human story. This approach prevents diffusion of accountability and aligns AI-augmented agile teams around shared adoption goals.
Whose Story Should It Be?
Determining whose story an AI project tells is fundamentally a stakeholder management challenge. Each stakeholder group has concerns, interests, and questions about AI’s impact. Change management ensures these stories are heard, integrated into project design, and addressed through the change plan.
Stakeholders, Storytellers, and Change Agents
Change agents embedded within the business, equipped with AIM methodology and skills, and accountable for adoption outcomes carry the human narrative into every team, function, and geography. They translate technical narratives into human terms and relay business concerns back to technical teams.
Mapping Narrative Ownership in AI Teams
Narrative ownership is rarely explicit, defaulting to technology teams. Explicit ownership assigns accountability for understanding stakeholder concerns, communicating the change story, owning adoption measurement, and adjusting plans when adoption lags.
AIM addresses this through change agent network design and sponsor accountability. The change agent network owns the human story within the business; executive sponsors own it organizationally. The change management practitioner leading AIM connects these roles into a coherent narrative defining AI initiative purpose and success.
How AIM Clarifies Roles in AI-Augmented Agile Teams
AIM for AI Transformation in Agile Environments
IMA Worldwide and Peacock Hill Consulting have demonstrated that integrating AIM with agile delivery frameworks significantly improves AI adoption metrics, with organizations reporting up to 40% faster behavioral change and 35% higher sustained usage rates.
Applying AIM Principles to Sprints and Iterations
AIM maps change management activities to sprint cadences. Each sprint produces software functionality and change management outputs: stakeholder engagement progress, communication touchpoints, change agent network milestones, and adoption measurement data. These outputs complement technical velocity metrics, providing a comprehensive progress view.
Sustaining Adoption Across Agile Releases
Agile AI programs face challenges sustaining adoption as new releases affect employees who adapted to prior versions. Each release is a change event requiring communication, capability development, and reinforcement.
AIM’s multi-release adoption management includes pre-release impact assessments identifying affected groups, targeted communication campaigns explaining changes, updated training addressing capability gaps, and adoption measurement tracking behavioral responses per release and cumulatively.
The Unique Change Management Challenges When AI Joins the Agile Team
When AI actively participates in agile teams, unique change management challenges arise. Role clarity erosion occurs as AI assumes tasks, causing confusion and reduced accountability. This leads to narrative drift, shifting focus from human-centered goals to technical outputs, weakening stakeholder engagement and adoption.
Retrospectives and feedback loops may lack accountability because AI-generated outputs miss human context. Without clear role contracting, teams risk losing alignment on adoption responsibility and communication.
Accelerating Implementation Methodology (AIM) addresses these challenges by structuring explicit role contracting and accountability within the change agent network. AIM ensures human roles are clearly defined alongside AI capabilities, narrative ownership remains with designated change agents, and retrospectives include technical and behavioral adoption metrics. This prevents failure modes related to role ambiguity and narrative drift, enabling agile teams to harness AI effectively while maintaining organizational change momentum.
How AIM Manages Story Ownership in Agile AI Projects: A 5-Step Process
- Establish Clear Narrative Ownership From the outset, AIM assigns responsibility for the human story to a dedicated change agent network and executive sponsors, ensuring accountability is explicit and embedded in project governance.
- Integrate Change Management into Sprint Planning Each sprint planning session includes a review of change management activities, stakeholder engagement, and adoption metrics alongside technical backlog items to maintain alignment.
- Develop and Empower Change Agents AIM builds a network of change agents embedded in business units who translate technical narratives into human terms and gather feedback to inform ongoing adjustments.
- Monitor Adoption Continuously Behavioral adoption metrics are collected and analyzed sprint-by-sprint, enabling rapid identification of adoption gaps and timely interventions.
- Co-Create the Change Narrative Frontline employees and managers are engaged in defining the AI initiative’s purpose and success criteria, fostering ownership and commitment to the change.
“In AI-assisted agile programs, unclear story ownership is the leading cause of adoption failure not the technology itself. When AIM structures accountability from sprint zero, teams see measurably faster change adoption.” IMA Worldwide field research.
Questions Every Agile Team Should Ask Before Adopting AI Tools
- Who will own the narrative and accountability for AI-generated user stories and acceptance criteria?
- How will change management activities be integrated into sprint planning and delivery cycles?
- What mechanisms will ensure continuous adoption measurement and feedback?
- How will change agents be empowered and embedded within business units?
- What communication and training strategies will support sustained adoption across multiple AI releases?
The models are ready. Your people may not be. Find out in about 4 minutes.
Writing a Better AI Story Together
Co-Creating the Change Narrative
The most effective change narratives for AI initiatives are co-created with the people who will live the change. This involves frontline employees and managers in defining the AI initiative’s purpose in human terms, success criteria from their perspective, and organizational support needed for the transition.
Co-creation is a practical strategy for building ownership and commitment that sustain adoption. People who help write the story are more likely to live by it. IMA Worldwide and Peacock Hill Consulting facilitate this process to ensure alignment and engagement.
Measuring Whether the Story Is Landing
Behavioral metrics are the ultimate measure of narrative success: are employees using AI tools, making decisions supported by AI, and producing intended outcomes? These metrics require rigorous design, tracking, and action, akin to other performance indicators.
IMA Worldwide and Peacock Hill Consulting assist agile AI teams in building measurement frameworks, change agent networks, and narrative ownership structures that transform technically delivered AI systems into genuinely adopted organizational capabilities.
Why Agile AI Adoption Stalls at Implementation, Not Installation
Agile teams ship AI tools fast, but agile AI change management is not finished when the tool is installed. It is finished when people change how they work. The Accelerating Implementation Methodology (AIM), developed by Don Harrison at IMA Worldwide, names this the gap between installation, the tool going live in the sprint, and implementation, the team actually owning new practices and story ownership around it. In agile AI transformations that gap is wide because the tooling moves faster than the behavior.
AIM also weights leadership effort: reinforcement carries roughly three times the impact of the initial announcement. For an agile AI team that means reinforcing new roles every retrospective, not introducing the AI once and moving on. McKinsey & Company finds roughly 70 percent of large-scale change programs miss their goals, most often because the people side is underfunded relative to the technology.
Frequently Asked Questions
How does AI change Agile ways of working?
AI can draft stories, code, and tests, but the team still owns the outcome and the judgment behind it. The shift is less about tooling and more about how people adapt their roles, which makes it a change management challenge as much as an Agile one.
How do you manage the human side of adopting AI in Agile teams?
Through active sponsorship, building readiness in the people who must change how they work, clear communication about what AI does and does not decide, and reinforcing the new ways of working after rollout. These are the practice areas the Accelerating Implementation Methodology (AIM) applies to AI adoption.
Who is accountable for work that AI helps produce?
Accountability stays with the people and the team. AI assists, but ownership of quality, ethics, and outcomes remains human, which is why adoption has to be managed deliberately rather than assumed.
This guidance draws on the Accelerating Implementation Methodology (AIM), created by Don Harrison and refined across 40+ years of implementation research at IMA Worldwide. Curated by Ann Marvin.
Ann Marvin is Founder of Peacock Hill Consulting and Chief of AI Tools at IMA Worldwide (Implementation Management Associates).
