Product Marketing Career PathProduct LaunchesStakeholder ManagementInfluencing the Product RoadmapProduct Marketing KPI'sEstablishing Product MarketingBuilding a Product Marketing TeamCompetitive PositioningGo-To-Market StrategySales EnablementMarket ResearchProduct Marketing InterviewsEnterprise Product MarketingProduct Marketing 30/60/90 Day PlanConsumer Product MarketingBrand StrategyPricing and PackagingPlatform and Solutions Product MarketingInfluencing the C-SuiteCategory CreationSelf-Serve Product MarketingProduct Management Career PathGrowth Product MarketingProduct Marketing SkillsSMB Product MarketingProduct Roadmap & PrioritizationProduct Marketing Soft and Hard SkillsIndustry Product MarketingBuilding a Product Management TeamRelease MarketingDeveloper Product MarketingAnalyst RelationshipsBuilding 0-1 ProductsTransformative Product LaunchesProduct StrategyProduct Management SkillsProduct Marketing / Demand Gen AlignmentEstablishing Product ManagementDemand Generation StrategySMB Product ManagementDemand Generation Career PathProduct Management KPI'sTechnical Product ManagementConsumer Product ManagementStorytellingRevenue Ops KPIsProduct Management InterviewsAI Product ManagementRevenue Ops 30 / 60 / 90 Day PlanAccount Based Marketing StrategyProduct Marketing vs Product ManagementProduct Management 30/60/90 Day PlanDeveloping Your Customer Success CareerRevenue Ops Career PathTechnical Product MarketingScaling a Revenue Ops TeamEnterprise Product ManagementScaling a Customer Success TeamProduct Development ProcessEstablishing the Revenue Ops FunctionRevenue Strategy ExecutionBuilding a Demand Generation TeamScaling a Sales TeamCustomer Success Soft and Hard SkillsGrowth Product ManagementCustomer Success InterviewsAI and Product MarketingDeveloping Your Sales CareerSales Soft and Hard SkillsDemand Generation KPI'sBuilding a Revenue Ops TeamDemand Generation 30 / 60 / 90 Day PlanSales InterviewsPartner Product MarketingMessagingCustomer Success KPIsChannel MixProduct VisionPlatform Product ManagementGrowth Marketing StrategySales KPIsDemand Generation InterviewsRevenue Ops SkillsDemand Generation Soft and Hard SkillsScaling a Demand Generation TeamDemand Generation SkillsCustomer Success 30 / 60 / 90 Day PlanProduct Management vs Product MarketingEstablishing the Customer Success FunctionEstablishing a Demand Generation FunctionRevOps ReportingDigital Marketing StrategyCustomer Marketing StrategyIntegrated Campaign MarketingEnterprise SalesSales DevelopmentCustomer Success / Revenue Ops AlignmentProduct Marketing Productivity HacksDeveloper Product ManagementSales KickoffManaging Mature ProductsProduct AdoptionProduct InnovationProduct DifferentiationSegmentationRevenue Ops InterviewsSales 30 / 60 / 90 Day PlanCampaign OperationsData and AnalyticsOutbound Product ManagementEstablishing the Sales FunctionCustomer ExperienceEnterprise Customer SuccessCustomer MarketingDeal StrategyCustomer Success LeadershipProduct OperationsMarketing / Revenue Ops AlignmentAI and Customer SuccessInfluencing without AuthorityDiscovery TacticsEvent Marketing StrategyTechnology ManagementDigital MarketingFinance / Revenue Ops AlignmentSales/Revenue Ops AlignmentSales / Demand Gen AlignmentAccount ExpansionUser Interviews
Get answers from product management leaders
Kie Watanabe
Kie Watanabe
HubSpot Group Product ManagerOctober 14
This is a two-part question. Let me first articulate how I like coming up with ideas for new opportunities, followed by how I like to make decisions about what to build. Hopefully, you don’t mind that I’m thinking about “opportunities” because it might not always be a feature that’s the right solution. I should start by saying that there isn’t one right approach to coming up with ideas. In my experience, I’ve had success ensuring that there are: 1. Insights from the four lenses: Customer, Business, Market, Technology 2. Effective methods to facilitate ideation At the core, you have to have a deep understanding of the underlying user pain point you’re trying to solve through a thorough investigation of the Customer by talking to customers and product usage. You might actually learn very quickly that the user problem is around discoverability or activation, not necessarily a feature gap. Ideally, the customer impact is so deep that it translates effectively into Business impact. The Market context is critical to help understand how your user will experience the product within the broader competitive landscape and the direction an industry is headed. Finally, the Technology lens offers insight into what capabilities could be used as part of a solution. Preferably, these four lenses come together through cross-functional ideation that has the right participants (e.g. PM, UX, Eng, and even folks go-to-market teams). In a hybrid world where we’re working across time zones, I’ve enjoyed having the opportunity to ideate together synchronously and asynchronously. In terms of decision-making, the ideation process should lend itself to initial layers of prioritization. I won’t go into prioritization frameworks here, but there are many out there. They do tend to distill back to impact and effort and sequencing. At HubSpot, depending on the type of decision we are trying to make, we may use a “driver, approver, contributor, informed” DACI model used by other companies we admire like Atlassian.
...Read More
18578 Views
Upcoming AMAs
Avantika Gomes
Avantika Gomes
Figma Group Product Manager, Production ExperienceDecember 22
There's a lot written about basic PM competencies (https://a16z.com/2012/06/15/good-product-managerbad-product-manager/), and for any PM on my team, they should be able to do all these things you'd expect from a PM (write specs, understand the customer, communicate upwards and outwards, GSD). I'll focus my answer on a few attributes that I think are really "make-or-break" for me: * Good communication skills, both written and verbal, are an absolute must-have for any PM on my team. Whether it's through writing specs, influencing stakeholders, or pitching product ideas, PMs have to be able to communicate effectively across mediums (written, verbal), forums (large groups vs. small groups vs 1:1) and audiences (to developers, marketers, sales, executives). In particular, they need to be able to tell good stories (e.g.,, can they get their team inspired about an idea?), structure their communication effectively (e.g., can break down ambiguous problems using a framework?) and make technical concepts easy to understand for non-technical folks (e.g., can they explain how routers work to someone without a CS background?) * Great PMs "own" the problem. They're not afraid the step outside the boundaries of their function to do what it takes to get the product out the door. They rarely ever use phrases like "that's not my job" or "this was the designer/developers responsibility". Their strong sense of ownership of the problem leads them to passionately debate about the right solution, speak truth to power when necessary, but also be open to other points of view (because it's not about "them", it's about solving the problem).
...Read More
11745 Views
Ajay Waghray
Ajay Waghray
Udemy Director of Product Management, Consumer MarketplaceAugust 26
We have a great podcast episode about this! To summarize, it’s less about explicit processes and more about tools in the toolbelt. It’s all about right tool, right job. The tools that come to mind for incorporating customer feedback are: 1. User research. This typically involves a full user research team, crafted questions and a lab that users visit to provide feedback on designs, prototypes, live product, whatever is being used for testing. But sometimes it’s something you do on your own with the help of a user researcher. 2. Surveys. This usually involves working with someone that specializes in surveys, product marketing or something you do yourself (very carefully!) to survey customers about what things they like and don’t like about new or current product features. You can also ask about how likely they are to promote the product or feature to their friends, prices they’re willing to pay for products, etc. 3. Customer Support Feedback. This is what customers tell your customer support team if you have one. A great way to collect this is to sit with your customer support team and either field calls yourself or listen in while others are fielding calls. 4. Written Feedback. Can come from a feedback widget on a website or app, app store reviews, emails to the CEO, etc. This tends to be lower fidelity but can be really useful when troubleshooting or looking for lots of feedback volume. 5. Quantitative Data. This is not something people usually think of when it comes to customer feedback! But Quantitative data is really just a data representation of customer feedback. It shows what customers are actually doing. And, when analyzed properly, can reflect what you see in the more qualitative methods above. There are more, but these tend to be the most common ones. Depending on what the need is for a product or feature you’re working on, you might want to use different tools for different purposes and project phases. For example, if you’re trying to redesign a product page for the whole website, it’s worth taking your time. It would make sense to start looking at quantitative data and written feedback early in the process. Then, once you have prototypes to test, user research can play a bigger role. But maybe you have some bigger questions to answer before then, like what kinds of elements do users want to see on these pages? Then engaging user research to help figure that out can be a big help since it’s less structured and more complex. And of course sometimes you need something fast to ship in the next few days. Written feedback, quick surveys and customer support feedback can be really helpful. Each of these tools have some bias baked in as well. For example, written feedback is more biased to more engaged, more passionate users. So it’s good to keep in mind what those biases are and figure out how best to use those tools depending. Great question!
...Read More
21653 Views
Tamar Hadar
Tamar Hadar
The Knot Worldwide Senior Director of Product | Formerly Trello (Atlassian)February 3
As a first PM, you will need to be very judicious with how you allocate your time and resources. In fact, I think that’s true for larger companies as well. There are always going to be more ideas than resources available. As a product manager, you are responsible for translating the company’s vision into a roadmap so your first priority should be internalizing the company’s goals. Is it to drive sign-ups? Increase retention? Increase MRR? Or something else altogether? Narrowing in on that top goal helps to weed out work that may be less relevant. Once you’ve identified the top goal (there may be more than one), filter out any initiatives that do not map to this goal. The exceptions being pressing engineering initiatives (i.e. a platform upgrade, reducing technical debt etc.) or time-sensitive projects. Hopefully, you’ve been able to narrow down your list through this process of elimination. This is where a prioritization framework will come in handy. My go-to is the impact/effort matrix. It is very similar to ICE and RICE but simpler and more visual. For each initiative, assign an estimated impact to a measurable goal and a level of effort. Make sure to collaborate with your engineering and design counterparts when evaluating each initiative. This will reduce the chance of your own bias getting in the way and lead to better prioritization. For those initiatives left on the cutting room floor, think of a way you could still make some progress—is there an MVP you could run to learn something while the teams are working on the selected initiatives? There might be a low-cost way to validate assumptions via user research or data deep dive so that by the time you go through this exercise again, you are able to make a more informed decision.
...Read More
12920 Views
Mckenzie Lock
Mckenzie Lock
Netflix Director of ProductAugust 4
I’ll skip the obvious things - pay well, set a vision, growing company, skill building, career pathing - and highlight some under-rated ones: * Hire well and have high talent density. Most people who choose a career in Product Management are motivated by self improvement - being around other talented PMs who they admire and who push their thinking is motivating. * Stay lean. This may seem counterintuitive - isn’t it good to have enough PMs? Honestly, no. If you hire well you want to give people room to grow and stretch. The worst thing you can do is to staff up too quickly, only to have frustrate your stars who are ready for more in a year (or worse yet, sudden shift in the business which requires you to scale back projects). Having too many PMs will also lead to more work being generated, you then need to resource. It’s far better to have PMs that have 20% too much to do than 20% too little. My rule of thumb is: everyone should be just uncomfortable enough with their scope that they drop a few things, but not so uncomfortable that they burn out. * Autonomy. People choose a career in product management because they want to make or be at the center of product decisions. Allowing them to do so is one of the most important things you can do to keep them motivated. As a people leader your jobs is to set goals, give context, guide, and identify blindspots. It’s not to operate the product for the PMs on your team. At Netflix we have a value, “Context over control” - leaders should focus first & foremost on setting context so others can make decisions vs. making decisions for them. * Actually care about them. When I think about the best managers I’ve had they have one intangible thing in common - I felt on a deep level that they actually, genuinely cared about me. This had a ripple effect on every part of my job because I felt supported, was calmer, and did better work. Caring looks like regularly thinking about the growth & success of another person without being asked to. It looks like advocating for or elevating behind the scenes, especially if they are in a disadvantaged position. It’s something that you can’t fake.
...Read More
7931 Views
Katherine Man
Katherine Man
HubSpot Group Product Manager, CRM PlatformApril 12
The ideal product manager to engineer ratio can vary from company to company and even team to team, but it usually depends on the company size, product complexity, the skill level of the engineers, and the role scope of the product manager. A general rule of thumb is 1 product manager for every 5-10 engineers. * 1:5 - This is common in startups or small teams where the product manager may need to be in the details. * 1:10 - As the team and company grows, a product manager may manage larger engineering teams. Sometimes it's one large team or multiple engineering teams. Since product managers don't have time to be in the details for every project, they are expected to work at a higher level on setting product vision and direction rather than detailed product requirements. It is common for senior product managers to manage multiple teams. * 1:7 - This is the sweet spot where a product manager can still get into the details of a project while also having a lot of impact with a team of this size.
...Read More
1280 Views
Marion Nammack
Marion Nammack
Braze Director of Product ManagementFebruary 9
Let’s say that a product team and an executive team are aligned on the goal of improving customer satisfaction with the product (measured by a CSAT survey). The product team will then do research and perform experiments to validate the best way to impact customer satisfaction. Including executives in the research process via stakeholder interviews is a great way to get input early - executives are viewing things from a much different perspective than team ICs and often have great ideas. When the team prioritizes opportunities to pursue, the framework they use for prioritization can also be used to convey their point of view on the best way to impact customer satisfaction. If an exec suggests making an adjustment to the roadmap during the team’s roadmap review, seek to understand why and dig into their thought process. Then, seek the truth. Is there a quick way to validate or invalidate the feedback? What does the objective evidence point towards as the best opportunity to impact the goals? For more on this topic, I recommend “Cracking the PM Career” by Jackie Bavaro which has a chapter on working with executives.
...Read More
8948 Views
Apurva Garware
Apurva Garware
Upwork VP Product and GMApril 28
1. Ability to communicate well - Someone told me early in my career: The single most important PM skill he looks for when hiring a PM is communication. Communication is really a proxy for building trust, driving alignment, having healthy debates when there’s conflict and committing to a path forward. That’s all under the hood of good communication, and is instrumental in driving product teams forward. 2. Data driven mindset - relevant to qual as much as to quant. Ask yourself and teams the right questions. Become familiar with qualitative research tools, understand what your dashboards need to look like, and get your dashboards in place. Be empowered to make data-driven decisions. 3. Ruthlessly prioritize - every day you have more you want to do than you will have time to do it. That’s just the reality. Every human has 24 hours, and one can’t change that. Make sure you prioritize your team and the team's time and resources.
...Read More
9236 Views
Zeeshan Qamruddin
Zeeshan Qamruddin
Cloudflare Sr. Director of Product | Formerly Segment, WeWork, AirbnbApril 13
At the company level, there are a few different methods of communications to keep everyone abreast of updates: 1. Product Notification emails (Ad Hoc) - These emails have a set template and allow product teams from around the company to share updates to their areas in a digestable format as major features go out of the door. 2. Product Newsletter emails (Weekly) - The weekly newsletter summarized major product updates and initiatives to all product team members. 3. Quartery Business Review meetings (Quarterly) - These larger meetings gather key parts of the business to talk through major updates each quarter, including an opportunity for the C-Suite to interact with and pose questions to respective teams. 4. Quarterly Kick-off meetings (Quarterly) - These meetings are specific to our Product Area and include our stakeholders; each team in Fintech is able to share wins from the prior quarter and plans for the coming quarter. 5. Slack Updates (Ad Hoc) - For major releases, the PM will often post a message in our global product channels to notify the broader group of the change. This allows an opportunity for the team to be recognized, as well as others to be informed about the update. 
...Read More
2307 Views
Rupali Jain
Rupali Jain
Optimizely Chief Product OfficerMarch 2
While there are different specific metrics that marketing and product teams track for product launches, what's critical is the alignment between the two and agreement on the metrics to track prior to the launch. Some examples of metrics tracked by each team: * Product team: Satisfaction, usage by users and individual accounts, full funnel from a user trying the feature to actually using it * Marketing team: % of reps enabled on the new product, leads generated, competitive win rate changes * Metrics that require deep partnership: Number of customer stories/references for the capability
...Read More
2426 Views