Would you rather put your energy, brain power and talents into solving the right problems, or the wrong ones? You know the ones. The problems your customers don't actually need solving. The features you worked around the clock on, that had close to no impact. Bad product strategy happens to good people at good companies, all the time. And it happens because there's a bunch of roadblocks that many teams aren't even aware of. If these roadblocks go unchecked, it's nearly impossible to answer questions like: - Do we know what's really important for our users, and for the business? - If not, do we know how to find out? - Do we have a good system in place for generating, identifying, and making the best use of insights? - Do we know how to turn those insights into action? - Do we have a scalable, repeatable way to do all the above? Here's our take on the biggest things standing in the way of good strategy, and how to overcome them: https://bit.ly/48nRSkR What holds your team back from knowing what to build next? #productmanagement #design
Dovetail’s Post
More Relevant Posts
-
🎯 𝗔𝗹𝗶𝗴𝗻𝗶𝗻𝗴 𝗘𝘃𝗲𝗿𝘆 𝗦𝘁𝗲𝗽: "𝗛𝗼𝘄 𝗥𝗲𝗶𝘁𝗲𝗿𝗮𝘁𝗶𝗻𝗴 𝗣𝗿𝗼𝗱𝘂𝗰𝘁 𝗩𝗶𝘀𝗶𝗼𝗻 𝗗𝗿𝗶𝘃𝗲𝘀 𝗣𝗿𝗼𝗱𝘂𝗰𝘁 𝗦𝘂𝗰𝗰𝗲𝘀𝘀" 😊 Let's discuss product vision today! Just like in life, having a clear vision when embarking on any project guarantees focused effort, provides the drive to push through challenges, and gives a concrete goal to work toward. In product management, 𝐭𝐡𝐞 𝐩𝐫𝐨𝐝𝐮𝐜𝐭 𝐯𝐢𝐬𝐢𝐨𝐧 𝐬𝐞𝐫𝐯𝐞𝐬 𝐚𝐬 𝐭𝐡𝐞 𝐠𝐮𝐢𝐝𝐢𝐧𝐠 "𝐧𝐨𝐫𝐭𝐡 𝐬𝐭𝐚𝐫" 𝐟𝐨𝐫 𝐞𝐯𝐞𝐫𝐲𝐭𝐡𝐢𝐧𝐠 𝐰𝐞 𝐝𝐨. Without a well-defined vision, the product risks drifting, with efforts scattered, lacking direction; and any effort that is not channeled cannot be maximized. However, 𝘀𝗲𝘁𝘁𝗶𝗻𝗴 𝘁𝗵𝗲 𝘃𝗶𝘀𝗶𝗼𝗻 𝗮𝗻𝗱 𝗰𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗶𝗻𝗴 𝗶𝘁 𝘁𝗼 𝗲𝘃𝗲𝗿𝘆𝗼𝗻𝗲 𝗶𝗻𝘃𝗼𝗹𝘃𝗲𝗱 𝗶𝘀 𝗼𝗻𝗹𝘆 𝘁𝗵𝗲 𝗯𝗲𝗴𝗶𝗻𝗻𝗶𝗻𝗴. In my experience, I believe 𝘁𝗵𝗲𝗿𝗲’𝘀 𝗮 𝗰𝗿𝗶𝘁𝗶𝗰𝗮𝗹 𝗻𝗲𝗲𝗱 𝘁𝗼 𝗰𝗼𝗻𝘀𝘁𝗮𝗻𝘁𝗹𝘆 𝗿𝗲𝗶𝘁𝗲𝗿𝗮𝘁𝗲 𝘁𝗵𝗲 𝗽𝗿𝗼𝗱𝘂𝗰𝘁 𝘃𝗶𝘀𝗶𝗼𝗻. When discussing features, we should ask, 𝘩𝘰𝘸 𝘥𝘰𝘦𝘴 𝘵𝘩𝘪𝘴 𝘵𝘪𝘦 𝘪𝘯𝘵𝘰 𝘵𝘩𝘦 𝘷𝘪𝘴𝘪𝘰𝘯? When drafting the roadmap, we need to question,𝘸𝘪𝘭𝘭 𝘵𝘩𝘪𝘴 𝘣𝘳𝘪𝘯𝘨 𝘶𝘴 𝘤𝘭𝘰𝘴𝘦𝘳 𝘵𝘰 𝘵𝘩𝘦 𝘷𝘪𝘴𝘪𝘰𝘯? When defining strategy, the key question is always, 𝘪𝘴 𝘵𝘩𝘪𝘴 𝘵𝘩𝘦 𝘣𝘦𝘴𝘵 𝘢𝘱𝘱𝘳𝘰𝘢𝘤𝘩 𝘵𝘰 𝘳𝘦𝘢𝘭𝘪𝘻𝘦 𝘵𝘩𝘦 𝘷𝘪𝘴𝘪𝘰𝘯? It’s easy to lose sight of the vision amid day-to-day tasks. Yet, it’s crucial that every decision—whether about what to build, which problem to solve (and why), or even who to hire—should be measured against the vision. 𝐄𝐚𝐜𝐡 𝐦𝐢𝐥𝐞𝐬𝐭𝐨𝐧𝐞 𝐦𝐮𝐬𝐭 𝐩𝐮𝐬𝐡 𝐮𝐬 𝐜𝐥𝐨𝐬𝐞𝐫 𝐭𝐨 𝐭𝐡𝐞 𝐠𝐨𝐚𝐥 otherwise, we risk a lot of wasted effort and resources. Lastly, 𝗰𝗼𝗻𝘀𝗶𝘀𝘁𝗲𝗻𝘁𝗹𝘆 𝗿𝗲𝘃𝗶𝘀𝗶𝘁𝗶𝗻𝗴 𝘁𝗵𝗲 𝘃𝗶𝘀𝗶𝗼𝗻 𝗲𝗻𝗮𝗯𝗹𝗲𝘀 𝘂𝘀 𝘁𝗼 𝗰𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲 𝗶𝘁, 𝗿𝗲𝗳𝗶𝗻𝗲 𝗶𝘁, 𝗮𝗻𝗱 𝗮𝗱𝗱𝗿𝗲𝘀𝘀 𝗮𝗻𝘆 𝗴𝗮𝗽𝘀 𝗼𝗿 𝘄𝗲𝗮𝗸𝗻𝗲𝘀𝘀𝗲𝘀 𝗶𝗻 𝘁𝗵𝗲 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝘆. This keeps us on track to achieve the vision in the most effective, competitive way possible I hope you enjoyed the read! Until next time; happy producting. 😉
To view or add a comment, sign in
-
What to do if you product design fails Sometimes, your requirements are too broad or to narrow to cover corner or all the cases, this can lead to design fail. Once this happens, you need to address it with focus. There is no way to keep fighting for what didn’t work, but proactive work to reduce the noise and protect your product reputation. Focus on the root cause then how this connects with all the other workflows. Test the fix to that and all the other workflows with different datasets. The same way you congrat the development you need to congrat the debug. Take the lead as the product manager. Show your face, take responsibility. Engage your team to focus on what matters, avoiding the blame game. Nobody will win if you discover the one who failed, but everybody will once you discover the solution. Keep going! Failure is a result not a destiny . #productdevelopment #productmanagement #productdesign #healthcare #management
To view or add a comment, sign in
-
Which product roadmap format is best? It depends - organizational culture, company stage, team setup, the nature of your product... All these factors play a role in selecting the right format for your roadmap. Every product roadmap should consist of three foundational elements: When - the horizontal axis on a roadmap that indicates the timeline of your initiatives. These might be actual dates (months, quarters or something else) - or Now, Next, Later * What - the core items on your roadmap that represent what you will be working on. These might be features, problems, outcomes, or other initiatives. Categories - use categories to group initiatives on a roadmap. * A Notes on Now, Next, Later The Now-Next-Later roadmap was invented by Janna Bastow, co-founder of Mind the Product. The idea is to remove the false certainty of absolute dates by replacing them with relative timeframes: - What are we working on now? - What will we start next? - What are we saving for the future? A Now-Next-Later roadmap can help your organization escape the certainty trap. Instead of wasting time discussing when things will be done, it forces a discussion on what is more important.
To view or add a comment, sign in
-
Building the right product takes a lot. . . . . . . 1. Putting efforts into thinking about what to do, when to do and how to do it. 2. Being creative to make it usable. 3. Making it scalable for the future to avoid effort in future. 4. Cutting down creativity to get it out on time. 5. Finding the right people to get your vision executed. 6. Clearing hurdles for your team along the way. 7. Keeping yourself sane while telling stakeholders what you did and why you did it. People say if you do it in a structured manner, you'll do it in a better way. I don't buy it. Every person and feature has its journey based on constraints, conditions etc. You have to figure out your way! #product #productmanagement #business
To view or add a comment, sign in
-
Exploring the art of prioritization with Value vs. Complexity frameworks! 🎯✨ In the dynamic world of product development, deciding what to build next can be daunting. Here’s how a #Value vs. #Complexity framework elevates our decision-making: #Assess #Value: What impact does this feature have on our users and business goals? 🔍💡 #Evaluate #Complexity: What resources, time, and effort are required to implement this? 🛠️⏳ #Find #Balance: Seek opportunities that offer high value with manageable complexity. ⚖️🚀 This method enables us to prioritize features that deliver maximum benefits with optimal use of resources. Let's build smart, not hard! #PrioritizationFrameworks #ProductManagement #ValueVsComplexity #SmartDecisions #EfficiencyInAction #Innovation #UserCentric #TeamworkMakesTheDreamWork #BuildBetter
To view or add a comment, sign in
-
What are the biggest challenges of product development? * Coming up with new ideas? * Testing new ideas? * Successfully executing a new idea? * Defining requirements & specifications? * Completing a project on time and on budget? * Knowing what the customer wants? * Overcoming the "unknown" challenges along the way? What are your biggest challenges in product development? I would love to hear your thoughts on the comments below. #innovation #design #productdevelopment #engineering #leadership #communication
To view or add a comment, sign in
-
The First Fully Baked Versions Of Your Product Determine Rate Of Success In the world of product development, we all start with a Minimum Viable Product (MVP). However, the approach you take from the beginning sets the tone for your overall success. This initial "style" of development is hard to change once established. Consider this: once your product is fully baked, it becomes extremely difficult to make significant changes. At that point, you'll likely be out of R&D money, making your initial scoping and design exercises crucially important. Instead of focusing solely on end-user processes, think about your platform holistically. This broader perspective will give you the flexibility to build new services and adapt to future needs. In essence, the way you approach product development is more important than you might think. Creating a feature-rich product isn't the key differentiator—your strategic approach and flexibility are. #ProductDevelopment #MVP #Innovation #R&D #BusinessStrategy
To view or add a comment, sign in
-
Here's your Blueprint to developing new products! Building a new product at your workplace? Don’t let the process overwhelm you. Here’s a distilled blueprint from my own experiences, ensuring your next offering is not just good, but great. 1️⃣ Identify the Gap: Start with the market, not the product. What’s missing? Listen to your customers' unmet needs. 2️⃣ Concept Validation: Before diving deep, validate. Talk to potential users. Are they excited? Would they pay? If not, pivot early. 3️⃣ Design with Empathy: Every feature, every line of code, should solve a real problem. Keep it simple, but significant. 4️⃣ Prototype and MVP: Get something tangible out there. It doesn’t have to be perfect. Early feedback is gold. 5️⃣ Iterative Development: Use the feedback. Improve, refine, and repeat. Agile is not just a buzzword; it’s a strategy. 6️⃣ Launch Plan: Start marketing early. Build anticipation. A great product with no audience is a tree falling in an empty forest. 7️⃣ Post-Launch Analysis: The launch isn't the end. Gather data, understand user behaviour, and prepare for the next cycle. Remember, success is not linear. Embrace the setbacks as stepping stones. I’ve seen too many promising products falter by skipping these steps. Your process might differ, but the principles? They’re universal. 🤔 Question for you: What’s one lesson you’ve learned in product development that you wish you knew earlier? #ProductDevelopment #Innovation #productgrams #productmanagement
To view or add a comment, sign in
-
Recently, I had the pleasure of attending a sip and paint session, and I decided to paint my favorite cartoon character, the Minions. While my artwork might not be perfect, it captures the essence of the Minions and brings a smile to my face every time I look at it. This experience reminded me of an important concept in product management: the Minimum Viable Product (MVP). In product management, developing an MVP is crucial. It’s about creating a product with just enough features to satisfy early customers and provide feedback for future development. Here’s why focusing on an MVP is essential: 1. Validation: An MVP helps validate your ideas and assumptions. By releasing a product early, you can quickly learn what works and what doesn’t. 2. Customer Feedback: Early adopters can provide invaluable feedback, helping you refine and improve your product. 3. Resource Efficiency: Developing an MVP allows you to test the market with minimal resources, saving time and money. 4. Agility: With an MVP, you can adapt and pivot based on real user data, ensuring your product evolves to meet customer needs. Just like my Minion painting, an MVP doesn’t have to be perfect—it just needs to work. It should embody the core value of your product and serve as a foundation for future improvements. Remember, the journey of product development is iterative. Embrace the imperfections, learn from them, and continue to build something amazing.
To view or add a comment, sign in
-
RICE, MoSCoW, HEART... There are countless product prioritization frameworks out there. But let's be honest, they are all flawed: - they don't fit your unique context - they require a lot of effort to implement - they only work for specific prioritization tasks What if there was a prioritization framework that avoided these pitfalls while keeping all the good practices? Introducing 𝘁𝗵𝗲 𝗣𝗿𝗼𝗱𝘂𝗰𝘁 𝗣𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘇𝗮𝘁𝗶𝗼𝗻 𝗙𝘂𝗻𝗻𝗲𝗹 🔻 The Funnel is an efficient way to filter all your product ideas and initiatives, allowing you to focus on what really matters and discard the rest. Simplicity is key—choosing from 10 options is far easier than from 100. The funnel filters in action: 🔍 𝗩𝗶𝘀𝗶𝗼𝗻/𝗦𝘁𝗿𝗮𝘁𝗲𝗴𝘆: Ditch what doesn't align. 🎯 𝗖𝘂𝗿𝗿𝗲𝗻𝘁 𝗚𝗼𝗮𝗹𝘀: Skip what's not driving your objectives. ⛓️ 𝗖𝗼𝗻𝘀𝘁𝗿𝗮𝗶𝗻𝘁𝘀: Cut out what's beyond your resources. 📊 𝗗𝗮𝘁𝗮: Follow the numbers that promise success. Leverage the Product Prioritization Funnel to turn prioritizing from a tedious task into a straightforward path to Product Success. Filter. Focus. Build. 🌟
To view or add a comment, sign in
26,132 followers