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
Drawing from his 20+ years of technology experience and extensive research, Nishant shared insights about how these activities vary across different organizational contexts – from startups to enterprises, B2B to B2C, and Agile to Waterfall environments.
From surfacing hidden landmines during duediligence to bringing entire product orgs under one cohesive vision, Brians got the battle scarsand the winsto prove it. If you arent invited to the diligence party, rattle some cages: Arm Corp Dev: Provide them a short list of mission-critical data you must have before closing.
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.
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 product roadmap, sometimes also referred to as theme-based. 4 Keep it Simple.
Challenges due to hypergrowth. Onboarding: A huge number of hirings, from C-Level to PMs and Tech lead Process-oriented, not mission, not goals Purpose lost: make new employees impact the team as soon as possible No feedback-loop with new employees. Low accountability Limited visions of the product by PMs. Low transparency.
Relative to other standard roles defined in an organization such as Ops, Marketing, Tech etc., Often, this is due to resource constraints rather than a lack of understanding of a PM role. The path and the steps to reach the destination is defined through a product roadmap. Product Roadmap.
1] Figure 1: A Product Strategy System You can use the model in Figure 1 to review and improve your current product strategy approach. A great way to discover an effective product strategy is to capture your initial ideas, using a tool like my Product Vision Board , and then systematically correct and refine them.
While you can watch the full hour-long interview here , this post breaks down four of the key lessons we learned from Jessi Alva, Director, Technical Product Management at SAP Concur. What strategies do you use to prioritize your product roadmap? About Jessi: Jessi is a director, technical product manager, SAP Concur.
You’re Stuckand It’s Because You’re Playing by the Rules In product management, youve been told to follow the rules: stick to the roadmap, build consensus, and hit your OKRs. As can be easily found in many organizations: Roadmaps trap you in outdated plans. Rule 1: Trust the RoadmapRoadmaps are your comfort zone.
5] What about Product Roadmap Generation? You might have noticed that I didnt list the creation of product roadmaps as an AI benefit, even though several tools offer it. There are two reasons for this: First, the AI-generated roadmaps I came across during my research were feature-based, which is a roadmapping approach I dont recommend.
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.
PMs are often celebrated for their vision, decisiveness, and ability to ship. In our newest Patreon-exclusive Roadmap to Mastery article , we explore: The types of questions that unlock clarity across customers, teams, and stakeholders. This is part of the Roadmap to Mastery Collectionavailable exclusively on The Product Way Patreon.
I like to think of the product strategy as a high-level plan that helps you realise your vision and that answers the following four questions: Who is the product for? To capture the product strategy, you can use my product vision board. You can download the product vision board from my website and by clicking on the image below.
He is convinced that product is the single most important success driver for tech companies, which is why he founded Prodify to share what he learned from being an advisor to over 50 tech companies to realize their full potential. Ben has led successful technology products for the last 25 years. He It provided a lot of clarity.
Listen to the audio version of this article: [link] Traditional vs Outcome-based Roadmaps Before I share the four steps, let me briefly describe the main differences between a traditional, feature- and an outcome-based product roadmap. A traditional roadmap is essentially a list of features, which are mapped onto a timeline.
Youve aligned the roadmap. You need a coalition shared purpose, mutual trust, and real support behind your product vision. Read it now on The Product Way Patreon : [link] Exclusive Access to Mastery This post is part of the Roadmap to Mastery Collection , a premium series on The Product Way Patreon. But still things stall.
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.
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”.
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. How can the product be built?
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. Choose the next outcome on the roadmap as your product goal and copy it into the product backlog.
It’s a model of an iterative process that systematically links the product strategy with the product roadmap , the product backlog , the development work, and the key performance indicators (KPIs). Sample product goals are acquiring new users, increasing engagement, removing technical debt to future-proof the product, and generating revenue.
I review strategies and roadmaps. At the end of this review, I do a Product Leadership workshop with C-Suite and Product leaders, where I show them what good looks like, and they have a chance to reflect on where they are. Then we put together a roadmap for change, and I check in with them along the way as they transform.
I had a strong roadmap, clear goals and a vision for the product. A production release was a distant vision. As we were getting closer to the end of the year, my senior vice president called me in, to review our progress against our goals. I’m not a technical Product Manager. Similar, right? Should be an easy fix.
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.
But, it’s usually challenging to assess what’s the right way to go about it – how much of iteration should be that from user feedback versus founder’s vision for the product? However, I don’t necessarily agree with the idea that its user feedback “versus” the founder’s vision.
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 ).
Consequently, a platform should have its own product strategy and roadmap , KPIs , product backlog , and well-designed software architecture that leverages the right technologies. Ensure that the Platform is User-Led, Not Technology-Driven. Treat the Platform as a Product. Start Small.
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.
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. Carefully select them by using the factors discussed above, and regularly review and adjust them.
Hold Regular Product Strategy Reviews. But as the strategy will change, I recommend that you review and adjust it at least once per quarter—as a rule of thumb. Make sure that you block the necessary time for product strategy reviews in your calendar. Use Collaborative Workshops to Review and Adapt the Strategy.
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’re pushing the boundaries of computer vision and machine learning. Wyze’s tagline is to make great technology accessible. 3:15] How does Wyze compete?
As Kristen says: She predicts that this strategy of letting the product guide the sales process is the future of tech: “I think that’s where a lot of the future of sales and tech in general is going to go to some extent, which is to really let the product guide the people. Crowning the customer.
The importance of measuring the small outcomes associated with their product goals or visions is the key to churn expected benefits throughout the product life cycle. In summary, this framework gives an opportunity to discover, experiment, build, measure, learn and sell the product for outcomes aligned with the product vision.
Contrast this with a sprint review meeting , which might help you determine if users can easily sign up for the product. But for sprint review meetings , you may also want to invite (selected) users and customers to collect their feedback. Review and adjust product roadmap; check potential impact on the product strategy.
In the product planning model above, the vision describes the ultimate purpose for creating the product; the product strategy states how the vision will be realised; and the product roadmap states how the strategy will be implemented. The picture below shows the planning horizons I like to work with.
New technologies alone introduce change and uncertainty—think of the Internet of Things, Blockchain, machine learning, and generative AI, for example. Additionally, schedule regular collaborative strategy reviews —at least once per quarter—and invite the key stakeholders and development team members to them.
We all treat our products with care, respect, and diligence. It’s like a chance bit of customer feedback that we end up devoting a two-year roadmap to. Just as with a product, you should start with a vision. Once we’ve got our vision, we can begin to formulate a strategy that begins to bring this to life. The Roadmap.
is another common question asked by stakeholders when they review the proposal. Vision and strategygoals A vision statement should answer the following question: Where are we heading and why? Bad vision statements To be the best eCommerce platform in theworld. It doesnt highlight customer value or experience.
Let’s talk about how to define a product vision, and why the lack of a product vision is so detrimental to your team. Review design. 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.
Previously, in order to avoid becoming a bottleneck, I could review only high-stakes communications, like emails to the CEO or all-hands presentations. Of course, I’m still available to review work—and I do. And while this may sound like a chore (who enjoys being graded?), my team has found it invaluable.
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.
Identify needs that are not yet met and use this to inform your product roadmap. Get validation of your priorities by asking members how they feel about your roadmap and it’s prioritization. Align your vision and product strategy with the strategic direction of your customers business. New Idea Generation. About Lee Atkins.
A handy tool to capture your answers and describe the product strategy is my Product Vision Board shown in the picture below. You can download the template by clicking on the image and you can find more advice on how to use it in the article The Product Vision Board.
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.
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