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
I view the roadmap as a product plan that describes how you intend to implement the strategy and which specific benefits or outcomes the product should provide over the next, say, 12 months, based on the needs and business goals stated in the product strategy. I call these outcomes productgoals.
You can avoid these drawbacks by using a different roadmap type: a goal-oriented or outcome-based product roadmap. As its name suggests, this roadmap focuses on productgoals and outcomes, such as acquiring customers, increasing engagement, and future-proofing the product by removing technical debt.
The roadmap in figure 1 describes how the product strategy will be implemented in the next six to twelve months; it communicates the specific benefits the product will achieve; and it aligns and guides the stakeholders and development teams. You can simply copy the next productgoal into the backlog together with its features.
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. Additionally, include the development team members in product backlog decisions , and always choose sprint goals together.
Third and most importantly, focus the backlog on a specific productgoal. Then decline and remove items that do not serve this goal, as I discuss below. The Product Backlog is Too Detailed. The former means that there is no productgoal that guides the decision if an item should be added to the product backlog or not.
To put it differently, meeting the productgoals must help achieve the portfolio objectives. As a consequence, a product roadmap is no longer exclusively directed by the corresponding product strategy. A question I often get asked in my workshops is, How detailed should a portfolio roadmap be?
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. We were so inspired by Tali’s enthusiasm that we just had to share her story here on the Product Talk blog. It was a great experience,” says Tali.
For example, a product strategy workshop 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. Listen to this article: [link]. 1 Set an Objective.
This means that nobody involved in the goal-setting process has any meaningful objections against the goal. A great way to engage the individuals is to invite them to a collaborative workshop, which may take place onsite or online. [4] This will help you make the right roadmapping decisions and generate strong buy-in.
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.
Figure 2: Roman’s Goal-Setting Framework with Product Management Artefacts The goal-setting framework shown in Figure 2 suggests that a product team needs four different objectives: a product vision, user and business goals, productgoals, and sprint goals. Let’s take a look at them.
I therefore recommend applying a different product roadmapping approach and using goal-oriented roadmaps , which are also called outcome-based. As their name suggests, these roadmaps focus on productgoals or outcomes such as acquiring customers , increasing engagement , and future-proofing the product by removing technical debt.
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 productgoals on the product roadmap to discover additional KPIs. Step 3: Add Health Indicators. Less is More.
This includes sprint planning , Daily Scrum , sprint review , and sprint retrospective , as well as product strategy and product roadmap workshops. Having an effective Scrum Master allows you to focus on your job—to maximise the value the product create. The same is true for setting productgoals.
Communication & Alignment Workshop. Using The Kano Model To Prioritize Product Development (blog). How to fix Your ProductGoals for Better Human Outcomes (blog). How to fix Your ProductGoals for Better Human Outcomes (blog). Product Management Foundations Workshop. Question 2. Question 4.
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 productgoals or outcomes that direct the development of the product.
While it is useful to ask what the Scrum Master should do, let's consider what the product owner can do. Work Tactics for Product Owners If you are a product owner, I'm going to assume you are overloaded. In that case, consider when you will: Work with the team, to workshop stories and plan the next bit of work.
Carrying out the relevant product discovery work and taking into account product ethics. Creating and validating a product strategy including market and user research. Developing a product roadmap and setting realistic productgoals/outcomes.
This detailed article will guide you through how we facilitate a UX project kick-off workshop here at UX studio. What happens at a project kick-off workshop? We hold kick-off workshops when a new project starts. You want to see progress, finally seeing your product go in the right direction. First, choose the goal.
Therefore, don’t turn it into a product backlog or roadmapping workshop. Similarly, if you require the help of the team to work on the product roadmap, then hold a separate workshop. Do you doubt the team’s ability to meet the sprint goal? Additionally, don’t forget to balance your various duties.
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. Additionally, include the development team members in product backlog decisions , and always choose sprint goals together.
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 productgoals on the product roadmap to discover additional KPIs. Step 3: Add Health Indicators. Less is More.
I therefore recommend applying a different product roadmapping approach and using goal-oriented roadmaps , which are also called outcome-based. As their name suggests, these roadmaps focus on productgoals or outcomes such as acquiring customers , increasing engagement , and future-proofing the product by removing technical debt.
I’m thrilled to be Master of Ceremonies for this year’s Leading the Product conference in Australia. As part of that, I’ll be offering one-day workshops on career ladders to product leadership: Melbourne , 16 October, What Do Product Leaders Do, and How Can I Become One? ( registration ).
What: Product Dojo conference on Mastering Product Leadership. When: December 4 th (workshops) and December 5 th (conference). I am joining the Product Dojo team for a combined workshop-plus-conference event in San Francisco. How is that the same/different from what individual product managers do?
She’d inherited a technical product where the engineers already had a view of the direction and deliverables required. During planning workshops the engineers were mentioning a lot of tools, methods, processes and concepts that were unfamiliar to her.
Product (and company) strategy is the backbone that guides productgoal-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. Defining the North Star: A Full-day Workshop.
Ideation sessions – individually or as teams, run workshops that remove the constraints and baggage specific to you and just look at the art of the possible. Get out of the normal environment, set an agenda that isn’t the day-to-day, employ some of the tactics below in this type of session to interrupt your mindset.
Despite expert communication, workshops, a corporate intranet, and a placemat for your desk, I was clueless. There was an enormous chasm between the company’s goals and my role in executing the strategy. If you decide to go north, you cannot go south at the same time.” So what exactly was I expected to do?
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 productgoals or outcomes that direct the development of the product.
Goals Beyond background context, you’ll almost always want to provide clarity on the goals of the feature being built?—?for A good productgoal, like any other, should be specific & well-defined, measurable, achievable/realistic, and timeboxed for success. for the user, for your business, and/or both.
Carrying out the relevant product discovery work and taking into account product ethics. Creating and validating a product strategy including market and user research. Developing a product roadmap and setting realistic productgoals/outcomes.
Organizing workshops to involve stakeholders in persona creation has two major benefits: Holistic understanding – Usually, each team tries to understand customers from their lens. There are online resources, including templates created by our team to help you organize persona workshops. Persona workshop template on Miro.
The Modus Kickstart is a structured, facilitated set of workshops to help accelerate a successful product release. It outlines a framework for facilitated product discussions and feature prioritization based on key assumptions, constraints, and KPIs leading to a more clearly defined plan. Product Vision and Goals.
Creating a strategy and tooling process so that product managers can succeed. Growing cross-functional collaboration, trust and camaraderie. Working with C-level execs on business/product/goal alignment. FYI, I’ll be leading “up the career ladder” workshops this Fall in Cleveland , Melbourne and Sydney.).
Depending on the size of the organisation, running a workshop with all team-members who have the most amount of knowledge of various aspects of each target market could be a quick, collaborative way developing a series of user scenarios. We then build or validate the user and buyer personas.
For this reason, do not do feature prioritization as a solo activity; the more diverse a team (from product designers to business people), the better are the results from the feature prioritization session. Check the following methods because they approach a product’s functions from various perspectives.
Good opportunities to engage stakeholders are Scrum events like the Sprint Review, workshops such as user story mappings, or training team members of stakeholders to better communicate with the Scrum Team in general. A product could be a service, a physical product, or something more abstract.” Source: Scrum Guide 2020.)
30-minute timeboxes to do a draft of a workshop. They don't have a specific sprint goal. They do have productgoals. I use timeboxes to focus on and finish one small piece of work: 15-minute timeboxes to write anything. Nonfiction, fiction, books, articles—you name it. 10-minute timeboxes to create images.
I am ready to provide business leaders and product managers the information, access, and expert guidance that they wish they had earlier in their product journey. I share my passion for product through workshops, published articles and speaking engagements. Interested in having me speak or attend an event?
We created an actionable 12-week virtual workshop series to help you jump through the hoops of prioritization and roadmap planning by using a clear, measurable, reproducible process for prioritizing features and initiatives. In this 30-min demo, we’ll dive deeper into how our SOAP™ methodology and tool can help you achieve your productgoals.
The better each product supports its business goal, the closer you are as an organization to making your portfolio vision a reality. Customers and prospects love you even more when your productgoals mirror their business goals! On to product strategy. Sales Training on Customers vs. Products.
We created an actionable 12-week virtual workshop series to help you jump through the hoops of prioritization and roadmap planning by using a clear, measurable, reproducible process for prioritizing features and initiatives.
We created an actionable 12-week virtual workshop series to help you jump through the hoops of prioritization and roadmap planning by using a clear, measurable, reproducible process for prioritizing features and initiatives. In this 30-min demo, we’ll dive deeper into how our SOAP™ methodology and tool can help you achieve your productgoals.
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