Introduction
At the outset let us understand the difference between the want, the need and the expectation. The ‘want’ and ‘need’ are not the same. ‘Want’ is you would like to have, whereas ‘Need’ is you have to have. For example, humans have basic needs like food, shelter and cloth. Anything beyond this is your want like food in five star hotel, a big bungalow and branded clothes. Whereas, ‘Expectation’ is the anticipated circumstances. For example, one may feel that if I join new job I might be able to repay my home loan immediately or someone may expect that I want to purchase new house. So, these are the probable or likely or anticipated circumstances from this new job.
Many times what customer wants or need have trouble in expressing it or find it difficult to narrate for various reasons like technical, commercial etc.
Problem Statement
Whatsoever even though we want to exceed customer expectations but without understanding their wants and needs it is difficult to do so. The customer may want an apple, but he was in need of orange and we delivered watermelon assuming his expectation. To avoid this we need to show the customer what we have done after interpreting his requirement.
Solution
In any study it is essential to identify, discuss and freeze. Thus, by using “Show and Tell” concept one can get
· Get multiple perspectives of the stated problem
· Check for conflicts as well as reinforcements
· Able to filter the blame part of the problem statements and classify them as events that prevent operations. These would translate into high level requirements for addressing the business pain area and as requirements for the systems
This strategy must be applied to whatever stage we enter into the engagement, the team must give opportunity to the customer to express his desire by showing the in-process building system from time to time. This will help to identify the,
· Business pain area (problem recognition)
· Perceived solution for the pain area
· Study scoping of the requirement
· Business model – drawing of complete process maps (including workflow, rules, location for the processes, managing events, etc.)
By using this concept of ‘show and tell’, one can split the pain areas into smaller components and establish accountability, validate and re-validate goals and from time to time check for feasibility of the solution components and trigger innovations.
Regards,
Vaishali Tikare