{"id":7269,"date":"2018-04-17T13:26:52","date_gmt":"2018-04-17T12:26:52","guid":{"rendered":"https:\/\/uxstudioteam.com\/?p=7269"},"modified":"2022-05-19T14:34:41","modified_gmt":"2022-05-19T13:34:41","slug":"ai-ux","status":"publish","type":"post","link":"https:\/\/timemachine.uxstudioteam.com\/ux-blog\/ai-ux\/","title":{"rendered":"AI UX: 7 Principles of Designing Good AI Products"},"content":{"rendered":"

One thing we can learn from the latest fatal Tesla accident: AI and machine learning products need very careful designing. In this article, I will go through the seven basic AI UX principles products should follow.<\/b><\/p>\n

\"AI<\/p>\n

With the arrival of AI products, we enter a new era where machines start to behave differently. They not only perform our orders, but they do things by themselves. This will change how people react, how we behave and what we expect from these products.<\/span><\/p>\n

As designers, we aim to create useful, easy-to-understand products in order to bring clarity to this shady new world of machine learning. Most importantly, we want to use the power of AI to make people\u2019s lives easier and more joyful.<\/span><\/p>\n

So let\u2019s see how we can achieve these with good (UX) design. Here follow my seven principles of AI UX.<\/span><\/p>\n

AI UX Principle #1<\/strong>
\nDifferentiate AI content visually<\/span><\/h2>\n

In many cases, we use AI and machine learning to dig deep into data and generate new and useful content for ourselves. These can come in the form of movie recommendations on Netflix, translations in Google Translate, or sales predictions in CRM systems.<\/span><\/p>\n

AI generated content can prove extremely useful for people, but in some cases, these recommendations and predictions need greater accuracy. AI algorithms have their own flaws, especially when they don\u2019t have enough data or feedback to learn from.<\/span><\/p>\n

We should let people know if an algorithm has generated a piece of content so they can decide for themselves whether to trust it or not. Thus reads the first principle of AI UX.<\/span><\/p>\n

\"zendeskIn the image above you can see Zendesk\u2019s AI prediction for support tickets. It clearly identifies this as a prediction, so people know what to expect in that column.<\/span><\/p>\n

Firebase, a tool for mobile developers, labels the predicted data with a magic wand icon. Here they also provide information about the accuracy for the prediction, and users can also set the risk tolerance. Of course, this tool serves engineers who know more about machine learning. Everyday people would not necessarily understand \u201cHigh Risk Tolerance\u201d. But the magic wand still handily highlights AI content.<\/span><\/p>\n

\"ai<\/p>\n

AI UX Principle #2<\/span>
\nExplain how machines think<\/span><\/h2>\n

Artificial intelligence often looks like magic: sometimes even engineers have difficulty explaining how the machine-learning algorithm comes up with something. We see our job as a <\/span>UX company<\/span><\/a>\u00a0as helping people understand how machines work so they can use them better.<\/span><\/p>\n

This doesn\u2019t mean we should explain how a convolutional neural network functions in a simple photo search up. But we should give users hints about what the algorithm does or what data it uses.<\/span><\/p>\n

A good old example comes from e-commerce, where we explain why we recommend certain products. These recommendation engines were the first AI UX many people encountered, many years ago.<\/span><\/p>\n

\"AI<\/p>\n

Self-driving cars provide another good example of AI UX. To build trust in passengers, we suggest putting a screen in the cars where everyone can check what the car sees around itself. Check out this example design from our <\/span>self-driving lab project<\/span><\/a>.<\/span><\/p>\n

\"AI<\/p>\n

Last but not least, let\u2019s take a look at Drip, an email marketing tool. Not an AI product per se, it has a scoring function which shows newsletter subscriber engagement. Clicking on the score, you get a detailed list of actions which explains why people got their score.<\/span><\/p>\n

\"Drip<\/p>\n

AI UX Principle #3<\/span>
\nSet the right expectations<\/span><\/h2>\n

In the deadly <\/span>Tesla accident<\/span><\/a> mentioned above, the driver probably trusted the Autopilot system too much.<\/span><\/p>\n

Unlike other self-driving technologies like Google\u2019s cars, Tesla\u2019s autopilot does not have enough sophistication to navigate complex situations, so drivers must keep their hands on the wheel, even when using Autopilot. This driver didn\u2019t follow these instructions, regardless of getting multiple visual and voice notifications. Probably he thought the car could handle the driving itself.<\/span><\/p>\n

\"Tesla
\nWe must set the right expectations, especially in a world full of sensational, superficial news about new AI technologies.<\/span><\/p>\n

Some <\/span>chatbots<\/span> use messages to clarify their level of advancement. In this case, we try to lower the expectations with a nice copy and a kind character for the bot.<\/span><\/p>\n

AI UX Principle #4<\/span>
\nFind and handle weird edge cases<\/span><\/h2>\n

AI can generate content and take actions no one had thought of before. For such unpredictable cases, we have to spend more time testing the products and finding weird, funny, or even disturbing or unpleasant edge cases.<\/span><\/p>\n

Many funny and rude chatbot examples abound where the bot didn\u2019t understand the context or people gave them simple, but unexpected, commands.<\/span><\/p>\n

\"chatbot<\/p>\n

Many stories about <\/span>Amazon\u2019s Alexa<\/span><\/a> are coming out too. Once, it ordered a dollhouse just because it heard a conversation about it on the radio. In another example, a passport checker bot didn\u2019t accept photos of Asian people because <\/span>\u201cTheir eyes were closed\u201d<\/span><\/i>.<\/span><\/p>\n

\"passport<\/p>\n

Extensive testing in the field can help minimize these errors. Clear communication about the products capabilities can help humans understand these unexpected situations.<\/span><\/p>\n

Designers have to provide developers with information about user expectations, too. They can fine-tune the algorithms to prevent bad responses. In many cases they play with the trade-off between precision and recall.<\/span><\/p>\n

Optimizing for recall <\/span><\/i>means the machine-learning product will use all the right answers it finds, even if it displays a few wrong answers. Let\u2019s say we build an AI that can identify Picasso paintings. If we optimize for recall, the algorithm will list all the Picasso paintings, but some van Goghs will appear in the results too.<\/span><\/p>\n

Optimizing for precision<\/span><\/i> means the machine learning algorithm will use only the clearly correct answers, but it will miss some borderline positive cases. It will show only Picasso paintings (with no van Goghs), but it will miss some Picassos. It won\u2019t find all the correct answers, only the clear cases.<\/span><\/p>\n

When we work on AI UX, we help developers decide what to optimize for. Providing meaningful insights about human reactions and human priorities can prove the most important job of a designer in an AI project.<\/span><\/p>\n

AI UX Principle #5<\/span>
\nProvide engineers with the right training data<\/span><\/h2>\n

Creating an AI product from the engineering side usually takes these three high-level steps:<\/span><\/p>\n

    \n
  1. Finding the best AI algorithm for your task.<\/span><\/li>\n
  2. Feeding the AI training data. The AI learns from this data and creates a model it will use in the live product. In our example above, the training data would include a lot of paintings and the name of the painter for each.<\/span><\/li>\n
  3. Publishing the product. It will use the model trained before doing certain things for the users. It might also collect new data for later use, re-training the model and improving its own performance.<\/span><\/li>\n<\/ol>\n

    So, you really need training data. UX people help collect training data and define the expected outcome people want to see from the AI product.<\/span><\/p>\n

    Sometimes defining expected outcomes comes easy. Things start to get more difficult with outcomes subjective to the users. Which Netflix film recommendations really prove useful? The <\/span>UX team<\/span><\/a> aims to understand people and define these criteria.<\/span><\/p>\n

    Engineers will need training data, specifically well-defined outcomes for different inputs they can feed into the machine learning algorithm. Google <\/span>reportedly<\/span><\/a> hires \u201ccontent specialists\u201d, experts in the domain of the product who help build this training data set.<\/span><\/p>\n

    After collecting an initial data set, the engineers can train the algorithm and we can start doing user tests with early prototypes. With these tests, we double check the first trained models to see how they perform with real users.<\/span><\/p>\n

    In an AI project, you will need even closer collaboration between developers and designers. <\/span><\/p>\n

    If you are a Product Manager who wants to learn more about how to achieve this, read our <\/span>free UX e-book for Product Managers<\/span><\/a>!<\/span><\/p>\n

    AI UX Principle #6<\/span>
    \nUser testing for AI products (default methods won\u2019t work here)<\/span><\/h2>\n

    Testing the UX of AI products can prove much more difficult than for regular apps. These apps mainly promise to provide personalized content, but you hardly can emulate that with some dummy stuff in a wireframe. Two great methods can work though: Wizard of Oz testing and personal contents.<\/span><\/p>\n

    \"Wizzard<\/p>\n

    During Wizard of Oz studies, someone emulates the product\u2019s response from the background. It very often tests chatbots with a human being answering each message, pretending the bot is writing. <\/span><\/p>\n

    You can also use the test participant\u2019s personal content in test situations. Ask for their favorite musicians and songs, and use them testing a music recommendation engine. This tests people\u2019s assumptions and how they react to good and bad recommendations very well.<\/span><\/p>\n

    AI UX Principle #7<\/span>
    \nProvide an opportunity to give feedback<\/span><\/h2>\n

    The user experience of AI products gets better and better if we feed more data into the machine learning algorithms.<\/span><\/p>\n

    Look at the movie recommendation system UI we designed below. For each movie displayed, you can set if you like it or not. It collects vast amounts of training data for the algorithm.<\/span><\/p>\n

    \"movie<\/p>\n

    Also provide your users the opportunity to give feedback about the AI content.<\/span><\/p>\n

    On every screen where the app has made a recommendation or prediction, give the users the chance to give feedback easily and right away. It usually means one-tap feedback options displayed next to the AI content.<\/span><\/p>\n

    In Zendesk, a button next to the prediction report bad ones.<\/span><\/p>\n

    \"zendesk<\/p>\n

    In Google\u2019s feed, you could see questions below each card to provide feedback about the card\u2019s usefulness from time to time. You can see they also found a great way to communicate how the algorithm works. They displayed the phrase the user has shown interest in to explain why they recommend a certain article.<\/span><\/p>\n

    \"Google<\/p>\n

    Summary: The seven principles of AI UX<\/span><\/h2>\n

    To sum it up, the seven things to do while designing AI UX:<\/span><\/p>\n