Last revised 15 September 2026
There is a difference between working hard and making progress, and sometimes it can be hard to see the difference.
It is easy to spend a great deal of time on work that feels productive without actually changing the outcome. You can write the plan, build the list, refine the deck, research the market, draft the email, leave comments in a document, and discuss the idea in a meeting. All of that may be necessary. But until the work reaches someone outside the team, very little has actually happened.
A sales plan does not create a booking. A list of journalists does not create an article. A draft campaign does not create engagement. A guest outreach strategy does not create an inquiry. Preparation matters because it supports the work that follows, but preparation is not the result.
The problem is that preparation can become a comfortable place to stay. There is always another pass to make, another detail to refine, another conversation to have. At some point, the question has to become simpler: what is different in the world because we did this work?
This strips away a lot of narrative. “I wrote the outreach script and identified 50 people to contact” may represent several days of effort, but it tells us nothing about progress toward the goal. “I contacted 50 people, 10 responded, and 3 want to continue the conversation” does.
That is the kind of progress we want teams to focus on and the kind of updates to share. Less explanation of the work. More evidence of what changed. The detail can come after.
One way to make this easier is to define the external part of a project at the beginning. What is the point where the work actually meets the world? It might be sending the pitch, publishing the article, calling the prospect, asking for the booking, launching the product, presenting the proposal, or putting the idea in front of a real user. That external action should be part of the project definition, and a major milestone.
The internal work should support that moment. The research matters because it helps you make a better decision. The list matters because it gives you people to contact. The draft matters because it helps you publish something useful. But if the project never crosses that line, the value remains theoretical.
There is also a reason people stay in the preparation phase for too long. The next step is often the uncomfortable one. Once you send something, someone can ignore you. Once you publish something, people can judge it. Once you ask for the sale, someone can say no. Once you put forward an idea, someone can reject it.
Preparation is safer because you are still in control.
That is why discomfort can be useful information. If a task has been circling for too long, it is worth asking what is keeping the team from putting it out in the world. Another revision may feel productive, but often the more valuable move is to send it and learn from what happens.
The same idea applies to how people contribute within teams. It is easy to offer a critique, leave a comment, point out an error, or suggest that something could be better. Those things can be helpful, but they are relatively low-effort contributions because they leave the next step to someone else.
A stronger contribution carries the idea forward. Instead of only pointing out what is wrong, suggest the alternative. If you see an error and can fix it, fix it. If a question keeps coming up, do not just answer it again. Turn the answer into something the team can reuse.
If someone sends a guest a thoughtful explanation that solves a recurring problem, that is useful. If they turn that explanation into a guest guide that can be used again and again, the value compounds. If a guest is confused by the arrival instructions, helping the guest is expected. Rewriting the instructions so the confusion disappears is more valuable.
Hospitality is full of similar examples. A team member gives one guest a great restaurant recommendation. Good. Turn it into a vetted guide and every future guest can benefit. A service issue is handled thoughtfully. Good. Add what was learned to the playbook and the organization gets better.
The point is not just to have good ideas. It is to convert good ideas into shared knowledge and better work.
Teams naturally talk about effort because effort is visible. Hours spent, meetings held, pages written, contacts researched, tasks completed. Those measures are not useless, but they are secondary. The more important questions are what happened after the work met reality. How many people did we contact? How many responded? How many booked? How many used it? What changed? What did we learn?
Those are the numbers that tell you whether the work is moving.
Good work still requires thought, care, preparation, and polish. The mistake is treating those things as indicators of progress. The finish line is usually somewhere outside the team, where another person responds and the work has the chance to change an outcome.
So when a project feels busy but is not moving forward, ask two questions: What will be different in the world because we did this work? And what is the next uncomfortable step that will measurably move us toward that outcome?