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
Product Roadmapping Once product positioning is established, product managers move into the more action-oriented activity of roadmapping. This planning phase requires careful consideration of multiple contextual factors that significantly impact how roadmaps should be developed and managed.
At Proscai, I had the task to build a new Point of Sale (POS) solution for our clients and these three phases along with its corresponding documents helped me plan the development process and make sure all the team and stakeholders understood why, how and what we were building. This is where Roman Pichler’s GO Product Roadmap comes in handy.
Every product manager has made the mistake of thinking a perfect product roadmap would solve the problem in front of them. Every product manager has been there and thought “there’s got to be a better way – I just need a great product roadmap!”. Ah, of course, the product roadmap. And yet, you still need a product roadmap.
Roadmaps are altered by user feedback, new strategies and changing client needs. Help your team adapt and keep clients aligned with these documents, meetings, and conversations. In a recent live stream from one of our mentors of The Product Mentor , Andrew Hsu, lead a conversation on this topic.
A product roadmap needs to both capture your product’s strategy and outline your execution plan. Because these documents are such an essential component of your job as product manager, you also need to strategize your roadmap presentation. In this webinar, you will learn: How to communicate ROI in your product roadmap.
And your product roadmap is likely bearing the load. Do you think your product roadmap is running on fumes from too much change, or decaying from not enough focus? Then Revive Your Product Roadmap is the next thing you should read. Create a living document. Product teams are tired. Avoid too much detail.
Question: How do you respond to requests for date-based roadmaps? To provide a bit more context, one CDH community member was being drawn into theoretical debates about date-based roadmaps. First, I’d like to address some of the shortcomings of date-based roadmaps. At best, creating a date-based roadmap is a waste of time.
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.
So, your boss’s boss walks into your office and changes your roadmap…. The only real solution was to rebuild everything from scratch; requiring phasing out the old platform and creating a new one and managing multiple products and roadmaps. No, this is not a bad joke. As a product manager you prep, plan and execute.
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 timely customer feedback. Companies frequently make this mistake by creating a product roadmap 1-3 years in advance. How to Manage your product roadmap.
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?
1password.com) Strikingly- Public Forum, Idea Forum , where customers request and vote on features Public Roadmap (ie Slack , bitsian ) . Are things that we are learning finding their way into the roadmap? How do you internally communicate customer requests/feedback vs the roadmap? Are customers being engaged directly?
These interactions weren’t just about immediate product needs – they focused on building long-term partnerships and ensuring customers saw value in the product vision and roadmap. ” She found that being vulnerable about what she didn’t know actually added value to the team.
Product roadmaps are one of the best-known tools and also the most misused by product managers. We have talked twice before with Bruce McCarthy, co-author of the book, Product Roadmaps Relaunched: How to Set Direction while Embracing Uncertainty , to learn how to make roadmaps work for us instead of against us.
Speaker: Michael Veatch, Senior Director, Implementations & Ella Aguirre, Director of Solution Consulting
Whether you’re considering embedded payments or already underway, this interactive and informative webinar will help you build a clear roadmap to actualizing the true value of your payments investment!
so my investor said that I need a product manager to do our product roadmap?”. When I worked as a product management consultant clients would often talk about “needing a product roadmap ASAP”. In reality, asking for a product roadmap was shorthand for “please help me with my strategy”.
It forced me to question a belief, as a product leader, I treated as an absolute — that products always require roadmaps. Do you think every company and product needs a roadmap?” Then I thought further; maybe scenarios exist where roadmaps are optional. Roadmaps are not always needed. Roadmaps early on tend to box you in.
A stakeholder map is the best way to document all stakeholders in every project. The communication plan is simply a document we created to figure out the pathways of communication with the stakeholder. It could also include the actual team creating and executing the development to finish the product. Communication Plan.
A research conducted by Alpha UX found that 25% of Product Manager surveyed wished for a clearer product roadmap and strategy. While salary increase is a complex subject with variables outside of our control, I believe that having a clear product roadmap and strategy is every Product Manager’s responsibility. Research article.
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.
When I need to take a break from writing, I save the document. But the ability to save the document is a feature, a part of the overall product. A feature owner is an individual who owns a capability end users can interact with, for example, the ability to persist a Word document or to edit it. Word is the product.
Yet most product managers still rely on long documents, jargon-filled briefs, and clunky slide decks that dont land with the people who matter. But instead of telling a clear, compelling story, they send out a spec or share a roadmap deckand hope it gets read. 90% of executives say they prefer visual storytelling over dense reports.
At Headspace back in 2016, we had established our product roadmap and success metrics and our mission and vision, but teams were still confused about why we were working on the projects we chose. The plan or roadmap is basically an ordered list of projects based on some notion of prioritization and sequence of delivery.
How to Develop Product Roadmap? To lay out and document your strategy, you need to develop a Product Roadmap. Product Roadmap?—?What What Product Roadmap is a guiding strategic document?—? Facebook 10 Year Roadmap It maps out a high-level visual summary of the product vision and direction.
Talk to any of the product managers, and one of the main problems they will share how difficult it is to create an achievable product roadmap. I have mentioned “achievable” in the title because, most of the time, the product team comes up with a roadmap only to realize that it’s not achievable. This could happen for multiple reasons.
Planning includes the product vision, strategy, and roadmap. How do you set the vision, strategy, and roadmap? Who are the right stakeholders and partners to work with as you are setting your vision, strategy, and roadmap? We tap into all of that to write the vision document. [8:27] At what cadence do you do that?
Document your Key Assumptions. You won’t be there for the hundreds of decisions they’ll need to make as they execute on the roadmap, so the more context they have, the better their decisions will be. If it’s a senior PM, it may be showing an exciting opportunity to VPs or CPO. Communicate Communicate Communicate Communicate.
If you do things that are purposeful, you’ll eventually be successful.” — Howard Schultz Several years ago, I found myself in a heated discussion about product roadmaps with a client. So as he leaned across the table and looked me in the eyes, he demanded, “Explain why I need a product roadmap.” Why not, indeed?
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.
This includes a sound understanding of the market, the user and customer needs, and the competition as well as solid product management skills such as the ability to develop an effective product strategy and an actionable product roadmap (as I explain in more detail in the article The T-Shaped Product Professional ).
A Tale of Two Roadmaps — And Why You Can’t Succeed With Only One “There is no one-size-fits-all product roadmap. A roadmap can and should look different depending on the situation. Todd Lombardo Once upon a time, in a city like yours, two versions of a roadmap emerged. Both roadmaps, though different, are crucial.
The word roadmap usually conjures up thoughts of a product roadmap for people in a technology product company. For customer success managers though, the intent of a customer account roadmap, while similar, is bit more surgical than a product roadmap when it comes to defining success and leading customers to it.
Knowledge is power and user documentation is necessary for building it. But great documentation doesn’t happen by accident. This comprehensive guide will enable proactive product managers to figure out exactly how to craft documentation that will help users solve their problems and delight them. What is user documentation?
I call these goals product or release goals and I capture them on a product roadmap. Use a Product Roadmap to Plan Multiple Releases. The former can be nicely done with a product roadmap. The goals on your product roadmap should tell a compelling story about the likely development of your product.
When proposing redesign to stakeholders, you should prepare a document that will create a proper context for them and provide answers to the most common questions they likelyhave. Note that you dont have to provide an in-depth explanation of the reasoning right in the introduction; you will do it later in the document.
Always document decisions, next steps and circulate them When you have reviews with different stakeholders and agree on decisions, it’s always important to document what you agreed on, and note next steps or follow up items. Always use numbered lists in documents or slides Sounds simple? Repeat your goal. Done, right?
One of the biggest debates I see internally in product management teams is whether or not they should have a customer-facing roadmap. Should you take a plunge and share your roadmap externally? Best practices when building your roadmap: Define your audience as this will define the level of details. What is a roadmap, anyway?
Your product team is already soliciting feedback to drive the roadmap today. Developers will find both our iOS and Android SDKs well documented and straightforward to integrate. .” Indeed, many companies struggle to follow-up on specific customer feedback because of resource or technology constraints. Fast and Easy Migration.
Consequently, a platform should have its own product strategy and roadmap , KPIs , product backlog , and well-designed software architecture that leverages the right technologies. It typically requires documentation that shows how the platform assets can be used. A software platform, therefore, is more than a set of APIs. Start Small.
Forming such a team connects the person in charge of the product—the product owner—with the people who design, architect, program, test, and document the solution—the developers. Use a product vision ; a product strategy with user needs and business goals; and a product roadmap with product goals (aka.
The product roadmap is an essential piece of communication for your teams. It is a high-level document that conveys the strategic goals of a product amongst the product line and portfolio.
The strategy is the document that directs the mass of energy in the same direction significantly moving the needle versus a lot of activity moving in different directions not getting very far. There is a misconception in the industry that any feature list using a gantt style chart is a roadmap.
Such a backlog has enough “ ready ” high-priority items to guide the work of the development team and to allow its members to create a “done” product increment—executable software that is tested and documented and that could be released. Myth #5: It’s the product owner’s job to get the project delivered.
Communication underpinned and still does underpin my day to day to work, whether this is nonverbal communication in the morning to uplift your team, a quick rational response over slack to make informed decisions, or presenting your product roadmap to a room of customers. .
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