top of page
Search

Rituals That Actually Ship Work



If you work in knowledge work long enough, you’ll see rituals drift from helpful to hollow. Standups become story time. One-on-ones turn into CYA updates. And somewhere in there, someone puts on the Scrum Master headdress and we all pretend we’re aligned… even as the work wobbles.


Here’s the thing: rituals aren’t the problem. Rituals without results are.

I used to think of rituals like baseball superstitions — lucky socks, tap the plate twice, don’t step on the foul line. Fun, sure. Predictive? Not really. In software and services, our “superstitions” look like daily syncs, QBRs, and backlog grooming. We show up because we always have. We talk because silence is awkward. And we leave with the same fog we walked in with.


Then we tried something simple with our delivery team: rotate who owns the standup. On paper, nothing changed — same calendar slot, same people, same goal. In practice, everything changed. When a different person facilitates, all the “we just kind of know where to click” gaps light up. Which dashboard? Which metrics? Whose rock is it? And my favorite surprise: we added a scribe. I imagined action items. Our teammate started capturing the updates themselves. Better. Tighter. Shareable. The ritual grew meat.


Process debt isn’t caused by too many rituals — it’s caused by rituals that aren’t serving both sides. If a standup only feeds the manager’s report, the team tunes out. If it only feeds the team’s weeds, leadership gets lost or insecure and starts word-salading. Either way, the ritual survives while the result dies.


So we tightened where it matters and stayed loose where it counts.

Tight: We wrote a tiny playbook: Monday, Wednesday, Friday each have a purpose. We listed the 3–5 checks that take 20 seconds each — time entry filled? blockers tagged? capacity vs commitments visible? These micro-hygiene items keep the engine clean. You don’t need a sermon. You need a checklist.

Loose: We left breathing room for “what’s new/what’s next.” If nothing’s critical, we skip it and give time back. If something novel hits — a client asking for five hours “right now” via Slack, the modern drive-by — we decide as a team, not as distracted individuals. Ritual creates a place for those exceptions so they don’t hijack the day.


The manager’s job got clearer too. In high-functioning teams I’ve loved, there was always a single whiteboard (literal or digital): who asked for what, what it is, and who’s got the rock. The manager leaves that ritual ready to defend capacity upstream — “we’re fully deployed” — or pull the next priority. That’s not ceremony; that’s airflow for work.


A couple more notes that helped:

  • Two-party agreements. Every recurring meeting answers two questions: what does the manager need to steward the system, and what do the makers need to ship? If the agenda can’t serve both, fix the agenda — not the people.

  • Make the ritual visible. Humans hold 5±2 things in working memory. Write the flow down. Link the dashboards. If your ritual requires tribal knowledge to run, it’s not a ritual — it’s a personality.

  • Recognition is a ritual, too. Every Friday we highlight wins and breakthroughs. Not performative kudos — specific recognition that teaches the team what “good” looks like. It bonds the group and reinforces outcomes, not theatrics.

  • Change the ritual without drama. The world shifts. So should the doc. If the standup needs a new metric, add it. If a section adds no value for two weeks, kill it. Iteration is not failure; it’s hygiene.


Rituals are scaffolding for results. They reduce cognitive load, make priorities legible, and give the team a shared place to push from. When they drift into superstition, they’re just noise. When they’re designed to serve both the system and the makers, they become the quiet, boring, reliable engine behind great weeks.


Process Debt Truth: most teams don’t suffer from a lack of rituals — they suffer from rituals that don’t earn their keep. Make yours earn it.

 
 
 

Comments

bottom of page