Turn “search must be fast and relevant” into testable acceptance criteria.

Instruction: Propose measurable criteria and tests, distinguish assumptions from agreed requirements, and explain how you would obtain a relevance oracle.

Context:

A fictional product owner writes only: “Search must be fast and relevant.” The feature searches a 10,000-document internal catalog. A staging corpus of synthetic documents and a list of 20 representative user tasks are available. No latency budget, concurrency target, relevance labels, supported devices, or stale-index policy has been agreed. You may propose values for discussion, but they are not existing product commitments.

Updated

Official answer available

Read the opening below, then unlock the full answer and practical guidance.

I would first turn the vague words into a reviewable proposal, then have product and engineering agree the workload and tradeoffs. I would not convert an invented threshold into a reported defect...

Upgrade to view official answer

Related Questions