The 6C Model

From apppm
Revision as of 14:37, 12 February 2023 by ChristinaKjaer (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

During a design process, knowledge is produced in many ways. In multidisciplinary teams several approaches are implemented in the traditional design process, resulting in a continuously expanding field. To drive innovation, sustainability, economy and functionality, knowledge from non-design fields are influencing the traditional deign approaches in amongst other sketching, prototyping, planning and development. [1]

A designer needs to understand the ways in which knowledge is produced during a deign process to combine/include different fields and manage a holistic team with common understanding. To help expand the designer's understanding a model has been developed - namely the 6C Model. The goal with the model is to help members in a design team actively observe and become aware of different approaches when designing to enable acting with consciousness. It describes six types of knowledge production in a design process and, together with a collection of co-creation cards, helps translating knowledge into practical approaches.

   [\url{file:///C:/Users/Pc/OneDrive%20-%20Danmarks%20Tekniske%20Universitet/DTU/Master/4.%20semester/42433%20-%20APPPM/Wiki%20article%20material/Friis_The-6C-Model_20016.pdf} 
   ][2]
   

It takes a design process through fours stages: Collect, Comprehend, Conceptualize and Create, not necessarily in that order. This is held together by tools for collaborating and with continuous communication.

The term knowledge production is referring to everything that is shared, used or implemented in a design process, that may contribute to a project. The method combines theory of cross-functional teamwork and understanding of design process, similar to the framework from the 3 Cs [3] and the Double Diamond [4], respectively.

This article will explain the model and how it works together with a comparison to similar models. Finally, benefits and limitations using this model will be discussed.

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox