HEALTHCARE · ORGANIZATIONAL TRANSFORMATION
A university hospital had to roll out, within 4 months, a new emergency-care protocol mandated by national health authorities. The text changed triage priorities, care timelines by condition and coordination between emergency medicine, radiology and specialties.
The department had 240 healthcare professionals and had been under structural strain for 24 months. The question was not whether the protocol was good. It was what it would change in real work.
THE PROBLEM
A new procedure arrives in an environment that already has its habits, routines, hierarchies, informal coordination, time constraints, differences in experience and atypical situations. The protocol may be coherent in theory ; its real effect depends on how it meets that organization.
Here, the organization had been under strain for 24 months : high turnover, absenteeism above the hospital average, several local labor disputes over working conditions. Management feared blockages, a temporary deterioration in care quality, or even departures.
The hospital’s executive management and the head of the emergency department used our system to test 6 rollout scenarios, with 31 dynamic follow-ups on resistance points identified live and an 18-month projection.
WHAT IS THE SAME FOR EVERYONE
WHAT DIFFERS FOR EACH GROUP
A MECHANISM : PRESCRIBED WORK, REAL WORK
Conceptual diagram. It does not represent any measured value : it only identifies the stages through which a written rule becomes actual practice.
Apparent resistance may be genuine opposition. It may also be a professional adaptation to a constraint the protocol has not sufficiently integrated. Adaptation and non-compliance are not the same thing.
THE INCOMPLETE QUESTION
A healthcare professional can support the principle, consider the rule useful, and still be unable to apply it systematically. Conversely, a skeptical professional can correctly apply a procedure that fits well into their work. Stated support is not actual adoption.
THE QUESTION USUALLY ASKED
“Are you in favor of the new protocol?” This question produces little actionable information.
WHAT THE CASE SHOWS
68 % of healthcare professionals do not reject the protocol: they recognize its technical relevance.
WHAT THEY REJECT
A rollout pace perceived as abrupt and incompatible with the existing workload.
WHAT THIS IMPLIES
Stated support is not actual adoption. The decisive parameter was not the content, but the rollout conditions.
WHAT IS TESTED
The protocol deployed is identical in all six scenarios. What varies are the conditions : the pace, who delivers the training, and whether individual support exists. That difference in rollout conditions was the object of the simulation.
640 synthetic healthcare professionals were interviewed individually across the 6 rollout scenarios, with 31 dynamic follow-ups on resistance points identified in real time. The 18-month projection incorporated within-team adoption and resistance dynamics, collective learning effects and departure risks among the most mobile staff.
SIMULATED POPULATION
The reconstructed population covers 2 400 European emergency-care professionals, calibrated on public hospital-sector surveys and the university hospital’s internal studies on working conditions in emergency departments.
It is structured into 11 profiles crossing profession — physician, resident, nurse, nursing assistant —, seniority, relationship to hierarchy, prior exposure to protocol redesigns and involvement in local labor disputes.
EMERGENCY PHYSICIANS
high clinical autonomy, constant trade-offs between rule and situation
INTERNS
low seniority in the department, high dependence on the written framework
NURSES
coordination role, direct exposure to workload transfers
NURSING ASSISTANTS
role only lightly covered by the protocol text, indirect effects
HIGH SENIORITY IN THE DEPARTMENT
memory of previous redesigns and what followed
NEWCOMERS
no prior protocol history, different relationship to standardization
DISTANT RELATIONSHIP TO HIERARCHY
the legitimacy of the messenger matters more than the content
INVOLVED IN LOCAL LABOR ACTION
the protocol is read through 24 months of conflict over working conditions
These configurations make part of the population’s heterogeneity visible. The simulation concerns synthetic individuals, not a few persona types : the population is not reduced to physicians versus nurses, but to distinct work positions and relationships to the protocol.
REACTIONS
RESISTANCE IS ABOUT THE PACE, NOT THE RULE
Our system identified that 68 % of healthcare professionals do not reject the new protocol as such: they recognize its technical relevance. What they reject is a rollout pace perceived as abrupt and incompatible with the existing workload. An 8-week rollout triggers blockages; a 6-month rollout with peer training achieves adoption without degrading interim quality.
THE LEGITIMACY OF THE MESSENGER DETERMINES RECEPTION
Top-down training delivered by management or managers from outside the department generates 42 % staff adoption. Peer training — healthcare professionals from the department trained first, then training their colleagues — generates 78 %. A protocol presented by a colleague who has tested it is accepted; the same protocol presented by the hierarchy is perceived as imposed.
ACKNOWLEDGING THE WORKLOAD IS A PREREQUISITE
Any announcement of a new protocol must be preceded by explicit acknowledgement of the existing workload by management. A rollout preceded by this acknowledgement achieves 68 % adoption. Without it, even with the best technical arrangements, adoption tops out at 34 %. This is not a symbolic gesture: it is a structural condition.
THE TIMING PARAMETER OUTWEIGHS THE TECHNICAL CONTENT
The six scenarios do not differ in the protocol deployed — it is identical in every case — but in the pace, who delivers the training and the prior framing. This difference in rollout conditions, not the text itself, produces the projected adoption gap at 18 months.
A team can recognize the relevance of a rule and reject the timetable carrying it. That rejection is not opposition to change : it is information about the existing workload.
THE FRICTION POINT
The operational pathway — arrival, triage, assessment, orientation, care, reassessment — is not affected uniformly. A rule does not create friction everywhere; it creates it at specific points, for specific roles.
The frictions described here are those identified by the simulation for this department and this synthetic population. They do not constitute a clinical evaluation of the protocol.
SAME PROTOCOL, DIFFERENT CONTEXTS
Conceptual diagram. The heights are illustrative : they represent neither time, nor measured workload, nor a hospital performance indicator.
The same text is experienced differently depending on context. The robustness of a rule is revealed in extreme situations, not in the average situation.
WORKLOAD TRANSFER
An improvement for one part of the system can transfer work to another. The benefit and the cost do not appear in the same place, or for the same professionals.
THE PRINCIPLE
Optimizing one stage does not always remove work: it can shift it to another stage or another profession.
WHAT THE PROTOCOL CHANGES HERE
Triage priorities, care timelines by condition, and coordination between emergency medicine, radiology and specialties.
WHY IT MATTERS
A coordination change cannot be read in the protocol text: it is visible in the workload of those who provide that coordination.
WHAT THIS REQUIRES
The rollout must be observed profession by profession, not only at department level.
ADOPTION IS COLLECTIVE
It works because several roles manage to coordinate around it. The simulation therefore focused on interactions between professional populations, not only on summed individual acceptance.
COMPARISON
Qualitative comparison derived from the simulated scenarios. The “ perceived workload ” column indicates the level of additional workload felt by teams : a low level is favorable. No scenario is cost-free : a uniform rollout meets the regulatory timetable and concentrates resistance ; a long progressive rollout reduces friction and extends the deadline ; a peer-based arrangement increases adoption and requires champions to be identified, trained and recognized. No comparison is made here regarding safety, clinical effectiveness or care outcomes.
THE MOST ROBUST
Protocol unchanged progressive rollout over 6 months peer training prior acknowledgement of workload individual support on request
THE MOST FRAGILE
Rapid, uniform switch neither acknowledgement of the existing workload nor internal educational legitimacy
DECISION
PROJECTION, THEN OBSERVATION
The university hospital selected the strategy combining a progressive rollout over 6 months, peer training with 12 peer champions identified and trained first, explicit acknowledgement of the existing workload through a joint statement by the chief executive and department head, and individual support available on request.
At 12 months, measured staff adoption is 78 %, above the 71 % projection. Time to stable care quality is 4 months, versus an 8-month projection under the abrupt-rollout scenario. The staff departure rate over the period is equivalent to the average for the previous 24 months. The protocol is cited as a methodological success by the regional health authority.
These values are those documented by the commissioning organization. They concern adoption and rollout, not clinical outcomes.
TAKEAWAY
The problem was not that teams rejected the rule. 68 % recognized its technical relevance. What they rejected was a timetable incompatible with a workload already in place for 24 months.
The rollout pace proved structurally more decisive than the protocol content. And educational legitimacy — a colleague from the department rather than the hierarchy — produced an adoption gap from 42 % to 78 %. These two parameters appear nowhere in the procedure text. Yet they determine its application.
POSSIBLE FUTURES
A
IMPOSE
Uniform, rapid rollout, same timetable for the whole department
B
SUPPORT THROUGH HIERARCHY
Staggered rollout, top-down training led by management
C
ROLL OUT THROUGH PEERS
Progressive over 6 months, 12 peer champions trained first, prior acknowledgement of workload, individual support on request
METHOD
640 synthetic healthcare professionals interviewed individually across 6 scenarios, 31 dynamic follow-ups on resistance points, and an 18-month projection incorporating within-team adoption-resistance dynamics, collective learning effects and departure risks.
This case adds a capability to the library : treating resistance as information. An organization may read it as a refusal to change. The simulation makes it possible to test not only “ will they accept it ? ” but “ where and why will the transformation meet real work ? ”
This case comes from a simulation conducted for a university hospital. The institution is not named, no personally identifiable data entered the system, and the detailed results remain the property of the commissioning organization. The comparisons between scenarios published here are qualitative ; the quantitative values cited are those documented by the commissioning organization.
The simulation focuses exclusively on teams’ organizational and behavioral reactions to different rollout approaches. It is neither a clinical validation, nor a medical protocol, nor a care-safety assessment, nor an individual care recommendation.
Your next decision
Describe your need. We can point you to the right level of support.
State your decision. See the future it produces.
