alexe-ev Design Operating Cadence
Purpose
Help teams design a structured operating cadence that keeps planning, execution, and alignment running smoothly across product, engineering, and design.
Skill type
Conceptual skill
Use this skill when
- A team has no consistent operating rhythm
- Meetings are too many, too few, or poorly structured
- Planning and review cycles are misaligned with delivery
- A new team or function needs an operating model
Do not use this skill when
- The goal is a single meeting agenda or facilitation (out of scope)
- The goal is project-level delivery planning (use plan-delivery-collaboration)
Required inputs
- Team structure (product, engineering, design, leadership involved)
- Current state of the operating process (even rough description)
Optional inputs
- Team size
- Current pain points
- Planning horizon (quarterly, 6-week cycles, etc.)
- Stakeholder reporting requirements
Upstream context
Works best when:
- Goals and OKRs are defined
- Team structure is known
Downstream handoff
Output can feed:
- align-cross-team-communication
- manage-tooling-documentation
Instructions
- Identify all recurring team needs: planning, execution review, retrospectives, stakeholder updates.
- Design the meeting cadence: frequency, duration, attendees, goal for each.
- Define the planning cycle: how often, what outputs, who is involved.
- Define the review and reporting cadence.
- Identify where decisions are made and who makes them.
- Design the async communication norms to complement meetings.
Output
Provide:
- Meeting cadence design (recurring meetings with frequency, duration, goal, attendees)
- Planning cycle design
- Review and reporting schedule
- Decision-making framework (who decides what)
- Async communication norms
- Known failure modes and mitigations
Risks / caveats
- More meetings is not more alignment — quality over quantity
- Cadence design must match team size and velocity
- Leave room for unplanned work — don't over-schedule teams