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]
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]
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.
The core focus of these activities is on thorough market research, continuous customer engagement, and strategic productdevelopment. We explored the 19 essential activities that define successful software product management today. Thorough market research in the problem space is fundamental to product success.
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.
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.
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.
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.
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?
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!
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.
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?
When I first joined, the startup I work at had often been stuck with a backlog of products and services to create. Our startup’s sales team is incredibly talented and sells successfully – but does not necessarily sell products that have already been developed. There are many issues with having clients drive the 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. Specific : Make the goal—a.k.a.
You'll learn how to set clear, measurable targets, link them to your productstrategy, and effectively communicate progress with stakeholders. 📅 September 25, 2024 at 11:00 am PT, 2:00 pm ET, 7:00 pm GMT Use Product Management Today’s webinars to earn professional development hours! Register now to save your seat!
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?
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.
The product manager’s journey from Individual Contributor to Chief Product Officer Watch on YouTube TLDR Kimberly Bloomston’s journey from individual contributor to Chief Product Officer at LiveRamp demonstrates the key transitions and skills needed at each level of product management leadership.
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.
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.
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).
“What is your ProductStrategy? YOU NEED A STRATEGY.” When I replay this scene in my head, I can hear the CTO very audibly yelling (slash pleading) with our product team. This is the way we were taught to think about ProductStrategy. This isn’t a strategy, this is a plan. He was on edge.
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.
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.
A development team does a good job if the following three conditions are fulfilled: First, the group reliably meets the agreed sprint goals and delivers product increments that offer a great user experience and exhibit the desired software quality. This can make it challenging to help a development team improve.
How first principles can help you design productroadmaps from the ground up. Productroadmaps are no exception. Creating or even updating a productroadmap can feel like being handed a blank sheet of paper and told you have 60 minutes to write a ten-page college essay on a topic you didn’t study for….
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.
In a recent live stream from one of our mentors of The Product Mentor , Chris Butler, lead a conversation around “Business Development vs. Product Management”. We are always looking for more product mentors from all around the world. About The Product Mentor. Signup to be a Mentor Today! View the live stream….
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?
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.
Goals in Product Management. As I explain in my book How to Lead in Product Management , setting the right goals is crucial to align stakeholders and development teams and to achieve product success. Does this mean that there is a natural fit between goals in product management and OKRs?
Hence it is critical that one is aware of the best practises of the role and develops his own philosophy which results into maximum positive leverage for the organization. As I strive towards becoming a product leader, I wanted to understand the best practises in product management and in the process develop my own product philosophy. .
But without clear priorities, the development team lacks direction, and there is only a slim chance of creating a successful product. A common root cause of not being able to prioritise a product backlog is a lack of understanding of who the users of the product are and what specific value it should create for them.
The rest of the product backlog emerges to define ‘what’ will fulfill the product goal.” The product owner is accountable for “developing and explicitly communicating the product goal.” The entire Scrum team is “focused on one … product goal” at a time. Product Goals and the ProductRoadmap.
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.
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?
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.
Listen to the audio version of this article: [link] Introduction My first product management job wasn’t exactly what you call a success story: I was part of a team that was called in to help with a new productdevelopment effort, and I ended up working with the lead product manager.
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 ).
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).
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. This will allow them to take full ownership of and responsibility for their products, and it will increase their motivation, productivity, and job satisfaction.
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