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
What is Bad Performance? Before I discuss how you can help an underachieving team, let’s briefly explore what good performance looks like, assuming that an agile, Scrum-based process is used. Second, the team participates in continuous discovery and strategizing , and its members regularly help refine the product backlog.
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. Decisions related to a new or significantly changed strategy have a very high impact.
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.
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.
“What is your ProductStrategy? YOU NEED A STRATEGY.” When I replay this scene in my head, I can hear the CTO very audibly yelling (slash pleading) with our productteam. This didn’t sit well with the CTO because in reality he didn’t want a strategy, he wanted a plan. This isn’t a strategy, this is a plan.
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).
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.
I look at four dimensions for robust Product Organizations: Product Organizational Design ProductStrategyProduct Operations Product Culture Inside each of these are a few capabilities that are then broken down further into sub-capabilities that help me pinpoint where the issues are.
Listen to the audio version of this article: [link] What Is a Product Portfolio Strategy and Why Does It Matter? A product portfolio strategy is a high-level plan that helps you maximise the value a group of products creates. These guide and align the strategies of the portfolio members , as Figure 1 illustrates.
Whenever you are faced with an agile, dynamic environment—be it that your product is young and is experiencing significant change or that the market is dynamic with new competitors or technologies introducing change, you should work with a goal-oriented productroadmap, sometimes also referred to as theme-based.
Be Clear on When to Involve the Stakeholders and DevelopmentTeams. Complex and high-impact decisions, however, are best made together with the stakeholders and developmentteams. Additionally, include the developmentteam members in product backlog decisions , and always choose sprint goals together.
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….
So, how do you get started with product analytics ? 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. What is product analytics? Why should you have a product analytics strategy?
Hence it is critical that one is aware of the best practises of the role and develops his own philosophy which results into maximum positive leverage for the organization. As I strive towards becoming a product leader, I wanted to understand the best practises in product management and in the process develop my own product philosophy. .
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?
Productside | Product Management Courses & Training Writing Effective Product Requirements to Drive Outcomes Most product managers dont set out to write bad requirements. And theyre juggling context, roadmaps, and Jira ticketsjust trying to keep up. Theyre under pressure to deliver. So what happens? Whats fast.
While common sense suggests that managing a product without the right measurements is not a sensible approach, I’ve seen productteams who did not use any KPIs. Consequently, these teams relied on: Anecdotal feedback : “Customers love our product, they told me so.” 3 Stakeholder or Big Boss Dictates KPIs.
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 user experience, 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.
The Scrum Guide released in November 2020 states that “the product goal describes a future state of the product … [It] is the long-term objective for the Scrum team.” It also suggests that “the product goal is in the product backlog. The entire Scrum team is “focused on one … product goal” at a time.
Manage the Product, not the Team. Focus on your job as the product manager or product owner, and manage the product, not the team. Provide guidance on the product, including its market, value proposition, business goals, and key features. Treat the Team as an Equal Partner.
For example, a productstrategy 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. Assess productstrategy and adjust if necessary.
For example, the owner of a persistence service has to be able to describe its interfaces or APIs and converse with the users—the developmentteam members who use the service. I regard feature and component owners as members of a productteam , a group of product people who collaboratively manage a larger product.
Listen to the audio version of this article: [link] The Core ProductTeamProductteams come in different shapes and sizes. But all productteams I have seen consisted of the person in charge of the product—the product manager or Scrum product owner —and developmentteam members.
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 teamsdevelop successful products. Continue the discovery and strategy work while the product is being developed. But don’t stop there.
How to Achieve Success in Your ProductStrategy In today’s rapidly evolving market, having a clear product vision and a well-defined strategy is essential for the success of any tech product. A compelling product vision is a guiding light, providing direction and purpose to the development process.
Listen to the audio version of this article: [link] Introduction To discuss empowerment in product management, I find it helpful to distinguish three main levels of decision-making authority, product delivery, product discovery, and productstrategy, as the model in Figure 1 shows. [1]
Consequently, your focus shifts from managing a product to looking after the product people on your team and empowering them to do a great job. For instance, you might show the individuals how they can make effective strategic product decisions, create an actionable productroadmap, and effectively use the right KPIs.
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).
Having “no company strategy” is one of the biggest issues facing product managers, according to a recent survey of over 600 product people. After all, how can you set a reasonable direction for your product when you don’t know where your company is headed? These were, why does the company exist (i.e.
Platforms offer several benefits: They can help grow a product portfolio faster and cheaper and they can help increase revenue. If the teamsdeveloping the different apps all created their own user-interface layers, there would be considerable code duplication, added development costs, and increased development time.
I once worked with a telco company that was developing a brand-new commercial product. Product management and development were located at separate sites in different countries. But this didn’t seem to matter much as everybody was in great spirits and had high hopes for the new product. To Collocate or Not.
I once worked with a telco company that was developing a brand-new commercial product. Product management and development were located at separate sites in different countries. But this didn’t seem to matter much as everybody was in great spirits and had high hopes for the new product. To Collocate or Not.
Defining your productstrategy is the most important aspect of deciding to build something new. It helps your entire team rally around a vision and a set of outcomes, making sure everyone is aligned in reaching those product growth goals. What is a productstrategy? How do you set a product vision?
If you thought there were a million ways to define product management, productstrategy might have it beat by a longshot. Just think about how many ways productstrategy is defined within your own organization. It’s the number one thing that makes productstrategy both challenging and frustrating at the same time.
Roadmaps don’t need to be complex, nor should you need a PhD to create one. Here’s a simple version to win over your team and stakeholders. Photo by Matt Duncan on Unsplash Ahh the dreaded word roadmap… The mere mention of a roadmap can divide the room, and send Product Managers into a world of panic.
Staffing : Help find people who have the right skills and are motivated to work on the product and who can fill the roles. For example, I’ve seen organisations where the Scrum Masters work with HR and the developmentteams to recruit new team members. The same is true for setting product goals.
Before the advent of agile frameworks like Scrum , a product person—the product manager—would typically carry out the market research, compile a market requirements specification, create a business case, put together productroadmap, write a requirements specification, and then hand it off to a project manager.
It forced me to question a belief, as a product leader, I treated as an absolute — that products always require roadmaps. My mentor and I started in our usual spot, talking about startups and new products in the healthcare industry. Do you think every company and product needs a roadmap?”
It compounds quietly across every team, workflow, and decision. When data collection is messy, product managers lose visibility, teams waste hours chasing answers, and user experience suffers. Your roadmap, now skewed by partial data, doubles down on solving the wrong problem.
But for every success story, there’s a graveyard of failed products laid low by badproductstrategies. A badstrategy is hard to overcome. And if no one realizes it’s wrong or adjusts course quickly, a promising product can become a lost cause. What Does a BadProductStrategy Look Like?
Embracing new technologies like machine learning, micro services, big data, and Internet of Things (IoT) is part of that change, as is the introduction of agile practices including cross-functional and self-organising teams, DevOps, Scrum, and Kanban. Determine the Right Learning and Development Measures.
The Critical Role of ProductStrategy When Money Is Scarce (Part 2 — Rounds A, B, and Later) When you start selling your product, you feel great, but that doesn’t last for too long. A productstrategy is often the missing link that would convert your efforts into actual revenue. Here is how it works.
The Critical Role of ProductStrategy When Resources Are Limited (Part 2 — Rounds A, B, and Later) When you start selling your product, you feel great, but that doesn’t last for too long. A productstrategy is often the missing link that would convert your efforts into actual revenue. Here is how it works.
Lackluster sales and/or poor adoption shouldn’t come as a surprise. Your products and technologies are always the enabler or the vehicle that actually delivers the value to the customer. How you design and build products doesn’t change in a portfolio management model. The intent of that design and development changes a lot.
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