Short answer

When designing collaborative information systems, plan for their entire lifecycle, not just the initial development phase, by integrating a long-term 'infrastructure time' perspective.

Field: Innovation & Design
Source: Computer Supported Cooperative Work (CSCW) (2010)
Method: Case Study Analysis
Evidence: Moderate effect

Successful collaborative development of information infrastructure hinges on recognizing and integrating 'infrastructure time,' a long-term perspective, alongside short-term 'project time.' This innovation & design research insight is drawn from a 2010 study published in Computer Supported Cooperative Work (CSCW). Using Case study analysis, researchers explored how this design variable affects real-world outcomes. The key design takeaway: When designing collaborative information systems, plan for their entire lifecycle, not just the initial development phase, by integrating a long-term 'infrastructure time' perspective.

Study

Innovation & DesignHigh ImpactModerate effect

Long-term 'Infrastructure Time' is Crucial for Sustainable Collaborative Development

Successful collaborative development of information infrastructure hinges on recognizing and integrating 'infrastructure time,' a long-term perspective, alongside short-term 'project time.'

Computer Supported Cooperative Work (CSCW) · 2010

Key Findings

01Information infrastructure development requires consideration of both short-term 'project time' and long-term 'infrastructure time'.
02A 'continuing design' orientation, which embraces 'infrastructure time,' is vital for the sustained success of collaborative information infrastructures.
03Existing approaches to collaborative work often prioritize short-term project cycles, potentially hindering the long-term viability of shared infrastructures.

Application

Design takeaway

When designing collaborative information systems, plan for their entire lifecycle, not just the initial development phase, by integrating a long-term 'infrastructure time' perspective.

How to apply

When initiating a design project for a shared digital platform or standard, map out not only the immediate deliverables but also the anticipated evolution, maintenance, and long-term user support required.

Project actions

01When defining the scope of your design project, consider how the product will be used and maintained beyond its initial creation.
02Think about how users will adapt and evolve the product over time, and design for that flexibility.

Method & Evidence

AimHow can the temporal dimension, specifically the distinction between 'project time' and 'infrastructure time,' inform the collaborative development of information infrastructure?

MethodCase Study Analysis

ProcedureThe researchers analyzed the collaborative development of a metadata standard for ecological research, focusing on the practices and perspectives of stakeholders across different temporal orientations ('project time' vs. 'infrastructure time').

ContextCollaborative development of information infrastructure for data-rich scientific collaboration.

Variables

IVTemporal orientation (project time vs. infrastructure time)

DVSuccess/sustainability of collaborative information infrastructure development

CVType of infrastructure being developed, stakeholder involvement, domain of application

Strengths & Limitations

Strengths

+Provides a novel conceptualization of temporality in collaborative development.
+Offers practical insights into the challenges of long-term infrastructure maintenance.

Limitations

This research is based on a specific type of collaborative development (metadata standards). Applying its findings to other domains might require adaptation.

Reliability & validity

The validity of the findings relies on the in-depth analysis of a specific case. Reliability might be improved by replicating the study across diverse infrastructure development contexts.

Think critically

How might the conflict between short-term project deadlines and long-term infrastructure needs be managed in practice?

Design Principles

"Design for enduring utility by integrating long-term temporal considerations into collaborative infrastructure development."

Designers and engineers often focus on immediate project goals, but for complex systems like data infrastructure, a sustained, long-term view is essential for their eventual utility and evolution. Neglecting 'infrastructure time' can lead to solutions that become obsolete or unmanageable quickly.

What This Means for Your Design

When you build something for a group to use over a long time, like a shared tool or a set of rules, you can't just think about finishing it quickly. You also need to think about how it will be updated, maintained, and used years from now. This long-term thinking is called 'infrastructure time'.

How to use in your project

1.Reference this study when discussing the long-term implications of your design choices, particularly for collaborative tools or systems.
2.Use the concepts of 'project time' and 'infrastructure time' to analyze the temporal challenges and opportunities in your design process.

Add to My Project

Quick Cite

Paragraph starter

The development of collaborative information infrastructure necessitates a temporal perspective that extends beyond immediate project completion. As highlighted by Karasti, Baker, and Millerand (2010), distinguishing between short-term 'project time' and long-term 'infrastructure time' is crucial. A 'continuing design' approach, which embraces 'infrastructure time,' ensures the sustained utility and adaptability of shared resources, a critical consideration for any design project aiming for lasting impact.

Source

Computer Supported Cooperative Work (CSCW)

Infrastructure Time: Long-term Matters in Collaborative Development

journal · 2010

View source

Questions About This Research

What does the research say about long-term 'infrastructure time' is crucial for sustainable collaborative development?: When designing collaborative information systems, plan for their entire lifecycle, not just the initial development phase, by integrating a long-term 'infrastructure time' perspective. Evidence: Computer Supported Cooperative Work (CSCW) (2010).
Why does "Long-term 'Infrastructure Time' is Crucial for Sustainable Collaborative Development" matter for design?: Designers and engineers often focus on immediate project goals, but for complex systems like data infrastructure, a sustained, long-term view is essential for their eventual utility and evolution. Neglecting 'infrastructure time' can lead to solutions that become obsolete or unmanageable quickly.
How can designers apply this research?: When designing collaborative information systems, plan for their entire lifecycle, not just the initial development phase, by integrating a long-term 'infrastructure time' perspective.
What were the main findings?: Information infrastructure development requires consideration of both short-term 'project time' and long-term 'infrastructure time'.. A 'continuing design' orientation, which embraces 'infrastructure time,' is vital for the sustained success of collaborative information infrastructures.. Existing approaches to collaborative work often prioritize short-term project cycles, potentially hindering the long-term viability of shared infrastructures.
What research method was used?: Case Study Analysis.
How strong is the evidence?: Evidence strength is rated Moderate effect, based on a 2010 journal from Computer Supported Cooperative Work (CSCW).
What should I do differently in my next project?: When initiating a design project for a shared digital platform or standard, map out not only the immediate deliverables but also the anticipated evolution, maintenance, and long-term user support required.
What are the limitations?: The study is a single case study, and the findings may not be universally generalizable to all types of collaborative infrastructure development.