gtm-command-center
Applies when one operator's work is scattered across many tools and nothing shows the whole day in one place. Produces a single personal operating surface - the lanes that matter, refreshed on a cadence - and one daily roll-up of only what needs that person today.
A command center is not another tool to maintain. It is a read-mostly mirror: it pulls the current state of each lane you already work in and lays it on one screen, so you stop tab-hopping to reconstruct your own day. The discipline that makes it work is subtractive - what you leave off matters more than what you put on.
Build it
- List the lanes, then cut half. Write down every surface you check in a normal day. Keep only the lanes where you personally take action - the task board, the outreach queue, the research digest, the content/publishing queue, the events or presence lane, a pipeline snapshot. Drop anything you only monitor. The lane catalogue and the data contract each lane needs are in
references/lanes.md. - One source of truth per lane. Each lane points at exactly one system of record and mirrors it. Never let a lane hold state that also lives somewhere else - the moment two places disagree, you stop trusting the surface and go back to the tabs. The build patterns (read-mostly aggregation, refresh cadence, single-source rule) are in
references/build-guide.md. - Keep it read-mostly. The surface shows and links out; it does not become the place you edit everything. A dashboard that turns into another editing tool is just one more thing to keep in sync. Allow only the few low-friction actions that keep you on the surface (mark done, add a note); everything heavier links back to the system of record.
- Wall off anything teammate-facing. If any part of this surface is ever shown to teammates, a boss, or clients, it must carry none of your private working notes, raw scores, or internal labels. The clean-room separation - private working surface vs shareable view - is in
references/clean-room.md.
Run it daily
The payoff is one morning read that answers a single question: what needs me today. Assemble the roll-up across lanes, rank by what only you can move and what has a clock on it, and suppress everything that is merely in progress. The assembly method, the ranking rule, and what to surface vs suppress are in references/morning-rollup.md.