Top 5 Tips to write like an Amazonian

 At Amazon, there are no slides or PowerPoint presentations, all documents are written in prose. Jeff Bezos believes this forces a clarity of thinking that can be masked if one uses bullet points in slides.

It’s not easy to follow these rules, but if you do, your communication in the workplace will be better understood and received.

Top 5 tips for ‘Writing like an Amazonian’:

Tip 1: Use less than 30 words per sentence: 
To achieve this eliminate clutter words.

Examples:
Due to the fact → Because
During the course of → During
Came in contact with → Met
During the time that → While
We’re in the process of learning → We’re learning

Tip 2: Replace adjectives with data: 
Examples:
We made the performance much faster → We reduced server-side tp90 latency from 10 ms to 1 ms
Nearly all customers → 90% of our customers

Tip 3: Does your writing pass the “so what” test?:
Has the reader learned anything to help them make a better decision at the end of your document?

Tip 4: Use subject-verb-object sentences with “doers” and “action”


Tip 5: Avoid jargon and acronyms as much as possible
as they exclude newcomers and non-experts. Always explain technical terms, acronyms, and abbreviations the first time they appear
Example: 
After we sign the Non-Disclosure Agreement (NDA) ...



Comments

Post a Comment

Popular posts from this blog

Software Architecture Techniques - Part 6

Question 1: What is the 20-minute rule, and when is it best to apply it? Answer: The "20-minute rule" for software architects is a time management technique that encourages dedicating short, focused bursts of time (around 20 minutes) regularly to learn new technologies, tools, or industry trends. The goal is to increase the architect's technology width, which refers to broadening their knowledge and understanding of different technologies and practices beyond their current expertise. Here's how the 20-minute rule can be applied: Consistent Learning : Set aside at least 20 minutes each day or several times a week to engage in learning activities. This could include reading articles, watching videos, attending webinars, or exploring documentation related to new technologies or architectural concepts. Focused Approach : Use the 20-minute sessions to maintain focus and avoid distractions. Eliminate interruptions during this time and fully immerse yourself in the learning ...
Read more

Software Architecture Techniques - Part 2

Question 1: What are the two dimensions of the risk assessment matrix? Answer: The risk assessment matrix typically consists of two dimensions: Likelihood : This dimension assesses the probability or likelihood that a risk event will occur. It is often represented on a scale from low to high or with numerical values (e.g., 1 to 5, where 1 is low likelihood and 5 is high likelihood). The likelihood helps in understanding the chances of the risk event happening. Impact : This dimension evaluates the potential consequences or impact of the risk event if it occurs. It is also represented on a scale from low to high or with numerical values (e.g., 1 to 5, where 1 is low impact and 5 is high impact). The impact helps in understanding the severity of the risk if it materializes. By combining the likelihood and impact assessments, organizations can categorize risks into different levels of criticality, such as low, medium, and high risk. This information is valuable in prioritizing risk respon...
Read more

Software Architecture Techniques - Part 3

Question 1: What is irrational artifact attachment, and why is it significant with respect to documenting and diagramming architecture? Answer:  Irrational artifact attachment is a cognitive bias that occurs when individuals become overly attached to certain artifacts, such as documentation and diagrams, without considering their actual usefulness or relevance to the architecture or project. It refers to the tendency to treat artifacts as inherently valuable or important, even when they may not provide substantial benefits or are outdated. This bias can be significant with respect to documenting and diagramming architecture for several reasons: Misleading Focus : When individuals are irrationally attached to specific artifacts, they may focus on maintaining and updating those artifacts rather than on the actual architectural decisions and their impact on the project. This can lead to a misallocation of time and effort. Loss of Agility : Outdated or unnecessary artifacts can impede ...
Read more