---
title: "Roadmap"
description: "2 posts about Roadmap, summarised, each linking to the original."
---

# Roadmap
> 2 posts about Roadmap, 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.


### [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.
