Protocol
Turn a quality word into a testable condition
Replacing “fast” with “within the accepted threshold” still leaves the decisive question unanswered: what result would pass?
Before you use it
- Use when
- Acceptance depends on words such as fast, easy, robust, flexible, sufficient or user-friendly.
Keep this limit in mind
- Metrics can create false precision. Choose a threshold because it reflects a real need, not because a number looks rigorous.
Current editorial reading
Finish the condition
Name the situation, observable outcome, measurement method and agreed criterion. A hypothetical report requirement might read: with reference dataset R in environment E, at least 95% of measured requests reach an interactive report within two seconds of submission, using test T. Those numbers illustrate a completed condition; they are not a recommended performance target.
Keep unresolved choices visible
Choose the criterion because it addresses a real need. If the team has not agreed the dataset, measurement or threshold, mark that part unresolved and assign the next decision rather than presenting the sentence as ready for acceptance. Some qualities need inspection or a demonstrated user task instead of a single number. A precise measure can still measure the wrong thing.
Take it with you
Give two reviewers the same test result and the written condition. They should be able to decide pass or fail without inventing a threshold, while still questioning whether that threshold protects the intended need.
Sources and evidence (1)
What we checked
NASA recommends precise verification criteria, explicit unresolved values and requirements that can be assessed through test, demonstration, inspection or analysis.
Selected official passages inspected on 2026-10-04. The report example and its numbers are authored illustrations, not NASA thresholds or empirical usability evidence.
Appendix C: How to Write a Good Requirement · C.3 General Goodness; C.4 Completeness and Verifiability/Testability
NASA calls for unresolved values to retain a rationale, resolution action, responsible person and due date, and for assumptions to be confirmed before baselining.
Rechecked on 2026-10-04. This limits treating an apparently precise sentence with unresolved criteria as settled acceptance. The illustrated numeric target still needs project-specific agreement.
Appendix C: How to Write a Good Requirement · C.3 General Goodness Checklist, unresolved values and assumptions
Editorial sources (1)
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingTurn a quality word into a testable condition
Original edition evidence and sources
These records belong to the original released edition. The current editorial reading has its own evidence above; neither set silently replaces the other.
NASA guidance warns against unverifiable terms such as easy, fast, adequate or user-friendly unless they are translated into criteria that can be tested, demonstrated, inspected or analyzed.
Qualitative goals can still be useful during discovery when they are explicitly treated as goals rather than acceptance requirements.
Appendix C: How to Write a Good Requirement · Verifiability/Testability
All sources (1)
Original edition, downloads and provenance
The reading above is editorial version 1.0.0, bound to this exact source edition. The original data and saved downloads retain that edition and the separate editorial layer. They may contain earlier wording; use the current reading above when interpreting it.
Version 0.1.0
No review details are supplied for this edition.
Read the original edition and overlay as JSON · Release details