“The installations are complete” can be an entirely accurate statement and the beginning of an unresolved conversation. The field team may have done the work within its assignment, while configuration or customer acceptance remains elsewhere in the organisation. I have no interest in diminishing the first result. I do want the provider to explain the second without making the customer reconstruct the boundary between our functions. That is a management responsibility, not a request for every team to own every task.
Multi-site programmes make the distinction especially visible. Different locations may reach different stages, and a percentage can hide the combination behind it. A senior review may welcome the apparent clarity of one number. The customer may need to know which services can be used on the agreed basis and what remains to be done at each site. Both audiences deserve an account that is clear enough to support their decision, rather than one measure used indiscriminately for both.
## Ask what has actually reached completion
At the review point in our fictional 2016 programme, twenty-one of twenty-four sites had completed technical installation. Seventeen had reached the agreed customer handover. Four installed sites still required configuration or acceptance work, and three had installation pending. Those quantities are consistent: seventeen plus four accounts for the twenty-one installed sites, and the remaining three complete the twenty-four-site population. The arithmetic is useful because it forces the report to retain the stages it might otherwise compress.
It would have been wrong to describe all twenty-four customer services as complete. It would also have been wrong to imply that the installation team had achieved nothing at the four sites awaiting the next stage. I wanted a report that could recognise substantial progress and preserve the continuing undertaking at the same time. The distinction should have been available in the main discussion, not discoverable only after a customer challenged the headline.
The words matter because they shape what happens next. If the programme is declared complete, the remaining work may lose its connection to the original commitment, even when everyone intends to finish it. If every completed installation is treated as unresolved until the entire estate is handed over, the field team’s contribution may become difficult to assess. A more specific account gives each stage its proper place and helps the responsible people understand what they are being asked to close.
I would not assume that the same acceptance condition applies to every service or agreement. The relevant stage must be established from the actual undertaking. A management narrative cannot decide contractual treatment simply by choosing a label. My point is narrower: once the appropriate condition is known, the operating report should describe it accurately and distinguish it from other legitimate measures of progress.
## Recognition does not require closing the wider obligation
The installation team wanted recognition for difficult work across the estate. That was reasonable. An account that focuses only on what remains open can make completed work invisible and encourage defensive reporting. I wanted the twenty-one installations acknowledged explicitly. At the same time, the account team needed to explain the four installed sites still awaiting further work and the three not yet installed. Recognition and accountability were not opposing choices; they depended on the same precise description.
We funded SEK 1.7 million in temporary parallel service and support while the programme continued. That expenditure belonged in the explanation. It was not evidence that the customer had experienced no inconvenience, and it did not establish the complete financial effect of the delay. I retained it as a consequence of the position we were managing. Commercial treatment remained subject to the agreements and authorised decisions, rather than being inferred from a percentage on the programme slide.
A colleague proposed treating the outstanding items as a separate follow-up list after closing the main delivery. I understood the administrative attraction. Programmes need endings, and not every minor task should keep a major body of work open indefinitely. In this instance, however, the remaining configuration, acceptance and installation stages were still part of the customer undertaking being described. Moving them elsewhere would have made the completion statement less representative of that undertaking.
The better response was to keep the programme account connected while making the specific remaining responsibilities manageable. That does not require a single person to perform every task. It requires the provider to maintain a coherent view of the customer obligation across the people who do. I wanted the reader to be able to see what had changed since the previous review and which supported conclusion could now be drawn, without assuming that absence from the main list meant completion.
There is a fairness issue here that operators sometimes overlook. When the wider obligation is poorly defined, teams can be judged for circumstances outside their remit or rewarded for moving work into somebody else’s queue. A clear stage account does not remove all disagreement, but it gives the discussion a better basis. It can show where a team has delivered, where another decision is needed and where management must resolve a dependency between them.
## The unfinished part still belongs to the original promise
I read an outstanding item differently when I can see the undertaking from which it arose. A configuration question after installation is not just another technical task; it may affect whether the customer can accept the intended service. A pending installation at one location may have a different consequence from a documentation correction at another. The account should retain enough context for the response to be proportionate, rather than making all open items equivalent through a shared status.
This perspective does not justify indefinite programme extension. Closure should be assessed against the actual scope and agreed conditions, with a clear treatment of work that legitimately belongs elsewhere. The discipline is to make that treatment explicit. If management proposes separating an item, it should explain why the original undertaking can still be described as complete. That explanation is more useful than an arbitrary insistence that every record must remain in one place forever.
The customer also needs a coherent conversation. They should not have to interpret our organisation chart to understand why an installed service still awaits the next stage. A responsible update can identify the relevant condition and the next agreed action without disclosing unnecessary internal detail. I want the provider to own that explanation. Saying that another function has the task may be true, but it is not by itself an answer to the customer’s question about the service.
For a board or search partner examining my leadership record, the case is therefore about more than delivery administration. It shows the choice to keep an inconvenient remainder connected to a visible success, and the expense required while the work continued. It also shows where my authority stopped. I coordinated the operating response; I did not replace technical assessment or determine contractual rights through the language of a public profile.
I would like a completion statement to be useful to the person whose undertaking it describes. Installation is a real result and deserves its own measure. Customer handover may require something further. When both remain visible, the organisation can recognise progress without asking the customer to accept an ending that has occurred only inside the report.