User Driven Development For Palinet

Slide 1: More Than Just P2E Why user-driven development is key to responding to the new user community Presented By: Jonathan Clark Date: April 10th 2007

Slide 2: Product Development should start and end with the user (UCD)  user understanding  user acceptance  avoid opinion wars  should deliver just what's needed (Agile)  understanding of user needs by all involved  prioritising to these needs  avoid requirements wars  2

Slide 3: User-Centred Design Process Understand the user, their tasks and their goals Design for the user, make sure they can efficiently and easily complete their tasks Evaluate the UI, not the user 3

Slide 4: Example: Electronic Information Retrieval Morning Lunch Afternoon After Hours Librarian Researcher Student Practitioner Significant generalizations; Use of Elsevier electronic products is much smaller 4

Slide 5: Example: Differences and Similarities rs Pr he • Clinical decision • Values completeness ac rc support and fact lookup and exhaustiveness tit ea io es • Collaborative • Need for a concise ne • Links to references R and easily rs and evidence • Likes to cast a broad scannable answer search first, then • Current awareness systematically refine • Need for concise results overviews • Quick and Advanced searching • Interested in seeing • Highly mobile what has NOT been • Help user understand done content • Time pressured • Needs to secure • Spellchecking grants/funding • Has little time to sift through large answer • Needs to publish sets original research 5

Slide 6: User-Centred Design Process Understand the user, their tasks and their goals Design for the user, make sure they can efficiently and easily complete their tasks Evaluate the UI, not the user 6

Slide 7: Evolution of the Refine Results box 7

Slide 11: How to display citation tools? ? 11

Slide 12: Summary – UCD Process Involves users throughout development process  Users are at the centre of the process  decisions based on user data  reduces design battles & opinion wars  Iterates through “understand, design, evaluate”  cycle until there is user acceptance 12

Slide 13: Product Development should start and end with the user (UCD)  user understanding  user acceptance  avoid opinion wars  should deliver just what's needed (Agile)  understanding of user needs by all involved  prioritising to these needs  avoid requirements wars  13

Slide 14: Elsevier Agile Development Process Key characteristics:  Iterative & time-boxed  Dedicated team & collaborative  Customer focused & testing intensive  We talk more, write less  Show software to users  Acknowledge that requirements emerge  Progressively refine our understanding of the  product 14

Slide 15: Elsevier Agile Development Process + Prototyping Architect/Developer (IT Lead) QA Specialist Initiate + Initial Story Writing Content Workflow Manager Project Manager Release Project Planning Initial Spikes + Iteration Manager Product Manager Content Planning + UCD Analyst Iterative Development Feedback / Usability Testing Preparation Spike Release! Iteration 1 Iteration 2 Iteration 3 Iteration 4 Iteration 5 Deployment Run Run Write Functionality Write Write Iteration Select Prioritize Functional Regression Stories Review Code Tests Showcase Story Stories Tests Tests & Tests Kick-Off Development Testing Update Usability Monitor Verify Ranking/ Design Fix/ Review Stories Testing Progress Story Estimating Session Correct Stories 15

Slide 16: Tell the story… Requirements are captured as “Stories” on index cards.  Stories are short descriptions (1-2 sentences) of something a  user wants to do or a capability the system must have. Typical form: “As a ___, I want to __, so that I can ___”.  Acceptance criteria go on the card (usually the back)  PathologyConsult Stickers show progress: 2.3 Inline Images • Red: Development has started As a pathologist, I want to be able to see images that relate to the text of a diagnosis appear in • Orange: Development the appropriate place. has completed The images of Rosai should appear in the text in the appropriate place and so must be linked to • Yellow: Testing by the data. Images should have the label and caption underneath as well as an ALT description . Developers & QA is complete Acceptance Criteria: · Hovering over or right-clicking the image should result in the label and caption being • Blue: The Product displayed. Manager has signed · References in the text to an image should be a link that jumps the user to the image where it is displayed on the page. off that card is complete Estimate: 2pts 16

Slide 17: User stories come from the user UCD is integral to our agile process  A UCD Specialist builds prototypes in collaboration with  the Product Manager and users Analysts draw the stories from the prototypes  UCD has a on-going role in the product development  process: Working one or more iterations ahead of development  Gathering feedback and usability results to update stories for  future iterations Provides input to the Product Manager on the prioritization of  the stories 17

Slide 18: PathConsult started with a book... 3000 pages  >8000 images  organized by organ  system 9th edition  includes diagnostic  pearls 18

Slide 19: What does a pathologist do? 90% of what a pathologist does is:  Look at microscope slides & make a diagnosis  If they cannot make a diagnosis, they:  Look up information or ask a colleague or order additional  stains or send out to an expert Why do they look up information?  They’re not sure what they’re looking at  They can’t decide between 2 or more possible diagnoses  They know what the diagnosis is but need additional  information They need help on what to do to determine a diagnosis  19

Slide 20: Pathologists at work 20

Slide 21: Primary Persona Perry, Private Practice, 42 • Has been in private practice for 8 years • Comfortable using computers, but currently doesn’t use them as much as his books for pathology-related questions • Often has very specific questions related to thresholds, margins, staging, grading; just wants the important bits, not all the background or foundation information • Driving need: Needs something that can help him work more quickly, more efficiently, and more effectively. Perry works in a private practice located in a medium-size hospital in the western suburbs of Chicago, Illinois. There are 6 pathologists in the office, plus a pathology assistant who handles gross. Perry is the “go to” person in the office for gastrointestinal cases, but everyone handles a bit of everything. His day is incredibly busy, with sometimes as many as 60 cases to review. The majority of the cases are fairly straightforward, though sometimes he will have a rare diagnosis. Perry usually eats lunch at his desk around noon, but often won’t it finish until a few hours later because of the number of cases he has to finish in a day. Life Goals  Perry has a large library of books and refers to them often. Usually he looks for a specific  Be good at my job picture to match a case, trying to pinpoint a diagnosis. He gets frustrated having to read Experience goals  through lots of text to just find the one piece of information he’s looking for, and wishes  Don’t waste my time he could just jump past all of the basic information right to the things he needs. Sometimes his work is interrupted, as colleagues ask for opinions on other cases. While  Don’t be condescending this can be frustrating, he doesn’t mind, as Perry often asks them for help with areas End goals  about which they are more knowledgeable.  Answer a specific question about a possible diagnosis He tries to keep up with new developments in the field, but it’s not as important as when  Find a picture he was an attending, since he mainly sees the same types of cases. Still, it’s good to  Find a specific piece of know about new immunostains and emerging areas like genetics, even if they’re not information for a case always useful in his day-to-day work. Perry works hard, and tries his best to leave on  Be more efficient time to get home and spend time with his wife Jeanne and his three kids. 21

Slide 22: consultant the boss pathologist pathologist product mgr developers developers pathologist UCD developer 22

Slide 23: High-level features & benefits list A website for pathologists should contain:  Lots of high-quality pictures, with descriptions  Clear, concise, and current diagnosis info  Ability to compare differential diagnoses  Immunohistochemical stain information  For each diagnosis, pathologists want  Clinical information  Gross and microscopic description  Prognosis  Pictures  Differential diagnoses, including pitfalls and tips on what to look for  Content has to be:  Concise, bulleted style  Differential diagnosis information  Diagnostic pearls  23

Slide 24: High-level features & benefits list A website for pathologists should contain:  Lots of high-quality pictures, with descriptions  Clear, concise, and current diagnosis info  Ability to compare differential diagnoses  Immunohistochemical stain information  For each diagnosis, pathologists want  Clinical information  Gross and microscopic description  Prognosis  Pictures  Differential diagnoses, including pitfalls and tips on what to look for  Content has to be:  Concise, bulleted style  Differential diagnosis information  Diagnostic pearls  24

Slide 25: Story 7 As a Persona C I want to be able to view diagnostic information on a group of conditions so that I can decide between possible diagnoses. 25

Slide 26: Differential Diagnosis: low-fi prototype Home > Differential Diagnoses First, select a body system Thyroid Select a different body system Then, select up to 5 diagnoses to compare View Amyloidosis Follicular carcinoma Differential Clear cell tumors Follicular adenoma Hürthle cell (oncocytic) tumors Papillary carcinoma Add  Hyalinizing trabecular adenoma and related lesions  Remove LYMPHOID TUMORS AND TUMORLIKE CONDITIONS Malakoplakia Medullary carcinoma MESENCHYMAL TUMORS METASTATIC TUMORS Other neuroendocrine tumors Parathyroid tumors Poorly differentiated carcinoma 26

Slide 27: Differential Diagnosis: low-fi prototype Home > Differential Diagnoses > Comparison Follicular carcinoma Follicular adenoma Papillary carcinoma Remove from comparison Remove from comparison Remove from comparison Image caption Image caption Image caption (stain, magnification) (stain, magnification) (stain, magnification) • Diagnostic Pearl • Diagnostic Pearl • Diagnostic Pearl • Diagnostic Pearl • Diagnostic Pearl • Diagnostic Pearl • Diagnostic Pearl • Diagnostic Pearl • Diagnostic Pearl 25 additional images available 15 additional images available 18 additional images available View complete diagnostic View complete diagnostic View complete diagnostic information for Follicular information for Follicular information for Follicular carcinoma adenoma carcinoma 27

Slide 28: Differential Diagnosis: as deployed 28

Slide 29: Differential Diagnosis: as deployed 29

Slide 30: From Pathology Book…. .....to Diagnostic Tool 3000 pages   >8000 images  organised by organ  Online diagnostic clinical decision support covering system general pathology. 9th edition  Designed to be used at the point of work. includes diagnostic  Image based. pearls  Core is differential diagnosis tool to compare conditions. At launch will includes 500 most useful conditions based  on feedback from Pathologists 30

Slide 31: Summary When the process revolves around the user  user understanding increased => better products  teams have a common focus => better collaboration  When traditional requirements are replaced by stories /  low-fi prototypes etc whole team better understands user needs => faster  When short iterations are used  better prioritisation => more focus on user value  The challenge is how to manage interface with less agile  parts of the organisation 31

Slide 32: Thank you j.clark@elsevier.com

Slideshare.net (beta)