User oriented design

USER ORIENTED DESIGN “If you don’t go, you don’t know” - Eric Rasmussen Nicolás di Tada Martín Verzilli Ary Borenszweig nditada@instedd.org martin@manas.com.ar ary@manas.com.ar twitter: nditada

THE PROBLEM • Design is a contextual activity • What works here doesn’t work there • You don’t know what your users know • What you think your users need is not what they need • What users think they need is not what what they need

TOMBODU (SIERRA LEONE) TRADITIONAL REGISTRATION

PLAY PUMP (WWW.WATERFORPEOPLE.ORG)

WILLIAM’S WINDMILL WILLIAMKAMKWAMBA. TYPEPAD.COM

HOW CAN WE DO IT? • Go • Listen • Watch • Play • Iterate

TAKE 1 Group SMS communications

• Most health workers don’t have Internet access at their workplaces... • ...neither they have computers • But most of them have cell phones

GROUP SMS

TAKE 2 Interacting with the system

EXPLORING SYMBOLS #?

Verbose syntax?

Abbreviated syntax?

Symbol syntax?

LET USERS FIND OUT

PLAYING WIZARD OF OZ • Test how users interact with your system before it actually exists • Make users believe that there’s a system already built and you want them to help you test it • Put someone behind the curtains to interact with them as if he/she was the system

TAKE 3 Reporting structured data

UNSTRUCTURED VS. SEMISTRUCTURED VS. STRUCTURED WAYS OF SHARING INFORMATION • Unstructured: “We are dealing with cholera Simple, easy, outbreak will call you later” ﬂexible Simple, • Semistructured: “at Rachaburi, we are requires FEATURE seeing Cholera URGENT” EXTRACTION, some training • Structured: “H5N1, Birds:200, Lab:No, Complex for human entry, FollowUp: no” hard to learn and to get right

SMS SYNTAX USABILITY

syntax seentags Simplify your users’ experience Machines adapt to the users

TAKE 4 Removing SMS !

How do I spell it? Diahrrea, diarhea, diharrea? disease:23 place:Thurdor cases:15 Received report of 15 diarrhea cases in Thurdor Ooops... I meant dengue

REPORTING WHEEL

WHEEL DESIGN GOALS • Instructions must be in users’ native language • The wheel has to explain itself, to minimize the need for training • Have you ever tried to write instructions and make them as short as possible? Quite a challenge!

USERS HAVE THE ANSWER • Findpotential users and conduct usability tests over the ﬁrst prototype with their help • Givethem a minimal explanation about what the wheel is trying to solve, not how it works

WIZARD OF OZ, THE SEQUEL

COLLECT FEEDBACK • Amazing feedback just from the initial reactions • “Why can’t I report what’s in the left?” • “What do I have to do with the report I built?” • “What will happen if I call that number?”

ITERATE!

SUMMARY • Don’ttry to guess: you won’t get it right • Leave your preconceived ideas of what works at home, at home! • Listen, watch, ask, be humble • People like to play • Iterate...forever

THANK YOU! QUESTIONS ? Nicolás di Tada Ary Borenszweig Martín Verzilli nditada@instedd.org ary@manas.com.ar martin@manas.com.ar twitter: nditada

http://mekongict.org	540
http://www.slideshare.net	22
http://translate.googleusercontent.com	2
http://webcache.googleusercontent.com	1

User oriented design

by nditada on Jun 13, 2010

Accessibility

Categories

Tags

Upload Details

Usage Rights

4 Embeds 565

Statistics

User oriented design — Presentation Transcript