u/Glad-Programmer-5505

spent three weeks documenting a noise violation. had a log with forty seven entries, dates, times, decibel readings, two written complaints i had submitted previously with confirmation emails.got my two minutes at the board meeting. started presenting. board chair interrupted halfway through and said the previous complaints had been reviewed and no violation was found.i knew this was wrong. i had confirmation emails showing the complaints were received but never formally reviewed. i had them printed out.but something about being in that room, outnumbered, everyone staring, the chair's confident dismissal just made me say 'okay, i just wanted to make sure it was on the record.'left having failed to present half my evidence and having implied i was satisfied with an answer i completely disagreed with.how do you hold your ground at an HOA meeting when the board is clearly just trying to end the conversation

remote PM at a company spread across US, UK, and India. we are fully async-first in principle. in practice we're async-first except for the 6 meetings a day that somehow still exist.

the real async work is everything between meetings. project updates, decision requests, context sharing, feedback loops. all written. all in slack or notion. and all taking way more time than anyone budgets for.

I counted last week: I sent 47 slack messages over 3 words long on monday. forty seven. some of those were quick answers but a lot of them were multi-paragraph updates with context because the person reading them is in a different timezone and can't ask me follow-up questions until tomorrow.

I've gotten faster at producing these by dictating the longer ones instead of typing. I use an AI voice dictation tool called Willow Voice and just talk through the update naturally. it adjusts the tone for slack vs email which is a small thing but it matters when you're switching between a casual team channel and a formal client thread. saves me maybe an hour a day compared to typing everything.

but I don't think speed is the real issue. the real issue is that async communication requires you to front-load context in a way that in-person communication doesn't. in person I can say "hey the timeline shifted" and answer questions in real time. async I have to anticipate every question, include all the context, and write it out clearly the first time because the feedback loop is 8-16 hours.

that context-loading work is mentally draining in a way that's different from meetings. meetings are draining because of interruption. async is draining because of cognitive load per message.

I love remote work and I'm not going back. but can we stop pretending async is "easier" than sync? it's a different kind of hard.

how are other remote teams actually handling async communication load? not the tools, the human energy side of it.