Skip to main content

When to pivot

Pivoting is a very painful decision for Product Managers. It is also a decision that we , as product managers, dread.

Pivoting in essence is one of the key decision points that a product manager needs to always be on the look-out for.

A little bit of Context

The job of the product manager, at various levels, is also to look at it from a 30,000 feet level, understand the context the product is perceived by the customer and understand how he can make the product better for the customer.

This is easily said that done.

Product managers tend to get lost in the daily details of running the show that their interactions are always on the transactional level.

Irrespective of whether the product is doing well or not, a product manager needs to watch out for the changing landscape.

To Pivot ot Persevere

The product manager needs to make a hypothesis on whether there needs to be a revision on what problem it is solving.

The hypothesis needs to provide a result that will help the product manager understand on whether to change what the product is all about or persevere with what we are doing today.

One of the means is a new minimum viable product. (To know what a minimum viable product is, do checkout Minimum Viable Product)

Comments

Popular posts from this blog

My Journey in Inquiry and Advocacy - An experience report

It is recently that I have consciously started practicing Inquiry. Let me explain. I am a consultant who constantly looks at the situation and comes up and implements the solution to progress from there. While I do that, I constantly use Inquiry as a means to progress - one of the key facilitation technique specifically in multiple stakeholder situations.

Principles for developing systems that are anti-fragile

I have been trying to make sense of what anti-fragility means and how do I use that in my day job. As a Business Principal, I tend to work with the abstract but orchestrate a program of work that needs details. This makes my job a little difficult in the terms of designing for more self-preserving systems that preserve the spirit of the abstracted strategy or vision. I came across an article from Daniel Russo on anti-fragility and his attempt at creating a manifesto similar to the manifesto for agile software development. For more reading on Daniel Russo, here is his profile:  http://djrusso.github.io More reading from his paper here:  https://www.sciencedirect.com/science/article/pii/S1877050916302290 This post is an attempt for me to understand what goes into developing a program that uses every opportunity to strengthen itself and achieve its objective - the vision.  I liked the approach of principles for developing systems that are anti-fragile. It is a very valua

User Personas

User Personas are a very good tool for the product owners, business analysts or product managers to be able to co-create with designers. It is predominantly a product of the user research and should not be an amalgamation of demographic data. It is the best way for us to list all scenarios that a persona would take when they want to attain a goal. It is predominantly used to build empathy with user, focus the team and build consensus in a large diverse stakeholder group. The website I referred to is here:  https://www.smashingmagazine.com/2014/08/a-closer-look-at-personas-part-1/