• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Designing better-ux-workshop-4
 

Designing better-ux-workshop-4

on

  • 257 views

 

Statistics

Views

Total Views
257
Views on SlideShare
242
Embed Views
15

Actions

Likes
0
Downloads
3
Comments
0

1 Embed 15

http://absguxd.tumblr.com 15

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Designing better-ux-workshop-4 Designing better-ux-workshop-4 Presentation Transcript

    • Designing better UXuxd@absg.com uxd.absg.comGirish GangadharanABSG Enterprise ArchitectureWorkshop - 4
    • Gathering RequirementsMore than just documentation
    • How we do it nowYou tell me.How do we gather requirements in any of our projects?
    • More features != Better product
    • Who are you talking to?
    • Why is User Research so important?Let’s talk numbers.Successful Projects: 29%Canceled projects cost $55 Billion AnnuallyChallenged Projects: 53%Failed Projects: 18%Stats: http://www.galorath.com/wp/software-project-failure-costs-billions-better-estimation-planning-can-help.php
    • Why is User Research so important?Some more numbers.IT projects that failed to meet their schedules: 62%Projects with budget overruns: 49%Higher-than-expected maintenance costs: 47%Failed to deliver expected business value & ROI: 18%Failed to perform against expectations: 33%Stats: http://www.galorath.com/wp/software-project-failure-costs-billions-better-estimation-planning-can-help.php
    • User-Centered DesignDesign for the targeted audienceDesign for yourselves or stakeholdersVs.
    • User-Centered Design
    • User Research StrategiesVs.Words NumbersVs.Subjective ObjectiveVs.Inductive DeductiveVs.Contextualization GeneralizationQualitative Vs. Quantitative
    • Common methodsQuestionnaires
    • Common tasksContextual Inquiry
    • Common tasksTask Analysis
    • Common tasksDiary Study
    • Common tasksFocus Groups
    • It all boils down to questions…Don’t lead the user (“is this a useful feature?”)Don’t judge (there is no right or wrong answer)Don’t assume (be specific)Avoid binary questions (let them speak their mind)OrDon’t ask any questions!Just observe what they do.
    • To ask or not to askGood questions Vs. Bad questionsWhat do you do after you complete this task?You think you should see more information here?Vs.Is this how you always come to this page?Why didn’t you click that button over there?Ask about the past.Don’t ask about the future.
    • Let’s do a quick exerciseIf you had to do the user research fora insurance claims management app,how would you do it?Hint: Tools, Surveys, Labs etc.
    • UXUX Design Cheat SheetUsefulnessSimplicityCommunicationIntuitiveness???Efficiency
    • Questions ?
    • Designing better UXuxd@absg.com uxd.absg.comGirish GangadharanABSG Enterprise ArchitectureWorkshop - 4