Dec 05 2008

Ramsay’s Kitchen Nightmares

Published by xiaoming at 3:44 am under Tech

Gordon Ramsay, a famous British food writer, business man and TV star. He stars in the Channel 4 series Ramsay’s Kitchen Nightmares which tells stories how he help some dreadful restaurants to come back to the business and win back customers. I watched the episode this Thursday, which was very impressive because I found that there were so much in common of what Gordon did in his show and what we did in our agile software development projects.

The show started, he walked into this rural Lancashire pub where he had found the landlord laying down the law in the kitchen and doing 120-hour weeks, despite undergoing a quadruple heart bypass, and had debts of £250,000.

It reminds me a failing project that was over spent and had people doing quite a lot over time but still did not seem to make the deadline.

Gordon identified some key problems and found out the root causes very quickly.

Problems Root causes
£250,000 debt Restaurant was running very inefficient, one person was the decision maker for everything.
No one could work in this restaurant more than 6 months Team was forced to taken order from the owner and no motivation and appreciation
There were many fancy plates, decorations that were not necessary and did not match Pub theme food Not customer centered and lack of communication with customer
People did not trust each other, there were huge boundaries between the manager and staffs. Lack of communication and integrity

Does it ring any bell to you? Yes, we had very similar problems in software development projects. Let’s look at a series of ways that Gordon tried to solve above problems.

  • Changed the menu that is simpler and customer centered
  • Kicked the boss out of kitchen and let other chiefs make decisions as a team
  • Got rid of those fancy plates which did not suit for the pub food theme and was not used that often
  • Strengthen what they were good at (Original puddings) as a brand and selling point
  • Encourage communication inside the team and with customers
  • Gathered the whole team to do stand up meeting and asked them to look back what they did right or wrong
  • Motivate the team, show praise and appreciation to the team, build good relationship between the boss and the team members

Gordon Ramsay played a very good project manager role in this game and he demonstrated many good software development practices by using agile and lean principles.

Problems Root causes Solutions and practices Principles/Methodologies
£250,000 debt Restaurant was running very inefficient, one person was the decision maker for everything. Change menu, make it simple and efficient, customer centered KISS, Lean(Eliminate waste), Value driven
No one could work in this restaurant more than 6 months Team was forced to taken order from the owner and no motivation and appreciation Kicked out the boss, team motivation and decision, self-organized team “Walk Out The Door”, People who do the work make decision, Lean (Empower the team), Lean (Build integrity in)
There were many fancy plates, decorations that were not necessary and did not match Pub theme food Not customer centered and lack of communication with customer Got rid off unnecessary stuffs, more communication with customers Lean (Eliminate the waste), User centered design
People did not trust each other, there were huge boundary between the manager and staffs. Lack of communication and integrity Stand up meeting, retrospective Agile, Lean (Eliminate waste), encourage communication

Running a business or managing a project might be very different between different industries and domains. However insight how to solve problems, there are methodologies and principles that could be used in common. Maybe it is because running a restaurant and developing a software are both professional service. I still remember that I benefited a lot from the experience of working in a restaurant when I started my IT career as a technical support engineer.

Bookmark on del.icio.us

2 responses so far

2 Responses to “Ramsay’s Kitchen Nightmares”

  1. Adrianon 09 Dec 2008 at 12:35 am

    I love analogies, love cooking, love anything on TV related to cooking (including the tyrant Ramsay). As software development professionals we have alot to learn from older professions … like cooking, and music.

    I consider Ramsay a counter-example to the self-directed team approach that we agile development professionals espouse. He’s a command and control poster-child.

    I did not see the episode to which you refer. I question some “leaps of faith” that you convey here though, like the fact that the high turnover was due to: “Team was forced to taken order from the owner and no motivation and appreciation”

    Perhaps some of them were not good cooks. Or good servers. Or perhaps the pay turned out to suck because the patrons were not good tippers.

    Still, I think it’s an analogy worth expanding. Thanks for posing it.

  2. xiaomingon 09 Dec 2008 at 3:16 am

    Thanks Adrian, you are absolutely right. I generally might not like that way Ramsay manage a business however, there were some shining points that I felt quite interesting :-) . There were some reasons behind the high turnover. One of them would be that the show want it to happen or the audience want to see it happening. According to the show, there were two chiefs who were very much qualified but they did not have chances to contribute their ideas and strength. When their boss (owner and head chief) was kicked off the kitchen. Ramsay let them grow, gave them chance to make decisions, to put their ideas on the menu which helped a lot to increase the efficiency and customer’s satisfaction.

    We used to have a project that about 20 people had to take order from one person who was responsible for customer facing, then this person became a big bottle neck of the project, things turned out to be really ugly. We realized that it must be changed, and got more people in the team as customer interfaces and worked as a team to make decisions. Also the person who used to be a bottle neck could focus more on account management and certainly contributed more value to the project. It finally turned into a double win.

Trackback URI | Comments RSS

Leave a Reply

Creative Commons License
This work is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 United States License.