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
To ensure that the right technologies are applied, you’ll benefit from using a technology strategy. The latter, in turn, drives the product roadmap, which directs the product backlog. Similarly, the technology strategy is directed by the business strategy. But that’s still not enough.
I believe the main culprits are Mr. Roadmap and Mr. Backlog. Culprit #1: Mr. Roadmap. How should we balance technical debt vs our feature roadmap? Technical debt can be valued in terms of “future change” outcomes like improved delivery velocity or better platform scalability, for example. Why is that?
Opportunity solution trees help product teams chart the best path to their desired outcome. Opportunity solution trees help product teams chart the best path to their desired outcome. – Tweet This In this article, we’ll cover what an opportunity solution tree is, the benefits of using one, how to create one, and so much more.
Businesses and individuals are increasingly making SaaS (Software-as-a-Service) applications their choice softwareplatform for their business needs. The increasing popularity of cloud computing indicates that the importance of SaaS will only increase in the future. SaaS products already have these integrations.
Unfortunately, “If you build it, they will come” does not hold true when it comes to the mobile app launch. This famous line from Field of Dreams is all too representative of how many app publishers face the ‘inessentiality’ of mobile marketing. They focus all of their time and resources on building a great app. It’s marketing.
Product Roadmaps, in general, are confusing. Three years ago I wrote a blog post about Rethinking the Product Roadmap , in which I advocated for a focus on solving customer problems instead of listing out features with deadlines. But first, let’s talk about Roadmaps in general, and how they got us on the wrong track to begin with.
Some of these are Fortune 10 software-enabled companies going through digital transformations. Others are SaaS companies that are scaling or have scaled recently and want to ensure they are doing it in the best way. I review strategies and roadmaps. At all of them, I start understanding the current state of Product Management.
Many of us in the design and technology community pride ourselves on being tool builders, creating products that others can use to get things done. Tools are part of who we are. We all have a very fundamental relationship with the tools we use. We all have a very fundamental relationship with the tools we use.
But like any tool, Scrum has its benefits and limitations. These are typically brand-new and young products as well as products that are experiencing a bigger change, for example, to extend their life cycle by addressing a new market segment or by replacing some of the technologies. But a mountain bike is better for riding offroad. [3]
No product tool or template can save you if you’re not killing it in these three areas. neither the product nor roadmap are ever static. That’s why we’ve listed 12 tools that the best product managers use to do their jobs better? and not the best product management tools. other than the objectives ?—?neither
How to Achieve Success in Your Product Strategy 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.
Their visions, target groups, needs, standout features , and business goals must comply with the overall portfolio strategy. [1] These might be end-user-facing or internal ones like a softwareplatform, for instance; they might directly generate revenue or support commercial offerings. A product portfolio is a group of products.
It’s like driving a car with your vision blurred: You can’t see if you are heading in the right direction or getting closer to your destination. Then take into account the product goals on the product roadmap to discover additional KPIs. Without KPIs, you end up guessing how well your product is performing. But it is not enough.
Deepa Subramanian (a graduate of Harvard Law School and a veteran of Salesforce) set out to improve businesses’ understanding of the customer voice by co-founding Wootric , a platform that offers a range of feedback collection and analysis tools to help teams gain deeper, more relevant insights into their users’ desires and complaints.
The Concept Map Target Audience: Product Teams and Leadership Intent: Sharing Vision and presenting the concept for acceptance The concept map helps you illustrate and present, well, a concept. Source: [link] The Past, Present, Future Map Target Audience: Product Teams and Leadership Intent: Sharing Vision An idea in a time is static.
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?
With a Master’s degree in human-computer interaction and over two decades of experience in user research and user experience in companies like Oracle, he now leads the design team across all product offerings at IBM. User research is a vital part of the design process. Since Thomas Watson Jr.
Much of the literature that defines the role as the intersection of business, technology, and user experience isn't particularly helpful for practitioners who are left wondering what skills they need to learn versus the fine people they work closely with in actual business, technology, and user experience roles.
It takes a fair bit of effort and time to keep up with the constant innovation in the product management software space. The tools are constantly evolving and changing their pricing plans, so it may be difficult to ensure that your product team is using the right tools and getting the best value for the money.
Much has been written about the process of creating product roadmaps, not least the six great articles written by my own team. I believe the actions of a product leader all too often are the root cause of a “bad” roadmap. Without thoughtful leadership around them, it may not be in product manager’s gift to achieve a “good” roadmap.
We’re a 14-year-old company that started off as an ads business, and we’re transitioning into a SaaS business. We have five product managers, one UX researcher , five designers—one of them director of design, leading the design team. It sounds like you are responsible for product, design, and research. Teresa: Okay.
Take a productivity tools suite like Microsoft Office or Google Workspace. If I was in charge of such a portfolio, I would use an overall strategy for the entire suite and separate product strategies for the individual tools like Microsoft PowerPoint and Google Slides.
What architecture patterns and technologies may be used? In order to answer the questions above, you may want to use techniques such as direct observation, user interviews, prototyping, creating a strategy canvas or E-R-R-C grid , and you may capture some of them using a tool like my product vision board. Look for opportunities.
One of our key findings from the survey is that product teams across the board say feedback from customer-facing teams like sales and support is highly influential when it comes time to prioritize their product roadmaps. Internal teams ranked by level of influence over the product roadmap. How does this work in practice?
“Should we buy this software or should we build it?” Juggling your company’s immediate needs with long-term goals is always tricky, but when it comes to purchasing a tool to make your team’s lives easier, managers tasked with the decision to build or buy often struggle in what seems to be a comparison of apples to oranges.
“Should we buy this software or should we build it?” Juggling your company’s immediate needs with long-term goals is always tricky, but when it comes to purchasing a tool to make your team’s lives easier, managers tasked with the decision to build or buy often struggle in what seems to be a comparison of apples to oranges.
After all, excellent design and engineering can only come from product teams that are empowered to solve hard problems and build great software. Core to that balance is a diversity of skill sets and vision on the team working in alignment. Product managers should not build the roadmap. You have to expect it to be that way.
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 then jammed those models into our platform so that customers could access the outputs in many ways.” You also have a mobile app that sends similar messages via push notifications. Widening the Scope from Solutions to Opportunities. Lisa says, “We led with ‘What can we predict?’ But what exactly is orchestration?
This vision holds true with our own organization as well. It is a very meta experience to build the ProductPlan platform as a go-to central hub for everything product management-related. Through this effort, we created a very exciting and strategic annual roadmap. And what better way to do that than a customer-facing roadmap?
A digital product is commonly redeveloped for two reasons: It has accumulated too much technical debt or its technologies are outdated, but the product is still needed—be it to generate revenue, support other revenue-generating products, or automate business processes and increase productivity.
Are product roadmaps sales tools? Think of a product roadmap as a sales pitch for your product. Thinking of your roadmap this way is helpful when you want to get support from stakeholders and gauge interest from customers — important people who care about your product’s future. Absolutely! Build excitement.
We’re confident this won’t help people game our system, but it will give you the best chance to show us your strengths. Our vision is to bring a messenger-first, personal experience to all customer and business communication. Our principles help us make decisions about strategy, roadmaps, design, and more. On-site interviews.
It’s Product Roadmap Building Time Again! The end of 2020 is nearing and it’s product roadmap building time again?—?at To make that process as worthwhile as possible, adhering to the following seven product roadmap first principles has proven beneficial in my experience. The classic quote from Lewis Carroll works here, too.)
Instead of creating, for example, product strategies and roadmaps and tracking KPIs , you should help the people on your team acquire the right knowledge and develop the right skills so that they can carry out the relevant work on their own. This includes the following ten capabilities: Formulating an inspiring vision for a product.
Crafting a winning product strategy is crucial for SaaS success, and finding the right product strategy example can provide all the inspiration you need. This article provides concrete examples of different product strategies employed by SaaS companies. There are 11 main product strategy examples in SaaS today.
There are many issues with having clients drive the roadmap. It is much better to think ahead and innovate to create products that fit into the bigger vision of the company. Secondly, waiting for clients to drive the roadmap tends to puts companies in a situation where the backlog becomes too large to practically handle.
Creating a successful product requires a clear vision. Equally important, it requires confidence that the vision is aligned with the needs of the customers the company exists to serve. This helped to inform its focus on developing its learning platform, Fender Play. The Fender Play learning platform.
It’s not just about training people to conduct interviews , use opportunity solution trees , or test assumptions —though those are all important activities—it’s also about convincing them of the value of these activities and getting the people they work with on board as well. Sandrine Veillet is the Vice President of Global Product at WebMD.
What is a Digital Transformation Roadmap? Above all, product teams can use a digital transformation roadmap to summarize the plan and goals for any move from a manual process to a digital one. Replacing your on-prem servers for storing corporate data with a cloud-based data management and backup solution.
You use an outcome-based product roadmap and/or an opportunity solution tree , personas , user journey maps, and the product backlog to capture and validate your decisions and guide the product delivery effort. You follow a business strategy and, if appropriate, a product portfolio strategy , which guide and constrain your decisions.
As a SaaS professional, you’ve probably asked yourself, “What’s tech product management?” We covered everything you need to know, from technical skills and responsibilities to a step-by-step roadmap for getting started. Technical product manager responsibilities include: Conduct user and market research to understand user pain points.
Here’s 3 steps you can take to start tackling your to-do list: Step 1: Get Organized With the Right Tool(s). But if you’re looking to mix up your day-to-day task tools, here are some suggestions. Task Management Tools for Product Managers. What it does well: It’s an extremely basic, simple solution.
Markets and technologies change. Here’s how we define it in ProductPlan’s eBook, 100+ Product Management Terms You Should Know: Digital transformation refers to a company’s move to digital solutions to improve its operations or products. Setting up digital communications tools to enable remote work.
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