Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Sonya Betz (betzs3@macewan.ca) | Robyn Hall (hallr27@macewan.ca) | October 2014
MICROINTERACTIONS
MACRO RESULTS
Why You Sh...
IRs aka “Roach Motels”
roam.macewan.ca
User testing= Observation
User testing is not…
Asking users their opinions:
What do you think?
Do you like it?
Don’t ask! Watch…
At its most basic
1. get some representative users
2. ask the users to perform representative tasks
3. observe and identif...
Microinteractions
the difference between “a product we love and
a product we just tolerate”
Saffer, D. (2013). Microintera...
“A contained product
moment that revolves
around a single use case –
a tiny piece of functionality
that only does one thin...
What is a Microinteraction?
“a contained product moment that revolves
around a single use case — a tiny piece of
functiona...
= Do It Yourself
= Let Us Do It
Contribute Processes
Let Us Help
Not sure if you hold copyright? You can look up journal archiving policies using SHERPA RoMEO, review publication agreemen...
Other file types?
Select and click Add. Add additional collections as appropriate for any MacEwan co-contributors.
Citation
Please provide a complete citation for previously published works
Conclusions
References
Jean, B. T., Soo Young, R., Yakel, E., & Markey, K. (2011). Unheard voices:
institutional repository end-users....
Microinterations, macro results: Why you should design the details
Microinterations, macro results: Why you should design the details
Microinterations, macro results: Why you should design the details
Microinterations, macro results: Why you should design the details
Microinterations, macro results: Why you should design the details
Microinterations, macro results: Why you should design the details
Microinterations, macro results: Why you should design the details
Microinterations, macro results: Why you should design the details
Microinterations, macro results: Why you should design the details
Microinterations, macro results: Why you should design the details
Microinterations, macro results: Why you should design the details
Microinterations, macro results: Why you should design the details
Microinterations, macro results: Why you should design the details
Upcoming SlideShare
Loading in …5
×

Microinterations, macro results: Why you should design the details

922 views

Published on

Details matter. Each of these presentations share tips and advice on getting the interactions and content on your website right for your users. MacEwan librarians look at how micro-interactions, the moments when we delight our users by refining the way we offer services, lead to macro-results. Get concrete recommendations for designing positive micro-interactions with library users in mind. Speakers use their own experience designing a new institutional repository to outline steps to identify, refine, and test micro-interactions with users, and highlight the impact of their strategy on the overall user experience.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Microinterations, macro results: Why you should design the details

  1. 1. Sonya Betz (betzs3@macewan.ca) | Robyn Hall (hallr27@macewan.ca) | October 2014 MICROINTERACTIONS MACRO RESULTS Why You Should Design the Details
  2. 2. IRs aka “Roach Motels”
  3. 3. roam.macewan.ca
  4. 4. User testing= Observation
  5. 5. User testing is not… Asking users their opinions: What do you think? Do you like it? Don’t ask! Watch…
  6. 6. At its most basic 1. get some representative users 2. ask the users to perform representative tasks 3. observe and identify what users do, where they succeed, and where they have difficulty 4. Rinse and repeat http://www.nngroup.com/articles/usability-101- introduction-to-usability/ Users performing tasks: Successes? Challenges?
  7. 7. Microinteractions the difference between “a product we love and a product we just tolerate” Saffer, D. (2013). Microinteractions: Designing with details. Cambridge: O’Reilly. Microinteractions Products we love Products we tolerate
  8. 8. “A contained product moment that revolves around a single use case – a tiny piece of functionality that only does one thing” – Dan Saffer
  9. 9. What is a Microinteraction? “a contained product moment that revolves around a single use case — a tiny piece of functionality that only does one thing.” Focus: Single tasks…
  10. 10. = Do It Yourself = Let Us Do It Contribute Processes
  11. 11. Let Us Help
  12. 12. Not sure if you hold copyright? You can look up journal archiving policies using SHERPA RoMEO, review publication agreements, or contact rights holders directly. Or contact us with information about your work (e.g., title, publisher). We will look into it and get back to you. Learn more.
  13. 13. Other file types?
  14. 14. Select and click Add. Add additional collections as appropriate for any MacEwan co-contributors.
  15. 15. Citation Please provide a complete citation for previously published works
  16. 16. Conclusions
  17. 17. References Jean, B. T., Soo Young, R., Yakel, E., & Markey, K. (2011). Unheard voices: institutional repository end-users. College & Research Libraries, 72(1), 21-42. Retrieved from http://crl.acrl.org Nielsen, J. (2012, January 4). Usability 101: Introduction to usability. Retrieved from http://www.nngroup.com/articles/usability-101-introduction-to-usability Salo, D. (2008). Innkeeper at the roach motel. Library Trends, 57(2). Retrieved from http://muse.jhu.edu/journals/library_trends Saffer, D. (2013). Microinteractions: Designing with details. Cambridge: O’Reilly. Dekker, F. & McCarthy, A. (2014). Little big details: Your daily dose of design inspiration. Retrieved from http://littlebigdetails.com

×