Capacity and resourcing
Domain 04 of the eight in the NBOP standard. This page explains what the domain is and how it fails. It does not say how much the domain is worth, because that has not been decided yet and will not be decided here.
Its number in the published standard, which is an order rather than a ranking.
The standard is at version 0.9. The weight of this domain is not set.
Domains you need personal accountability in to be eligible. This is one of the eight.
The standard an assessment is built from, readable in full, permanently.
What the standard says
Understanding where the constraint sits, forecasting demand against capability, and sequencing work so the constraint moves deliberately rather than by accident.
That is the whole of the published entry. Everything below expands it and is not itself the standard. Where the two ever disagree, the standard is the document that governs.
What this domain is
Capacity and resourcing is what can actually be spent, in people and in hours, against what is being asked of the business. Before any of that, it is knowing which part of the system is the limit, because capacity added anywhere else changes nothing.
The constraint is not the busiest team. It is the one that sets the rate for everything downstream. Those are frequently different, and telling them apart is most of the skill in this domain.
What it looks like when it is working
- You can name the constraint, and you are naming the thing that sets the rate rather than the thing that complains.
- Work is sequenced against it deliberately, so the limit moves where you intended it to move.
- When the constraint shifts, somebody notices and says so, because somebody is watching for it.
- Forecasts are made against capability rather than headcount, and the gap between the two is a known number rather than an assumption.
How it fails
The expensive failure is resourcing the loudest function. The team that escalates hardest gets the hire, the constraint stays exactly where it was, throughput does not move, and the flat result is attributed to ramp time.
The second is forecasting demand without forecasting capability, which produces a plan that is arithmetically sound and cannot be executed by the people who exist.
Why competent operators miss it
Because the busy signal is real. That team genuinely is overloaded, the distress is not manufactured, and refusing them help feels like bad management. Being overloaded and being the constraint are two different facts about a system, and only one of them is worth spending against. Separating them requires saying no to somebody who is visibly suffering, which is why it so rarely happens.
What accountability here actually means
Eligibility for NBOP-CP asks for personal accountability in at least four of the eight domains. Personal is the operative word. Having worked somewhere that did this well is not accountability, and neither is having been consulted. The test is whether the decision was yours to make and yours to answer for.
For this domain, that looks like at least one of the following.
- You have said no to a hire, or yes to one against pressure, on constraint grounds.
- You sequenced work so the limit moved on purpose, and you can say where it moved to.
- You have forecast against capability and been held to the number.
What NBOP does not claim about this domain yet
Not how much it is worth. The weight of each domain is being set by a job task analysis of practising operators, rating tasks on criticality and on frequency, and the weights are derived from those paired ratings rather than from editorial preference. Until that closes, the standard states equal provisional weighting and says so on its face.
Not what an assessment will ask about it. The examination blueprint follows the analysis. Publishing an item count now would mean inventing one and quietly changing it later.
Not that this description is finished. Version 0.9 is a draft and is expected to change materially before ratification. If you hold operational responsibility and think this domain is described wrongly, that is the input worth having.
The eight domains
Each governs a different part of how an operation is run. They are numbered for reference, not for importance.
Set the weight of this domain
The weighting is decided by operators rating the work, not by NBOP deciding what matters.
The analysis is open now. It takes about twenty minutes, because every task is rated twice, and the results are published in aggregate including the findings that contradict the current draft. If you have held operational responsibility, your rating counts toward the weight this domain ends up carrying.