In most organisations you can ask how many days an order takes and get an answer; but ask how many of those hours were actual work and how many were waiting, and usually nobody has the number. That gap is where the waste lives.

Bottlenecks stay invisible in the monthly report because reports show each unit's output separately, while the waste settles in the space between units: a file parked on an approver's desk, an order waiting on a warehouse decision, a message answered two days later.

Waste hides inside waiting

Break a process cycle time into its parts and in most cases the share of waiting exceeds the share of work. What matters is where you intervene: adding people to a step that is itself waiting raises cost and leaves output untouched. The step that genuinely caps total capacity is found only by looking at the whole chain.

From the monthly report to event data

The input is something most organisations already produce without realising it: a trail of events. Every order entry, every status change in finance or inventory, every approval and handoff carries a time. Putting those times together reconstructs the real path of work, a path that almost always differs from the flowchart on the wall.

Four things process analysis delivers

• Finding the bottleneck: locating the step that caps the capacity of the whole chain, based on measured time rather than management intuition.
• Allocating capacity: moving people and equipment towards that step instead of distributing resources evenly.
• Forecasting load: estimating the workload of coming days and weeks from past patterns, so shifts and stock are set before the pressure arrives.
• Detecting deviation: surfacing the cases that left the standard path; those cases usually account for the bulk of delay.

Why it pays off in Iranian industry and services

When energy, raw material and financing costs have risen and raising the sale price is not always possible, margin has to come from the cost side rather than the revenue side. Releasing capacity already dormant inside a process is the cheapest form of growth: it needs neither investment in a new production line nor foreign currency for imported equipment.

A three-month path

• Month one: choose a frequent process with a clear owner, define its boundaries, start logging the entry and exit time of each step, and set one target metric; if the system does not capture this, a simple paper log is enough.
• Month two: map the real path of work, form two or three hypotheses about the bottleneck, and test the cheapest change on a single line or shift.
• Month three: compare the result with the period before the change; turn whatever improved the metric into standard procedure and move on to the next bottleneck.

Common mistakes

• Optimising a unit that is not the bottleneck; the result is a pile of unfinished work in front of the real constraint.
• Measuring without a basis for comparison; with no picture from before the change, any improvement can be disputed.
• Buying speed at the expense of quality; a shorter cycle time that raises rework is not an achievement.
• Ignoring the knowledge of frontline staff; the people working inside the process every day usually know where the bottleneck is and have never been asked.

What you should measure

Three numbers are enough for most organisations: cycle time from start to delivery, throughput or the count of items finished per unit of time, and the volume of work in progress. The relationship between the three gives a clear picture; if work in progress grows while throughput stays flat, it means the organisation is starting more and waiting more.

Frequently asked questions

• Do we need an ERP system?
  Not to begin with; a few weeks of disciplined step-level time logging is enough to find the first bottleneck.
• What if our process is not standardised?
  That absence of a standard is itself measurable through deviation analysis; in such an organisation the biggest gain is making the path consistent, not making it intelligent.
• When will we see results?
  Finding the bottleneck usually happens in the first weeks; the financial effect appears once the change has settled into daily routine.

Takeaway

Optimising operations with AI does not begin with buying a tool; it begins with asking where the work sits waiting. Log the time of each step and follow one metric, and you release capacity that had already been paid for and was going unused.

Glossary

• Bottleneck: the slowest step in a chain, which caps total output.
• Cycle time: the interval between starting a job and delivering it to the customer.
• Throughput: the number of items completed per unit of time.
• Work in progress: the volume of work that has started and is not yet finished.
• Event data: the timestamped record of everything that happens in your systems, from which the real path of work is built.
• Rework: redoing a job that was not completed correctly the first time.