Support/Goals/findability-and-browsability: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(16 intermediate revisions by 3 users not shown)
Line 5: Line 5:
===New Search implemenation===
===New Search implemenation===


===Taxonomy Research by Nielson Group===
=== Taxonomy Research by Nielson Group, due February 9===
Needed:
'''Resources:'''
* existing site plan: assigned to Bram, he should have by next week
* [https://docs.google.com/document/d/1twbZBmj0bfdcJuS6JTJp2YrkozxwtcC59oLTBZO6-tI/edit Statement of Work]
* [https://docs.google.com/spreadsheet/ccc?key=0AqTssbJSHVTndGU4cWx6VnBaSm04aEUtS1FNWlMwRFE Site map]
* [https://docs.google.com/document/d/1W8TAZtGH226QCZyGRVmQy6jxqVCOhUStG9tNQ-hX3bg/edit Top tasks based on search data]


Nice to have:
=== Final recommended IA structure and a brief write-up of any further recommendations etc. - due March 30 ===
* FAQs - Susan to carry out interview with Michael
* card sort of articles into susan's categories and analysis
* URLs/web addresses in the search logs - Bug to be filed.
* test new hierarchy in treejack
* web-search query statistics (terms driving people in from the web) - Crystal to check with Cheng.
* Deliverables: Final recommended IA structure (spreadsheets) and a brief write-up of any further rationale, recommendations, and findings.


===New Homepage and question workflow based on design by Barm===
=== Paper prototyping of new iA due May 29 ===
*Input from Michael, Kadir, Ricky, Crystal
* 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)
 
Goals: Discover what's confusing about terms that the previous testing could not resolve, check the performance of alternative terms and layouts against top user tasks, rapidly iterate the designs to improve their usability, and figure out what kind and how many screens, messages, and feedback mechanisms will be needed to accomplish interactive tasks efficiently.
 
Deliverables:
* Test plan (stands as an artifact for reuse in future PP tests)
* Changes to the IA structure and labels
* A brief writeup of any other interesting findings.
* validated prototype designs as a byproduct of this process
 
See here for further work: https://docs.google.com/document/d/1Gxnun6gRrySdptGuWVbUyR8W0XlcnsE1oaQlWU1RZH8/edit?hl=en_US&pli=1
 
=== New Homepage and question workflow based on design by Bram ===


===Implementation of new design by sumodev===
===Implementation of new design by sumodev===


==How do we know it's done?==
==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 26: Line 41:


==Schedule==
==Schedule==
Estimated time: 3 month


Taxonomy research phase 1: January 1st - January 31st<br>
*Taxonomy research phase 1: January 1 - February 10<br>
UX design phase: February 1st - February 28th<br>
*Taxonomy research phase 2: January 20 - March 5<br>
UX implementation: March 1st - March 31st
*Taxonomy/UX research phase 3: March 5 - April 15<br>


*UI design phase: mid to end May<br>
*UX implementation: June/July
Elastic Search integration:  
Elastic Search integration:  
Turning it on for a number of user: January 3 - 17
*Turned on for 50%: February 16
*Turned on for 100: March 6 (right after bug 729103 lands)




Line 41: Line 58:
==Notes==
==Notes==
Next step:
Next step:
*
* Paper prototyping

Latest revision as of 14:38, 10 May 2012

Purpose

Increasing the usability of SUMO as a whole. Specifically, we will have a mental map of users with the taxonomy research. We will redesign the site around that model, and implement the changes. In addition and in parallel to this we will introduce a new search engine with measurably improved performance with regards to click through rates.

Project plan

New Search implemenation

Taxonomy Research by Nielson Group, due February 9

Resources:

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
  • test new hierarchy in treejack
  • Deliverables: Final recommended IA structure (spreadsheets) and a brief write-up of any further rationale, recommendations, and findings.

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).
  • 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)

Goals: Discover what's confusing about terms that the previous testing could not resolve, check the performance of alternative terms and layouts against top user tasks, rapidly iterate the designs to improve their usability, and figure out what kind and how many screens, messages, and feedback mechanisms will be needed to accomplish interactive tasks efficiently.

Deliverables:

  • Test plan (stands as an artifact for reuse in future PP tests)
  • Changes to the IA structure and labels
  • A brief writeup of any other interesting findings.
  • validated prototype designs as a byproduct of this process

See here for further work: https://docs.google.com/document/d/1Gxnun6gRrySdptGuWVbUyR8W0XlcnsE1oaQlWU1RZH8/edit?hl=en_US&pli=1

New Homepage and question workflow based on design by Bram

Implementation of new design by sumodev

When are we done?

  • Elastic search is used 100%
  • Homepage redesign is in use
  • New workflow from homepage to articles is in use
  • New workflow to ask question is in use

Schedule

  • Taxonomy research phase 1: January 1 - February 10
  • Taxonomy research phase 2: January 20 - March 5
  • Taxonomy/UX research phase 3: March 5 - April 15
  • UI design phase: mid to end May
  • UX implementation: June/July

Elastic Search integration:

  • Turned on for 50%: February 16
  • Turned on for 100: March 6 (right after bug 729103 lands)


Blocked

NO

Notes

Next step:

  • Paper prototyping