---
title: "Product Management"
description: "17 posts about Product Management, summarised, each linking to the original."
---

# Product Management
> 17 posts about Product Management, summarised, each linking to the original.

## Articles

### [Intercom&#x27;s Paul Adams on product - The Intercom Blog](https://yomu.fyi/post/intercom-x27-s-paul-adams-on-product-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 13, 2026
- Type: Explainer

Paul Adams, VP of Product at Intercom, shares product management principles from his experience at Google and Facebook, where he worked on Gmail, YouTube, and Facebook Ads. He advocates for small, resource-constrained teams with a 1:1:5 ratio of product manager, designer, and four to five engineers, arguing that limited resources force focus on what matters. Adams introduces a ‘666 roadmap’ framework: a six-year vision, six-month strategy, and six-week execution cycles to balance long-term goals with daily work. He emphasizes aiming for 10x improvements rather than incremental 10% gains, and predicts a shift from app icons to apps as services, citing WeChat as an example. For startups, he advises ignoring annual tech predictions and instead focusing on long-term vision to avoid distraction.


### [Insights and lessons from some of the best people in product - The Intercom Blog](https://yomu.fyi/post/insights-and-lessons-from-some-of-the-best-people-in-product-the-inter.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 12, 2026
- Type: Explainer

The post compiles insights from Intercom’s 50th podcast episode, featuring product leaders Bob Moesta, Julie Zhuo, Michael Pryor, and Jason Fried on topics from customer jobs to pricing and product overhaul. Bob Moesta explains that new products always replace existing consumption; understanding what customers stop doing reveals the job to be done, as there is no new time in the world. Julie Zhuo describes a hierarchy where utility is foundational, then ease of use, and finally emotional appeal differentiates products when utility is equal. Michael Pryor shares that Trello initially avoided charging but user fear of shutdown forced them to introduce a simple pricing model, and they debated per-user versus flat fees. Jason Fried advocates for periodic ground-up rebuilds when new ideas cannot be retrofitted, supporting old versions indefinitely and not forcing upgrades.


### [6 Keys to Getting High-Quality &amp; Useful Customer Feedback](https://yomu.fyi/post/6-keys-to-getting-high-quality-amp-useful-customer-feedback.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Explainer

The post outlines six keys for collecting high-quality customer feedback: the type of customer, prompted vs. unprompted feedback, motivations, volume, repetition, and stakes. Loyal or heavy users provide more valuable feedback, and unprompted feedback often reveals unknown issues, while customers are motivated to give feedback when they have extreme experiences, leading to a J-curve distribution. Methods for collecting feedback include live chat, short surveys, and social media, and a seven-step analysis process categorizes feedback by type, theme, and code to prioritize insights. Volume protects against recency bias, repetition indicates unresolved basics, and high-stakes feedback like security loopholes requires immediate action. A case study of Albacross shows how using NPS surveys and automated follow-ups via Intercom doubled their NPS score from 12 to 30 and increased reviews on Capterra.


### [Make Sales &amp; Product meetings a win-win](https://yomu.fyi/post/make-sales-amp-product-meetings-a-win-win.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Tutorial

Fortnightly sales-product meetings at Intercom use a structured feedback loop to align product strategy with market needs. Sales teams first meet internally, using a shared Google Doc to categorize recent feedback and prioritize three to five items backed by concrete data such as the customer’s job title, revenue at risk, and competitor presence. The cross-functional sync includes representatives from each sales segment (SMB, Mid-Market, Enterprise) plus product owners, who ask context-gathering questions and share roadmap progress. This method replaces ad-hoc feature requests with evidence-based discussions, helping product understand customer impact and sales set realistic expectations with prospects. The process has resulted in popular features like automatic conversation routing to the right team and stronger cross-functional collaboration between sales and product teams.


### [The right way to respond to feature requests - The Intercom Blog](https://yomu.fyi/post/the-right-way-to-respond-to-feature-requests-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Tutorial

Customer support teams frequently encounter feature requests that reveal gaps between a product and user goals, and responding effectively requires a rigorous framework. The post categorizes these requests into three types: unresolved problems with existing features, improvements to existing features, and brand new feature requests. For each type, it recommends a tailored response: educate customers on workarounds for problems without promising specific fix dates, suggest alternative existing functionality for improvements, and honestly decline new requests while acknowledging the gap and offering third-party solutions like Zapier or YouCanBookMe, sharing context about limited engineering resources. Prioritization should also consider customer lifecycle, high-value users, implementation difficulty, and feedback volume to balance satisfaction with engineering resources and long-term strategy. Closing the loop by tagging conversations in Intercom and sharing monthly customer voice reports with product managers ensures feedback drives roadmap decisions and builds long-term customer success.


### [Does your support team know more about your product than you?](https://yomu.fyi/post/does-your-support-team-know-more-about-your-product-than-you.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Problem & solution

Customer support teams interact with customers daily and possess valuable product and customer insights that product teams often overlook. Treating support as an outsourced function or ignoring their conversations wastes unsolicited feedback that differs from survey data. Intercom tags every support conversation with team and category tags to make feedback actionable, enabling product teams to create dashboards, spot trends, and explore conversations for insights. For example, tagging ‘product confusion’ revealed an onboarding issue where customers saw nothing if they only completed one of two setup steps, leading to a pop-up that told customers exactly what they needed to do and reduced those conversations. Product teams also use tags like ‘unaware’ to improve feature discoverability, track bug reports via a GitHub integration, and compile quarterly ‘customer voice reports’ of top feature requests while closing the feedback loop with customers.


### [Your product is already obsolete - The Intercom Blog](https://yomu.fyi/post/your-product-is-already-obsolete-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 9, 2026
- Type: Explainer

Technology products inevitably become obsolete as industries shift, and failing to adapt can kill a business faster than most founders expect. Success breeds complacency, which breeds failure, making paranoia a necessary survival trait for everyone in tech. Historical examples like satnav manufacturers gutted by the iPhone and telcos disrupted by WhatsApp show that customers will abandon an incumbent for a simpler, faster way to achieve their goals. To avoid this fate, Intercom advocates thinking of a product as a flexible system rather than a set of screens or user flows, allowing it to integrate across new mediums. This systems approach enables the product to remain relevant through multiple technology cycles by focusing on helping customers make progress in their lives.


### [Inside Intercom New York startup panel - The Intercom Blog](https://yomu.fyi/post/inside-intercom-new-york-startup-panel-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 8, 2026
- Type: Explainer

At an Intercom World Tour panel in New York, founders from Augment, an AR platform; Greenhouse, recruiting software; and Hello Alfred, on-demand home services, shared lessons on building emerging technologies. Mike Boufford of Greenhouse described fixing bugs by chatting with customers and deploying fixes within minutes, demonstrating how product and support intertwine. Christian Bjelland of Hello Alfred explained that their service must advocate for customers when real-world problems like lost laundry occur, requiring quick reactions. On growth, Boufford advised proving product-market fit before raising money, while Bjelland stressed dense, sustainable growth in specific zip codes to maintain quality. Lindsay Boyajian of Augment noted that no AR platform existed before, so constant user feedback and rapid iteration are critical to building a useful product.


### [2021 in conversation: Learnings from the podcast - The Intercom Blog](https://yomu.fyi/post/2021-in-conversation-learnings-from-the-podcast-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 8, 2026
- Type: Explainer

In this 2021 year-end compilation, Intercom reflects on insights from its podcast series Inside Intercom, featuring conversations with business leaders and pioneers like CEO Karen Peacock, Hubert Palan from Productboard, and Amanda Renteria from Code for America. They discuss leadership, product strategy, customer experience, and the challenges of running a business during the pandemic, including building world-class customer experiences and addressing diversity gaps. Speakers like Farhan Virji from Later share how B2C support strategies can inform B2B teams, while Will Larson of Calm explores technical leadership careers beyond management. The episode also marks Intercom’s 10th anniversary, with founders Des Traynor and Paul Adams reflecting on maintaining speed as the company scales and avoiding unnecessary processes that slow progress. Zanade Mann and Janeen Uzzell offer insights on allyship, diversity, and ensuring knowledge equity in government services, as well as the importance of advocating for underrepresented groups.


### [Intercom&#x27;s New Book: A Guide to Project Management](https://yomu.fyi/post/intercom-x27-s-new-book-a-guide-to-project-management.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 8, 2026
- Type: Announcement

Intercom published its first book, ‘Intercom on Product Management’, consolidating and updating their best articles from over two years on fundraising, pricing, process, design, and product management with new content to bridge gaps and clarify concepts. The book delivers practical, grounded advice for anyone who works with products, directly addressing the lack of value in abstract and clichéd guidance. The team optimized the reading experience across all devices, creating epub, mobi, and PDF formats with careful design, layout, and visuals, crediting Frantisek Kusovsky and Jeff Kriege for their tireless work. The book is free, with a request that readers share it with others, and even regular readers benefit from updated content that removes repetition and clarifies concepts. Intercom views this publication as the beginning of a series, with plans to continue writing and release more books, measuring value by impact rather than length or breadth.


### [Product Teams: How to Build &amp; Structure Product Teams for Growth](https://yomu.fyi/post/product-teams-how-to-build-amp-structure-product-teams-for-growth.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 8, 2026
- Type: Explainer

Intercom shares the process it used to scale its product team from a smaller size to four Product Managers, four Designers, and 25 Engineers over 12-18 months. The process is built on four areas: decision-making guidelines, clear role-based accountability, a lightweight transparent roadmap, and a culture of goal setting. The roadmap has three timeframes: solid releases for the next 4-6 weeks, planned high-level briefs for the following months, and speculative ideas beyond that. Accountability is assigned by role, with the PM responsible for problem analysis and success, the Designer for design quality, and the Engineering Lead for delivery and code quality. Teams set weekly goals tracked in an internal tool called Hustle and daily goals on whiteboards, with weekly demos every Friday to reinforce the cadence of building.


### [Intercom&#x27;s product principles: Start with the problem to achieve better solutions - The Intercom Blog](https://yomu.fyi/post/intercom-x27-s-product-principles-start-with-the-problem-to-achieve-be.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 8, 2026
- Type: Explainer

Intercom’s primary product principle “Start with the problem” guides all its teams to focus on understanding real customer issues more deeply before designing any solutions. The company argues that many businesses fail because they quickly jump to solutions without thoroughly exploring the underlying problem, leading to solutions that often miss the mark, do not match real customer needs, and end up unused entirely. Common pitfalls include insufficient problem comprehension, failing to update problem understanding over time, and solving problems that are too niche, not urgent, or not aligned with customer needs. To counter this, Intercom dedicates about a third of a team’s effort to problem definition before any building begins, using problem statements and customer research. This whole-team approach builds shared understanding, ensures accurate solutions, and allows “porpoising” between problem and solution understanding while defining measurable success metrics upfront to validate impact.


### [Product strategy best practices \[with examples\]](https://yomu.fyi/post/product-strategy-best-practices-with-examples.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 8, 2026
- Type: Explainer

Product strategy requires being great at saying no, not maybe or later, to maintain a cohesive product with well-defined parameters. When a product gains traction, good ideas for features come from customers, colleagues, and oneself, each with reasons to say yes. The post presents 12 common arguments used to sneak features in, such as selective data analysis, feature blackmail, and appeals to anecdote or raw numbers. It argues that even good ideas should be rejected if they do not fit within the product’s purview, as every addition adds hidden complexity and weakens product definition. Saying no to good ideas is the hard part of product decisions, distinguishing a repository of features from a true product.


### [Product Judgment: How to repeatedly create product success](https://yomu.fyi/post/product-judgment-how-to-repeatedly-create-product-success.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 8, 2026
- Type: Explainer

Product judgment is the ability to use your own intuition to repeatedly and accurately predict what customers need, want, and value, and to design and ship the right solution for them. It is not innate but learned through years of deliberate, wide-ranging direct experiences with real customers using your product, covering both the product and the market sides and all customer types. Indirect sources like summarized feature requests, survey data, or recorded interviews cannot create it, only supplement judgment already built through direct contact. You must also deeply know your product by using it yourself to fully interpret customer feedback and ask perceptive questions, and you must continually check your predictions against outcomes to refine your judgment. Building strong judgment requires never-ending customer contact as technology and competitors evolve, is domain specific, and typically demands at least 100 to over 1,000 direct interactions.


### [The Importance Of A Clear Career Path For Product Managers](https://yomu.fyi/post/the-importance-of-a-clear-career-path-for-product-managers.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 8, 2026
- Type: Problem & solution

Product management lacks clear deliverables such as code or designs, making performance reviews inconsistent and overly reliant on peer feedback across multiple managers. Career ladders address this by clarifying role expectations and promotion criteria, enabling fairer and more consistent reviews, though promotion remains nuanced beyond discrete tasks. Intercom’s ladder organizes PM skills into five buckets: insights driven, strategy, execution, driving outcomes, and leadership behaviors, each with two to four discrete areas totaling 17, chosen from real feedback given to team members. Expectations are defined from Associate to Principal level, with execution explicitly tied to R&D principles like starting with the problem, thinking big but starting small, and shipping to learn. The ladder deliberately separates driving outcomes from shipping to ensure PMs focus on impact without sacrificing delivery, and includes leadership behaviors such as communication, collaboration, ownership, and decisiveness.


### [Intercom on Product: The evolution of product management in the age of AI - The Intercom Blog](https://yomu.fyi/post/intercom-on-product-the-evolution-of-product-management-in-the-age-of.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 5, 2026
- Type: Explainer

Product management is at a critical juncture as generative AI reshapes how products are conceived, built, and used. Indiscriminately adding AI is risky; product managers must ensure the technology solves real user problems rather than being an end in itself. Curiosity is essential for driving exploration of generative AI’s new possibilities. A foundational understanding of AI is important, but the ability to collaborate with AI and ML experts is even more critical for bridging technical possibilities with customer needs. The future of product management will be shaped by those willing to learn, adapt, and explore the art of the possible.


### [Intercom on Product: Riding the AI wave in 2024 - The Intercom Blog](https://yomu.fyi/post/intercom-on-product-riding-the-ai-wave-in-2024-the-intercom-blog.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 5, 2026
- Type: Explainer

Intercom leaders reflect on 2023’s generative AI dominance in a podcast, predicting deeper investments, AI-first companies, and hardware transformations like wearable tech and AI-native products in 2024. Standout moments include Paul’s AI holiday using phone camera translation for travel and Emmet’s praise for Nintendo’s Tears of the Kingdom physics innovation. Optimal AI deployment requires careful use-case selection, avoiding misapplication on structured tasks needing human oversight, while wearable tech success depends on seamless lifestyle integration over status. Customer support will evolve from ticket-resolution to a continuous relationship-building model, emphasizing ongoing engagement over finite tasks, with design playing a key role. A key concern is that over-reliance on AI tools as magic wands may erode critical thinking and judgment in product management and complex troubleshooting, where details matter.
