Fixing the Wrong Thing Faster Changes Nothing.

Mapping one process is straightforward. Optimizing an organization is a different problem, and it is mostly a question of sequence. Which process do you fix first, what does that unlock, and how do you avoid the common outcome where four departments each improve something and the customer notices nothing.

That outcome is more common than most owners realize. Teams optimize locally, everyone reports progress, and total throughput stays flat. I have watched it happen across 35+ years in engineering and manufacturing organizations, and the cause is almost always the same: work was done everywhere except at the one place that was actually limiting the business.

Why Local Improvements Often Change Nothing

Picture a business where quoting is slow, production is comfortable, and shipping is fast. If you improve production, nothing changes for the customer, because work still arrives at the same rate quoting can release it. You have added capacity where capacity was not the problem.

This principle is formalized in the Theory of Constraints, which holds that every organization has at least one constraint limiting how much of its goal it can produce, and that only improvements at that constraint increase overall throughput. The Lean Enterprise Institute describes a constraint as any factor limiting the organization from getting more of what it strives for, and notes that constraints are frequently not on a production floor at all: market demand or a sales function's ability to convert demand into orders can be the real limit. Verified 22 July 2026.

That last point matters for smaller businesses. Owners often assume the bottleneck must be operational, when the actual constraint is a single overloaded person, an approval that only one director can give, or a capability the business does not have.

How to Find Your Constraint

1. Follow the delays, not the complaints. Where does work physically sit and wait? A queue in front of a step is the clearest signal that the step is limiting.
2. Ask where work piles up before someone touches it. Unstarted files, unquoted enquiries, jobs waiting on approval. Accumulation points to the constraint immediately downstream.
3. Look for the always-busy resource. The person, machine, or team that is never idle and always behind. If everything waits on one place, that is usually it.
4. Test it against a thought experiment. If this step could produce twice as much tomorrow, would the business deliver more? If yes, you have found it. If no, keep looking.
5. Check outside operations. If nothing internal is limiting, the constraint may be demand, cash, or a capability you lack. Those are real constraints with different solutions.
6. Confirm with the people doing the work. They usually know exactly where the jam is and have rarely been asked directly.

The Sequence That Works

First, get more from the constraint before spending on it. A limiting resource is often idle for reasons that cost nothing to fix: waiting for materials, doing work someone else could do, sitting through meetings, or handling exceptions that should never have reached it. Protecting the constraint's time is usually the cheapest capacity you will ever buy.

Second, align everything around it. Upstream steps should release work at the pace the constraint can absorb, not at the pace that makes upstream teams look productive. Downstream steps should be ready when output arrives. This step is uncomfortable, because it means some parts of the business deliberately run below their maximum, and it conflicts with how most organizations measure departmental performance.

Third, expand it if it is still limiting. Now spending makes sense: hire, buy equipment, add a shift. Doing this before the first two steps means paying for capacity you already had but were wasting.

Fourth, find the next one and expect it to have moved. Relieve one constraint and another appears somewhere else. That is the system working, not a failure. The mistake is assuming the old constraint is still the problem and continuing to invest there out of habit.

How Do You Keep the Gains While Moving On?

This is where organization-wide efforts usually fall apart. A team improves a process, attention shifts to the next area, and within a year the first process has drifted back. Three things prevent it.

Write down the new standard, plainly. Not a procedures manual nobody opens. A short description of how the work is now done, visible where the work happens, that a new employee could follow.

Give it an owner and a review date. One named person, one recurring check. Without both, the change belongs to nobody and quietly expires.

Keep measuring the number you improved. If it was worth a project, it is worth a monthly glance. Drift shows up in the number long before anyone notices it in the work.

What Determines Whether This Sticks?

How Do We Work With Organizations in Durham Region?

Gurley Leadership Solutions is based in Ajax and works with organizations across Whitby, Oshawa, Clarington, Pickering, Barrie, Mississauga, and the wider Durham Region and Greater Toronto Area, in sectors including manufacturing, healthcare, not-for-profit, engineering, and operations. Most conversations start by working out where the actual constraint sits, because that single answer usually reorders the whole improvement plan. For the underlying methodology, see the guide to Lean Six Sigma implementation, or read more about Malcolm Gurley.

Frequently Asked Questions

How do I optimize workflow across my whole organization?

Improve the constraint rather than everything. Every organization has one process limiting total output at any time, and improvements elsewhere create local efficiency without increasing what the business delivers. Find the constraint, get more from it before spending on it, align surrounding processes to keep it fed, expand it if it still limits, then find the next one.

How do we identify our constraint?

Follow the delays rather than the complaints. Look for where work physically waits, which resource is never idle and always behind, and where unstarted work accumulates. Then test it: if that step could produce twice as much tomorrow, would the business deliver more? If not, the constraint is elsewhere, possibly outside operations entirely.

Why did our improvements not increase output?

Almost always because the work happened somewhere other than the constraint. Improving a step that was not limiting anything produces local efficiency and no additional throughput. It is a common and expensive pattern, and the fix is to establish where the actual limit sits before choosing the next project.

How do we stop improvements from sliding back?

Three things. Write the new standard down plainly and keep it visible where the work happens. Give it one named owner and a recurring review date. And keep measuring the number you improved, because drift appears in the measure well before anyone notices it in the work.

How do we get started?

Book a free 15 minute phone call with Malcolm Gurley through the button above, or call 416.669.7644, Monday to Friday, 8:00 AM to 6:00 PM. There is no cost and no obligation for the initial conversation.

Gurley Leadership Solutions Inc. delivers leadership development and organizational improvement programs licensed through Leadership Management International; every engagement is customized and outcomes vary by organization. Guidance in this article is general; the correct sequence and priorities depend on the specific organization and its constraints. Results described from prior engagements, including the Honeywell figures, describe those engagements and are not a guarantee of future results. Return-on-investment figures, including any 10:1 reference, describe typical results from prior engagements and are not a guarantee of future results. This article is general information, not a proposal and not an offer.