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?
Running a User Story Map workshop with your team will give you a comprehensive list of features prioritized by different releases ( you want to ocus on learning quickly ), and you will have common understanding among the different people involved. This is where Roman Pichler’s GO Product Roadmap comes in handy. Slice Out Releases.
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.
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.
Speaker: Eric Feinstein, Professional Services Manager, Looker
Eric Feinstein, Professional Services Manager at Looker, has done workshops with product managers who are looking to add effective reporting. He will discuss working through personas, data types, reporting needs analysis and ultimately how this comes together to form a roadmap for reporting functionality and interface.
How would you assess your own roadmapping process? A new book, Product Roadmaps Relaunched, could help you re-think and re-launch your approach to Product Roadmapping. The 11-chapters are a master class on product roadmapping, and is supported by 65+ interviews from real practitioners.
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 product roadmap, sometimes also referred to as theme-based. 2 Do the Necessary Prep Work.
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.
What Product Roadmaps Are (in a Nutshell). To start with, let’s briefly recap what a product roadmap 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 Dates Are Beneficial.
Successful product leaders use workshopping to develop strategy, roadmaps, and anything else where input and feedback are valuable. A workshop can set a group on a great path forward, but it can also suffer from tangential conversations, people who dont participate, or disrespectful behavior.
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.
Before you order the roadmap items, double-check that you have a validated product strategy in place. If you haven’t nailed the answers, then do not continue the roadmapping effort. Otherwise, your roadmap may be built on false assumptions. To prioritise the product roadmap, consider in which life cycle stage your product is.
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.
Organizing a workshop is also a kind of journey, and we're ready to share the roadmap with you. In the previous part of this article, we covered the preparatory phase of the customer journey mapping workshop, and now it's time to delve into the actual conduct of the session and what follows. [.]
Decision-making process for PMs: No common process, standardized No journey from OKRs to problems and solutions No articulation of the roadmap with uncertainty Not ahead of the needs Problems for making streamlined decisions, for articulating decisions. Mental models for decisions not clear. Team dynamics and structure.
In practical terms, involve stakeholders and dev teams in decisions that affect the product strategy and the product roadmap —be it that you create the plans or that you make bigger changes to them. Then invite the right people to a collaborative workshop, no matter if it takes place online or onsite. Lead by Example.
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.
For example, a product strategy workshop might have the objective to identify the key changes required to achieve product-market fit. As a rule of thumb, avoid meetings with more than ten attendees when you have to make high-impact decisions and/or rework the product strategy , product roadmap , or product backlog. 1 Set an Objective.
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.
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. Establish clear roles and responsibilities.
Product strategy workshops 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…
How do you collectively build your marketing persona through a workshop? Preparing for a Persona Workshop. Market research and having a customer proxy are prerequisites for a persona workshop. As well as product managers, stakeholders, marketing, sales, and dev representatives should attend a persona workshop.
Product Management Every feature, every roadmap decision, every investmenttied directly to user jobs that, when improved, create measurable benefits for the customer. No fluff, no filler, just impact. Don’t start with products, start with user jobs that most need improvement and product priority decisions will be a lot easier.
Learn How to Groom Value-Based Product Backlogs From a Single Strategic Roadmap. Atlanta, GA – Proficientz announced today that it will host a Strategic Portfolio RoadmappingWorkshop in Atlanta on September 5th, 2019. The workshop will take place at Serendipity Labs in Alpharetta, GA and begin at 8:30 a.m.
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 product strategy and a product roadmap that are based on the vision. Visioning Workshop Attendees. Encourage the participants to describe the purpose that they associate with the product.
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? The post Carbon Neutral Roadmaps – Chris Adams on The Product Experience appeared first on Mind the Product. Emily Cunningham. And some honorary Emilys: Maddie Stone.
Hard skills like market research or roadmapping are important, but they’re not enough. A collaborative workshop with key stakeholders is a great way to kick off a new product development effort and create the initial vision. Hard skills like market research or roadmapping are important, but they’re not enough.
Design workshops, like persona, jobs-to-be-done or customer journey workshops can help the team to get a better understanding of customer’s pains and needs. These workshops are fun, and they are also useful to align the team and get everyone on the same page. Designers will also ask for feedback frequently.
To prevent your product backlog from becoming a wish list, follow these two tips: First, select a product goal and align your product with a strategic plan like a product roadmap (as I discuss below). Collaborative Product Backlog Workshop. Product Roadmap, Product Backlog, and Product Goal. Second, have the courage to say no.
He is president of Voltage Control, an Austin-based workshop agency that specializes in Design Sprints and innovation workshops and formerly worked with Google Ventures. You might do a workshop beforehand with all the people you’re interested in, and then choose who will be in the Design Sprint. Innovation Quote.
Previously, Bruce joined us for a three-part series on creating and using product roadmaps. He is the co-author of the book Product Roadmaps Relaunched: How to Set Direction While Embracing Uncertainty. 7:13] How did you move from focusing on roadmaps to focusing on stakeholder management? The goal is alignment of the team.
And just like I encourage trios to share their discovery context before they share their roadmaps and backlogs, I’ll do the same here, before I talk about my plans for the year ahead. To address this opportunity, we launched our two-day Continuous Discovery Habits workshop. My personal roadmap looks like this: Now.
What’s more, the decisions captured in the product strategy are crucial to achieve product success: I view them as prerequisites for deriving an actionable product roadmap with specific, measurable product goals or outcomes that direct the development of the product. Contrast this with the product strategy and the product roadmap.
When No-one Agrees With Your Roadmap. What do you need as a product person looking to get a roadmap updated or in place? You don’t need consensus to get your roadmap in place. Let’s clarify (and repeat) that: You do not need consensus to get your roadmap in place, nor do you need it to edit your roadmap.
And finally, Tali was so convinced of the power of opportunity solution trees that she started leading workshops at product events to teach others how to use this tool. Tweet This After trying it out herself, Tali conducted a series of workshops with her dev team, explaining the basic concepts and then filling out the tree together. “It
On this episode of Intercom on Product myself and Paul Adams, our SVP of Product, take a look at roadmapping. Knowing how and when to define a roadmap, who to include and how long to plan for are key elements to finding the balanced approach that you need. As you grow functions, the audience for your roadmap widens.
On this episode of Intercom on Product myself and Paul Adams, our SVP of Product, take a look at roadmapping. Knowing how and when to define a roadmap, who to include and how long to plan for are key elements to finding the balanced approach that you need. As you grow functions, the audience for your roadmap widens.
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 ).
Product people descended upon central London this morning for a series of Mind the Product training workshops , kicking off #mtpcon ahead of tomorrow’s conference. From the 14 workshops there was plenty to take away. If you missed today’s #mtpcon workshops, fear not! It can be very frustrating.”
You use an outcome-based product roadmap and/or an opportunity solution tree , personas , user journey maps, and the product backlog to capture and validate your decisions and guide the product delivery effort. You should therefore involve them in creating and updating the plans, preferably in the form of collaborative workshops.”
Instead of creating, for example, product strategies and roadmaps and tracking KPIs , you should help the people on your team acquire the right knowledge and develop the right skills so that they can carry out the relevant work on their own. Developing a product roadmap and setting realistic product goals/outcomes.
Imagine that John is a sales rep and a key stakeholder who hardly ever attends the product strategy workshops you’ve invited him to. Instead, he requests product roadmap changes by talking directly to you. The opposite is true: You can empathically address unhelpful and inappropriate behaviour, as the following example shows.
Product marketing roadmaps aren’t a staple in most B2B organizations, but there are a host of reasons they should be. What is a Product Marketing Roadmap? The execution part of the product marketing roadmap consists of the action items and artifacts required to generate demand and support the sales process.
This includes securing the necessary training budget and selecting the right training courses, as well as creating a training-on-the-job program, attending product strategy workshops as a stakeholder , and acting as a sparring partner for strategy-related questions.
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