Write the operating cadence for a team that outgrew standups

Team: {{size, roles, how it's split, remote or not}}. Current meetings: {{list them all with frequency, length and attendees}}. What's actually going wrong: {{decisions taking too long / people surprised by things / rework / nobody knows priorities}}.

Design the operating cadence.

For each rhythm — daily, weekly, monthly, quarterly — tell me: what it decides, who must be there, who must not, how long, what the input document is, and what output proves it happened. Anything that produces no decision or document gets deleted.

Then map my current meetings onto it: which ones survive, which merge, which become an async document, and which die. Be specific and be willing to kill a meeting people like.

Address the things cadence usually misses: how a decision gets made when the meeting isn't for three days, how information reaches people who weren't in the room, and where bad news is supposed to surface early.

End with the rollout — what to change in week one, and what to leave alone until the first change holds.