Systems and tooling
Domain 07 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
Selecting, implementing, and retiring the tools an operation runs on. Judging integration cost honestly. Recognising when a tooling problem is actually a process problem.
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
Systems and tooling is the set of instruments the work runs on, and whether they encode the process or fight it. Selection is the visible part. The two harder parts are estimating integration cost before you are committed, and retiring things afterwards.
Retirement is the half most operations never do. Tools accumulate, each with a small number of committed users, and the cost of the estate is paid in integration surface and in the question every new hire asks about which system is the real one.
What it looks like when it is working
- Every tool has an owner and a stated reason, and somebody can say what would break if it were removed.
- Integration cost is estimated before purchase and reviewed after, and the estimates have got better over time because somebody compared them.
- Tools get retired, meaning actually switched off, not left running for three users.
- The data that matters lives somewhere the business controls and could leave with.
How it fails
The common failure is buying a tool to solve a process problem. The process is undefined, the tool arrives and defines it, the tool opinion becomes the process, and the mismatch surfaces eighteen months later as the system will not let us.
The second is an integration estimate that counts the build and not the maintenance, which is the larger number and the one that recurs.
Why competent operators miss it
Because the tool genuinely does improve things at first. Anything is better than nothing, the early result is real, and the person who bought it is vindicated inside the window anybody is still watching. The cost is deferred onto whoever inherits the estate, which is usually not the person who chose it.
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 turned something off, including the conversation with its remaining users.
- You said no to a tool and fixed the process instead.
- You bought one and owned the integration cost you predicted, including where you were wrong.
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.