Saturday, March 13, 2010

Bollywood Movies and Society

Bollywood. Indian film industry and one of the big businesses in the world. It's an industry which is having  long history from black and white era to the current state. Most of the subjects handled are local to India and with ample variety. And, followed by millions of Indian population.
Every year number of movies are released based on true stories. With the latest release of "Lal Baug Parel",  a movie based on Mumbai cotton mill industry,  its history and impact on common man.
In case of movies based on true stories, most of the time objective stated is to bring facts to the larger masses. Just stretching it little bit further, I would like to ask  bringing facts to larger masses is just a business or does it help to the society in any way ?
Unfortunately, I do not recall single example wherein subject screened for larger audience  has created waves or minor action to address/resolve/help  the core issue.  So,  I am not sure if movies based on true stories bring anything beyond "entertainment value" ?

Any views ?

Monday, March 1, 2010

Input and Infosys

Any work which we carry out can be modeled as “Input”, “Process” and “Output”. I see that more often than not importance is given to the “Process” and “Output” part.

I will take two examples to set the context

1. Software Development Project
Input: Business Problem Statement
Process: Development of System
Output: Finished Product to Business.
2. Consulting Engagement
Input: Business Problem Statement
Process: Analysis of Problem
Output: Recommended Solution.

Theoretically, we have been taught all the time that equal importance needs to given to ALL the three phases. But, when it comes to project/assignment whose delivery is on critical path, we start putting more time and effort on “Process” part to achieve “Output”. Here, we create another problem than real one. If we do not review our input, validate it, scope it then whatever degree of skill/expertise we apply to the “Process” part we will not be get “Output”. Any effort spend has to be billed to the “Rework”, “Learning” and “Wastage” etc. This goes on until you work on “Input”.
This holds true from smallest problem of resolving a bug in the software to the setting up and running successful organization. Input can be in the form of “Correct/Accourate problem statement”, “Right Resources” i.e. right team to run your business. I believe, Infosys is an example wherein they ensured right team since beginning which resulted in sustained growth.

You will agree more to the above deliberation if I quote few examples of ill attention to “Input”.

1. After days of work, we conclude “Problem Statement is NOT clear” or “I think we do not know the problem statement”.
2. Business confirms product is not meeting their needs.
3. With positive markets, company is unable to achieve desired growth or lagging the peers.

I will conclude with the statements that, Successful leadership is outcome of choosing perfect team to work on organization goal. This is nothing but “Input”.

Make sure, "Input" is correct. Define It, Validate It, Scope It.