Process Improvement Mastery: How Business Analysts Lead Change, Not Just Document It

DAY 1 | Why Process Improvement Is a BA's Most Powerful Skill

I want to tell you about a warehouse operations team I worked with early in my BA career.

They had a goods-in process that required three separate sign-offs before any delivery could be accepted. Each sign-off came from a different department. Each department had different working hours. The result was that deliveries regularly sat in the loading bay for hours, sometimes overnight, waiting for the third signature to arrive. Drivers were delayed. Stock was late reaching the floor. The operations team had adapted by building workarounds that created their own problems. I was brought in to document the process as part of a wider system implementation. So I documented it. Every step. Every handoff. Every signature. I produced a process map that accurately reflected exactly what was happening.

A good piece of work, technically. And completely useless, because what I produced was a detailed record of a broken process that would now be built into the new system.

The person who eventually fixed the goods-in problem was not a consultant or a process engineer. It was a BA who came in three months later, looked at the same process map I had drawn, and asked a question I had never thought to ask: why do all three sign-offs need to happen before acceptance, rather than concurrently or after?

The answer, it turned out, was that nobody knew. The three-signature requirement had been introduced after a stock discrepancy years earlier and had never been reviewed. The underlying risk it was supposed to address had been resolved by a different control entirely. The signature requirement was a process fossil. And removing it reduced the average goods-in time from four hours to forty minutes. That is what process improvement looks like when it is done properly. Not a methodology. A question.

What Process Improvement Actually Is

Process improvement is the structured work of identifying why a process is not performing as well as it should, understanding the root causes of that underperformance, and designing and implementing changes that produce measurably better outcomes. Most definitions stop at the first part: identifying what is wrong. That is process analysis. Process improvement includes everything that comes after it: the diagnosis, the design of the solution, the engagement of the people affected, and the implementation of change in a way that actually sticks.

The distinction matters because it changes what you do. A BA focused on process analysis asks: what is the process? A BA focused on process improvement asks: why does the process fail, and what would a better process look like? These are different investigations. They require different questions, different stakeholder conversations, and a different willingness to challenge what exists rather than simply recording it.

Why BAs Are Better Placed to Lead Improvement Than Anyone Else

Process improvement gets assigned to different people in different organisations. Sometimes it goes to operations managers. Sometimes to consultants. Sometimes to dedicated process teams with Lean or Six Sigma certifications. But the Business Analyst is often the best-placed person in the room to lead it, and here is why.

• The BA already understands the business. They have spent time with the people who run the process, understand its purpose, and know where the pressure points are. They do not need to start from scratch with the organisational context the way an external consultant does.

• The BA knows how to elicit the real problem. The skill of getting past what people say to what they actually mean is central to requirements work. It is equally central to process improvement. The person running a broken process will often describe the symptoms without being able to articulate the cause. The BA who can listen past the symptom to the underlying problem is already halfway to the solution.

• The BA bridges business and delivery. Process improvement almost always produces a requirement for change: a system change, a policy change, a role change, or some combination. The BA who leads the improvement work and then carries that requirement into the delivery process removes the translation gap that causes so many improvement initiatives to produce analysis without action.

• The BA understands the people side. Process improvement fails more often because of resistance and disengagement than because of poor analysis. The BA's stakeholder management skills are directly applicable to the work of bringing people along through change. This is not a generic observation. The specific skills covered in last week's series on stakeholder management are the same skills you need to take a process improvement initiative from diagnosis to implemented change.

The Cost of Documenting Broken Processes Without Fixing Them

There is a version of BA work where documenting the current state is the goal. You produce the as-is process map, hand it over, and move on. This version of the role is common in organisations where the BA function is positioned as a documentation service rather than an analytical one. The cost of this approach is real and it compounds. When a broken process is documented without being improved, it gets built into the new system. The inefficiency becomes structural. What was a process problem becomes a system problem, and system problems are significantly more expensive to fix than process problems because they require development resource, testing cycles, and re-deployment.

When a broken process is documented without question, the people who run it take that as validation. If the BA came in, mapped the process, and left without raising any concerns, the implicit message is that the process is acceptable. That makes subsequent improvement conversations harder because the organisation has been given reason to believe the status quo was approved. When improvement opportunities are consistently missed, the BA's value proposition shrinks. The BA who only documents is replaceable by cheaper alternatives: a junior analyst, a business administrator, or in some cases a process mapping tool. The BA who analyses, challenges, and improves is not replaceable. They are the person who changes things.

The Mindset Shift That Changes Everything

Process improvement starts with a single shift in how you approach a process workshop or a current state review.

Stop asking: what does this process do?

Start asking: why does this process exist, is it achieving that purpose, and where is it falling short?

The first question produces a map. The second produces an analysis. They sound similar. They lead to completely different conversations. When you ask why a step exists, you find process fossils like the three-signature requirement in the warehouse story. Steps that were introduced for a reason that no longer applies. Checks that duplicate each other. Handoffs that exist because of an organisational structure that changed two years ago.

When you ask whether the process achieves its purpose, you surface the gap between what the process is supposed to do and what it actually produces. That gap is where the improvement opportunity lives. When you ask where it is falling short, you get the stakeholders to name the pain. And once they have named it, they have a stake in fixing it.

This week we are going to build every practical skill you need to go from that mindset shift to a completed improvement initiative.

• Day 2: Root Cause Analysis. The three techniques every BA must know, how to use each one, and the mistakes that produce surface-level fixes.

• Day 3: Lean Thinking and Kaizen. How to see waste in a process, how to apply Lean principles without becoming a process engineer, and what Value Stream Mapping looks like in BA practice.

• Day 4: Leading an Improvement Initiative. How to structure the work, engage stakeholders, manage resistance, and measure whether the change actually worked.

• Day 5: The Process Improvement Toolkit. A practical reference guide to every tool and technique from this week, with a free downloadable resource to use on your next improvement project.

Go out and be successful.

Oluwatosin Ogunkoya | Flotog BA Insights | www.flotogbainsights.com

Tomorrow: Root Cause Analysis. The three techniques that find the real problem rather than the visible symptom, when to use each one, and the most common mistakes that lead BAs to fix the wrong thing.