单一意识路线图：公司统一产品发布规划框架，实现工程与营销同步

Single Consciousness Roadmap by coowoolf/insighthunt-skills

2 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/coowoolf/insighthunt-skills --skill 'Single Consciousness Roadmap'

项目管理创业产品管理

🇨🇳中文介绍

单一意识路线图

"我们希望打造一家千人规模的公司，但其运作模式看起来却像只有十个人在运作。" — Brian Chesky

核心理念

这是一个规划框架，让整个公司基于单一、滚动更新的两年期路线图运作。这确保了工程、设计和营销部门能够完美同步，实现大规模、统一的发布。

适用场景

公司频繁发布产品，但客户感知度低
工程与营销部门步调不一致
团队拥有零散的路线图，缺乏连贯的叙事
需要创造具有新闻价值的发布时刻

核心原则

1. 滚动式两年规划

维护一个展望未来两年的路线图，每六个月更新一次。近期规划是固定的；远期规划则保持灵活。

2. 指标服从于日历

承诺固定的发布日期（例如，夏季和冬季发布）。这迫使团队做出范围决策，并防止陷入无休止的优化循环。

3. 将发布视为剧集

将产品发布视为电视剧集或书籍章节。将功能打包成一个连贯的叙事，以便营销部门能够有效推广。

4. 完全透明

所有项目必须列入中央路线图（次要基础设施项目除外）。如果不在路线图上，就等于不存在。

如何应用

STEP 1: 定义发布节奏
└── 选择固定的发布窗口（例如，5月和11月）
└── 从发布日期倒推工作

STEP 2: 创建单一事实来源
└── 为整个公司制定一份路线图文档
└── 所有计划必须纳入发布"剧集"中

STEP 3: 将功能打包成叙事
└── 将相关功能分组为"章节"
└── 为每次发布创建营销故事

STEP 4: 强制执行透明度
└── 禁止"影子路线图"或消耗资源的副业项目
└── 定期召开跨职能同步会议

常见错误

❌ 允许团队拥有消耗资源的"影子路线图"或副业项目

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

🇺🇸English

The Single Consciousness Roadmap

"We wanted a company where a thousand people could work, but it'll look like 10 people did it." — Brian Chesky

What It Is

A planning framework where the entire company operates off a single, rolling two-year roadmap. This ensures that engineering, design, and marketing are perfectly synchronized for massive, unified launches.

When To Use

Company is shipping frequently but customers aren't noticing
Engineering and marketing are out of sync
Teams have fragmented roadmaps with no coherent narrative
Need to create newsworthy launch moments

Core Principles

1. The Rolling 2-Year View

Maintain a roadmap that looks 2 years out, updated every 6 months. The immediate horizon is fixed; the distant horizon is flexible.

2. Metrics Subordinate to Calendar

Commit to release dates (e.g., Summer and Winter releases). This forces scope decisions and prevents endless optimization loops.

3. Launches as Episodes

Treat product releases like TV episodes or chapters in a book. Bundle features into a cohesive narrative that marketing can actually sell.

4. Total Visibility

All projects must be on the central roadmap (except minor infra). If it's not on the sheet, it doesn't exist.

How To Apply

STEP 1: Define Release Cadence
└── Choose fixed release windows (e.g., May + November)
└── Work backwards from launch dates

STEP 2: Create Single Source of Truth
└── One roadmap document for entire company
└── All initiatives must fit into release episodes

STEP 3: Bundle Features Into Narratives
└── Group related features into "chapters"
└── Create marketing story for each release

STEP 4: Enforce Visibility
└── No "shadow roadmaps" or side projects
└── Regular sync meetings across all functions

Common Mistakes

❌ Allowing teams to have "shadow roadmaps" or side projects that consume resources

❌ Shipping continuous small updates with no coherent marketing story

❌ Optimizing for velocity metrics over customer impact

Real-World Example

Airbnb's "Winter Release" and "Summer Release" cadence, where they bundle hundreds of upgrades (like Guest Favorites and the new Host Tab) into a single newsworthy moment.

Source: Brian Chesky, Lenny's Podcast

Weekly Installs

Repository

coowoolf/insigh…t-skills

GitHub Stars

First Seen

Jan 1, 1970

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass