Top Banner
Sonya Betz ([email protected]) | Robyn Hall ([email protected]) | October 2014 MICROINTERACTIONS MACRO RESULTS Why You Should Design the Details
30

Microinterations, macro results: Why you should design the details

Jul 15, 2015

Download

Technology

Robyn Hall
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Microinterations, macro results: Why you should design the details

Sonya Betz ([email protected]) | Robyn Hall ([email protected]) | October 2014

MICROINTERACTIONSMACRO RESULTS

Why You Should Design the Details

Page 2: Microinterations, macro results: Why you should design the details

IRs aka “Roach Motels”

Page 3: Microinterations, macro results: Why you should design the details

roam.macewan.ca

Page 4: Microinterations, macro results: Why you should design the details

User testing= Observation

Page 5: Microinterations, macro results: Why you should design the details

User testing is not…

Asking users their opinions:

What do you think?

Do you like it?

Don’t ask! Watch…

Page 6: Microinterations, macro results: Why you should design the details

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?

Page 7: Microinterations, macro results: Why you should design the details

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

Page 8: Microinterations, macro results: Why you should design the details

“A contained product moment that revolves around a single use case –a tiny piece of functionality that only does one thing” – Dan Saffer

Page 9: Microinterations, macro results: Why you should design the details

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…

Page 10: Microinterations, macro results: Why you should design the details

= Do It Yourself

= Let Us Do It

Contribute Processes

Page 11: Microinterations, macro results: Why you should design the details
Page 12: Microinterations, macro results: Why you should design the details
Page 13: Microinterations, macro results: Why you should design the details

Let Us Help

Page 14: Microinterations, macro results: Why you should design the details

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.

Page 15: Microinterations, macro results: Why you should design the details
Page 16: Microinterations, macro results: Why you should design the details
Page 17: Microinterations, macro results: Why you should design the details

Other file types?

Page 18: Microinterations, macro results: Why you should design the details
Page 19: Microinterations, macro results: Why you should design the details

Select and click Add. Add additional collections as appropriate for any MacEwan co-contributors.

Page 20: Microinterations, macro results: Why you should design the details
Page 21: Microinterations, macro results: Why you should design the details
Page 22: Microinterations, macro results: Why you should design the details

Citation Please provide a complete citation for previously published works

Page 23: Microinterations, macro results: Why you should design the details
Page 24: Microinterations, macro results: Why you should design the details
Page 25: Microinterations, macro results: Why you should design the details
Page 26: Microinterations, macro results: Why you should design the details
Page 27: Microinterations, macro results: Why you should design the details
Page 28: Microinterations, macro results: Why you should design the details
Page 29: Microinterations, macro results: Why you should design the details

Conclusions

Page 30: Microinterations, macro results: Why you should design the details

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