What prevents projects from getting clear, testable requirements? Share fixes, templates and war stories

We keep seeing requirements arrive late, stay vague, conflict between stakeholders, or fail in real workflows. Help the community with short, practical contributions you’ve used in the field.

Please answer in this format (one specific problem → one reproducible fix):
1) Single obstacle that most often derails requirement clarity or validation (e.g., stakeholder politics, missing user context, requirements written as solutions). Keep it to one sentence.
2) Concrete practice, template, question or tool you used to fix it (exact wording, workshop step, checklist item, or tool + how you used it). One short actionable example.
3) Anonymized artifact or snippet you can share or describe (acceptance-criteria template, checklist, a 5-step workshop agenda, exact interview questions, or a traceability example). Paste the snippet or summarize in 2–6 lines.

Optional: say whether you’d join a live “requirements clinic” to walk through one real example, and tag your role and project scale (PO / BA / PM / QA / Arch; team <10, org 50–200, enterprise 1000+).

Prefer short, copy-pasteable templates and war stories that others can adapt. We’ll curate the best practices into a follow-up summary — please keep submissions practical and anonymized.