This article began with an accident. Earlier today I was browsing through an old folder of certificates — looking for something else entirely — when one of them stopped me mid-scroll. My membership certificate of the International Institute of Business Analysis. December 2006. Member Number 661.
The IIBA itself was barely three years old when this was issued. The first edition of the BABOK Guide was still finding its readership. I was deep inside an IT organisation, designing digital solutions for oil and gas customers, and I drew liberally on BABOK concepts — elicitation, requirements management, stakeholder analysis, solution evaluation — to give shape to those engagements. The framework worked.
That certificate, almost twenty years on, made me wonder: If those concepts worked so well in 2006 with spreadsheets, Visio diagrams, Word templates, and hours of stakeholder workshops — what would the same discipline look like today, with AI sitting on every BA’s laptop?
That single question is why I am opening a new series within this newsletter, with a deliberate focus on the BA community.
The Quiet Sorting Inside the BA Profession
Business analysis as a discipline is not dying. Far from it.
The global big-data and business analytics market, valued at roughly USD 193 billion in 2019, is projected to cross USD 420 billion by 2027 (Allied Market Research)
69% of executives say AI brings a new urgency to enterprise reinvention (Accenture Pulse of Change, 2025)
McKinsey estimates that up to 30% of work hours could be automated by 2030
The World Economic Forum’s Future of Jobs research shows that 50% of workforce skills become obsolete every five years
But within those numbers, a quiet sorting is taking place.
The BAs whose value lay in writing thorough requirements documents, running structured elicitation workshops, building neat process diagrams, and documenting acceptance criteria are finding that AI tools can now produce a credible first draft of all of it.
A first draft. Not the final deliverable. Not a substitute for judgement. But a starting point that would have taken six hours yesterday and now takes six minutes.
If your value as a BA was the production of those drafts, the disruption is already at your door. If your value was something larger — framing the right problem, navigating stakeholder politics, validating whether a proposed solution actually fits the business context — then AI is the most powerful assistant you have ever had access to. The same technology. Two very different futures.
Why BABOK Is Necessary, But No Longer Sufficient
BABOK’s six knowledge areas — Business Analysis Planning and Monitoring, Elicitation and Collaboration, Requirements Life Cycle Management, Strategy Analysis, Requirements Analysis and Design Definition, and Solution Evaluation — remain the most rigorous map of what business analysis actually is.
But BABOK was last revised before generative AI became a workplace reality. It tells you what a BA does. It does not yet tell you which parts of that work an AI should do, which parts you must do, and which parts you must do together.
That layer is being written right now, in practice, by every BA who is experimenting with these tools — often without a framework to guide them. That is what I want to build with you, edition by edition.
What This Series Will Cover
Starting with the next issue, I will work through the BABOK knowledge areas one at a time, asking:
- What does this knowledge area look like in 2026?
- Which AI tools are genuinely useful here, and which are over-sold?
- What is the practical workflow that combines the BA’s judgement with the AI’s speed?
- Where does the AI fail, and what must the BA never delegate?
- What new competencies does this demand of us?
The roadmap:
- AI in Business Analysis Planning and Monitoring
- AI in Elicitation and Collaboration — the fastest-changing area
- AI in Requirements Life Cycle Management
- AI in Strategy Analysis
- AI in Requirements Analysis and Design Definition
- AI in Solution Evaluation
- The new operating model — what a BA looks like in 2027
Across these editions I will share actual prompts tested, outputs produced, what was useful, and what I had to throw away. No theoretical promises. Practical artefacts you can adapt to your own work tomorrow morning.
A Word to Three Audiences
To Practising BAs
This is for you most of all. You are the ones who will either ride this wave into far more strategic roles, or watch routine BA work commoditize around you. The choice is being made now.
To BA Managers and Consulting Leads
Your teams are quietly using AI tools already, often without guidance, sometimes without your knowledge. The question is not whether to allow it. The question is how to govern it, train for it, and channel it into competitive advantage.
To Aspiring BAs and Students
You are entering the profession at the most exciting moment in its history. The bar is higher, but so is the ceiling.
Why I Am Genuinely Excited About This
In forty years of work, I have reinvented myself eight times. Refinery operator to simulation developer. PSU engineer to consultant. Technical specialist to author and keynote speaker. And now, at 63, building AI applications and writing about them.
Each reinvention has had the same quality — a moment when the old way of working stopped paying the dividends it used to, and a new way demanded courage and curiosity in equal measure.
The business analyst profession is in that moment now. Like a catalyst in chemistry, my job is not to replace your effort — it is to lower the activation energy required for your own reinvention.
Closing Thought
Reinvention is not a single decision. It is a practice. Let us get to it.
Originally published in the Reinvention in the AI Era newsletter on LinkedIn.