Amazon Writing Style Tip #1: Be Direct
• Use less than 30 words per sentence.
• Replace "due to the fact that" with "because".
• Replace "totally lack the ability to" with "could not".
• Replace adjectives with data. For example, instead of saying "we made the performance much faster", say "we reduced server-side TP90 latency from 10ms to 1ms".
• Eliminate weasel words. Replace "nearly all customers" with "87% of Prime members" and "significantly better" with "+25 basis points".
• Does your writing pass the "so what" test? If you get a question, reply with one of 4 Amazon answers: Yes, No, A number, or I don't know (and will follow up when I do).
Amazon Writing Style Tip #2: Be Objective
• Avoid adjectives and adverbs as they are imprecise and don't contribute to decision-making.
• Replace subjective statements with objective data. For example, instead of "Sales increased significantly in Q4", say "Unit sales increased by 40% in Q4 2011, compared to Q4 2010, because of holiday promotions".
Amazon Writing Style Tip #3: Avoid Jargon and Acronyms
• Always explain technical terms, acronyms, and abbreviations the first time they appear. Example: "After we sign the Non-Disclosure Agreement (NDA)..."
• Avoid vague weasel words. Do not use phrases like "would help the solution", "might bring clarity", "should result in benefits", "significantly better", "arguably the best".

Source: Write Like an Amazonian
Published: November 2018

Amazon Writing Guidelines in YAML for LLM legibility

writing_guidelines:
  version: "2024.1"
  source: "Write Like an Amazonian"
  last_updated: "2018-11"
  
  core_principles:
    - name: "Direct Communication"
      rules:
        sentence_structure:
          max_words: 30
          response_types: ["Yes", "No", "Number", "I don't know (with follow-up)"]
        word_replacements:
          - replace: "due to the fact that"
            with: "because"
          - replace: "totally lack the ability to"
            with: "could not"
        
    - name: "Data-Driven Writing"
      rules:
        metrics:
          - replace: "subjective statements"
            with: "quantifiable metrics"
          examples:
            - before: "performance is much faster"
              after: "reduced TP90 latency from 10ms to 1ms"
            - before: "nearly all customers"
              after: "87% of Prime members"
            
    - name: "Technical Clarity"
      rules:
        acronyms:
          format: "{full_term} ({acronym})"
          example: "Non-Disclosure Agreement (NDA)"
        prohibited_phrases:
          - "would help the solution"
          - "might bring clarity"
          - "should result in benefits"
          - "significantly better"
          - "arguably the best"

  validation:
    required_elements:
      - quantifiable_metrics
      - specific_data_points
      - defined_acronyms
    prohibited_elements:
      - weasel_words
      - subjective_adjectives
      - undefined_acronyms