Async diagram reviews: get feedback without a meeting
Async diagram reviews work when you ask a specific question, on the right shape, by a date. How to run one, close the loop, and when to call a meeting anyway.
A typical diagram review meeting spends its first half walking people through boxes they could have read alone. An async diagram review replaces that half, but only if your request is better than “any thoughts?”
Quick AnswerAn async diagram review works when you ask named people a specific question, pinned to the shape it concerns, with a date attached. Close it by answering every thread and saying what changed. Keep a meeting for disagreements about direction, which comment threads rarely settle.
Why “any thoughts?” gets you the wrong feedback
An open request hands the reviewer the job of deciding what the review is for. Most people pick the easy job: a typo, a label, an arrow that could be straighter. What you needed to know, say whether IT can set up accounts before a contract is signed, gets no comment at all, because nobody knew it was in question.
Silence then reads as approval. More often it means the person opened the board, saw nothing aimed at them and closed it.
How to run an async diagram review
Decide what kind of feedback you need
There are three kinds, and they come from different people. Accuracy (is this what really happens?) comes from whoever does the work. Decisions (should it work this way?) come from whoever can say yes. Completeness (what did I miss?) comes from the team next door. Tell each person which one you want from them.
Say what is settled
Add a short note at the top of the board: what the diagram is for, which parts are agreed and which are open. Reviewers then spend their attention where you need it. This is far easier when the diagram answers one question in the first place.
Put each question on the shape it concerns
One question per thread, pinned to the exact box. In FlowDraw, press C or pick “Comment”, then click the board. A thread is anchored to a shape, so it stays with that shape when you rearrange things. If the question depends on a policy or a screenshot, attach it to the thread with “Attach files”.
Name the person and the date
A good request looks like this:
@Mark Evans Can IT set up a new hire’s accounts before the contract is signed, or does that wait? I drew it as waiting. Please answer by Thursday noon. After that I will publish the onboarding checklist as drawn.
The last sentence matters most. It tells Mark when his answer stops being useful and what happens if he says nothing. Comments in FlowDraw have no due date, so the date goes in the words.
Make sure people hear about it
Mentions count only for people who can open the board, so share it first: “Share”, then “Add people by email”. The role starts on “Can edit”, so switch it to “Can comment” if you want comments and no edits. People added to the board this way don’t take a paid seat, as long as they don’t also join the workspace.
For everyone but the board’s owner, the default level under “Comment notifications” is “Just mentions and replies”. A reviewer you don’t mention won’t hear about your new thread.
Close the loop
When the date arrives, reply in each thread with what you did, including “left as drawn, because…”, then “Resolve” it. We would have the person who drew the diagram do the resolving, so a resolved thread always means the answer was dealt with.
Resolved threads drop out of the “Comments” panel unless someone turns on “Show resolved comments”, so what remains there is your list of open questions. Finish with one summary comment at the top of the board: what changed, what didn’t, and why. People who can see their answer made a difference are quicker to answer next time.
When a meeting is still the right call
Async is the right default, and it fails in recognizable ways. We would still book a meeting in these cases, and keep it short.
- A thread has gone back and forth more than twice without moving. Stop typing, talk for 15 minutes and write the outcome back into the thread, so the record stays in one place.
- The question is about direction, not detail. Whether support should be able to refund without billing is a trade-off between two teams. Threads tend to harden positions on questions like that.
- Someone is about to lose something, such as scope, ownership or a step they care about. Tell them in person.
- The reviewers lack context. People seeing a new system for the first time need a walkthrough once. After that they can review alone.
- The clock is shorter than the reply time. During an incident, call people. Nobody should be waiting on a comment while checkout is down.
A meeting that follows an async round is better than one that replaces it. Everyone has read the board, so you can start at the open threads rather than the first box, and spend the time on the two questions that need a conversation. Remote teams get the same benefit from drawing before they meet.
Don’t review through an embed. It opens without an account, which makes it tempting for outside reviewers, but it is read-only and shows no comments. Anyone commenting has to be signed in with at least “Can comment”, so if a stakeholder won’t create an account, send them an export and copy their answer into a thread yourself.
FAQ
Long enough that each reviewer gets a normal working day with it, and short enough that they cannot put it off. We would start at two or three working days. Say so in the request, and say what happens when the time is up.


