# Run the Team Operating Cadence

Status: draft · v0.1.0 · Manager System
draft reference — not a fitted standard

Run the minimum recurring planning, coordination, decision, learning, and improvement mechanisms needed to keep team work visible and moving.

## Purpose
Synchronize work and decisions at the rhythm the operating system requires without turning management into a stack of status meetings.

## Steps
1. Design the cadence system — Match recurring mechanisms to the team’s natural work and decision cycles.
2. Prepare the operating state — Make current evidence available before synchronous attention is consumed.
3. Orient to outcomes and priorities — Create shared situational awareness without turning the event into serial status narration.
4. Coordinate work and dependencies — Protect flow across people, disciplines, systems, shifts, and connected processes.
5. Make decisions and escalate constraints — Move issues through explicit authority instead of allowing repeated discussion.
6. Close commitments and communicate — Translate the cadence event into one authoritative operating state.
7. Review and improve the cadence — Keep recurring mechanisms useful as work and context change.

## Connections
- upstream: Establish the Manager Operating Role (/processes/establish-manager-operating-role) — trigger: The Manager Operating Charter launches or changes.
- downstream: Manage Team Capacity and Priorities (/processes/manage-team-capacity-and-priorities) — trigger: The cadence identifies a capacity or priority decision.
- downstream: Enable Decisions and Escalation (/processes/enable-decisions-and-escalation) — trigger: A decision requires focused work or authority outside the cadence event.
- downstream: Run Manager Check-ins and Feedback (/processes/run-manager-check-ins) — trigger: A matter requires an individual operating conversation.
- downstream: Review Manager-System Health (/processes/review-manager-system-health) — trigger: The manager-system review point or material signal occurs.

## Measures
- Cadence operating value: Combined review of decisions, resolved dependencies, commitment reliability, participant evidence, outcome movement, and time cost; not meeting satisfaction alone.
- Material-item closure quality: Material agenda items with complete state, owner, timing, and source update divided by all material agenda items.
- Decision and dependency flow time: Elapsed time from ready state to decision or acknowledged dependency outcome, by type, authority, and wait cause.
- Authoritative state adoption: Applicable items sourced from and closed in authoritative systems divided by all applicable items.
- Cadence exception pattern: Exceptions by mechanism, type, owner, severity, cause, recurrence, and disposition.
- Attention, access, voice, safety, quality, and privacy guardrail: Context-specific review of time load, participation, shifts, access, voice, safety, quality, privacy, and participant feedback; not a causal or legal conclusion.