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.
Listen to the audio version of this article: [link] Make Time to Keep up with Technology Trends As new technologies come and go, it’s important for you—the person in charge of the product—to stay on top of the developments. The following four measures will help you with this.
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. This includes Tech estimates (at least T-shirt sizing) and resources identified for the projects. Data vs Intuition.
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. About Jessi: Jessi is a director, technical product manager, SAP Concur. “You really need to be technical. WATCH THE FULL INTERVIEW HERE.
She shared insights from her experience leading product teams at various organizational scales and helping companies transform their product vision into measurable business growth. She now runs her own consultancy, helping CEOs scale their companies by transforming product vision into measurable business growth.
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.
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.
Having worked on a number of large technology programmes involving the selection and management of strategic suppliers, I wanted to share my perspectives from the ‘buy side’ on how to build effective partnerships. Establish a regular cadence to review supplier service and performance metrics?—?this
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.
Basecamp exemplifies this approach by openly encouraging debate and dissent to refine their vision. Every meeting becomes a performance review rather than a space for creative problem-solving. Stay tuned to find out how to take control of your products vision and strategy. OKRs should serve the strategy, not dictate it.
In my company, we review a living document with our management chain on a quarterly basis to align business direction for the short-term (immediate one to two quarters) to the long-term (two to five years). No formal stakeholder review as this is meant to be the first version that will undergo many iterations and refinements.
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. 3 Tell a Coherent Story.
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.
We had a large group of talented people – some who knew features and workarounds better than anyone else, some who were experts in technical concepts, some who excelled in project and relationship management, and others who had a deep knowledge of particular industries. The only problem? We were operating in silos. part of the name.
Photo by Gabriel Tovar on Unsplash So many aspects in our lives are based on other people’s visions coming true. Going through history, visions which became reality changed our lives dramatically, and as technology progresses, this becomes more and more true. but, what’s next? and a crucial one for us product people.
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?
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.
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.
You need a coalition shared purpose, mutual trust, and real support behind your product vision. 1-on-1 Support spanning personalized mentorship and resume reviews (available at higher tiers). Youve got the stakeholders in the room. But still things stall. Because alignment isnt enough.
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. It is therefore worthwhile to measure the code quality and minimise technical debt.
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.
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. Other Times, it's due to a lack of skill set in product leaders. Lots of data goes into pinpointing.
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.
However, as technology continued to change and the pace of change grew, there was a recognition that a more formalized approach was needed. The second application in 2024 included an on-site review process, allowing the PDMA team to experience DFW’s innovation initiatives firsthand through presentations and an airport tour.
Paul is an experienced product management professional with over 15 years of experience in technology management and 10 years in product management. Prior to Medidata, Paul led product management and was head of technology at Centage Corporation, a budgeting and financial forecasting software company in Natick, MA.
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. These indicators suggest that achieving product success will be much harder in the future, due to an increase in technical debt , higher absenteeism or turnover rate.
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.
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.
We’re pushing the boundaries of computer vision and machine learning. Training a computer vision model is very hard and usually requires an AI research team, but we wanted to make that problem accessible to anyone. Wyze’s tagline is to make great technology accessible. They felt like they were already part of Wyze.
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.
Paul is an experienced product management professional with over 15 years of experience in technology management and 10 years in product management. Prior to Medidata, Paul led product management and was head of technology at Centage Corporation, a budgeting and financial forecasting software company in Natick, MA.
A handy tool to formulate the strategy is my Product Vision Board, shown in Figure 2. Apply the checklist I have created for the Product Vision Board to ensure that your strategy is detailed enough. Should you stick with your strategy, significantly modify it, or no longer pursue your overarching vision?
Instead, I review the lessons learned from myself and my team that created and launched the summit. 6:41] Vision: Anytime we’re thinking about a product, vision is a very important aspect of planning to get the team on the same page. 14:24] Other decisions we were happy with: Pre-recorded sessions—technology worked.
Organizations are trying to figure out how to use these technologies effectively while keeping employees productive and motivated. Uncertainty and Ambiguity in Adoption Integrating generative AI into existing work processes isn’t always straightforward.
Here are key criteria to consider: Strategic fit with company objectives Sales potential and market size Competitive landscape User experience and customer value Technical feasibility and complexity Financial metrics (e.g., Let’s break down these approaches and look at their pros and cons.
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.
It’s important that they have the right skills to spot and evaluate design and technology opportunities and to develop a rough understanding of the likely effort required to implement product decisions. The vision describes the ultimate purpose for creating the product and the positive change it should bring about.
Sample product goals are acquiring new users, increasing engagement, removing technical debt to future-proof the product, and generating revenue. Use the KIPs and the development progress data to review the product strategy and the product roadmap, and change them as appropriate. I call these outcomes product goals.
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.
Sarah Dayan is a staff engineer at Algolia , a “Search-as-a-Service” platform that helps developers build index and search capabilities into their own platforms through an API, and the host of two tech podcasts: Developer Experience and Entre Devs. How would she provide the right technical direction for the company? Brian: Super.
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