Each morning the team gathered to speak of yesterday, today, and blockers.
A new developer asked the senior, “Why do we do this every day?”
The senior replied, “So that we remember we are not alone.”
The developer asked, “But I am blocked by nothing and working on the same thing as yesterday.”
The senior said, “Then say so. The silence between us is also information.”
The Teaching Unfolds
The daily standup is one of the most debated rituals in software development. Too long, too short, too formal, too casual. Teams argue about whether it should be synchronous or asynchronous, in person or remote, fifteen minutes or five. And yet the ritual persists, in almost every team, in almost every organization, because something in it is doing work that the debate about its format tends to miss.
The new developer in this koan is asking a reasonable question. If nothing has changed, if there are no blockers, if the work continues as planned, what is the point of the ceremony? It feels like theater. Like a form that exists to satisfy a process rather than to serve the people in it.
The senior’s first answer cuts through the procedural framing entirely. We do this so that we remember we are not alone. Not to update a board. Not to satisfy an Agile framework. Not to give a manager visibility into progress. We do it because software development, for all its collaborative trappings, is a deeply solitary practice. Most of the real work happens inside a single mind, in the private space between a problem and a cursor. The standup is a small, daily act of surfacing. We come up for air together.
The second answer goes deeper. When the developer reports that they have nothing new to report, the senior does not dismiss the concern. Instead, the senior reframes what communication actually is. The silence between us is also information. A developer who is unblocked and steady is not withholding news by saying so plainly. That steadiness is itself a signal. The team learns something from it. The project breathes easier because of it.
This is a teaching about the nature of presence. We often think of communication as the transmission of problems, changes, or requests. But the absence of those things is also a communication. “I am here, I am steady, I am working” is a gift to a team that is trying to hold a shared picture of a complex system in progress.
There is also something here about why ritual matters even when its content is thin. The standup is not just a transfer of information. It is a practice of showing up. Of orienting together before dispersing into separate terminals and separate problems. The content of what is said is almost secondary to the act of gathering. Many developers who have worked in deeply effective teams report that the standup they remember most clearly is not the one where a critical blocker was surfaced. It is simply the feeling of knowing, each morning, where everyone stood.
The koan does not argue that standups should be long, or emotional, or vulnerable. It argues only that they should be honest. Say what is true. Even if what is true is that there is nothing new to say. The team will hear it.