When this matters
“Add an export” can hide choices about permissions, data, format and errors. A developer can propose defaults, but those proposals are not approved requirements. Starting the irreversible part of the work before the owner decides can create avoidable rework.
A practical approach
- List only unknowns that could change behaviour, scope, safety or the technical solution. Separate facts already confirmed from assumptions.
- Turn each unknown into a question with two or three concrete options where possible. Explain the consequence of each option.
- Assign a decision owner and the latest useful answer date. If one answer blocks another, show the dependency.
- Record the answer in the ticket. Then write acceptance criteria from confirmed decisions; leave unconfirmed proposals clearly labelled.
Example
For a customer export, ask: “Should it include all filtered records or only the visible page?” and “Which existing role may export personal data?” The product owner confirms all filtered records, while security approval for the role is still pending. The team can prepare a UI draft but should not expose the endpoint until the permission decision is made.
Make the next decision
A good question reduces a specific uncertainty. “Please clarify the task” does not. Keep the list short enough to answer in refinement. The readiness tool can surface gaps and draft questions; a person responsible for the product must still approve the decisions. Only then should a draft criterion become a commitment.