Saturday, May 18, 2013

For Harsha Bhogle - Don't cry for cricket

This blog is in response to Harsha Bhogle's article in Indian Express: Don't cry for cricket

Hi! Harsha,

As always a great article. But at this point we need more than just great commentary about the dark times that cricket is facing.  

It is easy for all of us mere mortals (excluding you :) to tell the players to stay away from greed of money. But how can they? There's just too much of it. It's humanly impossible to stay away from it, unless you are the master of your domain. You are dealing here with very basic human tendency - Greed, power and fame. We all have it and the temptation is just too powerful to control. Infact these grown up players are no different from 10 year olds. They see candy and they want it. Who wouldn't?  

There's just too much money being pumped into IPL. It is impossible to separate candy from the game. Cause people who are putting money in IPL are not putting in for the sake of the sport. They are in it for the money. If you ask me, IPL and cricket are two different things. IPL is business and cricket is a sport. Their combination is dangerous and that is what has exactly happened here in the case of match fixing. You tell me otherwise how else are these people (aka investors), who are pumping in Corers of Rs., expected to get their money out?  

So, the focus now has to be on how the candy can be separated form sports? You inherently need some candy since that's also the motivate to make the sport worthwhile. Hence that economic element (candy) has to be there. The key is balancing the candy and protecting the sport from it. What steps can be taken to bring that balance? This is something that the BCCI has to think about. I haven't seen BCCI do anything about the balance, do they even know that such a balance is needed? OR have they succumbed to investors?  

My question to gods of cricket such as GavaskarJi, KapilJi, DarvidJi, SachinJi and others is how get the sport called CRICKET back to life? Please let them know that me, my 10 year old son and my 13 year old niece are waiting for Gods to answers our prayers, just like drought hit farmers wait for rains....

Aditya

Wednesday, May 15, 2013

Stop and Think...And Think Through…


One of the perks that I get as part of leading a company that focuses on starts ups is that I get to meet with a number of eager beavers. These are typically founder, co-founders or part of the core startup team that has embarked on an exciting journey. They are all about action…now or never, just do it, should have been done yesterday… type of attitude. Nothing fundamentally wrong with this attitude, but this attitude should come with a warning label of ‘Don’t overdo it’ and more importantly ‘don’t overdo it by trying to do it all by yourself’.

Hence as work with startups every day, I ask them to follow the principle that was taught to my elder son when he was in first grade.
STOP & THINK!
The principle…simple….STOP & THINK! His school emphasized so much on this principle that they would give out STOP & THINK award at the end of school year.

There's a reason why this principle of STOP & THINK is applicable in case of startups and especially the technology focused ones in India is for a few reasons:
  1. They focus on their organizational strengths and put all their precious resources toward that. For example, most startups (the core team) are extremely technology focused. This means that the little precious resources they have are exhausted in writing the last line of core for beta or buying software or getting that one additional developer to speed up development. More often than not this leads to no resources, mostly money, being left for other critical activities like Product Strategy, Product Marketing, Sales, etc. This leads to the next reason…
  2. Since there is no money / resources left they venturing into attempting to taken on tasks that are not their core strengths.  In the example that I mentioned, it would be a person focused on technology trying to get into Product Strategy, Marketing and Sales activities. Due to these none core skill set activities that they perform, they not only lose focus on core activities but badly botch other key activities that are not core to them.

A thoughtful balanced approach…
Balanced Approach

Here’s the guidance that I provide to startups that I work with...

STOP & THINK: Every time there is a task or a type of activity that you have perform…STOP & THINK…ask yourself the following questions: 
  1. Do you have skills to perform that activity?
  2. Is the right activity to be focusing your time and attention on?
  3. Is it going to take you away from your core activities?
  4. Are there other related activities that might come up?
  5. Is this activity going to end up being huge time sink?

9 out of 10 times as an entrepreneur you will be better off getting paid professional help for taking care of your non core functions. It doesn’t have to be super expensive. But you will end up being saving time, money and make faster progress on things that you want to focus and spend time on.

One of the most common mistakes that technology focused startups do is not getting the appropriate help for Product Strategy and Marketing. These critical functions when done right can help in many ways, some of them being:
  1. Identifying the right customer and market segment.
  2. Building the right product by putting yourself in customers’ shoes.
  3. Putting the development team on right product development roadmap.
  4. Identify partnerships for expanding product offering and increasing product adoption with large customer base.
  5. Position the Product in a way so that customers of the product can relate to it.
If not done correctly and at the right time, lack of Product Strategy and Marketing can spell doom on the startup because…
  1. Team has built technology that the user doesn't want.
  2. The technology is cool but cannot be monetize
  3.  Team has run out of resources to make any course corrections.

If you are one of those technology focused entrepreneur, then I strongly recommend that you take a balanced approach and pull in experts where needed, when building your products and services, early on.

Remember you are sufficient for your idea, but call on experts for running a successful business built on that idea…

Monday, April 8, 2013

Leveraging Customer relationships as a Product Manager


There have been epics written on ways businesses should be:
1.     Identifying customers
2.     Acquiring new customers from competition
3.     Retaining customers
4.     Cross selling and up selling into existing customers 
5.     Leveraging Customers for expanding business

For a Product Manager, who has to deal with many internal and external entities, Customer is by far one of the most business critical entities that he has to deal with. And rightly so, since it's the customers who not only pay for your product but help in innovation, evangelizing product and most importantly give you the credibility to make the right product / business decision and the confidence to stand by it.

Every organization has different dynamics around customer management. Hence as a Product Manager, once you get into a new organization you have to feel your way into the customer management dynamics. Let’s focus on some of the common trends and techniques used for successfully getting a handle on building successful Customer relationships.

1.     Identifying Customers: One of the first and the foremost tasks is to identify the customer. There are two types of customer:
o    Internal Customer: These can be folks within in your organization who use your product or service to assist your external customer or use the product / service on behalf of your external customer. As a Product Manager you should give their voice a significant ear, since they can not only share their experience but also be a voice for external customer. Another benefit is that since they are part of your organization you can leverage them for beta testing, brain storming ideas, hand holding external customer and even for evangelizing products

o    External Customer: These are your paying customer. As a company you have made a promise to them for delivering a product / service and that must be kept. You should categorize the customers in terms of their value to the organization:
§  Revenue (current and potential)
§  Brand value
§  New market beach head
§  New geo beach head

2.   Initial Customer Contact: Initial customer contact is a crucial point in your relationship with the customer. Hence it is critical that you do all the necessary research on the customer account prior to the meeting whether it’s in person meeting or on the phone. The per-call prep can help you gain insights into customers:
o    Business
o    Current issues
o    Temperament
As part of this initial introduction to the Customer, you must establish credibility by highlighting your relevant past experiences and listen intently by being the fly on the wall. One the key things to remember is that as a Product Manager you must align and fit well into the Sales team dynamics, since they are typically the owner of the customer relationships.

     3.   Basic Ground Rules for Ongoing Customer Engagement: Once your initial introduction is done, managing the ongoing customer contact is delicate balancing  act. A customer managed properly can help take your product to the next level along with its revenue.

o    You must establish basic ground rules:
§  Reviewing meeting agenda with the sales team
§  Sending meeting agenda in advance to the customer
§  Follow through plan after the meeting
§  Set up meeting success criteria

o    You have to be careful not to overwhelm the Customer with long and frequent meetings since it can cause confusion and delay in reaching your goal. This is especially true when you and your Customers are geographically apart. Crisp, succinct and to the point conversation is critical for ongoing communication with any Customer.

o    Remember the Buddha story about teaching Nirvana to a starving disciple? As long as the disciple was starving, there was no way he would have been interested in learning about Nirvana. Similarly, focus on the immediate needs of your Customer before offering him advance solutions. Once you solve Customer’s immediate business problems, he will be interested in working with you since trust in the relationship is built.

o    It’s critical to set expectations when you have conversation with Customers. Typically, if you ask customers to share their pain points, they will open the floodgates and expect those pain points to be fixed immediately. Hence before asking the Customer to open the floodgates, you should make sure that you set the right Customer expectations so that Customer doesn’t loose interest and let down. No one wants to tell the same story again and again, especially if your organization is expected to fix at some point. This same principle goes for sharing product and services roadmap. You should help Customers understand that documents like these are for confidential and for directional purposes only.      
These basic principles for managing customer interaction will vary based on geography, industry vertical, business model, company size, number of products, product life cycle, etc. But, if followed consistently will take your business to the next level by forging long lasting relationships with your loyal Customers...

Saturday, February 9, 2013

The Keyser Söze Effect

Here's some information about Keyser Söze, for those who are asking to themselves,"Who or what is Keyser Söze???". From Wikipedia:'...being fooled into believing in a person who does not exist....'

As a Product Manager, I have worked very closely with cross functional teams in various organizations in my past. Everyone has an opinion about the overall direction of the product and the order in which the product features should be built. And then I start the judicious process of investigating the details of these cross-organization opinions, which to say the least is very interesting. It's truly amazing to see the extent to which people will go to make Product Managers believe the validity of the product need that they are representing. Some of the most commonly given reasons are:
  1. The CEO / VP etc. is asking for it
  2. Our competition has it
  3. Lots of customers are asking for it
  4. I know it will sell (corollary - I cannot sell without it)
  5. It has lot of revenue potential
  6. Customer wants it now!
There are many more such justifications that I see come up from time to time. And every time I find a new one, it feels like I'm dealing with Keyser Söze. Only in this case I'm being convinced into believing in a feature instead of a person that doesn't exist. Hence, as a Product Manager when I'm in product roadmap and strategy conversations  I have to understand if I'm dealing with Keyser Söze situation or not.

The good news is that it's not rocket science to get out of a Keyser Söze situation. Here are a few ways:
  1. Ask 'Why?'. Keep asking 'why?', 'what?', 'how?' until the business opportunity or product need is quantified. You have to be able to associate some numbers. It can be revenue, customers, or some other number.
  2. Get to the source. As a Product Manager the farther away you are from the source of the need the worse Keyser Söze effect gets.So cut the to chase and get to the source. This will help you understand the real business need and urgency around it along with saving you tonnes of times and resources. Armed with this information you will be able solve the problem and not just the symptoms.
  3. Then there is pattern recognition. You can leverage historic data, the blast from the past, to see if the product need is valid. This is especially helpful when you don't have direct access to the source or you want to perform high level validation. 
At the end of the day as a Product Manager, you have to reduce the Keyser Söze effect to a level where you are able to take a stand. A great Product Manager is able to do this fast and extremely effectively over a period of time by leveraging:
  1. Data repository of product usage, industry trends, etc
  2. Direct and indirect relationships built with source of the need.
  3. Processes that help others in the organization understand and deal with Keyser Söze effect.
And for those who are still mystified with Keyser Söze, I would suggest watching 'The Usual Suspects'...one of my all time favorite movies...

Sunday, February 3, 2013

Thoughts on: Career in Product Management

Product management is one of the most rapidly growing professional fields. With software industry’s rapid growth, it’s becoming more and more critical to hire the right Product Managers.
In a nutshell Product Manager is the person, who identifies business problems and creates revenue generating solutions in the right time and at the right time. As a product Manager you should know the answers to these basic questions in the context of your product / service:

1. What value is the product bringing to its customers?
2. What is the business problem being solved by the product?
3. What is the revenue opportunity for solving the business problem?


Without knowing answers to these questions you are the captain of a ship without radar. And this is not a onetime exercise. Business conditions in this internet age change rapidly. So as a Product Manager you have to be continuously on the lookout for new competition, and threats that can quickly make your product irrelevant in the market. 


People can argue that one doesn't need to be a Product Manger to come up with good ideas. And they are right! Identifying the right opportunity for your product / service is just one piece of the puzzle. The other key piece of Product Manager’s life is to enable smooth execution across the organization by creating the right alignment. Remember just like justice delayed is justice denied…execution of an idea delayed is an opportunity lost. Hence, as a product manager your one eye is on the market and another on execution of idea and bringing it to the market at the right time. What this means is that, you identifying and bringing the right product growth opportunities to various stake holders such as Engineering, Quality Assurance, Sales, executive team, etc. You get them on board and get their sign off on the execution plan. In this process you may leverage project managers to help you coordinate various activities. But at the end of the day you, are one responsible for making idea / business opportunity real. Your behind is on the line!
In your life as a Product Manager, you will find yourself in the middle of this virtuous cycle of business problem and solution execution of that business problem. As you start your career in Product Management, you may focus on one or two features and then grown on to take more and more responsibilities till you finally become completely responsible for that product / service. Then as you become Director or Sr. Director of Product management you may own a portfolio of products. In this role you will be responsible for revenue that can be attributed to your products. The executive team depends on your products for the overall growth of the company. This continued growth leads to positions like Chief Product Officer (CPO). This is just of the possible career growth paths. Many product managers eventually start their own business with an idea that they have and become CEO, Co-Founder, VP of Product Management, etc.


Here’s a short list of questions to ask yourself when thinking of a career in Product Management:


1. What kind of problems do I want to passionately solve? Quick test of passion – Does this problem keep you awake at night?
2. Do I like to be in the middle of action and be the deal maker to align various organizational stake holders?
3. Can I create cross org alignment for my product?
4. Do I have vision about product or the business problem that my product addresses?
5. Can I convince people to invest in the business problem that needs to be solved?
6. Can I succinctly communicate with various internal and external audiences regarding my product?
7. Can I convey the value of my product so that the audience can relate to my product?
8. Do I like to analyze data, spot trends, join the dots together?
9. Can I explore and present options to keep moving the team forward?
10. Can I own up, roll up the sleeves and do what it takes to get the job done?