Monday, April 20, 2009

The Universe at the End of the Restaurant

When we eat in restaurants, there is often a clear difference between the quality of the food and the quality of the service. The quality of the food may be dependent on the processes in the kitchen, as well as the quality and freshness of the raw materials, but our enjoyment of good food can be spoiled by poor service, which usually means a poorly designed process.


I found an Australian report about innovation in the restaurant industry (Submission to the Cutler Review by Restaurant & Catering Australia, pdf, April 2008), from which I picked out the following points.

  • The majority of the innovation is product innovation and therefore does not lead to significant productivity improvements.
  • The genesis of a new process should still be seen by a business as a competitive advantage. The development of these processes, however, requires a critical mass of thought that is often not evident in a small business.
  • The critical mass of funds required to change a process often means that innovation only occurs in small businesses when they change hands.


Obviously one form of innovation is to change the menu or introduce new items - in other words product innovation. For example, Nigel Green describes how his local pub was Thinking Adaptive and Adoptive over Fish & Chips - applying Cynefin to make sense of weak signals from regular customers.

A poorly designed process doesn't only reduce customer satisfaction. If it increases the length of time customers wait at tables for service, then it reduces the number of customers that can be accommodated in a session. Process innovation may therefore have a bigger impact on the business viability of a restaurant than product innovation.

Furthermore, the kind of bloggers I read generally have more to say about process management than cooking. So I have got a few contrasting examples here.

In my earlier post Agility and Variation, I described the frustration of David J Anderson's Sushi Lunch. Anderson was taken to a restaurant in Japan where the food was excellent but the process was broken. Anderson being a follower of Goldratt's Theory of Constraints, he diagnosed the problem in terms of a poor division of responsibility, although I took the opportunity to point out that the case also provided a counter-example to his usual line on eliminating variation.

Now for two more successful process examples. David Wertheimer describes Process innovation at Moe's (a Mexican restaurant) while in Process Improvement and the Chaat Cafe, Chris Bird talks about the stages of innovation in his favourite Indian restaurant, and throws in a brief mention of VPEC-T.


For those who like abstraction, all these restaurants have the same basic requirements. But what is interesting about these cases is that they are all different - a wide variety of problems and issues. I am also struck by the variety of problem-solving and other methods that are suggested - Cynefin, Theory of Constraints, VPEC-T.

Sunday, April 19, 2009

Open for Business Innovation?

My neighbour and good friend runs a successful bakery around the corner, and has opened a couple more bakeries a few miles away. I was trying to give him some ideas for business improvement.

My best idea was to install a BakerTweet system, which posts messages to Twitter whenever warm bread comes out of the oven. I think this is a brilliant idea, and I already wrote about it in my other blog (IT Innovation at Small Bakery).

But my friend is sceptical. How can I convince him to try?

Thursday, April 16, 2009

Getting Intelligence

Just reading a review of Richard Nisbett's book on "Intelligence and How to Get It", by Nicholas D Kristof, "How to raise our IQ", New York Times, 15th April 2009, via James Governor. Haven't got my hands on the book itself yet, but here's the quote James picked from the review that got my attention.

"Professor Nisbett provides suggestions for transforming your own urchins into geniuses — praise effort more than achievement, teach delayed gratification, limit reprimands and use praise to stimulate curiosity."

What if we ran companies on this basis? Perhaps this would be a better solution than recruiting people because they are "talented" and then rewarding them with large bonuses when they manage to game the system for short-term advantage.

Wednesday, April 1, 2009

Consultancy and Professionalism

A consultant advises a CEO to hide behind the scene and not face the people after a layoff. Catuslee asks: What kind of professionalism is this?

Whose professionalism - the CEO or the consultant?

If consultant says "why not hide" and CEO says "dammit I'm not hiding", then the consultant has achieved the right outcome. Sometimes big businessmen need to be treated like small children - you suggest the exact opposite of what you really want them to do. Is it more professional to trick or bully someone into doing what's right, or to permit someone to do what you know is wrong?

But if CEO says "please help me hide", what should the consultant say?


@catuslee The fact: CEO said "I don't know what to say to the people." and the consultant said "why not ask HR to face them."

@richardveryard If the HR director is the one with backbone, maybe it would be better all round if the HR director took over as CEO.

@richardveryard A good CEO would know exactly why not to delegate that to HR. Is it consultant's job to provide moral backbone to a weak CEO?

@catuslee I like this. And the new CEO should first fire the consultant. ha ha

@catuslee At time that the CEO need to show leadership, the consultant should do whatever to influence him to do so. (yeah, ur case 1)