Confirmed users
1,424
edits
Support/Goals/findability-and-browsability: Difference between revisions
Support/Goals/findability-and-browsability (view source)
Revision as of 14:38, 10 May 2012
, 10 May 2012→Final recommended IA structure and a brief write-up of any further recommendations etc. - due March 5
| (4 intermediate revisions by 2 users not shown) | |||
| Line 11: | Line 11: | ||
* [https://docs.google.com/document/d/1W8TAZtGH226QCZyGRVmQy6jxqVCOhUStG9tNQ-hX3bg/edit Top tasks based on search data] | * [https://docs.google.com/document/d/1W8TAZtGH226QCZyGRVmQy6jxqVCOhUStG9tNQ-hX3bg/edit Top tasks based on search data] | ||
=== Final recommended IA structure and a brief write-up of any further recommendations etc. - due March | === Final recommended IA structure and a brief write-up of any further recommendations etc. - due March 30 === | ||
* card sort of articles into susan's categories and analysis | * card sort of articles into susan's categories and analysis | ||
* test new hierarchy in treejack | * test new hierarchy in treejack | ||
* Deliverables: Final recommended IA structure (spreadsheets) and a brief write-up of any further rationale, recommendations, and findings. | * Deliverables: Final recommended IA structure (spreadsheets) and a brief write-up of any further rationale, recommendations, and findings. | ||
=== Paper prototyping of new iA due | === Paper prototyping of new iA due May 29 === | ||
* Create paper prototypes (represent key page alternatives and paths to the top task goals for 5-10 top tasks). | * Create paper prototypes (represent key page alternatives and paths to the top task goals for 5-10 top tasks). | ||
* Test paper prototypes and/or wireframes developed by Mozilla with a small number of users (6-8) in think-aloud qualitative usability sessions. Testing should be done at several stages of the design process (paper, clickable wireframes, visual design draft) | * Test paper prototypes and/or wireframes developed by Mozilla with a small number of users (6-8) in think-aloud qualitative usability sessions. Testing should be done at several stages of the design process (paper, clickable wireframes, visual design draft) | ||
| Line 34: | Line 34: | ||
===Implementation of new design by sumodev=== | ===Implementation of new design by sumodev=== | ||
== | ==When are we done?== | ||
* Elastic search is used 100% | * Elastic search is used 100% | ||
* Homepage redesign is in use | * Homepage redesign is in use | ||
| Line 46: | Line 46: | ||
*Taxonomy/UX research phase 3: March 5 - April 15<br> | *Taxonomy/UX research phase 3: March 5 - April 15<br> | ||
*UI design phase: mid to end | *UI design phase: mid to end May<br> | ||
*UX implementation: | *UX implementation: June/July | ||
Elastic Search integration: | Elastic Search integration: | ||
*Turned on for 50%: February 16 | *Turned on for 50%: February 16 | ||
| Line 59: | Line 58: | ||
==Notes== | ==Notes== | ||
Next step: | Next step: | ||
* | * Paper prototyping | ||