Find where adoption stalls and decisions get stuck
Does a new product or method still need your specialists after handoff? Do program decisions wait after the evidence is in? Do teams keep fixing the same problem?
I help teams see why a product or method is hard for the next team to use, why program decisions stall, and where repeat work consumes staff time. Together, we decide what to change and how to measure whether it worked.
Installed is not the same as running on their own.
A diagnostics company can hit its installation target while every new site still depends on the same specialist to troubleshoot routine runs.
On the launch dashboard, the rollout is on track. In that specialist’s week, the hours go to repeat training and follow-up calls, and the team has less time to prepare the next launch or improve the product.
Growth is not evidence of health. Sustainability is. Sustainability is the ability to keep serving customers and meeting quality expectations as demand grows.
Read the Premise: how to tell which steps protect quality and which create avoidable work →Where I help
A product or method has to work in someone else’s lab, and they keep needing help.
- What we’d look at
- The workflow from handoff to routine use, and whether each fix belongs in the product or method document, the training, or support.
- What you’d get
- A log of where help is needed, traced to its source, with each issue assigned to the document, the training, or a named contact.
- What we’d measure
- Time to first successful independent run. Follow-up support hours or clarification requests per site.
Program decisions wait after the evidence is ready.
- What we’d look at
- Who prepares the evidence, who can decide within existing procedures, and what needs formal review or escalation.
- What you’d get
- A decision map: who prepares the evidence, who decides, and which steps need formal review.
- What we’d measure
- Time from evidence ready to decision.
Teams keep fixing the same problem.
- What we’d look at
- Where repeat tests, incomplete handoffs, or recurring support questions start, and the time and materials they use.
- What you’d get
- An estimate of what the repeat work costs in time and materials, and the changes worth making first.
- What we’d measure
- How often the work repeats. Staff hours and materials used.
From pharma. During an analytical method transfer, the receiving lab, at another site or a CDMO, keeps sending questions. Comparative runs are repeated, and analysts at the sending lab are pulled off their own work. The transfer protocol, acceptance criteria, and QA review stay as they are. The work looks at what the protocol doesn’t capture: assumptions written into the method document, know-how that was never written down, and where each question starts.
From biotech. A routine program decision, such as releasing the next set of experiments in an approved plan, keeps going back to the founder after the data is in. Mapping it shows who prepared the evidence, which part the team can decide within existing procedures, and which part needs formal review. The review still happens where it is required. The rest stops waiting.
What you get from an engagement
We start with one workflow or one decision. Every assessment gives you the following, and the section above shows the specific output for each situation:
- A map of how the work moves today
- A baseline built from the data you already have
- A short list of changes, each with a proposed owner and a measure
When the engagement includes a pilot, I work with your team to test one change on one workflow or with a small group of users, through your change control. We review the results before expanding it.
Timing depends on the scope.
Where I’ve worked the handoffs
At Abcam, I led a mammalian cell line expansion and banking team. Supporting a live-cell product meant the work could not stop at the lab bench. I helped define how material moved from expansion into banking, and worked with logistics and the other receiving teams so each one knew how to handle the material at its handoff.
At Leica Biosystems, I led a national field applications team supporting academic, biotechnology, and pharmaceutical labs, including through new product introductions, and developed training materials for the colleagues who supported them.
I’ve also collected and processed clinical specimens myself, so I’ve seen how timing, workload, and handoffs determine whether a sample arrives ready for testing or the work has to be repeated.
Each is the same problem from a different side: the work holds only when the people receiving it know what to do next.
How many of your sites can run on their own after go-live?
In the example, 38 of 48 sites reach routine independent use two months after the last install; with fewer sites needing extra help, all 48 do, and the team spends 140 fewer hours on repeat work.
Try the simulator →The simulator is a simplified model with illustrative numbers, not a forecast. It runs in your browser, and what you enter is not sent anywhere while you use it. Pick a scenario, change the assumptions, and see what moves.
- Diagnostics rollout →
Two rollouts with the same installation schedule. Change how often sites need extra help and how many specialist hours are available, then see how many sites reach routine independent use, how many hours go to repeat training and troubleshooting, and how many support requests carry over into the next week. - What the repeat costs: specimen redraw →
A specimen waits too long at a busy collection site and can’t be used, so the patient needs a redraw. Compare three responses to the same first miss: repeat the step, check the likely cause first, or find it in rehearsal. - What the repeat costs: assay evaluation →
During an evaluation, part of the expected signal is missing. It could be the assay or the imaging setup. Compare the same three responses and what each costs in specialist time and scheduled evaluations.
What happens on a busy shift?
The examples above follow from one premise and five axioms. Each axiom below comes with what it means in plain terms and a question to ask about your own workflow.
Mission precedes operations. Before you change a workflow, decide what it needs to accomplish. For a new diagnostic tool, the purpose is easy to state: a lab runs the workflow reliably on its own, during normal work. That is routine independent use. Each axiom asks a different question about that outcome.
Axiom I · Environment
The environment shapes what people can reliably do.
In plain terms: to improve performance, change the conditions people work in rather than asking them to work harder.
Ask: Can users complete a run with the time, tools, and instructions available on a normal shift?
Axiom II · System Expression
Every outcome is the expression of a system.
In plain terms: results are what the underlying structure was always going to produce, not accidents or acts of individual will.
Ask: What do users run into at the step that keeps generating support requests?
Axiom III · Fragility
Growth without structural integrity compounds fragility.
In plain terms: scale applied to a weak foundation multiplies risk.
Ask: What happens to the support queue when more sites go live and specialist capacity stays the same?
Axiom IV · Measurement
Measurement changes behavior. Choose carefully.
In plain terms: what you measure becomes what you optimize.
Ask: Would your installation dashboard tell you which sites can run independently?
Axiom V · Incentive Drift
Institutions drift toward whatever they repeatedly reward.
In plain terms: over time, an organization becomes the behavior it consistently reinforces.
Ask: If the team is rewarded for closing tickets, who has the time and the ownership to fix the recurring issue?
I’m Alex de Verteuil. I hold a Ph.D. in biology. At Abcam, I led cell line operations for commercial mammalian cell line development. At Leica Biosystems, I led a national field applications team and developed training materials that helped colleagues support life science researchers.
More about Alex →Tell me what your team is trying to accomplish and where the work keeps getting stuck.
A sentence or two is enough: the workflow, the team receiving the work, and what has already been tried. I reply to every message myself. Your message is used to reply to you and is not sold. How your information is handled.
Start a conversation