build-an-operating-cadence

# build-an-operating-cadence Each forum must have a distinct decision purpose and controlled inputs. ## When to use - Use for a team, program, portfolio, service, launch, or cross-functional operation. - Do not create meetings for information that can be consumed asynchronously. ## Procedure 1. Map recurring decisions, information latency, stakeholders, legal or financial calendars, and operational rhythms. 2. Inventory existing meetings, reports, dashboards, decisions, actions, overlaps, and gaps. 3. Design daily, weekly, monthly, quarterly, and event-driven forums only where their decision clocks require them. 4. Define purpose, chair, participants, input owner, pre-read, metrics, agenda, decision rights, output, and service level for each. 5. Connect risks, issues, actions, dependencies, finances, people, customers, and strategy through one source of record. 6. Set cancellation, delegation, asynchronous, urgent escalation, and accessibility rules. 7. Pilot, measure preparation time, decision latency, attendance, action closure, and duplicate effort. 8. Retire low-value forums and review cadence as the operating model changes. ## Done - An operating cadence document records decision map, forums, inputs, participants, authority, outputs, timing, records, and escalation - Overlap, calendar, decision-latency, accessibility, action, attendance, cancellation, and retirement checks verify value