Here is an exercise worth doing for anyone who runs a team. Take the recurring meetings, multiply each one by the fully loaded hourly cost of everyone who attends, and total it for a quarter. The number is usually large enough to read twice. A standing weekly with nine people on it can cost more per year than a junior hire, and produce little more than a status update nobody reads and a vague sense of alignment that evaporates by Thursday. If you had to write a check for that meeting every week, you would cancel it on the spot. So treat the calendar as if you did.
That is the frame that changes a meeting culture. A meeting is not free because no money visibly leaves the building. It is one of the most expensive things a company does, and it should have to justify the cost like anything else. The bar is simple: a meeting has to do something that writing cannot do better. Hold a typical calendar to that single test and very little survives it.
The default should be writing, not a meeting
Most of what happens in meetings is information moving in one direction. Someone presents, others listen, a few ask questions they could have asked over text. That is not a meeting. That is a document being read aloud, slowly, to people who can read faster than you can talk. A status update is the clearest example. By the time nine people have each said what they are working on, an hour is gone, and the only person who needed all nine updates was the manager, who could have read them in five minutes.
So the first move in fixing meeting culture is to make writing the default and the meeting the exception. Anything that is one-directional, a status, an announcement, a decision already made and now being communicated, becomes a written artifact. People read it on their own time, at their own speed, and it stays searchable forever instead of dissolving into the air. This is the heart of async work. It is not about never talking. It is about refusing to spend synchronous time on things that do not require everyone in the same moment.
What writing cannot do
There are real exceptions, and naming them precisely is what keeps you from swinging to the other extreme of never meeting at all. A meeting earns its hour when the work is genuinely interactive. A few categories pass the test consistently:
- Decisions with live disagreement, where the back-and-forth is the point and a thread would take three days to do what twenty minutes can.
- Building something together in real time, a plan, a pitch, a tricky design, where the output is shaped by the conversation itself.
- Anything with real emotional weight, hard feedback, a sensitive personnel matter, repairing trust, where tone and presence carry information that text strips out.
What these share is that the value comes from the interaction, not the information. You cannot get there faster by writing, because the writing is not the work. The work is the human exchange. Everything else, and it is most things, is information transfer wearing a meeting's clothing.
The pre-read does most of the work
The single most effective change is the pre-read. Before any meeting that survives the test, someone writes a short document: the context, the options, the recommendation, the specific decision needed. People read it before they walk in. The meeting then starts not at zero but at the disagreement, which is the only part that needed a meeting in the first place.
This sounds like more work, and the first few times it is. But the document is the meeting, in a real sense. The act of writing it forces the owner to actually think the problem through, which often reveals that there is no real decision to make, at which point the meeting cancels itself. When the meeting does happen, it is half as long and twice as sharp, because nobody spends the first thirty minutes being brought up to speed.
Example: Picture a weekly cross-functional sync that runs sixty minutes with eleven people. Replace it with a shared written update that everyone posts to by Monday noon, plus a fifteen-minute optional call for whatever is genuinely contested that week. Most weeks the call has a few people on it and ends early. The team gets back close to ten person-hours a week and loses nothing, because the thing that meeting was supposedly protecting, alignment, lives in the writing all along.
Smaller rooms, fewer recurring slots
Two more disciplines matter for time management at the team level. First, attendance. The cost of a meeting scales linearly with the number of people in it, so every name on the invite should be there for a reason you can state. "Keeping them in the loop" is not a reason to put someone in a room for an hour. That is what the written summary is for. If a person's only role is to listen, they do not need to be live; they need the notes.
Second, recurring meetings. A standing meeting is a decision you made once and then stopped questioning, and standing meetings are where calendars go to rot. Put expiration dates on them. Every recurring slot should get reviewed each quarter and re-earn its place against the same test. Many will not survive the review, because they were created to solve a problem that has since been solved, and they have been coasting on inertia ever since. Killing them is the cheapest productivity win available to any team.
The point is attention, not just hours
It would be easy to read all of this as a war on time, but the real scarce resource is attention. A calendar broken into fragments by meetings leaves no block long enough to do the deep work that actually moves a business. Protecting maker time is the whole reason to be ruthless about the meetings, and good team collaboration depends on people having uninterrupted hours to think, not just on getting everyone in a room. We built a lot of Atlas around this conviction, that work should live in writing the team can search and act on, and that the calendar should hold only what genuinely needs to happen live.
The test stays the same once you have run that cost exercise. Could this be a document. Does it require these specific people, right now, in real time. If the honest answer is no, it is not a meeting that earns its hour, and it should come off the calendar. You will be surprised how much of your week comes back, and how little you miss what you cancelled.
Where this lives in wrxstack: Atlas Meetings and Atlas Tasks.