A dual-carrier proposition has an understandable appeal. The customer hears two suppliers and expects a service arrangement less dependent on one source. That can be a legitimate part of the proposition. I become concerned when the supplier distinction is allowed to settle a different question about physical separation without the relevant evidence. The two claims are related, but one is not a map of the other. An operating leader should want the difference understood before it becomes a disputed expectation.
I approach this as a question about the service undertaking and its explanation. I do not independently certify routes or design a technical alternative. Qualified specialists must assess the relevant infrastructure and the requirements of the actual service. My role is to ensure that their finding remains connected to the commercial proposition and the operating decision, especially when the qualification makes an otherwise attractive description harder to use.
## Supplier diversity and physical separation are different claims
In the fictional 2025 case, a proposed arrangement for six selected business sites involved two carriers. A qualified assessment identified a common physical entry dependency at those sites. The finding did not say that the carriers were the same business or that every element of their services was identical. It said that a particular physical dependency remained. The account needed to represent that fact before the customer understood the arrangement as addressing a broader requirement than the evidence supported.
The commercial team had already invested considerable effort in the dual-carrier proposal. Reopening part of the proposition was inconvenient. Engineering colleagues wanted their assessment treated as a material condition of the discussion, rather than an observation appended after the main decision. I supported that position while asking for the finding to be described precisely. A broad warning about resilience would have been less useful than an explanation of the actual dependency and the limits of what had been established.
There are good reasons to avoid putting sensitive route detail into a general executive or public account. The answer is not to remove the qualification altogether. It is to give each audience evidence appropriate to its decision through the proper process. A public case can explain that a common entry was found without identifying a real site or disclosing a live configuration. The institution making the actual decision still needs access to the appropriate evidence and advice.
I also want the record to distinguish a technical finding from the response chosen around it. The specialist assessment identifies the relevant condition. Management then has to examine the requirement, available alternatives, cost and commercial implications with the responsible parties. A COO cannot make the physical question disappear through a budget approval, and an engineering observation does not by itself settle every commercial term. A sound account preserves both contributions and their respective authorities.
## An uncomfortable finding does not invalidate every part of the proposal
One response to the common-entry finding would have been to leave the proposition unchanged and rely on the difference in carrier names as sufficient shorthand. I did not support that response because it failed to answer the question that had actually arisen. Another response would have been to describe the entire arrangement as worthless. I did not support that either. The finding was specific, and the decision needed to be equally specific about what remained valuable and what required another treatment.
This distinction matters in senior discussions because an inconvenient qualification can polarise the room. One group wants to protect the work already done; another wants to ensure the risk is not understated. If the choice becomes whether to endorse or reject the whole proposal, the organisation may miss the narrower decision that the evidence supports. I try to keep the requirement visible enough that the discussion can address the actual dependency rather than defend a team’s earlier position.
The approved review and alternative-entry work in the case cost SEK 3.6 million across the selected programme. That amount was separate from recurring service charges. I retained it as the cost of the chosen response, not as a calculation of every interruption that might be prevented. The business could assess whether the expenditure was justified without an invented avoided-loss figure. Where a financial estimate would be useful, it would need an explicit basis rather than an impressive number attached to the word continuity.
The customer discussion also had to preserve the scope of the resulting proposition. Addressing the identified entry dependency did not establish uninterrupted service under all conditions. Other factors could remain relevant to the actual arrangement. I wanted the revised explanation to state what the selected work addressed and where another question began. That is not a retreat from accountability. It makes the commitment assessable by the people who will rely on it.
A supplier may reasonably ask that its contribution be described fairly. A common physical condition at the premises does not necessarily reflect a failure in every part of the service provided. The customer may reasonably ask why the distinction was not clear earlier. Both questions belong in the account. The operating leader should be prepared to examine the earlier assumption without turning the review into a general judgement that its evidence does not support.
## State the dependency addressed and the uncertainty retained
I would like a continuity proposition to identify the requirement it is intended to meet before relying on the architecture’s shorthand description. If the relevant concern is a physical dependency, the evidence should speak to that dependency. If the proposition addresses another form of dependence, it should say so. A list of components or suppliers can be accurate and still fail to explain the condition the customer believes has been addressed.
This does not mean that the executive account must reproduce a technical design. It means that management should be able to explain the relationship between the stated requirement, the specialist assessment and the chosen response. Where the evidence is incomplete, the status should remain clear. Where the response leaves a material limitation, the limitation should travel with the conclusion. The account becomes more useful when a reader can see why a particular statement is supported, rather than simply being asked to trust a confident label.
At board level, I would frame my contribution around the quality of that assurance. I could ask whether management has examined the dependency behind a significant customer promise and whether the financial account includes the chosen response. I would not become the route designer or treat operating experience as independent technical certification. The board’s scrutiny should strengthen the demand for appropriate evidence without creating a parallel engineering authority.
I would also revisit the proposition when the service circumstances materially change. An earlier assessment supports an account under its stated conditions; it should not acquire indefinite authority simply because it once resolved a difficult discussion. That does not require a fresh executive debate over every routine event. It requires the responsible organisation to understand which changes matter to the conclusion and how they should be assessed through the proper process.
The six-site case gives me a practical way to describe this habit. Two supplier names were relevant information, but they did not settle the physical question we had to answer. The eventual response had a cost and a defined limitation. Keeping those facts together made the customer proposition more defensible. That is the leadership result I would claim from the fictional example: a clearer undertaking grounded in the appropriate assessment, with no promise that one arrangement can make every future interruption impossible.