Rice University logo
 
Top blue bar image Engineering 120: Freshmen Design Projects Blog
Rice Center for Engineering Leadership
 

Archive for February, 2011

ENGI 120 Student Presentations

Thursday, February 24th, 2011

After the apprentice leaders met with Dr. Volz to learn how to coach presentations, we were prepared to watch the ENGI 120 students with a keen eye for common presentation faux paus. These included everything from “ums,” tense body language, a “question” or “?” slide, and how the students fielded questions.

I was pretty confident after watching the student’s practice presentations that these ENGI 120 students would do far better than we had previously imagined freshman students would do. And I have to say, I was still impressed with the presentations the day of. The students were eloquent, clearly enthusiastic, and yet professional. I was impressed with their designs and coolness on the spot when it came to technical questions. The surrey group had even constructed a little model to better explain the different design options.

However as newly trained coaches, we were noticing and writing down comments on possible areas of improvement for the students including talking speed and pauses.

Overall, we were impressed with the extraordinary group of freshman engineering students in ENGI 120. We were especially impressed with how engaged the presenter’s peers were during the different student presentations. Many of the students asked their peers great specific, technical questions at the end. I guess our skit on good and bad questions paid off!

Oral Report Coaching

Tuesday, February 22nd, 2011

One of my favorite aspects of this course is not only getting to learn about how to do things, but also getting to learn how to teach things.  This is definitely the case with coaching the freshmen on their oral reports.  As a junior mechanical engineer, my experience in giving oral reports is still quite limited.  Naturally, before this course, I never had an opportunity to practice coaching others on their oral report skills.  But this is exactly the situation we were in for class on Tuesday.

Dr. Tracy Volz helped us to develop these skills.  We watched some example senior design presentations to practice watching for different aspects and writing careful notes of what was important.  We also role played giving feedback on writing samples to make sure we had a good balance of encouragement and constructive criticism.  One thing I discovered was that I tend to be a little too up-front with my observations, often leading to discouragement on the part of the recipient.  This was something I was careful to avoid in giving feedback to the Forearm Group on Tuesday.

Listening to the Forearm Group present, I was very impressed by how well prepared they were.  But no matter how good their presentation was, I still was able to think of many things to comment on.  It was a challenge to be methodical in sharing what I thought was important while also being careful to present only as much as would be beneficial for their team to improve their presentation.  Over all, I felt good about the encouragement I was able to give the team, and was thrilled by how receptive the team was.  It is empowering to step into such a leadership role in this class and see the students listen so carefully to the things I say!

Oral Presentations and AL Skit

Thursday, February 17th, 2011

One of the final lectures the students of ENGI 120 received before their mid-semester presentations were due was one on how to prepare and give oral presentations and how to ask constructive questions after a presentation. This entire lecture was a tag team effort between Dr. Saterbak, Dr. Volz and all the Apprentice Leaders.

The first portion of the lecture was handled by Dr. Saterbak who explained the CATME evaluation system to the students. This technique has been used by the teams to evaluate each of the members and will contribute to their overall grade.

The next part of the lecture consisted of Dr. Saterbak presenting to the class about how to design a good presentation for a design proposal. This included the strategies required to make an effective presentation and also how to conduct oneself during a presentation.

The final part of the presentation was an interesting Skit on how to ask good questions, done by the ALs. We gave a very short presentation on a sandal that detected metal and provided product descriptions. This was followed by the remainder of the ALs asking a variety of questions, both good and bad, and the presenting ALs showing the students how to answer questions politely and effectively.

How to be an Affective Leader

Thursday, February 10th, 2011

I think if I knew how to be an affective leader, I could likely sell a lot of books, and make a lot of money as a speaker. However, that is one of the greatest parts of the ENGI 316 course, that we are not only teaching but also learning leadership. We all came into the course with the preconceived notion that we were selected for our leadership capabilities, and thus set out to lead the freshman into greatness on their projects. This is a great set up for a lesson in humility. It’s easy to say that my shortcomings as a leader have been because the group isn’t responding to my style of leadership. However, learning to be a capable of multiple styles of leadership will make me a better leader in the future. Therefore, I am finding myself stretched to explore other styles, a position fitting for the mission of RCEL.

Learning how to be an affective leader has come largely from the Shriner’s AL’s interaction with the freshman teams. I can mainly attest to my own interaction; but, I have found that I approach leadership in a lead from behind method. I try to direct the team, through veiled comments such that at the end they feel they have arrived all on their own, when in reality I was guiding all along. However, with one of our groups, it has become evident that this is not affective. For example, the groups were encouraged to designate a facilitator for the day. However, the facilitator for this one group did not adequately insure that everyone’s voice was being heard. So, I stepped in and asked for the opinions of different group members throughout the course of the meeting. The result was that I modeled what a facilitator should do, but the group (and especially the acting facilitator of the group) learned nothing. In discussing the situation with our faculty mentors, I learned that in that situation I needed to explicitly say that I was modeling the position of facilitator. It is difficult for me to approach leadership so explicitly. However, it is also important that we all learn how to lead in different ways and different situations.

Methods to Evaluate Solutions 1

Tuesday, February 8th, 2011

It can be really fun and easy to throw out many ideas during the brainstorming process regardless of how practical they are. The topic of this class was the hard part: evaluating these ideas to determine the best design choice. Dr. Saterbak described two different design evaluation tools. She also stressed that the brainstorming and evaluation process is an iterative process. When evaluating solutions, new and potentially better ideas often come to mind.

The first evaluation tool is a morph chart. This chart organizes the brainstorming ideas into solutions for specific functions and attributes. The best combination of design solutions can be chosen from the possibilities. The second is a priority checkmark matrix that evaluates the solutions based on their ability to meet the design criteria and satisfy the constraints. The design criteria are rated based on a checkmark system; therefore, the solutions that meet highly rated design criteria receive the highest scores. Dr. Saterbak ended the lecture by stressing that these evaluation tools are only valuable and useful if supporting data dictates the evaluation numbers.

Apoorv and I worked with the OEDK roof after the lecture. We discussed the brainstorming memo and talked in more detail about how the sensors would connect to the control system. Some of this may require some programming skills, or the system can potentially be designed with on/off switches. More evaluation tools will be discussed on Thursday, and then the groups will turn in a memo using these evaluation matrices.

Brainstorming Class

Thursday, February 3rd, 2011

Ideas from the OEDK group's brainstorm session

True to the subject matter of the class, Dr. Saterbak challenged everyone to come up with a list of things you could do with a phonebook in two minutes. The ENGI 120 students, other apprentice leaders, and I were all furiously thinking and writing down EVERY idea that popped into our head.

We then formed groups to discuss our impressively long lists of possible activities involving phonebooks. Everyone came up with some pretty unique and creative ideas. However, none of the ideas that we formed by ourselves were nearly as impressive as the ideas that resulted from the group brainstorming session.

After this exercise the freshman and the apprentice leaders were clearly ready to apply the same creativity from our brainstorming challenge to the design projects. As Dr. Saterbak had stressed with person anecdotes, no idea is a bad idea during brainstorming. I believe that everyone truly took this to heart in the groups. In the early stages there were some comical ideas like creating a “squirrel power plant” to power the moisture control box for the OEDK green roof. Although that was a more farfetched idea, the brainstorming session resulted in a wealth of great ideas that could solve these design problems.

It was inspiring to see all the creativity flow in a organized and logical way. From the picture you can see that each group was able to come up w a plethora of ideas.

Search Tools and Written Reports

Wednesday, February 2nd, 2011

A critical part of any project revolves around research and in depth study of the problem, current and potential solutions, etc. At the same time, it is also very important to be able to document technical details and support arguments in a proper manner. While the teams had already been making use of technical memos at each stage of the design process, to document their findings, this lecture was meant to provide them with a clear purpose for their efforts, and ways that they could improve their presentation.

A great deal of emphasis was laid on how to structure the technical memos, especially using the idea that the most important information needs to be put first, and then must follow a sequential order of significance. Another very important point made was that as engineers, we must be able to quantify our objectives and arguments as much as possible and use graphs and tables to illustrate our point better rather than being vague and qualitative. A set of activities were carried out to encourage the students to be able to critically analyse technical memos and writing styles in engineering.

The next part of the lecture and the area that the ALs were most involved in was around the subject of research and search tools. The students were told to not only to try to use the right tools, but also to make sure that they were asking the right question. Given the information overload that occurs today with the Internet especially, it is crucial that students starting their research careers are able to sift through all the information and sort out the good from the bad. The concept of peer reviewed papers and primary literature was also introduced and, examples of places where these could be found and referenced were mentioned, such as Google Scholar, etc. Following the lecture, the apprentice leaders spent some time with the teams discussing the tools at hand and showing them how to use them to find specific data relevant to their projects. Some time was also spent starting some of the preliminary research for each of the teams, in order to get them started on the information accumulation.

Teamwork

Tuesday, February 1st, 2011

The Wheelchair Team, "AGP - Arthrogryposis Going Places" at a social activity

Teamwork is hard work.  On the teams I’ve experienced, some teams seem to instantly connect, ready to work together effectively and efficiently.  Other teams take a while to warm up to each other.  And other teams just don’t seem to work at all.  Sometimes, the best solution I’ve had for a dysfunctional team is to try to do parts myself, and then push the rest onto other people in the group.  But for design projects, teamwork is absolutely essential.  Not only does having people to work with allow greater productivity, it also allows better ideas, wider outlooks, and a variety of skill sets.

So how do we cultivate good teams?  It’s so easy just to think about the challenging team situations we’ve been on.  How could any of us Apprentice Leaders know how to work perfectly with a team?  How could we even claim to have figured it out?  For the most part, teamwork is just something that happens.  In my experience on teams, I mostly just think about myself and the idea we are all working towards.  Other people come into play when they can help make my life better or bring us closer to the goal.  So to sit with these teams of students, and not think about ourselves, or even necessarily about the projects, but just about shear teamwork and what healthy teamwork looks like, it can be enlightening.  Suddenly all my tendencies to dominate groups I’m in become obviously inappropriate.  Suddenly my greatest desire is to see each member contribute in some way and feel “enfranchised.”  If I see one student taking complete control, I see that student as an enemy to the good of the team.

Not only is this kind of meta-analysis challenging, it’s also hard to know how fruitful it is.  Once I’ve arrived at some level of understanding, how can I actually do something to push a team in the right direction to grow as a team?  Or how do I know when a team has “arrived?”

One thing we AL’s did to try and build team connectedness was throw a social for one of the teams.  We set a rule: no talking about the project for the duration of the social event.  Instead, we hung out, played pool, drew pictures, and learned some about each other.  I thought everything was perfect, until I realized that the same dynamics that bothered me in the classroom were also present in this social interaction.  Once having put on these group-interaction analytical goggles, could I never take them off?

And even though I don’t know what I’m doing, it is encouraging to see all the teams moving closer together.  Maybe the point of this isn’t to “arrive” anywhere, but to leave where we used to be?