andon/docs/adr/0001-defects-are-about-the-board-not-project-work.md

A Defect is about the Board artifact, not the reporter's project work

An Andon system normally signals a problem in the work being done; a reader could reasonably assume a click on a Section classifies a project problem under a Lean category (and aggregates to "which practices are weakest"). We decided the opposite: a Defect is feedback about the physical Board itself — a Section that is confusing, out of date, redundant, or missing — because the Board is the product we are rolling out company-wide and we want to find its weak points (Dantotsu) before/while scaling it.

Consequences

• A Section that accumulates Defects is a Weak Point of the Board, not of a delivery team.
• The dashboard's red-dot map ranks Board sections, not project practices.
• If we later want to capture project-level problems too, that is a different concept and should not be conflated with Defect.