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

Archive for the ‘Leadership’ Category

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!

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.

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?

Balancing Leadership

Tuesday, January 25th, 2011

The first set of technical memos have been turned in and graded, and the groups are on their way towards solutions. The first memo tasked groups with outlining their projects. One thing that became evident was that there was a disparity between the quality of the memos. This seemed directly correlated to the amount of interaction and feedback they had gotten from the A.L.’s during the writing of the memos. Groups that had been utilizing outside resources were much better prepared in writing their memos. However, this is likely a greater reflection on our (A.L.’s) leadership, than on the groups themselves.

One major challenge we have been facing is how to adequately interact with the groups, when there are 3 mentors to 2 groups. In the case of the Shriner’s groups, we have been having a divide where one leader has been shepherding the forearm rotation group and the other two have been effective paired to the wheelchair modification group. This divide led to a lot of really positive interaction in the forearm rotation group. However, it also meant that the wheelchair group was not getting as strong of a leadership role from us. We realized that our roles might not have been clearly communicated to the freshman. Therefore, we addressed the two groups as a whole in order to convey two major points.

  • We are all working with both groups
  • We are open and desiring feedback (via e-mail or in person)

We are still debating as to how best shift between groups. We don’t know if it is best to work with one group one day, and another group the next, or if we should be fluidly moving between both groups throughout the day. One major concern brought up was how to share what each group had been accomplishing with each other. For now, we are attempting a GoogleDoc that we jointly access and provide updates on what the groups were talking about and doing while we were with them. We will see if this is an affective solution. We are also trying to address the issue of having it appear that two A.L.’s are paired and the other is alone. We hope that by mixing up what two are together when talking to a group we can address this. For now, we are realizing that the three Shriner’s mentors each have different leaderships styles that are all pertinent for the groups to be exposed to. Thus, we need to work towards finding a balance in our interactions. Further, we hope to solicit feedback to help us become better leaders.

Where Did We Come From?

Monday, January 10th, 2011

RCEL AL Joey Spinella chats with John Doerr at the Nov 5 launch celebration.

The Rice Center for Engineering Leadership was launched on November 5, 2010 from a $15 million dollar grant from Rice engineering alumni Ann and John Doerr.  To prepare for the launch, a group of twenty students met weekly to discuss solutions to the world’s biggest engineering problems.  Students formed research teams and took turns leading the class in seminars, as topics ranged from global warming and green energy to cyber security and wikileaks.  Out of those twenty students and some recommended peers, applications were received and six RCEL Apprentice Leaders were chosen – Becca Jaffe, Leslie Miller, Camille Panaccione, Apoorv Bhargava, Andrew Owens, and Joey Spinella.

What are we doing?  Setting out to change the way engineering education is done at Rice.  Rice University offers excellent technical engineering degrees, filled with theory and mathematical proofs and analytical brute force.  But Rice could improve in allowing students more hands on experience before they are thrown into their mythical “senior design projects,” right before being expelled into the workforce or graduate school.

RCEL AL Becca Jaffe looks on as Ann Doerr shares in a launch breakout session

This thought process started in May of 2010, when Dr. Embree led a trip including two of the RCEL Apprentice Leaders to schools that excel in those “hands on” experiences for underclassmen.  On their sojourn across the United States, they learned about various engineering leadership programs and noticed how many of them included design opportunities for underclassmen students.  To implement what they learned, the course ENGI 120 was organized.  ENGI 120 seeks to distinguish itself from other Rice courses offered to freshmen by being the first ever complete, semester-long design course.  And this is not trivial, book-learning design, but design to contribute to the communities we live in and make an immediate difference.

Once we RCEL Apprentice Leaders were chosen, we set immediately to work, meeting with Mark Embree and Ann Saterbak to think of potential design problems to present to the freshmen students.  For a while, it seemed like we couldn’t think of enough legitimate ideas, but soon we had key connections with Shriner’s hospital and the Rice administration and some great opportunities emerged.  This whole process of setting up a course and choosing projects was not a neatly organized experience for us Apprentice Leaders.  Instead, every meeting we came to, we didn’t know quite what to expect.  From the beginning, Embree told us, “This course is not for complainers.  If you are looking for everything to be handed to you and to work out smoothly, this is not the opportunity for you.”  This very quickly proved to be true, as we realized in November that we would be lucky just to finish all preparation just in time for each class period.

To prepare, we met over lunch weekly starting in mid-November.  Finding mutually agreeable meeting times was a continual challenge near the end of the semester.  To select the six projects we would present to the freshmen students, we constructed a Pugh matrix and rated the projects in comparison to each other.  After they were chosen, we were given the task of each preparing a technical memo to describe one of the projects to the freshmen students.  Additionally, we were set in charge of running the team building portion of the second class period, for which we chose to do the “Marshmallow Challenge.”  By the time we had these assignments, we were already on Winter break.  And before we knew it, the semester had started.

Blog Kick off

Sunday, January 9th, 2011

ENGI 120 is a new engineering design class for freshmen students. They will solve problems from Shriner’s hospital and the Rice University campus with assistance from Dr. Saterbak, Dr. Embree, Dr. Griffin, and the Apprentice Leaders. The Apprentice Leaders are upperclassmen students who will act as mentors for the design projects. The campus projects include designing an automatic irrigation system for the OEDK green roof and modifying a surrey for FE&P to use as an alternative to golf carts. The Shriner’s projects include designing a forearm rotation measurement device and modifying a wheelchair so that a patient may use the wheelchair with his existing range of motion and strength. This blog will document the progress of the projects from the perspective of the Apprentice Leaders as well as the freshmen students. It will include written descriptions of classroom activities as well as pictures of the students throughout the design process. The Apprentice Leaders and the freshmen students will write about why they joined this class and what they hope to gain. They will also write about what excites them this semester as well as challenges that they face.