Search results

New article in Simplifying Complexity series -- Iterate and increment on content following an agile approach

by Tom Johnson on Aug 31, 2018
categories: simplifying-complexity

I added a new article in my Simplifying Complexity series about iterative content development. The article is titled 'Iterate and increment on content following an agile approach'. This is a principle I feel strongly about as a central approach in all writing, but one with particular application to complex scenarios.

Here’s the principle:

Iterative development is a principle of design that applies as much to documentation as it does to software development and UX design. With iterative development, you continually improve the content by gathering feedback and then incorporate the feedback as appropriate into new iterations of the content. You write in a shorter cycles with increased feedback reviews, working on developing content over a longer period of time rather than a short burst of writing activity in a one-and-done type effort. This iterative approach better addresses scenarios involving complex documentation where the audience, needed information, steps, and other details are less certain and predictable.

Read more here: Iterate and increment on content following an agile approach

About Tom Johnson

Tom Johnson

I'm an API technical writer based in the Seattle area. On this blog, I write about topics related to technical writing and communication — such as software documentation, API documentation, AI, information architecture, content strategy, writing processes, plain language, tech comm careers, and more. Check out my API documentation course if you're looking for more info about documenting APIs. Or see my posts on AI and AI course section for more on the latest in AI and tech comm.

If you're a technical writer and want to keep on top of the latest trends in the tech comm, be sure to subscribe to email updates below. You can also learn more about me or contact me. Finally, note that the opinions I express on my blog are my own points of view, not that of my employer.