Dispatch is a clear event. A unit leaves the supplier, a record changes and an operational milestone can be reported. The customer’s intended outcome may still depend on site preparation, access, assessment and installation. I want the product proposition to acknowledge that distance between the event and the usable experience. This does not make the product team responsible for managing every activity at a customer site. It means the company should explain what the offer requires, which party must act and what remains before the equipment can enter its intended workflow.
The fictional Pravellen programme involved 240 planned workstation sites. Before dispatch, 168 had confirmed the specified prerequisites and seventy-two had not. We made preinstallation assessment explicit in the proposition and staged a ninety-unit pilot. At review, seventy-three units had been installed and seventeen remained pending. The six-point-three-crore programme expense did not establish a causal improvement against an earlier baseline, because the case supplied none. It also did not establish a clinical result or determine when finance should recognise the transaction.
Name the state the milestone actually describes
I would begin by identifying the different states in the customer’s journey. An order, a confirmed site condition, a dispatched unit and an installed unit describe different events. Each can be useful, provided the account does not let one stand silently for another. The product leader should understand which state supports the claim being made to the customer and which supports the progress statement being made internally. A milestone can be accurate in an operations report yet misleading if repeated as evidence that the customer is already able to perform the intended work.
The dispatch-first argument had a legitimate concern behind it. Delaying shipment can complicate schedules and hold equipment at the supplier while site work continues elsewhere. I would want those costs and constraints examined. But sending the unit does not itself resolve the missing condition. The decision needs to compare the consequences of staged dispatch with the consequences of equipment arriving before the intended installation can proceed. The answer may differ by product and site; it should not be settled by the desire to make the progress column look complete.
In the case, service colleagues challenged the assumption that outstanding prerequisites could simply be absorbed after delivery. Their concern changed the product account before it became a customer expectation. I chose to make the assessment and dependencies visible as part of the offer. The site still owned its preparation, and engineering and service colleagues retained their assessments. The product decision was to stop presenting those dependencies as incidental work outside a supposedly finished proposition. That made the offer more precise without transferring every operational responsibility into the product function.
Make prerequisites part of the offer
A prerequisite should be understandable enough for the responsible person to act on it. A broad statement that the site must be ready may conceal several different conditions and owners. I would ask the relevant colleagues to describe the conditions at the level needed for a meaningful assessment, including how confirmation is obtained and what happens when something remains unresolved. The exact requirements belong to the particular equipment and its intended setting. A general leadership essay should not invent a universal installation checklist or imply that returning a form proves technical suitability.
The customer also needs to know which decisions remain with the supplier. If a site condition requires further review, the commercial description should not suggest that the buyer can approve it independently through a simple declaration. Conversely, the supplier should not imply it will perform site work that the offer leaves with the customer. I would want the boundary stated before the parties rely on it. A clear product proposition allows the commercial, service and site conversations to refer to the same responsibilities, even though different people carry them out.
Staging can then become an explicit choice rather than an unexplained delay. The parties should know what evidence permits the next step and what remains pending. That account must remain proportionate; not every minor uncertainty requires a board-level discussion or a new product decision. The point is to keep material dependencies visible at the appropriate level. I would ask product and service leaders to identify where a missing condition changes the intended experience or creates a commitment that should be reconsidered, rather than simply adding more administrative steps to every delivery.
Report the remaining work without moving the boundary
The pilot ended with seventeen units pending. Those units did not become installed because they had been dispatched, scheduled or discussed with the customer. I would retain that status even when the programme needed a concise progress summary. The account can explain what has been completed and the nature of the remaining work without presenting incompleteness as failure in every case. Some dependencies may be expected and manageable. They still belong to a different state from the one the product promised as the usable outcome.
The absence of a prior baseline also matters. Seventy-three installations among ninety pilot units cannot establish how much the staged approach improved performance compared with another process. The case supports an account of what happened, not an invented before-and-after result. A later evaluation could ask a more demanding question if it had appropriate evidence. I would prefer to preserve that distinction than attach a causal claim merely because the team believes the new approach was sensible. Product judgement and measured programme effect are related but separate parts of the story.
Financial recognition requires the same separation. A product account may discuss delivery and installation states without determining the accounting treatment of a real transaction. Finance and the appropriate advisers need the actual terms and evidence. I would keep those owners involved and avoid using the leadership narrative to settle a conclusion outside its scope. Similarly, an installation observation does not demonstrate a patient outcome or quantify a clinical delay. Those claims would require different evidence, and adding them would make this operationally grounded product story less credible.
For a prospective director, the useful question is whether management’s account preserves the material distance between a reported milestone and the customer promise. The board should receive enough context to understand that distance without taking over site scheduling. A real example would need verified terms, authorised evidence and the applicable specialist assessments. The fictional case illustrates how I would approach the product decision: make dependencies visible early, retain the work still pending and let each milestone describe the event it actually records. A clearer offer begins when the company stops asking a dispatch number to tell the whole customer story.