Pragmatic Contextual Inquiry ( John Law) - Presentation Transcript
Pragmatic Voice-of-the-Customer Research Discovering Unmet Market Needs Through Simplified Contextual Inquiry by John Law Product Management View Webinar September 19, 2007
What is “Contextual Inquiry”?
Field studies observing users in their native environment
Origins in ethnography (branch of anthropology)
“ Go where the customer works, observe the customer as he or she works, and talk to the customer about the work.” Holtzblatt & Beyer
Enables a thorough understanding of your target-users’ work practices
Software Product Management / Market Research / New Product Development
Purpose of contextual inquiry
“ If necessity is the mother of invention, then if you don't know what the users need you can't invent.” Dan Bricklin
Use to...
generate breakthrough new product ideas
develop marketing strategies
Don’t use for...
quick and dirty projects
narrow scope projects
The Iceberg What customer says they want What they really need Software Product Management / Market Research / New Product Development
What you gain
In-depth understanding of user needs
Authoritative knowledge of your target market
Clear perspective for establishing product development priorities
Spotting compensatory behaviors
Software Product Management / Market Research / New Product Development
Traditional contextual inquiry
Team of people
Travel to location
1-2 sessions per day
Barriers to this method
Resource intensive and expensive
Time consuming for product managers
Intrusive to customers/users
Software Product Management / Market Research / New Product Development
Pragmatic contextual inquiry
Light-weight, accessible alternative for software products and web applications
Advantages to this method
Leverage internet-based utilities
Automate recruiting and screening participants
Observe remotely from the convenience of your office
Software Product Management / Market Research / New Product Development
Methodology – 7 simple steps
Plan
Solicit participants
Screen candidates
Schedule sessions
Observe online (and record)
Closing interviews
Summarize findings (use video snippets)
Software Product Management / Market Research / New Product Development
Planning – Think it through
Objectives
Logistics & technology requirements
Project schedule
Participant profiles
Recruiting approach
Session protocol/outline
Observation data collection template
Software Product Management / Market Research / New Product Development
Recruiting participants
Use targeted ads on user “watering holes” sites
Emphasize that it entails no work, minimum effort, little time
Enticement (typically some form of compensation)
Don’t disclose your company’s name
Screening candidates
Use an online survey tool
Include brief overview of study
Maintain anonymity but establish legitimacy
Collection minimal profile information
Don’t ask for personal info except email address
Include schedule to collect dates/times when candidate is available to participate
Software Product Management / Market Research / New Product Development
Sample screener survey Columbia University Dept. of Computer Science
Selection and scheduling
Review survey response to select participants based on qualifications and schedule fit
Generic email account (gmail, yahoo, hotmail)
Assign session date/time
Require confirmation
Provide session access details
Software Product Management / Market Research / New Product Development
Sample email correspondence Software Product Management / Market Research / New Product Development
Observe and record
Internet-based tools for remote observation
Web conferencing services (Webex, LiveMeeting, etc.)
UserVue from TechSmith
Ethnio by Bolt | Peters (current getting a makeover)
Software Product Management / Market Research / New Product Development
UserVue observation console Software Product Management / Market Research / New Product Development
0 comments
Post a comment