The fastest way to find missing requirements: run the Q11 on a napkin
By Q11 AI
Have you ever shipped a feature that worked as exactly as designed… and practically every customer was certain it was a bug? That’s usually not a coding problem. It’s a requirements problem, which we can translate into a question problem. Here’s a handy low-tech trick: run Q11 on a napkin (or a sticky note).
Pick any feature of your product and run it through the 11 questions. Keep the answers light and simple – don’t write paragraphs, just write answers you can test directly.
A napkin-friendly Q11:
✅ How can I do this correctly?
❌ How can I do this incorrectly?
⏱️ When can I do this / not do this?
👤 Who can / cannot do this?
🔄 What happens after / if I don’t?
📏 How big/small/early/late can it be?
📈 How many times can I do this?
If there’s a question you are struggling to answer, congratulations! You have just found a missing requirement and saved yourself another defect triage meeting.
The Punchline
Yoda, “Do or do not. There is no try.”
There is no real middle-ground. Define your requirements or you are leaving your product up to chance.
