Many organizations still treat workflow changes as a project milestone: design, build, train, launch. Then they’re surprised when the new process “goes live” but doesn’t ever take hold. Disruption is obvious, adoption is partial, and the gap continues to widen between the new, “official” workflow and the one people actually use. Recent thought on workflow interruptions, team communication, and technology acceptance gives us clearer picture of why this happens and what could be done differently. ¹³⁷
A good place to start this investigation is to look at the difference between formal workflow on paper and lived workflow in practice. When a new process arrives, it doesn’t instantly replace the old one. For a while, both coexist. People move between them, improvise shortcuts, and negotiate steps in the moment. Studies of multidisciplinary teams in clinical settings show that even brief workflow interruptions can shift communication patterns, increasing negative statements and repetitive clarification as people try to re-establish the next step in the flow. ¹² These interruptions don’t simply slow work; they consume attention and change how people interact.
That effect is even more apparent in environments in which work is already fragmented. Hybrid teams and knowledge workers often face continuous interruptions from messages, alerts, and system prompts. When a new workflow is presented in this context, it adds another layer of negotiation: which screen to use, which sequence to follow, who is responsible at each step. Research on workflow interruptions finds that teams spend meaningful time after each disruption re-explaining information and confirming basic details. ¹² In practice, every new process carries with it the burden of extra explanation, corrections, and rework.
Traditional rollout patterns often don’t account for this. A cutover date is set, training is delivered, and resistance is treated as something to be handled with messaging. The underlying assumption is that, “understanding leads to adoption.” But research into technology acceptance suggests something different. Perceived usefulness and perceived ease of use consistently emerge as strong predictors of whether people actually adopt a new system or process. ³⁶ When a new workflow clearly helps people do their work and feels manageable, adoption rises. When it adds effort without visible benefit, though, usage is shallow and even perfunctory.
Studies applying the Technology Acceptance Model to health information systems describe perceived usefulness as the belief that a system improves job performance, and perceived ease of use as the sense that using it does not feel overly demanding.³⁶ Both factors significantly influence willingness to adopt tools such as electronic records and decision support systems, as well as satisfaction and ongoing usage.³⁶ If a new workflow increases steps or risk for frontline staff, they’ll revert to older methods whenever they can, regardless of how clearly it has been explained.
And then we come to the way in which the change is actually introduced. Recent change management guidance emphasizes iterative or phased implementation, with continuous monitoring and adjustment, instead of large, single releases.⁷⁸ Organizations that use staged rollouts and then refine based on feedback report higher success rates and fewer delays than those relying on big-bang launches.⁷⁸ For workflow changes, this suggests that starting small, testing with real cases, and adjusting before broad rollout can reduce disruption and improve adoption all at the same time.
Suppose a company moves from email-based HR change approvals to an HRIS workflow. Formally, this looks to be straightforward. In practice, though, managers must learn a new sequence of steps, HR must monitor requests differently, and finance may depend on the timing of approvals for payroll and reporting. If the new workflow is introduced via a single cutover with minimal real-world testing, the first cycles are likely to produce delays, errors, and disaster. Those issues trigger extra emails, manual corrections, and last-minute reconciliations. The official workflow exists, but the lived workflow is a mixture of old habits and new steps stitched together under time pressure.
If handled differently–iteratively–the change can be more stable and manageable. A small group of managers and HR staff first run real scenarios in a safe environment. They identify points of confusion, missing information, and points of friction. Those become design targets: clearer labels, fewer required fields, better defaults. Early in the rollout, the organization treats the first runs as a learning period, with short, focused reviews on where requests stalled, where people reverted to email, and which steps generated questions. Disruption still occurs, but it is treated as useful input for refinement rather than an unexpected problem.
Importantly, research on team communication adds an additional layer. When workflows are disrupted, communication tends to become more negative and repetitive. ¹² That means early conversations about a new process will surely focus on what is broken or missing. If there is no structure around those conversations, they can easily harden into a narrative that the new workflow simply “doesn’t work.” Regular review sessions that log specific issues, prioritize them, and show visible progress can counter that tendency and keep attention on improvement rather than complaint.
There’s also a time dimension. Recent change management research suggests treating adoption as an extended period of observation and adjustment, not a just single checkpoint.⁷⁸ Some suggest using basic analytics to track real usage and identify groups that are struggling before frustration becomes entrenched.⁸ This reflects a shift from viewing workflow change as a slice in time to viewing it as a transition, during which old and new practices overlap and gradually stabilize into a new normal.
Taken together, the evidence suggests a different approach to workflow change. Instead of seeing disruption as an unavoidable side effect and adoption as a matter of persuasion, both can be treated as design goals. That involves three practical commitments: designing workflows around perceived usefulness and ease of use for the people doing the work, anticipating and observing disruption in the early phases rather than ignoring it, and using incremental rollout patterns that create room for learning and adjustment.
To best set them up for success, new workflows can be introduced with respect for how people actually work, with attention to what interruptions reveal, and with mechanisms to refine both the process and its support over time. The research on interruptions, acceptance, and change now provides a stronger foundation for that kind of practice, for organizations that are willing to treat workflow change as something to be managed thoughtfully rather than something simply to be delivered and then on to the next thing.¹³⁶⁷⁸
Notes
- Janssens, T., & Brüggen, E.
“The Impact of Workflow Interruptions on Team Communication.” Academy of Management Proceedings, 2024.
(Abstract and details on workflow interruptions and team communication in multidisciplinary settings.)
https://journals.sagepub.com/doi/10.1177/10596011241303982 - Tilburg University – Multidisciplinary Teams Study
“The impact of workflow interruptions on multidisciplinary team communication.” Tilburg University Research Portal, 2024.
(Empirical study of interruptions in hybrid multidisciplinary team meetings and their effect on interaction quality.)
https://research.tilburguniversity.edu/en/publications/the-impact-of-workflow-interruptions-on-multidisciplinary-team-co - Alsyouf, A. et al.
“Drivers of digital transformation adoption: A weight and meta-analysis.” Humanities and Social Sciences Communications (Springer Nature), 2022.
(Meta-analysis on digital transformation and technology adoption, emphasizing perceived usefulness and ease of use.)
https://pmc.ncbi.nlm.nih.gov/articles/PMC8841366/ - BMC Nursing – Longitudinal Study on Workflow Interruptions
“The Impact of Workflow Interruptions, Work Readiness, and Related Factors on Patient Safety Competency.” BMC Nursing, 2026.
(Three-wave longitudinal study on nurses, interruptions, and patient safety competency.)
https://pmc.ncbi.nlm.nih.gov/articles/PMC12894779/ - Springer – Technology Acceptance and Mediating Effects
“The mediating effects of perceived usefulness and perceived ease of use on technology acceptance.” BMC Health Services Research / Springer platform, 2025.
(Examines how perceived usefulness and ease of use mediate technology acceptance in healthcare contexts.)
https://www.springerpflege.de/the-mediating-effects-of-perceived-usefulness-and-perceived-ease/50632420 - Nature / Health Information Systems Adoption
“Role of perceived ease of use, usefulness, and financial strength in adoption of health information systems.” Humanities and Social Sciences Communications, 2024.
(Study on how perceived usefulness and ease of use influence adoption of health information systems.)
https://www.nature.com/articles/s41599-024-02976-9 - IT Toolkit – Change Management Best Practices
“Change Management Process: 7 Steps & Best Practices 2025.” IT Toolkit, 2025.
(Practical guidance on staged change management and process implementation.)
https://www.ittoolkit.com/change-management-process-7-steps-best-practices-2025/ - Spendesk – Change Management Plan
“6 steps to develop an effective change management plan for 2025.” Spendesk, 2026.
(Article on modern change management planning, including monitoring adoption and using metrics.)
https://www.spendesk.com/blog/change-management-plan/
