codefordenver / codefordenver/DataViz
Test with Users
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
### Testing with Users
Great! You've created something for your project!
Now we want to get user feedback to make sure our assumptions match customer expectations. Hopefully by now, you have a relationship with a partner or partners to which you can throw your newly-developed software.
Be sure to put the product in front of them to how they use it, and incorporate feedback into your next iteration. Validate that you're solving the right problem, and check to make sure you've reduced any friction involved in the user experience. Pivot as necessary.
This cycle of refining after demoing should go a long way towards injecting life into the project. That should translate into the customer getting a lot of value from our efforts!
For more information on UX research, see [this presentation](https://docs.google.com/presentation/d/1GKp98UVZXyxo2fjeOfV87TbJb8Z4zF7MozZ4ILtOO_k/edit) given at one of our Code for Denver Meetups.
Copyright 2016 CA, Inc.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the issue text and the linked UX research presentation to understand the intended user-testing approach. The issue does not name files or tests, so clarify the project users and expected deliverable first; done should include user feedback and a documented next iteration.
Written by the indexing model from the issue text.
Assessment
- Domain
- design
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100