Contextual Inquiry slides presented to Baobab staff, February 2015

2. ●
●

3. ●
●

8. ●
●
●
●

9. Context: social, organizational, etc.
System:
desktop,
mobile,
tablet, etc.User
Tool
Task
Data analysis?
Writing?
Graphing?

23. Iterative process

24. “All models are wrong…”

25. Key Points

26. Key Questions & Tradeoffs
●
●
●
●
●
●
●

27. Who: Stakeholder Analysis
Rosson & Carroll 2002
●
●
●
●
●

28. Stakeholders - Challenges
●
●
●
●
●

29. Example: Cancer Deep Phenotyping Extraction from
Electronic Medical Records
G. Savova, and R. Jacobson co-PIs

30. DeepPhe Stakeholders

31. DeepPhe Stakeholder:
Translational Scientist with
“Dry Bench” Bioinformatics skills
Background
• PhD trained scientist in wide range of fields relevant to cancer (e.g. genetics, pharmacology, molecular
biology, immunology)
• Analytically trained and familiar with statistical methods, including genomics/bioinformatics.
• Unfamiliar with NLP Concepts
• Unfamiliar with NLP tools and resources
• Limited familiarity with OO programming languages
• Familiar with text manipulation languages ( e.g. Python, Perl, Ruby)
Premise/story
• Cancer biologists are unraveling the genomic and molecular changes that drive tumors towards
specific behaviors such as progression and metastasis. Identifying these molecular drivers will
require information about the specific cancer behaviors that they produce. This class of users
will examine data for case finding and to classify cases based on outcome.

32. DeepPhe Stakeholder:
Translational Scientist with
“Dry Bench” Bioinformatics skills
Expectations
• Population-level statistics, summarization, and comparisons.
• Graphical displays, including bar charts, error bars, etc.
• Inferential statistics
• Export to statistical software (SAS,SPSS,RapidMiner, R)
Information needs
• Demographic data
• Treatment data
• Disease progression, metastasis and other outcomes (e.g. RECIST criteria)
• Available biomarkers and other clinical molecular information not in structured format (e.g.
Oncotype Scores)
Current tools and limitations
• Mac desktop, Linux and Windows computing
• Some familiarity with DBMS and data management principles
• Knowledge and use of statistical software (e.g. SAS, SPSS, RapidMiner, R), but time required
to extract and format data is substantial.
• Routine access to PHI clinical text for work, able to interpret clinical text reports, but in-
depth review is too error-prone and time-consuming.

33. Checklist: Stakeholder
Identification

34. KCH Lab Stakeholders?

35. Stakeholder definition issues?

36. Data collection

37. “talking to the users..”

38. Observation

39. Types of Observations

40. Passive Observation

41. Checklist:
Observation Planning

42. Checklists: Observations

43. Checklists: Observations

44. Checklists: Observations

45. Drawbacks of observations

46. Contextual Interviews
Synthesis Lectures in Human-
Centered Informatics
Morgan & Claypool 2014

47. Contextual Interviews
●
●
●
●

48. Principles of contextual inquiry
modified from Beyer & Holtzblatt 1998, 2014

49. Context
Beyer & Holtzblatt 1998,2014

50. Partnership
Beyer & Holtzblatt 1998, 2014

51. Interpretation
Beyer & Holtzblatt 1998, 2014

52. Focus
Beyer & Holtzblatt 1998, 2014

53. Accomplishment
Beyer & Holtzblatt 1998, 2014

54. Identity
Beyer & Holtzblatt 1998, 2014

55. Sensation
Beyer & Holtzblatt 1998, 2014

56. The “Triangle of Joy in Use”
Beyer & Holtzblatt 2014

57. Checklist: Contextual Inquiries

58. Challenges

59. Contextual Inquiry Example

60. Analysis exercise

61. Recording

62. How many participants?
●
●
●
●
●

63. When to involve users?
●
●
●
●

64. Baobab Contextual Inquiry
Exercise

65. Participatory Design
Kemmis & McTaggart (1982)
reprinted in Clemensen, et al. 2007
Clemensen, et al. 2007
•Users involved throughout
•Scenario design between CD
and PD
•Pros and Cons?

66. Ethnography
●
●
●
●
●
●
●

67. Tradeoffs
●
●
●
●

68. Rapid Ethnography
Millen, 2000
●
●
●
●
●
●
●
●

69. Rapid Ethnography

70. Eliciting Feedback
●
●
●
●
●
●

71. Discussion of LIMS

72. Checklist for LIMS:
Observation Planning

73. Where are we?

74. Scenario-Based Design
Rosson & Carroll 2001, 2002

75. “Five Reasons for Scenario-Based Design”
J.M. Carroll, 1995

76. Scenario-based design
Rosson & Carroll 2001, 2002

77. Problem scenario: visit to a
science fiction club meeting
Rosson & Carroll 2002

78. Checklist: Problem Scenarios