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
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.
2] Market Research AI-based tools can discover user and customer trends using predictive analytics. This can help you create a new strategy and evolve an existing one. 4] Product Performance and KPIs AI tools can continuously monitor how much value a product is creating and recommend improvements.
How product managers can adapt core responsibilities across different organizations and contexts Watch on YouTube TLDR Through his research and practical experience at MasterCard, Nishant Parikh identified 19 key activities that define the role of software product managers.
Listen to the audio version of this article: [link] What is a Portfolio Roadmap and Do You Need One? Neither is a singular atomic product. Microsoft 365 is a product portfolio, a suite that contains productivity tools like Word, PowerPoint, and Excel. This is where product portfolio roadmaps come in. [2]
Speaker: Johanna Rothman - Management Consultant, Rothman Consulting Group
Senior leaders often want to see months - or years - long productroadmaps. But these predictions often do not create products your customers will love. While customers aren’t fickle, they often do not know what they want until you give them something to try.
Listen to the audio version of this article: [link] A ProductStrategy System The productstrategy system in Figure 1 consists of four main parts: people, processes, principles, and tools. Having said this, the system in Figure 1 captures the specific productstrategy approach Ive created. [1]
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 product goals.
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? Four Artefacts.
Her first professional role was with a retail industry consulting company, where she started as a part-time employee during college. The company operated a software platform for their call center, managing customer communications while ensuring compliance with state regulations.
Speaker: Christian Bonilla, VP of Product Management at UserTesting
Every product team wants to build things users love. It’s why breakthrough products rarely happen by accident. Rather, they start with a strong product vision. Getting that vision right is one of the most important responsibilities of the product team. The goal may sound simple, but it’s hard to do.
Overview of the Learning Roadmap. Like a modern productroadmap, a learning roadmap states the specific outcomes or benefits you’d like to achieve to become a more competent product person, and it captures them in form of learning goals. To make these ideas more concrete, let’s look at a sample learning roadmap.
Securing everyone’s buy-in would be impractical—it would most likely take too much time. 2] Figure 1: The Power-Interest Grid The grid divides stakeholders into four groups: crowd, subjects, context setters, and players depending on how interested they are in your product and how much power they have.
Traditionally, productroadmaps 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. Second, it overlaps with the product backlog, especially when detailed features are used. Outcome-based).
In our a recent live stream from one of our mentors of The Product Mentor , Ian Moulton, lead a conversation around “Conducting User Research”. We are always looking for more product mentors from all around the world. About The Product Mentor. Better Products. Better Product People. View the live stream….
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. Key result 2: The onboarding system is improved, and time-to-proficiency is reduced by 25%. What are ProductRoadmaps? Can You Combine OKRs and Roadmaps?
Listen to the audio version of this article: [link] What Information Should a ProductStrategy Provide? I like to think of the productstrategy as a high-level plan that helps you realise your vision and that answers the following four questions: Who is the product for? Do You Need a Strategy for Your Product?
Listen to the audio version of this article: [link] Overview The GO ProductRoadmap consists of five elements, as the image below shows: Date, name, goal, features, and metrics. Sample goals include “acquiring new users,” “increasing conversion,” and “reducing cost.” Specific : Make the goal—a.k.a.
I believe the main culprits are Mr. Roadmap and Mr. Backlog. Culprit #1: Mr. Roadmap. An output is what we see and experience (the features and products we “touch”). How should we balance technical debt vs our feature roadmap? Why is that? Chock-full of Themes, Epics, Releases and Features. Culprit #2: Mr. Backlog.
Truly understanding your customers and finding ways to improve your product is an overwhelmingly daunting task. Customer discovery is key to informing productstrategy and there is a mountain of techniques and methods available for conducting customer discovery. Customer needs. Market knowledge.
There are many issues with having clients drive the roadmap. By the time the client asks for something “new”, all your competitors probably already have it too. It is much better to think ahead and innovate to create products that fit into the bigger vision of the company. Step 3: Creating the Roadmap.
The post includes plug-and-play strategy templates, recommended timelines, the stakeholders to involve at each step, and more 🔥 For more from Chandra, follow him on LinkedIn , and VRChat is hiring ! I worked closely with a seasoned board member to trace this back to a lack of productstrategy—both articulated and aligned.
How first principles can help you design productroadmaps from the ground up. Productroadmaps are no exception. Creating or even updating a productroadmap can feel like being handed a blank sheet of paper and told you have 60 minutes to write a ten-page college essay on a topic you didn’t study for….
Why a ProductStrategy Process Matters. An effective productstrategy process should ensure that a valid productstrategy and an actionable productroadmap are always available—that a shared and valid approach to achieving product success is available at anytime, as the picture below illustrates.
Listen to the audio version of this article: [link] 1 No Strategy The first and most crucial mistake is to have no productstrategy at all. When that’s the case, a product is usually progressed based on the features requested by the users and stakeholders. The strategy is therefore either too big or too narrow.
Taking charge of a product management team can feel like juggling flaming torchesthrilling, but also risky if you dont have the right game plan. Why the First 90 Days Matter When you lead a new product team, your opening move sets the tone. Let them sponsor your efforts at firstlike a borrowed VP badge. Do I push back?
Aligning on three things before diving into a solution can help ensure teams spend the right amount of time and energy solving every problem. What outcome does the customer want? . A well-crafted problem statement ensures the team shares an understanding of the core problem your customers are facing. Why do they want it? .
When we were writing this post, we did a little research to see what other brands were saying about mobile customerexperience. So, we won’t waste your time. Stop talking about customer-centricity; turn it into action. Every company says they’re “customer-centric,” but very few actually are. Sound good?
A four-layer framework to create a winning productstrategy Today we are talking about creating productstrategy. Bob is the author of the book Creative Strategy Generation. I first heard of Bob when he was the president of Sequent Learning, the product management training company.
Before you order the roadmap items, double-check that you have a validated productstrategy in place. You should be able to confidently say why users would want to use your product and why it is worthwhile for your company to invest in it. Instead, carry out the necessary product discovery and strategizing work.
the Product Manager role is a rather recent phenomenon. As a result, there are various different approximations that are made about the role in an organization depending upon their experience with building products. Also, in various organizations which have grown in product maturity, customer base etc.,
Your team is following the roadmap. You’re gathering customer feedback, hitting your OKRs, and tracking every metric imaginable. And yet, your product is stuck. Users churn, innovation stalls, and your team feels like theyre running on a never-ending treadmill. Roadmaps provide alignment. And customers?
A process for improving productroadmapping using Objectives and Key Results – for product managers. Today we are talking about roadmaps. Some product people love roadmaps, while a lot hate them. Summary of some concepts discussed for product managers. [2:11] What can make them better?
You’re Stuckand It’s Because You’re Playing by the Rules In product management, youve been told to follow the rules: stick to the roadmap, build consensus, and hit your OKRs. But what if I told you they’re actually sabotaging your product’s potential? Lets take them apart.
A first step to form effective product teams is therefore to identify the products in your organisation. But what is a product? I view it as an entity that creates tangible value for users and possibly customers as well as the business. The former is achieved by solving a problem or by providing a specific benefit.
It sounds simple, but that doesn’t mean it’s easy. – Tweet This While many product teams want to talk to customers every week, they struggle to make this a reality. You’ll hear how Orbital addresses many of their needs and helps the HiveMQ team generate a steady stream of customers to speak with every week.
Better Products. Better Product People. Each Session of the program runs for 6 months with paired individuals… Conducting regular 1-on-1 mentor-mentee chats Sharing experiences with the larger Product community Participating in live-streamed product management lessons and Q&A. Signup to be a Mentor Today!
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 productroadmap. A traditional roadmap is essentially a list of features, which are mapped onto a timeline.
The key results might then be “simplify user journey A” and “enhance feature alpha.”. In figure 1 above, the key result “simplify user journey alpha” becomes an objective with two new key results, “remove user journey step two” and “improve performance by 10%” thereby connecting the two OKRs. Figure 1: Cascading OKRs.
As marketers, our job is to understand our customers – their hopes, their wants, their needs – and then communicate the value of our product in the context of their lives. At SaaStr Summit , I spoke about how businesses can adapt during these uncertain times by focusing on customer impact.
Scaling a product isnt just about selling moreits about refining product-market fit, unlocking the right growth levers, and making sure your go-to-market strategy actually aligns with what your customers need. Rachel shares how shes helped SaaS products scale from $1M to $10M in a year. Dont miss Rachels insights.
Listen to the audio version of this article: [link] ProductStrategy and Change Strategy means different things to different people, so let me briefly share my definition. A productstrategy describes the approach chosen to make a product successful. These reviews help you see bigger trends.
The first one carries the risk of being a feature broker and offering a product that has a weak value proposition, gives rise to a poor userexperience, and consists of a loose collection of features. A stakeholder is anyone who has a stake in your product, who is affected by it, or who shows an interest in the offering.
Consequently, you don’t know for sure how fast you are running and if you are on track to achieve your target finish time. You’ll end up guessing how well the product is doing and if it is creating the desired value. Consequently, these teams relied on: Anecdotal feedback : “Customers love our product, they told me so.”
Product analytics refers to the process of gathering and analyzing data on how users interact with a product. It tracks key metrics such as feature usage , user flows, and behavior patterns to explore user preferences and pain points. Why should you have a product analytics strategy?
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