Service Design Tools
User Stories
User stories capture features from the user's perspective. They follow this format: "As a [type of user], I want [goal] so that [benefit]." This ensures we focus on user value.
Duration
45 mins
Group Size
3-6
Category
Service Design Tools
Difficulty
Easy
Participants will:
- Capture requirements from the user's perspective.
- Focus on user value, not technical specs.
- Enable iterative development and prioritization.
- Facilitate conversation between the team and stakeholders.
- Break down complex features.
- Maintain user-centered design.
- Create testable acceptance criteria.
Participants will leave with:
- User stories.
- Clear requirements.
- A foundation for development.
- Keep stories independent and negotiable. Sometimes teams struggle with 'negotiable'.
- Focus on the "why," not just the "what."
- Avoid technical details.
- Write from one user's perspective.
- Include acceptance criteria.
- Ensure stories fit into one sprint.
- Use INVEST (Independent, Negotiable, Valuable, Estimable, Small, Testable).
- Prioritize discussion over documentation.
Start the conversation
Be the first to share your thoughts, experiences, or questions!