Your team is busy all day. Orders are waiting, decisions are delayed and unfinished tasks keep piling up. A common first thought? We need another employee. But what if the problem is not the number of people? What if work is not moving forward because every task has to pass through too many handovers, approvals, waiting periods and unnecessary steps? In that case, hiring another person may not solve the problem. It may simply increase the amount of work waiting at the same constraint.

Before expanding your team, check where your process is losing time.

At Yoptis, we therefore do not start business process optimisation by asking how to get people to work faster. We start by asking: What is stopping work from moving faster from start to finish?

What is a bottleneck in a business process?

A bottleneck is a part of a process that limits its capacity or throughput. It may be a machine, an employee, an information system or a physical constraint. It may also be something far less obvious: an approval rule, unclear responsibility, a handover between departments or a decision everyone is waiting for.

To illustrate, imagine a company where sales brings in orders quickly and administration processes them as they arrive, but dispatch can only begin once one person has given approval. Every department is busy. Yet if orders spend most of their time waiting for approval, speeding up administration will not necessarily shorten the time until dispatch.

Completing an individual task faster does not necessarily mean a faster process.

7 signs that work is not flowing well

1. The task is completed quickly, but the overall process takes too long

Preparing a document may take a few minutes, yet several days pass between the request and completion. This usually means you need to examine two things separately: how long someone actively works on the task and how long the task waits.

What to check: For the five most recently completed cases, record the start time, completion time and any waiting periods in between.

If most of the time passes without active work, first investigate why the work is waiting.

2. Tasks keep waiting for the same person

One person approves orders, handles exceptions, makes decisions and answers questions from several departments. They may be very capable. That may be precisely why, over time, they have become the person almost everything has to go through. The problem is not necessarily that person. It may be the process’s dependence on a single decision point.

What to check: Which activities stop when this person is absent? Which decisions truly require their judgement, and which could follow a predefined rule?

3. The number of tasks started grows faster than the number completed

New projects, orders and activities begin every day. The team looks productive, but the list of unfinished work keeps growing. Starting more work does not necessarily mean completing more work. It often means more coordination, more interruptions and more waiting.

What to check: How many tasks were started last week, how many were completed and how many are still open?

4. Priorities change almost every day

Task A is important until urgent task B arrives. Then C comes along.

Task A remains unfinished, B is interrupted and C becomes the new priority.

Occasional urgent changes are inevitable. The problem arises when constantly changing priorities becomes the normal way of managing work.

What to check: How many times during the week was work already in progress interrupted by a new priority? Which tasks stalled as a result?

Putting more pressure on employees does not necessarily improve the flow of work.

5. The same information is transferred between several systems

A piece of information is already in the CRM, but someone enters it again into the order management system, then into the accounting software and finally into Excel.

Duplication creates extra work and opportunities for errors. But before automating such a procedure, it is worth checking why it exists in the first place.

What to check: Where does the information originate, who enters it again and which transfers are necessary for business or control requirements?

Sometimes an integration between systems makes sense. In other cases, an unnecessary record can be removed or a rule simplified.

The aim is not to automate everything. The aim is to eliminate unnecessary work.

6. Errors and rework keep recurring

Someone completes a task, only for the next department to return it for corrections. Information is missing, an instruction was unclear or two departments are following different rules. The work was done, but the result was not usable.

What to check: What proportion of cases are returned for correction? What are the three most common types of corrections?

A change at the start of the process may matter more than an additional check at the end.

7. Extra help does not eliminate delays

When there is too much work, a company adds people, overtime or external support. This may be entirely the right decision. But if delays remain in the same place, you need to check whether the extra capacity was directed at the part of the process that actually limits the result.

What to check: Has the additional help led to more completed work, or simply to more prepared tasks waiting for the next step?

How can you identify a bottleneck in your company?

You do not necessarily need a lengthy project or a new information system to carry out an initial review. You can start with one specific process. For example: from receiving an order to dispatch, from receiving a complaint to resolving it, or from an internal request to approval.

Step 1: Choose one process

  • Do not try to optimise the entire company at once.
  • Choose a process where delays, repetition or dissatisfaction are clearly visible.
  • Define where the process starts and when it is truly complete.

Step 2: Follow five actual cases

For each case, record:

  • when it started and finished;
  • who was involved;
  • where it waited;
  • how many times it was returned for correction;
  • which steps required active work.

Five cases are not a statistically reliable basis for every decision. They are, however, a useful starting point for forming hypotheses and identifying areas that need closer analysis.

Step 3: Look for a recurring constraint

Do not look only for the slowest employee or the longest individual task. Look at where cases consistently stall, accumulate or get sent back.

Are several orders waiting for the same approval? Are complaints being returned because the same information is missing? Does the process stop every time a task passes between departments?

The pattern matters more than a single exceptional case.

Step 4: Propose the smallest testable change

Once you have a hypothesis, you do not need to redesign the entire process immediately. Perhaps certain requests could be handled according to a clearer rule. Perhaps the information needed at a particular handover could be prepared earlier. Perhaps an unnecessary step could be removed or responsibility defined more clearly.

The change must not compromise quality, safety or necessary controls.

Step 5: Measure whether the flow has actually improved

Before making the change, define what you will measure. This could be the time from start to finish, the number of completed cases, the amount of unfinished work or the frequency of errors. Then compare the results with the original situation, taking the volume and complexity of the work into account.

When is hiring another employee the right solution?

Sometimes the answer really is more people. If the process is appropriately designed, work is piling up because capacity is persistently insufficient and additional employees would increase capacity at the limiting step, hiring may be justified.

The same applies to new software or automation. Yoptis’s approach is not about opposing investment. It is about the order of decisions. First establish what limits the result. Then decide where to invest.

How can Yoptis help?

Yoptis helps companies identify hidden friction in business processes, customer journeys and operational work. We combine observation of the actual process, available data, an understanding of behaviour and testable changes.

Yoptis Flow Check is designed for companies that want to start with one clearly defined problem. It is a diagnostic review of one specific process. Its purpose is to identify key constraints and formulate a testable hypothesis for improvement, with the findings brought together in a written Flow Report.

This allows the company to make a more informed decision about its next step before committing to a broader change or investment.

Explore Yoptis Flow Check

Frequently asked questions

Is a bottleneck always the slowest part of the process?

Not necessarily. The constraint may depend on how work is scheduled, decision-making, the availability of information, required controls or an uneven arrival of tasks.

Can automation eliminate a bottleneck?

Yes, if automation removes the actual constraint. If it speeds up a step that already has sufficient capacity, the overall process may not become significantly faster.

How should we choose the first process to optimise?

Start where the problem matters to the business, recurs regularly and has a scope narrow enough for you to observe it and measure a change.

How do we know whether an improvement has worked?

Before intervening, establish the baseline and a measure of success. After the change, check whether the overall time from start to finish, the number of completed cases, quality or another important outcome has improved.

Conclusion: it is not just about how much work the team does

It also matters how much work actually reaches completion. If tasks are piling up, do not assume that people are working too slowly. They may have too much unnecessary work. They may be waiting for decisions. The process may require steps that nobody can justify anymore.

Before increasing pressure, headcount or the budget for new technology, check one thing:

Where is work actually getting stuck?