mediumConceptScenarioMidSeniorLead
The business insists on a requirement that nobody can test — "the system must be intuitive". What do you write instead?
4 min readUpdated 2026-08-15
Answer
Short answer
Convert the adjective into an observable: who is doing what task, under which conditions, and what result counts as a pass. Where no honest measure exists, record it as a design constraint with a named reviewer rather than leaving an unverifiable sentence in a document somebody signs.
Was this answer helpful?
Likely follow-ups
- How would you handle the same problem for "the system must be scalable"?
- Who signs off a requirement whose verification is a usability review rather than a test?
- The stakeholder rejects every number you propose as arbitrary. What do you do next?
- How would you write acceptance criteria for a requirement that the new process must not increase the error rate, when nobody measures the current error rate?
Related questions
- What goes in a BRD versus an FRD versus a user story, and how do you decide which to produce?mediumAlso on requirements and non-functional-requirements5 min
- Everybody signed off the requirement and two of them still mean different things by it. How do you catch that before the build?mediumAlso on acceptance-criteria6 min
- What does a business analyst do on an agile team, and how does requirements work survive without a signed-off specification?mediumAlso on acceptance-criteria6 min
- What is the Definition of Done, who owns it, and what do you do with an item that misses it at the end of a Sprint?mediumAlso on acceptance-criteria4 min