feedback-triage

Capture each comment verbatim with its source and context, then classify it as ADOPT-NOW, ADOPT-IF-TIME, DEFEND, or DECLINE using explicit criteria. Log direction changes in a decisions file and create timeboxed cards for adopted items.

Run mentor suggestions through the same classification table as judge feedback. Before any adoption, state the cut-list math out loud: what existing work would this new item displace. Expensive but valid ideas go to ADOPT-IF-TIME with a ranked cut-list.

Use DEFEND when you disagree with the feedback and have evidence supporting your approach. Gather the evidence, then deliver it as a callback in the next round rather than arguing live during the session.

The ritual classifies and routes feedback but does not implement changes itself. It depends on disciplined verbatim capture and honest cut-list math; teams that skip logging or adopt everything will still face scope creep.

Prepare a callback script for the next round referencing each prior item and its status, such as what was built, what number resulted, or why an alternative was chosen. Visibly incorporated feedback scores well in multi-round judging.