1 / 24

MessageWiz Final Presentation

MessageWiz Final Presentation. IS 213 May 4, 2006. Introduction. Kenya has seen a 500% rise in TB infection rates in the last 10 years.

kirima
Download Presentation

MessageWiz Final Presentation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MessageWizFinal Presentation IS 213 May 4, 2006

  2. Introduction • Kenya has seen a 500% rise in TB infection rates in the last 10 years. • During a critical period of unsupervised treatment some patients default on treatment leading to continued sickness, a high risk of developing resistance to prescribed antibiotics, and the continued spread of TB through the Kenyan population. 

  3. Goals and Features • Goals • The interface is a patient reminder system designed to allow Kenyan health workers to create and schedule SMS and voice messages that will be used during the unsupervised treatment phase to remind patients to continue their medication regimen. • Features • SMS message creation (multiple languages) • Voice message creation (multiple languages) • Patient group creation • Scheduling

  4. HE Lessons • Use of text for clarification • Placement of actions • Consistency and simplicity

  5. HE Lessons: Use of text for clarification

  6. HE Lessons: Use of text for clarification

  7. HE Lessons: Placement of actions

  8. HE Lessons: Placement of actions

  9. HE Lessons: Consistency and Simplicity

  10. Major Changes to UI • Revised flow and architecture • Consolidated the message library and message send section into one main message group. • Consolidated the Message Categories • Created a more wizard like format. • Implemented simple explicit questions for users to step through • Improved language description

  11. New MessageWiz Architecture

  12. Revised Prototype • Live Prototype

  13. Pilot Usability Testing • Participants • U.S. (3) • Two health field professionals • One novice, non-English-speaking computer user • Kenyan (3+1) (basic computer skills) • One female nurse with familiarity with TB • Two male users with no domain knowledge • Facilitator also provided feedback • All had only basic computer skills

  14. Pilot Usability Testing • Apparatus • U.S. • Internet-connected desktop computer, written notes • Kenya • Viewer application connected through a VNC • VOIP using Skype PC-to-PC. • IM Chat • Video and Audio recording software • Facilitator on the ground

  15. Pilot Usability Testing

  16. Pilot Usability Testing • Results: Remote Testing Process • Facilitator key; training important • Bandwidth problems: no Skype • Chat’s one advantage • Pre-arranged dedicated usability testing setup • 2 observers • Extra computer • Time change (!)

  17. Pilot Usability Testing • Results: Content • New navigation flow much more intuitive and easier for participants • Increased use of wizard Q&A: success! • Stepped-through Patient section: ambiguous • Many problems of word choice & arrangement • Kenyans: Word choice, amount, & arrangement more problematic than navigation flow • Patient selection; Date clicking (8:20; 13:55)

  18. Lessons Learned: #1 Constrain User Actions • Users can get very lost, very fast, unless prevented from doing so • Wizard format • especially binary decisions • Steers user from irrelevant areas; • Makes options clear • Disable normal browser buttons

  19. Lessons Learned: #2 Low-literacy a persistent problem • Reduce text amount, complexity • Do not count on text to cue user action • Scrolling problematic, keep “above-the-fold” whenever possible • Still need textual confirmation

  20. Lessons Learned: #3 Consistency • Create user expectations and conform to them every time • Text / word choice • Navigation flow: • Users learn to expect Q & A for big decisions, action links for isolated choices • Limited ability to scan the page is helped when options are consistent • Ex: they learn that back/continue will always be at the bottom

  21. Upcoming Changes • Header: • confirmation message below main header • reduce header size; reduce amount of text • Consistency of Text: • same font size text for all user Q & A • Exits: more obvious back buttons • Calendar: expand “clickable” region. • Diction: final redo of all word choice

  22. Questions?

More Related