What is the difference between reactive and proactive management?

Reactive management waits for a deviation and corrects it afterwards. Proactive management forecasts where a number will land and acts before it gets there, then lets new facts correct the forecast.

What is a control cycle in management?

It is the closed loop a goal passes through, from noticing the pressure to finishing or maintaining the goal. Control by forecast is the only scheme that runs all eight stages.

How do I start proactive management in a small business?

Pick one goal and forecast it every Monday: the driver, the rate, the projection and the gap. Then pull one lever that week. A rolling three-month forecast of cash, enquiries and workload is the full version, explained on Kindle with every number.

Reactive vs Proactive Management: the 15-Minute Monday Forecast

Elena's month was heading for a miss while it still looked like a good month.

Take a Monday when her book's page shows 280 visitors for the week. At her rate of 1.5 buyers per hundred, that pointed to about 17 sales in four weeks. Her goal was 21. Nothing had gone wrong yet. The forecast had.

Now picture your own first of the month. The report lands. Sales missed by a fifth. You can explain every cause. You can fix none of them, because that month is closed.

You spend the first week of each month explaining the last one. That is the habit this post breaks.

Explaining last month won't save it. The Jirgenson Model answers that as a control system: real numbers, a forecast of where each goal lands, levers pulled before the miss. It is scientifically proven that the Jirgenson Model works (doi.org/10.5281/zenodo.23964934).

Reactive vs proactive management: where the difference sits

Both styles watch numbers. The difference is which numbers they act on.

Reactive management acts on the past. It waits for a gap, measures it, then corrects. Proactive management acts on the future. It forecasts where a number will land and moves before it gets there.

In the Jirgenson Model, proactive management is control by forecast: forecast the next state, act on the forecast, and let new facts correct it. Reactive management is control by deviation. Feedback stays in both, because forecasts err; the forecast decides when you move.

The model counts four ways to steer a number. One road, four drivers:

Scheme	The driver	Example
By plan	Pedal locked; never looks at the road	The same order every day, rain or shine
By deviation (reactive)	Brakes when the brake lights ahead come on	"We missed last month, so push harder this month"
By disturbance	Reacts to a measured cause, not to the damage	The outside temperature drops and the heater starts before the room cools
By forecast (proactive)	Watches three cars ahead and eases off early	Elena's Monday forecast

Feedback loop management without a forecast is driving by brake lights. You stop in time only when the car ahead is slow.

The Monday forecast: one goal, 15 minutes

Pick one goal. Do this every Monday. Each step below shows Elena's entry next to it.

1. Write the goal and its deadline

Use one number with a unit and a date.

Elena: 21 book sales a month.

2. Pick the driver you can count each week

Find the number that comes before the result. Then find the rate that turns it into the result.

Elena: page visitors, counted weekly. Rate: 1.5 buyers per 100 visitors, from a trial stream of traffic she sent to the page.

3. Project to the deadline

Multiply this week's driver by the rate. Stretch it to the deadline.

Elena: 280 × 1.5% = 4.2 sales a week. Over four weeks, about 17.

4. Write the gap in the goal's units

Forecast minus goal. Write it down while the month is still open.

Elena: 17 against 21. Four sales short.

5. Pull one lever this week

Choose an action that moves the driver or the rate before the deadline.

Elena: rewrite the page headline, or email her subscribers. Both act inside this month, not after it.

6. Correct next Monday

Set last week's forecast against what happened. Adjust the rate if it was wrong.

Elena: she does this every week, because her own experience is the weak point of the forecast.

The same six lines work at any scale. Alex, thirteen, saves for a €300 bicycle by 1 September. On 1 June his plan says €105; the piggy bank holds €90. He switches to €50 a month: 90 plus three months of 50 makes 240, and his scooter brings another €60. Exactly 300. The forecast adds up with nothing to spare, and that alone is a signal to act.

The same month, run twice

Here is Elena's month handled both ways. The reactive column is an illustration.

	Reactive (illustration)	Proactive
Week 1	Watches total sales; nothing looks wrong	Forecasts 17 against 21
Week 2	Still waiting for the month to close	Headline rewritten, subscribers emailed
Week 4	Month closes at 17	Next Monday's facts check the change
What she learned	"Sales were weak"	Whether the headline moved the rate

The reactive owner gets a verdict. The proactive owner gets an experiment. A forecast is not a prophecy; it is a hypothesis you test every week.

"Forecasts are always wrong." Single numbers usually are. That is why step 6 exists. The forecast does not need to be right; it needs to be checked. A forecast never set against the facts can do worse than plain feedback.

"Then I'll check daily." Speed is not foresight. In a two-week test on croissant orders, the rule "order what sold yesterday" missed by 130 croissants. A fixed order of a hundred missed by 100. The rule that knew the weekday pattern missed by 76. Fast reaction chased noise and lost to doing nothing.

What reacting late costs

Andrew runs the coffee shop at the centre of the method. His reserve stood at half a month of expenses against a goal of two.

His "change nothing" forecast was blunt. At a 9% margin the reserve reaches two months at month 16, four months past the deadline. By the end of month 3 it stands at about 0.8: the red zone. With his margin plan working, the goal arrives at month 10.

That is reactive vs proactive management in one shop. A reactive owner meets that red zone on a bank statement. A proactive one saw it in month 1 and started on the menu and the supplier that week. At 9% margin, one breakdown also costs a full month of progress; at 15%, about half.

Then the human cost. The owner who waits for the statement is the one who flinches every time the bank calls.

The enemy is the report that arrives after the damage. It looks like control. It is a history lesson.

Where the Monday forecast stops

The six lines are complete. Use them today. But be clear about what they fix: the symptom of learning too late.

The cause sits further in. You still have no rule for which gap deserves a response. Without that rule, a forecast that wobbles by one sale will tempt you to pull levers on noise. And one forecast line hides the choice you face: what happens if you change nothing, against what happens if the plan works.

This is one step of a closed loop: goal, state, error, levers, plan, forecast. Two further steps close it:

Zone thresholds. Where green ends and red begins for each number, so a small wobble leaves the levers alone. Chapter 4 holds the exact method.
Two forecasts as a range. "If nothing changes" set against "if the plan works", with dates and conditions. Chapter 8 holds the formulas.

If you run PDCA, treat this as a PDCA example with one change: the Check step looks forward, not back. Where the forecast sits among all eight stages is laid out in the control cycle.

Key takeaways

Reactive vs proactive management is about timing. Reactive acts on last month; proactive acts on where this month will land.
The Monday forecast: goal, driver, rate, projection, gap, one lever, correction.
Faster checking is not foresight. Pattern first, then speed.
A forecast is a hypothesis you test, not a prophecy you defend.
The forecast tells you a gap is coming. Zones and two forecasts tell you when to act.

Two choices for this Monday

You have two choices this week. Wait for the month-end report and spend the first week of next month explaining it. Or write six lines today and fix the month while it is still open.

Next Monday you open the sheet, read one gap in sales, and pull one lever before lunch.

The Monday forecast shows the gap coming. The zone thresholds and the two forecasts tell you which gaps to ignore and which to fight.

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, with every forecast worked out in numbers.

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

This topic is covered in Chapter 7, Full control cycle: eight stages; Chapter 9, Three ways to control: from the calendar to the forecast; Chapter 14, One model for every field of Steer, Don't Guess: Setting Priorities, Reading the Numbers and Correcting Course in Business and Life. The numbers in the examples are illustrative; the book states its limits in Appendix G.