Team Rituals

Scope

Covers

• Designing a small set of high-leverage team rituals that drive alignment, execution, learning, and belonging
• Turning rituals into an operating system (not “more meetings”): named rituals, clear owners, repeatable templates, and explicit outputs
• Creating “Golden Rituals” that are Named, Templated, and Known by every new hire by their first Friday

When to use

• “Our meetings are chaotic; design a better team cadence.”
• “Define our team operating system / rituals / ceremonies.”
• “Create named, templated Golden Rituals and a one-pager for onboarding.”
• “We need better alignment and decision velocity without adding meeting load.”

When NOT to use

• You need to define team culture code, values, or norms first (use building-team-culture — rituals should express decisions you’ve already made about culture)
• You need to facilitate or improve a single meeting or workshop (use running-effective-meetings — this skill designs an end-to-end ritual system, not one meeting)
• You need to set up product operations cadence or cross-team coordination (use product-operations)