Most teams can’t answer that question cleanly. They’re certainly busy with the work. But work that is busy and work that is moving forward produce very different results, and the gap between them accumulates until it’s expensive.

Work resets. A team finds itself rebuilding what already existed, often without recognizing that’s what’s happening. I watched this happen to a team I worked with directly. They had been building a long-arc product strategy with serious thinking and real progress over several months. Then an urgent priority was inserted over the holidays. When they returned to the original work, several members believed the strategy had been abandoned. It hadn’t been. But the reasoning wasn’t preserved, the decision wasn’t anchored, and the progress wasn’t stored anywhere retrievable. The work reset as thoroughly as if it had never happened. The strategy owner lost ground and credibility that took months to recover.

This is a work design problem.

Why resets are invisible until they are expensive.

A work reset is rarely obvious. It looks like a long meeting to re-establish what was settled. It looks like a status update that covers the same ground as the last one. It looks like a capable person going quiet in a conversation they’ve already had three times. The cost accumulates gradually in time, in trust, and in energy.

Leaders feel it as unpredictability. Contributors feel it as erosion of their work and energy.

Three things cause work to reset.

Every team I have observed losing ground is losing it through one or more of these:

Context erodes. The reasoning behind a direction, the assumptions that made a decision sensible, the problem a piece of work was meant to solve… none of it persists without deliberate preservation. When attention moves to something else or people change, context fades. When it’s gone, teams don’t pick up where they left off.

Decisions decay. An unrecorded decision is not a settled decision. It’s a position that will be relitigated the next time someone who wasn’t in the room asks a question, or the next time the original participants remember it differently. If a decision cannot survive absence, it was never truly made.

Progress doesn’t compound. Finished thinking that isn’t retained might as well not exist. Teams can work hard across months and find themselves no further along because each cycle begins without the foundation the previous cycle built.

Why capable people don’t fix it.

The people most aware of the waste are already compensating for it. They keep personal notes. They re-send old context. They re-explain decisions they’ve already made. That effort substitutes for a structural solution, and it has a cost. The people carrying the most institutional knowledge are spending their discretionary effort on maintenance instead of advancement. When that calculus tips far enough, they leave for an environment that feels tighter.

Adding more meetings, more check-ins, and tighter oversight doesn’t address what’s underneath. The work is resetting because nothing was designed to hold it.

Where to start.

The entry point is simpler than most people expect. Before anything else, name the outcome. (Not the activity, the outcome.) Then record what was decided, note what changed relative to that outcome, and refuse to restart conversations from scratch.

That discipline alone — giving your work a memory — reduces reopened decisions, produces clearer updates, and creates the conditions for work to reach completion consistently.

If you want to know where your team currently stands, the diagnostic at amykennedyleadership.com/diagnostic will show you which of these failure points is active in your work right now and where the most productive place to begin is.

If you’re a leader interested in piloting this discipline with your team, I’d welcome that conversation.

Work that builds is not an accident. It’s a design choice. It’s available to any team willing to make it.