Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Additions based on 2 years of experience at USDS #189

Open
wants to merge 1 commit into
base: gh-pages
Choose a base branch
from
Open

Additions based on 2 years of experience at USDS #189

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 8 additions & 6 deletions _plays/01.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,12 +7,14 @@ We must begin digital projects by exploring and pinpointing the needs of the peo

### Checklist
1. Early in the project, spend time with current and prospective users of the service
2. Use a range of qualitative and quantitative research methods to determine people’s goals, needs, and behaviors; be thoughtful about the time spent
3. Test prototypes of solutions with real people, in the field if possible
4. Document the findings about user goals, needs, behaviors, and preferences
5. Share findings with the team and agency leadership
6. Create a prioritized list of tasks the user is trying to accomplish, also known as "user stories"
7. As the digital service is being built, regularly test it with potential users to ensure it meets people’s needs
2. Include the entire team: designers, developers, engineers, product, legal -- everyone who makes design decisions
3. Use a range of qualitative and quantitative research methods to determine people’s goals, needs, and behaviors; be thoughtful about the time spent
4. Test prototypes of solutions with real people, in the field if possible
5. Document the findings about user goals, needs, behaviors, and preferences
6. Share findings with the wider team and agency leadership
7. Create a prioritized list of tasks the user is trying to accomplish, also known as "user stories"
8. As the digital service is being built, regularly test it with potential users to ensure it meets people’s needs
9. Make sure that everyone on the team spends at least 2 hours every six weeks learning from users

### Key Questions
- Who are your primary users?
Expand Down