How many of your sites can run on their own after go‑live?
Compare two rollouts with the same installation schedule and specialist capacity. See how many sites can run on their own and how much specialist time goes to repeat training and troubleshooting.
Start with the example numbers, or enter your own.
What the model shows
Your rollout: change the numbers
Your numbers are locked while the form is open, so the read matches what you send.
The hours left after other duties, for training, troubleshooting and follow-up. All specialists together.
Assumptions: site variation, rollout plan, staffing, reporting and ownership
See the details
| Your rollout today | Comparison rollout |
|---|
Where the specialist hours go
Each site can look lean on its own. Across the system, every site that can't run on its own is a kink in the hose: specialist hours go in, and repeat work holds them there instead of reaching the next site, the next product or the next patient.
Sites that took more than eight weeks to run independently
Why this happens
The five axioms of the A. de Verteuil Framework, each read against your rollout today. Each one gives a question to investigate. The label shows how strongly your numbers point there.
Your rollout read
Where I would look first, for the rollout you entered.
Your rollout read appears here, on this page, for the numbers above. It covers where I'd look first, what I'd check, and one change worth testing.
Approximate numbers are fine. You don't need to enter company names or confidential details.
To show the read, I ask for your name and email; company is optional. When you send the form, it includes the inputs above: sites per month, months, weekly specialist hours, hours per site, both extra-help shares, site variation, rollout plan, staffing cut, what leadership looks at first, and who fixes recurring issues, plus which axiom the model points to first. See the privacy policy.
Prefer to talk it through instead? Email contact@adeverteuil.com.
This is a simplified model for illustration. It is not advice for your situation.
How the model works
Running on their own means routine independent use: the site has finished training and needs no further specialist help in normal work. The model does not track the earlier milestone, a site's first successful independent run.
This is a simplified model for discussion, not a forecast. It runs week by week from the first install until two months (eight weeks) after the last one. The two rollouts see the same sites with the same conditions, so differences come only from the extra-help share.
- A site that gets the help it needs runs on its own in about four weeks.
- A site that needs extra help needs two and a half times the usual hours. It adds half an hour of troubleshooting each week until it runs on its own.
- Sites that need extra help come from two places: the share you enter, and, with the same plan everywhere, sites whose conditions sit far from typical. The page reports both, and counts a site that falls in both groups once.
- Sites differ in patient flow, acuity and local procedures, so each has its own workload. A plan fitted to each site costs about an hour more per site and removes the mismatch.
- The team works the oldest sites first. Training that does not happen this week comes back as repeat work: three tenths of the missed hours return as retraining and troubleshooting.
- Repeat hours are the hours spent on troubleshooting and on retraining after missed help. They are reported two ways: as a share of the hours the team used (Why this happens, Axiom II), and as a share of all the hours available (Where the specialist hours go).
- A site that took more than eight weeks to run independently is counted from its own go-live date. Sites that never ran on their own within the model's window are included.
- Removing specialist hours takes them off the weekly total in full. Automation is assumed to take over half of the routine training it replaces and none of the repeat work. A week at full capacity counts toward burnout risk.
- Axiom labels: Low, Moderate or High. Axiom I (Environment): share of sites needing extra help up to 15%, up to 35%, above. Axiom II (System Expression): share of used hours on repeat work up to 15%, up to 35%, above. Axiom III (Fragility): no carry-over at the last install, a steady carry-over, a growing one. Axiom IV (Measurement): sites not yet on their own at the last install up to 15%, up to 30%, above; when leadership already looks at independent use, Low up to 40% and Moderate above. Axiom V (Incentive Drift): a named owner, whoever has time, no one (one step higher when leadership counts tickets closed and repeat work is above 15%).
What the repeat costs
The first miss creates work. Acting on the wrong explanation creates more. Pick a case and compare three responses to the same first miss. The team, the planned workload and the launch date are the same in each. Only the response changes.
The default result
1 · Assumptions
Illustrative numbers, not data. Change any of them.
2 · What the miss costs
| Repeat first | Check the likely cause first | Find it in rehearsal |
|---|
Patient return visits, customer evaluations and field visits are counted on their own. They are not staff hours.
3 · Where the spare hours go
4 · Timeline
How this works
This is a simplified model for illustration. The numbers are synthetic and the roles are generic. It is not advice for your situation.