Fix the process, not just the problem it created
When the same problem keeps happening, I don't want to keep fixing the result — I want to understand why the process keeps allowing it to happen. LeanLine Advisory helps businesses understand how work actually gets done, identify where time and resources are being lost, and improve the process in a way that makes sense for the people using it. Not a perfect-looking process map — work that's easier, more consistent, and easier to manage.
The kinds of issues we look at
These are the kinds of issues I look at.
Same Mistakes, Again
The same errors keep happening no matter who's doing the work.
Constant Workarounds
Employees have quietly built their own way around the official process.
Too Many Steps
A simple task requires far more steps than it should.
Duplicate Data Entry
People enter the same information more than once.
Waiting on Approvals
Work sits idle waiting for someone to sign off or answer a question.
Everyone Does It Differently
The same process looks completely different depending on who runs it.
Customers Feel the Delay
Customers experience delays even though employees are working hard.
One Person, One Process
The process depends heavily on a single employee.
Nobody Knows Why
A step still happens and nobody's sure why it's still there.
Procedures, Unused
Documented procedures exist, but employees don't actually follow them.
Grown Business, Old Process
The business has changed. The process hasn't kept up.
Technology Added, Still Manual
New software went in, but the process still feels like manual work.
Make the invisible work visible
Once we can see the whole process, the problems usually become much easier to identify.
Process Mapping
We don't just look at the procedure — we look at what employees actually do: where responsibility changes, what gets approved, where people wait or create workarounds.
Root-Cause Analysis
The first problem we see isn't always the real one. A late order might really be an inventory problem, an approval problem, or rework from earlier in the process. We keep asking why.
Bottleneck Identification
A process only moves as fast as its slowest consistent point — a person, a system, an approval, a vendor. We find it so improvement efforts land where they matter.
Waste Reduction
A business can be extremely busy and still full of unnecessary work — waiting, re-entering data, correcting mistakes. The goal isn't to work harder, it's to stop wasting time.
Standardization
We find out which method actually works best first, then build a practical standard around it — not just force everyone to follow whatever's already in place.
Roles & Responsibilities
A lot of process problems are really ownership problems. We define responsibility at every handoff so nobody has to guess who owns the next step.
Approval & Decision Processes
Approvals matter, but they can also become bottlenecks. We ask what risk each one is actually controlling — and whether the control still fits the risk.
Handoff Improvement
Many problems happen between departments. We look at what information needs to move, who owns the transfer, and how the receiving person knows it's ready.
SOPs & Process Documentation
Documentation should support the work, not become another task nobody wants to maintain. We match the format — checklist, workflow, or full procedure — to the process.
Process Controls
A good control prevents or detects a meaningful problem; a bad one just creates work. We evaluate whether existing controls actually earn their keep.
Data & Performance Measurement
We measure what tells us whether the process is actually improving — cycle time, rework, backlog, errors — not data for its own sake.
Technology, AI & Automation
Technology can improve a process — or make a bad one harder to understand. We simplify first, then determine what's worth automating.
Processes that are slowing the business down
This can apply to administrative processes, operations, project work, manufacturing, service delivery, reporting, approvals, customer workflows, and many other areas.
Seven steps from problem to proof it's better
Start With the Problem
Tell me what isn't working — that's where we begin.
Follow the Process
End to end: who's involved, where work waits, where it differs from the official version.
Identify the Cause
Separate the visible problem from the reason it keeps happening.
Simplify
Look for what can be removed or combined before adding anything new.
Improve
Redesign the process around what the business actually needs.
Test
See how the change holds up when employees actually use it.
Measure
Confirm it's faster, more accurate, or easier — or keep working on it.
Questions business owners actually ask
How do I know if a process actually needs improvement?
Look for friction.
Where do employees complain? Where do customers wait? Where are mistakes happening? Where is work being repeated? Where does one person constantly have to intervene? Where does work pile up?
Those are usually signs that something in the process deserves a closer look.
How do you identify what's wrong with a process?
I follow it.
I want to understand what happens from the first step to the last and compare what is supposed to happen with what actually happens. Then I look at the data, the handoffs, the waiting, the rework, and the workarounds.
The process usually tells you where the problem is if you take the time to follow it closely.
What is process mapping, and do we really need it?
Process mapping is simply a way to make the workflow visible.
It helps us see who does what, in what order, what information is needed, and where responsibility changes. It doesn't need to become a complicated diagram.
Sometimes a simple map is enough to expose a problem everyone has been dealing with for years.
Why do employees create workarounds?
Usually because something in the official process doesn't work well for them.
Maybe it takes too long. Maybe the system is difficult. Maybe a required step doesn't make sense. Maybe information is missing.
A workaround isn't automatically bad. Sometimes it's a clue. I want to understand why it exists before deciding whether it should be eliminated.
We already have SOPs. Why are our processes still inconsistent?
Because having a procedure doesn't mean the procedure reflects reality.
Maybe it's outdated. Maybe employees weren't trained on it. Maybe it doesn't cover common exceptions. Maybe nobody uses it because it's too complicated.
I compare the documented process with the actual process. That's often where the problem becomes obvious.
Should every process be standardized?
No.
Some processes need flexibility. Others benefit greatly from consistency. I look at the risk, frequency, complexity, and impact of variation.
If different approaches create quality problems, delays, or errors, standardization may help. But I don't standardize something just so we can say it has a standard.
How can we reduce the number of approvals in a process?
First, understand why each approval exists.
What is it supposed to prevent? What authority does that person have? Does the approval actually catch problems? Could a rule or threshold replace it? Could authority be delegated?
Sometimes the approval is necessary. Sometimes it became part of the process years ago and nobody has questioned it since.
Our process is slow. Should we add more employees?
Maybe, but I wouldn't assume capacity is the issue.
I would first look at where the time is going. Are employees working continuously? Or are they waiting? Is one step creating a backlog? Is information missing? Are people correcting errors? Are approvals holding up the work?
If demand truly exceeds capacity, additional employees may make sense. But I want the process to show us that first.
How can we reduce rework?
Follow the rework back to where the problem starts.
The person fixing the mistake may not be where the mistake was created. Maybe incomplete information enters the process early. Maybe requirements aren't clear. Maybe the quality check happens too late.
The objective is to prevent the error earlier instead of becoming better at correcting it later.
What is the difference between a bottleneck and a staffing problem?
A staffing problem means available capacity doesn't meet the workload. A bottleneck means one part of the process is limiting the flow.
Sometimes the bottleneck is staffing. Sometimes it isn't. That's why I don't jump directly to hiring — I want to know exactly what is restricting the process first.
How do we improve a process without upsetting employees?
Involve the people doing the work.
They usually know which parts of the process are frustrating, unnecessary, or difficult. That doesn't mean every suggestion becomes the solution.
But changing a process without understanding how employees actually use it creates unnecessary resistance. People are much more likely to support an improvement that genuinely makes their work easier.
How do you know whether an improvement worked?
Measure something that matters before and after the change — turnaround time, errors, backlog, rework, cost, or customer complaints.
The measure depends on what we were trying to improve.
If we can't explain how the process is better after the change, we need to keep working on it.
How much process documentation do we need?
Enough to make the work reliable. Not more.
A complicated process may need detailed documentation. A simple recurring task may only need a checklist.
I want the documentation to be used. If nobody reads it, it doesn't matter how complete it is.
Can process improvement reduce costs?
Yes, especially when cost is being created by waste.
Rework costs money. Waiting costs money. Duplicate work costs money. Poor scheduling costs money. Errors cost money. Unnecessary software and manual processes cost money.
I prefer finding those costs inside the process before jumping straight to cutting resources.
Can process improvement improve customer service?
Absolutely.
Customers often feel the effect of internal process problems — delays, inconsistent answers, providing information twice, waiting while employees figure out who owns the issue.
Improving the internal process can improve the customer experience without adding more customer-service staff.
How do we improve a process that crosses several departments?
Follow the handoffs carefully.
Cross-functional processes often break where responsibility moves from one department to another. I want to know what information is passed, who owns the next step, how they know it's ready, and what happens when something is incomplete.
Many cross-department problems are really handoff problems.
Should we automate a process before improving it?
Usually, no.
If the process is inefficient, automation may simply lock the inefficiency into the system.
I prefer to simplify the process first — remove unnecessary work, clarify responsibilities, fix the flow. Then determine what is worth automating.
How do we know which process to improve first?
Start with impact. Which process creates the most delays? The most errors? The most customer complaints? The most frustration? The highest cost? The biggest risk?
Then consider effort. Sometimes a relatively simple change can solve a major recurring problem. Those are great places to start.
Our process worked fine before. Why doesn't it work anymore?
Because the business may have changed — more customers, more employees, more transactions, more systems, more approvals, more exceptions.
The process may not be bad. It may simply have outgrown the environment it was designed for. That's common in growing businesses.
Can you help if we don't know which process is causing the problem?
Yes. You can start with the symptom.
Maybe customers are waiting. Maybe employees are overwhelmed. Maybe projects keep slipping. Maybe errors are increasing. Maybe something simply feels harder than it should.
We can trace the problem back through the work until we understand where the process is breaking down.
What does a process improvement engagement with LeanLine look like?
I start with the problem you're experiencing. Then I follow the process — how the work is supposed to happen, how it actually happens, where people wait, where mistakes occur, where responsibility changes, and where employees have created their own ways around it.
From there, we identify the root cause, remove unnecessary work, and develop a better way of doing it. The solution might be very simple. It might require a larger redesign. But I don't decide that before understanding the process.
The objective isn't to make the process look better on paper. It's to make the work actually work better.
Better processes make better businesses
Most businesses don't need every process redesigned — they need the ones creating the most problems fixed. LeanLine Advisory helps find those problems, understand what's causing them, and make practical improvements that reduce unnecessary work and make operations easier to manage.