Short answer
When designing and implementing new digital platforms, anticipate that user roles will evolve and consider whether a structured or more adaptive implementation strategy best suits the organization.
- Field
- Innovation & Design
- Source
- Journal of the Association for Information Systems (2000)
- Method
- Comparative case study
- Evidence
- Moderate effect
Organizations can adopt either a structured, planned change approach or an improvisational, experimental approach when implementing intranets, with both leading to distinct yet potentially successful outcomes. This innovation & design research insight is drawn from a 2000 study published in Journal of the Association for Information Systems. Using Comparative case study, researchers explored how this design variable affects real-world outcomes. The key design takeaway: When designing and implementing new digital platforms, anticipate that user roles will evolve and consider whether a structured or more adaptive implementation strategy best suits the organization.
Improvisational vs. Planned Change: Two Paths to Intranet Success
Organizations can adopt either a structured, planned change approach or an improvisational, experimental approach when implementing intranets, with both leading to distinct yet potentially successful outcomes.
Journal of the Association for Information Systems · 2000
Key Findings
- 01Intranet technology blurs the lines between developers and users, necessitating new organizational roles and structures.
- 02Organizations can adopt either a 'planned change' approach (emphasizing control and planning) or an 'improvisational' approach (emphasizing experimentation and local initiative) for intranet implementation.
- 03No single ready-made organizational model exists for successful intranet implementation.
Application
Design takeaway
When designing and implementing new digital platforms, anticipate that user roles will evolve and consider whether a structured or more adaptive implementation strategy best suits the organization.
How to apply
When planning a new digital tool rollout, consider the trade-offs between a tightly controlled, phased implementation versus a more agile, iterative approach that allows for user-driven innovation.
Project actions
- 01When proposing a new system, consider how it might change existing job roles.
- 02Think about whether your design project would benefit more from a rigid plan or a flexible, adaptive approach.
- 03Document how users interact with the system and how their roles might evolve over time.
Method & Evidence
Variables
Strengths & Limitations
Strengths
- +Provides a comparative analysis of two distinct implementation strategies.
- +Highlights the human and organizational aspects of technology adoption.
Limitations
The specific context of intranet implementation might not directly translate to all design projects, especially those involving physical products.
Reliability & validity
The validity of the findings relies on the depth of the case studies and the accurate interpretation of organizational practices. Reliability might be limited due to the qualitative nature and small sample size.
Think critically
How might the 'improvisational' approach, while fostering innovation, lead to inconsistencies or a lack of overarching strategy in system development?
Design Principles
"Technology implementation strategies should be tailored to organizational context, acknowledging that both planned and improvisational approaches can yield effective results."
The implementation of new technologies like intranets challenges established work roles and organizational structures. Understanding these different strategic approaches can help design teams anticipate and manage the human and organizational factors involved in technology adoption.
What This Means for Your Design
When introducing new technology like an intranet, companies can either plan everything very carefully from the start or let people experiment and figure things out as they go. Both ways can work, but they change how people work and who does what.
How to use in your project
- 1.Use this research to justify your chosen development methodology, explaining why a planned or improvisational approach is suitable for your design project.
- 2.Discuss how your design anticipates or accommodates the blurring of roles between creators and users.
Add to My Project
Quick Cite
Paragraph starter
The implementation of new digital systems, such as intranets, often necessitates a re-evaluation of traditional IS development roles, blurring the distinction between developers and users and leading to emergent organizational structures. Research indicates that organizations can adopt either a 'planned change' approach, emphasizing management control, or an 'improvisational' approach, prioritizing experimentation and local initiative. This suggests that design projects should consider the organizational context and choose an implementation strategy that aligns with the potential for emergent roles and adaptive workflows.
Source
Journal of the Association for Information Systems
Corporate Intranet Implementation: Managing Emergent Technologies and Organizational Practices
journal · 2000
View sourceQuestions About This Research
- What does the research say about improvisational vs. planned change: two paths to intranet success?
- When designing and implementing new digital platforms, anticipate that user roles will evolve and consider whether a structured or more adaptive implementation strategy best suits the organization. Evidence: Journal of the Association for Information Systems (2000).
- Why does "Improvisational vs. Planned Change: Two Paths to Intranet Success" matter for design?
- The implementation of new technologies like intranets challenges established work roles and organizational structures. Understanding these different strategic approaches can help design teams anticipate and manage the human and organizational factors involved in technology adoption.
- How can designers apply this research?
- When designing and implementing new digital platforms, anticipate that user roles will evolve and consider whether a structured or more adaptive implementation strategy best suits the organization.
- What were the main findings?
- Intranet technology blurs the lines between developers and users, necessitating new organizational roles and structures.. Organizations can adopt either a 'planned change' approach (emphasizing control and planning) or an 'improvisational' approach (emphasizing experimentation and local initiative) for intranet implementation.. No single ready-made organizational model exists for successful intranet implementation.
- What research method was used?
- Comparative case study.
- How strong is the evidence?
- Evidence strength is rated Moderate effect, based on a 2000 journal from Journal of the Association for Information Systems.
- What should I do differently in my next project?
- When planning a new digital tool rollout, consider the trade-offs between a tightly controlled, phased implementation versus a more agile, iterative approach that allows for user-driven innovation.
- What are the limitations?
- The study is based on only two organizations, limiting the generalizability of findings.