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
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. Why study the 19 key activities of software product managers?
Productside | Product Management Courses & Training How WellNest Rebooted Product Strategy (eBook Preview) When product teams get stuck in backlog chaos, stakeholder noise, and reactive shipping, its not a process problem. Its a product strategy problem. Their current approach lacks a cohesive product strategy.
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?
Listen to the audio version of this article: [link] AI Strategy Benefits My research shows that AI can help you make better strategic decisions faster, at least for certain products. [1] 2] Market Research AI-based tools can discover user and customer trends using predictive analytics. 5] What about Product Roadmap Generation?
The quality of a customer care strategy can make or break a company. Simply resolving a customer service issue or complaint is no longer enough— in a competitive, customer-obsessed environment, there is always room for improvement. And do all of this while reducing the ever increasing cost and complexity of customer care.
Overwhelmingly, the #1 response is: access to customers. In Continuous Discovery Habits , I wrote that the only way to make continuous discovery sustainable is to automate your customer recruiting process. If you hustle each week to find customers to engage with, you simply won’t build a strong habit. This doesn’t surprise me.
Listen to the audio version of this article: [link] A Product Strategy System The product strategy 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 product strategy approach Ive created. [1] If so, what are they?
The path from IC to Chief Product Officer isn’t just about gaining more responsibility it’s about transforming how you think about product development, team leadership, and business strategy. Her first professional role was with a retail industry consulting company, where she started as a part-time employee during college.
Productside | Product Management Courses & Training How Product Management Strategy Turns Struggles into Structure We’ve worked with hundreds of teams stuck in reactive delivery cycles, constantly shipping features but never sure if they’re actually moving the needle. What WellNest needed wasn’t another roadmap or velocity boost.
Speaker: Johanna Rothman - Management Consultant, Rothman Consulting Group
Senior leaders often want to see months - or years - long product roadmaps. 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.
Overview of the Learning Roadmap. Like a modern product roadmap, 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.
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.
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.
Securing everyone’s buy-in would be impractical—it would most likely take too much time. 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. I refer to this group as key stakeholders.
Speaker: Lisa Mo Wagner, Product Management Coach, Writer, Speaker and WomenTech Ambassador
Timeline roadmaps provide us with a false sense of certainty and security. Often, product teams fall into the trap of creating a roadmap that doesn’t support timelycustomer feedback. Companies frequently make this mistake by creating a product roadmap 1-3 years in advance. How to Manage your product roadmap.
Key result 2: The onboarding system is improved, and time-to-proficiency is reduced by 25%. What are Product Roadmaps? A product roadmap is an actionable plan that describes how a product is likely to evolve. [3] Fortunately, in the last ten years, outcome-based, goal-oriented roadmaps have become more popular.
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. Progress bars and Milestones.
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? Figure 1: My Product Strategy Model. Four Artefacts.
Listen to the audio version of this article: [link] Introduction My first product management job wasn’t exactly what you call a success story: I was part of a team that was called in to help with a new product development effort, and I ended up working with the lead product manager. As helpful as a product strategy is, it’s not enough.
Speaker: Eric Feinstein, Professional Services Manager, Looker
For a long time, Product Managers have found it challenging to design interfaces inside their products that users could use for reporting. He will use the example of a product manager of a learning management software system and how she would go through the process of defining reporting for users of the product.
In this article, we’ll talk about: What product analytics is and why you need a solid strategy. Key steps to build and improve your product analytics strategy. Product analytics refers to the process of gathering and analyzing data on how users interact with a product. Why should you have a product analytics strategy?
Listen to the audio version of this article: [link] Overview The GO Product Roadmap 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.
Below, you’ll find what I believe is the most actionable, specific, and straightforward framework for crafting a strategy, for both your product and your company. As Chandra shares below, his framework sits on top of the best strategy wisdom out there (e.g. So we teamed up to make that happen.
The panel shared practical strategies to help you make that leap successfully: Delegate and Build Trust : Letting go of the “I can do it all” mindset is a critical step in scaling your impact. Lead with Influence : Align teams, shape strategy, and drive organizational vision.
How do you validate strategies, reduce risks, and ensure alignment with customer value? Discover how to develop a pilot that captures real customer feedback, aligns internal teams with usage metrics, and rethinks sales incentives to prioritize lasting customer engagement.
Customer support teams hear everything. Review support conversations regularly Look for patterns in user struggles, confusion, and pain points. Use insights to drive product improvements Support-based feedback can guide roadmap changes, de-risk decisions, and increase customer satisfaction.
Listen to the audio version of this article: [link] What Information Should a Product Strategy Provide? I like to think of the product strategy as a high-level plan that helps you realise your vision and that answers the following four questions: Who is the product for? Who are the users and, if appropriate, who are the customers?
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. Secondly, waiting for clients to drive the roadmap tends to puts companies in a situation where the backlog becomes too large to practically handle.
In todays product environment, questions are your sharpest tool for uncovering user needs, guiding teams, and influencing outcomes. In our newest Patreon-exclusive Roadmap to Mastery article , we explore: The types of questions that unlock clarity across customers, teams, and stakeholders. can shift your entire strategy.
Speaker: Jon Harmer, Product Manager for Google Cloud
Move from feature factory to customer outcomes and drive impact in your business! You will deepen your understanding of your customers and their needs as well as identifying and de-risking the different kinds of hypotheses built into your roadmap.
Leadership or investors push for short-term wins that conflict with the roadmap. Customer feedback is overwhelming , making it hard to separate signal from noise. Stakeholders request features that dont align with core strategy. Communicate trade-offs clearly by tying product decisions to business objectives and user outcomes.
In our latest Productside webinar, Becoming an Effective Product Management Leader , Principal Consultants Roger Snyder and Kenny Kranseler delivered a no-nonsense roadmap for new leaders who want to nail their first 90 days (and beyond) and get the tools on how to become a product management leadereffectively. How do I make a difference?
Your team is following the roadmap. You’re gathering customer feedback, hitting your OKRs, and tracking every metric imaginable. Users churn, innovation stalls, and your team feels like theyre running on a never-ending treadmill. Roadmaps provide alignment. Customer feedback drives iteration. And customers?
How first principles can help you design product roadmaps from the ground up. Product roadmaps are no exception. Creating or even updating a product roadmap 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….
Continuous development takes things further by giving product teams more autonomy and freedom to test out their ideas and experiment with new features in production by choosing who they want to test on. The importance of feature flags in your release strategy to mitigate risk, and whether you should build or buy a feature flag solution.
No matter what role you playproduct management, marketing, sales, customer onboarding, or account managementif your starting point isnt quantifiable customer value, fuhgeddaboudit! Align every part of the company to the customers most critical business goals (that are actually relevant to what you do) first. End of story.
Despite her years of experience, Jane realized something critical: even seasoned PMs need a plan to establish credibility in a new environment. With the right strategies, you can hit the ground running, build trust, and leverage your expertise to thrive in your new role. The good news? Pro Tip: Pair your quick wins with data.
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. As can be easily found in many organizations: Roadmaps trap you in outdated plans. Rule 1: Trust the RoadmapRoadmaps are your comfort zone.
There is no such thing as placing too much importance on your customers. Customers are the oxygen for any business model. One of the primary goals of any business strategy is to identify and meet needs of the customer. Customers differ widely from each other in various aspects. Analysis of the data.
Speaker: Christophe Louvion, Chief Product & Technology Officer of NRC Health and Tony Karrer, CTO at Aggregage
Christophe Louvion, Chief Product & Technology Officer of NRC Health, is here to take us through how he guided his company's recent experience of getting from concept to launch and sales of products within 90 days. Stakeholder Engagement 👥 Learn strategies to secure buy-in from sales, marketing, and executives.
As a result, there are various different approximations that are made about the role in an organization depending upon their experience with building products. As you climb the ladder, primarily the focus changes from solution and execution to strategy. This role also focuses on increasing the retention rate for existing customers.
A process for improving product roadmapping using Objectives and Key Results – for product managers. Today we are talking about roadmaps. Some product people love roadmaps, while a lot hate them. Our guest has had good experience creating roadmaps from objectives and key results (OKRs), and he is going to tell us how.
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. 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.
Ruthless prioritization translates to product teams spending time building the right thing at the right time. The objective is to receive feedback and prioritize it internally against (1) company objectives (2)customer pains/experience (3) Quarterly Product OKRs and ship out solutions. . And per customer?
Speaker: Michael Veatch, Senior Director, Implementations & Ella Aguirre, Director of Solution Consulting
Embedding payments can be a transformative step for software companies looking to enhance their platform capabilities, boost customer satisfaction, and drive long-term growth. However, the success of payments hinges on a single thing: implementation.
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