Build a useful investigation brief
Collect competing interpretations
Ask each collaborator to state expected result, actor, starting state, edge cases, and evidence without editing toward consensus first. Identify differences in outcome, scope, timing, permissions, and acceptable failure. Preserve dissenting examples until an owner resolves them.
Test with concrete scenarios
Run representative success, rejection, empty, retry, and boundary examples against each interpretation. Record where interpretations produce different decisions and which product or operational consequence follows. Compare one concrete success and failure example where interpretations diverge.
Write testable criteria
Convert resolved outcomes into concise pass and fail conditions, examples, exclusions, evidence owner, and remaining uncertainty. Recommend a decision or escalation when stakeholders still disagree. Record who resolves the remaining acceptance boundary and when.
What to carry forward
A useful brief makes competing interpretations and their consequences visible, then produces criteria a reviewer can execute. Stop when pass and fail conditions are testable; if values remain disputed, route that decision rather than disguising it as a technical gap.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow