Make the work after the decision visible
An approved idea still needs people, time and a route through the working organisation. A change can stall when the next action is unclear, dependencies appear late or the people delivering it were absent from the original case.
Our implementation-planning direction within PHARMORIS connects a medicines proposal with that practical work. The purpose is to give teams a clearer basis for deciding whether to proceed, what support is needed and how progress will be examined.
In the conversation.
NEUVIOR and our founder’s perspectives have appeared across science, business and technology publications.
Reporting, commentary, letters and podcast appearances | Read each feature for its format and source.
Understand the process that already exists
Begin with how the task happens today. Who prepares the evidence? Who reviews it? Which handovers need clarification? Where is information reconstructed, and which decisions require agreement from another team?
This account helps identify the real constraint. A coordination problem may benefit from clearer ownership. A capacity problem may require resources. An unresolved clinical or supply question may need further evidence. Naming the constraint allows the response to fit the work, rather than assume that adding software will resolve every obstacle. It also establishes a fair baseline for evaluation.
Give each action an accountable owner
A list of tasks does little if responsibility is shared so broadly that nobody can move the next step. Identify who prepares, who decides, who delivers and who needs to be consulted. Authority and workload both matter.
In a pharmacy group, headquarters may provide training or resolve a supplier question while branch teams deliver the service. In a hospital, clinical, pharmacy, finance and operational colleagues may each own a distinct decision. A useful plan makes those responsibilities understandable without turning the process into an endless chain of meetings.
Put dependencies into the commercial case
A medicines change may depend on staff training, communication, supply arrangements, local approval or access to the right expertise. Some dependencies can be addressed quickly; others can determine whether the proposed change is worthwhile at all.
Bring these requirements into the case early. A buyer needs to understand the work carried by its own organisation as well as the supplier’s contribution. This makes the decision about affordability and timing more realistic. It can also reveal a smaller first phase that is useful on its own and easier to evaluate.
Keep the purpose visible as circumstances change
Implementation introduces new information. The workload may differ from the estimate, a supply condition may change or users may identify an exception. The team needs to know whether this affects the original reason for proceeding.
A useful plan preserves that reasoning and identifies meaningful review points. What would justify adapting the approach? Which condition would make a pause sensible? What evidence is needed before extending the change? These questions keep the programme focused on its purpose and allow the organisation to respond without losing the history of the decision.
Change needs somewhere to land.
The proposed change meets an existing working day: people, permissions, dependencies and other responsibilities. An action list earns its value when those practical conditions are understood.
Examine what must be ready before the action, what could interrupt it and what the responsible person needs to report back. The purpose is an executable next step, rather than another dashboard.
Film source and contextAbstract optical stock movement. Not data, an instrument signal or software output.
A promising branch is not the whole network.
An investment case gets stronger when it explains the conditions for repetition. Make the next commitment depend on evidence.
A pharmacy group has an encouraging early result from one well-supported site. Before extending the change, it wants to know whether ordinary branches have the cover, demand, governance and support needed to repeat it. The next comparison should deliberately include different operating conditions, rather than select only the easiest settings for a showcase.
Supports an investable boundary: suitable now, suitable after a defined dependency, unsuitable under present conditions or still unknown.
What would we need to understand?
- The specific operating change and decision owner
- Baseline service mix and professional cover
- Central and local implementation effort
- Site differences, non-participation and exceptions
Constructed decision example | No customer results are shown.
Give the front line a workable experience
A centrally attractive process can create extra work in the place it is delivered. Branch staff and clinical teams need clear instructions, an understandable escalation route and realistic demands on attention. Their experience is part of the implementation case.
A proposed evaluation should include onboarding, queries, checking and the effort of keeping the process current. Compare variation between settings rather than assume a single workflow fits everywhere. A local difference may indicate a design problem, a training need or a genuine constraint that should shape the approach.
Measure follow-through against good existing practice
Our planned implementation work asks whether the complete approach improves a defined process. Relevant measures include clarity of ownership, missing handovers, delays, rework, completion and the effort needed to maintain the record.
Observed implementation should be distinguished from an approved plan or a completed software task. The comparison also needs to recognise other changes happening at the same time. In England, NHS medicines-optimisation guidance places emphasis on collaborative system delivery; the practical contribution still has to be demonstrated in the particular setting being examined.
Bring the change that needs a route forward
Tell us what has been agreed, where delivery is getting stuck and which team has responsibility for the next step. Include the current approach and what a worthwhile improvement would mean.
An implementation conversation can then examine a bounded evaluation with appropriate professional input, a credible comparison and a clear account of the resources required.