Centerline: how the operations coach holds weekly cadence

Most operating systems fail because nobody owns the cadence. Centerline is the operations coach that holds it — weekly review, drift detection, accountability — without consuming the founder's week.

Centerline is the operations coach specialist that OPS (the COO exec) manages. It runs three jobs: the weekly review, the drift watch, and accountability followup.

Named after the principle from the Centerline book: every business has a narrow path where work, outcomes, and the people doing the work actually line up. Off the line, the business looks the same on the surface — same metrics, same priorities, same meetings — but the connection between them has frayed.

Centerline holds the line.

The weekly review

Every Monday morning, Centerline pulls the prior week's data: what was prioritized, what shipped, what slipped, what surprised. It runs the comparison against the priorities you set at the start of the week — and against the patterns it's seen across all prior weeks.

The output is a one-page summary delivered to the operator's inbox by 8am Monday:

• 5-7 things that shipped (with the impact, if measurable)
• 1-2 things that slipped (with why)
• 1-2 drift signals (patterns the operator might miss)

The format is fixed. The content is the operator's actual operating reality.

Drift detection

The operator-facing job most operators don't have a system for. Drift is the slow erosion that doesn't show up as a single bad week — a metric trending sideways for the third week, a priority that's been on the list for four weeks without progress, a meeting that's stopped producing decisions.

Centerline's drift watch surfaces these specifically. It says: "this metric has not moved in 21 days; was it supposed to?" or "this priority has been on the list for 4 weeks; is it still real?"

The operator's job is to decide what to do about each drift signal. The system's job is to make sure the signals don't go unnoticed.

Accountability followup

When priorities are set on Monday, Centerline tracks what was committed to. By Thursday, if a priority has no progress visible in the underlying systems (PRs not opened, tickets not closed, deals not advanced), it surfaces a quiet check-in: "this priority has not moved this week; is it still on?"

The followup is gentle. It is also reliable. The operator doesn't have to be the chasing layer.

What it doesn't do

Centerline doesn't make decisions. The decisions about what's important, what to prioritize, what to cut are operator decisions. OPS (the COO exec that manages Centerline) sets the framework; the operator decides the content.

It also doesn't replace the operating system you already have. If you run a weekly meeting, Centerline doesn't cancel it — it gives you the right pre-read so the meeting produces better decisions.

What this looks like for a 25-person operator

The before state: weekly priorities written somewhere (Notion, a doc, a Slack thread). Mondays start with the operator trying to remember what was supposed to ship last week. Drift surfaces only when something explodes.

The after state: Monday at 8am, a one-page summary of last week + drift signals + this week's priorities is in the inbox. The operating cadence runs on schedule. The operator's Monday morning is for decisions, not status.

For most operators, that's 1-2 hours of recovered time per week + meaningfully better decision quality. Same job as a senior COO would do at this scale, at the price of a tool subscription.