FROM USABILITY TO USE:
MEASURING THE SUCCESS OF TESTBEDS
IN THE REAL WORLD
Emily Ignacio and Ann P. Bishop
University of Illinois
Moving from needs assessment to deployment of DeLIver, we are faced with new issues:
Also evolved new way of working to address these issues:
Presentation will be a candid reflection:
ROLL-OUT PANIC: WILL ANYONE USE OUR DL?
Web stats (Nov. 1-14, 1997)
Of 1540 attempted accesses
1276 (83%) stopped at NetID form
Of 186 people who entered NetID
91 (49%) stopped at registration form
HOW CAN WE REDUCE BARRIERS TO USE?
Which option will succeed? What are implications?
Simplify functionality
Cut authentication and registration
Streamline authentication and registration
Step up publicity (pinpoint hubs of use)
WHY REDUCE BARRIERS?
Testbed as hybrid
Make a better system!
Demonstrate high use!
Learn more about DLs and use!
WHAT IS CAUSING BAIL OUTS?
Pooling expertise and experiences
HOW SHOULD WE MEASURE USE?
Number of registered users
Type of registered user (are some users better than others?)
Frequency of use
Number of documents accessed
Number of search sessions conducted
HOW SHOULD WE GAUGE SUCCESS?
% of potential users
Likelihood of use
Use compared to what?
CUT AND TRY ENGINEERING:
STREAMLINED NETID FORM
Web stats (Dec. 9-19, 1997)
Of 462 attempted accesses
259 (56%) stopped at NetID form
Of 113 people who entered NetID
35 (31%) stopped at registration form
Fewer people are bailing out at the NetID form, but ....
Why are there so many fewer attempted accesses?
Why do more complete the registration form?
Introduction: The First Two Years or "I am user, Hear me Roar"
primary goal: to help system designers create usable and functional Digital Library.
methods reflected our goals
methods used during needs assessment phase:
The Shift to Usability Tests (the third year)
several teams; different goals, deadlines, and methods of evaluation
the wake up call
same deadline; needed to fuse different goals and methods of evaluation
teams began to merge
The "Threat" of Use: after the roll-out