Observable condition
A job is scheduled, staff are available and most materials are ready, but one component has not arrived. Or a service process has every document except one certificate. Or a project can proceed in every respect except for one approval, licence or prerequisite. The missing input may be small compared with the total work, yet the entire process waits.
Realisation
The visible problem is the missing item. The deeper pattern is that the business discovered a critical dependency too late. A process is not ready because most of its inputs are present; it is ready when every dependency required for the next meaningful stage is available or an approved alternative exists.
Identification
This is a dependency-visibility and constraint-management problem.
Diagnosis
Common causes include planning by department rather than end-to-end flow, prerequisites stored in separate systems, weak lead-time visibility, incomplete bills or checklists and no mechanism that distinguishes a critical dependency from ordinary stock. ISO process guidance emphasises managing process interactions, while value-stream mapping focuses on the complete flow rather than isolated activities. The important question is not simply whether each function did its part; it is whether the whole process can move.
Commercial impact
The value wrapper is throughput, working capital, service reliability and planning resilience. Other resources can sit ready but idle. Expedites and substitutions consume management attention. Customers experience a delay caused by one prerequisite even though substantial effort and inventory may already have been committed.
Common misidentification
The response is often to carry more inventory of everything. That can hide some shortages while increasing capital tied up in non-critical items. The better question is which dependencies actually govern readiness and whether the business can see risk early enough to act.
Possibility
A stronger operating model makes prerequisites explicit. Jobs, orders or service cases can carry a readiness view showing required inputs, responsible owners, expected availability and blocking status. Exceptions are raised before the scheduled start rather than discovered during execution.
Intervention
Review several recent jobs or processes that stopped because something was missing. List every prerequisite, when its absence became visible, when it could first have been known and who could have acted. Then identify the smallest set of dependencies that should be monitored as readiness constraints.
Practical diagnostic questions
- What must be true before this process can genuinely start?
- Which prerequisites can stop the entire flow?
- Can the business see those dependencies before scheduling work?
- Are expected arrival, approval or completion dates connected to the job?
- Do teams measure inventory availability or actual process readiness?
Bottom line
When one missing item repeatedly stops a larger process, the business may have plenty of resources but too little visibility into the dependencies that determine flow.