When Workload Spikes

When Workload Spikes: 9 out of 10 causes  is about Human Behavior

Recently, I was speaking with a client who was struggling with a familiar problem: unpredictable workload spikes. Their team was overwhelmed at the start and end of every month, phones ringing off the hook, staff stretched thin, and customer frustration rising.

On paper, nothing seemed unusual. The staffing levels were stable. The processes hadn’t changed. Yet every month, like clockwork, the same tidal wave hit.

So we stepped back and looked at their demand profile — not just the numbers, but the story behind the numbers.

And the answer was surprisingly simple.

They sent out all their bills at the start and end of the month.

  • Customers received them.
  • Customers had questions.
  • Customers called.

The spike wasn’t a mystery. It was a perfectly predictable human response.

Customer Bills

The tempting solution that wouldn’t have worked

The client had already started brainstorming ideas. One suggestion was to let customers choose their own billing date. In theory, this would spread the workload more evenly.

But when we looked at it through the lens of real human behaviour, the picture changed.

Most people get paid at the end of the month.
Most people budget around that.
Most people want bills to arrive when they actually have money in their account.

So if customers were given the choice, they wouldn’t spread themselves evenly across the month. They’d cluster — right back at the end or start of the month.

The spike would remain.
The workload pressure would remain.
And the organisation would still be firefighting.

Understanding demand means understanding people

This is the heart of demand and capacity modelling:

  • You’re not just analysing numbers.
  • You’re analysing behaviour.
  • Why do people call?
  • When do they call?
  • What triggers the peak?
  • What constraints shape their choices?

Once you understand the “why,” the “what to do about it” becomes much clearer.

In this case, the organisation had two realistic options:

 1. Accept the spike and design staffing around it

 Some peaks are simply part of the landscape. If customer preference drives the pattern, fighting it can cause more harm than good.
 After all, what’s worse?
 A predictable spike in workload

or

 A wave of unpaid bills because customers received them at a time they couldn’t afford to pay?

 Sometimes the most efficient solution is to work with the pattern, not against it.
 

2. If the spike truly must be smoothed, change the trigger

 If spreading demand is essential, you need a billing date that customers won’t cluster around.
 Two options emerged:

  •  Bill customers on the date they signed up
  •  Bill customers on their birthday each month

 Both approaches spread demand naturally, without forcing customers into financial stress.

Helping organisations see the story behind the numbers

This is the work we do every day: helping organisations understand their demand, redesign their staffing, and create systems that work for both customers and employees.

If your team is wrestling with workload spikes, unpredictable demand, or shift patterns that never quite fit, it might be time to look at the story behind your numbers.

Because once you understand the “why,” the “how” becomes a whole lot easier.

At C‑Desk Technology and VisualrotaX, we design shift patterns that deliver from day one. Our patterns are built around demand, fairness, and operational sense.

As independent advisors, we bring no bias and no assumptions. We create human‑led shift systems that minimise cost, maximise efficiency, and genuinely support the people who work them. With decades of experience across industries worldwide, we know how to build patterns that work first time — and keep working.

If you want a rota that saves money, strengthens performance, and earns the trust of your workforce, we’re here to help you build it.

Go to our website to find out more

 


Comments

Popular posts from this blog

⚖️ Fairness Isn’t a Feeling: How to Build Rotas People Trust

The Five Shift Patterns Every Organisation Should Know (and When to Avoid Them)

Reasons for Fairness at Work