A customer asking for a connection date is not asking to learn the provider’s internal organisation. They need to plan premises, people and work around a service becoming available. I think that need makes the quality of the date more important, not less. A provider does the customer no favour by offering a familiar interval before it has established the work that the particular order requires. The promise may be simple while the responsibility behind it remains unclear.
I have heard the argument that a more qualified commercial proposition will lose business to a competitor prepared to sound certain. That is a real commercial concern. It does not establish that the operating work will conform to the simpler proposition. The COO’s contribution is to connect the expectation with evidence early enough that the business can make a useful commitment, rather than leave delivery teams to explain the difference after the customer has already organised around it.
## The simple proposition contains an operating assumption
In our fictional 2023 review, sixty contracted service orders had been discussed using a common thirty-day activation expectation. Thirty-eight could use existing access arrangements. Twenty-two required additional external work. That division did not tell us the completion date for every order, but it showed why one interval was doing more work than the evidence supported. The commercial description had treated different delivery circumstances as if they were the same proposition.
An existing-access order can still encounter a difficulty. An order requiring external work can sometimes progress more straightforwardly than expected. I would not replace one overgeneralisation with another by attaching a fixed outcome to each category. The point of the review was to make the order’s actual conditions relevant to the commitment. A useful assessment should identify the material dependency, the responsible next decision and the evidence on which the proposed date rests.
The sales team wanted a proposition it could explain consistently. I did not regard that as an objection to responsible delivery. A business needs a commercial language, and an elaborate internal description can make it harder for a customer to understand what is being offered. The task was to build consistency around the assessment and the meaning of the commitment, rather than around an interval that preceded the relevant knowledge.
I also wanted our operating colleagues involved before their contribution became a list of exceptions. When delivery joins only after a date has been repeated to the customer, its questions can sound like reasons to avoid responsibility. When the relevant work is understood earlier, the same questions help form the responsibility. That difference affects how functions work together, but it does not depend on pretending that every order can be fully predictable at the point of sale.
## Correcting the message does not erase the undertaking
The review led me to stop using the universal thirty-day message and support service-specific commitments after assessment. Existing customer agreements still had to be addressed on their actual terms. A management decision to change our internal explanation did not remove an undertaking already made or determine the remedy for a missed expectation. Those questions belonged with the responsible commercial and legal colleagues and the customer discussion.
The programme incurred SEK 4.8 million in remediation and coordination expense. I retain that cost because a corrected proposition can otherwise be presented as a simple improvement in management discipline. The organisation had already created expectations, and addressing them required work. I would not claim that the expenditure represented every financial consequence or that the revised approach immediately improved retention. The account can explain the correction without inventing a broader result that was not established.
There is a particular temptation to revise the language of the original promise after the event. A date that the customer understood as a commitment can become an internal estimate in the later report. I would want the actual agreement and communications examined rather than allow a convenient label to settle the question. The operating account should preserve what was understood, what became known and how the discrepancy was resolved through the proper process.
That candour also helps the organisation learn. If the earlier expectation is quietly rewritten, the next review may conclude that delivery alone caused the difficulty. If the original assumption is retained, the business can examine how the proposition was formed and which evidence was missing. The aim is not to transfer blame from one function to another. It is to make the decision available for scrutiny at the point where the organisation can change it.
I would also distinguish an honest qualification from a proposition so vague that it leaves the customer unable to plan. Saying that everything depends on circumstances is not a sufficient operating response. The customer needs the best supportable commitment, an explanation of material conditions and a responsible route for the next update. The organisation still has to do the work of making the uncertainty intelligible, rather than simply passing it outward.
## Give the customer a date that has an explanation
A useful service date should carry a reason that the provider can explain without disclosing confidential infrastructure or overwhelming the customer with internal detail. Where existing access supports a proposed interval, the account can say so. Where additional work requires another decision, that dependency should be represented appropriately. The precise treatment depends on the service and agreement; my broader point is that the date should arise from the order’s circumstances rather than substitute for examining them.
This also changes the executive review. I would ask which commitments are supported by the relevant assessment, which material dependencies remain and how customers are being kept informed through the agreed process. A single average interval may still have a legitimate use in understanding the portfolio. It should not be allowed to describe an individual undertaking without regard to the distribution and conditions behind it. The measure and the promise operate at different levels.
A business must eventually make decisions with incomplete knowledge. I do not see responsible commitment as waiting until uncertainty has disappeared. It means being clear about the evidence used, the conditions that matter and the authority to agree the undertaking. Where a later event changes the position, the correction should retain its cost and its connection to the original account. That is different from treating every difficulty as proof that no date should ever have been offered.
From a board perspective, I would want to understand whether a growth proposition contains an operating assumption that has been tested against the actual work. The board should not schedule a customer installation. It should be able to ask how management knows the promise is supportable, what happens when the underlying conditions differ and whether the reported economics include the cost of correcting earlier expectations. Those questions connect commercial ambition with operating responsibility without confusing their roles.
I believe a connection date earns its usefulness through that explanation. The customer needs a commitment they can plan around, and the provider needs an account its delivery organisation can recognise. When those requirements meet, the date becomes more than a phrase that wins the first conversation. It becomes a statement of work the organisation has examined and is prepared to own, including the obligations that remain when the circumstances become more difficult than the original summary suggested.