Improving the User Experience

1,427 views

Published on

Andy Powell, Eduserv; presentation given at the OpenAthens seminar: Work smarter not harder with FAM. March 2011

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,427
On SlideShare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
15
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Improving the User Experience

  1. 1. Putting the “rated” into federated<br />improving the user experience<br />Andy Powell<br />@andypowe11<br />
  2. 2. Usability 101<br />“the study of the ease with which people can employ a particular tool or other human-made object in order to achieve a particular goal” (Wikipedia)<br />
  3. 3. A framework for usability<br />learnability: how easy is it for users to accomplish basic tasks the first time they encounter the design?<br />efficiency: once users have learned the design, how quickly can they perform tasks?<br />memorability: when users return to the design after a period of not using it, how easily can they re establish proficiency?<br />errors: how many errors do users make, how severe are these errors, and how easily can they recover from the errors?<br />satisfaction: how pleasant is it to use the design?<br />
  4. 4. Discovery, access and use<br />with federated access management, “usability” covers a lot of ground<br />from discovery (Google search vs. institutional portal)<br />…thru access… (the publisher’s website)<br />to use (having the thing on your desktop)<br />
  5. 5. Even ‘access’ spans multiple players<br />the publisher’s website<br />the federation WAYF service (in some cases)<br />the institutional identity provider (IdP)<br />
  6. 6. From perspective of the user<br />(and the user’s institution)<br />the institutional IdP is always the same<br />but every publisher website has different look and feel (for login)<br />some use the WAYF, some don’t<br />not easy for the institution to provide ‘help’ documentation that covers all cases<br />
  7. 7. From perspective of the publisher<br />every user sees the same website<br />but each user has different IdP (and possibly WAYF)<br />not easy for the publisher to provide ‘help’ documentation that covers everyone<br />
  8. 8. And… wider context<br />need for global publishers to accommodate multiple‘academic’ federations<br />need for publishers to handlenon-academic audiences (local usernames/passwords, pay-per-view, etc.)<br />need for publishers to handle social media (Facebook, Google, Twitter, etc.)<br />
  9. 9. 3 examples…<br />of current practice<br />
  10. 10.
  11. 11.
  12. 12.
  13. 13.
  14. 14.
  15. 15.
  16. 16.
  17. 17.
  18. 18.
  19. 19.
  20. 20.
  21. 21.
  22. 22.
  23. 23.
  24. 24.
  25. 25. Some ongoing work…<br />back in 2009, JISC commissioned a “Publisher Interface Study” by Rhys Smith at Cardiff<br />improved WAYF<br />embedded discovery module for Shibboleth (by Rod Widdowson, Steading System Software)<br />KantaraUniversal Login Experience (ULX) Working Group<br />Google<br />
  26. 26.
  27. 27.
  28. 28.
  29. 29.
  30. 30.
  31. 31.
  32. 32.
  33. 33.
  34. 34.
  35. 35.
  36. 36.
  37. 37.
  38. 38.
  39. 39.
  40. 40.
  41. 41.
  42. 42.
  43. 43.
  44. 44.
  45. 45.
  46. 46.
  47. 47.
  48. 48. Conclusions<br />usability across federated login is hard<br />variety of practice by today’s publishers<br />variety of exploratory work in progress<br />need to use this to drive more consistency<br />no longer just an ‘academic’ problem (c.f. Kantara and Google work)<br />at Eduserv, we are watching this space<br />

×