...
- Initial research
- User interviews
- What tasks do users perform most often? Do all users follow the same workflow to perform those tasks?
- What are the pain points in the existing interface? What are the most frustrating tasks?
- What do users wish they could do with the current interface but are unable to?
- Where/when/how do users interact with Grouper?
- How much functionality needs to be supported on small screens?
- What's the true breakdown of expert vs intermediate users?
- How much time, if any, should be spent testing the current interface against new users? existing users?
- User interviews
- Gather requirements (concurrent with Initial Research)
- Identify core functions
- Identify existing functionality to be preserved
- Identify new features requested by the community
- Vote on new features?
- Finalize list of new features and freeze requests
- Low-fidelity wireframes - desktop and mobile
- Initial sketching and low-fi electronic wireframe development
- Test common tasks against wireframes
- Rinse and repeat
- High fidelity wireframes - desktop and mobile
- Develop richer wireframes
- Test common tasks against wireframes
- Report results
- Proof of concept of accessible widgets and write framework code (custom tags, common javascript etc)
- Some of this could be done concurrently with steps outlined above
- autocomplete
- tree control
- popup window
- menu
- layout (frame-like)
- tooltips
- Graphic Design
- Development (iterative) (see the Developers Guide)
- Testing
Key Tasks for User Testing
...