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
Listen to the audio version of this article: [link] What is a Portfolio Roadmap and Do You Need One? 1] But wouldnt it make sense to harmonise not only the product strategies but also align the product roadmaps? This is where product portfolio roadmaps come in. [2] How Can You Capture a Portfolio Roadmap?
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.
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.
The definition of success differs between your boss, engineering, the CEO. With all these challenges and hard lessons, learn from Jordan Bergtraum, product management expert, about how a product research roadmap can help you overcome them. The definition of success can be a moving target.
Speaker: Hannah Chaplin - Product Marketing Principal & Steve Cheshire - Product Manager
Without product usage data and user feedback guiding your product roadmap, product managers and engineers end up wasting money, time, and effort building what they think stakeholders want, rather than what they know they need. Product roadmaps must focus on the "now" and allow feedback to inform the "later."
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.
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….
A process for improving product roadmapping using Objectives and Key Results – for product managers. Today we are talking about roadmaps. Some product people love roadmaps, while a lot hate them. Our guest has had good experience creating roadmaps from objectives and key results (OKRs), and he is going to tell us how.
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?
Speaker: Eric Feinstein, Professional Services Manager, Looker
It seems like PMs and engineers have grown to hate embedded reporting. He will discuss working through personas, data types, reporting needs analysis and ultimately how this comes together to form a roadmap for reporting functionality and interface. Building a team to support your deployment.
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. Mental models for decisions not clear. Team dynamics and structure.
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.
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. Run structured stakeholder sessions to ensure leadership, engineering, and marketing teams remain aligned.
For the very first time, we’re releasing Engineer Chats , an internal podcast here at Intercom about all things engineering. Previously hosted by Jamie Osler , a Senior Product Engineer at Intercom for over seven years, it’s now up to Principal Systems Engineer Brian Scanlan to pick up the baton and keep the chats going.
Speaker: Donna Shaw - Senior Product Manager & Eric Frierson - Director of Innovation for Public and School Libraries
Learning Objectives How to utilize data to gain stakeholder buy-in, prioritize, and shape the product roadmap Why empathy is not only critical for developing software for users that addresses their market problems, but is equally important in empowering those in engineering, user research, and design to produce the best outcomes to meet user needs (..)
It’s always better when we’re together Photo by henry perks on Unsplash When I entered the wondrous world of product & engineering for the first time, I did not understand why there was a split between Product & Engineering. Engineering decides how and executes. One cannot exist without the other.
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. Not because the ideas are bad, but because the delivery misses the mark.
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?
How many more engineers do you need to do everything on the backlog? If you have four times as many engineers, you’ll be able to go four times as fast, right? . I also re-framed the alignment meetings as “Roadmap” meetings, not “Prioritisation” meetings. Finally, share the roadmap far, and share it wide.
Speaker: Mark Ridley, Owner and Founder, Ridley Industries
Any PM or technical leader who’s led the charge of building a digital product knows that product engineering is one of the most expensive elements of business.
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.
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? Prioritization methods are based upon the notion of Value, but given the sort of questions people struggle with, it clearly is ill-defined for many. Why is that?
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.
Improve product awareness and your roadmap. No matter what kind of product you have, the first order issue you’ll need to address as a product manager is Search Engine Optimization (SEO). Its blog and studies have golden advice for enterpreneurs, engineers, and of course, product managers. ahrefs I absolutely love ahrefs.
Think your customers will pay more for data visualizations in your application? Five years ago they may have. But today, dashboards and visualizations have become table stakes. Discover which features will differentiate your application and maximize the ROI of your embedded analytics. Brought to you by Logi Analytics.
Technology Roadmap Figure out the dev stack, the product backlog tools (Jira vs. Aha?), Hot Tip: At one acquired company, Brian discovered they used a rare programming language (Clojure) that none of his existing engineers knew. She standardized everythingno more 14 different ways to build a roadmap.
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
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.
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?
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.
They’re tasked with market and competitive analysis and laying out a product roadmap that delivers unique value based on their customers’ demands. Excerpts from an article I was recently quoted in on customer feedback and product validation ( [link] ): Product managers have a tough job.
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.
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.
A startup development team consisting of a product manager and two offshore engineers was facing major challenges in meeting client deliverable deadlines – repeatedly. Each major release deadline created a high pressure environment with engineers working overtime in the weeks prior in order to meet delivery dates. THE CHALLENGE.
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.
Effective prompt engineering is key to leveraging Generative AI for SaaS competitive intelligence. This post provides practical examples and advanced techniques, including role-playing and chain-of-thought prompting, to help you analyze pricing strategies, product roadmaps, marketing campaigns, and more.
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?
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….
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. I knew that I couldn’t look into the code to see that our engineers had built what I was looking for. We were making great progress.
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? Finally we write the roadmap for year one. At what cadence do you do that?
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.
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. Product managers should not build the roadmap.
Since our main objective was to include a subset of the main product’s functionality, most of our roadmap for the next 6 months was clear. Our QA engineer quit. We lost the QA Engineer, as we couldn’t to fix all of the issues with the process. Valia is a product manager and engineer, currently working on mobile apps.
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