A founder once described his team to me as "the hardest working group I've ever managed." He said it with real pride. When I asked what they had actually accomplished against the year's top three priorities, he paused for an uncomfortably long time.
That pause is common. Effort and outcome are not the same thing, and most operating reviews measure the wrong one.
Motion Is Easy to Mistake for Momentum
Teams fill their calendars with meetings, their inboxes with updates, their task lists with completed items. All of that generates a feeling of forward motion. None of it guarantees the business is any closer to its actual goals. A sales team can hit call volume targets while missing revenue targets. An operations team can close hundreds of tickets while the core process problem generating those tickets goes untouched.
I look for this gap specifically in status reports. When an update says "completed 40 tasks this week" but can't connect those tasks to a specific outcome that moved, that's a signal the team is optimizing for visible activity rather than results.
Why This Happens Even With Good People
This is rarely about laziness. Good employees want to show they're contributing, and completed tasks are an easy, tangible way to demonstrate effort. Ambiguous, harder goals — the ones that actually matter, like reducing churn or improving gross margin on a specific product line — are slower to show progress and easier to avoid in favor of things that can be checked off today.
Founders reinforce this without meaning to when they praise busyness in meetings. "Great, you got a lot done this week" feels like good management. It is, unless "a lot" wasn't connected to what actually needed to move.
Rebuilding the Scorecard Around Outcomes
The fix starts with rewriting how progress gets reported. Instead of asking "what did you work on," ask "what moved, and by how much, against which goal." If a team can't answer that clearly, it's a sign the goal wasn't translated into something trackable, or the work wasn't actually connected to it.
I encourage leadership teams to pick three to five metrics per function that represent real progress — not activity counts, but outcome measures like margin, retention, cycle time, or conversion — and review those, and only those, at the top of every operating meeting. Everything else is detail that supports the conversation, not the headline.
The Discomfort Is the Point
This shift is uncomfortable at first, because it exposes gaps that busyness used to hide. Some weeks, the honest answer is "nothing moved." That's a hard thing to say out loud, and a far more useful one than another list of completed tasks. Progress reporting that tolerates that honesty is the only kind that actually helps a company get where it's going.