Short answer
Prioritize thorough stakeholder analysis and clear communication channels to prevent the introduction of system use errors stemming from unaddressed conflicts.
- Field
- Commercial Production
- Source
- Work (2012)
- Method
- Qualitative analysis of system development and deployment processes.
- Evidence
- Strong effect
Failure to identify and reconcile conflicting stakeholder needs during the development and deployment of healthcare IT systems introduces system use errors, impacting quality and efficiency. This commercial production research insight is drawn from a 2012 study published in Work. Using Qualitative analysis of system development and deployment processes., researchers explored how this design variable affects real-world outcomes. The key design takeaway: Prioritize thorough stakeholder analysis and clear communication channels to prevent the introduction of system use errors stemming from unaddressed conflicts.
Stakeholder Dissonance Leads to System Use Errors in Healthcare IT Deployment
Failure to identify and reconcile conflicting stakeholder needs during the development and deployment of healthcare IT systems introduces system use errors, impacting quality and efficiency.
Work · 2012
Key Findings
- 01System use errors in HIT originate from both development and deployment phases.
- 02Failure to identify and address conflicting stakeholder needs (NWDs) results in stakeholder dissonance.
- 03Misinterpretations of stakeholder needs during requirement translation lead to latent errors.
- 04Errors in translating requirements into specifications cause drift errors.
- 05End-users often expend significant resources to avoid or mitigate system use errors.
Application
Design takeaway
Prioritize thorough stakeholder analysis and clear communication channels to prevent the introduction of system use errors stemming from unaddressed conflicts.
How to apply
Before initiating a new technology project, conduct a thorough stakeholder mapping exercise, identifying all potential users, administrators, and beneficiaries, and actively solicit their input on needs and expectations. Establish a clear process for documenting, prioritizing, and resolving conflicting requirements.
Project actions
- 01When defining your project, clearly list all potential users and stakeholders.
- 02Develop a plan for how you will gather and incorporate feedback from these different groups.
- 03Consider how different user groups might have conflicting needs and how you will address this.
Method & Evidence
Variables
Strengths & Limitations
Strengths
- +Highlights the systemic nature of errors in technology deployment.
- +Emphasizes the critical role of stakeholder management.
Limitations
It can be challenging to identify *all* stakeholders, and some may not be willing or able to articulate their needs clearly.
Reliability & validity
The findings are based on analysis of processes and may be subject to interpretation. Replicating the exact conditions of HIT development and deployment for controlled testing is challenging.
Think critically
How can a design team effectively prioritize conflicting stakeholder needs when resources are limited, and what are the ethical implications of prioritizing one group's needs over another's?
Design Principles
"System design and deployment must proactively identify, analyze, and reconcile the needs of all stakeholders to prevent latent and drift errors."
This research highlights a critical pitfall in the implementation of complex technological systems, particularly in high-stakes environments like healthcare. Understanding and mitigating stakeholder dissonance is essential for ensuring that technology adoption leads to intended improvements rather than unintended negative consequences.
What This Means for Your Design
When you build technology, especially for healthcare, you need to talk to *everyone* who will use it or be affected by it. If you don't listen to their different ideas and needs, you'll end up making mistakes in the technology that cause problems later on.
How to use in your project
- 1.Reference this research when discussing the importance of user research and stakeholder analysis in your design process.
- 2.Use it to justify the time spent on user interviews and feedback sessions.
Add to My Project
Quick Cite
Paragraph starter
The successful implementation of any complex system, particularly within the healthcare sector, hinges on a thorough understanding and reconciliation of diverse stakeholder needs. Research indicates that a failure to address stakeholder dissonance, where conflicting needs, wants, and desires are not identified or managed, directly contributes to system use errors. These errors, stemming from misinterpretations during the translation of stakeholder input into development requirements and specifications, can lead to significant inefficiencies and risks, underscoring the critical importance of comprehensive stakeholder engagement in the design and deployment phases of any project.
Source
Questions About This Research
- What does the research say about stakeholder dissonance leads to system use errors in healthcare it deployment?
- Prioritize thorough stakeholder analysis and clear communication channels to prevent the introduction of system use errors stemming from unaddressed conflicts. Evidence: Work (2012).
- Why does "Stakeholder Dissonance Leads to System Use Errors in Healthcare IT Deployment" matter for design?
- This research highlights a critical pitfall in the implementation of complex technological systems, particularly in high-stakes environments like healthcare. Understanding and mitigating stakeholder dissonance is essential for ensuring that technology adoption leads to intended improvements rather than unintended negative consequences.
- How can designers apply this research?
- Prioritize thorough stakeholder analysis and clear communication channels to prevent the introduction of system use errors stemming from unaddressed conflicts.
- What were the main findings?
- System use errors in HIT originate from both development and deployment phases.. Failure to identify and address conflicting stakeholder needs (NWDs) results in stakeholder dissonance.. Misinterpretations of stakeholder needs during requirement translation lead to latent errors.. Errors in translating requirements into specifications cause drift errors.
- What research method was used?
- Qualitative analysis of system development and deployment processes..
- How strong is the evidence?
- Evidence strength is rated Strong effect, based on a 2012 journal from Work.
- What should I do differently in my next project?
- Before initiating a new technology project, conduct a thorough stakeholder mapping exercise, identifying all potential users, administrators, and beneficiaries, and actively solicit their input on needs and expectations. Establish a clear process for documenting, prioritizing, and resolving conflicting requirements.
- What are the limitations?
- The study focuses on the origins of errors and may not quantify the exact impact of each type of error or provide specific solutions for all contexts.