User Driven Development For Palinet

More Than Just P2E

Presented By: Jonathan ClarkDate: April 10th 2007

Why user-driven development is key to responding to the new user community

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

3

Understand the user, their tasks and their goals

Evaluate the UI,not the user

Design for the user, make sure

they can efficiently and

easily complete their tasks

User-Centred Design Process

4

Librarian

Morning Lunch Afternoon After Hours

Researcher

Student

Practitioner

Significant generalizations; Use of Elsevier electronic products is much smaller

Example: Electronic Information Retrieval

5

Example: Differences and Similarities

• Values completeness and exhaustiveness

• Clinical decision support and fact lookup

• Interested in seeing what has NOT been done

• Need for a concise and easily scannable answer

• Links to references and evidence

• Current awareness

• Quick and Advanced searching

• Help user understand content

• Spellchecking

• Needs to publish original research

• Has little time to sift through large answer sets

Resea

rcher

s Practitioners

• Need for concise overviews

• Time pressured

• Highly mobile

• Collaborative

• Needs to secure grants/funding

• Likes to cast a broad search first, then systematically refine results

6

Understand the user, their tasks and their goals

Evaluate the UI,not the user

Design for the user, make sure

they can efficiently and

easily complete their tasks

User-Centred Design Process

7

Evolution of the Refine Results box

8


9


10


11

How to display citation tools?

?

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

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

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

15

Elsevier Agile Development Process

Iterative Development

Iteration 1 Iteration 2 Iteration 3 Iteration 4 Iteration 5 Deployment

Preparation Feedback / Usability Testing

Release!

Initiate Project

Architect/Developer (IT Lead)

Analyst

QA Specialist

Iteration Manager

Project Manager

Product Manager

Content Workflow Manager

UCD

Prototyping

Initial Story Writing

Initial Spikes

Content Planning

+

+

+

+

Release Planning

Write Stories & Tests

Review Stories

Kick-Off

Prioritize Stories

Functionality Review

Ranking/ Estimating

Design Session

Development

Select Story

Write Tests

Verify Story

Write Code

Monitor Progress

Testing

Run Functional

Tests

Run Regression

Tests

Fix/Correct

IterationShowcase

Update Stories

UsabilityTesting

Spike

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)

PathologyConsult2.3 Inline Images

As a pathologist, I want to be able to see images that relate to the text of a diagnosis appear in the appropriate place.

The images of Rosai should appear in the text in the appropriate place and so must be linked to the data. Images should have the label and caption underneath as well as an ALT description.

Acceptance Criteria:

· Hovering over or right-clicking the image should result in the label and caption being displayed.

· 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.

Estimate:2pts

Stickers show progress:

• Red: Development has started

• Orange: Development has completed

• Yellow: Testing by Developers & QA is complete

• Blue: The Product Manager has signed off that card is complete

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

18

PathConsult started with a book...

3000 pages >8000 images organized by organ

system 9th edition includes diagnostic

pearls

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

20

Pathologists at work

21

Life Goals Be good at my job

Experience goals Don’t waste my time Don’t be condescending

End goals Answer a specific question

about a possible diagnosis Find a picture Find a specific piece of

information for a case Be more efficient

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.

Perry has a large library of books and refers to them often. Usually he looks for a specific picture to match a case, trying to pinpoint a diagnosis. He gets frustrated having to read through lots of text to just find the one piece of information he’s looking for, and wishes 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 this can be frustrating, he doesn’t mind, as Perry often asks them for help with areas about which they are more knowledgeable.

He tries to keep up with new developments in the field, but it’s not as important as when he was an attending, since he mainly sees the same types of cases. Still, it’s good to know about new immunostains and emerging areas like genetics, even if they’re not always useful in his day-to-day work. Perry works hard, and tries his best to leave on time to get home and spend time with his wife Jeanne and his three kids.

Primary Persona

22

pathologist

pathologist

pathologistconsultant

developers

product mgrthe boss

UCD developer

developers

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

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

25

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.

Story 7

26

Amyloidosis

Clear cell tumors

Hürthle cell (oncocytic) tumors

Hyalinizing trabecular adenoma and related lesions

LYMPHOID TUMORS AND TUMORLIKE CONDITIONS

Malakoplakia

Medullary carcinoma

MESENCHYMAL TUMORS

METASTATIC TUMORS

Other neuroendocrine tumors

Parathyroid tumors

Poorly differentiated carcinoma

Home >

Differential Diagnoses

Then, select up to 5 diagnoses to compare

Add

Remove

Follicular carcinoma

Follicular adenoma

Papillary carcinoma

First, select a body system

Thyroid Select a different body system

View Differential

Differential Diagnosis: low-fi prototype

27

Home > Differential Diagnoses >

Comparison

Image caption (stain, magnification)



• Diagnostic Pearl



25 additional images available

View complete diagnostic information for Follicular carcinoma





View complete diagnostic information for Follicular adenoma





View complete diagnostic information for Follicular carcinoma

Papillary carcinomaRemove from comparison

Follicular adenomaRemove from comparison

Follicular carcinomaRemove from comparison

Differential Diagnosis: low-fi prototype

28

Differential Diagnosis: as deployed

29

Differential Diagnosis: as deployed

30

3000 pages >8000 images organised by organ

system 9th edition includes diagnostic

pearls

From Pathology Book….

Online diagnostic clinical decision support covering general pathology.

Designed to be used at the point of work. Image based. Core is differential diagnosis tool to compare conditions. At launch will includes 500 most useful conditions based

on feedback from Pathologists

.....to Diagnostic Tool

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

Thank [email protected]

User Driven Development For Palinet

Business

Transcript of User Driven Development For Palinet