A project slows down, so you add a weekly catch-up. Then a mid-week check-in. A month later the calendar is full, the work is no faster and half of each meeting is spent reading out what everyone already did.
Meetings feel like progress because everyone is in the room. But stalled work is usually waiting on a decision, a file or an owner, and none of those needs an hour on a call.
Why does adding meetings not fix stalled work
A status meeting tells you where things are. It rarely changes where they are. If the problem is that nobody knows who is approving the design, another catch-up will raise that again without resolving it.
Meetings also take time from the people doing the work. An hour with five people is five hours of working time, and it breaks up the day around it.
What can replace a status meeting
Three written habits cover most of what a status meeting does.
| Instead of | Use | How it works |
|---|---|---|
| A weekly status meeting | A written update | Each person posts what moved, what’s next and what’s blocked, by the same time each week. |
| Asking who has what | A shared list of open work | Every task shows one owner, a date and a status, so the answer is there to read. |
| A call to get a decision | A written decision request | State the options, your recommendation and the date you need an answer by. |
How do you write an update people read
Keep it short and use the same headings every time, so readers know where to look.
- What moved. Finished work and decisions made since the last update.
- What’s next. The work planned before the next update.
- What’s blocked. Anything waiting, who it’s waiting on and what would unblock it.
Write it for someone who has two minutes. Put anything that needs a reply at the top, with the person’s name and the date you need it. A question buried in the fourth paragraph is easy to miss.
Clients can receive a version of the same update. A client who hears from you every Friday has less reason to ask for a call to find out where things are.
How do you get decisions without a meeting
Many meetings exist to get one decision. Ask for it in writing first.
Hi [name], we need to choose between [option A] and [option B] for [part of the work]. I recommend [option], because [reason]. The other option would mean [trade-off]. Could you confirm by [day]? If I don’t hear otherwise, I’ll go ahead with [option] on [date].
Naming a default keeps the work moving if the reply is slow. Use it only for decisions that are easy to reverse, and where you’ve agreed with the client that you can work this way. Anything affecting cost, scope or deadlines needs a clear yes.
When should you still meet
Some things are better handled in conversation. Keep meetings for:
- Kickoffs, where people are meeting for the first time and expectations are being set.
- Disagreements, or anything where tone matters.
- Complex decisions with several people and trade-offs to weigh.
- Sensitive news, such as a missed deadline or a change in price.
- A written thread that has gone back and forth three times without settling.
When you do meet, give the meeting a purpose and finish with decisions, owners and dates in writing. A weekly review is one meeting worth keeping. For a suggested agenda, read A weekly operations review for a small agency.
How do you make the change
Don’t cancel everything at once. Pick one recurring meeting that is mostly status updates and replace it with a written update for a month. Keep the calendar slot free for the first few weeks in case something needs discussion.
Tell clients what’s changing and why: they’ll get a regular written update, and you’re available for a call when something needs one. For the product overview, see Stack’s workspace.
After a month, ask the team and the client whether anything was missed. If nothing was, keep the change and look at the next meeting on the calendar.