The lanes and their data contracts
A lane is one horizontal strip on the command center: one area of your work, mirrored from one system of record. This page lists the lanes a cross-function GTM operator usually needs, what each shows, and the minimum data contract that keeps the lane cheap to build and hard to break.
The rule for adding a lane
A lane earns its place only if you take action in it. If you only watch it, it is a report, not a lane, and it belongs in a weekly review, not on your daily surface. When in doubt, leave it off; an empty-feeling command center you trust beats a full one you skim.
The common lanes
| Lane | What it shows | System of record | You act by |
|---|---|---|---|
| Task board | Your open deliverables, owner-labelled, with a done state | Your project/task tool | Marking done, reprioritising |
| Outreach queue | Drafts and sends awaiting your review or follow-up | Your outreach/sequence tool or drafts folder | Approving, editing, sending by hand |
| Content / publishing queue | Posts, articles, or assets waiting on you to draft, approve, or schedule | Your content calendar or draft store | Approving, scheduling |
| Research digest | The latest signal on your beat - competitor moves, news, mentions | Your research feed or saved searches | Deciding what to act on |
| Events / presence | Upcoming events, who is going, what is committed vs a candidate | Your calendar and events tracker | Deciding attendance, prep |
| Pipeline snapshot | The few deals or opportunities that need you now | Your CRM | One next action per item |
Pick the four to six that match your role. A content-and-comms operator leans on the outreach, content, research, and events lanes; a seller leans on pipeline, tasks, and outreach. Do not ship all six by default.
The data contract per lane
Keep each lane's contract to the smallest set of fields that lets you act without opening the source tool. A workable default per item:
- a title that is legible on its own,
- a stable id so the item can be toggled or annotated without duplicating,
- a state (for example: waiting on you, in progress, done),
- an owner or lane label so a shared view can be built cleanly later,
- a link back to the system of record for anything heavier than a glance,
- optionally a why-now note or a small score, kept behind the item, not shown as a wall of numbers.
The contract is the boundary between the lane and its source tool. If you find yourself wanting a seventh and eighth field, you are rebuilding the source tool inside the lane - stop, and link out instead.
Candidate events vs commitments
One subtlety that trips people up: a lane that lists candidate events (things happening that quarter you could attend) is not a plan. Keep candidates visibly separate from commitments (things you have actually said yes to or spent money on). Collapsing the two makes the surface lie to you about what is real. Label the state, do not infer it.