Difference between revisions of "Crowdresearch:WinterMilestone 3 Alipta - Usability Longterm"

From crowdresearch
Jump to: navigation, search
 
(2 intermediate revisions by the same user not shown)
Line 7: Line 7:
  
 
'''Surface Layer'''
 
'''Surface Layer'''
*Already covered in Usability_Actionable Section
+
 
 +
*Overall there are a lot of labeling & Taxonomy issue noticed and a steep learning curve for first time users, some issues notice relating to Visual affordance & Design
 +
*Since we do not know the user profile of the end users we assume the system is little complicated for semi-literate
 +
users
 +
 
 +
*Steep learning curve for requester while creating a task
 +
*Information grouping is required to reduce cognitive load, for e.g. My Tasks can have sub groups like submitted task, open task, closed task similarly My Projects can have sub groups like submitted task, open task, closed task
 +
*As the site becomes more complex with additional features 7 functionalities a visual language has to be created in terms of color definition , font style, layout & design.
 +
 
 
[http://crowdresearch.stanford.edu/w/index.php?title=Crowdresearch:WinterMilestone_3_Alipta_-_Usability_Actionable]
 
[http://crowdresearch.stanford.edu/w/index.php?title=Crowdresearch:WinterMilestone_3_Alipta_-_Usability_Actionable]
 +
 +
 +
----
  
  
 
'''Skeleton Layer'''
 
'''Skeleton Layer'''
 
*Saving/reusing a template If the requester is posting a similar type of task the system should allow the user to save the template & reuse it later for future use & publish task
 
*Saving/reusing a template If the requester is posting a similar type of task the system should allow the user to save the template & reuse it later for future use & publish task
 +
 +
 +
----
  
  
Line 20: Line 34:
 
*Identify UI Design patterns & analyse them based on the user persona
 
*Identify UI Design patterns & analyse them based on the user persona
 
* Group task based on different geography & categories
 
* Group task based on different geography & categories
 +
 +
 +
----
  
 
'''Scope Layer'''
 
'''Scope Layer'''
 
*Customize the portal for potential markets  
 
*Customize the portal for potential markets  
 
*Define labeling & taxonomy for specific demography
 
*Define labeling & taxonomy for specific demography
 +
 +
 +
----
  
  
Line 31: Line 51:
 
*Provide seamless experience across channels
 
*Provide seamless experience across channels
 
*Grouping task under categories like region, type will induce user from other languages/culture to use the platform and user from different culture & demography can have direct access to Task posted by US requester, tasks posted by Indian requester..task posted by UK requester...
 
*Grouping task under categories like region, type will induce user from other languages/culture to use the platform and user from different culture & demography can have direct access to Task posted by US requester, tasks posted by Indian requester..task posted by UK requester...
 +
 +
 +
== Milestone Contributor ==
 +
@alipta

Latest revision as of 01:10, 1 February 2016

Garret breaks down the elements of UX as follows

Layers.pngTest


The usability findings at different levels are not the same

Surface Layer

  • Overall there are a lot of labeling & Taxonomy issue noticed and a steep learning curve for first time users, some issues notice relating to Visual affordance & Design
  • Since we do not know the user profile of the end users we assume the system is little complicated for semi-literate

users

  • Steep learning curve for requester while creating a task
  • Information grouping is required to reduce cognitive load, for e.g. My Tasks can have sub groups like submitted task, open task, closed task similarly My Projects can have sub groups like submitted task, open task, closed task
  • As the site becomes more complex with additional features 7 functionalities a visual language has to be created in terms of color definition , font style, layout & design.

[1]




Skeleton Layer

  • Saving/reusing a template If the requester is posting a similar type of task the system should allow the user to save the template & reuse it later for future use & publish task




Structure Layer

  • Detail IA activities has to be carried out, which will help grouping & labeling information.
  • Define navigation pattern for multiple form factors
  • Identify UI Design patterns & analyse them based on the user persona
  • Group task based on different geography & categories



Scope Layer

  • Customize the portal for potential markets
  • Define labeling & taxonomy for specific demography




Strategy Layer

  • Cater to global users Internationalization & Localization for different geographies
  • Make the platform available to multiple form factors, Mobile Tablet
  • Provide seamless experience across channels
  • Grouping task under categories like region, type will induce user from other languages/culture to use the platform and user from different culture & demography can have direct access to Task posted by US requester, tasks posted by Indian requester..task posted by UK requester...


Milestone Contributor

@alipta