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.
Productside | Product Management Courses & Training How WellNest Rebooted ProductStrategy (eBook Preview) When product teams get stuck in backlog chaos, stakeholder noise, and reactive shipping, its not a process problem. Its a productstrategy problem. Thats where the Productside Blueprint comes in.
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.
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.
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.
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.
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.
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] This is where product portfolio roadmaps come in. [2]
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.
Listen to the audio version of this article: [link] 1 Complement Scrum with a Product Discovery and Strategy Process Scrum is a simple framework that helps teams develop successful products. How can you capture the right user stories , for instance, if you are unsure who the users are and why they want to use the product?
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. Additionally, you should be confident that your strategy is correct, and you should have data to support your view.
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.
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.
No matter the specifics of how your company adapts and grows, it’s crucial to be aware of how your pricing strategy relates to other aspects of your business. It’s all too easy to make the mistake of adopting a pricing model that is ill-suited to other aspects of your company, such as the go-to-market strategy or sales strategy.
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.
(Often, a combination of strategy and tactics.) 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.) They can't.
Consequently, a Scrum product owner should own a product in its entirety—from the product vision to the product details. The individual should carry out product discovery and strategy work in addition to taking care of the product backlog work.
Collaboratively set goals , for example, user and business goals on the productstrategy and productgoals on the product roadmap. Involve the Stakeholders in Important Product Decisions. But this also means holding people accountable for meeting their agreements.
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.
For example, the marketer has to create the marketing strategy, and the development teams have to design and build the product. 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.
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.
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. OK, What’s A Company Strategy? And a great tactician.
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. State of Product.
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.
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.
Consequently, a product manager and a Scrum product owner are leaders, too. They guide the stakeholders , development teams, and in the case of large products, other product people, to meet the agreed productgoals , create the desired outcomes, and achieve product success, as Figure 1 shows.
As the person in charge of the product, you may not be terribly concerned about how clean and well-structured the code is. The messier the code and the less modular the architecture is, the longer it takes and the more expensive it is to change your product.
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.
This article is dedicated to how I go about including these activities in my routine, and some tools and strategies that work for me. Competitive analysis is fun as long as you are curious and open to learning the good and bad of your product. I suggest that you do not constantly compare your product to the ones you’re researching.
What is a messaging strategy? A messaging strategy is a marketing framework /plan that outlines how your brand communicates its key messages and unique selling proposition to its target audience. Why should you have a solid messaging strategy? SMART goal-setting framework. Let’s look at how that’s done!
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.
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.
Pete, the marketer, agreed to rework the marketing strategy to support the next major release. Cindy who helps you manage the product started to come late to meetings. Finally, consider if it is feasible to meet onsite. If you meet online, make sure that the cameras are switched on and that you can clearly see each other.
Businesses invest heavily in product marketing through webinars, blog posts, and video content for a reason – it gets them notable results. If you’re looking to start or improve your SaaS product marketing strategy, this is the article to read. Product management focuses on building the right SaaS products.
According to a Foundry 2023 report, 93% of all companies have already adopted or plan to adopt a digital-first business strategy. But this doesn’t mean their staff can handle a highly technical software product. This way, you can develop targeted retention strategies to re-engage these users before they leave your product.
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. Take the Apple Watch as an example.
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?
What is a land and expand strategy? In this guide, we’re going to show you how a land and expand strategy can help you grow your revenue generation from existing clients by deploying a foot-in-the-door approach with your sales team! Select the right expansion strategy for your product, business goals, and pricing model (i.e.
Step #1 Line up Your ProductGoals To find Product-Market Fit ( PMF )— you need to define what the PMF condition looks like. The PMF goals need to align with your company's financial milestones. Credit: Slidebean Financial Model 101 The financial milestones are broken down into Product Team Goals.
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.
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