How to Identify and Navigate Chaos in your Product Strategy Imagine if the above didn’t have to happen… We’ve all been there: the feeling of dread when nothing you’re doing seems to work, clients are angry, sales is furious, and you are swimming in a sea of feedback while being pulled in a million different directions. Although we don’t talk about it, most product managers will be handed a bad strategy at some point in their career and be expected to succeed. Having worked across companies of different industries/sizes/goals, I wanted to distill a general framework for evaluating product strategy across industries and company sizes. So by way of an illustrative analogy, here are the ways to both diagnose the symptoms of a bad strategy, and the tools I’ve used to help fix them. Framing the Product Maze Let’s start by looking at this maze, which represents the constant state any PM finds themselves in at a given point in time. Much like a maze, there are countless potential paths to choose from, but most of those paths lead to dead-ends rather than exits. But what exactly is at the end of a maze for a product manager trying to escape? This is what we call the . Product Vision Product vision is long-tail goal of what you want to achieve, your elevator pitch, your exit to the maze. It is an imagination of the future that takes into account business factors like customers, competitors, monetization, and industry. Additionally, most everyone in a company typically has a sense of the product vision, even it slightly differs (we all want to get out of the maze). So once you know there’s an exit to the maze, the question becomes, “How do you go about getting out?” This is called the Product Strategy. While product vision describes the ultimate end-state, product strategy describes how to get there (how to navigate the maze). More importantly, Much like being trapped in a maze, there’s only so much time you have to escape before you run out of resources… you’re not likely going to have the time or energy to wander down every path. product strategy requires taking into account the limited resources and time a business has to prove a concept. Product strategy therefore is how to describe to your organization the path you want to explore to get out of the maze (AKA achieve your product vision). It’s also important to note that much like an initial path, a product strategy can be informed and change frequently, whereas vision is usually more static. So you find yourself in the maze, with an idea of how to chart a course out, but how do you choose which path to go down first? Challenge 1 — Which Direction to Head? If you think about the above image of the doors, it presents a few major issues: There are a lot of options, but there’s no clear indicator of a ‘best’ path to pursue We don’t actually know what the characteristics of a correct path are. If one of the doors is ‘red’ vs ‘blue’ — is that good or bad? This is a rightfully stressful situation and, without a good solution, you have the first symptom of a bad product strategy: Symptom 1: Trying to go down every single path (hunting for revenue/lacking focus) It can start of as completely harmless — “We’ll just go try out some things until we find something”, but this is not always an unreasonable thing! However, when you analyze the situation you come across two big problems: Similar to being stuck in a maze, you may not actually have great insight into how long it will take to get out (product/market fit) Much like a maze, you likely don’t have the resources to stay there forever (running out of supplies / time / trust your team places in you) What happens in the business world is that too many quests for validation will deplete resources, make people question your ability to navigate your product, and put you at risk of never achieving your vision. So what’s the solution for starting out? Solution: Create a way to leave a trail! (wander with a purpose) Without tangible goals or tracked assumptions you’ll go down a path and eventually forget how to ever get back. Instead make like Hansel & Gretel and create a trail of breadcrumbs to help you get back! So what are breadcrumbs in the business sense? They are typically called a roadmap, which traditionally shows a multi-year stack-ranked timeline of features to be completed. In reality, it’s a list of stuff you’ll mostly never get to that’s only accurate for about 1–2 months out, ouch. If it sounds like I’m being harsh, it’s because roadmaps are a terrible tool to relay strategy and business value! Let’s go back to the maze example — if you were stuck with a group of people in the center, how confident would you be telling someone where they’ll be half a mile? It sounds absurd in an analogy, and yet this is how thousands of PMs are trained to communicate where they’re heading! In reality, the way you convey what your team is building should relay the . So instead of relying on strategy proxies like a multi-year feature map that changes every quarter, consider moving to paradigms such as ‘ ’ that focus around the value of the work delivered rather than describing the work itself. value of the path you as a PM are sending people down themes Another similar approach the Monzo team wrote about is called ‘ ’, which is the process of identifying where the business makes and loses money. split trees Both approaches change the focus from mindlessly shipping work to describing what you hope to achieve with that work. Further combining things like Themes + Personas can even tell you what paths may be a complete waste of time without ever walking down it! Challenge 2 — How Far to Take a Path? So you did your research, picked a promising path, but now things are feeling off. Most decisions a product manager makes are not going to have an immediately observable effect, so you have the following issues: How long do I go down a path before I turn back? How do I ensure I have enough resources to even try another path? This is particularly problematic for products that are released and do not have great initial traction, and can lead to the second major symptom of a bad product strategy: Symptom 2: Going down the wrong path for too long (not validating product/features) This can be a harder symptom to detect because it often involves more than one stakeholder. For example, 1) the CEO of the company may have experience in the industry and state what you need to build, or 2) your favorite customer could request a one-off feature that they say is valuable to them. While it is tempting to just follow the lead and take the request at face value, there are problems to this approach: Without understanding the kind of path you’re going down, you may not even have the equipment to make it all the way! Having others tell you the way to go makes you become reliant on their ability to navigate the maze. A customer’s exit path may not match yours, and one-offs often lead to dead ends in the world of product management. Both of these issues highlight that have you risk wandering aimlessly down a road to nowhere without clear criteria for when to turn back. So how does a PM try and prevent this from happening? Solution: Decide how far is too far before setting out down a path (market validation) One amazing tool to do this is the which was made popular by the Silicon Valley Product Group. Much like Amazon’s of working backwards, it’s a devilishly simple looking list of questions that forces the PM to really understand what they’re getting into, and the value they’re seeking, long before code is written. Product Opportunity Assessment framework In essence, it creates valuable friction around the product development process and forces you to think about mapping out the journey before actually going down the road. If you see multiple paths as equally valuable, consider using the above in addition to the to map out your total addressable market. This not only helps define isolated opportunities, but also maps them to the total addressable market and helps visualize realistic stop points for validation. concentric circle approach To go along with the maze example — the core of a circle would be your initial market validation, with the outer circles representing potential expansion markets. Once a PM has launched a product with users completely served by your solution you now have a safe zone to expand from. This way forces people to understand that various segments of addressable markets can exist, and whether or not you’re even near the right area to expand to closely related segments. Ultimately, if you keep going out further of the safe zone without achieving a solid user base for what you’ve built, you’ve probably gone too far. Challenge 3 — Am I Following the Right Signs to Exit? At last, the light at the end of the tunnel! You’ve done validation, focused on responsible segmentation, and have picked strong strategic paths, what could stop you now? Alas there are still issues a PM needs to be vigilant about: What if what I’m hearing isn’t the reality of the situation? Is this the path we all need to go down, or the one I WANT to go down? You’ll notice that this is different than challenge 2; it’s not questioning the reasoning but rather the assumptions itself, which is the 3rd and final symptom of a bad product strategy: Symptom 3: Misinterpreting signals for validation Out of all 3 symptoms, this is the most non-obvious of the bunch, because everything is usually right… until it isn’t. Much like a maze — wind (signals) can be an indicator you’re almost at the surface, or it can lead you down deeper into the labyrinth. This happened to one of my former companies, we were experiencing great success, had momentum and clients, but started becoming too reliant on client requests as a measure for where we needed to go. Eventually it went sideways when we built a multi-month integration one client demanded, only to have them end up not using it because the person asking for it wasn’t the person writing the checks…I still have nightmares from this. So how can you minimize the chance this happens to you? Solution: Never get Comfortable with the path you’re on! Iterative feedback is absolutely critical if you want to continue to drive success for a product. This can happen in a plethora of ways — low fidelity mockups, user betas, product council groups, the list goes on. The key though is regardless of the methodology you take up, never lose touch with the heartbeat of your industry! Personas can be a valuable tool for this, but can’t be created in a vacuum! It’s fine to own the creation and updating if that’s what you as the PM decides works best, but owning does not mean being the only one that decides what’s included in the persona. As a PM you need to understand that this is a collaborative effort, usually with the people selling your product. Think about the maze again — a person stuck alongside you may not know specific characteristics of a good path, but if you give them a torch (persona) they can definitely assist in helping find what you’re looking for in a good exit path. I find that personas work best for this purpose when you focus it around 3 sections: Motivations Minimum features needed to use High-value features needed to love If this is done right, you should be able to take almost any feature/product request someone wants to make and ask which persona this helps contribute to. Tightly linked business goals to well-defined (and updated) personas can drastically reduce in-fighting on priorities and reduce ambiguity to desired outcomes for any feature request. Conclusion We covered a ton of material above, and I want to take a moment and make one last point before coming to a close. While I reference a lot of techniques and frameworks above — the fact is that there’s no 100% fail-proof way to managing a bad product strategy, and you always face the risk that the light at the end of the tunnel is a train. The best product strategies in the world can still fail for reasons beyond anyone’s control, and that’s something PMs need to realize as well in their career journey. Ultimately, taking account of where you are in the maze, why you’re going down the paths you’ve chosen, and what the indicators along the way are the best way to maximize your chances of getting out intact!
![Tensor Flow - [Technical Documentation]](https://hackernoon.imgix.net/images/undefined-q683u5r.jpeg?auto=format&fit=max&w=96)
