• Discoverability Visible
  • Join Policy Restricted
  • Created 07 Jul 2014

article:2307

Version 7
by (unknown)
Version 8
by (unknown)

Deletions or items before changed

Additions or items after changed

1 {{{
2 #!html
3
4
5

Using Reflection to Promote Teamwork Understanding in Engineering Design Education

6
7
8

“Using Reflection to Promote Teamwork Understanding in Engineering Design Education” Penny L. Hirsch and Ann F. McKenna

9 Purpose With teams almost ubiquitous in industry and increasingly the norm in engineering design classes, our study aimed at seeing whether reflective exercises can help students better understand the nature of high performing teams and how to leverage their own strengths—and manage conflicts--as members of an effective team.  In particular, we wanted to see how students’ understanding of successful teams evolves over time and whether their growing understanding can help us evaluate our instructional approach and learn how best to teach teamwork in relation to design.

10

Background The study context was a two-quarter, project-centered, team-based introduction to user-centered design—Engineering Design and Communication (EDC)--that is co-taught by faculty from engineering and communication and thus integrates communication and teamwork instruction into the design experience[1]. Teamwork instruction and coaching were part of the original course design, since faculty assumed that team experience alone is insufficient to help students acquire the teamwork competency needed to succeed in engineering. Following Schon’s and Kolb’s ideas about reflective practice and experiential learning [2, 3], students had several opportunities in the course to reflect on their team’s achievements and performance [4]. Thus their concrete design experiences were combined with reflection and abstraction so that their ideas could evolve as they underwent a holistic adaptive learning process.

11 Previous research [4] based on pre- and post-course memos about students’ team experiences suggested that students were indeed gaining awareness of the characteristics of effective teams that have been identified in the literature [5], such as dividing the work equally, benefiting from team members’ diverse strengths, and communicating regularly. However, findings also pointed to gaps that instructors considered important, such as failing to realize that “true teams” identify and work toward a shared, measurable performance goal. In addition, since the memos were very open-ended, they were difficult to code.

12

Method After taking steps to improve teamwork instruction in the following year, we planned a more structured assessment to explore student learning. Just before the course and at the end of their first quarter, students were given a reflective assessment to complete online: “Identify and discuss the factors that contribute to successful team performance.” In answering the question for the second time, students were able to see their original answer. Thus, they could see that the response was designed as an ungraded reflective answer, not a test. Approximately 96% of students completed the pre assignment and approximately 79% completed the post. For analysis, we randomly selected 75 paired responses (approximately 25% of the data). Two readers blind-coded the responses, looking for the same essential characteristics of successful teams that we used in the earlier study and that are widely identified in the literature.

13

Findings In the ten categories that were tracked, positive changes occurred in seven areas, where the post score was higher than the pre score. We used these scores not as a measure of “right” and “wrong” ideas about teamwork but rather as guides to analyze student responses in specific areas. From this examination, we concluded the following:

14
15
  • While students do not often refer specifically to a “true team,”—a term commonly found in the teamwork literature—many show an excellent understanding of a “true” or “high performing” team in language that demonstrates an understanding of the concept. Responses show an understanding of synergy—how a well functioning team of individuals working together can accomplish more than any one of them could accomplish alone—along with a focus on a shared goal or common purpose. This connection was lacking in the 2003 study.
  • 16
    17
  • Although the numbers in some categories do not change much, or may even decrease, the content indicates considerable growth in understanding teamwork and the nature of teams. This shows up in the greater specificity and elaboration of many post responses,
  • 18
    19
  • As students discuss key ideas about communication, open-mindedness, and respect, they connect them to essential design activities. Some students came into the course connecting high performing teams with creativity and innovation, but others gained this insight as the course proceeded.
  • 20
    21
  • Decreased scores related to some teamwork traits, like communication, may be a limitation of the study, since students tended to replace a broad term like communication with specific communication activities that they discussed in the post responses in terms of other skills such as project management. Ironically, despite the lower score, student responses suggest a more nuanced and sophisticated understanding of some of these concepts.
  • 22
    23

    Conclusion Opportunities for reflection on teamwork appear to have a useful place in design courses in the engineering curriculum. However, further work needs to be done to explore the relationship between this growth in teamwork and the students’ performance in design.

    24
    25

    References

    26 +
    <ol>
    27 +
    <li>P. Hirsch, B. Shwom, C. Yarnoff, J. Anderson, D. Kelso, G. Olson, and J. E. Colgate, “Engineering Design and Communication: the Case for Interdisciplinary Collaboration,” <I>International Journal of Engineering Education</I>, 17(4), 343-348 (2001).</li>
    28
    29 -
    <P class=MsoBodyText2>1.  P. Hirsch, B. Shwom, C. Yarnoff, J. Anderson, D. Kelso, G. Olson, and J. E. Colgate, “Engineering Design and Communication: the Case for Interdisciplinary Collaboration,” <I>International Journal of Engineering Education</I>, 17(4), 343-348 (2001).</P>
    +
    <li>D. A. Schon, <I>Educating the Reflective Practitioner</I>. San Francisco, CA: Jossey Bass Inc. (1987). </li>
    30
    31 -
    <P class=MsoBodyText2>2.  D. A. Schon, <I>Educating the Reflective Practitioner</I>. San Francisco, CA: Jossey Bass Inc. (1987). </P>
    +
    <li>D.A. Kolb, <I>Experiential learning: Experience as the Source of Learning and Development</I>, Englewood Cliffs, NJ: Prentice Hall (1984).</li>
    32
    33 -
    <P class=MsoBodyText2>3.  D.A. Kolb, <I>Experiential learning: Experience as the Source of Learning and Development</I>, Englewood Cliffs, NJ: Prentice Hall (1984).</P>
    +
    <li>J. Katzenbach and D. Smith, <I>The Wisdom of Teams: Creating the High-Performance Organization</I>, Boston: Harvard Business School Press (1993).</li>
    34
    35 -
    <P class=MsoBodyText2>4.  J. Katzenbach and D. Smith, <I>The Wisdom of Teams: Creating the High-Performance Organization</I>, Boston: Harvard Business School Press (1993).</P>
    +
    <li>P. Hirsch, A. F. McKenna, B. Shwom, “Teaching and Assessing Teamwork:  Implementing Continuous Quality Improvement,” <I>Proceedings</I> of the 2003 Association for Business Communication Annual Convention (2003).</li>
    36 -
    +
    </ol>
    37 -
    <P class=MsoBodyText2>5.  P. Hirsch, A. F. McKenna, B. Shwom, “Teaching and Assessing Teamwork:  Implementing Continuous Quality Improvement,” <I>Proceedings</I> of the 2003 Association for Business Communication Annual Convention (2003).</P>
    +
    38

    39 Author 1: Penny Hirsch; phirsch@northwestern.edu
    40 Author 2: Ann McKenna; mckenna@northwestern.edu
    41

    42
    43 Article Link: http://www.ijee.dit.ie/covers/covandabs24-2.pdf
    44
    45 }}}
    46
    47 [https://stemedhub.org/groups/cleerhub/wiki/issue:1326 : Back to 2009 Winter Issue, Vol. 4, No. 2]
    48
    49 [[Include(issues:footer)]]