After a really hectic trip from Mindtree Pune, I am inspired enough to blog about this. First of all, the weather was like magic. The rain felt like a fine spray (a 20µ nozzle spray, for the scientific minded) and the temperature perfect for vada pav (a great local delicacy which any amount of blogging, pictures, second life experience won’t help) or a special bhel puri (a mish mash of edible crunchy stuff with soggy stuff). In this weather, MTP had a whole week of cricket mania called MPL, with half a dozen teams playing against each other. The fan fare could be heard floors above the action.
In all this, I had plethora of innovation programmes and sessions with different teams. Now, what I really wanted to blog about was the effect of functional analysis and trimming. My earlier blog talked about IFR or ideal final result. The next step is to take up what seems to be the most important problem to solve, based on customer impact. If you have chosen one such problem from the IFR step, next we need to apply functional analysis. I have cut and paste what I wrote in an earlier blog.
1. Identify all possible elements or objects, NOT actions, but specific software modules, players, machines.
For example, importing is an action, but importing module is an object.
2. Interaction Matrix: In the above spreadsheet, rows have all the elements. Transpose these on corresponding columns as well. If elements physically touch each other or there is some direct interaction, mark “+” in the corresponding cell.
For example, if the system is a water bottle. Cap vs. Bottle, the interaction is “+”, although the cap does no actual function to the bottle.
3. The object with the maximum “+” signs should be drawn at the centre of the functional analysis diagram.
4. Keep adding objects to the diagram in the order of the number of “+”s
5. Identify a target object.
6. Add relationships between the objects, if they exist. Indicate the direction of the relationship using an arrow.
7. Add verbs on these relationships.
For example, Importing module “imports” data files.
8. Force verbs even if it is difficult to come up with a verb on all relationships.
9. Insert objects which are not currently used to their maximum potential and are free or almost free (Resources in the picture).
10. Look at which relationships are excessive, insufficient or harmful.
When you finish this diagram, what you have is a functional analysis diagram.
Now this diagram tells you where the problems are, which is the system that actually has control over, and what resources are relatively underutilized. Of course, it also tells you what your system should be doing (Target object). The process is not always the exact. You have to bring in innovation techniques to reach the desired end result. I always get a feel of how complex the system really is to do a simple function.
My next blog will be about Trimming or “A guide on how to make your life simpler”.