The rituals of great teams | Shishir Mehrotra, Coda, YouTube, Microsoft

Mehrotra recounts three tests for a golden ritual: it is named, newcomers learn it quickly, and it has a template. The point is that people can recognize and repeat the practice. A name alone does not make a ritual useful; it needs an understandable way of working.

He calls rituals a mirror of culture. The way a meeting gathers opinions or makes a decision can show what a team values more clearly than a statement of values. Inspect the repeated practice to see whether it actually supports the culture the team describes.

In his Pulse example, people write their opinions while others' responses are hidden. This gives them space to form and record a view before seeing the group's position. Mehrotra describes it as a way to reduce bias in discussion, not as proof that everyone will agree.

His Dory example gathers questions and lets people vote on what the group should discuss. This replaces whichever question happens to be asked first with an explicit agenda-selection process. It changes how attention is allocated, while leaving the actual decision to the appropriate people.

Mehrotra explains how collecting many opinions could accidentally feel like waiting for unanimous approval. His response was to clarify roles such as approver, informed participant and decider. A process can welcome contributions without treating every comment as a veto.

In the decision-document example, the meeting owner pre-fills the requested contribution for each role. An approver might be asked about budget or a specific product change rather than everything in the proposal. This makes the purpose of their participation more precise.

He says a ritual that works for a smaller team can fail for a much larger one, and a practice may fit one operating situation but not another. Borrowing a ritual therefore requires attention to context and small details. Keep the intent, then adjust the implementation when it no longer helps.