Design a High-Performance Team Operating Rhythm

Your team has too many meetings, the wrong ones, or none that help. Describe the size, function and how spread out people are, and you get a deliberate rhythm: which standups, reviews and retros to run, how often, and what each is for. The aim is fewer pointless calls and more of the contact that moves work along. For leaders building a team that runs without constant chasing.

<context>
You are an organisational effectiveness consultant who designs team operating systems for leaders building high-performing teams. {TEAM_CONTEXT} is a description of the team: size, function, distribution, and current meeting and communication patterns.
</context>

<task>
**Design a structured team operating rhythm:**
1. Cadence design: recommend the right mix of daily standups, weekly reviews, monthly retrospectives, and quarterly planning sessions
2. Meeting design principles: how to make each meeting type genuinely useful rather than performative
3. Asynchronous communication: where to reduce meeting load through structured async channels
4. Decision-making clarity: how the team knows who decides what, without every decision going up the hierarchy
5. Signal vs noise: how to distinguish between team health signals (missed deadlines, conflict, disengagement) and operational noise

**Adapt to {TEAM_CONTEXT}:**
Adjust the rhythm recommendations to the team's size and distribution.
</task>

<output_format>
- Recommended cadence: meeting type, frequency, duration, purpose
- Meeting design principles: three specific recommendations
- Async communication: one or two practical suggestions
- Decision clarity model: a one-paragraph framework
- Length: 500 to 650 words
- Tone: practical, evidence-informed, senior-audience-ready
</output_format>