This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Traditionally, strategy and execution are often viewed as separate, sequential pieces of work that are carried out by different people. For example, a product manager might determine the productstrategy and one or more development teams might be tasked with executing it. I call these outcomes product goals.
An effective productstrategy is key to successfully create, enhance, and manage a product. There is no point in worrying about the product details and writing user stories if a sound productstrategy is missing. But what exactly is a productstrategy? Figure 1: My ProductStrategy Model.
2] Figure 1: The Power-Interest Grid The grid divides stakeholders into four groups: crowd, subjects, context setters, and players depending on how interested they are in your product and how much power they have. Smaller strategy updates and productroadmapping decisions, however, are not as critical.
What are ProductRoadmaps? A productroadmap is an actionable plan that describes how a product is likely to evolve. [3] Fortunately, in the last ten years, outcome-based, goal-oriented roadmaps have become more popular. Let’s take a quick look at the roadmap’s five elements. 5] So What?
Speaker: Johanna Rothman - Management Consultant, Rothman Consulting Group
Senior leaders often want to see months - or years - long productroadmaps. But these predictions often do not create products your customers will love. That means product leaders need to integrate experiments and options into their roadmaps.
1 The ProductRoadmap is a Feature-based Plan. Traditional productroadmaps are usually output-focussed plans that map a list of features, like registration, search, and reporting, onto a timeline. Such a roadmap essentially states when a piece of functionality will be delivered. I don’t think so.
Listen to the audio version of this article: [link] What Information Should a ProductStrategy Provide? I like to think of the productstrategy as a high-level plan that helps you realise your vision and that answers the following four questions: Who is the product for? Do You Need a Strategy for Your Product?
Overview of the Learning Roadmap. Like a modern productroadmap, a learning roadmap states the specific outcomes or benefits you’d like to achieve to become a more competent product person, and it captures them in form of learning goals. To make these ideas more concrete, let’s look at a sample learning roadmap.
Listen to the audio version of this article: [link] Overview The GO ProductRoadmap consists of five elements, as the image below shows: Date, name, goal, features, and metrics. The checklist I’ve created offers criteria for each element as well as the entire roadmap. Do not state any product details such as user stories.
Speaker: William Haas Evans - Principal Consultant, Product Strategy Practice Lead, Kuroshio Consulting
In this webinar, we’ll explore the 4 key pillars that a value-driven product organization leverages to ensure they are connecting their strategy to execution to deliver business outcomes: The ProductRoadmap (What it is and what it’s not). Use Product Management Today’s webinars to earn professional development hours!
There are many issues with having clients drive the roadmap. Secondly, waiting for clients to drive the roadmap tends to puts companies in a situation where the backlog becomes too large to practically handle. Is there some niche that your product could fill and get ahead with in the market? Step 3: Creating the Roadmap.
Traditionally, productroadmaps are output-focussed plans that map features like registration, search, and reporting onto a timeline. Such a roadmap essentially states when a piece of functionality will be delivered. Second, it overlaps with the product backlog, especially when detailed features are used. Outcome-based).
A four-layer framework to create a winning productstrategy Today we are talking about creating productstrategy. Bob is the author of the book Creative Strategy Generation. I first heard of Bob when he was the president of Sequent Learning, the product management training company. Our guest is Bob Caporale.
Listen to the audio version of this article: [link] You Can’t See Further than the Next Three Months A productroadmap should be a realistic forecast that states the specific value a product is likely to offer in the next 12 months. [1] If you can’t see further than the next three months, then do not use a productroadmap.
Product managers and community managers share a common goal: to deliver value to their users. Through in-depth user insights, a clear productstrategy, and an inspiring roadmap. Building products is a team sport and involves everyone working together to get the right products to market faster.
What ProductRoadmaps Are (in a Nutshell). To start with, let’s briefly recap what a productroadmap is. I view a roadmap as a high-level plan that states specific benefits a product should provide over a certain timeframe, which may range from six to 12 months. Ensure the Roadmap is Realistic.
Why a ProductStrategy Process Matters. An effective productstrategy process should ensure that a valid productstrategy and an actionable productroadmap are always available—that a shared and valid approach to achieving product success is available at anytime, as the picture below illustrates.
Listen to the audio version of this article: [link] 1 No Strategy The first and most crucial mistake is to have no productstrategy at all. When that’s the case, a product is usually progressed based on the features requested by the users and stakeholders. The strategy is therefore either too big or too narrow.
Before you order the roadmap items, double-check that you have a validated productstrategy in place. You should be able to confidently say why users would want to use your product and why it is worthwhile for your company to invest in it. If you haven’t nailed the answers, then do not continue the roadmapping effort.
We'll explore the concepts of products and services as revenue generators or revenue suckers, and delve into how to share cost and benefit dollars within a portfolio or business unit. You'll learn how to set clear, measurable targets, link them to your productstrategy, and effectively communicate progress with stakeholders.
Listen to the audio version of this article: [link] Traditional vs Outcome-based Roadmaps Before I share the four steps, let me briefly describe the main differences between a traditional, feature- and an outcome-based productroadmap. A traditional roadmap is essentially a list of features, which are mapped onto a timeline.
A process for improving productroadmapping using Objectives and Key Results – for product managers. Today we are talking about roadmaps. Some product people love roadmaps, while a lot hate them. Summary of some concepts discussed for product managers. [2:11] What can make them better?
Listen to the audio version of this article: [link] What is a Portfolio Roadmap and Do You Need One? Neither is a singular atomic product. Microsoft 365 is a product portfolio, a suite that contains productivity tools like Word, PowerPoint, and Excel. This is where product portfolio roadmaps come in. [2]
Listen to the audio version of this article: [link] A ProductStrategy System The productstrategy system in Figure 1 consists of four main parts: people, processes, principles, and tools. Having said this, the system in Figure 1 captures the specific productstrategy approach Ive created. [1]
Speaker: Christian Bonilla, VP of Product Management at UserTesting
Join Christian Bonilla, VP of Product at UserTesting, as he reveals tips for taking ownership of the product vision to guide the development process. In this webinar, you’ll learn: Steps to creating a product vision that leads to better outcomes. How to position your vision as an umbrella for the productstrategy.
Developing your productstrategy and communicating your productroadmap is a continual improvement process. The post 4 Ways to Level-up your ProductStrategy appeared first on Mind the Product.
Welcome to “POV: Product Oriented Voices,” where we tackle pressing questions in the tech world. In this episode, we explore whether Web3 is dead and what it means for productroadmaps. Despite the potential, regulatory challenges and the initial hype often lead to skepticism.
There are many moving parts to product success, including understanding your market and the problems customers in the market face, … Continue reading → Building software platforms and applications that customers love, and will recommend to their peers, takes extreme focus and hard work.
I believe the main culprits are Mr. Roadmap and Mr. Backlog. Culprit #1: Mr. Roadmap. How should we balance technical debt vs our feature roadmap? Well, th at’s the role of a productstrategy. My favorite definitions of strategy are the simplest I’ve found. A simple representation for our productstrategy.
Figure 2 contains a set of cascading goals: vision, user and business goals, product goals, and sprint goals. The vision guides the user and business goals, which are contained in the productstrategy. The user and business goals help select the right product goals, which I capture on the productroadmap.
Roadmaps don’t need to be complex, nor should you need a PhD to create one. Photo by Matt Duncan on Unsplash Ahh the dreaded word roadmap… The mere mention of a roadmap can divide the room, and send Product Managers into a world of panic. Let’s face it, roadmaps have a bad reputation.
It contains subsections with steps that one should go through while building products. ProductStrategy. As a first step, PM needs to define the strategy for the product. A well defined productstrategy provides insights into the deep customer problems that your product is trying to address.
Product leader Aatir Abdul Rauf outlines questions product managers should ask when crafting a productstrategy. By Tremis Skeete , for Product Coalition Productstrategy continues to be a misunderstood concept and energizes many conversations and debates on LinkedIn. It’s not a roadmap.
If it is not clear who the users are and why they would want to interact with the product, it will be hard to decide which items should be in the product backlog and how important they are. A tool like my product vision board helps you capture and validate your productstrategy.
In this talk from ProductTank London, Susana Lopes (Director of Product at Onfido), talks about how Onfido moved from prioritising at the sprint & quarterly level to setting strategic direction and prioritise at a much larger scale.
But this taught me an important lesson: There is no point in worrying about the product details if a sound productstrategy is missing. As helpful as a productstrategy is, it’s not enough. 1] While I hope that this makes sense to you, I find that in practice, the different strategies are sometimes confused.
In this digital breakout session sponsored by Indicative at #mtpcon London 2022, Esmeralda Martinez, Head of Product at Indicative by mParticle discussed placing bets and taking smart calculated risks on your productroadmap. [.]
Not tied to a solution : Despite its name, I recommend keeping the product vision free from assumptions about the actual product or solution. This allows you to pivot, to change the productstrategy and the product while staying grounded in your vision. Who Owns the Product Vision?
A solid productstrategy takes time to build. Here is the method I use for creating a productstrategy that makes sense. When I talk to the startups I consult to , or with the CPO Bootcamp participants, I always say that building a solid productstrategy isn’t like solving a math equation.
What’s more, I like to ensure that product goals are connected to the productstrategy and its user and business goals. This helps me choose the right product goals and it ensures that meeting a product goal is a step towards creating the desired value for the users and the business, as figure 1 shows.
It forced me to question a belief, as a product leader, I treated as an absolute — that products always require roadmaps. My mentor and I started in our usual spot, talking about startups and new products in the healthcare industry. Do you think every company and product needs a roadmap?” An hour flew by.
When creating your roadmap, you need to consider what’s important to the company (not just to the product) and what is the best way to make progress across these multiple needs. These are the exact questions you need to ask when creating your roadmap. In startups, it is actually the company roadmap.
If you thought there were a million ways to define product management, productstrategy might have it beat by a longshot. Just think about how many ways productstrategy is defined within your own organization. It’s the number one thing that makes productstrategy both challenging and frustrating at the same time.
Then, hearing the idea repeated — delete, delete, delete — I started to think about products in general and roadmaps specifically. Why do we leave in old features rather than trimming the product- holding onto them like that comfortably worn, cherished old sweater? A reverse roadmap. About the idea of a reverse roadmap?
We organize all of the trending information in your field so you don't have to. Join 96,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content