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

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 i...

Designing for Accessibility

The software world has starting being more inclusive. After serving only the geeks and the techies, a lot of the software that is produced in this world has started looking at how it can be mor euseful. One of the key constituencies of software usage is people with disability. The ADA (Americans with disability Act) has forced a lot of the software developers to look at this issue. The software world has also responded sensitively and with care making as much of the software usable by people with disability. One of the key components that we are looking at in this are people with visual impairment. Over a period of time, a lot of the software has made sure that the user experience is adjusted in such a way that is is intuitive. Google has been a front runner in this and a lot of others are also not left behind. Text The size and the font typology is very important. Choose those aspects with ADA in mind. Media like Images A lot of the media , including video and images ,...

The cost of delayed decisions in Enterprise

Large enterprises have started their IT journey in earnest. However, they are miles behind what is happening.  Some of them have been trying to learn faster by creating research programs or separate business unites to try out and learn a few exotic ideas that have not yet gained acceptance in the industry or enterprise. Enterprises have moved record collection and data to IT long back and were pioneers in that. However, since the advent of personal computers, they have been left behind. Internet and mobile have left them far behind. For example, Network security, big data, mobile apps. social applications are solved problems that the enterprise choose to ignore.