
Your purpose in writing at work is to communicate to other people […] it's not about you; it's about them

Even if your audience does have substantial background knowledge, it can still be useful to provide some brief context before you plunge into your core content. While you have been thinking about this topic, your readers have likely been focusing on other matters and could use help getting their heads into the issue . That said, your purpose should not be to convey everything you know, but rather to identify and share the information your audience needs. (note: my emphasis)
learn about:
Hemingway App
bottom line up front, inverted pyramid
how to order phrases correctly (especially in user guides) so that people know what's coming, vs academic or storytelling writing where you build the argument and then give the solution or meaning
memos - use cases, formatting

If your audience is seeking information to solve a problem or answer a question, make sure to address their needs directly. Good writing anticipates and answers the reader's questions.

[Use appropriate headings so] a reader could scan through your document, looking only at the headings, and still grasp your main points. Most readers do, in fact, skim through materials in this manner, particularly when they are reading online. Numerous eye-tracking studies have found an F-shaped pattern, where readers start by looking briefly across the top line of the page and then drop down, scanning for another place to stop and read again, which a heading can provide.

Always construct your headings in a parallel manor. You can use full sentences, fragments that start with a verb, or fragments that start with a noun. Just don't mix and match.

Keep in mind that while typing out a quick message can feel like speaking, a digital record is created every time you communicate—one that can be preserved indefinitely and shared with others, including a much broader audience than you intended, due to the ease of forwarding and screenshotting messages. Pay attention to the words you use, and pay extra attention when writing about a sensitive topic.

Much of what we call grammar is a matter of stylistic preference, often influenced by what we were taught in school or by our first boss. If your organization follows a style manual, or if your manager has particular preferences, let those be your guide—even if they seem outdated (or newfangled) to you.

[When writing instructions] don't make assumptions . It's far better to explain too much than too little. Your readers can skip over parts they already know, but can't fill in gaps.

My review
Things I learned
From my notes while reading (above) or after some reflection.
Hemingway App
The Hemingway Editor assists with improving writing clarity and readability. It highlights complex statements, passive voice, and adverbs. Choose Hemingway for style and simplicity, when clarity is your main goal.
Grammarly offers comprehensive style, tone, grammar, spelling, and plagiarism checks. Choose Grammarly for overall correctness and to catch errors beyond Hemingway's scope.
Putting the important stuff up front
Leading with the most important info improves comprehension, helps the reader decide if they should keep reading, gives them what they're looking for immediately
BLUF (Bottom line up front) - military writing
Place the key information at the beginning of each section
Inverted Pyramid - journalism
Most important points are delivered at the top of the story, followed by additional details
Include the 5 Ws immediately - who, what, when, where why
The how provides supporting details
Wrap up with background info
Links/references
Ordering concepts appropriately in instructions so the reader can follow
This is called "Action Before Result" or "Context Before Action" and prevents "instructional blindness" (when a reader starts an action before they realize they are in the wrong place or don't have the right tools). In UX writing this is called "front-loading."
Details should be mapped based on how the user will perform them. Include prereqs first, and make no assumptions.
Enter the platform, then do the action.
Don't assume they're already in the platform or know to go there first, even if the guide is about that platform (especially if the guidance includes other platform work)
If there are many prereqs, include them as a section before the instructions - ensure the reader has the right platform, permissions, and tools before they even begin
Place the goal/context first, then the details after that.
(bad) Do this to do that.
(good) To do that, do this.
You should tell the reader where an action should take place (or the conditions, objectives) before describing the action to take - where before what, who before what, etc.
"Click submit if you are an admin" vs "if you are an admin, click submit" - in the first scenario, the non-admin user may have already clicked submit before realizing it doesn't apply to them.
Links/references
Memos - When to send them
Use memos to communicate official messages to a large group
Policy, process, or org changes - documentation of decisions or agreements
Update on projects/goals
Staffing updates
Issuing a 'call to action' or other directive