LIFECYCLE CONTINUITY BOOK: Chapter Three
Mapping Continuity Gaps
Supply chain fragility often hides in the spaces between functions, systems, organisations and decisions. The challenge is to make these hidden discontinuities visible before they become failure.
Continuity gaps are not simply delays; they are breaks in the connection between state, information, ownership and action. Mapping reveals blind time, dormant time, unactionable time, weak handoffs and recovery dependence.
Discontinuity becomes diagnosable rather than invisible.
3.0 Introduction
Chapter Two defined lifecycle continuity as the connective condition across the lifecycle network of an entity. It showed that products, materials, orders, services, assets and obligations may carry physical, commercial, operational, regulatory, sustainability, information, decision and risk dimensions at the same time, and that continuity exists when those dimensions remain connected enough to support action. It also showed that lifecycle continuity is maintained operationally through the alignment of physical flow, information flow, responsibility flow and decision flow. When these flows remain connected, operational continuity is preserved. When they become disconnected, resilience weakens.
This chapter develops the next stage of the framework: the mapping of continuity gaps. If lifecycle continuity is the desired condition, then continuity-gap mapping is the method for discovering where that condition is weak, broken or at risk. It is the process through which an organisation makes discontinuity visible.
The central claim of this chapter is that supply chain fragility is often hidden in the spaces between activities. It is hidden between departments, between systems, between suppliers and customers, between physical movement and information updates, between known problems and authorised decisions, and between formal process design and the informal workarounds people use to keep the supply chain moving. These spaces are where continuity gaps develop.
A continuity gap is not simply a delay. A delay is often the visible symptom. The continuity gap is the underlying disconnection that causes the delay, extends it, obscures it or makes it difficult to recover from it. An order may be delayed because a product is unavailable, but the deeper gap may be that inventory status is not reliable. A shipment may be late because transport has failed, but the deeper gap may be that no one has authority to reroute it. A customer may be waiting because an item is held in quality inspection, but the deeper gap may be that quality release is not connected to customer priority or fulfilment planning.
Mapping continuity gaps therefore requires a different way of seeing the supply chain. It is not enough to map the formal process. The organisation must map the lifecycle as it is actually experienced by products, orders, materials, services, assets and decisions. It must identify where the lifecycle becomes unclear, where work waits, where responsibility weakens, where information loses value, where decisions are delayed and where recovery depends on informal effort rather than designed capability.
Earlier operational improvement models made hidden performance loss visible by distinguishing between elapsed time, value-adding work, waiting, overhead, rework and non-value-adding activity. Continuity-gap mapping builds on that tradition but extends it. The question is not only where time is consumed. The deeper question is where the lifecycle stops being connected, meaningful and actionable.
3.1 The purpose of continuity-gap mapping
The purpose of continuity-gap mapping is to reveal where operational continuity is being lost. It is a diagnostic method, but it is also a reframing method. It changes the question from “where is the process slow?” to “where has the lifecycle become disconnected?”
This distinction matters because many supply chain problems are treated at the level of symptoms. A late order is expedited. A missing update is chased. A supplier failure is escalated. A customer complaint is handled. A quality issue is investigated. These responses may be necessary, but they do not always address the underlying discontinuity. Once the immediate problem is resolved, the same pattern may return because the lifecycle design has not changed.
Continuity-gap mapping seeks to move beyond reaction. It asks why the organisation lost continuity in the first place. It asks why the lifecycle state became unclear, why ownership was not obvious, why the decision was delayed, why the information was not actionable, why the work waited, and why recovery required unusual effort. These questions help the organisation understand fragility before it becomes failure.
The value of mapping also lies in making hidden work visible. Many supply chains continue to operate because experienced people know how to compensate for weak process design. They know whom to call, which spreadsheet to check, which manager can approve an exception, which supplier contact will respond quickly, and which workaround will move the order forward. This informal knowledge is often valuable, but it is also a sign that the designed lifecycle may not be sufficiently continuous. If continuity depends on personal memory and informal relationships, resilience is vulnerable.
A lifecycle continuity map therefore does not only show the formal route. It shows where the real route differs from the intended route. It exposes the difference between what the process says should happen and what people actually have to do to make work progress.
3.2 The lifecycle as the unit of analysis
The first requirement of continuity-gap mapping is to define the lifecycle being studied. This is important because “the supply chain” is too broad to map meaningfully all at once. A supply chain contains many overlapping lifecycle corridors: product lifecycles, order lifecycles, supplier lifecycles, asset lifecycles, return lifecycles, service lifecycles, maintenance lifecycles and recovery lifecycles. Each corridor may also carry several lifecycle dimensions, including physical, commercial, operational, regulatory, sustainability, information, decision and risk dimensions. Mapping does not require every dimension to be examined with equal depth. It requires the dimensions that materially affect the selected outcome to be visible enough to show where continuity is lost.
The lifecycle chosen for mapping should be operationally significant. It should matter because it affects service, cost, resilience, quality, compliance, recovery, working capital, customer trust or strategic performance. A critical component with repeated supplier delays may be a suitable lifecycle to map. So may a customer order journey with frequent fulfilment problems, a returned product stream with poor recovery value, a spare-parts lifecycle that affects equipment downtime, or a regulated product where uncertainty around status creates risk.
The purpose of selecting a lifecycle is not to narrow the ambition of resilience. It is to create a clear starting point. Lifecycle continuity can only be strengthened when the organisation can see where continuity is actually being lost. A general statement that “our supply chain is fragmented” may be true, but it is not yet actionable. A more useful statement is that “the spare-parts lifecycle loses continuity between receipt, inspection, release and service allocation,” or that “the customer order lifecycle loses continuity when stock is physically available but not released for fulfilment.”
The lifecycle should be defined from origin to outcome. This means identifying where the lifecycle begins, where it ends, and what outcome it is meant to protect. In some cases, the outcome will be customer delivery. In others, it may be service restoration, asset recovery, product reuse, regulatory assurance or end-of-life closure. The definition of the outcome matters because continuity is not an abstract condition. It is continuity towards a purpose.
3.3 Mapping the current lifecycle
Once the lifecycle has been selected, the organisation must map how it currently works. This should begin with the real operating sequence rather than the ideal process. The aim is not to reproduce an official procedure, but to understand the actual movement of work through the lifecycle.
A formal process map may show a clean sequence of activities. It may suggest that an order is received, checked, allocated, picked, packed, shipped and delivered. In practice, the order may move backwards and forwards between teams. It may wait for stock confirmation, credit release, customer clarification, quality approval, transport booking, manual override or management escalation. These movements are part of the real lifecycle, even if they are absent from the procedure.
The same is true for products and materials. A formal production process may show materials entering production, being transformed, inspected and released. In reality, materials may be short, substituted, quarantined, reworked, split across batches, moved into temporary storage, manually reconciled or held while a decision is made. A lifecycle map must include these states because they are where resilience is tested.
The current lifecycle should therefore be mapped as a sequence of states rather than merely as a sequence of tasks. A task describes what someone does. A state describes the operational condition of the product, order, material, asset or service at a point in time. The difference is important. “Inspect product” is a task. “Awaiting inspection,” “inspection failed,” “inspection passed but not released,” and “released for fulfilment” are states. Continuity depends on whether these states are clear, owned and connected to next action.
This is where the lifecycle continuity framework begins to differ from ordinary process mapping. A process map can show the route. A lifecycle continuity map shows whether the route remains actionable.
