Learning from the NASSCOM event on 29th January 2012 – Speaker Ramesh Srinivasan Confianzys


I received a message from Duleep Sahadevan of Software Associates to attend a NASSCOM Event on 28th night. Somehow I had missed out the email on the event which was sent to the CAFIT group. Now I am thankful for Duleep for inviting me to the session. It was an excellent session. The best part was that unlike other sessions, it was making sense to a IT product company that is operating in Kozhikode. This is one of the best Nasscom sessions I attended so far.


Ramesh Srinivasan

Ramesh Srinivasan of Confianzys


The session answered what you should be doing when planning for an IT product. Most of the IT product companies have a feeling that IT products are different from consumer products. This is the first thing we must change. Consumer products do not change for a particular user. So we must also make sure that our core product doesn’t change for the customer. We must identify the need of the customer and try to solve the problem. The engineers must not be given a chance to come up with new products or ideas without a problem(Unless you are doing research). It will be like now you have a solution and try to fit in it somewhere. It is not a good approach. We need to identify the pain points for the customer and try to solve it.


Android iPhone training

Institutes like baabtra play a major role in transforming the graduates of any stream to a software engineer.

For any product there are users and buyers. If you are buying a product for yourself, you become both user and buyer. But there is always a conversation within yourself whether to buy or not. For example, you see a nice shirt in a shop and the user in you wants to buy it. You may not buy it if the cost is too high. So when we are creating a product, we must keep both in mind.

So make a product for the user but market it to the buyer. Product features matters to the user and the buyer is concerned about the outcome. 

Product management has two parts. Product planning(Customer Advocacy) and Product Marketing(Business Value).

For ease of learning, I am putting steps that you must take for creating an IT product.

  1. We must follow a disciplined process in creating an IT Product.
  2. Identify the need or pain point of the user.
  3. Watch the user doing the current activities. You must go to the ground and find out rather than sitting and thinking in the A/C room.
  4. Come and report the activities of the user to the Technical team and analyse whether our company has the competency to solve the problem.
  5. While building the solution, you need to consider the buyer side also. If you can list out the features for the users and outcome for the buyers, it is best.
  6. Once you have the solution, get some innovators and early adopters to use it. (From the book Crossing the Chasm by  Geoffrey A. Moore)
  7. Then you need to plan for Crossing the chasm. You might have to change many things like Channel, price, features etc   to make it appealing to the Early Majority. This is because early adopters of the product (the technology enthusiasts and visionaries) and the early majority (the pragmatists) have very different expectations.

If you believe that this article helped you please like our page  www.facebook.com/baabtra

www.baabte.com | www.baabtra.com | www.massbaab.com

Author can be reached at :

Linkedin –> in.linkedin.com/in/harisnp

Twitter  –>https://twitter.com/np_haris

facebook.com –>http://www.facebook.com/haris.np.9

About Haris NP