Quick answers
- How do you clarify requirements?
- Confirm scope, edge cases, and priorities. Get it in writing.
Key takeaways
- Ask about scope, edge cases, and priorities.
- Get examples.
- Confirm in writing.
Instead of → Say
| Instead of | Say |
|---|---|
| What do you want? | To make sure I understand: we're building [X] for [user]. Out of scope: [Y]. Is that right? |
| What about errors? | What should happen when [error case]? Do we show a message, retry, or fail silently? |
| How important is this? | If we have to cut scope, what's the priority order? |
Example dialogue
You: Before I start, I want to confirm scope. We're building the checkout flow for logged-in users. Guest checkout is phase 2. Payment failures: we show an error and let them retry. Sound right?
PM: Yes. One thing: we need to support saved cards.
You: Got it. I'll add that. I'll send the spec for your sign-off before I build.
Common mistakes
- Assuming.
- Not documenting.
- Skipping edge cases.
Frequently asked questions
- How do I clarify requirements?
- Repeat your understanding, ask about edge cases, confirm priorities, and document.
- What questions should I ask?
- Scope, edge cases, priorities, and examples for anything vague.
Related
Ready to practice?
Try a scenario with AI and get feedback on your communication.
Start practicing