Wednesday, July 29, 2009

Kaizen

Till date most of my blogs talked about corrective measures to be taken AFTER mistakes were committed. Now as I grew in my career, I have started (or made to) worrying about how to avoid mistakes.

While working in Amazon, I have learned a very good concept called KAIZEN. Kaizen is a Japanese concept which talks about continuous improvement. Do not worry a lot about major changes, rearchitecturing the whole system or reorganizing your team. Think about small improvements you can make in your day-to-day life. Can you be 0.001% more efficient by keeping your coffee mug on your right side than your left side? Can you be little faster by aligning your chair, keyboard and monitor correctly?

Kaizen is called "Kaizen" and not bug fix/project/enhancement if the change you have brought has following properties:
  1. is completed in not more than 5 working days
  2. has a direct dollar impact i.e. you can actually derive number of dollars your kaizen will have
  3. it is not a workaround but an actual root cause elimination (this applies only when you are solving any problem)
Kaizens are easy to identify. Anything you do to avoid MUDA (waste) can be called as Kaizen. In Amazon, we are always asked to identify and eliminate wastes. I have seen miraculous results coming out of various kaizens implemented in Amazon.

Following are few examples of kaizens which can be directly related to you:
  1. unnecessary compiling of unchanged classes
  2. long queues at coffee machine taking lot of your time
  3. network delays while working remotely
  4. number of times you type backspace.. instead try typing slow
  5. number of obvious bugs you fix.. can you write unit tests? if written, can you automatically run them at every check-in?
  6. amount of time you spend on documentation you are never going to see as soon as project is started.. work on only relevant documents
Try this and let me know whether or not you see any improvement in your efficiency. Let me know if there are more kaizens you can think of.

5 comments:

Bhavin Shah said...

yeah I too agree that kaizen, six sigma, continuous process improvement are just not management jargon but they do help if one implements correctly. The examples you mentioned are secondary, don't you think at some point it too matters that company should cap activities like chat s/w and emails other than use of official?

don.......... said...

Good writeup. I too believe in this...Keep writing

Unknown said...

Bhavin, capping of activities like chat/emails is a trade-off between employee satisfaction and efficiency.
If employees are really spending lot of time in chatting, it should be capped. But if it is making them innovative by talking to others, keeping them fresh and hence more efficient, then why to cap it?

Personally, I don't think chats/emails should be banned at all. As an employee, I would like to work free instead of working in restricted environment!

adhyas said...

Interesting read. I liked your blog. Maybe I will be back to read more. I do not agree with blocking chats/emails etc at workplace. Freedom is worth more than anything when it comes to innovation.

Anonymous said...

I believe in you keep writing.