Why Process Improvements Fail - and How to Fix Them with the Right Level of Process Thinking

@Stefani Markov's latest article explores how to choose the right approach:

Process Management (PM) for optimizing individual steps

End-to-End PM for cross-functional flow

Business Process Management (BPM) for enterprise-wide improvement

Systems Thinking for achieving true operational excellence

Each level expands the perspective — from fixing what’s in front of you to optimizing how everything connects.

Insight: Automation should follow improvement, not lead it.

Read the full article to see how applying the right level of process thinking helps organizations achieve sustainable, system-wide improvement.

In today’s fast-paced world, improving processes is essential for efficiency, quality, and business success. Many organizations struggle with process improvement because they apply the wrong approach or focus too narrowly, resulting in inefficiencies, duplicated work, or unintended consequences. 

Without clarity on the differences between Process Management (PM), End-to-End Process Management (E2E PM), Business Process Management (BPM), and Systems Thinking, improvements in one area may inadvertently create problems elsewhere, preventing organizations from achieving true operational excellence. 

Let's begin with the basics - what's what. 

• Process Management (PM): Focuses on improving individual processes in isolation, usually within one department or team. Improvements are local, often faster, but may create extra work elsewhere. 

• End-to-End Process Management (E2E PM): Looks at the entire process chain from start to finish, across departments. Optimizations consider handoffs, dependencies, and flow to avoid shifting work or creating bottlenecks. 

• Business Process Management (BPM): A structured approach that includes process modeling, automation, monitoring, and continuous improvement. Ensures processes are efficient, measurable, and sustainable. 

• Systems Thinking: Treats processes as part of a larger system, emphasizing interconnections, feedback loops, and unintended consequences. Focuses on optimizing overall system performance rather than individual steps. 

The evolution from Process Management to Systems Thinking can be visualized as a progression of scope and maturity — with automation fitting naturally as you move upward. 

If you’re like me and prefer a visual comparison, the table below shows how these approaches differ - with both finance and everyday-life examples - and how each connects to Continuous Improvement (CI) and Operational Excellence (OE). 

A quick reminder: Continuous improvement is how you improve. Operational excellence is what it looks like when you’ve built a culture around it. 

Why Process Improvements Can Backfire 

Improving a process may seem straightforward, but many organizations experience unintended consequences. This usually happens because the focus is too local - on a single step or department - rather than considering the end-to-end flow or system-wide impact. 

Example in Finance (R2R): 

Automating journal entry approvals speeds up that step, reduces manual effort, and increases throughput. However, reconciliations may now pile up because exceptions that were previously caught manually are missed, creating extra work downstream. 

Everyday Life Example: 

In a kitchen, you make chopping vegetables faster to save time. But if cooking and plating are not coordinated, you end up with ingredients ready at the wrong time, creating delays and stress for the whole meal. 

Both illustrate the same issue: local optimization versus system optimization. Improving one step in isolation - or automating it too early -can create new bottlenecks, errors, or inefficiencies elsewhere. 

Continuous Improvement (CI) and Operational Excellence (OE) 

Process improvement isn’t a one-time project - it’s a mindset. Continuous Improvement (CI) is the mindset of making incremental, ongoing enhancements, while Operational Excellence (OE) is the goal: a state where processes consistently deliver maximum value with minimal waste and risk. 

A key lesson I’ve learned from process automation is that speed alone doesn’t equal improvement. If a process is flawed, automating it will often amplify existing issues. For instance, a manual process that takes one hour with one error might, when automated, take 30 minutes but produce twice as many errors - creating even more rework downstream. 

In short: Improve first, then automate. 

Practical Guidance: Choosing the Right Approach 

Use PM when: 

• You need to optimize a single process quickly. 

• Dependencies are minimal, and risks of creating extra work elsewhere are low. 

• Tip: Avoid automating before improving the process. 

Use E2E PM when: 

• Processes span multiple teams or departments. 

• Coordination and handoffs are critical to avoid bottlenecks. 

• Tip: Map the end-to-end process before applying automation. 

Use BPM when: 

• You want to standardize, monitor, and automate processes. 

• You aim for sustainable, measurable improvements across multiple processes. 

• Tip: Apply automation after process improvement and ensure KPIs track the impact on downstream steps. 

Use Systems Thinking when Processes are highly interconnected.

• Local optimizations often create hidden downstream effects. 

• You are aiming for organizational-level operational excellence. 

• Tip: Model the entire system, anticipate feedback loops, and balance trade-offs before introducing automation. 

Tips to Avoid Local Optimization Pitfalls: 

• Map end-to-end processes before making changes. 

• Include cross-functional stakeholders in improvement discussions. 

• Simulate or model changes to anticipate downstream effects. 

• Use metrics for the full chain, not just individual processes. 

• Automation amplifies what exists — improve first, or you’ll just automate inefficiency. 

• Ensure executive-level commitment and invest in training to shift mindsets from departmental silos to cross-functional system ownership. 

• Leaders should ensure that improvement goals are aligned across departments before scaling automation — otherwise, local success can become enterprise inefficiency. 

Final Thought 

The real challenge in process improvement isn’t lack of effort - it’s lack of perspective. Many improvements fail because they’re made in isolation. True operational excellence comes from seeing how everything connects, not just fixing what’s in front of you. 

Whether you’re streamlining journal entries, managing an R2R close, or coordinating a kitchen dinner rush, the principle remains the same: think end-to-end, act system-wide, and let automation follow improvement - not lead it. 

Coming Next: Lessons from the Real World 

While understanding the theory behind Process Management, End-to-End Process Management, Business Process Management, and Systems Thinking is undeniably important, theory alone rarely captures the full picture. The real learning - and the real caution - often comes from seeing how these concepts play out in practice. 

In my experience, it’s the case studies and lessons learned that bring these frameworks to life. They show how even well-intentioned improvements can go wrong when context is ignored, or how success depends on the right balance between process design, governance, and culture. 

In the next article, we’ll look at real-world examples where process improvement efforts either delivered real transformation or went dramatically off course. We’ll start with the Queensland Health Payroll System - a project that began as a local process upgrade but turned into one of the most well-known examples of what happens when end-to-end and system-level thinking are overlooked. 

Each case will offer a simple takeaway: how to recognize which level of process thinking to apply - and how to avoid turning a good improvement into a costly problem. 

Ready? Let's talk.