Demand, Capacity, Queues and Workload for SMEs

Demand is the amount of work arriving. Capacity is the amount of work the process can complete. Queues are work waiting to be handled. Workload is the amount of work people or systems are carrying. When demand and capacity are poorly balanced, queues grow, waiting increases and staff feel constantly busy.

The direct answer is this: a process slows down when more work enters the system than the system can complete reliably, or when too much work is allowed to sit in progress. SMEs often experience this as firefighting, missed promises and staff overload.

Core Concepts

Concept	Meaning	Example
Demand	Work arriving into the process.	New enquiries per day.
Capacity	Work the process can complete in a period.	Quotes the estimator can prepare per day.
Queue	Work waiting before the next step.	Orders waiting for approval.
Work in progress	Work started but not finished.	Open jobs across the team.
Utilisation	How much available capacity is being used.	A technician booked for 95% of available time.

Queue Warning Signs

Work waits in inboxes, trays, message threads or spreadsheets.
Staff start many jobs but finish too few.
Urgent work constantly jumps the queue.
Customers chase for updates.
The team is busy but completed output does not rise.
Lead time grows even though individual task time has not changed much.

Demand-Capacity Matrix

Demand / Capacity	Enough capacity	Insufficient capacity
Stable demand	Standardise and improve flow.	Add capacity, reduce waste or reset promises.
Variable demand	Use buffers, scheduling rules and flexible staffing.	Triage demand, protect constraints and review service model.

Simple Workload Review Template

Week	New work received	Work completed	Work in progress	Oldest item age	Action needed
Week 1
Week 2
Week 3

Panith Illustrative Case Study

Panith Illustrative Case Study: A small IT support provider promises same-day response. Ticket volume rises from 25 to 45 per day, but the team still plans work as if demand is stable. Queues grow, staff multitask and customers wait. The first improvement is not a new tool; it is visibility of demand, WIP, ticket age and available support capacity.

Common Mistakes

Assuming delays mean people are lazy.
Letting unlimited work enter the system.
Planning at 100% utilisation with no room for variation.
Starting more work instead of finishing work.
Ignoring old items because new urgent work feels louder.

References and Further Reading

Next Lesson

Continue with Lesson 15: Identifying Bottlenecks and Constraints.

SEO improvement pass: expanded depth and practical application

Expanded Practical Guidance

Queues are not only a workload issue. They are also a promise issue. If customers are told work will be completed in two days while the queue already contains five days of work, the process is creating disappointment before anyone starts the task.

High utilisation can be dangerous in variable work. A team booked to 100% capacity has no room for urgent work, mistakes, sickness or customer changes. SMEs often need a visible buffer rather than a heroic culture.

Queue Diagnosis Table

Symptom	Likely issue	First check
Many items started, few finished	Too much WIP	Count open work by age.
Customers chase frequently	Unclear lead time or status	Compare promise vs actual completion.
One role always overloaded	Capacity imbalance	Measure demand by role.
Urgent work disrupts everything	Weak prioritisation rules	Review triage criteria.

Practical Next Step

Create a weekly workload view showing new work, completed work, open work and oldest item age. This simple view often reveals the queue before a complex system is needed.

Visual Learning Aids

The following visual structures translate this lesson into practical management tools. They are designed for SME use and can be copied into a workshop, team meeting or improvement plan.

1. Process Diagram

Input	Work system	Output	Owner	Main risk
Customer need or business trigger	Demand, Capacity, Queues and Workload applied to the business process	Reliable customer or internal outcome	Process owner	Rework, delay or quality failure

2. Flowchart

[Start] Trigger received
   |
   v
[Understand] Work is mapped
   |
   v
[Decide] Bottleneck or waste is identified
   |
   v
[Act] Improvement option is selected
   |
   v
[Review] New way of working is tested
   |
   v
[Improve] KPI review confirms next action

3. Decision Tree

Is the issue clear and evidence-based?
- No: clarify the problem, collect examples and involve the people closest to the work.
- Yes: does it affect customers, cost, quality, risk or growth?
  - No: document the learning and monitor lightly.
  - Yes: assign an owner, choose a practical method, define success measures and review progress.

4. Priority Matrix

	Low effort	High effort
High impact	Do first: quick operational improvement	Plan carefully: strategic improvement project
Low impact	Do only if it removes friction	Avoid or defer unless required for risk, compliance or learning

5. Implementation Timeline

Stage	Typical SME timing	Output
Diagnose	Week 1	Problem statement and evidence
Design	Week 2	Chosen method, owner and measures
Test	Weeks 3-4	Small pilot or controlled trial
Standardise	Weeks 5-6	Checklist, SOP, dashboard or decision rule
Improve	Monthly	Review notes and next improvement action

6. Illustrative Performance Chart

Illustrative example: replace these sample scores with real business data before using the chart for decisions.

Measure	Current score	Target score	Visual gap
Clarity	2/5	4/5	2 blocks to 4 blocks
Ownership	2/5	5/5	2 blocks to 5 blocks
Measurement	1/5	4/5	1 block to 4 blocks
Consistency	3/5	4/5	3 blocks to 4 blocks

7. Maturity Model

Level	Maturity stage	What it looks like	Next improvement
1	Informal work	Informal work is visible in the way the business manages this topic.	Documented process
2	Documented process	Documented process is visible in the way the business manages this topic.	Measured process
3	Measured process	Measured process is visible in the way the business manages this topic.	Controlled process
4	Controlled process	Controlled process is visible in the way the business manages this topic.	Continuously improved process
5	Continuously improved process	Continuously improved process is visible in the way the business manages this topic.	Sustain and refine through periodic review

8. Comparison Table

Dimension	Current-state process	Future-state process
Decision basis	Experience, urgency or individual memory	Evidence, agreed criteria and visible trade-offs
Accountability	Unclear or dependent on the founder	Named owner with clear responsibility and review rhythm
Measurement	Discussed only when something goes wrong	Tracked using cycle time, first-time-right rate, cost and customer impact
Scalability	Works only while the team is small	Can be taught, repeated and improved as the business grows