[tomekowal]

My two cents:

1. English is not my first language, and Grammarly helps a lot. Small things like correct punctuation and articles make the text much easier to read for native speakers.

2. I try to make communication "modular". There is tension between over-communicating (giving full context) and under-communicating (leaving out details). The first sentence of each paragraph summarizes the point. If you know that stuff already, you can skip. If you are re-reading, you can quickly get up to speed by skimming first sentences. If you are surprised by the first sentence, read the paragraph.

3. I often use numbers so that my recipient can answer or discuss just one point from my text. That usually starts with "Ad2". You can then "split" the discussion by numbering annotations "Ad2.1". If the conversation gets too long and convoluted, we need to add a summary of what we've written. Both Slack and email have flat conversation structure (Slack threads can go one level deep). That flat structure is usually a good thing for someone following the discussion.

It is very natural, and most people reply in the same way instinctively.

[el_don_almighty]

1. Writing is FOR THE READER and your effort reflects this point.

2. This style is very effective across non-native languages and helps facilitate future communications by organizing back-and-forth discussions with topic numbers

3. Focused topics provide transition space in the reader's mind for internal language translation and context framing for improved comprehension. Each topic sits in its own compartment of the Bento Box for consumption and consideration