Document 360: #1 Knowledge Base Software
Home
  • Home
  • API documentation course
  • Podcasts
  • About
    • About me
    • Presentations
    • Contact
    • Site analytics
  • Archives
    • 2021
    • 2020
    • 2019
    • 2018
    • 2017
    • 2016
    • 2015
    • 2014
    • 2013
    • 2012
    • 2011
    • 2010
    • 2009
    • 2008
    • 2007
    • 2006
    • Posts by tag
  • Series
    • Reflecting seven years later about why we were laid off
    • Simplifying complexity
    • Value arguments for docs and tech comm
    • Visual communication
    • Biking
    • Testing documentation
    • Voiceover techniques
    • Seven deadly sins of blogging
    • API documentation survey
    • Author in DITA and Publish with WordPress
    • DITA journey
    • Dallas STC Summit videocasts
    • Get a Job in Technical Writing
    • Innovation in tech comm
    • Jekyll versus DITA
    • Quick reference guides
    • Search engine optimization
    • User-centered documentation
    • User-centered documentation principles
    • My journey to and from wikis
    • Findability / organizing content
    • From overlooked to center stage
    • Java notes
    • JavaScript notes
    • DITA notes
  • Misc.
    • Jekyll doc theme
    • Posts for beginners
    • Technical writing podcasts
    • Advertising info
    • Academic/Practitioner Conversations Project
    • Donations
  • Nav

    Simplifying Complexity

      • Introduction
      • Principle 1: Let users switch between macro and micro views
      • Principle 2: Make information discoverable as the user needs it
      • Principle 3: Ensure information harmony in the larger landscape
      • Principle 4: Reduce and distill vast information down to its essence
      • Principle 5: Conform to the patterns and expectations of the genre and schemas
      • Principle 6: Reconstruct the absent user
      • Principle 7: Reduce the complexity of technical language
      • Principle 8: Align the product story with the user story
      • Principle 9: Iterate and increment on content following an agile approach
      • Principle 10: Hide complexity with UX design (such as through JS or CSS)
      • Principle 11: Be both a generalist and specialist at the same time
      • How to evaluate documentation
Stay updated
Keep current with the latest trends in technical communication by subscribing to the I'd Rather Be Writing newsletter. 5,600+ subscribers. (See email archive here.)

Search results

Search powered by Algolia
Document 360: #1 Knowledge Base Software

Principles for simplifying complexity



©2020 I'd Rather Be Writing. All rights reserved. Privacy policy

      Simplifying Complexity

        • Introduction
        • Principle 1: Let users switch between macro and micro views
        • Principle 2: Make information discoverable as the user needs it
        • Principle 3: Ensure information harmony in the larger landscape
        • Principle 4: Reduce and distill vast information down to its essence
        • Principle 5: Conform to the patterns and expectations of the genre and schemas
        • Principle 6: Reconstruct the absent user
        • Principle 7: Reduce the complexity of technical language
        • Principle 8: Align the product story with the user story
        • Principle 9: Iterate and increment on content following an agile approach
        • Principle 10: Hide complexity with UX design (such as through JS or CSS)
        • Principle 11: Be both a generalist and specialist at the same time
        • How to evaluate documentation
      Stay updated
      Keep current with the latest trends in technical communication by subscribing to the I'd Rather Be Writing newsletter. 5,600+ subscribers. (See email archive here.)