Co-design

From OPEN! - Wiki
Jump to: navigation, search

Co-design (sometimes referred to as participatory design) describes a cooperative design process involving relevant stakeholders as a team of co-designers who jointly explore the problem and solution space. Multistakeholder participation may, however, be restricted to the involvement and concurrent work of diverse stakeholder in design sessions. Co-design can occur in a co-located situation or in remote places. It mainly implies a cognitive synchronisation among the participants, the creation of shared understanding of the problem and the creation of shared representations. This requires active participation of all stakeholders and a suitable co-design environment.

Camarinha-Matos et al.[1] distinguish between cooperation and collaboration. Cooperation between heterogeneous stakeholders serves the purpose of collective value creation. This includes the alignment of activities as well as resources towards compatible goals. Stakeholders may also engage in shared design activities towards a common goal. This can lead to collaboration, the joint engagement of participants to solve a particular problem by means of sharing risks, resources, responsibilities, losses and rewards. This in turn requires the building of mutual trust, effort, and long-term dedication.

On a technical level, collective design tasks in distributed environments need to be supported by suitable collaboration engineering processes[2] and groupware solutions [3].

Co-design also falls within the wider scope of co-creation. This concept is widely attributed to Prahalad & Ramaswamy [4] who describe the shifting role of customers in the new economy and how they can serve as a new source of firm-competence. They engage in so-called enhanced networks where they act as co-developers, co-creators of market value, as well as competitors. Thus, value is created by ongoing collaboration with active customers to access their competencies and shape customer experiences.

In open source systems a broad distinction can be made between core team and development team members. Distributed contributions are those which come from outside of the core team.

References

  1. Camarinha-Matos, L.M.; Afsarmanesh, H.; Galeano N.; Molina, A.. 2009. “Collaborative Networked Organizations – Concepts and Practice in Manufacturing Enterprises.” Computers & Industrial Engineering, Collaborative e-Work Networks in Industrial Engineering, 57 (1): 46–60. doi:10.1016/j.cie.2008.11.024.
  2. Kolfschoten, G., & De Vreede, G. J. (2007). The collaboration engineering approach for designing collaboration processes. Groupware: design, implementation, and use, 95-110.
  3. Ellis, C.A.; Gibbs, S.J.; Rein, G.. 1991. Groupware: some issues and experiences. Communications of the ACM 34, 1 (January 1991), 39-58. DOI=http://dx.doi.org/10.1145/99977.99987
  4. Prahalad, C. K. & Ramaswamy, V. (2000). Co-opting customer competence. Harvard business review, 78(1), 79-90.