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
Ever wondered how product leaders juggle massive mergers & acquisitions, tricky integrations, and a pressure-cooker paceall while keeping their teams fired up and focused? From surfacing hidden landmines during duediligence to bringing entire product orgs under one cohesive vision, Brians got the battle scarsand the winsto prove it.
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. But within this complexity lay its charm.
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. 8:00] Tell us more about how you’re developing your core capabilities, especially AI visual recognition.
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. Developing a long-term relationship with someone who can act as your mentor and provide advice and direction can help to get around this. The Roadmap. Find a Mentor.
Whether you’re planning six months ahead or sitting in discussions right now, here’s the process I’ve developed through trial and error with clients over 15 years. Start demonstrating how you’ll solve their specific problems for the company/team. And how can I best show up for [name other team member(s)]?
BigVision BigVision is a business (or product or department) that has a big, exciting vision. We just need to start with First Opportunity first as due to our market analysis and business modelling, this is the best one to tackle”. HyperNarrowFocus tasks its research teams with performing a Discovery with First Opportunity in mind.
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.
I try to help product and sales teams succeed under the mantra “Easy to Sell, Easy to Renew.” I’ve struggled to find many examples detailing how to bond product and sales teams ( Antonia Bozhkova offers a good perspective ). Your teams will realign and strengthen their partnership as they see the product through each other’s eyes.
One of the few times a product manager really gets to take center stage and show the fruits of their labor is when they’re presenting the product roadmap. Roadmap presentations are the culmination of weeks, months, or possibly years of work. A compelling roadmap can inspire the company and set a positive tone for the future.
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.
A few years ago, I was the acting product manager at a startup, developing an enterprise software product. Building the product was hard: it was taking longer to develop than everyone expected (of course). I heard requests from customers, domain experts, consultants, our developmentteam, and internal stakeholders.
Added functionality, new capabilities, a more robust feature set…these are the talking points product marketers salivate over and executives search for on product roadmaps. Where are product teams getting their feature ideas? Why do product teams become feature factories? But are you solving for actual customer problems?
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.
As the CEO of Flow , a flexible project management app for teams, Daniel is working to create a productivity tool that defies conventional metrics, meaning that it simply allows you to get your most important work done without monopolizing the time you spend in the software itself. billion in 2015. How will you stand out from the pack?
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. You should know your company’s broader vision, objectives, target, and KPIs inside out and constantly view your product through the lens of this wider context.
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?
Over the course of the event, we explored our vision and beliefs for the future of customer engagement and communications, and heard from Intercom leaders like CEO Karen Peacock, Co-founder and Chief Strategy Officer Des Traynor, and Chief Product Officer Paul Adams, as well as some of our amazing customers. We’re here for you.”
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’.
And this is why we decided to bring you a special episode about these latest developments in the world of AI, what they mean, and whether it’s time to apply it in real-life scenarios such as customer support. Those manual tasks require really hard vision and processing things to solve. Des: Go into a forest and-. It would be great.”
Situation: You’ve painstakingly constructed a roadmap after consulting with various stakeholders, the developmentteam, and your peers. Soft skills” aren’t always part of their repertoire, not to mention loads of “ developer-speak.”. Be sure they’re aligned with the vision and goals for the product.
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