Adas Insights
Be smart, choose data, make decisions.
Most people think process optimization is about fixing inefficiencies. It’s not.
It’s about untangling invisible chaos that no one fully understands, but everyone has an opinion on. It’s about dealing with people, ambiguity, and complexity that doesn’t show up in any documentation.
People tend to imagine it as something clean and logical: well-defined workflows, clear steps, quick wins, and maybe a bit of automation to make everything faster. There’s this assumption that it’s linear. Analyze the problem, fix what’s needed, things improve.
But the process of improving processes is nowhere near that.
In reality, it looks more like playing five completely different roles, often in the same week. You’re a detective one moment, a therapist the next. And the quality of your work depends less on your analytical tools and more on how well you can navigate people, corporate politics, and incomplete information.
Here’s what those roles actually look like.
The first time I worked on a “process optimization” project, I thought I’d be improving workflows. Instead, I spent most of my time figuring out what people were actually doing vs. what they said they were doing.
The Detective: What’s documented is rarely what’s actually happening
Before improving anything, you have to understand how work truly flows across teams, decisions, and daily operations. Not what people say happens. What actually happens behind the scenes.
At some point, you stop feeling like an analyst and start feeling like a detective. You talk to employees, compare versions of the truth, validate them against KPI data, question inconsistencies, and try to reconstruct how value is really being delivered.
Because processes are built by people, most of the time the real functioning process is an undocumented, inconsistent version that evolved simply to make things work. Half the job is understanding that reality. The other half is getting everyone to agree on it.
“Excellent!” I cried. “Elementary,” said he.”― Arthur Conan Doyle, The Complete Sherlock Holmes
The Doctor: The problem is almost never where people point
Most times, stakeholders come in with a clear diagnosis. “We have delays.” “We need automation.” “The issue is X.”
But most of the time, those are just symptoms.
Delays are symptoms. Misalignment is the disease. When you dig deeper, the real issues tend to be things like unclear roles, messy handoffs, conflicting priorities, or incentives that push teams in different directions.
Your job is to analyze the symptoms, diagnose the actual disease, and treat it effectively. The visible problem is rarely the root cause. And treating symptoms without addressing the root cause only buys time.
“If you’re looking for a thank you, you’re in the wrong profession.” ― Dr. Michael Robinavitch, The Pitt (HBO Max Series)
The Negotiator: Most of the work is alignment, not analysis
Every team sees the process differently, and all of them are partially right.
Operations, commercial, finance, quality, leadership: each one experiences the process from their own context, and those perspectives don’t always align. So you’re not just analyzing workflows. You’re negotiating realities.
A big part of the job is getting people to agree on what’s actually happening before you can improve anything. Because if there’s no shared understanding of reality, there’s no foundation for change. And if you’re not careful about how you handle those conversations, you can cost someone their credibility, or even their job.
“We cannot negotiate with people who say what’s mine is mine and what’s yours is negotiable.” [ The Berlin Crisis: Radio and Television Address to the American People (The White House, July 25, 1961)]”― John F. Kennedy
The Therapist: Optimization threatens people before it helps them
Optimization sounds great, until it changes how someone works.
You’re not just improving a process. You’re changing habits, ownership, and sometimes even control. And people don’t resist change because they’re irrational. They resist it because change carries risk, and risk feels personal.
So before you can implement anything, you have to manage fear. You have to understand whose identity is tied to “the way things have always been done,” who feels like the new process is a verdict on how they’ve been working, and who is quietly waiting for it to fail.
Even if a solution is objectively better, adoption is never guaranteed. It’s subjective. It depends on how people perceive the change, how easy it is to follow, and whether it fits into their day-to-day reality.
That’s why process optimization is also about sitting with people’s discomfort and making the path forward feel safe enough to actually walk.
“By changing nothing, nothing changes.” ― Tony Robbins
The Surgeon: You don’t cut until you fully understand what’s inside
One of the most common reactions to inefficiency is: “let’s just automate it.” It sounds decisive. Logical. Like progress.
But a surgeon doesn’t operate based on a hunch. They study, they diagnose, they understand exactly what they’re working with, because cutting in the wrong place doesn’t fix the problem. It creates new ones.
Automation without clarity works the same way. If your process is messy, you get faster chaos. If roles are unclear, you automate confusion. If your data is inconsistent, you scale bad decisions.
Before automating anything, you need to understand why things are failing. Because investing in automation without fixing the foundation isn’t progress. It’s just scaling the problem.
“We all make mistakes, and we all pay a price.” ― Season 1, Episode 7 “Fidelity”, House M.D. (TV Series)
The through line: none of this is really about processes
Process optimization isn’t complicated, but it does require discipline across all five of these roles.
It starts with understanding before improving: taking the time to deeply analyze reality as it is, not as it’s described. Then comes clarity over complexity, because clear roles, clear handoffs, and clear rules are what make processes actually scalable.
It also means designing for how people actually work, not ideal scenarios. People don’t follow perfect processes. They follow functional ones. So you build around real behavior, not theoretical models. And finally, adoption over perfection: a good enough process that people consistently follow is far more valuable than a perfect one that no one uses.
Process optimization isn’t about making things perfect. It’s about making complexity manageable, decisions clearer, and work flow in a way that holds up in the real world, with real people, under real pressure.
And most of the time, that has less to do with tools and everything to do with understanding how people and systems interact.
If you work in operations, quality, or business analysis, you’ve probably worn a few of these hats yourself. Which role do you find hardest to play?
[contact-field type="rating" label="Did you liked this article?" labelclasses="wp-block-jetpack-label" labelhiddenbyblockvisibility="" inputclasses="" iconstyle="stars" fieldwrapperclasses="wp-block-jetpack-field-rating"]<div> </div>[/contact-field]
Leave a Reply