UX Learnings - II

As I progress with the second phase on top of our UX learnings, I have to share these notes to help you and myself in the future.

Remember the design for

Users to use interfaces to accomplish a task.
The best interface can only be designed if we understand the user and
the task they want to accomplish.

---

Every good design distilled from User Interface Design Cycle

User Interface Design Cycle, similar to the iterative process, right?

To have a proper design you first need to gather requirements to understand how the user completes the given task today. This is even before you are offering your design.
Therefore, it requires a certain set of requirement-gathering methods to be placed like:

1. Naturalistic Observations,

2. Surveys,

3. Focus Groups,

4. Interviews

Below is a chart to give you an understanding of the interaction and place perspective.

By conducting these techniques, you get

• Qualitative data — interpretation-based, descriptive, and related to language.
  It helps us to understand why, how, or what happened behind certain behaviors.

• Quantitative data — numbers-based, countable, or measurable.
  It tells us how many, how much, or how often in calculations.

Please remember that while using either of these techniques you may fall into various statistical biases. Therefore, the way how you craft your question needs to be reviewed carefully. The most common ones that you can fall into for your surveys:

• Recall bias —when we ask users to tell us about things that happened in the past,

  there is a chance that their recollections are inaccurate.

• Social-desirability bias —when we ask users about their opinions, they may want to respond in a way that pleases the researcher. Or that is per their cultural norms, but that may not reflect their actual attitudes

• Sampling bias —we only have data from the users in our study who chose to participate. These may not represent the users we couldn't reach or

  who didn't want to participate

---

Until now, you gathered requirements by various techniques and it’s time to present them. Before sharing your findings, it’s better to build a narrative. This narrative can be delivered with

• Descriptive statistics — allows us to summarize quantitative information

  • Mean — is the average of all of the numbers.

  • Median — is the middle number, when in order.

  • Range — is the largest number minus the smallest number.

• Characteristics —allow us to highlight a tabular summary of our findings,
  

  

• User personas
  

  

---

Some of the references are:

1. personalexcellence.co/blog/brainstorming-techniques/

2. leadinganswers.typepad.com/leading_answers/2009/03/nonfunctional-requirements-minimal-checklist.html

3. searchsoftwarequality.techtarget.com/answer/Differentiating-between-Functional-and-Nonfunctional-Requirements

4. usabilityfirst.com/usability-methods/facilitated-brainstorming/

5. blog.abovethefolddesign.com/2010/11/11/5-powerful-ways-to-brainstorming-with-teams/

6. inspireux.com/2013/07/18/tips-for-structuring-better-brainstorming-sessions/

7. slideshare.net/jessicaivins/aiga-cincy-uxworkshop01

8. asq.org/learn-about-quality/idea-creation-tools/overview/affinity.html

9. mindtools.com/pages/article/newTMC_86.htm

10. infodesign.com.au/usabilityresources/affinitydiagramming/

—

1. http://www.usability.gov/how-to-and-tools/methods/prototyping.html

2. http://www.telono.com/en/articles/lo-fi-vs-hi-fi-prototyping-how-real-does-the-real-thing-have-to-be/

3. http://www.usabilityfirst.com/glossary/high-fidelity-prototype/

4. http://www.atlargeinc.com/insights/high-fidelity-vs-low-fidelity-prototyping-web-design-and-app-development