A framework for understanding the workspace activity of design teams
CSCW '88 Proceedings of the 1988 ACM conference on Computer-supported cooperative work
A use of drawing surfaces in different collaborative settings
CSCW '88 Proceedings of the 1988 ACM conference on Computer-supported cooperative work
Distributed Artificial Intelligence (Vol. 2)
Findings from observational studies of collaborative work
International Journal of Man-Machine Studies - Computer-supported cooperative work and groupware. Part 1
More or less following a plan during design: opportunistic deviations in specification
International Journal of Man-Machine Studies - What programmers know
Designing engineers
Engineering design: a synthesis of views
Engineering design: a synthesis of views
Issues of expert flexibility in contexts characterized by complexity and change
Expertise in context
On Line and on Paper: Visual Representations, Visual Culture, and Computer Graphics in Design Engineering
IDEFO - SADT Business Process and Enterprise Modelling
IDEFO - SADT Business Process and Enterprise Modelling
Computer Supported Cooperative Work
Two sides of the story: Visualising Products and Processes in Engineering Design
IV '06 Proceedings of the conference on Information Visualization
Project Management: A Systems Approach to Planning, Scheduling, and Controlling
Project Management: A Systems Approach to Planning, Scheduling, and Controlling
Hi-index | 0.00 |
Successful realization of large-scale product development programs is challenging because of complex product and process dependencies and complicated team interactions. Proficient teamwork is underpinned by knowledge of the manner in which tasks performed by different design participants fit together to create an effective whole. Based on an extensive industrial case study with a diesel engine company, this paper first argues that the overview and experience of senior designers play an important part in supporting teamwork by coordinating activities and facilitating proactive communication across large project teams. As experts move on and novices or contractors are hired, problems are likely to occur as tacit overview knowledge is lost. If informal, overview-driven processes break down, the risk of costly oversights will increase, and greater management overhead will be required to realize successful product designs. Existing process models provide a means to express the connectivity between tasks and components thus to compensate partially for the loss of tacit overview. This paper proposes the use of design confidence, a metric that reflects the designer's belief in the maturity of a particular design parameter at a given point in the process, to address the limitations of existing models. The applicability of confidence-based design models in providing overview, as well as their shortcomings, will be demonstrated through the example of a diesel engine design process. Confidence can be used to make overview knowledge explicit and convey additional information about the design artifact, thereby informing communication and negotiation between teams.