Skip to main content

The medicines business | A question to investigate

Supply is back. What should change next time?

The return of stock can close a supply alert while leaving important questions unanswered. Which actions helped? Which assumptions failed? What work remained in pharmacies, procurement and customer services after the headline problem ended? NEUVIOR is interested in the review after recovery, when an organisation can turn an episode into a more useful understanding of its response without claiming that every favourable change was caused by its own intervention.

Film credits

In the conversation.

NEUVIOR and our founder’s perspectives have appeared across science, business and technology publications.

University of Warwick IATL | AI Ethics NowpharmaphorumTechRadar ProET PharmaFinancial TimesPharmaceutical TechnologyPharmaTimesManufacturing ChemistDigital HealthDaily BusinessTheBusinessDesk.comStartups MagazineInsider MediaYorkshire PostYork PressBusinessCloud

Reporting, commentary, letters and podcast appearances | Read each feature for its format and source.

Define recovery before measuring it

A replenishment date, normal order fulfilment and a stable position for customers are different milestones. A review should identify which one is being discussed and which evidence supports it. It should also examine the residual workload: outstanding orders, communications, alternative arrangements and unresolved exceptions. If recovery is defined only by a central stock position, the analysis may miss the work still being carried elsewhere in the supply chain.

Use the established coordination context

NHS England’s supply-issues guide describes management and escalation routes in England (NHS England, n.d.). EMA’s ESMP supports information exchange in European shortage contexts (EMA, n.d.). These references concern different jurisdictions and responsibilities. A proposed learning review would connect the relevant official context to the organisation’s own episode, without implying that a local retrospective exercise replaces national coordination or establishes the effectiveness of a wider shortage-management system.

Separate the event from the response

A shortage may end because manufacturing resumes, demand changes, another supplier becomes available or several factors coincide. A communication improvement can still matter without causing recovery. A useful review should reconstruct the timeline and distinguish external developments from the organisation’s decisions. It should record what was known at each point, including estimates later found to be wrong. Otherwise hindsight can make the response look more coherent and predictive than it actually was.

A lesson that can be tested next time

The proposed deliverable would connect each improvement action to the evidence that motivates it and the future observation that would test it. It would also preserve questions the episode cannot answer. That creates a practical learning agenda without claiming that a retrospective explanation has proved which intervention will improve the next response.

A public decision brief | An illustrative example

Open the question.
Inspect the reasoning.

Choose a business question, then look beneath its claim. See what a public source supports, what depends on the local setting and what a useful next step could be.

A distribution, quality or operations team examining the completeness of a temperature-controlled handoff record.

Can the next responsible person see the whole handoff?

Before an exception can be assessed, the responsible people need a coherent record: the item, the relevant conditions, the journey and the evidence still missing.

A proposition to investigate

Make the evidence easier to hand over.

A structured evidence brief could help a team identify what is present, what conflicts and what must be requested. The proposed value is a clearer handoff for authorised review. It does not decide whether a medicine can be used, released, returned or destroyed, and it supplies no treatment recommendation.

This is a constructed records question, not a live temperature event or disposition instruction.

What the next brief would contain

A decision someone
can commission.

The decision
Whether the handoff process needs a structured evidence request or evaluation.
The comparator
The organisation's current records and authorised handoff procedure.
The evidence
Applicable requirements, custody, logger details, time alignment, completeness and reviewer questions.
Stop or redesign
Stop if responsibility is unclear, evidence cannot be verified or the activity drifts into unauthorised disposition.

Constructed public example | Not PHARMORIS-generated software output or a measured customer result.

Keep this example brief

A proposed PHARMORIS retrospective

We would select one completed episode with a supply owner and permitted documentation. Inputs could include dated estimates, aggregate fulfilment information, approved communications and documented response actions. The comparator would be the organisation’s usual incident review. A proposed evidence-linked brief would be assessed for timeline accuracy, clarity of unresolved questions and the distinction between observed events and causal interpretations. No customer or patient information would be included beyond what a justified and authorised purpose required.

Measure the usefulness of the learning

Candidate outcomes include material timeline corrections, assumptions that can be tested in a future episode and improvement actions with an owner and review date. The study could also assess whether different functions agree on what the evidence supports. The number of lessons listed is not enough. A smaller set of actionable findings may be more valuable than a long retrospective narrative. Any claimed operational improvement would require later observation rather than being assumed from the review itself.

When an explanation becomes too convenient

We would pause if key records were reconstructed from memory without being labelled as such, if the analysis attributes recovery to actions without a credible basis, or if only favourable episodes are selected. The review should stop if its purpose becomes assigning blame without understanding system conditions. A useful finding may be that the data cannot support a causal conclusion. That limitation can still guide better recording and a more informative comparison during a future event.

A conversation after the pressure has eased

A supply, quality or operations leader can bring one recovered episode and a question that remains unresolved. Explain what the organisation would like to do differently and which decision the review should inform. We can explore a bounded learning exercise with a clear comparator and practical output. The commercial purpose is to convert experience into a more disciplined future response, with the evidence strong enough to challenge the comfortable explanation as well as support the useful one.

Another useful angle.

NEWSPerspectives & features