Why Processes? - Contd...

Part 3:

Since we can’t leave tasks to be performed differently by different individuals, we try to streamline activities by framing processes around them.

But, why is quality always looked at as ‘documentation’ or an overload of that? Why should we document? Is there any relationship between ‘process-focus’ and ‘documentation’ at all? Do we need SEI or ISO to tell us we are process-oriented? Why?

Let us take the example of your mother making ‘Dal’ or some delicious ‘Sambar’ in her kitchen…

She has the process ‘institutionalized’ in herself. She is habituated to making it a thousand times. Hence, she need not go through a manual or look at a written down process. She knows clearly what she is doing.

On the other hand, you/your wife/sister/brother want to emulate her cooking skills. You need to note down (document?!) the process, follow it a few times until you become an expert!

Alternatively, you could watch her and repeat the steps. But that is not scalable! You can’t really pass it on to the others who may want the recipe…

That is exactly what we do in business. We have some experts. They have tried and tested many recipes for successful projects. They have documented all that worked (and those that did not too!). If they had not documented or felt lethargic about it, we would be reinventing the wheel now! What a waste of everything it would have been?!

Now, you may ask me, why do I have to document my own project-related details (why a requirements document, a design doc and a test plan)? Well, wait for me to continue on more ‘whys’…