Showing posts with label Teaching Method. Show all posts
Showing posts with label Teaching Method. Show all posts

Sunday, February 8, 2009

“Tell me and I forget. Teach me and I remember. Involve me and I learn.” - Benjamin Franklin

The Darden learning experience is about learning real and relevant business cases through a class discussion, but it's also about taking the integrative business approach, constantly reminding one to look at the bigger picture.

And it really works.

I'm not sure if the professors have gotten better or if we did, but the discussions are just better.
Maybe it's the fact that people are now more concerned about finding a summer internship or perhaps people figured out that grades don't matter; at least not as much as they thought they did. There are almost no people, who are talking just for the sake of talking, thinking that it would increase their participation grade. And this makes for a focused, flowing class discussion.

I've had a few classes lately that had great discussions and the professor allowed the discussion to go in the wrong direction, but we've figured it out and corrected ourselves as happens a lot in the case method. Although it was an interesting discussion, we were seventy minutes into it and yet, no conclusion. I was starting to question what if at all have we learned during the class. We were summing up what information we've managed to discover using tools we've learned in this class and in the previous quarters and we've narrowed it all down to three courses of action the company can take. But which one will they take? 

In a real business situation you'll need to come up with a recommendation. And you'll need to present it in a manner your audience will understand, justify it and defend it just like we do in class every day.

In order to make this decision we had to tap in to material and experiences we've learned in a Strategy class. Then we knew what the company would have chosen to do. But we did not agree. Some people thought the company should take one direction and others thought it should take another. However all agreed about the company's goal. We combined what we've learned in parallel and previous courses without even noticing we did it, took a step back and fell into the CEO's seat (thank god he wasn't sitting there at the time) and then we understood. It all came together. In Hebrew we have a saying: "The token has dropped" - an expression from the 80's that refers to the public telephones we used to have that required special tokens to operate. When the call would go through, the token would drop.

In the end of the day, what matters is that when you come to a business situtation and when you'll have to make a decision, you'll have all the tools you've learned, you'll have all the different companies' experience from the different cases and you'll remember the discussions you've had, the wrong turns you took. 

Most importantly, you'll be able to take the CEO perspective and understand and integrate all the different divisions of the business and until you actually become a CEO, you'll be able to explain and defend your decision.

Friday, September 12, 2008

Gazogle

A game we played this week where we were divided into groups and asked to build Gazogles - Lego structures that look like the picture on the right.

The full game description can be found in an article writen by one of our operations professors. This would have probably helped my team not to do as bad as we did, but we cannot look these things up until we finish playing the game or discussing a case due to the honor code. Some more insights we've had in class discussin this is that we could actually talk to our customers and settle deals with them, perhaps sell them special product for premium price. We could also exchange some lego pieces for other pieces (bigger) to make the whole structure simpler to assemble.

I can say that being on the inside (I was assembler 1) you get to diagnose your own process as well as the one before or after you in the way they affect you. We have 15 minutes between rounds to perform process improvement (Kaizen events) but they went by so fast I could have sworn it was 3 minutes. During the events my group failed to consolidate the ideas so we ended up improving parts of the process while other parts (like supplies and procurement) remained inefficient rendering the whole process inefficient.

We failed collecting the input from all the different stations and looking at the whole process and improving it. I guess it may have been easier for an outsider to see things clearly.

This is probably what they hire consultants to do.
Anyway, I guess hindsight is 20/20.
Feedback Form