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? In both instances, Id recommend using an overall portfolio or bundle strategy in addition to the individual product strategies. This is where product portfolio roadmaps come in. [2] How Can You Capture a Portfolio Roadmap?
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 product strategy and one or more development teams might be tasked with executing it. Enter the Cycle. I call these outcomes product goals.
You have to work with different stakeholders to define the product vision and strategy, define the set of features that the product will have and figure out a rollout plan. Define Product Vision and Strategy. You should think about including designers, developers, and even potential users to this workshop to encourage collaboration.
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: 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.
An effective product strategy 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 product strategy is missing. But what exactly is a product strategy? How does it differ from a product roadmap and how do the two plans relate?
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. Decisions related to a new or significantly changed strategy have a very high impact. I refer to this group as key stakeholders.
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.
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.
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. Before You Start Prioritising …. Create a Compelling Narrative.
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.
Product strategyworkshops 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…
Listen to the audio version of this article: [link] 1 No Strategy The first and most crucial mistake is to have no product strategy at all. As there is no strategy, objectively assessing the impact of the requests is virtually impossible. The strategy is therefore either too big or too narrow.
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.
It is overwhelming when you get into hyper-growth mode, and it requires process and strategy to continue the success and growth. glidr) Sharing related articles Set up a Product Discovery Board (see Decision-making framework and Thematic Roadmap below). Mental models for decisions not clear. Team dynamics and structure.
For example, a product strategyworkshop 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.
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.
Hold Regular Product Strategy Reviews. A product strategy , 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.
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. A solution-agnostic vision allows you to change the product strategy but keep your vision stable.
Portfolio Strategy Forget every product team working in their own little silo. A portfolio strategy starts with the customers top business priorities, and then every product becomes a lever for delivering value that actually moves the needle for them. No fluff, no filler, just impact. Otherwise, FAHGETTABOUDIT!
This allows you to pivot, to change the product strategy and the product while staying grounded in your vision. Additionally, I like to capture the product vision together with the product strategy, as it’s done on my product vision board shown below. Do I need a Product Vision and a Product Strategy?
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.
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.
What Happens When the Head of Product Determines the Product Strategy? As you might have noticed, the list above does not mention determining the product strategy. Here is why: When a head of product determines the product strategy on a regular basis, then this is likely to cause the following two issues.
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 ).
Our goal was to define how we would set and communicate the company strategy, and how that strategy would lead OKRs and backlog definition. 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.
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 product strategy, as the model in Figure 1 shows. [1]
I recently led a workshop for an organic tech farm startup that wanted to set its foot online for selling organic food to B2B customers. I have some takeaways and learnings to share that I covered as a coach for their onboarding strategy. Let me walk through the entire workshop in the phases with its results.
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. The also need to understand the team dynamics, past work, and corporate strategy. Our guest knows how to help. 3:45] What is a Design Sprint? Innovation Quote.
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. Creating and validating a product strategy including market and user research.
To select the right KPIs, I recommend taking the following three steps: First, use the user and business goals in the product strategy to select an initial set of indicators. Then take into account the product goals on the product roadmap to discover additional KPIs. Step 1: Take Advantage of the Product’s User and Business Goals.
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.
Imagine that John is a sales rep and a key stakeholder who hardly ever attends the product strategyworkshops you’ve invited him to. Instead, he requests product roadmap changes by talking directly to you. At the same time, be frank. But this does not only reduce your ability to understand and connect with the individual.
I look at four dimensions for robust Product Organizations: Product Organizational Design Product Strategy Product Operations Product Culture Inside each of these are a few capabilities that are then broken down further into sub-capabilities that help me pinpoint where the issues are. I review strategies and roadmaps.
Strategic Portfolio RoadmappingWorkshop. In this hands-on workshop, you’ll learn how to develop a strategic portfolio roadmap that drives new growth by shifting your inside-out product vision to an outside-in customer vision. This workshop is ideal if…. This workshop is ideal if…. Course Takeaways.
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. Workshop Presenters. by Jonny Schneider, Head of Product Strategy and Design. Find out more!
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. My key learnings from the workshop were three things. Stephanie: Exactly.
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 product roadmap, write a requirements specification, and then hand it off to a project manager.
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.
Here’s the easiest way to marry company strategy and product strategy. The Downside of Multiple Product Strategies Here’s the first thing you SHOULD NOT DO. Don’t dispatch each product team to come up with a strategy that supports your company’s goals. They’re often conflated. Financial goals are just that. Impossible!
A UX workshop can help you gather the team and brainstorm to make better decisions. In a UX workshop, we share research results with the participants and let them come up with their own conclusions. Get everybody on the same page with a UX workshop. Persona workshop. A canvas is often a good tool to run a UX workshop.
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