Skip to content
Tyner Blain logo

Tyner Blain

Software product success.

  • Main
  • Profile
  • Tyner Blain
  • Subscribe
Communication / Design / Interaction design / Requirements Models / Use Cases / UX / Writing

Use Case Driven Documentation

Posted on: October 10, 2006February 19, 2007

Yesterday we wrote about focusing our documentation on what our users are trying to accomplish. With a structured requirements approach, or with an interaction-design driven approach, we’ve already solved half the problem – determining what to document.

Product Management / Software development / Writing

Goal-Driven Documentation

Posted on: October 9, 2006February 11, 2007

Why do we write documentation? Because someone told us to write it? Because our competitors have it? Or because we want our software to be easier to use? It should be the third one, but often, writing documentation is an afterthought, and it is deprioritized, and we just get it done, instead of thinking about the goals for doing it in the first place and doing it right.

Categories

Archives

Who Should Read Tyner Blain?

These articles are written primarily for product managers. Everyone trying to create great products can find something of use here. Hopefully these articles help you with thinking, doing, and learning.

Welcome aboard!

Recent Posts

  • The Secret of Diminishing Returns
  • When Clocks Aren’t Reliable
  • Coherence, Outcomes, and Dictation
  • Problems in the Solution
  • Being Wrong vs. Being Late
Niche Blog WordPress Theme by Fahim Murshed