[ativzzz]

> I’ve been on a few remote teams where I write a lot (in plain language too), and have found that if my audience is non-technical management that they simply don’t read it. Decisions continue to be made on their gut whims despite access to the critical information.

It feels like writing in a business context can easily enter TLDR territory.

I've often felt like I've had to write walls of text regarding various things, where it feels like there has to be a better more efficient way to transfer information between parties.

Walls of text work well for technical documentation, not so much with other things. You want to be concise, but often you literally cannot be.

Maybe a tool like Loom can be useful, but personally I hate watching a video when I can read instead. Maybe others disagree.

[clairity]

that's easily solved by a summary at the beginning of the document, laying out the premise, the conlusions, and a short thread connecting the two.

if you want to get fancy, you can work on organizing the document itself so that it's easily scanned for pertienent info (headings, charts, graphs, footnotes, etc.). but as the oft-quoted twain is said to have said: "I didn’t have time to write you a short letter, so I wrote you a long one."

[vorpalhex]

> It feels like writing in a business context can easily enter TLDR territory.

I frequently actually put "TLDR: Whatever-the-point-is" at the top of my presentations/write ups, and then use the paper to actually provide support and pro/cons.