Empfohlen
Weitere ähnliche Inhalte
Ähnlich wie Improving Catalyst by Reaching Out
Ähnlich wie Improving Catalyst by Reaching Out (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Improving Catalyst by Reaching Out
- 1. Improving Catalyst by Reaching Out Sean Hannan & Dave Kennedy
- 2. Some facts.
- 3. 135,789 total page views
- 7. 1,550 searches for online materials
- 8. 465 searches for journals
- 9. 146 records texted to mobile devices
- 10. 71% of Catalyst traffic comes from search engines
- 11. 70% comes from Google
- 13. Most viewed item: Gil Scott-Heron’s MFA thesis.
- 14. Why am I telling you this?
- 15. Other data collection methods:
- 17. User Testing
- 20. Locate a thesis on architecture published from 1900 – 1913 that can be found at the Eisenhower location. Save these to your Selected Items.
- 22. Users Tested 5 graduate 1 undergraduate 1 faculty 6 of the 7 indicated that the interface was easy to use and provided satisfying user experience.
- 23. Focus Groups
- 24. An example.
- 25. 146 records texted to mobile devices
- 26. “I like the SMS option and the search capability seems to be a lot better than the current one.” “The option to SMS a listing from the results screen is very nice…”- via Feedback
- 27. Only 3 of the 7 users in the user tests bothered to even rank it as a visible feature. The 3 that did, ranked it of low importance.
- 29. Questions?
Hinweis der Redaktion
- For the first 81 days.
- Not 70% of search engine traffic. Of all traffic.
- Because we are collecting this data in order to improve Catalyst.
- We’re not just limited to what our programming can record.
- Feedback form directly on every page of Catalyst. Asks for your comment, some contextual information, and an optional e-mail address if you’d like a response. Every item that has come in with an e-mail address has been responded to. 234 pieces of feedback have been submitted so far.
- Between April 5 – April 15, Cynthia York and I conducted one-on-on user tests with members of the MSEL community
- Silverback. Allowed us to document the user tests. Records the screen activity and user image and voice.
- (Blurred out user) Recording the face and voice is important. Someone may tell you (out of embarrassment, perhaps) that they did not have any trouble performing the tasks, but a scrunched up face and exasperated breaths may indicate otherwise.
- Example of a task that the users were asked to perform. Aimed at seeing how comfortable users are with using the limits, date range selection, and the selected items features of Catalyst
- Handout given to the user to rank the elements on the page. We received a lot of comments that indicated that certain things should and should not be on the page. It was very useful to make those preferences quantitative.
- Would have liked to get more, of course, but we are approaching this with a short testing cycle and then integrating the results into our updates.
- Members of the Catalyst team met with Eisenhower librarians, and members of the PI and TS HILTS groups to answer any questions and address any concerns relating to those user groups. Sometimes feedback can be hard to articulate in a text box or e-mail, so like the user testing, we felt that a face-to-face approach would gain some meaningful insights.
- So how are we using all of this data? I’m going to give you an example.
- Not enough. We think it’s a cool feature. People love to text. Mobile devices are everywhere. Maybe they’re not into it as much as we think they are.
- No, they do.
- Ah ha! Got it. People don’t know what it is. When you don’t know what something is, you don’t click on it.
- Here’s how it currently appears in Catalyst. Without all of that preamble, would you have ever clicked on that icon? Does it even look clickable for that matter? The icon was a design compromise to address another concern that we heard early on “There’s too much text.” It’s a compromise that didn’t work. We would have never known that, however, if we hadn’t bothered doing the research. And we would have spent a time and energy on a feature that no one would use. Some brief explanatory text will return in a future revision.