Engineering stereotypes
by Mark on Jun.26, 2009, under general
One of the things I love about being a grad student at Northwestern McCormick’s MSIT program is that I receive a regular newsletter from the engineering school (although it is apparently available as an RSS feed). In the most recent newsletter was a an article titled Study: Engineering Stereotypes Drive Counterproductive Practices, by Emily Ayshford.
The study was done by Paul Leonardi, the Breed Junior Chair in Design at Northwestern University’s McCormick School of Engineering and Applied Science, and colleagues at the University of Colorado. What they found was that engineering students would fall into stereotypical behavior they have observed in media or in older students, such as procrastination, working individually on a group project, or bragging about having done a problem without following directions. These behaviors are what students feel they need to do to prove their engineering prowess, but hiring managers are finding that they are counterproductive for the real world workplace.
"There’s a stereotype that engineers do things by themselves," Leonardi says. "So when students are asked to work in teams, they think, am I going to be disadvantaged? When I go to the workplace am I not going to be as valuable?"
In other words, students believed that if they weren’t able to do a project alone, they couldn’t consider themselves an expert engineer. Leonardi and his colleagues often saw groups splitting up group work, even if they were specifically asked to work on it together at the same time.
These findings fascinate me. At least since high school, I have been guilty of such behavior. In grad school, however, I have taken a slightly different approach. I’m still a bit of a procrastinator, but that has little to do with bragging and more to do with some occasionally poor time management. I like to do some of the coursework alone, but the huge amount of group work has been extremely beneficial to me. The chance to interact with others about the topics we’re learning in class has been invaluable, both from a personal learning experience perspective and from a professional networking perspective.
I have definitely found it is important to learn how to work well on a team, and even better to learn how to work well on a team where everyone has different strengths, weaknesses, and personalities. The guy who prefers to work alone or do everything himself only serves to bring the entire team down.
Are there any other stereotypical behaviors you’ve seen in school or in the workplace? Were they in engineering or in another field?
Related posts:
1 Comment for this entry
Leave a Reply
Interesting items- Sheriff's police bust prostitution ring in northwest suburbs
- Xbox Live 12-Month Gold Subscription Card $30
- Run Your Own Free Proxy Through the Google App Engine [Proxy]
- Woman Crashes Car While Shaving Vag
- Crash closes major Schaumburg intersection
- A Bizarre Story: Newegg, Fake Core i7 Processors and a Cease & Desist Order [Intel]
- will the last one at SF Gate / San Francisco Chronicle please turn out the lights? | violet blue ® :: open source sex
June 28th, 2009 on 10:23 pm
In grad school, a lot of our coursework was analytical discussion based, and i found 100 percent of the time that the classes where we had one or more windbags in there (people who just spent the whole time using the biggest words possible and only attended to their own thoughts and not the opinions of others) really brought everyone’s learning potential down. Just like you say the group work has helped you and your course-mates learn more dynamically, I know we all learned a lot better when we had actual discussions with one another during seminars, not just “I’m going to prove to the professor I’m smart” sessions.
Collaborative learning rocks.