design-an-operating-rhythm

# design-an-operating-rhythm Give each forum a distinct decision purpose and connect daily, weekly, monthly, and longer-horizon work. ## Procedure 1. Define organizational outcomes, planning horizons, decision rights, teams, time zones, and current pain. 2. Inventory recurring meetings, reports, reviews, planning cycles, and informal escalation paths. 3. For each, record purpose, inputs, decisions, participants, outputs, owner, frequency, and actual value. 4. Map decisions and signals to the shortest useful cadence; separate coordination, review, planning, learning, and governance. 5. Remove duplicates and status forums whose work belongs in an accessible system of record. 6. Design information flow so one forum's output becomes another's explicit input. 7. Protect focus time, working-hour boundaries, accessibility, preparation time, and decision latency. 8. Pilot the rhythm, measure attendance burden, decision completion, overdue actions, and unresolved escalation. 9. Review and retire forums that do not produce their stated outcomes. ## Failure plan - Do not equate more visibility meetings with better control. - Never require one region or caregiving group to absorb all time-zone cost. - If authority is unclear, fix the governance gap rather than adding a coordination meeting. - Preserve incident, personnel, and confidential review paths outside broad forums. ## Done - Every recurring forum has a distinct purpose, owner, inputs, decisions, and outputs - Duplicate work and total meeting burden are reduced or explicitly justified - Pilot evidence and a scheduled review confirm the cadence is operating