Notes
Outline
Listening to the Learner:
Strategies, Examples, and Implications from Research on a Medical Information Website
Jennifer Turns
Research Scientist, PETTT & CELT, University of Washington
Ph.D., Industrial Engineering, Georgia Institute of Technology
Setting the Stage
Topics
Informational Websites (e.g., home info, envt info)
When users are learners
An example
Health Information (e.g., Arthritis Source)
PETTT (“We”)
Goal: Enhance site, Support other educators in doing this
Team: Dr. Rick Matsen, Scott Macklin, Tracey Wagner, Ralph Warren, Kristina Liu, Aaron Louie, Julianne Fondiller, Jake Burghardt, …
My Role
Theory: Interface design, Cognitive Science, Learning, Usability, Design
Research: Design tools, Design processes, Educational technology
Talk Overview
Designing Informational Websites
Challenges
Why “Listening to the Learner”
Examples from Our Research
Our Informational Website – The Arthritis Source
Sampling of our “Listening to the Learner” Efforts
Wrap up
General observations
Current directions
Designing Informational Websites
Challenges include
Technical challenges
Business challenges
Lifecycle challenges
Collaboration/teamwork challenges
Communication/Education challenges
We know to “Know thy user”
Guidelines for effective design
(Technical Communication, August 2000)
Application of many guidelines requires knowledge of users
“Be sure that all links indicate that they are links” Farkas & Farkas, p. 342
“Make pages trustworthy.”  Spyridakis, p. 373
“Make sure that the visual elements in your display are large enough to be seen and interpreted.” Williams, p. 383
“Choose tone that fits the message and the audience.” Spyridakis, p. 371
“Select content that will be interesting and relevant to audience”, Spyridakis, p. 361
We know to “Know thy user”
Guidelines for effective design
August 2000 Issue of Technical Communication
“Know thy user” is imperative
Application of guidelines requires knowledge of users
Audience analysis is common theme
User-centered design (UCD) focuses on user
(Norman and Draper 1988)
Users?
On-the-job tasks
Budgeting with software
Maintaining customer information in database
Life tasks
Banking with Bank of America online
Other tasks
Email
Collaboration via tools
Knowing the User
What
Demographics
Tasks
Goals
Tools
…
How
Interviews
Observation
Laboratory tasks
Surveys
Contextual Inquiry
Think aloud protocols
Cognitive Theory
…
When users are learners?
Characteristics of learners
Growth (Soloway, 1994)
Diversity (Soloway, 1994)
Motivation (Soloway, 1994)
Prior Understandings (NRC, 1999)
Thinking about implications
What to know and why
Knowing users over time
Variations (how many to know)
Time required to truly “know”
Listening to Learner
How?
Online survey
Phone interviews
(Tools are similar)
“Listening aids”
Use may be different
Duration
What to listen for.
Growth
Diversity
Motivational Issues
Misconceptions
Listening to the Learner
Why this phrase
Is listening different than knowing?
An Admission - It is working for us….
Tentative thoughts…
Open to surprises (designer not all-knowing)
Implies duration (listen over time)
Power relationship (learner control)
Talk Overview (revisited)
Designing Informational Websites
Challenges
Why “Listening to the Learner”
Examples from Our Research
Our Informational Website – The Arthritis Source
Sampling of our “Listening to the Learner” Efforts
Wrap up
General observations
Current directions
Arthritis Source
Provides
Quality, authorized content
Variety of arthritis issues
History
“Information therapy” emerges
Dr. Matsen developed in 1995
Arthritis Foundation Materials
Directions
Learner-centered content
Sustainable model for content generation
Arthritis Source:  A PETTT exemplar
PETTT seeks to enhance the effectiveness of the University of Washington's faculty and thus of the institution itself, by creating a campus framework to promote the thoughtful exploration, development, assessment, and dissemination of next-generation technologies and strategies for teaching and learning.
Source: http://depts.washington.edu/pettt
PETTT Activities
Exemplars as testbeds for research and design
Disseminate tools, ideas, methods, findings to educators
Listening to Arthritis Source Learners
Research within Arthritis Source
Log files
Online Survey
Quick Poll
“Orthoedu” – Email your question
Research apart from Arthritis Source
Phone survey
Bulletin board discussion analysis
Listening to Arthritis Source Learners
Research within Arthritis Source
Log files
Online Survey
Quick Poll
“Orthoedu” – Email your question
Research apart from Arthritis Source
Phone survey
Bulletin board discussion analysis
Listening to Arthritis Source Learners
Research within Arthritis Source
Log files
Online Survey
Quick Poll
“Orthoedu” – Email your question utility
Research apart from Arthritis Source
Phone survey
Bulletin board discussion analysis
Listening: Online Survey
Goals
Listen for goals and success
Listen demographics and general user info
Listen for unexpected…
History
Designed with Julianne Fondiller (TC), Jake Burghardt (TC)
Implemented by PETTT staff
Data collection ongoing
Analysis, Oct-Dec, by Kristina Liu (Education)
Analysis, 192 complete (270 start, 62% completion)
Online Survey
Online Survey: User Success?
Question:
3a: Why have you visited the site today?…
3b: Have you been successful?
Surprise:
31% did not know
Online Survey: Who are they?
Question
Which category best describes you?
Surprise:
22% selected “other”
Online Survey: Location?
Question:
Where are you located?
Surprise:
Worldwide…
(International Issues)
Online Survey: Age?
Question:
What is your age?
Surprise:
All ages…
Online Survey: Is it feasible?
Results
192 complete (270 start)
62% completion rate
Duration: 13.25 min
Listening: Phone Interviews
Goals
Listen for usability/usefulness of Arthritis Source
Listen for knowledge of arthritis
(osteoarthritis and rhematoid arthritis)
History
Protocol designed with
Tracey Wagner (TC) and Kristina Liu (Education)
Recruitment via online survey
Data collection complete
Interviews: Interactions w/ Site
Some general observations
Extensive comparison shopping
Rave reviews
Offers to contribute
Surprise:  Enthusiasm for site
Interviews: Arthritis Knowledge
Example
Osteoarthritis and Osteoporosis Confusion
Surprise:
Getting informants to talk about knowledge
Comfort with limited knowledge
Listening: “OrthoEdu”
Goals
Listen for users situated questions
Information not on site / not findable
Complexity and nature of their questions
History
One of the original “listening aids”
Dr. Matsen answers questions
Analysis by Ralph Warren (Medical Informatics)
“OrthoEdu”
OrthoEdu: Topics?
Question Topics
Other Observations:
Diversity, Complexity
OrthoEdu: Surprises?
Change in Function
Initially developed as “listening aid”
Current efforts to leave as service (automate)
Learning of design team members
Initially, “We cannot answer this”
Later, “This could be answered with information on the site, but the information is hard to find and synthesize.”
Talk Overview (revisited)
Designing Informational Websites
Challenges
Why “Listening to the Learner”
Examples from Our Research
Our Informational Website – The Arthritis Source
Sampling of our “Listening to the Learner” Efforts
Wrap up
General observations
Current directions
Listening to the Learner
We are starting to understand our learners
Lots of diversity
Growth in knowledge, concerns
Levels of motivation
Levels of knowledge
Benefits of Listening
Design iterations
Surprises…
General Findings
Learners like to be listened to
Challenges:
Deciding when to stop collecting information
Integrating all information into design
Representing all information
Coordination and timing, getting technical issues in sync with our information
Transformative nature of listening –
Current Directions
Design new content for site
Templates to support distributed authorship
Templates informed by all information collected
Distributed authors will not get to listen
Continuing listening as the new information is released…
Making listening aids available to UW community...
Describe strategies
Disseminate via UW Catalyst
QUESTIONS?
Backup Slides
PETTT Research Approach
OrthoEdu: Complexity?
Requests for information
Specific details
Often more than one question
Complex questions