Activity trap
The activity trap is mistaking motion for progress: a team busy shipping work, hitting dates and reporting green, while the outcome that was supposed to change does not move. It is the most common failure in goal setting because activity is easy to see and outcomes are not.
Why it is so hard to see
Everything about the activity trap looks like competence. Work ships, dates are met, the status report is honest. Nobody is slacking, and that is exactly what makes it survive.
It survives because the reporting line measures the thing the team controls. Delivery is controllable, outcomes are not, so a system optimising for comfortable reporting will drift towards activity every time without anyone deciding to.
The question that exposes it
If every item on this list were fully delivered, would anything about the business be different?
Ask it about last quarter, where you already know the answer. If the honest response is that the work happened and the number did not move, you have found it.
The way out
Write the outcome above the work rather than beside it. Every initiative hangs under a measurable result, phrased from X to Y, and the initiative is judged on whether that result moved.
Then keep both in the report. Delivery status tells you the team is functioning; outcome movement tells you the bet was right. Reporting only the first is what created the trap.
What is the activity trap? +
Mistaking motion for progress: a team shipping work and meeting dates while the outcome that was supposed to change stays flat. It looks like competence, which is why it survives.
How do you avoid the activity trap? +
Hang every piece of work under a measurable outcome written from X to Y, and judge the work on whether the outcome moved rather than whether the work shipped. Report both, so you can tell the difference.