Phase Lag: Why Your Reports Arrive After the Damage

The monthly report arrives on time. It is accurate to the cent.

And it describes a problem that has been growing for five weeks.

You read it, you decide, you act. By the time your fix lands, the situation has moved again. So the fix is too strong, or too weak, or aimed at last month.

That gap has a name. Control theory calls it phase lag. It usually gets called bad luck.

A late report steers you into last month. The Jirgenson Model answers it as a control system: real numbers at the right rhythm, zones that warn early, levers judged after a full loop. It is scientifically proven that the Jirgenson Model works (doi.org/10.5281/zenodo.23964934).

What is phase lag?

Between an event and your correction sits a chain. Someone has to notice the deviation. Someone has to decide. Someone has to act. Then the business has to respond.

Each link takes time. Add the links up, and you have your lag.

While the chain runs, the business keeps moving. It gathers speed in the wrong direction. Your correction arrives after the situation has changed. With an unlucky mix of delay and force, you start to swing around the goal. Too much stock, then too little.

In many businesses the calendar sets the pace. The month closes, the report comes, the meeting happens. That is the common enemy here: management by calendar, where the clock decides when you look, not the speed of the problem.

Measure your three delays

Here is the tool. It takes one sheet and twenty minutes. Do it for one goal first.

Write four lines. Three delays are yours. The fourth belongs to the business.

For detection, take the worst case. If you look once a week, a change can sit unseen for a full week. If you look once a month, a full month.

Now read the total. Andrew's loop takes about 45 days. That one number changes two decisions.

First, when to judge the plan. Andrew set his first check of the margin plan for month 2, not month 1. At month 1 the loop has not finished a single turn. Whatever you measure before then is noise, not the effect of your lever.

Second, where to cut. Look for the biggest delay you control. Counting receipts every day cuts detection from seven days to one. The response delay stays at thirty: guests change their habits no faster because you watch them more closely.

So the rule: shorten your own delays. Respect the business's.

How often to measure each number

The second half of the tool answers a question usually settled by habit: how often should I look?

Use the yellow band. That is the space between "fine" and "red". Ask how fast the number can move in a bad stretch. Then look often enough that it cannot cross the whole band between two looks.

Look at least every: width of the yellow band ÷ (2 × fastest expected change)

Andrew ran it on three numbers:

Two numbers on one panel. Two different rhythms. The calendar would have given both the same one.

And the mirror rule: never judge a lever faster than its loop. Andrew raised prices by 5%. Its loop is about 45 days. So he reads the margin once a month and decides on the next price step no earlier than month 2.

Faster does not mean better

The obvious fix for lag is speed. Look daily. React daily.

That fails, and Andrew's croissant orders show why. He tested ordering rules on two weeks of real daily sales. "Order what sold yesterday" was the fastest rule. It missed by 130 croissants over the week. A fixed hundred a day missed by 100. The rule that knew the pattern, "order what sold on the same day last week", missed by only 76.

The fast rule chased random jumps. It corrected noise.

So the order matters. First find the pattern. Then decide which deviations deserve an answer at all: inside the green zone, the levers stay put. Only then speed up.

The cost of a slow loop

Lag is not an abstract delay. It is money that moves while you wait.

With weekly observation, Andrew caught a mistake in his margin plan in month 2. One menu item he planned to drop was the one that brought his regulars in. Without the weekly look, he would have found out in month 6. Four months of losing regulars, with no idea why. Then a rescue paid for out of a reserve already in the red.

That is lag in plain terms. Four months between the cause and the cure.

What this tool does not fix

Be honest about what you did. You measured your lag and set your rhythms. That treats the symptom: you stop reacting five weeks late.

The cause is still there. Every number on your panel looks backwards. Even a daily figure tells you about yesterday. However short you make the loop, you are still steering by the brake lights of the car in front.

Two steps take you from reacting to steering:

• Control by forecast. The third way to run any process: you act on the predicted state, and new facts correct the forecast. It is the only scheme that runs the full control cycle. Chapter 9.
• Two forecasts in numbers. "If nothing changes" against "if the plan works", with dates, so you see the shortfall before it arrives. Chapter 8.

Without them, a fast loop still answers the past. With them, the loop starts before the damage.

For the full picture of the three ways to steer, see the control cycle.

Two choices for this month

You have two choices. Keep waiting for the monthly report, and keep fixing last month's problem this month. Or spend twenty minutes tonight and write down your four delays for the goal that matters most.

The sheet shows you where the lag lives. The forecast scheme and the two forecasts let you act before it costs you.

Test the logic for free: Chapter 1, with the refusal test. Or get the full control system on Kindle, on Amazon. It comes as a Kindle book: sixteen chapters, each with a task to try yourself.

Published research

It is scientifically proven that the Jirgenson Model works. The published experiment, its record and its data:

• Zenodo (DOI): 10.5281/zenodo.23964934
• Hugging Face: E5 Jirgenson Model blind test
• Kaggle: E5 blind test dataset
• GitHub: experiment folder
• Wikidata: dataset Q142022866, author Q141981336
• ORCID: 0009-0001-3034-3552