FROM THE WORK
A promising test is only the start. The next job is to make ownership, support and the evidence for a wider decision clear.
A pilot can look successful and still go nowhere. The team may like the idea, patients may find it useful, and the early numbers may look encouraging. Then the pilot ends and everyone returns to their usual work.
Often the missing piece is not enthusiasm. It is a decision about what happens next. Who owns the service after the project team steps away? Who trains new starters? Who handles problems, updates the content and checks whether the change is still helping?
Before a test begins, agree what you need to learn and what would make you continue, adapt or stop. Choose a few measures that matter to the service: the patient experience, the work involved and any effects elsewhere in the pathway. Keep the definitions steady enough to compare what happened.
Talk to the people who will run the service as well as the people who use it. A tool that saves one team time but sends extra calls to another has moved the work, not necessarily improved it. Make the handoffs visible while there is still time to change the design.
At the end, write down the decision, the evidence behind it, the unresolved risks and the person responsible for the next step. Sometimes the right decision is to stop. That is useful too: the team has learned before investing in a larger rollout.
A pilot is not a miniature launch. It is a chance to find out what a service needs before asking more people to depend on it.
Explore the Practice Lab →