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
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.
Many CEOs of software-enabled businesses call us with a similar concern: Are we getting the right results from our software team? We hear them explain that their current software development is expensive, deliveries are rarely on time, and random bugs appear. These are classic inflection points for a developmentteam.
I love that Marty Cagan and Jeff Patton have long been advocates of dual-track development. If you aren’t familiar with dual-track development, it’s the separation of product discovery from product delivery. User stories and user story mapping help a team align around the top priorities and get clarity around what they are delivering.
From Raw Data to Clarity — Cleaning, Sorting, and Synthesising Insights Part 4 (of 5) of the UX Research Playbook series Synthesising qualitative data is similar to reaping the harvest after the diligent effort poured into research — it’s the step where hard work blossoms into meaningful insights. Context matters.
There are many ways to build a roadmap and many types of roadmaps you can make. Some will delight and engage the executive team by taking a high-level approach and focusing on goals and strategy. Others dive into the specifics and make engineering teams happy since they’re so detailed. Gather consensus around goals.
A common question for product managers, project managers, technical program managers, and software developers alike is what methodology to use given a project. Which should you and your teams decide the utilize? Whichever methodology a team operates under will heavily influence how they work and communicate with one another.
So, how do you ensure that UX gets its due in terms of investment? It also helps in saving on directionless development costs. Have you prioritized the design problems to be solved in your product roadmap? A product roadmap is a guiding document that details how your product strategy is to be transformed into a reality.
A Five-Step Methodology to Incorporate Generative AI into Business Strategy Developers, technologists, and innovators across enterprises are already using the new tools to boost their individual productivity at work and at home. The future of enterprise productivity is here, and generative AI powers it.
As the Director of User Experience, our team was tightly partnered with our product management counterparts to ensure we had baked-in practices and habits that enabled all of our developmentteams to deliver an exceptional product experience effortlessly. The Product Team’s Role in Customer Experience Strategy.
In this article, we want to tell you about what happened behind the scenes, including the deck we presented to the Benchmark team. This is the only way to know as entrepreneurs that there will not be an egregious term in the final documents. This is what happened again with the Benchmark team. for our community.
Like it or not, however, we now have no choice but to adapt – and that means ushering in a new era of potentially more efficient products, if we can just figure out how to get through a difficult learning curve where we’re frantically switching between calendars, video chats, email clients, spreadsheets, and documents. So what’s the solution?
From the process of disambiguation and the worst outage we ever had to our obsession with speed and how legal and engineering teams can work better together, Engineer Chats will give you a peek behind the engineering process at Intercom. The legal team isn’t there to slow R&D down. That is an ambiguous problem.
Bringing team members together, organizing user research, product demos, road mapping and more. They also said they wished they had a clearer product roadmap strategy. Review any existing feedback you have as well as additional direct channels such as chat bots, surveys, focus groups, and interviews.
Here are the 3 roles Product Managers must perform to achieve roadmap leadership: The Diplomat It’s not our role to dictate through authority where the product should go. Everyone’s opinion matters, and when they trust that we’re listening, a culture of respect develops. What gaps are being uncovered in sales?
Here’s what a comprehensive security assessment looks like: Step 1 – DueDiligence. You document information about the people, processes, and technologies that affect the organization’s overall security framework. SDLC (Software Development Life Cycle) of the organization . The Security Assessment Process.
Des Traynor laid out the six unique beliefs that guide our vision, mission, and roadmap here at Intercom. You’ll hear from the product managers that led the ideation, planning, and development of these products, and get their unique insights into the ways each of them can uplevel your customers’ experience with your company.
Golden rules for roadmap management. Everyone has a plan until they get punched in the mouth” — Mike Tyson I’ve wrestled with weak roadmaps — even some downright disasters. It was something that happened over time, a term I’ve coined ‘roadmap drift’. It was something that happened over time, a term I’ve coined ‘roadmap drift’.
Teresa: For those of you that are Product Talk readers, Melissa writes our Product in Practice series where we’re sharing stories about teams doing great discovery work, so you may have seen her name there. It’s allowing each team to really find what’s going to work best for them. Let’s go ahead and dive in.
Regardless of their scale and scope, they’re all products with production schedules, marketing plans, sales teams, logistics specialists, and—in most cases—product managers. All of that factors into creating comprehensive project schedules and product roadmaps , which then inform the far more complex go-to-market tactics for this industry.
And I think the similar kind of analysis you can do for B2B companies is for products that have different sized teams using it. If you have a really large team that they are all using a product, well, are they all using the product more as a result? And you can start to draw conclusions, sort of a natural A/B test in order to do that.
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