Why Do Organizations Have Trouble Embracing Qualitative Research? | indi young Because the business world shuns uncertainty, qualitative research gets twisted so that the conclusions sound like they were deduced, and their validity unimpeachable. Business research adheres to its cousin in the laboratory, where validity is determined by empirical evidence—which is a positivistic view. But, positivism is not embraced universally in the social sciences, and it is certainly not compatible with inductive reasoning. So why do businesses automatically turn to positivism when trying to understand human behavior and reasoning? When positivism was first extended to the academic social sciences, it met with opposition. Then another landmark event happened in the late 1990’s. A summary: Cognitive empathy work falls under constructivism and relativism. Now you have the explanation for why business seems to abhor qualitative research, and you can see it follows the historic tendency for natural sciences to get better funding and respect in the academic world.
Envisioning Experience Outcomes By Jim Nieters and Pabini Gabriel-Petit Published: April 20, 2015 “When your organization’s goal is to differentiate on the experience, you must start every product-development project by defining the experience that you want people to have with your product or service. ” When your organization’s goal is to differentiate on the experience, you must start every product-development project by defining the experience that you want people to have with your product or service. This is the fourth column in our series about what companies must do if they want to stop producing average user experiences and instead design great experiences. When we say that companies must start by envisioning experience outcomes, we mean that you must take the time and do the work to set a clear and worthy vision for your product or service—one that will delight your users and customers. Nevertheless, the goal of envisioning experience outcomes does not stand at odds with agile methods. Defining Clear Goals Apple
Ray Kurzweil Raymond "Ray" Kurzweil (/ˈkɜrzwaɪl/ KURZ-wyl; born February 12, 1948) is an American author, computer scientist, inventor, futurist, and is a director of engineering at Google. Aside from futurology, he is involved in fields such as optical character recognition (OCR), text-to-speech synthesis, speech recognition technology, and electronic keyboard instruments. He has written books on health, artificial intelligence (AI), transhumanism, the technological singularity, and futurism. Kurzweil is a public advocate for the futurist and transhumanist movements, as has been displayed in his vast collection of public talks, wherein he has shared his primarily optimistic outlooks on life extension technologies and the future of nanotechnology, robotics, and biotechnology. Life, inventions, and business career Early life Ray Kurzweil grew up in the New York City borough of Queens. Kurzweil attended Martin Van Buren High School. Mid-life Later life Personal life
The Big UX Impact You Can Make With Just a Few Words When we think about designing a great user experience, it’s easy to get caught up with all the things. The fonts, the colors, the overall design, the content. Everything. But there’s another component to UX that can instantly delight—or disappoint—your users that you might be overlooking. It’s small, and if you blink you might miss it, but when done right you’ll remind your users there’s a human behind all that code and design. I’m talking about microcopy. For example, have you ever started to fill out a form, only to abandon it because you couldn’t imagine why all the requested information was needed? For many companies, microcopy is an afterthought and often overlooked as an opportunity to connect with your users. But just because microcopy is small, doesn’t mean it’s easy to implement. How to identify microcopy opportunities If you haven’t paid much attention to microcopy yet, it probably sounds like a big job to get started. Conversion rates Errors Usability testing How to use microcopy
WAI-ARIA Overview Quick links: WAI-ARIA, User Agent Implementation Guide, FAQ See also FAQ: What is the current status of WAI-ARIA development? Introduction WAI-ARIA, the Accessible Rich Internet Applications Suite, defines a way to make Web content and Web applications more accessible to people with disabilities. This page describes the problems that WAI-ARIA addresses, and introduces the WAI-ARIA suite of technical documents. Making Ajax and Related Technologies Accessible Figure 1: Tree control Web sites are increasingly using more advanced and complex user interface controls, such as tree controls for Web site navigation like the example in Figure 1. Another example of an accessibility barrier is drag-and-drop functionality that is not available to users who use a keyboard only and cannot use a mouse. Many Web applications developed with Ajax (also known as AJAX), DHTML, and other technologies pose additional accessibility challenges. Technical Solutions WAI-ARIA provides Web authors with the following:
How to Win on Mobile: Understanding Micro-Moments and Consumer Behavior The mobile landscape has completely changed consumer behavior. Over the last few months Google released new research that has major implications for brands who want to win in an increasingly mobile world. There’s no doubt that mobile is becoming more popular every year. In fact, mobile searches now outpace desktop searches in 10 countries, including the United States and Japan. Tens of millions of sites around the world use Google Analytics, and opt in to allow their data to be aggregated and used for research. Mobile sessions (visits to websites) have increased by 20% in the last yearThe amount of time spent per visit has decreased by 18%Yet at the same time, conversion rates on mobile have increased by 29% That means our old mental model of web behavior is out-dated. Think about your own life: When you want learn, find, do, or buy something, you reach for the nearest device to you—it’s like a digital reflex. The Implications of Micro-Moments The Customer Journey Has Changed 1. 2. 3. 4.
How to choose the right UX metrics for your product | Google Ventures When designing for the web, you can analyze usage data for your product and compare different interfaces in A/B tests. This is sometimes called “data-driven design”, but I prefer to think of it as data-informed design — the designer is still driving, not the data. To make this work in practice it’s important to use the right metrics. Basic traffic metrics (like overall page views or number of unique users) are easy to track and give a good baseline on how your site is doing, but they are often not very useful for evaluating the impact of UX changes. This is because they are very general, and usually don’t relate directly to either the quality of the user experience or the goals of your project — it’s hard to make them actionable. I’m part of a group of quantitative UX researchers at Google, and we like to think of large-scale data analysis as just another UX research method. The HEART framework Happiness: measures of user attitudes, often collected via survey. Goals Signals Metrics
Hermeneutics for Designers “To understand the whole of a book it is necessary to grasp its individual words and sentences, but those words and sentences only have meaning within the larger context of the book, hence interpretation must be a matter of constant revision: revising one’s sense of the whole as one grasps the individual parts, and revising one’s sense of the parts as the meaning of the whole emerges.” -Paul Kidder – Professor of Philosophy in Gadamer for Architects The process Paul Kidder identifies in Gadamer for Architects is known as the “hermeneutic circle.” Central to this process is understanding both the bigger picture in relation to the details and the details in relation to the bigger picture. This understanding grows and changes as we continue to come across additional details, whether the big picture is a UX project or something as simple as reading a book. In design we are constantly moving along the hermeneutic circle. How might we use hermeneutics to benefit our designs? Prejudices