Skip to content
Ryan Wold edited this page Nov 1, 2019 · 11 revisions

Touchpoints Product Documentation

Touchpoints product documentation is loosely based on the The Product Cycle, which embraces living documentation, and the concept of blueprints as a shared abstraction to design and discuss product decisions.

In practice, to gauge whether these artifacts are valuable, ask:

  1. do they facilitate higher order conversations?
  2. do they allow for the capturing of product thought? (from broad-vision, to detailed product copy change)
  3. does it serve as a map? providing context AND driving action?
  4. are they easy to update?

Supporting Tools

  • Analytics
  • Backlog

Technical Reference

Clone this wiki locally