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
ProductGoals Defined. The Scrum Guide released in November 2020 states that “the productgoal describes a future state of the product … [It] is the long-term objective for the Scrum team.” It also suggests that “the productgoal is in the product backlog. Figure 1: The ProductGoal in Context.
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 productgoals.
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.
Be clear on the reason why the meeting is needed. What’s the meeting about? For example, a productstrategy workshop might have the objective to identify the key changes required to achieve product-market fit. Carefully consider who should participate in the meeting to achieve the objective you have set.
Whether you manage a feature, a product, or a whole suite of products, you likely have some goals that you're trying to meet. But do you have a strategy? Strategy and goals are different. It's your strategy that allows you to make decisions that help you meet your goals in the first place.
ProductGoals Defined. The Scrum Guide released in November 2020 states that “the productgoal describes a future state of the product … [It] is the long-term objective for the Scrum team.” It also suggests that “the productgoal is in the product backlog. Figure 1: The ProductGoal in Context.
Specific : Make the goal—a.k.a. productgoal —so detailed that you can tell what needs to be roughly done to achieve it and how long it is likely to take. Measurable : Describe the goal so that you can determine if it has been met. Do not state any product details such as user stories.
In both instances, Id recommend using an overall portfolio or bundle strategy in addition to the individual productstrategies. If I were in charge of the suite, Id use a portfolio strategy that guides and aligns the strategies of Word, PowerPoint, and Excel. [1] Take Microsoft 365 again as an example. Add metrics.
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 product roadmap (as I explain in more detail in the article The T-Shaped Product Professional ).
If it is not clear who the users are and why they would want to interact with the product, it will be hard to decide which items should be in the product backlog and how important they are. A tool like my product vision board helps you capture and validate your productstrategy.
The objective is the goal, which describes what you want to achieve. The key results state the specific criteria that have to be fulfilled to meet the objective. To make this more concrete, let’s look at an example: Objective : Grow the product management team. Key result 1 : Three product managers are hired. It depends.
However, product managers often face even greater challenges when navigating high-stakes situations with senior leadership or dealing with conflicting priorities across departments. These moments can be politically challenging, as they require balancing the immediate demands of stakeholders with long-term productgoals.
To successfully manage your product and maximise value delivery, you should use additional artefacts including the following five: An inspiring vision that describes the ultimate reason for offering the product; A validated productstrategy that captures your approach to realise the vision and make the product successful.
You might not know, for example, which marketing strategy is most appropriate or which sales channels are most effective. You need the stakeholders’ active contribution to progress the product and reach the productgoals. Invite the individuals to productstrategy review meetings and sprint reviews.
To select the right KPIs, I recommend taking the following three steps: First, use the user and business goals in the productstrategy 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.
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?
Step 2: Use the Outcome to Determine the Features With a specific, measurable, and outcome-based goal in place, determine the features that have to be delivered to meet the goal. A practical way to achieve this is to focus the product backlog on the outcome. Then determine how the product has to change to meet the goal.
Collaboratively set goals , for example, user and business goals on the productstrategy and productgoals on the product roadmap. In other words, involve the key stakeholders in product discovery and product development work. Involve the Stakeholders in Important Product Decisions.
Organisational change and empowerment : Work with senior management, HR, and other business groups to implement the necessary organisational changes required to fully empower product people and leverage agile practises. Meetings : Prepare and facilitate meetings. The same is true for setting productgoals.
Expanding on a recent post ( Revenue Goals are Not Company Strategies ), I’ve been seeing lots of maker teams (product, engineering, design) struggling to form productstrategies without a company strategy to hang them on. There are no generic productstrategies.
Launching a product without a well-defined productstrategy framework is similar—you risk wasting resources without a clear path to success. So, how do you outline a productstrategy framework that is the foundation of product-led growth ? Productstrategies help you design and grow your products.
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.
In practical terms, involve stakeholders and dev teams in decisions that affect the productstrategy and the product roadmap —be it that you create the plans or that you make bigger changes to them. I therefore recommend using a dedicated, skilled facilitator who runs the meeting and facilitates the decision-making process.
Setting smart productgoals is a vital skill for any sensible SaaS owner or product manager to get right. In this article, we’re going to explore what makes an effective productgoal, the difference between goals and product initiatives, how to set them and make them work with your product backlog, and more.
And, they might need to collaborate across the organization with a variety of product and portfolio leaders if the organization wants to EOL (End of Life) one product and start a new kind of business. Move between strategy and tactics and back again.) For lack of a better word, I'll call this the productstrategy team.
For instance, the marketing strategy, the user experience (UX) design and technology choices have to align to successfully acquire new users, increase conversion, or meet another productgoal. Involve people in product decisions. You might do this, for example, by running collaborative productstrategy reviews.
This second post on the methods we use at Onfido to help us think commercially and strategically looks at State of Productmeetings. This meeting is an exercise in strategy, an opportunity to take stock of where your product is, where it fits within the wider market, and where it should go. ProductStrategy.
How product managers can build trust and alignment on virtual teams Today we are talking about making virtual product teams more effective. Our guest is Anna Marie Clifton, Head of Product at Vowel. She is leading the effort to make virtual meetings more effective by turning them into searchable, sharable knowledge.
To select the right KPIs, I recommend taking the following three steps: First, use the user and business goals in the productstrategy 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.
In the product planning model above, the vision describes the ultimate purpose for creating the product; the productstrategy states how the vision will be realised; and the product roadmap states how the strategy will be implemented. Now how far is Tortuga?
Cindy who helps you manage the product started to come late to meetings. It can be tempting to ignore people issues and focus on product-related tasks like reviewing the productstrategy , updating the product roadmap , and refining the product backlog. But this is hardly a recipe for success.
He helps rapidly scaling early-stage startups craft their ProductStrategy and everything related to it. He also helps middle market and scrappy companies generate new productstrategies for significant, sustainable growth. 12:59] Where have you seen product teams getting pushed out of cross-functional collaboration?
Asking the right product discovery questions helps uncover the deeper needs driving user behavior and expectations. Without a clear understanding of these factors, products risk failing to meet real-world demands. Exploring unmet needs and validating hypotheses helps refine product direction while avoiding costly assumptions.
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?
For example, I have seen product teams that create OKRs around meeting with customers, and engineering teams that created OKRs around closing the tech debt. The problem with this approach is that it leaves a huge gap in the company’s ability to deliver on its top OKRs: the product itself. Is that realistic?
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.
We’ve taken all these findings onboard and put together this comprehensive productstrategy checklist for you to follow. Simply follow the below steps and tick them off in turn to deliver the best mobile app product you can. What needs are you planning to meet through the app? What are you trying to achieve?
For product managers, this complexity means adopting a more strategic approach to ensure your productmeets customer needs, aligns with organizational goals, and delivers measurable value. As companies scale, product designers help ensure the productmeets both customer expectations and business objectives.
In practical terms, involve stakeholders and dev teams in decisions that affect the productstrategy and the product roadmap —be it that you create the plans or that you make bigger changes to them. I therefore recommend using a dedicated, skilled facilitator who runs the meeting and facilitates the decision-making process.
A big part of their job is managing the roadmap and prioritizing technical initiatives in the product backlog. Technical PMs play an important role in helping the development and product team gain a shared understanding of the productgoals and technical requirements. Product vision. Product roadmap.
to guide product teams at every stage. Top-notch products. So, which product management frameworks should your team use? In this article, we’ve outlined an extensive list to help inform your productstrategy. JTBD (jobs-to-be-done) is based on the principle that people use a product to complete a specific job.
“What is it that you would actually do, now that you won’t be responsible for one product, but a portfolio of them?”. This parallels the outcomes-versus-busyness challenge for individual product managers. Stakeholders see product managers attending meetings, writing stories, presenting roadmaps or presenting shipment data.
Fear not though, as our product management software guide will give you insights into some of the best-in-class applications that will boost your team performance and help you build successful products! Roadmapping software visualizes and plans product development over time, facilitating coordination and alignment across teams.
Best product vision examples focus on delivering value , are clear, and inspire the team and customers. They are also in sync with the company’s vision and shape the productstrategy. A product vision statement template will help you focus on the key pieces of the puzzle you need to figure out. Conclusion.
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