Clusters

A cluster is a territory you've decided to own: a group of related topics you intend to cover properly rather than glance at. Clusters are where strategy actually enters the product: Topics shows you what the market asks, and a cluster is you committing to answer a coherent slice of it.

It's also the default path into production. Most work reaches a brief through a cluster rather than through a single opportunity picked off a list.

Reference

The header summarises the whole set: total clusters, estimated monthly demand, opportunity count, opportunity demand, briefs in progress, and pages published.

Each cluster row carries:

Opportunity demand often exceeds cluster demand. That isn't an error: opportunities include long-tail queries beyond the topics that defined the cluster.

Each band is its own group, with its own cluster count and demand subtotal. Empty bands are hidden, so a workspace using only Now and Next looks like a two-band screen.

Row numbers are position within a band, not priority. Rows sort by demand descending, then alphabetically. Priority lives in the band header: the number beside a cluster says nothing about how it ranks against the one below it.

The funnel columns are a diagnostic. High demand with many opportunities and no briefs is a cluster you committed to and never started. Many pages with low demand is one you over-served. Reading across a row is faster than any report.

Why it works this way

• Why committing to a few compounds