What async communication is
Asynchronous communication, often shortened to async communication, is when people exchange information without needing to respond at the same time. One person can leave a message, and the other can read and reply when they are available.
Common examples include:
- Project tickets: Written tasks, questions, updates, and feedback that team members can review later.
- Email : Messages that do not require an immediate reply.
- Recorded walkthroughs : Screen recordings that explain a task or demonstrate an issue.
- Shared documents: Briefs, specifications, and feedback that everyone can access.
When should you write and when should you have a meeting?
Not every discussion needs a meeting. Many routine tasks are easier to manage in writing.
| Write it | Discuss in a call or meeting | |
|---|---|---|
| Use for | Project briefs, questions, updates, reviews and progress reports | A new working relationship, a disagreement, a trade-off with no clear answer |
| Main benefit | Leaves a record everyone can refer to | Allows people to discuss an issue and reach an agreement quickly |
| Main cost | Takes time to write clear instructions | Requires everyone involved to be available at the same time |
Our usual approach was to handle routine work in writing. We use a call for what writing cannot settle. We log the outcome back in the relevant ticket so nobody has to rely on memory or search through meeting notes later.
Sixteen years, three formats
Anchor Wave is a web design and marketing agency in Tucson, Arizona, founded in 2003. From December 2009 to March 2026 we were its development team. Anchor Wave owned strategy, its client relationships and most of the design. We built and looked after the websites. The Anchor Wave story covers the work itself.
The tickets lived in a different place in each period, and each move kept what had worked.
- 2010 to 2015. Jobs came as tickets in Anchor Wave's own system, from page build-outs and design mockups to fixes and responsive conversions.
- 2015 to 2018. Each job had its own project with us.
- 2018 to 2025. One shared board for everything. Comments peaked in 2020, at more than 28,000 in the year.
What stayed the same was the unit: one job, one ticket, one place where everything said about it was written down.
How tickets replaced most status meetings
A meeting decides something, and then someone has to write it down. A ticket starts written down.
On the shared board, the brief, the questions, each draft and each revision sat in one thread. Page builds went through numbered drafts, some as far as an eighth. Anyone who picked up the task later could review the earlier discussion and understand why certain decisions had been made.
This made it easier for both teams to work independently. Developers did not need to wait for a meeting to ask routine questions, and the agency could review progress whenever it had time.
That is why the comment count matters more than the ticket count . More than 66,000 comments on 1,687 tickets show where the discussion happened: in the ticket, where both teams could see it.
How the shared board kept everyone updated
The board lists showed the current status of each job. It included lists for new tasks, development work, quality checks, and jobs waiting for a client response. Also, the status of every job was on the board , for both teams to read without asking.
One useful detail was the separate list for jobs waiting on a client's response. It distinguished work that was delayed because we needed feedback from the client from work that was waiting on our development team.
That distinction mattered. Without it, a delayed project could easily look like a development issue when the team was actually waiting for information or approval from the client.
Rules written down, once
During 2020 and 2021, the two teams documented their working rules so that everyone could refer to the same instructions.
These covered areas such as:
- How working hours and time entries were recorded
- How tasks were synchronized between the two teams' systems
- Who had access to different tools and information
- How work was reviewed before being handed back
Writing gave both teams a shared reference.
What we learned from 16 years of async communication
Working with Anchor Wave showed us that an outside development team does not need to be available for constant calls to keep projects moving.
The biggest benefit of async communication was not simply having fewer meetings. It was having a written record of the work that both teams could return to whenever they needed it.
Sometimes a call still made more sense. But most routine discussions did not need one.
