Knowledge Loss in Design Reviews

Huet, Greg; McMahon, Christopher; Sellini, Florence; Culley, S J; Fortin, Clément

doi:10.1007/978-1-4020-6761-7_19

Cited by 4 publications

(5 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The IMT was ultimately used to track them, while also providing means to qualitatively and quantitatively measure information loss between a meeting (based on its transcript) and its formal historical record (the minutes). Information loss has been shown to be very significant; up to 75% of content can be lost during minute taking (Huet et al, 2006). The implications of this study in terms of knowledge loss are further discussed in Section 5.…”

Section: The Imtmentioning

confidence: 89%

“…Finally, four comparative criteria to evaluate knowledge loss, outlined in Huet et al (2006), can be further illustrated using the examples provided in Figure 12. † Volume and length: These two criteria help to express the importance of a topic, knowledge concept, or thread relative to the rest of the document.…”

Section: Detailed Knowledge Loss Study For Two Critical Meeting Topicsmentioning

confidence: 99%

“…Overall, the primary activities in which the respondents are involved can be clustered as follows: 46% have a management role, 40% a design role, and 14% a manufacturing role. It is not the intent of the authors to detail the results of the survey; these are available in Huet et al (2006). However, the results are very relevant to the thrust of this paper and unequivocal; namely, engineers learn to take minutes by experience and only truly value the actions list, the practical side of minute taking.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Making sense of engineering design review activities

Huet

Culley

McMahon

et al. 2007

AIEDAM

Self Cite

View full text Add to dashboard Cite

Engineering design reviews, which take place at predetermined phases of the product development process, are fundamental elements for the evaluation and control of engineering activities. These meetings are also acknowledged as unique opportunities for all the parties involved to share information about the product and related engineering processes. For product development teams, the knowledge generated during a design review is not as secondary as it may seem; key design decisions, design experiences, and associated rationale are frequently made explicit. Useful work has been carried out on the design review process itself, but little work has been undertaken about the detailed content of the meeting activity; it is argued that understanding the transactions that take place during a meeting is critical to building an effective knowledgeoriented recording strategy. To this effect, an extensive research program based on case studies in the aerospace engineering domain has been carried out. The work reported in this paper focuses on a set of tools and methods developed to characterize and analyze in depth the transactions observed during a number of case studies. The first methodology developed, the transcript coding scheme, uses an intelligent segmentation of meeting discourse transcriptions. The second approach, which bypasses the time consuming transcribing operation, is based on a meeting capture template developed to enable a meeting observer to record the transactions as the meeting takes place. A third method, the information mapping technique, has also been developed to interpret the case study data in terms of decisions, actions, rationale, and lessons learned, effectively generating qualitative measures of the information lost in the formal records of design reviews. Overall, the results generated by the set of tools presented in this paper have fostered a practical strategy for the knowledge intensive capture of the contents of design reviews. The concluding remarks also discuss possible enhancements to the meeting analysis tools presented in this paper and future work aimed at the development of a computer supported capture software for design reviews.

show abstract

Section: The Imtmentioning

confidence: 89%

Section: Detailed Knowledge Loss Study For Two Critical Meeting Topicsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Making sense of engineering design review activities

Huet

Culley

McMahon

et al. 2007

AIEDAM

Self Cite

View full text Add to dashboard Cite

show abstract

“…A widely-used method of capturing activities within industry is meeting minutes, which follows the second approach. The observation from a study conducted by Huet (2006) within the context of engineering design in the aerospace industry, suggests that actions and decisions in meetings are usually well recorded but rationale and experience leading to these are not generally captured well in the minutes (Huet et al, 2007). Meeting minutes, when used to formally document the record of meetings are often limited in the extent to which they capture the information exchange that took place.…”

Section: Literature Reviewmentioning

confidence: 99%

Capturing Synchronous Collaborative Design Activities: A State-of-the-Art Technology Review

Hall¹,

McMahon²,

Bermell-García³

et al. 2018

Proceedings of the DESIGN 2018 15th International Design Conference

View full text Add to dashboard Cite

show abstract

“…As shown in Figure 2, design reports mix the process, rationale, decisions and the information resources. Furthermore, the rationale behind the design is often poorly recorded in these traditional design records -meeting minutes, for example, often say little about the rationale behind decisions [53]. The records are thus very difficult to reuse or retrieve for future product upgrade or new design projects.…”

Section: Framework Of Component-based Process Modelmentioning

confidence: 99%