# Effective Requirements Gathering
As a Business Analyst, your ability to gather and document requirements is crucial to project success.
## The Discovery Phase
### Stakeholder Interviews
Key questions to ask:
1. What problem are we solving?
2. Who are the end users?
3. What does success look like?
4. What are the constraints?
### Observation Techniques
Sometimes stakeholders don't know what they need. Observe their current workflow to identify:
- Pain points
- Workarounds
- Inefficiencies
## Documentation Best Practices
### User Stories
```
As a [type of user]
I want [some goal]
So that [some reason]
```
### Acceptance Criteria
Use the Given-When-Then format:
```
Given [some context]
When [some action]
Then [expected result]
```
## Common Challenges
### Scope Creep
- Document change requests formally
- Assess impact before agreeing
- Use a change control board
### Conflicting Requirements
- Facilitate workshops to align stakeholders
- Document trade-offs clearly
- Escalate when necessary
## Tools and Templates
- Confluence for documentation
- Jira for tracking
- Miro for visual collaboration
- Excel for requirements traceability matrix
## Conclusion
Great requirements are the foundation of successful projects. Invest time upfront to save time later.