Skip to content

Process Documentation

Process documentation is about capturing the steps, activities, and raw data of your design and development process. It often includes sketches, brainstorm notes, test results, failures, and reflections. For example, when your team experiments with different sensor setups, process documentation could contain test logs, quick diagrams, and rough observations from user tests. This is not polished but provides an authentic record of how decisions were made.

Why is this relevant to you? Because process documentation makes teamwork transparent. It helps you and your teammates keep track of what has been tried, what worked, and what failed. It also supports reflection and continuous learning.

Starting Points

  • Keep a design log or project diary with short daily updates.
  • Store sketches, test results, and meeting notes in a shared space (e.g., Miro, Notion, or GitHub).
  • Use photos or quick videos to capture prototypes or test sessions.

Key Points

  • You make the process traceable: document iterations, not just results.
  • You capture failures and dead ends honestly, because they are valuable learning points.
  • You ensure that all team members can access and update the documentation.
  • You reflect briefly but consistently on why certain choices were made.