Saturday, December 29, 2012

Product Management Approach to New Product development vs. Existing Product

I wanted to compare and contrast the product management approach to developing a new product vs. adding features to an existing product.  I have been thinking about it for a long time and after skimming through numerous product management books and discussing with fellow product managers, I believe the below approach makes a lot of sense.

New Product:

Opportunity Discovery --> Opportunity Assessment –> Opportunity Validation –> Product Discovery –> Solution Validation –> Metrics (KPI) definition –> Execution –> Go-to-market strategy –> launch –> post-launch assessment.

Opportunity discovery = ideation, but often the opportunity is presented to you either by either the founder in a startup environment or by a senior executives in a large company. It is difficult to cover each of these definitions in this article, but they are self explanatory. I will try to add more details in future.

Each of these phases are important and based on where you are in the product life-cycle (introduction, growth, maturity, decline), you might encounter one or more of them.

Existing Product

Compare this to the approach which generally works for adding features to an existing product where you analyze the usage metrics, come up with feature definition which could move the needle in the right direction, develop, deploy and measure. This cycle of build, measure, learn is very well documented by Eric Ries in The Lean Startup book.

 

I will try not to get into too much details, but it is suffice to say that the approach to product management for a new product is very different. While working on an existing product, the customers are known, their needs have been established, the solution has been validated and we now have a known product/known customer scenario. In the new product scenario, both the market and the product is unknown. You are not sure, if there is an opportunity. Even if there is one, is the need  strong enough that they are willing to pay for a solution. You have no idea about the solution and if it  has significant value proposition. You probably do not know who your customers are in the first place. Eric covers it very well:

 

 

Market Product Methodology

Known

Known

Waterfall

Known

Unknown

Agile

Unknown

Unknown

Lean

 

In the lean start up approach you have to focus on the customer development in parallel to product development. Read Steven Blank’s The Four Steps to the Epiphany for more details

Windows Live Writer

Windows

I have been looking for a good desktop client to manage blogs for sometime now. Based on some research, I found Live Writer from Microsoft. So far it is working out pretty well. http://www.microsoft.com/en-us/download/confirmation.aspx?id=8621

Sunday, November 25, 2012

Entrepreneur as a job title


While listening to Eric Ries talk about entrepreneur as a job title within large organizations, I could not help but reminisce about my days at Verizon. Verizon group CIO Shaygan was way ahead of his time as he implemented most of the principles suggested by Eric in his book  - The lean startup. He incentivised the culture of entrepreneurship by making each Director of Engineering responsible for P&L (even if it was just paper money and no real transfer of money took place).

Each Director was allowed to grow his organization as big as he wants to, as long as he can pay for it. If the P&L group could not raise enough money to pay for all the employees it was forced to let go off the resources. Obviously this encouraged group leaders to hire consultants so that scaling up and down can happen without impacting  full-time employees.

Overtime this culture of innovation and competitive spirit gave its way to politics.

Saturday, November 24, 2012

Audible.com

I signed up for audible.com yesterday just to try it out. I also wanted to review the
The Lean Startup: How Today's Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses book as I had no patience to read it the second time. I was pleasantly surprised by how effective audible.com is. Maybe my experience was so positive as I had already read the book. 

The only biggest issue with the audible books is you cannot purchase them within the iPhone apps. I am sure this has to do with Apple insisting that publishers pay 30% cut. I had to buy the book using a website and then download it to iPhone, which takes an effort. Remember my earlier post about reducing friction in user experience.

After wasting time politicking in my new role as a GM at a different kind of company, I am back to writing my book. I am hoping to start publishing some material from the book as blog articles. This will help me get some valuable feedback as well as generate buzz for the book.

Friday, November 23, 2012

Friction


Today I was talking to my friend about a product idea that requires users to take a very simple action to derive value from it. She thought that the product might have an issue with stickiness if it requires users to take an explicit action on regular basis. The reason that Mint works so well is because user is not required to take any action or change his normal routine in any manner. It pulls the necessary data from the bank servers.

The discussion reminded me of something I read in an innovation strategy book about continuous vs. discontinuous innovation. Even a small friction in value delivery can reduce the adoption and stickiness of the product. Users are less likely to adopt to discontinuous innovation, unless the value they derive from the effort to learn or perform an extra action is higher than the effort.



Wednesday, July 4, 2012

Data Driven Product Management

After a long time, I was finally able to find some time for my book (data driven product management). I now have 108 pages of content, ready to be published. I think I am 70% there. Now time to figure out, how to publish on Amazon.

Sunday, June 17, 2012

Graph Database - Neo4j

I have been studying graph databases for last few days for my new company, and Neo4j guys have done a pretty amazing job. If you are not very familiar with graph databases, think of them as a database to represent relationships between objects.

Since the real world relationships are very complex to represent in a regular relational databases, NOSQL databases come to the rescue.

Use case:

  • User 1 is a friend of User 2
  • User 1 is a man
  • User 1 lives in San Francisco
  • User 1 likes Netflix
  • User 1 watched movie seven
  • Users 1 traveled to Paris
The set of properties associated with user 1 like, he is a man and lives in San francisco and the relationships to other objects like is a friend of user 2 and likes object Netflix are very complex to represent in regular relational databases like MySQL. 

NOSQL databases are of 4 kinds, based on the use case. 

1. Key value
2. Column databases
3. document databases
4. graph databases

The above use case is best represented in a graph database. You can get more details by watching http://www.youtube.com/watch?NR=1&feature=endscreen&v=BFTLOABf5oY youtube video.

I will continue writing more as I explore it further.