Ritual Bankruptcy: What Should Your Team Stop Doing?

A team can inherit a full calendar and no memory of why it exists. The Friday celebration once marked a hard launch. The daily check-in once coordinated a temporary crisis. Years later, declining the invitation feels disloyal, even though the original problem has disappeared. Ritual bankruptcy is the point at which the obligation outlives the benefit.

Review the function before the format

List recurring practices, including gatherings, recognition routines, reports, and onboarding ceremonies. For each, name the behavior it was meant to support. 'Build culture' is not precise enough. 'New starters know whom to ask for help' or 'The next shift receives unresolved risks' gives you something observable to protect.

Separate optional cultural practices from required safety, legal, or operational controls. A team cannot simply cancel a compliance check because it feels repetitive. Route those controls through their accountable owner and approved change process. For everything else, calculate the real cost: participant time, preparation, interruption, and who does the unpaid coordination.

The ritual sunset review

1. 1Purpose: what current problem does this solve? Ask the sponsor and participants separately. Disagreement is evidence that the purpose needs repair.
2. 2Benefit: name two recent occasions when this practice changed a decision, prevented a problem, connected people, or helped someone do their job. Attendance alone does not establish value.
3. 3Access: who cannot participate easily because of shifts, location, disability, caring responsibilities, or the unwritten pressure to perform enthusiasm? Ask those people, not only regular attendees.
4. 4Cost: estimate participant-hours per cycle and preparation time. Identify whether the same colleagues repeatedly organize it without recognition or capacity.
5. 5Substitution: if it paused, where would its useful work happen? Name the channel, person, or process before assuming nothing would be lost.

Three decisions, with distinct criteria

• Retire when the problem no longer exists, the practice duplicates another working mechanism, or participants cannot identify a current benefit. Preserve anything needed for continuity before removing the calendar entry.
• Repair when the purpose is still necessary and evidence suggests the format is the problem: wrong participants, inaccessible timing, excessive frequency, or no clear owner. Change one design feature and test it.
• Replace when the purpose matters but the existing format fundamentally mismatches the work. A narrated status round may become an asynchronous update with a short exception discussion; a popularity award may become specific peer appreciation without a competition.

Do not pretend these are objective numerical thresholds. Apply the criteria to actual evidence and let participants challenge the conclusion. A low-cost welcome ritual can matter even when its benefit is relational rather than a measurable productivity gain.

Close the ritual without insulting its history

Use a plain announcement: 'This helped us coordinate during the launch. That phase is over. We are pausing it for two cycles, moving unresolved risks to the handoff log, and asking Jordan to check what we miss.' Thank the people who built it. State the replacement and the review date. Quiet deletion invites people to invent a story about what leadership no longer values.

Give the repaired version a contract

Write five fields: intended behavior, owner, cadence, evidence of benefit, and expiration date. At expiry, renewal requires a short review, not a recurring invitation that extends forever. If the practice is stopped, name who checks for lost information or connection during the pause. Retirement should be reversible when evidence shows something useful went missing.

Finish the review by asking the people doing the work: what became easier, what became harder, and what quietly moved onto someone else's plate? A lighter calendar is not success if the same coordination now happens through invisible overtime. The objective is retiring empty obligation while preserving the behavior worth keeping.