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? 1] But wouldnt it make sense to harmonise not only the product strategies but also align the product roadmaps? This is where product portfolio roadmaps come in. [2] How Can You Capture a Portfolio Roadmap?
Recently I found myself on the Product Management Meets Pop Culture podcast. Tafifi, The Living Roadmap. Check it out: Download file | Play in new window | Duration: 19:31. Show Notes For This Episode. Episode Sponsor: Audible. Linked In: Jeremy Horn. Twitter: @theproductguy. The Product Guy Blog.
This post is about making these ideas concrete through a set of guidelines, templates, and JIRA+Excel tips so you can create effective status and progress reports quickly, have less meetings , and get out of the building , which is where you need to be. Templates and tips for less status meetings. Progress / Status.
Overview of the Learning Roadmap. Like a modern product roadmap, 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 Product Roadmap 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. Single : Choose a single goal to effectively align and guide people.
The key results state the specific criteria that have to be fulfilled to meet the objective. What are Product Roadmaps? A product roadmap 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.
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. Understanding the client needs and drawing the bigger picture from these needs is essential when planning out a roadmap.
1 The Product Roadmap is a Feature-based Plan. Traditional product roadmaps 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. 2 Roadmap Goals are Features in Disguise.
Speaker: Edie Kirkman - VP, Digital at Focus Brands
Learning Objectives Learn how to gather and utilize data to enhance the user experience and optimize development effectiveness Discover techniques to partner with customers and technology to validate assumptions and uncover new use cases, minimizing the risk of developing products that do not meet user needs Understand how to build leading and lagging (..)
Product Roadmapping Once product positioning is established, product managers move into the more action-oriented activity of roadmapping. This planning phase requires careful consideration of multiple contextual factors that significantly impact how roadmaps should be developed and managed.
Once you and your team have a clear understanding of why this product is worth pursuing, as well as some solution ideas, it’s time to think about the specific features that the product should have to meet its objectives and bring its intended impact. This is where Roman Pichler’s GO Product Roadmap comes in handy. Feature Definition.
Thank you to everyone who attended the latest roundtable meet-up of The Product Group and discussed Product Roadmaps for Good and debated Featured Product, ADP… And, also, thank you to our awesome sponsors who make everything possible…
Be clear on the reason why the meeting is needed. What’s the meeting about? Contrast this with a sprint review meeting , which might help you determine if users can easily sign up for the product. Carefully consider who should participate in the meeting to achieve the objective you have set. 1 Set an Objective.
Speaker: Johanna Rothman, Management Consultant, Rothman Consulting Group
Do your roadmaps read like impossible wish lists? It may seem impossible now, but what if we said that with a few changes, you could be meeting deadlines with the ability to predict progress with accuracy, be happy with your progress against the roadmap, and be making time for near-continuous discovery? Well, you’re not alone.
Roadmaps are altered by user feedback, new strategies and changing client needs. Help your team adapt and keep clients aligned with these documents, meetings, and conversations. In a recent live stream from one of our mentors of The Product Mentor , Andrew Hsu, lead a conversation on this topic.
Traditionally, product roadmaps 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. This makes the product roadmap more susceptible to change and it increases the effort to update it.
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 product roadmap. A traditional roadmap is essentially a list of features, which are mapped onto a timeline.
The key to understanding your customers lies in meeting them where they are. Here are five tips to reassess your digital experience, meet customers where they are, and turn the channel into an actionable listening tool. Listen to your customers wants and needs, then build solutions to meet those desires.
Question: How do you respond to requests for date-based roadmaps? To provide a bit more context, one CDH community member was being drawn into theoretical debates about date-based roadmaps. First, I’d like to address some of the shortcomings of date-based roadmaps. At best, creating a date-based roadmap is a waste of time.
Listen to the audio version of this article: [link] You Can’t See Further than the Next Three Months A product roadmap 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 product roadmap.
The individuals whose buy-in to strategy and roadmap decisions is crucial are the players: They are interested in your product, as they, for example, will have to market and sell it. Smaller strategy updates and product roadmapping decisions, however, are not as critical. I refer to this group as key stakeholders.
You’re Stuckand It’s Because You’re Playing by the Rules In product management, youve been told to follow the rules: stick to the roadmap, build consensus, and hit your OKRs. As can be easily found in many organizations: Roadmaps trap you in outdated plans. Rule 1: Trust the RoadmapRoadmaps are your comfort zone.
Meet Brian Fugere , a pro whos navigated the high-stakes terrain of M&A more times than he can count. Technology Roadmap Figure out the dev stack, the product backlog tools (Jira vs. Aha?), She standardized everythingno more 14 different ways to build a roadmap. and how quickly you can merge them with your current methods.
In our latest Productside webinar, Becoming an Effective Product Management Leader , Principal Consultants Roger Snyder and Kenny Kranseler delivered a no-nonsense roadmap for new leaders who want to nail their first 90 days (and beyond) and get the tools on how to become a product management leadereffectively. The principle stays the same.
Pro Tip from Aarti Iyengar : Focus on outcome-driven roadmap planning. Meet the Roundtable Experts We were joined by two outstanding product leaders: Aarti Iyengar , Sr. Here’s what you can do today: Prioritize Outcome-Driven Thinking : Reassess your roadmap to ensure it focuses on outcomes rather than just deliverables.
Your team is following the roadmap. Roadmaps provide alignment. But heres the problem: The world doesnt care about your roadmap. Teams are trained to treat roadmaps as gospel, OKRs as strategic truth, and customers as the ultimate source of insight. You shipped everything on the roadmap, but customers werent delighted.
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. In order to determine the right product goal, I asked myself, “What would be a first good step to meet the from the user and business goal?”
In product management, one of the most complained about occurrences is that of MEETINGS — viewed as time-consuming, unnecessary, or simply ineffective. However, when designed and executed well, meetings can be highly beneficial and essential for driving alignment, fostering collaboration, and making complex decisions.
In agreeing our framework, we realised that we had been placing too much bias on ‘Market Fit’ in our meetings, and had neglected ‘Product Fit’. I also re-framed the alignment meetings as “Roadmap” meetings, not “Prioritisation” meetings. Finally, share the roadmap far, and share it wide.
These interactions weren’t just about immediate product needs – they focused on building long-term partnerships and ensuring customers saw value in the product vision and roadmap. However, she still needed to learn the company’s products, technology, and internal language.
Meet Ellen Brandenberger , a product coach and consultant and Director of Product at Stack Overflow. Meet Ellen Brandenberger, a product coach and consultant and Director of Product at Stack Overflow. Meet new Product Talk instructor Ellen Brandenberger! to the roster. Tell us a bit about your background.
The path and the steps to reach the destination is defined through a product roadmap. Hence roadmapping is a crucial exercise which can make or break your product. In my opinion, apart from a bad culture, a bad roadmap can also have a devastating impact on your organizational strategy. Product Roadmap. Data vs Intuition.
But instead of telling a clear, compelling story, they send out a spec or share a roadmap deckand hope it gets read. Tom put it this way: A storyboard is worth a thousand meetings. PMs are often tasked with aligning stakeholders, guiding engineering teams, and championing the customer. And if it isnt understood, it wont get built.
It’s a model of an iterative process that systematically links the product strategy with the product roadmap , the product backlog , the development work, and the key performance indicators (KPIs). With an actionable product roadmap in place, move on and stock your product backlog.
We’re there from start to finish – from the early stages of development to roadmap strategy, launching to market and beyond. And as we’ve matured and begun to cater to new segments, a wider range of use cases, and upmarket customers, product marketing’s role has evolved and expanded.
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 product strategy and an actionable product roadmap (as I explain in more detail in the article The T-Shaped Product Professional ).
Photo by AP Vibes Outcome-based roadmaps are considered the best practice; however, they are not as common as you would expect. The promise that we made was that by the first version, any listing that sells a product that meets certain criteria would be tagged with the right product from the new catalog.
One of the primary goals of any business strategy is to identify and meet needs of the customer. Defining target customer base helps with creating the roadmap. Knowing specifically what customer want, helps companies to build and deliver the precise solutions that meet customer needs. About Madhavi Marka.
I like to take this idea further, derive several product goals from the product strategy for the next 12 months, and capture them on a product roadmap. If you have a product roadmap, then ensure that it implements the overall product strategy. Do not add too much detail to your product roadmap , though, to keep it a high-level plan.
As I’ve often shared, a not-so-distant coffee meeting led me down a path I never would have guessed. It forced me to question a belief, as a product leader, I treated as an absolute — that products always require roadmaps. Do you think every company and product needs a roadmap?” Roadmaps are not always needed. I answered.
Identify needs that are not yet met and use this to inform your product roadmap. Get validation of your priorities by asking members how they feel about your roadmap and it’s prioritization. Arrange the meeting : Agree on a shared date and time each x weeks for the meeting. New Idea Generation. Prioritization.
Using a product goal addresses this issue: You only add an item to the backlog if it helps you meet the goal. Third, product goals help you connect the product roadmap and the product backlog , assuming that you use a goal-oriented plan like my GO product roadmap. Otherwise, you discard it, at least for now.
How does it differ from a product roadmap and how do the two plans relate? At the heart of the model in figure 1 are four artefacts: the product vision, the product strategy, the product roadmap, and the product backlog. With a validated strategy in place, you are in a great position to build an actionable product 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