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.
First, I did not know how to frame, develop and present productstrategy in a systematic way, and second, as a startup, my company has not historically had a good track record of strategy being developed outside of senior management (read: founder). Two major obstacles stood in my way.
Let’s make this more concrete by looking at a popular product discovery tool, Teresa Torres’ Opportunity Solution Tree (OTS). [2] 2] Before I proceed, let me point out that I am neither a product discovery expert in the sense discussed below nor do I fully endorse the specific approaches created by Marty and Teresa.
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.
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.
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.
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.
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.
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.
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?
Business Strategy vs. ProductStrategy. A business strategy describes how a company wants to achieve its overall aspiration and create value for its users, employees, and shareholders. The business strategy provides the company with the basis for making the right investment decisions. What is the company’s vision?
This article assumes that you are familiar with the product vision board or the key elements of a productstrategy : market, value proposition, standout features, and business goals. Solution : Successful products are not built by agreeing on the smallest common denominator or trying to please powerful stakeholders.
Strategy and enabling your team to solve problems makes the difference between a boss and an impactful leader. There’s no separate ‘productstrategy’ from company strategy?—?strategy strategy needs to be cross-departmental. He asked quite innocently in front of my new team, “what’s the productstrategy?”
For the first two quarters, the area is strategy; for the last two, it is leadership. The first goal is about creating a new strategy, the second one talks about the product life cycle model, the third one covers decision-making, and the last one addresses active listening. The third row contains the most important information.
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.
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. .
As their name suggests, these roadmaps focus on product goals or outcomes such as acquiring customers , increasing engagement , and future-proofing the product by removing technical debt. The goals state the specific value a product is likely to create and therefore communicate why it is worthwhile to progress it. Actionable.
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.
Productside | Product Management Courses & Training Writing Effective Product Requirements to Drive Outcomes Most product managers dont set out to write bad requirements. So the team builds it without questioning whether it fits the strategy or delivers value to the customer. So what happens? Whats fast.
The Eight Core Elements of a Winning ProductStrategy “The essence of strategy is choosing what not to do.”?—?Michael After what seemed like months of work, our product was emerging from stealth mode. The leadership team finally agreed on the vision. No choices = no productstrategy. Choice made.
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.
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.
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.
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.
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.
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.
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.
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?
To help you develop your agile product roadmap, I have created a goal-oriented roadmap template called the GO Product Roadmap. You can download the template for free from romanpichler.com/tools, and you can find more information on how to use it in my post The GO Product Roadmap. 2 Do the Necessary Prep Work.
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]
So, it was natural that we should want to develop a talent growth plan for our people. Each month we send out an NPS survey to assess whether the company is being a great place to work, but a few months ago I also sent Google’s manager feedback survey to my team of 10 product managers. Team execution and development.
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 product roadmap, and effectively use the right KPIs.
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.
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.
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. This is where tools like Userpilot come in, providing productteams with comprehensive analytics that bridge these dangerous data gaps.
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.
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.
You use them to take a fresh look at something that might feel overwhelming or vague — whether it’s a roadmap or a strategy — and start with what’s truly essential. While it would have been easy to blame the productstrategy, marketing, or any number of other potential targets, they weren’t at the heart of the problem.
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.
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 product roadmap, write a requirements specification, and then hand it off to a project manager.
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