I still remember the moment the question stopped being hypothetical.
I was sitting in a requirements workshop, slightly behind on my notes, when I opened a tool and asked it to draft the user stories from the discussion we'd just had. Within about forty seconds, there they were: structured, reasonably well-written, formatted correctly. Good enough that I could have submitted them after a light edit.
My first reaction wasn't relief. It was a quiet, unsettling thought: if that took forty seconds, what does that mean for me?
That question is one a lot of Business Analysts are sitting with right now. The World Economic Forum's 2025 Future of Jobs Report estimates that 92 million jobs will be displaced by AI by 2030, even as 170 million new ones emerge. The net figure is positive, but that statistic doesn't do much to quiet the nerves of someone watching a tool draft their deliverables in real time.
At the recent BA Summit SA, I spoke about what I think is the more useful response to that anxiety: not resistance, not resignation, but resilience. And resilience, I've come to believe, starts with an honest reckoning of what we actually do.
We Were Never "Just" Business Analysts
Here is something most job descriptions won't tell you: the BA role has always been far more than its artefacts.
Most of us aren't just Business Analysts. On any given week we are the Product Owner, the Scrum Master, the translator between an engineering team that thinks in systems and a business stakeholder who thinks in outcomes. We are the person who remembers that this exact requirement was tried two years ago and quietly failed for reasons that never made it into any document. We are the one in the room who notices that two teams are about to optimise for conflicting goals, and says so before it becomes a crisis.
We have always been something closer to connective tissue than documentation machines. AI enters a role that was never simple, and that matters.
The Co-Analyst in Training
The shift that has helped me most is a simple reframe. I stopped thinking of AI as a replacement or a shortcut and started treating it like a junior analyst on the team.
A junior analyst can draft a first pass at user stories. They can summarise a lengthy workshop discussion. They can flag potential gaps in a requirements document, or suggest approaches you hadn't considered. They bring genuine value. But they need direction. They need context. They need someone experienced enough to know when their output is technically correct but fundamentally wrong.
That is exactly what AI needs too.
When I use these tools now, I'm not handing over responsibility. I'm accelerating the parts of the work that don't require my judgement, so I can spend more time on the parts that do. I guide the prompts. I challenge the outputs. I use the tool as a sparring partner, asking it to critique my thinking, poke holes in my assumptions, play devil's advocate on a solution I've become attached to. The results are better when I treat it as a collaborator I'm supervising, rather than an oracle I'm querying.
This matters more than it sounds. PwC's 2025 Global AI Jobs Barometer, which analysed close to a billion job postings across six continents, found that workers in AI-exposed roles who engage actively with AI tools are seeing their wages rise twice as fast as those in roles least exposed to it. The people who are thriving aren't the ones waiting to see what AI does to their job. They're the ones who decided to figure it out first.
From Documentation to Strategy
If AI can produce documentation, and it can do so increasingly well, then documentation alone cannot be where the BA role lives.
This is uncomfortable to acknowledge, but it's also clarifying. Because the moment you accept it, the path forward becomes visible.
The work that AI genuinely cannot do is the work that has always been the most valuable part of what we do, even if it's been obscured by the volume of artefacts we produce. It can't walk into a room where the business sponsor and the engineering lead have subtly different ideas of what success looks like, and find the language that brings them to the same picture. It doesn't carry the memory of why the last re-platforming failed, or the intuition that the solution being proposed is solving a symptom rather than the problem underneath it.
Analyst roles involving socially oriented tasks, navigating stakeholder conversations, discussing nuance and exploring alternative paths, are considered among those least easily displaced by automation, precisely because they require something that cannot be replicated in software: the judgement that comes from being genuinely present in an organisation, over time.
The artefacts are automatable. The alignment work is not.
This is where reinvention begins: stepping deeper into solution design, not just capturing requirements but co-creating outcomes. Becoming the person who connects the dots across teams and business areas, who asks the questions no one else thinks to ask. Are we solving the right problem? Are we optimising locally at the cost of something bigger? What risk are we not seeing?
AI can help structure the answer. It cannot define the question.
Stay Connected
Our monthly newsletter keeps tech professionals informed with insider tech insights, career opportunities, and Entelect updates.
Jobs | Tech News | Memes | Culture
Investing Instead of Resisting
It is easy to fear automation. It is harder, and far more powerful, to invest in it.
In my own practice, I've been experimenting with teaching AI how I think: giving it context, iterating on prompts, using it to pressure-test requirements before they reach stakeholders. The more intentional I am about the inputs, the better the outputs become. It's less like using a tool and more like developing a working style with a very fast, very literal collaborator who has no ego and infinite patience.
That's not a minor thing. The BA role has evolved before, from documentation-heavy gatekeepers to facilitators of value delivery, from process mappers to product thinkers. This is the next evolution point, and it is one we can choose to move toward deliberately rather than be pushed into reactively.
So, Who Are We?
If AI can write the story, who are we?
We are the ones who understand why the story matters. We are the connectors across silos, the translators of complexity, the people who notice when the right answer to the wrong question is still the wrong answer. We are the custodians of alignment: not the documents that record it, but the conversations, the relationships, and the hard-won organisational knowledge that makes it possible.
Resilience in the age of AI is not about defending territory. It is about stepping into higher-value work, work that the tools are making more visible precisely because they're taking on so much of what used to obscure it.
The tools are changing. The core of what we do is not. Curiosity. Critical thinking. Contextual awareness. The ability to bring people together around the right problem.
AI can support those strengths. It cannot replace them.
The question isn't whether AI will change our role. It already has. The real question is whether we are willing to evolve with it, and if we are, the future of the Business Analyst is not smaller. It is more strategic than ever.
by Senaly Singh
