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. Below, well unpack his real-world advice on making acquisitions work, retaining your best people, and aligning tech stacks for a post-merger world that actually innovates.
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.
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.
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.
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. Regarding continuous delivery: Very technical focus (e.g. Low transparency.
Traditionally, product roadmaps are output-focussed plans that map features like registration, search, and reporting onto a timeline. Such a roadmap essentially states when a piece of functionality will be delivered. This makes the product roadmap more susceptible to change and it increases the effort to update it.
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.
But in today’s fast-paced world, your customer support can only be as effective as the technology that underpins it. Study after study shows that the vast majority of support teams are unhappy with their current customer support tech stacks. Download The Ultimate Modern Support Tech Stack guide. Is your tech stack ready?
It’s a familiar problem for all companies that scale fast – how do you keep your core technologies manageable for the increasing number of teams that depend on them? This surfaced as an increasingly large percentage of our product teams’ time being spent on operations or deep diving into understanding our small set of core technologies.
How first principles can help you design product roadmaps from the ground up. Product roadmaps are no exception. Creating or even updating a product roadmap can feel like being handed a blank sheet of paper and told you have 60 minutes to write a ten-page college essay on a topic you didn’t study for….
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.
Most innovators don’t have a technical background, so it’s hard to evaluate the truth of the situation. And unless they have a tech background, they can’t look under the hood themselves. The answer is to engage a trusted outside source for a TechnicalReview – a deep-dive assessment that provides a C-suite perspective.
Leadership or investors push for short-term wins that conflict with the roadmap. Shift from fixed yearly planning to rolling quarterly reviews to allow flexibility in roadmap decisions. Translate technical details into user-friendly language using real-world analogies. Full step-by-step approach in the Patreon recap!
Quick transitions to remote learning, usage and integration hurdles, lack of funding for new tech, and massive fluctuations in MAU all played a role in delivering a challenging year for educators and education technology across the country. Ratings, Reviews, and Interactions. Popular Phrases. Working in Mobile Education in 2021.
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.
While technical skills are still essential, the ability to influence, negotiate, tell compelling stories, and lead with empathy is now a critical differentiator. This is part of the Roadmap to Mastery Collectionavailable exclusively on The Product Way Patreon. Soft skills. The essential soft skills that top PMs are focusing on now.
Since there was no active grooming or planning session with the engineers, daily standups played the role of requirement review meetings. The team also agreed to initiate a weekly meeting to review and clarify requirements and to estimate the user stories. Long standups.
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.
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.
1] Figure 1: A Product Strategy System You can use the model in Figure 1 to review and improve your current product strategy approach. My Strategy Stack , shown in Figure 6, explains the connections between the product strategy and the business, product portfolio, and technology strategies.
Subcategories for Media Apps: News, Telco, Technology, Games, Sports, Music. “Thanks to the power of mobile, this cutting edge technology is at the fingertips of everyone with a cell phone right now,” Chip Kanne, Head of North America Emerging Sales, Snap. . Data included: Ratings and reviews. Popular phrases.
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.
What architecture patterns and technologies may be used? This includes discovering the right UX design and functionality and making the right technical decisions. Additionally, I recommend running weekly review sessions to understand the progress of the discovery work and adapt it if necessary. How might people use the product?
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. How asking What are we really trying to solve?
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. Sample goals include acquiring new users, increasing conversion, reducing cost, and removing technical debt to future proof the product.
It’s not about finding the right tech stack; it’s about finding the tech stack that works for your team. When it comes to the tools that support your continuous discovery, it’s not about finding the right tech stack. It’s about finding the tech stack that works for your team. Tweet This.
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
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.
You also might be reading this post thinking: “Who’s adding new tools to their tech stack right now?” Incorporating these tools into your customer experience tech stack will drive more engagement, gather high-quality customer feedback, and help inform your product roadmap. Supporting tech. This is a valid question.
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.
As she tells it, “When I was fresh out of college, I was working at my first job in the tech industry. Think about the impact that racism has already had in tech. Many people believe tech to be apolitical and unbiased, but that’s simply not true. The language we use shapes our world. Know the scope of the issue. Share the work.
A real-world case study of how strategic influence drove a 20% increase in engagement and reduced technical debt. Read it now: [link] Exclusive Access to Mastery This post is part of the Roadmap to Mastery Collection , a premium series on The Product Way Patreon. How successful PMs use influence to navigate complex challenges.
A Technical Exercise In this post, I’ll offer my idea of the sort of technical abilities expected from a product manager. This can be highly useful for hiring managers, as well as for PMs planning their roadmap. But is a surprisingly small amount of materials about the technical aspect of PM work. The Product Interview?—?A
Technology (media creation, connectivity, etc.). News apps saw incredibly high retention rates , likely due to how much news people consumed and the fact that there was breaking news almost daily. Music apps had the most app store ratings and reviews out of all Media subcategories. Technology Apps. Music Apps.
To keep track of what has been validated for delivery and development, a roadmap is your best tool. Product managers are often tasked with improving an existing roadmap — but sometimes you will need to create one from scratch. As you make changes to your roadmap, you will need to get feedback from stakeholders for your product.
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.
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.
Youve aligned the roadmap. 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. 1-on-1 Support spanning personalized mentorship and resume reviews (available at higher tiers). But still things stall.
Additionally, you’ve invited the senior management sponsor to the upcoming sprint review meeting to secure the individual’s continued support. An agile team is responsible for planning and tracking the work, reviewing the progress on a daily basis, and deciding how the work should be done to maximise the chances to meet the sprint goal.
Market Analysis Before and With AI Customers are clamoring for a number of improvements to your product and youre on a mission to get them funded and on the roadmap. AI has no idea which sales deals are hinging on your roadmap. AI doesnt know if anything on your proposed roadmap will open up new markets, etc.
Our goals and work are defined elsewhere, at different times, and there are good tools for that (like face-to face discussions, presentations, and roadmapping, product design and collaboration tools). Another reason is that people from outside of Tech don’t really like / know / want / remember to go to JIRA and Confluence.
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.
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.
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