Ritualist
The standup is about connection, the AI report is about visibility
The Ritualist adds AI-powered ceremonies on top of existing ones without ever subtracting. The old standup continues because it always has. The new AI status report runs alongside it because the Ritualist believes in progress. The result is twice the process for the same output, and a team that spends more time in ceremonies than in coding.
- Symptom
- Calendar density far exceeding team size. Multiple status artifacts with overlapping information. Process documentation that reads like geological strata. When someone proposes eliminating a redundant ceremony, the Ritualist produces an airtight justification. AI-powered reports that summarize other AI-powered reports.
- Why it matters
- The redundancy tax is paid in developer hours and morale. Every duplicated process costs time directly and indirectly through context switching and calendar fragmentation. The AI-powered additions feel free because the bot generates the report automatically, but someone still has to read it — or the report exists purely to be ignored.
- What the chapter gives you
- How to conduct a process audit with the consumer question, why sunset-by-default beats addition-by-default, and how to frame process reduction as process improvement so the Cleric can accept it.
Parent Class
From Volume 1 of The AI Developer's Field Guide
Read the full chapter in The AI Developer's Field Guide.
Get the book
Or choose your store:
Recognize this one in your codebase?
The book has the full chapter, the symptoms, and the interventions.