Async work has a reputation for being slow. Done badly, it is. Done well, it gives people long stretches of focus, fewer meetings, and a written record of everything the team decides. Here is the routine we use at Vyse to stay fast without living in meetings.

1. Write it down once

The foundation of async work is a good written update. Ours has three parts: what changed since the last update, what is blocked, and what you need from someone else. If an update cannot be read in under a minute, it is too long.

We keep updates in the same place the work lives, so nobody has to hunt for them. A teammate returning from a day off should be able to catch up in ten minutes, not an hour.

2. Name an owner for everything

Async breaks down the moment two people assume the other is handling something. Every task, decision, and follow-up gets exactly one owner. Not a team, not a pair, one person whose name is on it.

Owners do not have to do all the work. They are responsible for making sure it moves, asking for help early, and closing the loop when it is done.

“A short written update beats a long meeting every time, and it is still there next week when someone asks.”

Maya Chen, Co-founder and Head of Design

3. Set response expectations

People worry that async means waiting forever. The fix is to agree on how fast replies are expected. For us, normal requests get an answer within one working day, and anything urgent gets a direct message with the word urgent in it, used sparingly.

Once everyone knows the rules, the anxiety disappears. You can close the chat app for two hours and know nothing is on fire.

4. Meetings still have a place

We did not ban meetings. We moved them to where they are strongest: debating a hard decision, working through a disagreement, or celebrating a launch. Every meeting has a written agenda beforehand and a written summary afterward.

The summary is the part most teams skip, and it is the part that makes meetings pay off. If a decision was made, it goes in the log.

5. Review the routine every quarter

Any process drifts over time. Each quarter we ask the team what is working, what feels slow, and what we should stop doing. Small tweaks beat big overhauls, and the team stays in charge of how it works.