Short answer
When designing for or implementing open source software in complex environments, proactively map and address the surrounding material dependencies and interconnections to manage adoption speed and visibility.
- Field
- Innovation & Design
- Source
- IFIP International Federation for Information Processing/IFIP (2012)
- Method
- Comparative case study
- Evidence
- Moderate effect
The physical and digital infrastructure surrounding open source software (OSS) significantly impacts the pace and nature of its adoption within public sector organizations. This innovation & design research insight is drawn from a 2012 study published in IFIP International Federation for Information Processing/IFIP. Using Comparative case study, researchers explored how this design variable affects real-world outcomes. The key design takeaway: When designing for or implementing open source software in complex environments, proactively map and address the surrounding material dependencies and interconnections to manage adoption speed and visibility.
Materiality of Open Source Software Adoption Influences Implementation Speed
The physical and digital infrastructure surrounding open source software (OSS) significantly impacts the pace and nature of its adoption within public sector organizations.
IFIP International Federation for Information Processing/IFIP · 2012
Key Findings
- 01Despite shared goodwill towards open source, implementation paths varied significantly between the two councils.
- 02The 'materiality' of the open source ecosystem, encompassing various components and interdependencies, can both constrain and accelerate adoption.
- 03The perceived transparency of open source can be obscured by the complex and layered nature of its implementation, making processes less visible.
Application
Design takeaway
When designing for or implementing open source software in complex environments, proactively map and address the surrounding material dependencies and interconnections to manage adoption speed and visibility.
How to apply
Before initiating an open source software project in a public sector setting, create a detailed map of all hardware, software, network infrastructure, and organizational policies that will interact with the new system. Identify potential bottlenecks and dependencies within this 'materiality'.
Project actions
- 01When researching a new technology, consider not just the technology itself but also the environment it will be placed in.
- 02Think about how existing systems and structures might help or hinder the adoption of your design.
Method & Evidence
Variables
Strengths & Limitations
Strengths
- +Provides a nuanced perspective on technology adoption by focusing on the often-overlooked 'materiality'.
- +Uses a comparative case study approach to highlight differences and similarities in implementation.
Limitations
The specific 'materiality' of each case study might be unique, making it difficult to generalize the findings to all public sector IT adoptions. The study's qualitative nature means that the 'speed' of adoption is interpreted rather than precisely quantified.
Reliability & validity
The reliability of findings might be limited by the qualitative nature of the case studies and the specific context of UK local councils. Validity could be enhanced by triangulating data from multiple sources within each council (e.g., interviews, IT logs, policy documents).
Think critically
To what extent does the 'transparency' of open source software become a disadvantage when its implementation is obscured by complex materiality?
Design Principles
"The 'materiality' of a system's environment significantly shapes its adoption trajectory."
Understanding the 'materiality' of OSS, including hardware, existing software ecosystems, and organizational structures, is crucial for predicting and managing adoption timelines. Designers and implementers must consider these tangible and intangible elements to facilitate smoother integration and achieve desired outcomes.
What This Means for Your Design
Even though open source software is meant to be open, the actual computers, other software, and company rules it has to work with can make adopting it faster or slower, and sometimes harder to understand what's happening.
How to use in your project
- 1.Use this research to justify the importance of analyzing the existing system and environment as part of your design process, especially when proposing new technologies or systems.
Add to My Project
Quick Cite
Paragraph starter
This research highlights that the successful adoption of new technologies, such as open source software in public sector settings, is significantly influenced by the 'materiality' of the surrounding ecosystem. Factors such as existing hardware, software infrastructure, and organizational policies can act as either facilitators or constraints, impacting the speed and visibility of the implementation process. Therefore, a thorough analysis of these contextual elements is essential for effective design and project management.
Source
IFIP International Federation for Information Processing/IFIP
Mutability and Becoming: Materializing of Public Sector Adoption of Open Source Software
journal · 2012
View sourceQuestions About This Research
- What does the research say about materiality of open source software adoption influences implementation speed?
- When designing for or implementing open source software in complex environments, proactively map and address the surrounding material dependencies and interconnections to manage adoption speed and visibility. Evidence: IFIP International Federation for Information Processing/IFIP (2012).
- Why does "Materiality of Open Source Software Adoption Influences Implementation Speed" matter for design?
- Understanding the 'materiality' of OSS, including hardware, existing software ecosystems, and organizational structures, is crucial for predicting and managing adoption timelines. Designers and implementers must consider these tangible and intangible elements to facilitate smoother integration and achieve desired outcomes.
- How can designers apply this research?
- When designing for or implementing open source software in complex environments, proactively map and address the surrounding material dependencies and interconnections to manage adoption speed and visibility.
- What were the main findings?
- Despite shared goodwill towards open source, implementation paths varied significantly between the two councils.. The 'materiality' of the open source ecosystem, encompassing various components and interdependencies, can both constrain and accelerate adoption.. The perceived transparency of open source can be obscured by the complex and layered nature of its implementation, making processes less visible.
- What research method was used?
- Comparative case study.
- How strong is the evidence?
- Evidence strength is rated Moderate effect, based on a 2012 journal from IFIP International Federation for Information Processing/IFIP.
- What should I do differently in my next project?
- Before initiating an open source software project in a public sector setting, create a detailed map of all hardware, software, network infrastructure, and organizational policies that will interact with the new system. Identify potential bottlenecks and dependencies within this 'materiality'.
- What are the limitations?
- The study focused on two specific UK local councils, limiting generalizability to other public sector contexts or different types of organizations. The analysis relies on qualitative narratives, which may be subject to interpretation.