Krishna Dey Note
Meeting design checklist
A recurring meeting should earn another quarter. Most survive on habit.
On Custom Integrations, sprint calls used to absorb the implementation team in status reporting. I pulled them out of those calls and moved planning onto velocity and written work. The meeting got smaller. Delivery got more predictable. That is the bar.
Before a recurring meeting survives another quarter:
- Does it produce a decision, a commitment, or a shared view that written artifacts do not already give us?
- Is everyone in the room tied to that outcome, or are they audience?
- Could written prep replace the first twenty minutes?
- Is the cadence matched to how often the work actually changes?
- What would break if we cancelled it for two weeks?
If the answer to the last question is “nothing,” kill it. If the answer is “we would lose the only place state is visible,” that is not a meeting problem. That is a system problem, and a weekly call is covering for it.