Ambiguous Requirements Are Technical Debt in Advance.

Requirements do not need to be perfect before development starts. They do need to be explicit enough that the team can see what remains uncertain.

Unclear is still a decision

When a rule is left undefined, engineering will eventually choose an interpretation. If the interpretation is not shared, that choice becomes expensive to reverse after data, workflows, and user expectations have accumulated around it.

• Name the actor and the intended outcome.

• Separate confirmed rules from assumptions.

• Record the question that blocks a safe implementation.