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 Do You Stay True to Your Product Vision While Adapting to Market Realities? The Challenge of Balancing Vision vs. Market Demands Why Product Vision Often Gets Lost Product leaders start with a bold vision, but execution becomes difficult when: Market conditions change , requiring fast adjustments.
Building the Foundation for Product Vision This activity serves as a bridge between problem validation and product vision development. By identifying and validating solutions before creating a product vision, product managers ensure they’re building on solid ground rather than assumptions.
Productside | Product Management Courses & Training Breaking the Silos: How Product and Engineering Build Better Together In Season 3 of Productside Stories , we sat down with Guy Gershoni , Head of Engineering at genesIT, for a candid conversation on what it really takes to build great products in todays complex tech environments.
As VP of Operations, Kim worked with third-party engineering consultants to improve the platform’s ROI and customer outcomes. Whether you’re coming from engineering, business operations, or another field entirely, your unique background can provide valuable perspective and skills for a successful product management career.
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. Do I push back?
Decision-making process for PMs: No common process, standardized No journey from OKRs to problems and solutions No articulation of the roadmap with uncertainty Not ahead of the needs Problems for making streamlined decisions, for articulating decisions. Low accountability Limited visions of the product by PMs. Low transparency.
PMs are often tasked with aligning stakeholders, guiding engineering teams, and championing the customer. But instead of telling a clear, compelling story, they send out a spec or share a roadmap deckand hope it gets read. When people see the vision, they align faster. And if it isnt understood, it wont get built.
Let’s talk about how to define a product vision, and why the lack of a product vision is so detrimental to your team. As I’ll explain below, the “why” and “where” form your product vision, and your product team (especially your engineers), not only want this from you, but need it in order to do their best work.
Creating a product vision of the future that’s awesome for everyone. Product roadmaps are frequently used badly, almost as handcuffs for product managers. A year ago we explored roadmaps and how they should be used with Bruce McCarthy. We cover: What a product roadmap is. Who the roadmap is for.
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? Is this thing you’re asking with our mission, vision, value proposition? Why is that? Chock-full of Themes, Epics, Releases and Features. Progress bars and Milestones. .
A healthy relationship between product management and engineering is critical to building successful products. In a perfect product development world, communications are seamless, specifications are clear, and product and engineering teams work together without friction. Include Engineers in Product Decisions.
From surfacing hidden landmines during due diligence to bringing entire product orgs under one cohesive vision, Brians got the battle scarsand the winsto prove it. Technology Roadmap Figure out the dev stack, the product backlog tools (Jira vs. Aha?), She standardized everythingno more 14 different ways to build a roadmap.
Data PM: organizations dealing in data products (building AI/ML based products) prefer a PM with data science background so that they can appreciate the problems well and being able to work with data engineers/scientists. The path and the steps to reach the destination is defined through a product roadmap. Product Roadmap.
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. Ions Engine.
As the first and most senior PM, I recognized the need to clarify vision, formalize processes, and set a proactive agenda moving forward. They need to shift their focus to leveraging teams to execute their vision and it is up to you to help with this transition. Start at the Top. In most companies, this process is ongoing.
Tailor Your Communication: Adapt your messaging for different audiences, whether its engineering teams or senior leadership. Connect Decisions to Customer Needs: Show how your roadmap addresses customer pain points to build trust. Present a high-level roadmap by your 90-day mark to demonstrate strategic planning.
Can’t get your boss to part ways with a time-based feature roadmap? I wonder what it is about feature roadmaps that is comforting to the C-suite. For bosses, I think there’s a perceived risk in moving from a safe and predictable feature roadmap to an experiment-based lean product roadmap. Then sell them on the risk.
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.
Typically, there are two big phases in bringing a product from vision to launch: planning and execution. Planning includes the product vision, strategy, and roadmap. How do you set the vision, strategy, and roadmap? We tap into all of that to write the vision document. [8:27] At what cadence do you do that?
On this episode of Intercom on Product myself and Paul Adams, our SVP of Product, take a look at roadmapping. Knowing how and when to define a roadmap, who to include and how long to plan for are key elements to finding the balanced approach that you need. As you grow functions, the audience for your roadmap widens.
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.
On this episode of Intercom on Product myself and Paul Adams, our SVP of Product, take a look at roadmapping. Knowing how and when to define a roadmap, who to include and how long to plan for are key elements to finding the balanced approach that you need. As you grow functions, the audience for your roadmap widens.
Some organizations lean toward execution, with a focus on product artifacts like PRDs, user stories, and roadmaps. While still others may focus on data analysis, customer research, project management, or even engineering. How far ahead is your roadmap determined? How often do you speak with engineering and design?
I had a strong roadmap, clear goals and a vision for the product. The relationship between QA and Engineering was bordering on food fights, and we’d only achieved half of our requirements. A production release was a distant vision. At the end of 2015 I was in the worst nightmare of any Product Manager. Similar, right?
He grows revenue and adoption, and ensures product by turning business problems into profitable, simple, easy-to-use solutions Jordan works closely with his market, executives, and internal subject matter experts to develop roadmaps, and communicate these roadmaps internally and with clients.
In product management you’re schooled to, identify who your customers are; identify a value proposition strategy and to persuade stakeholders of the vision you want to achieve. A pivot is a “structured course correction designed to test a new fundamental hypothesis about the product, strategy, and engine of growth.”
Their visions, target groups, needs, standout features , and business goals must comply with the overall portfolio strategy. [1] To get started, create your own Portfolio Vision Board by downloading and adapting the Product Vision Board or by recreating it in your favourite tool.
He grows revenue and adoption, and ensures product by turning business problems into profitable, simple, easy-to-use solutions Jordan works closely with his market, executives, and internal subject matter experts to develop roadmaps, and communicate these roadmaps internally and with clients.
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. Engineering and design ?—?Any
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.
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. Product strategy sits in between the mission and vision and the plan, either at the company level or at the team level.
A group of passionate users in our social media and forum communities drives our roadmap and and helps us understand the problems we need to solve. We help external engineers understand the product requirements and user needs and rely on their expertise. We’re pushing the boundaries of computer vision and machine learning.
I oversee product planning, product roadmap, vision, and strategy for our products. Work collaboratively with engineering teams, quality teams, your DevOps organization, etc., Building the product tends to be an engineering activity, but product managers still have an important role to play.
After all, excellent design and engineering can only come from product teams that are empowered to solve hard problems and build great software. In our model, product teams effectively own a piece of the product, and consist of a Product Manager, Designer, and a few Product Engineers. Alignment on great product teams.
The best teams have collaboration between product management, development, and engineering. 20:16] What are your suggestions for structuring and using roadmaps? Especially for B2B software, roadmaps are a critical part of communicating with customers. We’re buying the roadmap. We’re buying the roadmap.
How product mangers can improve collaboration in cross-functional teams Today we are talking with Maziar Adl, the co-founder and CTO of Gocious, an organization that creates product roadmap management software. 6:52] Did you find a gap in the roadmapping tools that were available before you started Gocious?
I instead define a product manager as driving the vision, strategy, design, and execution of their product. Vision: Vision Narrative. Most product managers realize that defining a compelling vision for their product is a core responsibility of their role. Vision: Product Walkthrough.
Insights on roadmaps, metrics, OKRs, and more for product managers. Joining us for this episode is a CPO who shares some of the tools he uses, including roadmaps, metrics, and OKRs. In my company, I help with hiring great people across the company and explaining why the company is going to win using its great product vision.
roadmaps?” Executing a product roadmap requires more. Changes that you must reflect in the roadmap. You need your engineering, design, and marketing partners to succeed (if it’s a software company). Why is product lifecycle management important to product roadmaps? Queue the time travel music….
that products always require roadmaps. Do you think every company and product needs a roadmap?” Then I thought further; maybe complete scenarios exist where roadmaps aren’t needed. Fast forward to the end, there are in fact scenarios where companies and products do not need roadmaps. Tell me your perspective.”,
This article tackles one of the areas that gets the most interest from product managers: how can they use an essentialist approach to create and communicate better product roadmaps ? To ensure you’re adding the right features and initiatives to your product roadmap, I’ve outlined several suggestions here. Start with the product vision.
Like that soccer team, products can fall apart when the team doesn’t work together toward a common goal following a roadmap. Soccer is a perfect parallel for product management and roadmap development. While they might seem worlds apart, they share common core principles for success — especially when it comes to roadmap development.
Between interfacing with multiple teams, coordinating release schedules, prioritizing customer happiness, driving the mobile product roadmap, and endless other activities, it’s easy to get caught up in the hustle, bustle, and stress that is product management. Good companies manage Engineering. Bill Gates, Microsoft.
He is also the co-author of Build What Matters: Delivering Key Outcomes with Vision-Led Product Management. A lot of companies have a mission statement that they think is a strategy or vision. The vision is where you intend to be in several years. A lot of work that goes into a vision. It provided a lot of clarity.
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