Shortage, Excess and Imbalance Analysis
Compare resources and demand by session, then investigate allocation and practice differences before choosing a change.
Use this when an adequate daily total hides local overload or inconsistent work. List the tasks, compare like units in each session, and keep differences in versions or practice as separate investigation leads.
Work scope, demand, available resources, units, periods, quality limits, practice records and unknowns.
A shortage/excess/imbalance issue list, local arithmetic gaps and conditional change candidates.
How to use it
- List the work, quality floor, comparison unit and sessions.
- Record demand and available capacity, including estimates and unknowns.
- Identify local shortages, excess and allocation or practice differences without double counting.
- Check evidence and alternative explanations before suggesting reallocation.
- Choose a small trial with owner, permission, stop rule and measurement.
Keep its limits in mind
Judge resources against a specific need and window. Idle capacity may be a necessary buffer; it is not automatically removable. Equal totals cannot cancel time mismatches. Capacity cannot move across sessions or skills without checking constraints. Different practices do not prove causes. These three lenses are not a renaming of another lean taxonomy or an employee rating.
A balanced day hides a morning shortage
Original fictional I5 teaching packet: Clearbrook Support. Records, statements, trials and agreements are synthetic, not real outcomes or personnel assessments.
On a small screen, scroll across the diagram to read it.
Keep local gaps: AM has 6 request-equivalents of shortage; PM has 6 idle. The known sessions total 24 demand and 24 capacity, but EV is unknown and capacity cannot travel backward in time.
Investigate practice variation: A ten-form audit includes the two known missing-owner cases. Different fields are a lead, not proof of cause. Check constraints before trialling a change.
Keep AM shortage6 and PM idle6 separate; the24/24 total covers only known sessions, not a complete day.
Next step: With an evidenced issue list, use ECRS to explore reordering and simplification, then check resources, quality and added work.
Three reasons a daily total is not enough
First, pause when demand and capacity use different units or windows. A request count is not staff time until a conversion is stated, and estimated capacity is not measured throughput. Separate session-level records before aggregating. If some sessions are unknown, label the total as partial rather than replacing missing values with zero.
Second, do not treat spare capacity as waste automatically. It may cover variability, interruptions, quality checks, or work requiring a different skill. A later idle period cannot meet an earlier need without changing timing or the service arrangement. Investigate the actual flexibility before suggesting a shift or a staffing reduction.
Third, stop before converting a practice difference into a cause. Different forms or versions may be associated with missing information, but the record also needs task context and alternative explanations. The shortage, excess, and imbalance lenses can describe the same issue; counting each label as a separate saving would duplicate a claim.
Choose between local gaps, redesign, contribution, and causes
These three lenses organize an evidenced issue list. They do not rename another lean taxonomy or rate employees. Choose a related method once the missing output becomes more specific, keeping the same units and time boundary.
| Question and available input | Method | Output and limit |
|---|---|---|
| Demand, capacity and practice records by session | Shortage, excess and imbalance analysis | Local gaps and investigation leads; no automatic resource move. |
| A specific activity may need removal or reordering | ECRS | Change candidates with added work; no proven saving. |
| Comparable issue categories and counts | Pareto analysis | Contribution order within that dataset; no root cause. |
| Several explanations for one evidenced gap | Logic tree | Investigation branches; a branch is not a finding. |
Keep Clearbrook’s morning gap visible
The complete fictional I5 record is October 5 at Clearbrook Support. Demand and capacity are request-equivalents per session, assuming five staff-minutes per request and sixty available staff-minutes per session. AM demand is 18 and capacity 12; PM demand 6 and capacity 12; EV demand and capacity are both unknown. These are teaching assumptions, not observed waiting times, completed requests, or staffing requirements.
AM therefore has six request-equivalents of shortage, equivalent to thirty staff-minutes under the stated conversion. PM has six request-equivalents of unused capacity, also thirty staff-minutes. The known sessions total 24 demand and 24 capacity, but that equality does not eliminate timing constraints or establish a full-day balance. EV remains missing.
A separate audit examines ten of fifty trial forms and includes two missing-owner records. The v1 and v2 fields differ. This is a practice-variation lead, not a population estimate or proof that the version caused either case. A proposed shift or earlier booking requires skill, timing, buffer, and permission checks before any trial.
| Raw record | Bounded interpretation | Next check |
|---|---|---|
| AM demand 18, capacity 12 | Shortage6 equivalents; 30 staff-minutes under assumption | Confirm arrival window, conversion and skill availability. |
| PM demand 6, capacity 12 | Unused6 equivalents; not a cash saving | Check buffer and whether timing can actually change. |
| EV demand?, capacity? | Unknown; no full-day total | Coordinator gathers comparable EV records. |
| Audit 10 of 50, including 2 missing owners; v1/v2 differ | Two observed cases in this audit; variation is a lead | Trace the two records and compare instructions/context; do not extrapolate to 50. |
Define a small test without spending the same capacity twice
First confirm what a request-equivalent represents and whether the five-minute assumption is credible for the work considered. Different complexity or skills can make an average misleading. Retain the underlying records and quality floor instead of treating every request as interchangeable.
For a proposed timing change, identify who can move which work, who must agree, and which demand can genuinely move earlier or later. Count any booking, coordination, or checking work the change adds. The afternoon amount cannot simultaneously be a buffer, a transferred resource, and a saving.
Before an authorized trial, specify its scope, owner, stop condition, and measures for demand, capacity, completed work, waiting, and quality. Keep these measures distinct; more completed forms need not mean fewer errors or shorter waits. No reallocation or improved outcome has been supplied here.
At review, compare like sessions and include unknown or unresolved cases. Investigate the two missing-owner records separately from the load arithmetic. The decision may be to collect data, alter timing, standardize instructions, or leave a buffer intact. Explain the evidence behind it without turning an analytical label into a staffing judgment.
Check your work
- Demand and capacity use comparable units.
- Local shortages and idle capacity survive aggregation.
- Differences and candidates are not proven causes or savings.
Framework references
References explain the framework and its scope; they do not validate the fictional example's results.
Put the framework to work
Copy the outline and add your question, evidence, and open questions.