SUMMARY: A friction ledger records where members slow down, hesitate, or lose the route.
Friction is not always a bug. Sometimes it is a confusing label, a crowded room, a stale description, a page that loads correctly but fails to explain its purpose, or a discussion prompt that asks too much before giving enough context.
The operator should keep a lightweight ledger of repeated friction. The ledger does not need ceremony. It needs a date, a surface, the observed obstacle, the likely cause, and the next action.
Ledger Fields
Surface: page, post, topic, chat room, archive route, or account flow.
Signal: what the member was trying to understand or do.
Friction: the point where motion slowed or confidence dropped.
Adjustment: the smallest change that would restore flow.
When to Use It
Use the ledger with trust decay. Trust decay identifies the confidence leak. The friction ledger records the exact place where the leak becomes visible.
Operator rule: if the same hesitation appears twice, write it down before it becomes normal.