<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Efrat Weidberg on Medium]]></title>
        <description><![CDATA[Stories by Efrat Weidberg on Medium]]></description>
        <link>https://medium.com/@eweidberg?source=rss-f0944d5ce82d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dhfnJICPt4V6PtegYqz0kg.jpeg</url>
            <title>Stories by Efrat Weidberg on Medium</title>
            <link>https://medium.com/@eweidberg?source=rss-f0944d5ce82d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 06:30:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@eweidberg/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Lessons from designing digital health for patients, with patients]]></title>
            <link>https://uxdesign.cc/insights-from-designing-digital-health-for-patients-with-patients-31d975f4b326?source=rss-f0944d5ce82d------2</link>
            <guid isPermaLink="false">https://medium.com/p/31d975f4b326</guid>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[healthcare]]></category>
            <dc:creator><![CDATA[Efrat Weidberg]]></dc:creator>
            <pubDate>Thu, 02 Jan 2020 01:26:46 GMT</pubDate>
            <atom:updated>2023-05-04T15:01:22.855Z</atom:updated>
            <content:encoded><![CDATA[<h4>What designing a disease management app for patients living with chronic conditions taught me about the friction between people and technology.</h4><figure><img alt="Two women in a one-on-one interview" src="https://cdn-images-1.medium.com/max/1024/0*_GjY5KkbNKPaQ-3W" /></figure><p><em>Disclaimer: these learnings are based on qualitative observations and secondary research. I have omitted and obfuscated confidential information, and the learnings are my own and do not necessarily reflect the views of a client or a partner.</em></p><p>Designing products and services for chronic disease management is challenging, for two main reasons: First, the healthcare industry is a <strong>highly regulated, complex ecosystem</strong>, with many moving parts that rarely communicate effectively. Designers in healthcare must not only understand patient’s needs and frustrations but also consider the interests and motivations of different players in the ecosystem, for example, physicians, insurance companies and governments. This <a href="https://uxpamagazine.org/expand-your-view/">article</a> by Chris Kiess is a deep dive into the complexity of designing within the healthcare ecosystem. Second, <strong>motivating a new routine</strong> is not an easy task. Designers should learn about digital behavioral design and psychological models, <a href="https://uxdesign.cc/how-do-you-design-for-behaviour-change-790b9abefa08">The 6 stages of behavioral change</a>, for example.</p><p>According to the CDC, chronic conditions such as diabetes, hypotension or mental illness cause <a href="https://www.cdc.gov/chronicdisease/about/costs/index.htm">significant health and economic costs</a>. Ensuring that patients <strong>proactively manage their illnesses </strong>is key to reducing these costs and improving people’s lives. Disease management apps have shown the potential to engage more people in managing their health, but they have yet to live on to their <a href="https://hbr.org/2018/04/why-apps-for-managing-chronic-disease-havent-been-widely-used-and-how-to-fix-it">full potential.</a></p><p>Last year, I designed a disease management app for people living with chronic conditions. Through immersive patient interviews, secondary research and co-creation sessions, I learned about people’s emotional and functional barriers that may restrain them from proactively managing their health, and their relationships with technology. Here are my top 5 learnings.</p><h3><strong>#1 The patient-provider dynamic is changing</strong></h3><p>The<a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5682364/"> old paradigm</a> of the paternalistic model of medicine is transforming into an equal partnership between patients and doctors, where patients are empowered to take control of their health. The role of technology, in this case, is to <strong>facilitate a conversation</strong> between patients and their doctor, discussing a medication plan, for example. For this to work, patients must comply with a treatment plan and commit to self-management.</p><blockquote>To establish trust, technology should augment rather than replace patient-provider relationships.</blockquote><p>A core component of the doctor-patient relationship is the patient’s faith in the advice and treatment recommended by the doctor. In a recent<a href="http://hrms.urban.org/briefs/do-patients-trust-their-providers.html"> survey</a>, adults with chronic conditions were more likely to put high trust in their doctor, compared to those who consider themselves healthy.</p><p>Trust is individual and context-dependent. However, for most patients who participated in our interviews, there seemed to be a <strong>direct connection between trust and compliance</strong>, meaning that patients who trust their doctors will be more likely to use an app, as long as it has been ‘prescribed’ to them.</p><p>While data privacy was a general concern for many, <strong>patients were willing and expecting to share their data with their healthcare providers </strong>in exchange for a more personal treatment plan and improved health.</p><blockquote>In any app that collects medical data, it’s important to design a simple, easy-to-discover feature for patients to share data with their doctor.</blockquote><p>Apple’s Health allows users to download and share their entire health data. <a href="https://investor.fitbit.com/press/press-releases/press-release-details/2018/Fitbit-and-Google-Announce-Collaboration-to-Accelerate-Innovation-in-Digital-Health-and-Wearables/default.aspx">Fitbit</a> recently announced a partnership with Google to improve its ability to share data with medical professionals, although it is currently only available from the web app. In many data collecting apps, the data sharing feature is “buried” under Settings (Flo app, for example for women’s health) or Profile (Apple health). eMoods, a mood tracking app to manage bipolar symptoms, is a better example. It allows data sharing directly from its Graphs tab, a more intuitive, in-context placement.</p><figure><img alt="Screenshots of the Share Data feature on Apple health, Flo and eMoods" src="https://cdn-images-1.medium.com/max/1024/1*AvSs_-RH-3XvfIB4zdIZ1Q.jpeg" /><figcaption>On Apple’s health (left), the Export Data feature is under “profile”. On Flo, (middle), sharing data is under Settings. On eMoods (right), user can share their data directly from the Graph tab.</figcaption></figure><h3><strong>#2 Healthcare is personal</strong></h3><p>Every patient journey is unique to them and patients’ needs may vary based on their unique conditions, including permanent or temporary disability, lifestyle, and personality. Looking into a patient&#39;s entire journey may reveal the reasons why they fail to follow up on a treatment plan. For example, a missed medical appointments, for many patients, is the result of challenges in coordinating the logistics of special transportation needed to accommodate their chronic condition, as described in this HBR <a href="https://hbr.org/2017/08/health-care-providers-can-use-design-thinking-to-improve-patient-experiences">article</a>.</p><p>A good principle to keep in mind is the importance of design for extreme users. <a href="http://www.inclusivedesigntoolkit.com/whatis/whatis.html">Inclusive Design</a> considers from the very beginning how something might be used by everyone. Consider those who are <strong>least likely to engage </strong>because of their age, low-digital literacy, a permanent or temporary disability, or any other contextual or environmental cause.</p><p>To make treatment plans more personal, doctors collect and analyze patients&#39; medical data. A truly personal view of patients will not only include “medical” data, but also information about sleep, exercise, and nutrition. For example, <a href="https://apps.apple.com/us/app/one-drop-diabetes-management/id972238816">OneDrop</a>, a diabetes management app, collects nutrition and exercise data in addition to glucose level and medication.</p><p>An even more personalized approach also collects information about lifestyle indicators such as travel, life transitions (e.g divorce), and emotional well-being (e.g stress level). Stress level tracking is important given that many chronic conditions, including depression, heart conditions, and diabetes, are worsened by stress. <a href="https://apps.apple.com/us/app/breeze-mood-tracker-diary/id1450365119">Breeze</a>, a mood tracker, collects data about pretty much any lifestyle activity related to the user’s self-reported mood. <a href="https://flo.health/">Flo</a>, a women’s health tracker, tracks mood as well as lifestyle data such as travel and alcohol consumption.</p><figure><img alt="Screenshots showing data-collection UI from OneDrop  app, Breeze mood tracker app and Flo, a women&#39;s’ health tracking app" src="https://cdn-images-1.medium.com/max/1024/1*WQ_s3dlJqHEk7K_49SsD6Q.jpeg" /><figcaption>OneDrop (left) tracks nutrition and exercise data in addition to glucose level and medication. Breeze (middle), a mood tracker, collects data about pretty much any lifestyle activity, and Flo (right) tracks mood and lifestyle data in addition to physical symptoms.</figcaption></figure><h3><strong>#3. Patients don’t believe in “digital magic”</strong></h3><p>Some of the reasons for poor adoption of wearables are related to poor usability and perceived accuracy, as found in one<a href="https://www.aarp.org/content/dam/aarp/home-and-family/personal-technology/2015-07/innovation-50-project-catalyst-tracker-study-AARP.pdf"> AARP</a> study from 2015. Since then, wearables’ functionality and usability have improved significantly, although perceive accuracy is still a barrier for adoption.</p><p>Patients interviewed had two main concerns when it comes to accuracy: the first is sensor accuracy, especially in cases where data is being collected passively. The other is the accuracy of the analysis and insight. This was especially true when we presented concepts of predictive analytics and diagnostic features.</p><p>Every sensor used in tracking devices comes with an accuracy level, but accuracy level information does not have a primary location on UI. On the Garmin app, for example, there is a written section about sensor accuracy found down the More Menu. Similarly, the Apple Watch does not communicate the sensor accuracy, but it does provide information on how to make the reading more accurate.</p><p>As with in-person interactions, digital health interactions needs to be designed with transparency, using clear communications to promote trust. Like humans, machines aren’t perfect decision-makers, and medical predictions are based on information collected by both sensors and humans. Showing the data behind the prediction is one way to increase trust.</p><p>One Drop, a diabetes management app recently expanded its AI-powered <a href="https://c212.net/c/link/?t=0&amp;l=en&amp;o=2645912-1&amp;h=524854863&amp;u=https%3A%2F%2Fc212.net%2Fc%2Flink%2F%3Ft%3D0%26l%3Den%26o%3D2603088-1%26h%3D971044368%26u%3Dhttps%253A%252F%252Fonedrop.today%252Fblogs%252Fpress-releases%252Fone-drop-announces-blood-glucose-prediction-automated-decision-support%26a%3DPredictive%2BInsights&amp;a=Predictive+Insights">Predictive Insights</a> to include 8-hour blood glucose forecasts. The app provides an option to see more information about the prediction, which is directly linked to information previously provided by the user.</p><p>Another way is to be transparent about the <strong>confidence level of a prediction</strong>. In AI, a<a href="https://design.google/library/six-ai-terms/"> confidence level</a> is a numerical expression of certainty in percentages. Showing users, the confidence level of insight or a prediction will increase trust. This UI pattern has been used in the past by kayak on their price prediction, however today they only include a description of the data the prediction is based on.</p><figure><img alt="A screenshot from the kayak price prediction tool, and two screenshots of the OneDrop app showing glucose level prediction." src="https://cdn-images-1.medium.com/max/1024/1*WXErIKmQSgpD7yGTcvcZdA.jpeg" /><figcaption>Kayak (left) used to display the confidence level of the prediction. One Drop app (right) is offering more details about its health predictions.</figcaption></figure><h3>#4 Tone of voice can make a big different</h3><p>While the overall approach must be practical, empathetic design can go a long way when it comes to healthcare UX. By keeping a <strong>positive tone</strong> when educating and communicating, patients could subconsciously feel more hopeful about the outcome of their treatment.</p><p>Another way to enhance positivity in the patient experience is positive reinforcement. Adding prompts similar to those found in fitness apps (e.g “you’re doing great, keep going!”) can improve adherence, as long as they are designed thoughtfully and in the right context: You may want to avoid sounding too enthusiastic when the data means conditions are worsening, for example.</p><p>From those interviewed, some patients appreciated a more casual language at times, but most of them still wanted the overall design and tone to feel “medical” or “clinical”.</p><p><a href="https://emoodtracker.com/">eMoods</a> and <a href="https://apps.apple.com/us/app/breeze-mood-tracker-diary/id1450365119">Breeze</a> are mood trackers that take the opposite approach when it comes to tone. eMoods’ design language and tone are clear, minimal and utilitarian. On the other hand, you’ll find rainbows and clouds on Breeze’s interface, and a friendly, casual tone. After you complete your first entry, the app encourages you to keep going with a smiling cloud.</p><p>Some patients might find an app like Breeze too casual to be considered medical, while some may find the eMoods’ interface dry and discouraging.</p><p><a href="https://mymoodpath.com/en/">Moodpath</a>, another mood tracking app, is a better example. It prompts users with subtle notifications, in a neutral, respectful and optimistic tone.</p><figure><img alt="Screenshots of three mood trackers as an example of different approaches to tone in design." src="https://cdn-images-1.medium.com/max/1024/1*tKkpdrAGwTzIiqwkX83TOg.jpeg" /><figcaption>eMoods (left) does not provide any feedback when data is entered. Breeze (center) prompts users with a smiling cloud. Moodpath (left) shows progress and provides a subtle positive reinforcement.</figcaption></figure><h3><strong>#5 Patient satisfaction will be measured by time saved — not spent</strong></h3><p>Measuring success for digital health varies. With patient adherence being one of the <a href="https://www.raconteur.net/healthcare/medication-adherence">biggest challenges</a> in healthcare, a good design will be measured by patients’ engagement and participation. Ideally, it will lead to behavioral change that leads to improved health, cost, and efficiency.</p><p>Chronic disease management is time-consuming, especially in those cases when providers prescribe multipart protocols. While patients’ needs broadly spread across many spectrums, we found that when it comes to compliance, patients have a common goal: <strong>lessen the time they spend on “dealing” with their illness.</strong></p><p>Disease management is not something patients choose or want. It’s about what they must do daily. That is why designers should design with effectiveness and efficiency in mind, keeping a clean feel and clear communications.</p><blockquote>There is no ‘delight’ or ‘surprise’ in disease management, and patients are looking for tools that will end up saving them time, not add on to their plate.</blockquote><p>As a table stake, digital tools should work without friction, and be supported with attentive service. A nice to have will be an added personal touch or a sleek and modern design, for example. Beware of anything that feels too ‘gimmicky’ or any language that sounds more like “marketing talk”. Patients perceived those as a waste of time.</p><p>In addition to barriers of adoption resulted from a permanent or temporary disability, people are busy, distracted or simply uninterested. No matter what the barrier is, tracking tools must be designed to collect data with a minimum amount of effort from the user, within medical and technological constraints.</p><p><strong>Passive tracking</strong> might require some setup or specific tools, but once it is working the actual tracking should be largely automatic and require almost no additional action from the tracker. All you do is turn it on and you are collecting data. Wearable trackers offer this form of passive data collection. Garmin’s sleep tracking only requires users to set a goal, before passively tracking and analyzing sleep.</p><p>A good example of passive adherence tracking is the<a href="https://www.propellerhealth.com/"> propeller</a> inhaler, that collects data during usage. And then there is tracking from within the body, or “digestible”, for example, the FDA approved<a href="https://www.abilifymycite.com/"> Abilify MyCite</a>. These pills include sensors that record when the medication is taken.</p><p>But passive tracking is not always possible. Many data points require manual entry, and designers are challenged to make a data entry and simple as possible. We can reduce effort by sending reminders and notifications to enter data, with the simplest question format possible. Moodpath, for example, is using simple yes or no questions to collect self-reported data.</p><figure><img alt="Screenshots of the Garmin sleep tracking feature, Propeller health adherence tracking and moodpath yes or no questions" src="https://cdn-images-1.medium.com/max/1024/1*gctl7N72gXqnlApf0M0GPg.jpeg" /><figcaption>Garmin sleep tracking (left) only requires pairing with the watch and single time goal setting. The propeller app (center) counts usage, once connected to the inhaler. Moodpath (right) collects self-reported data using a simple yes/no question format.</figcaption></figure><p>Notifications are also used for critical times, like warnings (for example, heart rate threshold alerts) and timely reminders (”it’s time to take your pill”). When properly executed, push notifications can provide users with the most relevant information at the right time and encourage them to take action.</p><blockquote>For predictive notifications, it is important to include an advice on how to act on the insight, so users can feel more in control.</blockquote><p>For example, One Drop’s high glucose warnings include advising on how to reduce the risk of a rising glucose level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/949/0*vPAmN9Zr3tUzV-UH" /><figcaption>One Drop is letting users know what they should or shouldn&#39;t do</figcaption></figure><p>Push notifications can be disruptive if not managed properly and thoughtfully. Notifications should be flexible and easy to set and manage by the patient with or without their provider. The content and frequency must be attainable, realistic and time-sensitive. Patients might feel frustrated, annoyed or guilty if they cannot act on an actionable health insight at a given time.</p><p>Human-Centered Design is already playing a key role in the future of healthcare. Solutions must be developed out of a deep understanding of patients’ needs, pain points, motivations, and beliefs, and not out of the recent buzz of a technological breakthrough. An innovative, novel solution by itself may attract some enthusiastic early adopters at first but is not what will drive much-needed sustainable adoption or behavior changes.</p><p>Patients don’t think technology is here to replace their doctors but to assist with mutual decision making. They will most likely try a tool that is approved by their doctor, as long as they trust their doctor’s advice.<br>Patients are more than happy to share their medical data with their doctors, in exchange for a more personalized treatment plan. But many barriers prevent people from following up on their plan. These barriers include physical barriers, such as debilitating pain of disability, emotional barriers, such as low motivation, and pessimism, and mental barriers such as lack of trust or poor time management.</p><p>There are many ways app design can address these barriers. First, making it easy for doctors to know more about their patients, through holistic data collection that is easy to share. Second, adding more transparency patterns such as confidence level will increase trust in technologies and processes that are relatively new. Third, using an appropriate tone will make patients feel like they are being acknowledged. Finally, we must focus on optimizing interactions to be quick, frictionless, and non-disruptive, as patients wish to spend less time on their illness and more time doing what they love.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31d975f4b326" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/insights-from-designing-digital-health-for-patients-with-patients-31d975f4b326">Lessons from designing digital health for patients, with patients</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Navigating the hype — is blockchain a designer’s dream or nightmare?]]></title>
            <link>https://medium.com/@eweidberg/navigating-the-hype-is-blockchain-a-designers-dream-or-nightmare-3b4c216ab7b8?source=rss-f0944d5ce82d------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b4c216ab7b8</guid>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Efrat Weidberg]]></dc:creator>
            <pubDate>Wed, 15 Aug 2018 21:23:39 GMT</pubDate>
            <atom:updated>2020-01-02T01:04:42.467Z</atom:updated>
            <content:encoded><![CDATA[<h3>Navigating the hype — is blockchain a designer’s dream or nightmare?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rnMKY3idSmybH9I7.png" /></figure><p>There is <a href="https://www.theverge.com/2018/3/7/17091766/blockchain-bitcoin-ethereum-cryptocurrency-meaning">no universal definition of a blockchain</a>, yet It is often being described as a fundamental set of technologies. It may mean different things to different people, but it is helpful to <a href="https://hbr.org/2017/01/the-truth-about-blockchain">think about </a>internet protocols such as BitTorrent (a peer to peer network) or TCP/IP (an open, shared public network) as an analogy. The development and maintenance of blockchain is open, distributed and shared, just like TCP/IP’s. Understanding different types of computer networks, centralized, decentralized and distributed, for example, and the concept of trustless networks, is also a good start. Spending time with computer science literature may not be that appealing to designers, but in my mind they are a necessary foundation for those looking to make an impact in this space.</p><p>Nowadays, discussion is usually around one of the following topics: Cryptocurrencies, (blockchain 1.0 as referred to in “ <a href="https://www.amazon.com/Blockchain-Blueprint-Economy-Melanie-Swan/dp/1491920491">Blockchain: Blueprint for a New Economy</a>”, Melanie Swan), such as Bitcoin, and Ethereum. The second includes the development of <a href="https://blockgeeks.com/guides/smart-contracts/">smart contracts</a> (blockchain 2.0). <a href="https://hbr.org/2017/01/the-truth-about-blockchain">Early experiments</a> with such self-executing contracts have been seen first in the areas of venture funding, banking, and digital rights management. The third (blockchain 3.0), relates to the broader application of blockchain as a technology that can be used beyond finance and promises to transform many industries, especially those that rely on digital record keeping.</p><p>Another emerging area is often being referred to as web 3.0, or the <a href="https://www.wired.com/story/the-decentralized-internet-is-here-with-some-glitches/">Decentralized Web</a> (a familiar concept to fans of HBOs <em>Silicon Valley</em> series), where you can find decentralized versions of popular apps. Download a browser and experiment with it <a href="https://blockstack.org/">here</a>, as an introduction to the concept of the decentralized web, the adaptation of a <a href="https://en.wikipedia.org/wiki/Token_economy">token economy</a>, and owning your data.</p><p>In the book “ <a href="https://www.amazon.com/Decentralized-Applications-Harnessing-Blockchain-Technology/dp/1491924543">Decentralized Applications: Harnessing Bitcoin’s Blockchain Technology</a>”, Siraj Raval describes centralized systems as the most widespread model for software applications, including Facebook, Amazon and Google. Interestingly, apps like Uber and Airbnb, decentralized the “real life” part of the business. This required everyone to re-think their ability to trust one another, and for designers to learn what it means to <a href="https://www.ted.com/talks/joe_gebbia_how_airbnb_designs_for_trust">design for trust</a>. Those principles still apply when designing a blockchain-based decentralized application solution, but critically, the users will also have to trust the technology itself.</p><p>There is an increasing number of <a href="https://www.fastcodesign.com/90136657/why-blockchain-needs-designers">articles</a> calling designers to get themselves familiar with the technology even if they don’t really understand it. An earlier wave of editorials advocated for designing consistent interfaces and UX design principles. More recent articles focus on processes, system thinking and the <a href="https://media.consensys.net/designing-for-blockchain-whats-different-and-what-s-at-stake-b867eeade1c9">importance of designing for trust</a>, implying that In the blockchain space, designers will have to understand social, political and financial systems, in order to provide value beyond the interface.</p><p>I recently spoke with <a href="http://andreamoralescoto.com/">Andrea Morales</a>, a senior design strategist at ConsenSys: a blockchain venture production studio. In her work, she leverages design thinking and game design methodologies to create new strategic opportunities for businesses and social movements. <strong>Here are some of the learnings that have emerged from her experience.</strong></p><h3>#1 Design is playing catch-up.</h3><p>Morales:<em> “Developers in the space are moving fast, and designers often find themselves skinning interfaces and testing betas, without being a part of earlier stages of projects.”</em></p><p>Although a consistent, systematic UI, will certainly make an on-screen interaction better, it wouldn’t be a thoughtful solution without considering the entire system, and most importantly, it won’t help figuring out if a stated problem is even worth solving. Therefore, design can no longer be added at the end of a project. In the case of decentralization, designers will have to be active human-centric advocates throughout the solution lifecycle. That means that developers may have to slow down and acknowledge the role that design needs to play.</p><h3>#2 The designer is an advocate for the whole system.</h3><p>Morales:<em> “In the process of designing cryptosystems, and incentive mechanisms, the designer becomes the systems thinker. This is an ongoing design process, that involves thinking about how different actors are in constant exchange with each other. Designers are constantly mapping how the system reacts to different scenarios.”</em></p><p><a href="https://blog.joincivil.com/how-does-the-civil-media-company-make-money-and-why-is-it-good-for-journalism-34b4a6616256">Civil media’s</a> operating model is a self-governing system that is both ideologically and economically incentivized to promote quality journalism across a massive ecosystem — one that includes independent newsrooms and citizens across the world. The team has been brainstorming ideas for products, apps and services that will support the growth of the entire ecosystem in the name of their mission.</p><p>The adoption of blockchain built solutions, similar to Civil’s or on a smaller scale, is not as simple as learning how to use a new platform or application. There are many challenges that involve <a href="https://hbr.org/2017/01/the-truth-about-blockchain">coordinating the activity</a> of many actors and gaining institutional agreement on standards and processes. Service design methodologies such as journey mapping and service blueprints are helpful when we need to uncover use cases and required mechanisms, whenever a user interacts with a system. These tools are powerful not only in envisioning a future, but also in evaluating the current state to develop a clear problem statement. Once there is one, it is easier to get a group of people to work collaboratively in identifying solutions.</p><h3>#3 Making sure the problem is both a practical and ideological discussion.</h3><p>New technologies sometimes evolve so quickly that designers often find themselves putting a technology before a problem.</p><p>Morales:<em> “Of course there are cases where there are less expensive technologies that can solve a given problem. However, to put things in perspective, when it comes to decentralization, we are not just looking at a technology solution, but at a set of ethical and ideological driven convictions that decentralization is the right way to go.”</em></p><p>Without a problem worth solving through the lens of an ideological and organizational shift, a blockchain network solution is just another expensive data-structure mechanism. It is important for organizations to align internally on this challenge statement, before even considering blockchain. For those critics who perceive this tech to be useless, a common argument I heard is that many of the problems blockchain will supposedly solve, can be achieved by adopting a cheaper, more stable technology. But that is a rather simplified argument, missing the crucial opposing perspectives that view decentralization as a pathway to a larger purpose or outcome.</p><h3>#4 Collaboration will enabledecentralized business models.</h3><p>Let’s look at the example of healthcare. As a patient, we’ve all experienced the struggles of moving between providers, insurance carriers, doctors or health systems, as our data becomes scattered across these siloed organizations. This causes the loss of an easy access to past records, which can help improve care and even prove life-saving in emergency situations.</p><p>One of the more ideologically-driven solutions being discussed is having patients own their data, and the implications for the overall healthcare system. Hypothetically, data ownership in this solution would be technology agnostic. In practice, this requires a whole host of organizations to reach consensus with a lot of other organizations, before governance and implementation could even be considered. That could conceivably take years, especially in a fragmented system like the American healthcare industry.</p><p>On the other hand, there are already a few industry alliances out there, for example <a href="https://www.dlt.mobi/">MOBI</a>, the Mobility Open Blockchain Initiative, and the <a href="https://entethalliance.org/">Enterprise Ethereum Alliance</a>; indicating that select industries are recognizing these opportunities, and taking steps towards working together for a greater good.</p><h3>#5 Changing people’s perspective on the need for decentralization is part of the designer’s role.</h3><p>History also teaches us that it is extremely difficult to convince people that there are different ways to organize as a society. We are primarily creatures of habit.</p><p>Morales:<em> “We need to show people that there is a decentralized alternative to what they have gotten used to, and why that alternative is better. The hardest part is to convince people and companies to give up a little bit of power, for the gain of the network.”</em></p><p>Aside from our resistance to change, there are many other barriers to adoption. A decentralized software solution is fundamentally very different from what people have become accustomed to over the years. Digital products and services are continually becoming more usable, intuitive and delightful, but one important principle that is often overlooked, is the work of designers in making error recovery seamless. A good example for error recovery design is Google’s “undo send” Gmail feature, which gives users a second chance to change their mind after hitting the send button.</p><p>Blockchain, by its nature, offers the absolute opposite. With no central authority over the data, an error cannot simply be reversed like a chargeback on a credit card, or as <a href="https://www.wired.com/story/i-forgot-my-pin-an-epic-tale-of-losing-dollar30000-in-bitcoin/">Mark Frauenfelder</a> puts it (in the context of crypto trading), <em>“This decentralized nature of the bitcoin network is not without consequences — the main one being that if you screw up, it’s your damn problem”.</em> The ability to recover from errors is one of the most basic principles of a good user experience and the fact that the technology is so unforgiving when it comes to human error, creates a huge mental barrier for adoption.</p><h3>#6 The designer will shape economic incentive mechanisms.</h3><p>Morales:<em> “Unlike shared economy models, in networks like Ethereum, participants have to pay a small ‘fee’ (in the form ). This is how everyone is giving back to the network’s operational cost. Designers will play a role in communicating to people how the value of the network is being distributed among its participants. That is where a well-designed economic incentives system can work. This is similar to the idea of a co-op: we take all this value and distribute it amongst the network for the benefit of everyone.”</em></p><p>When it comes to our personal data, and the digital assets we create, advocates of the “decentralized movement” believe that decentralized apps mean a change in how value is captured, shared and exchanged so that it rewards the people creating that value; not institutions and their middlemen. In order to do that, users need to trust the system. But the system itself does not guarantee the accuracy of the data in it, or that the people entering the data trustworthy. In the end, it is really a matter or who, or what, we trust. The recent Facebook-Cambridge Analytics scandal has once again reminded people how much personal information we give away when interacting free online services. But this huge breach has not caused a significant change in people’s online behavior, according to <a href="http://www.businessinsider.com/americans-losing-trust-facebook-still-using-social-media-2018-3">Business Insider</a>. While all the Cambridge Analytics headlines have surely altered some people’s value calculations when it comes to using Facebook, there’s been no evidence of a sea change in Americans’ attitudes.</p><h3>#7 Designers must create different pathways towards mastery for all players.</h3><p>Morales:<em> “Designers involved in blockchain will be making decisions regarding how much of the system is shown: do we need to give users access to all the features from the beginning or set up constraints? Should we provide suggestions? As a game designer this mirrors how we design tutorials, while also creating varying levels of difficulty.”</em></p><p>As a common principle, a good design will make the technology disappear. However, when trust is not entirely established, some users may want to “see” the technology more than others. Reflecting on the healthcare example, let’s say a new system has been implemented and patients now hold the “key” to their own data. Select users may not even care about the underlying technology, as long as data entry is quick, efficient and enables control over their personal information. On the other hand, some users would require the confidence that comes from seeing the mechanism that makes their data secure.</p><h3>#8 Designers must keep unintended consequences in mind.</h3><p>Tim Berners-Lee, in the context of the World Wide Web, stated that when technology evolves quickly, society can find itself left behind, trying to catch up on ethical, legal and social and implications. This is already happening with blockchain solutions.</p><p>Among concerns around the security of the network, abuse of power, and illegal operations, there are also rising discussions about the ethics of decentralization as an ideology.</p><p>A technology that enables networks to self-govern and make their own decisions, in a way that everyone is a contributor and no middlemen profit, sounds like a utopian dream. But no matter what you believe the future of blockchain will be, as recent history has shown, powerful innovations always come saddled with unintended consequences.<br> So what can go wrong?</p><p>Morales:<em> “The idea behind decentralization is that communities will be able to govern themselves. Unfortunately, that means that there could be certain communities that may not want to empower all of their members, and some groups may be toxic towards other communities that are less powerful. Some people, like Taeyoon Choi, of the School for Poetic Computation, have started advocating for the word “distribution” vs. “decentralization”, since decentralization does not mean power is justly distributed. I still don’t know how we will deal with the problem of toxic decentralization and power distribution, but it sounds like keeping it in mind is a good start.”</em></p><p>Digital designers in the blockchain space been making usable interfaces (mostly for digital wallets) for a few years now. However, when it comes to social and business problems, designers will have the freedom to think big. Real big. This is a space where the technology and the ideology are interconnected. That means big problems and revolutionized solutions. For some, that ideology sparks nostalgia to the early days of the internet, where everything was open and decentralized. For others, this is an opportunity to create alternative solutions to existing business models.</p><p>Design will continue to represent and advocate for the “human”, in human computer interactions. In practice, their work will include methodologies from organizational design, business design and even game design. People are no longer a “touchpoint” in a network, but a living, moving contributor. And while good UX design is all about putting the user first, when it comes to blockchain, designers must place the entire system first. As exciting and diverse the role of designers in the space may be, it is important to remember that this is an immature technology in a complicated space, full of unknowns and potential risks. Investors and developers are moving fast, and there are many opportunities to explore. A passion for decentralization is a must, and a basic knowledge of the history of the internet is helpful, as well as a solid understanding of social and economic systems. This is a great opportunity to make a change, for those who are willing to embrace ambiguity and uncertainty.</p><p>While It is hard to navigate blockchain’s technological and ethical complexity, and the overall hype that comes with it, this is quite an exciting space for designers, even if it is not yet entirely understood or accepted. The main reason designers find the space exciting is that the technology of cryptocurrency has an underlying ideology, and it is so fundamental that its application will require people and organizations to rethink social systems and business models, and form a complete new set of governance.</p><p>For Andrea Morales, it’s all about making a social &amp; behavioral change for the greater good of society: <em>“As a game designer, I have a high interest in how Ethereum can innovate how we incentivize human behavior in ways that are understandable, and small enough in scale, that people will actually recognize how blockchain affects them. Our society itself could change if we design this properly.”</em></p><p>If you are a designer working on a blockchain product or part of a decentralized startup, we would love to hear your thoughts!</p><p><a href="https://smartdesignworldwide.com/people/efrat-weidberg/"><strong><em>Efrat Weidberg</em></strong></a><em> is an interaction design lead at </em><a href="https://smartdesignworldwide.com/ideas/alexa-product-service-voice-app/"><strong><em>Smart Design</em></strong></a><em>. Check out more from Efrat, and her perspective on designing for voice at </em><a href="https://smartdesignworldwide.com/ideas/alexa-product-service-voice-app/"><strong><em>smartdesignworldwide.com</em></strong></a></p><p><em>Originally published at </em><a href="https://medium.com/@SmartDesign/navigating-the-hype-is-blockchain-a-designers-dream-or-nightmare-8c82f12a6cb4"><em>https://medium.com</em></a><em> on August 15, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b4c216ab7b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Lessons We Learned Working In Design’s Wild West]]></title>
            <link>https://medium.com/@eweidberg/5-lessons-we-learned-working-in-designs-wild-west-8543724f6a9e?source=rss-f0944d5ce82d------2</link>
            <guid isPermaLink="false">https://medium.com/p/8543724f6a9e</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Efrat Weidberg]]></dc:creator>
            <pubDate>Mon, 05 Feb 2018 07:00:41 GMT</pubDate>
            <atom:updated>2020-01-02T01:01:40.562Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DL6FhM5eLbOpE6Nh.jpg" /></figure><p>Conversations: They reflect one of our most basic human instincts. As infants, learning to talk is one of our first acquired skills, and verbally communicating with others quickly becomes a fundamental part of daily life. But only recently have we started to converse with technology, asking it questions, making requests, and so much more.</p><p>Since communicating with one another is an inherent skill, you might think designers would have an easy time crafting conversational UI. But the truth is, there are dozens of intricacies that come with designing for voice, particularly since it’s still early days.</p><p>Our interdisciplinary team has gotten its hands dirty exploring the possibilities and pushing the boundaries of designing for voice UI over the past year, including designing and developing a proof-of-concept voice app for <a href="https://smartdesignworldwide.com/projects/gatorade-hydration-system/">Gatorade Gx</a>, and creating a personalized voice assistant for a woman living with multiple sclerosis for the upcoming <a href="http://www.bbc.co.uk/programmes/b09g5hwf">BBC Two series <em>The Big Life Fix</em></a>. The learnings that came out of these use cases were numerous, but here are the top takeaways:</p><h3>Voice should only be one piece of the pie</h3><p>When you add a voice UI component to your offering, you can shorten and simplify interactions, deliver faster results, provide a personalized service, and make your product more accessible. From a brand perspective, voice UI is a great way to convey brand personality and deepen relationships with customers.</p><p>One important lesson, however, is that a voice app is not going to replace other touch points of interaction with a service. A voice-based version of your app most likely won’t serve everyone. Take the Grubhub Skill on Alexa, for example: It only works if a user already has an active account and a previous order history. When using the voice app, customers can’t start an order from scratch; they must repeat an order. So the Skill is only relevant for frequent users who are trying to save time-and that’s okay. Meeting more targeted, personal user needs is exactly why companies invest in creating different digital touch points, and it’s important to remember that your voice app should only be one slice of the pie you’re offering.</p><h3>There’s no need to reinvent the wheel-it already exists</h3><p>Designing for voice UI doesn’t mean creating a brand-new design process or guiding principles. Classic frameworks such as Nielsen’s 10 usability heuristics for interface design <a href="https://www.nngroup.com/articles/voice-interaction-ux/">still apply</a> to voice UI. For example, visibility of system status-the principle of keeping users informed about what a system is doing and why-is an important VUI principle. The only difference is that the feedback may not be at all visual.</p><p>Also, similar to other emerging tech such as VR, voice interface design is nothing new. VUI systems were popular in the early 2000s, and there are plenty of learnings still relevant today, like how key it is to use conversational markers (“got it,” “almost there”) judiciously so users don’t get annoyed. As long as we keep pace with recent technological advancements, designers can continue to evolve their approach and be mindful of how these elements might change a user’s expectations.</p><p>There are dozens of VUI design guidelines published online including <a href="https://developer.amazon.com/designing-for-voice/">Amazon’s guidelines</a>, <a href="https://developer.amazon.com/docs/custom-skills/voice-design-best-practices-legacy.html">best practices</a>, and books including <a href="https://www.safaribooksonline.com/library/view/designing-voice-user/9781491955406/?utm_source=oreilly&amp;utm_medium=newsite&amp;utm_campaign=vui-design-chapter-2-excerpt-top-note-cta">O’Reilly’s Designing Voice User Interfaces</a>. Using and adopting these instead of trying to create your own will save your team time, effort, and resources.</p><h3>Keep the brand voice consistent</h3><p>When you’ve spent so much time on the brand voice for your company or product, you of course want to let it shine as much as possible in your new experience. There are couple of ways to consistently apply brand values into the VUI experience: the way your Skills use filler words such as “um” and “got it,” the approach the app takes in handling errors, and the manner in which it welcomes the user. Pay attention to even the smallest nuances; they all reflect your voice.</p><p>A voice app can also be personalized by using a prerecorded voice that may already be associated with your offering (Alex Trebek on the Jeopardy Skill, for example). This ensures it’s not just the stock Alexa tone speaking for you, but a language and tone that feels natural to your brand. Not everyone can afford to invest crazy efforts in applying an actual human actor’s voice to their offering, as the <a href="https://smartdesignworldwide.com/ideas/smart-salon-power-personalization-health/">AI-enabled personal trainer Vi</a> did when it crafted its product’s personality. But finding a way to embed your brand through voice is key if you want people to start emotionally connecting to the experience.</p><p>Another way is to express the brand personality onto what the user has to say. Looking back at our Grubhub example: Its voice app is prompting users to tell Grubhub “I’m hungry.” This is a subtle way the company has injected some of its playful personality into the voice product, unifying the experiences of its mobile and voice apps.</p><h3>Minimize errors, and keep interactions brief</h3><p>As a general guideline, a voice interaction should be brief, similar to the way we try to limit the number of clicks required to complete a task on a visual interface while providing the right amount of visual feedback. The same ideals apply to voice UI. However, too much of that feedback and confirmation can make the system sound dumb, while not enough can lead to errors. There are two avenues for providing feedback. We can choose to repeat the request, then go ahead and process it, or require a confirmation from the user first.</p><p>For our Gatorade Gx voice app experiment, we found that one way to avoid redundancy was to create an array of confirmation phrases, and randomly select one each time the user makes the request. For example, if a user says “running,” the app may confirm it by saying, “Running sounds like fun,” or “This is a good day for running.”</p><p>According to Amazon’s guidelines, confirmations should be used selectively, except when you’re talking about something with significant consequences (like a large transaction). Simply put, to evaluate the need for a confirmation, ask “what can go wrong?” and “what is the outcome?”The more time an error takes to recover, the more value the user will glean from a confirmation.</p><h3>Provide context, and keep it personal</h3><p>Context means being aware of the circumstances or setting in which the conversation is taking place, as well as things that have happened in the past. With a lack of visual reference, it is important to provide users with the context of their requests to make sure they are aware of the meaning being applied to their dialogue, in addition to making the interaction feel more personable.</p><p>We discovered there are a few simple ways to set up context to a conversation: If the user is logged in to the service already, the system can recall past, already personalized interactions with ease. But even without an account, non-personal variables such as time of day, weather conditions, or even location can help in establishing context.</p><p>At any point during the conversation, it is also important to provide users with information on potential actions they can take. This can be achieved by using “help” and “universals.” With the lack of a visual menu, universals are a good reinforcement of what the app can do. On our Gx voice app, for example, we added welcome and help functions to provide an overview of the options to the user, making it easier for them to navigate through the possibilities available to them.</p><h3>We’re just getting started</h3><p>Voice apps are still in their infancy, and while we as humans may be natural experts at conversing with one another, we must recognize that this is not yet the case when it comes to engaging in spoken dialogue with bots.</p><p>By maintaining an open mind while simultaneously implementing both proven design principles and new, VUI-centric ones, designers can develop cutting-edge guidelines and standards that go beyond today’s digital ecosystem. This approach will help us lay the foundation for the future of screenless experiences, something we’re excited to continue experimenting with.</p><p><em>Efrat Weidberg is an interaction design lead at Smart Design.</em></p><p><em>Originally published at </em><a href="https://www.fastcompany.com/90159254/5-lessons-we-learned-working-in-designs-wild-west"><em>https://www.fastcompany.com</em></a><em> on February 5, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8543724f6a9e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>