Preparing for a Seasonal Peak: What to Scale, What to Freeze, and What Breaks First

A seasonal peak does not break broken processes - those already fail every month. It breaks what barely works: the step depending on one person, the handoff that works because everyone remembers, and the stock that is exactly enough. Preparation is mostly identifying those three in advance.

What breaks first, in order

The first row is the foundation: load does not create new problems but magnifies existing ones. So the first step in preparing is identifying the bottleneck, as covered in finding the bottleneck in your process.

What to do a month ahead

1. Identify the bottleneck and decide how to scale specifically that.
2. Check stock of fast-moving items and order against the real lead time.
3. Settle with suppliers - lead times, collection windows, what happens at peak.
4. Set decision rules in advance: what is approved without asking, what happens when stock runs out.
5. Freeze anything non-essential - projects, system changes, tests.
6. Prepare customer messages for the predictable scenarios.

Point 5 is the hardest to accept and the most valuable. A system change the week before a season is unnecessary risk, however small it looks - and it can nearly always be deferred by a month.

What to scale and what not to

Do not scale everything. Scaling a step that is not the bottleneck only lengthens the queue in front of it, which is waste. What you do scale: the bottleneck itself, and customer response - because it absorbs the consequences of every other problem.

What is worth reducing during a season: variety. A promotion on three products is far easier to run than one on twenty, and it also cuts the number of items that can run out. Many businesses realise afterwards that the season was hard because of range rather than volume.

What to decide before rather than during

Three decisions that, if not made in advance, will be made mid-peak under pressure: what happens when stock runs out - cancel, offer an alternative, or wait; what happens when you are late - who tells the customer and when; and what takes priority when you cannot supply everything.

The third is the hardest and the most important: with no rule, everyone decides differently and similar customers get different treatment. A simple rule - order of receipt, say, or regular customers first - is entirely sufficient, as long as it is written and agreed.

Customer response during a peak

Enquiries grow faster than sales, because every order brings a question with it. Three actions reduce that substantially: publishing seasonal delivery times in advance, proactive status messages, and prepared answers to the three most common questions.

The second is the largest: a customer who gets an update does not ask. The full logic is in automatic tracking updates to the customer, and it holds in a season too - the only difference is that the range you promise must be realistic for the season rather than for an ordinary month.

What to do immediately afterwards

In the week after, while it is still fresh, write down three things: what broke, what saved the day, and what you would do differently. Half an hour of writing is worth more than any planning done a year later from memory.

That list is also the basis for the next preparation, and it makes each season better than the last. In businesses that skip it, the same problems recur every year - not because nobody noticed, but because by the next season everyone had forgotten the details.

How do you know the preparation is enough?

By three questions you can answer a week beforehand. What happens if volume is double the plan - is there an answer, or hope. Who decides when a fast call is needed - one name, and availability. And what do we stop doing if capacity has to be freed.

The third is the real test: preparation consisting only of additions and no sacrifices is not preparation but optimism. A business that knows in advance what it will freeze - which extra service, which order type, which project - enters the season with headroom, and that is what absorbs a surprise.

Also worth checking is the physical failure point: packing space, workstations, room for temporary storage. In most small businesses those break before the processes do, and they are easy to fix in advance at no cost - a second table and a marked area for outbound parcels often matter more than any planning spreadsheet.

Also worth deferring past the season, beyond projects: a new hire needing training, a change of supplier, and a price change. Each demands attention that will not be available, and all three produce errors exactly when there is no slack to correct them.

What happens to quality under load

This is the part you pay for after the season rather than during it. Under load, controls tend to slip - the check before sealing a box is skipped, an approval is waived, documentation is shortened. The result arrives about a month later, as a wave of returns and service enquiries.

So decide in advance which single control is never touched, however pressured things get. It is usually the check preventing the most expensive error - a wrong item, a wrong label, or a wrong amount - and everything else can be shortened. That choice is easy to make calmly and nearly impossible mid-way through a busy day.

Sources

• How to improve business efficiency
• Israel Tax Authority - information for businesses