You get project updates without status meetings by switching to asynchronous status: each person updates their own work in a shared place before a fixed time, someone (or software) turns that into one short written summary, and the remaining meeting time is spent only on blockers and decisions. The meeting existed to move information. Once the information moves in writing, most of the meeting can go.
Why status meetings stop working
A status meeting looks cheap: 30 minutes, everyone hears everything. In practice it costs every attendee's time, interrupts focused work around it, and still leaves you without a written record.
The research points the same way:
- In Microsoft's 2023 survey, people ranked inefficient meetings as their number one productivity obstacle and too many meetings as number three (Microsoft Work Trend Index, 2023).
- Asana found that too many meetings was the most cited cause of missed deadlines, named by 24% of workers (Asana Anatomy of Work Index, 2022).
- Executives spend nearly 23 hours a week in meetings, up from less than 10 hours in the 1960s (Perlow, Hadley and Eun, Harvard Business Review, 2017).
- Meetings have also spread across the day. Microsoft's 2025 telemetry shows that 57% of meetings are ad hoc calls without a calendar invite (Microsoft Work Trend Index, 2025).
The useful part of a status meeting is short: hearing what is blocked and making the decisions that unblock it. The rest is people reading out information that could have been written once.
What happens when teams cut meetings
Researchers writing in MIT Sloan Management Review surveyed 76 companies with more than 1,000 employees that had introduced one to five meeting-free days per week. Employees reported less stress and micromanagement and more autonomy and cooperation, whatever the number of meeting-free days. The best results came at companies with three meeting-free days per week (Laker et al., MIT Sloan Management Review, 2022).
Notice that the best results did not come from eliminating meetings entirely. Meetings still matter for relationships and for decisions that need discussion. The goal is to remove the reporting, not the conversation.
The async status system in five steps
1. Agree on one place for status
All work lives in one shared list with an owner, a status and a due date for each item. Updates written anywhere else (chat threads, email, someone's notebook) do not count. Without this, written updates become another thing to chase. If you're starting from zero, How to Stop Chasing Status Updates From Your Team covers the basics.
2. Set a fixed update rhythm
Pick a time, for example "by 10:00 every Monday and Thursday", and keep it. Each person updates their own items. A good update answers three questions:
- What moved? Status changes, finished work.
- What is next? The next concrete step and its date.
- What is in the way? Blocked by what or whom, in one sentence.
Two or three lines per item is enough. Long paragraphs are a sign the update is doing a meeting's job.
3. Turn updates into one summary
Nobody should have to read twenty task comments. Someone writes, or software generates, one summary for the team lead and the team:
| Section | What goes in it |
|---|---|
| Moved | Work that changed status since the last summary |
| Late or at risk | Items past or close to their deadline |
| Blocked | What is stuck and who can unblock it |
| Needs a decision | Questions only the lead or a stakeholder can answer |
This is the part where AI is now genuinely useful. In Microsoft's 2023 survey, 80% of people said they wanted AI to summarize meetings and action items (Microsoft Work Trend Index, 2023). A summary of the task list itself is even more reliable, because it is built from the actual statuses rather than from what was said.
4. Keep a short meeting for blockers and decisions only
Replace the weekly status round with a 15-minute slot that has one agenda: the "Blocked" and "Needs a decision" sections of the summary. If both sections are empty, cancel the meeting. That cancellation is the best signal that the system works.
5. Close the loop in writing
After a decision, write it on the task or project: what was decided, by whom, and what changes. This stops the same question from coming back next week and gives new people a record. See How to Stop Answering the Same Questions Over and Over for building that record into a knowledge base.
Common mistakes
- Replacing a meeting with a long email. If the update takes longer to write than the meeting took, people will stop.
- No deadline for updates. "Update when you can" turns into "update when asked".
- The lead still asks in chat. If you ask for status privately, people learn the written update doesn't matter. Read the summary first.
- Hiding bad news. Make "blocked" and "at risk" normal statuses. A late item reported early is a good update.
A sample week
| Day | What happens | Time for the lead |
|---|---|---|
| Monday 10:00 | Everyone updates their items | 0 min |
| Monday 10:30 | Lead reads the summary, answers decisions in writing | 10 min |
| Wednesday | 15-minute blocker slot, only if needed | 0–15 min |
| Thursday 10:00 | Second update and summary | 10 min |
| Friday | Look at what slipped and why | 15 min |
How Orakis does it
Orakis keeps goals, tasks, owners, statuses and deadlines in one workspace, so status is already written down where the work is. Each morning the Home view shows a written briefing of what moved, who is waiting on you and what is already handled, next to what is late or due next. Updates, questions and decisions that need you land in one Inbox. The AI follows up on late or blocked work and brings only the decisions that need a person to that person. Orakis is a young product in closed beta and focuses on coordination, not on deep reporting.
FAQ
How often should a team post written updates? Two fixed times per week works for most teams. Fast-moving projects may need a short daily update; slow ones can do with one. The fixed time matters more than the frequency.
Won't we lose team connection without meetings? Keep meetings that are about people and decisions. In the research on meeting-free days, the best results came from companies that kept some meeting days, not from those that dropped meetings entirely.
Can AI write the status summary? Yes, if the work is in one system with owners, statuses and dates. An AI that reads the task list can summarize what moved, what is late and what is blocked. Have a person check decisions before they go out.
Sources
- Will AI Fix Work?, Microsoft Work Trend Index (2023)
- Breaking Down the Infinite Workday, Microsoft Work Trend Index (2025)
- Asana Anatomy of Work Index 2022: Work About Work Hampering Organizational Agility, Asana via MarTech Series (2022)
- The Surprising Impact of Meeting-Free Days, MIT Sloan Management Review (2022)
- Stop the Meeting Madness, Harvard Business Review (2017)