No products in the basket.
BA Summit Southern Africa 2025 packed Sandton with about 300 business analysts and change professionals, all wrestling with one big question: how do you stay resilient and relevant when everything around you keeps shifting?
Four tracks, more than thirty speakers, and three days under the theme “Resilience & Reinvention: Business Analysis in a Fast-Changing World.” Business Change Academy was right in the thick of it with a full-day workshop drawn from the BCS Foundation in Business Analysis syllabus and translated into straightforward, practical tools.
If you are still new to this space, think of business analysts as the people who connect strategy with change and technology so that time, money, and attention land where they matter. BAs work with sponsors, product owners, business users, architects, developers, testers, operations and often customers, helping everyone stay honest about the problem, the options, and what “good” really looks like.
BA Summit SA is where that community in Southern Africa comes to sharpen skills and steal better ways of working. Business Change Academy is one of the places they go when they want to turn that energy into structured learning and accredited certification.
Across the formal sessions and the corridor chats, five themes kept surfacing that you can fold into everyday BA work, not just big change programmes.
Thinking and acting like a consultant
A message that cut through the noise: stakeholders do not buy documents, they buy decisions and outcomes. Nobody is excited about a 60-page specification. They care about launching a product, reducing complaints, meeting regulations without chaos, or unblocking revenue.
The analysts who stood out framed their work like consultants. They kept the tools, but led conversations with value, options, and trade-offs. “Here is my process model” became “Here are a few ways we could shorten onboarding, and what each one means for cost, risk, and delivery.”
You can start doing this simply by preparing for key meetings with four things in mind: the outcome you are aiming for, a couple of realistic options to reach it, the main risks and assumptions, and the smallest next decision that would move things forward. When discussions slide into detail for its own sake, you bring them back to, “Which option gets us closest to the outcome with acceptable risk?”
That small shift signals that you are not just recording the conversation, you are helping to shape it.
Choosing certification as a step, not an identity
Certification questions are permanent residents at BA Summit. BCS or IIBA? Full diploma or just foundation? Is it worth it if you are already “doing the job”?
The shared view was simple: certification works best when it is anchored to a clear, near-term goal. It is a tool, not a personality type. If you want credibility for a promotion, confidence to lead a bigger piece of analysis, or a structured view of what “good” looks like, then a course and exam can be powerful.
Where it falls flat is when certificates are collected without a clear “before and after.” If you cannot finish the sentence “After this certification, I expect to…” with something concrete, you risk spending effort without much change.
A quick reset is to sketch where you are now and where you expect to be a few months after a course: the kind of work you will be trusted with, the roles you can apply for, the conversations you can have. Once that is clear, you can pick the smallest meaningful qualification that closes that gap and leave the rest for later.
Rediscovering the basics
Despite all the talk of AI and new frameworks, the success stories kept coming back to three basics: clear outcomes, clear edges, and early acceptance rules.
Teams that delivered consistently could describe their outcome in one sentence. They were clear on what was in and out of scope, and which good ideas would simply wait. They had agreed, upfront, how they would judge whether the change was working in the real world.
When those basics were missing, everything felt harder: long meetings with no decision, teams moving in different directions, and late-stage panic about what “success” even meant.
You can test any current piece of work with three questions: Can people explain the outcome simply? Do they know what is definitely in and definitely out? Do you already have a shared sense of how you will judge success? If not, a short conversation that ends with a single outcome sentence, a simple “in / out / later” list, and a few plain-language acceptance points will often do more for the project than another slide deck.
Letting AI sit next to you, not in your seat
The “Reinventing with Tech” track focused heavily on AI, but the pattern from teams using it well was surprisingly consistent. AI worked as a co-analyst, not as the analyst.
Where it added value, teams were feeding AI real context about goals, users, constraints and current processes, then asking for help with heavy lifting: alternative phrasings, edge cases, examples and counterexamples, risks, or test ideas. They still applied their own standards and stakeholder knowledge before anything went near Jira or a deck.
Copying AI-generated requirements directly into official artefacts, on the other hand, almost always led to rework.
A lot of speakers used Given–When–Then style examples to show what good looked like: given a situation, when something happens, then a specific result is expected. AI is very good at generating many of these, especially once it knows your desired outcome and scope edges. Your job is to decide which ones are specific, observable, valuable and feasible in your context, and which ones go in the bin.
Used this way, AI widens your thinking, but you stay firmly in the driver’s seat.
Treating resilience as a rhythm
With a theme centred on resilience, the summit could have become a festival of slogans. Instead, the practical stories all treated resilience as something you build into your team’s rhythm, not a heroic personality trait.
The resilient teams were not the ones bragging about long hours. They worked in short, visible loops, protected focus time, and kept a handful of simple rituals that helped them adjust regularly. You could see a pattern in how they planned, delivered, reflected, and tweaked their approach.
A tiny weekly retrospective came up again and again: a short, regular check-in asking what helped, what drained time or energy, and what small experiment to try next. The emphasis was on consistency and on choosing one change at a time, then giving it space to prove itself.
Over time, that kind of rhythm does more for resilience than any poster on the wall.
Where this leaves you as a BA
If you are early in your BA journey, the jargon and frameworks can feel like a lot. POPIT models, investigation techniques, requirements standards, certification paths. Underneath all of that, the work stays the same: help organisations understand problems and opportunities, define what “good” looks like, and guide change so that solutions create real value.
Events like BA Summit SA and programmes like Business Change Academy’s Foundation in Business Analysis are there to make that work more deliberate. They give you a shared language for outcomes, edges, and acceptance, a toolkit that works in both agile and traditional environments, and a clear step on a career and certification pathway.
If you want to take things further, a good start is to plug your current project into a simple requirements or acceptance template, or to map it against POPIT to see if you are missing impacts on people, process, or information. From there, a structured course can tie the pieces together.
However you choose to move forward, the themes from #BASummitSA offer a straightforward compass: talk in outcomes, not documents; let certification serve a real step in your career; respect the basics; treat AI as a partner; and build resilience into the way you work, one small habit at a time.