Skip to main content

Analysis Vs Synthesis

The 2 skillsets that a product manager needs a lot are Analysis and Synthesis.

I am a business analyst who turned into a product manager. It is easier for me to be reliant on my analysis skills since that is what I am trained as a business analyst.

However, what is also equally important is the synthesis skills.


How are they different

Analysis refers to the ability to break down a problem into constituents and start attacking them. This helps the product manager a lot when there is enough feedback from users and all the product manager has to do is just carry it out. There is no need for prioritisation from the side of the product manager since the user’s preference would clearly give that information as well.

This works well when the product is an already released product and it is not difficult to understand what is needed and why it is needed.

Synthesis, on the other hand, refers to the ability to piece together multiple pieces of information to understand the bigger picture.

Synthesis involves hypothesis testing. This is key to a product manager mostly during the initial phases when the product is being introduced or tested and during a phase when the product hits a bottleneck.

How can we balance out both the skills

At any point of time, the product manager needs both the skills. The key lies in identifying when to do analysis and when to do synthesis.

My rule of thumb is as follows:

When you have enough information, analyse the situation and include it in the product plan.

When you do not have enough information, form an hypothesis, test it and based on the outcome decide on the future option.

Hypothesis can be tested either as Minimum Viable product or as a pivot , as the situation might dictate.
Labels:

Comments

Post a Comment

Popular posts from this blog

The right business model for your product

How would you decide what is the best business model for your product? Deciding on the right business model is very important for the product. It does not necessarily mean what is the price of your product. There could be no price for your product - though that is a myth. For example, we think google or Facebook is free. However, we are never the customers for Google or Facebook. It is the advertisers that are its customers. What we need to figure out when we decide on a business model are as follows: Who is my target audience? Who is my customer What is the price. How is the support model going to work Who are my partners While we do not absolutely need to price a product, we need to understand how we would make money. For example Open ERP does not price its product. However, its product is not the ERP software but really the hosting, service and training that it offers. While pricing is an important part, what is more important is in realising who is you...
Post a Comment
Read more

Finding your target audience

The biggest task of the product manager is to find your target audience. Typically it is a very tight rope walk. You define it too narrowly and you would struggle to generalize the product later. You define it too broad and you would struggle to satisfy a lot of people and the product might not take off at all. There is this awesome post by Dave Mcclure on why Niche target segment works. Blog link here . What he says is mostly right and that is what we did as well. We did it mostly by accident. We had to define our niche because we could only talk to those kind of retailers and get data from them to start developing the data. It did have its upside. We were very clear on what we wanted to develop and we are slowly talking to retailers and adding more scenarios. As we are doing this, we are also talking to a slightly different set of retailers. This helps us incrementally build our product while also generalizing the existing features. In our case, we did not fin...
Post a Comment
Read more

Constructing the Product Roadmap

When I started out in the team, I was tasked out with coming out with a plan so that we can demonstrate the product with real data. The idea was to demonstrate it to our prospect with their own data and win them over. However, when I started working, I found out that what we lacked was not a plan but a vision. I quickly put together a one day workshop with our team and our product owner. When we started talking, we talked about several things and figured out that we needed a plan of various proportions. We needed a plan that could help us one the following: Provide a focus for the long term with near term focus on just one thing Help us talk to prospects on what we are going to do Help us decide on when we would need to focus shift on which function - Engineering , sales etc We also did a quick “Product in a box” exercise so that all of us in a team can practice and imbibe the elevator pitch. We needed this since we had to do this pitch at several levels - Inter...
Post a Comment
Read more