# What is async communication? A guide for project teams > Async communication lets a team make progress without everyone being live at once. Here is how to do it well on projects. By Austin DeBerry, Founder, Coastline CRM --- Async communication is communicating without requiring everyone to be present at the same time. Instead of pulling people into a meeting or expecting an instant reply, you write down the context and the decision you are proposing, and people respond on their own schedule. A well-written message, a thread, a document with comments: those are async. A meeting and a live chat where you sit there waiting for someone to type back are synchronous, because they only work if the other people are available right now. The distinction sounds small, but how a team handles it shapes how much real work it can actually get done. ## Why it matters more every year Teams are more spread out than they used to be. Different time zones, different working hours, people who do their best thinking at 6 a.m. and people who do it at midnight. If your team can only make progress when everyone is online together, you have created a bottleneck that gets worse with every person and every hour of time difference you add. Async breaks that dependency. It also protects focus. Every "quick sync" interrupts someone who was deep in hard work, and that context-switch costs far more than the fifteen minutes on the calendar. The hidden tax of a meeting-heavy culture is enormous, and constant interruption is quietly one of [the reasons good projects stall and fail](/blog/why-do-projects-fail). Async lets people do concentrated work in long blocks and handle communication in the gaps, which is the opposite of the all-day-meetings trap. ## What good async actually looks like Async is not just "send a message instead of meeting." Done badly it is worse than a meeting: a one-line "thoughts?" with no context, that kicks off six rounds of clarifying questions over two days. The skill is front-loading. A good async message carries everything the reader needs to respond without asking you anything: - The context: what this is, why it matters, what led here. - The specific decision or input you need, stated plainly. - Your recommendation, so people can react to a concrete proposal instead of starting from a blank page. - A deadline for response, so it does not drift forever. When you write like that, the reply you get back is a decision, not a request for more information. This is the same muscle behind [a good written status update](/blog/how-to-write-a-project-status-update): give people enough that they can act without scheduling a call to understand you. ## When to stay synchronous Async is the default, not the only mode. Some things genuinely need everyone in the room at once, and forcing them into a thread is its own mistake. Reach for synchronous when: - The topic is emotionally charged or sensitive (hard feedback, conflict, anything where tone matters and text gets misread). - You are brainstorming and need fast back-and-forth that builds on itself in real time. - The decision is urgent and a 12-hour reply cycle is too slow. - The group is genuinely stuck and needs to hash it out together. A useful rule: if it would take five rounds of async to resolve, just have the 20-minute call. The goal is not to ban meetings. It is to stop using them as the default for things a clear written message could handle. ## Making it a team habit Async only works if the team agrees on a few norms, otherwise people feel anxious that they are ignoring an "urgent" message that was never urgent. Set expectations explicitly: what a reasonable response window is (say, by end of next working day for normal items), what counts as truly urgent and how to flag it, and where decisions get written down so they are findable later. The last part matters most. The whole payoff of async is that the context lives in writing, so the record has to be somewhere durable, not buried in a chat that scrolls away. This fits naturally with [distributed and hybrid teams](/blog/what-is-a-hybrid-project-team), and it is a core part of [delegating work without hovering over people](/blog/how-to-delegate-without-micromanaging): you hand off with enough written context that someone can run with it on their own time. ## The takeaway Async communication means giving people what they need to respond without requiring them to be present in the moment. Write the context, propose the decision, set a response window, and let people answer when they are at their best. Keep the live conversations for the things that truly need them. Get this balance right and you will run more work with fewer meetings, which is most of what a calm, productive team feels like from the inside.