AgentSkillsCN

Single Consciousness Roadmap

一种全公司统一运作的滚动两年期路线图规划框架，各条产品线同步发布、协同推进。当企业虽高频交付，却始终未能赢得用户关注时，或当工程与市场部门步调不一致时，不妨尝试这一模式。

SKILL.md
--- frontmatter
name: Single Consciousness Roadmap
description: A planning framework where the entire company operates off a single, rolling two-year roadmap with synchronized releases. Use when shipping frequently but customers aren't noticing, or when engineering and marketing are out of sync.

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

code
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