Video summary

The Most Underestimated Role in Your AI Transformation with Angela Wick

Main summary

Key takeaways

News and Commentary

Overview

Angela Wick (BA Cube) and Susan Moore (IIBA) discuss Wick’s article on the “evolving role of business analysis in the agentic era.” The central emphasis is that the most underestimated part of an AI transformation is business analysis integrated into the end-to-end lifecycle of embedding AI in organizations—not simply business analysts using AI tools to help with analysis.

1) The article’s focus: define BA’s role for AI leadership

  • The article was published in a senior-level IT leadership journal to help CTOs/CIOs understand how business analysis fits into AI orchestration from strategy through delivery and validation.
  • Wick stresses that BA for AI is not:
    • “business analysts using AI to do BA work”
  • Instead, it is:
    • analysis that integrates AI into enterprise workflows and operations
  • A key BA contribution is creating shared definitions, because AI-related terms (e.g., context, orchestration, AI agents, governance) are often used inconsistently across stakeholders.

2) What most companies miss in AI strategies

Wick argues many organizations miss three foundational areas:

  1. Overfocus on tools/technology instead of redesigning real work and operations
  2. Lack of governance and accountability for AI-enabled processes
    • Especially important because AI systems are not deterministic
  3. Insufficient trusted enterprise assets and content
    • So AI can reliably use organizational knowledge and context

3) “Modern analyst” skills replace the old requirements-gathering model

  • Traditional requirements practices assumed:

    • code was expensive
    • changes were costly → requirements were produced in phases/silos

  • With AI (and rapid prototyping/iterative development), requirements become:

    • continuous
    • collaborative
    • co-created rather than handed off as static artifacts.

Wick says business analysts need to level up with:

  • AI fluency (beyond basic chat/Copilot usage)
  • Strong communication, decision facilitation, and information structuring
  • Change management, collaboration, critical thinking, and systems thinking

These skills are framed as table stakes for BAs in AI environments.

4) If AI seems to reduce BA needs, it’s actually “analysis debt”

Wick introduces analysis debt, meaning organizations skip analysis and documentation of:

  • what is really happening
  • what rules exist
  • where data quality is poor
  • where operational workarounds are used

She distinguishes between:

  • reducing need for “note-taking/spec phase” BA (should decrease)
  • reducing need for BA’s deeper integration work (should not disappear)

She warns that when structured analysis is skipped, agentic AI initiatives struggle later—eventually “chaos breaks out” when governance and context are missing.

5) SDLC changes: requirements collapse into engineering/prototyping

Wick argues SDLC assumptions are shifting quickly because:

  • coding is becoming “cheap”
  • AI coding agents increasingly include analysis/testing/gap analysis

Implication:

  • requirements are no longer a phase
  • they happen in parallel with building prototypes

BA should avoid clinging to a “requirements silo/artifact” approach and instead:

  • facilitate structured analysis
  • support discussions around working artifacts while prototypes are built

This creates an identity crisis for some BAs:

  • if BA identity was tied to producing artifacts and owning a siloed process,
  • the role must evolve toward co-creation and orchestration.

6) Orchestration in practice: multi-agent ecosystems need BA oversight

  • “Orchestration” is explained using an orchestra analogy: different agents (human and AI) must “listen” and adapt while staying within shared boundaries.
  • BA’s practical contribution is defining:
    • context, scope, guardrails, assets, ownership/accountability
    • outcome metrics and governance/monitoring

The business must supervise AI ecosystems; this is not purely an IT delivery concern.

7) Advice from Q&A

User stories written with AI (“AI slop”)

  • BAs should collaborate with product owners and engineers to:
    • clarify intent
    • remove contradictions
    • ensure machine-readable, testable structure
  • Use AI to detect conflicts, rather than blindly accepting outputs.

Combining roles/titles

  • Leadership wants:
    • fewer silos
    • fewer handoffs
  • The mindset shift is to bring people together with unique BA lenses, not argue who “owns” rapid prototyping.

First steps to embed AI into process/governance

  • Start with value hypotheses and lean experiments
  • Ensure BA teams understand enough about AI to recommend where agentic systems belong
  • Avoid “AI everything” spending without ROI

Measuring BA value

  • Use rapid prototyping as visibility:
    • BAs enable scenarios quickly
    • results guide architecture/security/data governance decisions

Improving AI fluency

  • Prioritize practice in real work
  • Use structured courses/workshops and iterative experimentation

Adoption under governance risk (FP&A context)

  • Move via hypothesis → experiment → monitoring
  • Governance includes:
    • supervision
    • accountability
    • handling AI drift over time

AI analysis for infrastructure/IT

  • Always connect technical layers to real business needs, e.g.:
    • who uses a phone system and how
    • what business outcomes depend on it

Key takeaway / main argument

Business analysis is underestimated in AI transformation because organizations often treat AI as an IT/tooling project.

Wick’s core claim is that BA’s true role is to integrate AI into enterprise operations through:

  • continuous structured analysis
  • trusted assets/content
  • governance
  • decision facilitation
  • orchestration of people/tools/agents

…not merely producing traditional artifacts or using AI to draft documentation.

Presenters / contributors

  • Susan Moore — Community Engagement Manager, IIBA (host/moderator)
  • Angela Wick — Owner, BA Cube; author/speaker/trainer (guest)

Original video