A team gives a status update. It runs twenty minutes. The leader asks a clarifying question. The team answers at length. Nobody is padding. Nobody is covering for weak work. There is just no short answer, because the update wasn’t held to anything short enough to measure against.
The length is a signal. Most organizations treat it as a writing problem.
Why updates expand
An update that has a named outcome to measure against answers one question: what changed relative to what we said we were producing? That answer is bounded. Either something changed or it didn’t. Either the work is closer to the observable evidence of success or it isn’t.
When the outcome wasn’t stated precisely enough to measure against, the update answers a different question: what has the team been doing? That question has no natural boundary. Effort is open-ended. There is always more to say about what happened than about whether it moved the work toward a defined result.
The update grows to fill the absence. It is an accurate report on a condition the work created for itself.
The outcome that doesn’t get named
Most teams define an outcome at the start of an initiative. Few define it with enough precision to make subsequent updates short.
There is a difference between a project title, a deliverable, and a named outcome. A project title is a label. A deliverable is a thing the team produces. A named outcome has two components: what the team commits to produce, and the observable change that proves it mattered. The first without the second is just a task. Together, they give the team a standard specific enough to measure progress against.
The second component is the one that gets skipped. It requires the team to answer a harder question: what will be different in the world when this is done, and how will we recognize it? That question is uncomfortable to answer before the work starts, because it commits the team to a specific standard of success. Teams often defer it. The update length is where that deferral shows up later.
Where the meeting time comes from
Long updates and long meetings share the same root. When the outcome is not named precisely enough to measure against, the meeting has to do the work the named outcome should have done: establish a shared picture of where the work stands and whether it is moving.
That process takes as long as it takes. The leader asks what the update meant. The team explains the context behind it. Someone raises a concern. The meeting expands to accommodate what the record should have held.
When a team meets with a named outcome in place, the question is simpler: are we closer to it? That answer is short. It leads to a decision or it doesn’t, and either way the meeting has somewhere to go.
Guarding the outcome across time
Naming the outcome at initiation is the first step. It isn’t a permanent fix.
Work in progress erodes the named outcome without anyone deciding to let it. Priorities shift. New information arrives. Scope expands without a formal decision. The team continues measuring updates against the outcome, but the outcome has drifted from the one the team committed to at the start.
Updates start to lengthen again. Meetings start to circle. The signal is the same as before: something is missing that the team is compensating for in real time.
The named outcome does its job only when the team returns to it deliberately at each update. Not to restate it, but to test the update against it: does this answer the question of whether we moved toward it? When the answer is no, the outcome needs more precision, or the update does, or both.
The outcome isn’t something the team defines once and files. It is the reference point the team maintains.
That test is the practice. The outcome isn’t something the team defines once and files. It is the reference point the team maintains.
What to do with the length
If your team’s updates are running long, or your status meetings are starting with clarification rather than decisions, the place to look is not the update format. It is whether the initiative has a named outcome precise enough to measure against.
The question that does that work is this: what observable change will prove this was worth doing? If the team can’t answer it cleanly, or the answer is vague enough to fit almost anything, the update will stay long. Make the answer specific enough that the team can say yes or no to whether progress happened this week. Then write the next update against it.
The length will tell you whether you got there.
👉 Find out where your team’s work is losing ground: https://amykennedyleadership.com/choose-your-diagnostic/