Capacity

Where does your capacity really go?

A constraint in one stage can leave other people or assets waiting. Adding resources before understanding that constraint can simply create a larger queue.

Does this feel familiar?

Always busy. Yet output barely moves?

  • Overtime without more output
  • Work queues in one department
  • Some assets idle while others overload

Recognition is the beginning

Follow the work

Follow the whole flow to find the limiting step. The constraint may sit at any stage.

Load the systemDo the workRelease useful output

An illustrative starting point for investigation; the actual flow depends on your business.

  1. 01

    Demand

    Understand the volume and mix entering the operation.

    What might slow this down?

    Demand arrives in a pattern that the current plan cannot absorb.

    Assess the impact using actual cases and evidence.

  2. 02

    Plan

    Sequence work around the capability actually available.

    What might slow this down?

    Priorities overload one stage while another waits.

    Assess the impact using actual cases and evidence.

  3. 03

    Prepare

    Make people, information and materials ready to begin.

    What might slow this down?

    The team is available, but a dependency is missing.

    Assess the impact using actual cases and evidence.

  4. 04

    Execute

    Compare useful output with time and resources consumed.

    What might slow this down?

    Changeovers, interruptions or a limiting resource restrict flow.

    Assess the impact using actual cases and evidence.

  5. 05

    Check

    Release good work without avoidable inspection queues.

    What might slow this down?

    Checks wait for approval or send work back for correction.

    Assess the impact using actual cases and evidence.

  6. 06

    Release

    Move completed work to its next useful destination.

    What might slow this down?

    Completed work stays blocked by a handover or release decision.

    Assess the impact using actual cases and evidence.

Compare queues and available capacity across these stages; investigate where the flow is limited.

What could be happening?

A different cause needs a different solution.

These are possible drivers to investigate, not a diagnosis of your business.

The visible symptom

Always busy. Yet output barely moves?

Potential drivers to investigate

  • Scheduling

    Does the plan reflect the real constraint?

  • Changeovers

    How much time is lost between jobs?

  • Dependency bottlenecks

    Which dependency controls the pace of output?

  • Skills and maintenance

    What keeps a critical resource unavailable?

Make existing capability count

Sometimes you don’t need more resources. You need more from the resources you already have.

Adding people can solve a capacity problem. It can also make an inefficient operating model more expensive.

I’ve worked on how capability was organised, resources allocated, teams shared capacity and management could see where resources were being consumed.

Selected experience from my career, before this independent practice.

Existing capability
  • Utilisation
  • Priorities
  • Ownership
  • Workload
  • Cross-team flow
Understand the constraint before adding resources.

That distinction matters.

The result was a more deliberate use of existing capability. When a business says “we need more people”, I first ask what is preventing the people already there from delivering more.

How I may help

Fix the cause.
Improve the outcome.

Improve the limiting step before adding resources elsewhere.

  1. 01

    Find the limiting step

  2. 02

    Improve scheduling and hand-offs

  3. 03

    Build capability at the constraint

The right change depends on what is actually limiting useful output.

The answer might sit in scheduling, queues, hand-offs, skills, equipment, priorities, ownership or the way existing capacity is allocated. Add resources only when the evidence shows capacity itself is the constraint.

Explore how I help

Evidence before investment

Observe. Connect. Prove.
Quantify. Decide.

Follow actual work, test likely causes and assess the business impact before committing to a change.

  1. 01

    Observe

    Follow actual work.

  2. 02

    Connect

    Link symptoms to possible causes.

  3. 03

    Prove

    Test the explanation against evidence.

  4. 04

    Quantify

    Assess the business impact.

  5. 05

    Decide

    Choose what is worth changing.

How I work

What could improve?

Potential improvements depend on the diagnosis and your starting point.

  • More useful output
  • Shorter queues
  • Better use of people and assets

Connected outcomes

One change can reach further.

  • Growth

    Additional demand tests the business’s ability to fulfil it.

  • People

    Capability and decision ownership affect available capacity.

  • Efficiency

    Avoidable work consumes time that could support output.

Let’s start a conversation

Before you add more capacity, should we find out what’s constraining what you already have?

A number that concerns you. A frustrating process. Something that should work better. You don’t need the root cause, a solution or a formal project brief.

01I have a problem02I want a better outcome03I’m not sure where to start

In 30 minutes, we can explore what’s happening, what may be driving it and what deserves closer attention. A starting point, not a complete diagnosis or a commitment to a larger engagement.