Changing Product Direction
From time to time you need to tweak and change your product’s direction. Essentially, this means that you’ll be trying to work in new things, but also change existing things at the same time.
So, how does this impact the organization? Well, in a lot of ways. Namely, it’s the swapping and changing of certain key features that currently exist and changing those out for new features that better match the revised vision.
Really, this is just all about one thing: alignment. Competitors will come and go, but to make a product truly great, it has to align to your overarching vision - the identification of the solution for how to solve your chosen market problem(s).
Now, in theory this is very simple. Turn some knobs here, change out some labels over there - easy, right? Well, not really.
Successfully shifting a product from one chosen strategy to another (regardless of the size of that shift) can face some adversity within the business. People are inherently adverse to change, which is really where the challenge lies. Everyone will be OK with things until features start to get severely changed (or, in many cases, dropped) because they may feel things are working out really well as they are - or maybe, the didn’t understand that a product strategy shift would mean so many new and/or different things.
So, how can you as a product manager help to ease this transition to the new strategy you may have created (or not)? You kind of can’t - just let it run it’s course. Clear things up for people as much and as regularly as possible.
The other thing you can do is communicate early and often. This is something I struggle with because I always ask myself, “why are people interested in what I have to say?” I am slowly coming to the realization that it has nothing to do wit me as a person, but me as a product owner. If you are in charge of the product (and thus, the associated strategy) that’s changing, everyone will be interested in what you have to say.
Why? Because it directly affects them and what they do.
Make the change - buy in to that change. Execute it. Remove features, change features - sometimes more drastic changes are required. It will make the product feel awkward. It will feel drastic, and in some cases downright wrong. But you have to buy-in and you have to commit. Otherwise, you are failing to properly execute the product strategy you believe will make it successful in the end.
