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
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]
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.
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.
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).
Whenever you are faced with an agile, dynamic environment—be it that your product is young and is experiencing significant change or that the market is dynamic with new competitors or technologies introducing change, you should work with a goal-oriented productroadmap, sometimes also referred to as theme-based.
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.
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.
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.
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.
Productstrategyworkshops are facilitated sessions where key stakeholders come together to define the vision, goals, and roadmap for a product. The workshops help align the team on strategic…
Hold Regular ProductStrategy Reviews. A productstrategy , like any other plan, is subject to change. How changeable your strategy is, depends on your product’s life cycle stage. As long as your product hasn’t reached product-market fit, the strategy is usually volatile.
In practical terms, involve stakeholders and dev teams in decisions that affect the productstrategy and the productroadmap —be it that you create the plans or that you make bigger changes to them. Additionally, include the development team members in product backlog decisions , and always choose sprint goals together.
For example, a productstrategyworkshop might have the objective to identify the key changes required to achieve product-market fit. Contrast this with a sprint review meeting , which might help you determine if users can easily sign up for the product. Assess productstrategy and adjust if necessary.
To build such a stakeholder community, try the following techniques, which I discuss in more detail in my book How to Lead in Product Management : Bring people together and have joint workshops instead of holding separate conversations with the individual stakeholders, see also the section below.
If that’s not the case, then it will be difficult to encourage the individuals to agree to more specific goals and to follow a productstrategy and a productroadmap that are based on the vision. Encourage the participants to describe the purpose that they associate with the product.
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?
Product (and company) strategy is the backbone that guides product goal-setting and roadmap definition, although it’s sometimes overlooked or confused with having a vision. Without it, product teams become feature teams focused on outputs and not outcomes. It is the guiding principle for OKRs and roadmaps.
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).
For example, ensure that the individual product people are sufficiently empowered to succeed in their roles and establish a product-led way of working. What Happens When the Head of Product Determines the ProductStrategy? As you might have noticed, the list above does not mention determining the productstrategy.
Listen to the audio version of this article: [link] Introduction To discuss empowerment in product management, I find it helpful to distinguish three main levels of decision-making authority, product delivery, product discovery, and productstrategy, as the model in Figure 1 shows. [1]
This includes a sound understanding of the market, the user and customer needs, and the competition as well as solid product management skills such as the ability to develop an effective productstrategy and an actionable productroadmap (as I explain in more detail in the article The T-Shaped Product Professional ).
Consequently, your focus shifts from managing a product to looking after the product people on your team and empowering them to do a great job. For instance, you might show the individuals how they can make effective strategic product decisions, create an actionable productroadmap, and effectively use the right KPIs.
Emily Tulloh – and the overview on Workshop on Service design in a climate emergency – What do digital services in a world of net-zero look like? Use the #podcast channel in the Mind the Product Slack community. Emily Cunningham. Emily Atkin (featured on the What Next podcast on 15 Jan 2020 ). Suggest a guest to us here.
To select the right KPIs, I recommend taking the following three steps: First, use the user and business goals in the productstrategy to select an initial set of indicators. Then take into account the product goals on the productroadmap to discover additional KPIs.
At all of them, I start understanding the current state of Product Management. I then do various interviews with executives all the way to Product Management team members and surrounding functions. I review strategies and roadmaps. This is one of the biggest issues I see when helping Product Management organizations.
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.
We’re thrilled to announce the first of our amazing line-up of speakers and announce all our deep-dive workshops, connecting international and regional thought leaders with the vibrant product and UX community across AsiaPac. Sherif thinks building simple products is hard and so is writing a simple, short bio.
Imagine that John is a sales rep and a key stakeholder who hardly ever attends the productstrategyworkshops you’ve invited him to. Instead, he requests productroadmap changes by talking directly to you. At the same time, be frank.
Indeed the role of a product leader is different to that of a product manager. A product leader not only has to manage products but also to guide and direct the overall productstrategy and team, and ensure that products are delivered to market.
A UX workshop can help you gather the team and brainstorm to make better decisions. Ensure everybody is on the same page by making them more involved in the product development process with these tools. In a UX workshop, we share research results with the participants and let them come up with their own conclusions. Preparation.
My first MVP had little resemblance with the finished product: I used my productstrategy and roadmapworkshop as the initial minimum viable product. This helped me better understand which strategy and roadmap-related challenges product managers commonly experience and which advice is helpful for them.
Here’s the easiest way to marry company strategy and productstrategy. – Grow into adjacent markets with existing products. The Downside of Multiple ProductStrategies Here’s the first thing you SHOULD NOT DO. They’re often conflated. Financial goals are just that. – Retain our best employees.
Organisational change and empowerment : Work with senior management, HR, and other business groups to implement the necessary organisational changes required to fully empower product people and leverage agile practises. Having an effective Scrum Master allows you to focus on your job—to maximise the value the product create.
STEP 3 Assuming product management uses its collective market knowledge to craft portfolio/productstrategies, roadmaps, plans, priorities, backlogs, etc., The skids are greased for stakeholder alignment and it will happen more naturally than it would otherwise.
Before the advent of agile frameworks like Scrum , a product person—the product manager—would typically carry out the market research, compile a market requirements specification, create a business case, put together productroadmap, write a requirements specification, and then hand it off to a project manager.
So either we work together to understand your objectives, call them goals if you’d like, and the outcome you are looking for from the product, or we will end the discussion, and you won’t get a committed set of work on the roadmap.” We went away from detailed, long-term, feature-committed roadmaps. I explained this many times.
Each release goal should be a step towards meeting the user and business goals, and it should describe the specific benefits a major release or product version will provide, for example, acquire users , increase engagement , generate revenue , or remove technical debt to future-proof the product.
While the three roles exercise different leadership, the people involved must effectively collaborate to achieve product success and align productstrategy, roadmap, backlog, design and technology, and process decisions—without losing focus of their respective core responsibility. [1]. Lead the Product.
Teresa: One of the things I think I’ve written in the past is if your backlog or your roadmap or your idea log—whatever you’re going to call it—isn’t changing based on what you’re learning in discovery , there’s a disconnect there. You had five product teams , a user researcher who was new to the role.
You might talk to the sales rep, for example, and ask them about the viability of using existing sales channels or get their feedback on a draft productroadmap. You’ll then repeat the process with the other stakeholders until you have acquired enough information or managed to create a roadmap everybody accepts.
Companies with an existing product management group usually require up-skilling and retraining their product people, as well as adjusting roles and responsibilities and career plans. These range from establishing a product culture to empowering the product people, giving the necessary decision-making authority.
In practical terms, involve stakeholders and dev teams in decisions that affect the productstrategy and the productroadmap —be it that you create the plans or that you make bigger changes to them. Additionally, include the development team members in product backlog decisions , and always choose sprint goals together.
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