Principles

A company crisis rarely emerges overnight.

Deadlines do not simply stop being met one day. Customers do not all become dissatisfied at once. Money does not suddenly run out, and the best people do not leave without prior cause.

Before a crisis, there are almost always smaller warning signs:

• the same problems keep recurring;
• work queues are growing;
• decisions are taking increasingly longer;
• some people are constantly working overtime;
• more and more exceptions are being made for customers;
• managers are becoming increasingly involved in day-to-day operations;
• achieving results requires more and more manual work;
• the organization is getting bigger, but not more capable.

These signs are often treated as separate problems.

Sales needs to forecast better. Project management needs a new tool. Employees need to take more responsibility. Customer support needs one more person.

In reality, all these problems may stem from the same constraint.

A bottleneck is not the loudest problem in a company.

It is the point that limits the performance of the entire company.

The bottleneck is not always where the problem becomes visible

When customer support is overloaded, it seems logical to conclude that the bottleneck is in customer support.

But the real cause of the workload may be a poorly designed product, promises made by sales that cannot be kept, or inadequate customer onboarding.

When development cannot complete its tasks, it may seem that more developers are needed.

The real cause may be constantly shifting priorities, unclear requirements, or the fact that no one decides which features will not be built.

When sales are not growing, it may seem that the problem lies with the salespeople.

In reality, the company may be selling the wrong customer a solution whose value is not clear enough.

The effect of a bottleneck usually becomes visible somewhere other than where its cause lies.

That is why the true constraint cannot be found simply by looking at the longest work queue, the worst number, or the highest volume of complaints.

You need to look at where the problem begins and how it moves through the company.

First, decide which outcome the bottleneck is limiting

A bottleneck always exists in relation to a specific outcome.

If the company does not know which outcome it most wants to improve right now, every department may identify a different bottleneck.

For sales, the problem is too few leads.

For marketing, the problem is low visibility.

For production, the problem is the exceptions made by sales.

For finance, the problem is slow cash collection.

All of them may be talking about real problems, but those problems may not be limiting the company’s most important outcome.

Before diagnosing the issue, the company must define what it is trying to achieve.

For example:

• more profitable customers;
• faster delivery;
• better customer retention;
• greater production capacity;
• more stable cash flow;
• less dependence on the founder;
• bringing a new product to market;
• better profitability.

Only then can you ask: which single constraint is doing the most to prevent that outcome?

When the objective is unclear, the company starts trying to improve everything at once.

This consumes resources but may not change the company’s overall performance.

View the company as one end-to-end value stream

Dividing a company into departments helps organize accountability.

When diagnosing problems, however, it can fragment the overall picture.

The customer does not see marketing, sales, product development, delivery, and finance as separate functions. To the customer, there is one end-to-end experience, from the moment a need arises to the moment the promised outcome is delivered.

To find the bottleneck, you need to look at that same whole.

For example, the value stream may be:

1. The right customer notices the company.
2. The customer understands the offer.
3. Sales reaches a decision.
4. The necessary information is handed over to delivery.
5. The product or service is prepared.
6. The customer receives the promised outcome.
7. The customer pays.
8. The customer stays and buys again.

Then, at each stage, ask:

• How much work enters this stage?
• How much comes out?
• How long does work wait here?
• How many errors occur?
• How much rework is required?
• How many exceptions are there?
• Which person or decision is holding up the work?
• Does the stage’s throughput meet the needs of the next stage?

The bottleneck is often the point where work begins to accumulate in front of it while the next part of the process waits.

But it may also be a decision, information, or expertise—not merely a shortage of people.

A queue is one of the earliest signs of a bottleneck

People usually talk about a crisis when a deadline has already been missed.

A bottleneck emerges much earlier.

A queue begins to form in front of it.

The queue may be visible:

• unanswered sales inquiries;
• unfinished projects;
• defects waiting to be fixed;
• unapproved proposals;
• unresolved customer requests;
• unissued invoices.

But the queue may also be invisible:

• decisions someone is waiting for;
• information sitting in one person’s inbox;
• tasks people keep in their personal notes;
• ideas that have received neither a yes nor a no;
• problems employees have not dared to raise with their manager;
• customers who are waiting but have not yet filed a formal complaint.

If the queue grows week after week, the problem is no longer a temporary spike in workload.

More work is entering the system than the critical stage can process.

In this situation, making the rest of the company faster does not help.

It only creates an even larger queue in front of the bottleneck.

Look at where the strongest people are always deployed

One very clear sign of a bottleneck is where the company’s best people repeatedly have to step in.

If the same specialist resolves every complex customer case, the company depends on that person.

If the CEO has to close every major sales deal, the sales process cannot operate independently.

If one project manager has to rescue every late project, quality comes from that person rather than from the system.

If the technical lead is constantly fixing other people’s mistakes, the problem is likely in development inputs, the quality process, or capability.

Strong people can conceal a bottleneck for a long time.

They work harder, solve problems quickly, and keep customers satisfied. To management, the system may appear to be working.

In reality, the system works only because of those people’s extra effort.

The question is not simply who is the busiest person in the company.

You need to ask:

• Whose absence would bring the company’s work to a halt?
• Who handles all the exceptions?
• Who holds information that is not in the system?
• Who approves decisions that others could make?
• Who makes it possible to achieve the outcome even when the process itself does not work?

If the answer is repeatedly the same person, the company has identified at least one potential bottleneck.

The bottleneck may be in decision-making

In many companies, performance is not limited by people’s capacity to work.

It is limited by the speed of decisions.

The work is ready but waiting for approval.

A proposal could be sent, but the manager has not approved the price.

The project could move forward, but a conflict between priorities remains unresolved.

The employee knows what to do but does not know whether they have the authority to decide.

This kind of bottleneck is especially dangerous because, from the outside, people appear passive.

The manager may conclude that the team lacks initiative.

In reality, the organization has learned that decisions made independently may later be reversed.

Signs of a decision-making bottleneck include:

• managers attend a very large number of meetings;
• the same topics move from one meeting to another;
• increasingly more information is gathered before a decision is made;
• people seek approval even for small matters;
• problems pile up when the manager is away;
• management discusses actions but does not make clear choices;
• no one knows who has final decision-making authority.

The solution to this kind of bottleneck is not more people.

What is needed is a clear decision-making framework: who decides, based on what information, and within what timeframe.

The bottleneck may be the wrong work

Sometimes the problem is not that the company works too slowly.

It is doing too much work that does not need to be done.

The wrong customers create exceptions.

A weak product generates recurring questions for customer support.

An unclear strategy creates parallel projects.

The absence of a pricing logic brings unprofitable orders into the company.

A manager’s need for control creates reports and approval steps.

In this situation, the capacity of the bottleneck should not be increased.

The amount of work reaching it should be reduced.

This may mean:

• ending service to some customers;
• shutting down unnecessary projects;
• simplifying the product;
• reducing exceptions;
• fixing the root cause of errors;
• removing duplicate controls;
• moving decisions closer to the work;
• stopping some activities entirely.

The cheapest way to increase a bottleneck’s capacity is often to stop burdening it with work that does not create enough value.

The bottleneck may be a mismatch between a person and a role

When someone in a critical role cannot deliver the required outcome, the entire system begins to adapt around them.

Other people check their work.

Deadlines are given larger buffers.

Some responsibility quietly shifts to managers.

New layers of coordination are built around the problems.

After a while, the entire process appears complex.

In reality, much of the complexity may come from trying to use the system to keep someone working in a role that does not fit them.

This does not automatically mean that the person is bad or should be dismissed.

The cause may be:

• unclear expectations;
• missing expertise;
• insufficient training;
• an excessively broad area of responsibility;
• a lack of decision-making authority;
• a mismatch between the person’s strengths and the nature of the work;
• conflicting directions from the manager.

But it must be assessed honestly.

If other people’s results are repeatedly held up by one person’s work, this is not merely an HR issue.

It is a risk to the company’s operations.

The bottleneck may be outside the company

Not every bottleneck can be resolved by improving internal ways of working.

The company’s performance may be limited by:

• a market that is too small or shrinking;
• low customer readiness to buy;
• a lengthy regulatory process;
• a critical supplier;
• limited raw materials;
• dependence on a single platform;
• a partner’s speed of decision-making;
• the customer’s own ability to implement the solution.

Even in this case, management must define the constraint precisely.

“The market is bad” is not a sufficient diagnosis.

Is there no need in the market?

Are there too few of the right customers?

Does the buying decision take too long?

Is the cost of sales too high?

Is the customer unable to realize value until they have done a large amount of work themselves?

The more precisely the external constraint is defined, the more options the company has.

It can change the target audience, offer, pricing, channel, partner, or entire business model.

A vague external problem cannot be managed.

A strategy can be built around a specific constraint.

Do not confuse the bottleneck with the worst-performing area

The department with the weakest performance is not necessarily the company’s bottleneck.

If that department’s performance is improved but the company’s overall performance does not change, resources were spent in the wrong place.

For example, marketing may generate too few inquiries.

But if the sales team can process only half of the inquiries it already receives, increasing marketing volume will not help. It will create more unused opportunities.

Production may be working slowly.

But if sales does not bring in enough orders, speeding up production will not improve the company’s performance.

Customer support may respond slowly.

But if most requests are caused by a single recurring product defect, the product should be fixed rather than merely increasing response speed.

A useful test question is:

“If we improve this area’s performance twofold, will the company’s most important outcome improve as well?”

If the answer is no, this is probably not the primary bottleneck.

Look for deviations, not just averages

Averages can conceal a bottleneck for a long time.

Average delivery time may be within target even though some projects are severely delayed.

Average customer satisfaction may be good even though the most valuable customers are dissatisfied.

Average workload may appear normal even though two critical people are constantly working overtime.

Average sales conversion may remain steady even though results for one customer segment have already fallen sharply.

A bottleneck often first appears in deviations:

• steadily increasing waiting times;
• growing variation in outcomes;
• the number of exceptions;
• the frequency of rework;
• a disproportionate workload on certain people;
• differences in profitability between customer segments;
• repeated last-minute rescue operations to meet deadlines.

The average shows how the company is doing overall.

Deviations show where the system is beginning to break down.

Employees often see the bottleneck before management does

The people who do the day-to-day work usually know very well where time is being lost.

They know:

• which information they constantly have to chase;
• which approvals take too long;
• which customer creates an unreasonable amount of work;
• which error is fixed repeatedly;
• which tool creates extra work;
• which process exists only on paper;
• whose absence brings work to a halt.

Management may not receive this information because problems are resolved before they reach senior levels.

Conscientious employees do not want to complain. They find workarounds, add manual steps, and keep the system running.

That is why it is not enough to ask: “Is everything all right?”

You need to ask more specific questions:

• What work do you do repeatedly even though it should not be necessary?
• What do you spend the most time waiting for?
• Which problem do you solve again every week?
• Which activity creates no value for the customer or the company?
• Which decision could you make yourself but are currently not allowed to?
• If one person left tomorrow, which work would come to a halt?
• Which problem do you think management underestimates?

These answers may reveal more about the bottleneck than yet another general performance report.

The bottleneck must be validated with a small experiment

The initial diagnosis may be wrong.

That is why management should not immediately undertake a major restructuring, hire a new team, or buy an expensive system.

First, it must test whether the suspected constraint truly affects the company’s overall performance.

If we believe the problem is slow decision-making, we move decision-making authority closer to the work in a limited area and measure the outcome.

If we believe the bottleneck is burdened by the wrong customers, we stop offering certain exceptions and observe how workload and profitability change.

If we believe the problem lies in one stage of the process, we temporarily increase its throughput or reduce the work reaching it.

If the company’s overall performance improves, the diagnosis was probably heading in the right direction.

If nothing significant changes, the next constraint must be found.

Finding the bottleneck is not about winning an argument in a meeting.

It is a testable hypothesis.

A bottleneck can never be eliminated permanently

When one constraint is removed, the constraint moves elsewhere.

This is normal.

If sales begins to perform better, the next bottleneck may emerge in delivery.

If delivery is automated, the constraint may move to customer onboarding.

If responsibility is distributed appropriately, missing expertise may become visible.

If the wrong customer segment is removed, insufficient marketing volume may become the next problem.

A good company is not a company without bottlenecks.

A good company knows how to identify its primary constraint quickly, manage it deliberately, and notice when the constraint has moved.

Problems arise when the organization continues improving the old bottleneck after the company’s true constraint has already moved elsewhere.

An early warning system must measure causes, not just effects

During a crisis, companies usually look at lagging indicators:

• revenue fell;
• profit disappeared;
• a customer left;
• a project was delayed;
• an employee left;
• cash is running out.

These show that the problem has already affected the outcome.

An early warning system must monitor the signals that precede it:

• growth in work queues;
• decision-making time;
• volume of rework;
• number of customer exceptions;
• frequency of recurring errors;
• overtime worked by the best people;
• number of times the founder intervenes;
• number of projects in progress;
• time to customer value;
• lengthening collection times;
• variation in quality;
• tasks left without a clear owner.

A company does not need hundreds of metrics.

It needs a handful of indicators that provide early warning that its most important workflow is beginning to clog.

Seven questions for finding the real bottleneck

When a company’s performance begins to deteriorate, management should answer seven questions.

1. Which single outcome do we most want to improve right now?

1. What stages make up the creation of this outcome?

1. In front of which stage does the most work or waiting time accumulate?

1. Where do the most errors, rework, and exceptions occur?

1. The absence of which person, decision, or piece of information most often brings work to a halt?

1. If we improve the performance of this area twofold, will the company’s overall performance improve?

1. What small experiment can we use to test this assumption quickly?

If these questions have not been answered, the company should not choose a solution yet.

Otherwise, it may hire people, buy software, and restructure an area that was never the true constraint.

A crisis begins when early warning signs are treated as normal

A bottleneck rarely turns into a crisis because of a single mistake.

It turns into a crisis when the organization becomes accustomed to its symptoms.

Constant overtime is recast as dedication.

A growing work queue is recast as a sign of strong demand.

The manager’s constant intervention is recast as strong leadership.

Customer exceptions are recast as flexibility.

Manual fixes are recast as the normal way of working.

To identify the problem, it is not enough for management to look at results.

It must look at the effort, waiting, and rework required to achieve those results.

The real bottleneck is often visible long before the crisis.

The question is whether the company knows how to see it or has already learned to live around it.

Preventing a crisis does not begin with reacting faster.

It begins with the ability to find the right problem before the entire company is forced to react to it.

Mikk OrglaanChalleng.ist