<?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 Nikki Clark on Medium]]></title>
        <description><![CDATA[Stories by Nikki Clark on Medium]]></description>
        <link>https://medium.com/@nikkic1ark?source=rss-99c1b5aef37------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*xFNQxeMfe7qYT59X4y46-g.jpeg</url>
            <title>Stories by Nikki Clark on Medium</title>
            <link>https://medium.com/@nikkic1ark?source=rss-99c1b5aef37------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 13:40:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nikkic1ark/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[When Robots Speak “Human”]]></title>
            <link>https://medium.com/hello-thirteen23/when-robots-speak-human-669e2c782569?source=rss-99c1b5aef37------2</link>
            <guid isPermaLink="false">https://medium.com/p/669e2c782569</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[amazon-echo]]></category>
            <category><![CDATA[alexa]]></category>
            <category><![CDATA[voices]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Nikki Clark]]></dc:creator>
            <pubDate>Wed, 15 Feb 2017 16:14:23 GMT</pubDate>
            <atom:updated>2019-08-14T15:59:44.753Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DBtC8yzp6JZhpgOSeVUPlg.jpeg" /></figure><h4>Language considerations for designing Alexa Skills</h4><p>I’ve learned quite a few interesting things while prepping materials for the <a href="http://schedule.sxsw.com/events/PP60965">SXSW Workshop</a> that <a href="https://medium.com/u/dad5ea2384f8">Tom Hudson</a> and I are running this year. After editing the data for 35 Alexa skills, and going through each of the 1600 lines out loud with Alexa, some clear patterns emerged of what type of language works best.</p><p>I was surprised to learn that language which works on the web can be virtually unusable in an audio interface. Some of this copy can be modified with audio-friendly grammar patterns, but some needs to be caught with a careful ear. In many cases Alexa reads input very literally; if you miss a comma or mistype a letter, Alexa will boldly push on through the mangled sentence, phonetically sounding out obvious typos. This means that designers need to be very careful of the language they include in the interface, because even small mistakes are glaringly obvious when read out loud.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/76/1*XEGc9FuxjHsO21XY1mDxFg.jpeg" /></figure><h3>Sentence length</h3><p>The first thing that became clear was that sentences sound really bizarre when the speaker doesn’t need to breathe. Commas usually serve as breath markers when a piece is read aloud, but without them, a person reading will tend to make a place for them anyway. Alexa doesn’t need to do that. To make her reading sound more “human,” break up sentences wherever possible. When writing for a voice interface, it’s better to err on the side of too many commas than too few.</p><blockquote><strong>Original:</strong> “Losses of managed honey bee colonies were 23.1 percent for the 2014–2015 winter but summer losses exceeded winter numbers for the first time, making annual losses for the year 42.1 percent.”</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fw.soundcloud.com%2Fplayer%2F%3Furl%3Dhttp%253A%252F%252Fapi.soundcloud.com%252Ftracks%252F307724460%26show_artwork%3Dtrue%26secret_token%3Ds-yWUrX&amp;url=https%3A%2F%2Fsoundcloud.com%2Fuser-275711973%2Fsentencelength-01%2Fs-yWUrX&amp;image=http%3A%2F%2Fa1.sndcdn.com%2Fimages%2Ffb_placeholder.png%3F1487002698&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=soundcloud" width="800" height="166" frameborder="0" scrolling="no"><a href="https://medium.com/media/881c249c220e8f77ed95247317936a55/href">https://medium.com/media/881c249c220e8f77ed95247317936a55/href</a></iframe><blockquote><strong>Voice UI:</strong> “Losses of managed honey bee colonies were 23.1 percent for the 2014–2015 winter. For the first time, summer losses exceeded winter numbers, making annual losses for the year 42.1 percent.”</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fw.soundcloud.com%2Fplayer%2F%3Furl%3Dhttp%253A%252F%252Fapi.soundcloud.com%252Ftracks%252F307724459%26show_artwork%3Dtrue%26secret_token%3Ds-JMsXj&amp;url=https%3A%2F%2Fsoundcloud.com%2Fuser-275711973%2Fsentencelength-02%2Fs-JMsXj&amp;image=http%3A%2F%2Fa1.sndcdn.com%2Fimages%2Ffb_placeholder.png%3F1487002698&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=soundcloud" width="800" height="166" frameborder="0" scrolling="no"><a href="https://medium.com/media/1d7e8f81ac0eee8fb00286f9a8e2e7e1/href">https://medium.com/media/1d7e8f81ac0eee8fb00286f9a8e2e7e1/href</a></iframe><p>It’s also likely that in a voice interface you’ll have to deal with short-term retention issues. Interface designers already face this frequently, such as designing accommodations to prevent disappearing form field labels when a user clicks into a field. In an audio interface, this mostly appears in long or convoluted sentences that introduce multiple ideas. Unfortunately, it’s also harder to track retention issues in an audio interface, because it’s easier for a user to become distracted or inefficiently multitask. The best defense is to write in short, clear sentences with a single central theme. The second best defense is to test your interface effectiveness with real humans.</p><h3>Numbers</h3><p>It’s even easier to get lost in a long sentence with multiple number sets than in another, similarly long sentence without numbers.</p><p>In a sentence like the following, it may be hard for a listener to remember which numbers are related:</p><blockquote>“Of 160,000 e-mails and instant messenger conversations collected under Section 702 between 2009 and 2012, 90 percent of the communications the government had captured and retained were from online accounts not belonging to foreign surveillance targets.”</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fw.soundcloud.com%2Fplayer%2F%3Furl%3Dhttp%253A%252F%252Fapi.soundcloud.com%252Ftracks%252F307774781%26show_artwork%3Dtrue%26secret_token%3Ds-d1Wel&amp;url=https%3A%2F%2Fsoundcloud.com%2Fuser-275711973%2Fnumbers-01%2Fs-d1Wel&amp;image=http%3A%2F%2Fi1.sndcdn.com%2Fartworks-000207812847-0grw2c-t500x500.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=soundcloud" width="800" height="166" frameborder="0" scrolling="no"><a href="https://medium.com/media/30ff240ee402d6b817543944b53c98b2/href">https://medium.com/media/30ff240ee402d6b817543944b53c98b2/href</a></iframe><p>If you’re comparing two sets of numbers, try to place them closely together in a sentence. If possible, put distance between dates and unrelated numbers. Revised, this copy could read:</p><blockquote>“Between 2009 and 2012, 160,000 emails and instant messenger conversations were collected under Section 702. 90 percent of these communications were from online accounts not belonging to foreign surveillance targets.”</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fw.soundcloud.com%2Fplayer%2F%3Furl%3Dhttp%253A%252F%252Fapi.soundcloud.com%252Ftracks%252F307774868%26show_artwork%3Dtrue%26secret_token%3Ds-L4oFw&amp;url=https%3A%2F%2Fsoundcloud.com%2Fuser-275711973%2Fnumbers-02%2Fs-L4oFw&amp;image=http%3A%2F%2Fi1.sndcdn.com%2Fartworks-000207812915-ivsmuh-t500x500.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=soundcloud" width="800" height="166" frameborder="0" scrolling="no"><a href="https://medium.com/media/a45eb6dc31332439d76d6aa53285b1cd/href">https://medium.com/media/a45eb6dc31332439d76d6aa53285b1cd/href</a></iframe><p>If possible, you should also consider rounding the numbers in your interface. “More than 40%” may have just as much impact as “41.5%” in a sentence, and be much quicker to understand.</p><p>Also, be sure to drop unnecessary decimal points. Provided the decimal point isn’t making an intentional statement, 4.0% will be read like “four point zero percent,” and could be simplified to 4%.</p><h3>Oxford commas</h3><p>Oxford comma advocates may end up vindicated when we all ditch our phones for voice interfaces. While a minor grammatical issue, Oxford commas (otherwise known as <a href="https://en.wikipedia.org/wiki/Serial_comma">Serial commas</a>) are common enough to warrant a discussion. Style guidelines differ on whether or not they advocate use of these commas, so both with and without are technically correct for written language. But in an audio UI, missing this comma means a sentence may sound very awkward. Humans will pause if reading a series regardless of the second comma, but Alexa’s interpretation makes it sound like the last two items are grouped.</p><blockquote><strong>Original: </strong>“Almost half of the world’s timber and up to 70% of paper is consumed by Europe, United States and Japan alone.”</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fw.soundcloud.com%2Fplayer%2F%3Furl%3Dhttp%253A%252F%252Fapi.soundcloud.com%252Ftracks%252F307726432%26show_artwork%3Dtrue%26secret_token%3Ds-QILh0&amp;url=https%3A%2F%2Fsoundcloud.com%2Fuser-275711973%2Foxford-01%2Fs-QILh0&amp;image=http%3A%2F%2Fa1.sndcdn.com%2Fimages%2Ffb_placeholder.png%3F1487002698&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=soundcloud" width="800" height="166" frameborder="0" scrolling="no"><a href="https://medium.com/media/315d976c4c01ab1332cbe4a4740ce3f3/href">https://medium.com/media/315d976c4c01ab1332cbe4a4740ce3f3/href</a></iframe><blockquote><strong>Voice UI: </strong>“Almost half of the world’s timber and up to 70% of paper is consumed by Europe, United States, and Japan.”</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fw.soundcloud.com%2Fplayer%2F%3Furl%3Dhttp%253A%252F%252Fapi.soundcloud.com%252Ftracks%252F307726486%26show_artwork%3Dtrue%26secret_token%3Ds-yYhsq&amp;url=https%3A%2F%2Fsoundcloud.com%2Fuser-275711973%2Frevised-sentence-for-voice-ui-with-oxford-comma%2Fs-yYhsq&amp;image=http%3A%2F%2Fa1.sndcdn.com%2Fimages%2Ffb_placeholder.png%3F1487002698&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=soundcloud" width="800" height="166" frameborder="0" scrolling="no"><a href="https://medium.com/media/ddccf03f981ef6abbbdb758b6868f3c9/href">https://medium.com/media/ddccf03f981ef6abbbdb758b6868f3c9/href</a></iframe><h3>Other sloppy writing practices that will come back to digitally haunt you</h3><p>There are a few additional things that might pass in a written piece but don’t translate well (or at all) to audio interfaces:</p><ol><li><strong>Repeated words: </strong>You’ll need to be extra vigilant against these, as they are much more obvious when read aloud.</li><li><strong>Double hyphens:</strong> Putting “- -” (no space) instead of an em dash “ — ” to indicate a pause is fairly commonplace, and some text editors even translate that into an em dash automatically. But note that Alexa reads it quickly as a single hyphen.</li><li><strong>“And/or”:</strong> It’s not unusual to see this particular wording in written or informal text conversations on the web, but if you use for Alexa, it will be read literally as “…and or…” If you’d like Alexa to read the slash, you can enter it as “and / or”, but you may consider rephrasing to avoid it if possible.</li><li><strong>Caps =/= spelled out:</strong> Writing LAX will cause Alexa to attempt a phonetic interpretation, but writing L.A.X. or using a SSML tag will prompt her to spell it out.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/76/1*XEGc9FuxjHsO21XY1mDxFg.jpeg" /></figure><p>It’s also worth noting some of the other cool features Amazon gives developers to control language. While we don’t have much control over Alexa’s inflection or rhythm, Amazon has given us wide-ranging control over pronunciation and interpretation. Developers can use <a href="https://developer.amazon.com/public/solutions/alexa/alexa-skills-kit/docs/speech-synthesis-markup-language-ssml-reference">SSML</a> tags to spell out words by letter, add pauses, interpret numerical values in numerous ways, or even change pronunciation to match regional dialects or foreign words.</p><p>At the end of the day, while Alexa is surprisingly adept at interpreting most input, there are still many small things that can be done by designers and developers to improve the experience for the end user. Designing for voice is a complex endeavor, but care with your language will get you a long way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/76/1*XEGc9FuxjHsO21XY1mDxFg.jpeg" /></figure><p>thirteen23 is a digital product studio in Austin, Texas. We are an award-winning team specializing in human-centered design. Together with our clients, we conceive, design, and develop intelligent software. Ready to build the next big thing? <a href="https://www.thirteen23.com/contact/">Let’s talk</a>.</p><p><em>Find us on </em><a href="https://www.facebook.com/thirteen23?source=post_page---------------------------"><em>Facebook</em></a><em>, </em><a href="https://twitter.com/thirteen23?lang=en&amp;source=post_page---------------------------"><em>Twitter</em></a><em>, and </em><a href="https://www.instagram.com/hello.thirteen23/?source=post_page---------------------------"><em>Instagram</em></a><em> or get in touch at </em><a href="http://thirteen23.com/?source=post_page---------------------------"><em>thirteen23.com</em></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/90/1*XRJ5LLN6DdxDNyJWY60Dpg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=669e2c782569" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hello-thirteen23/when-robots-speak-human-669e2c782569">When Robots Speak “Human”</a> was originally published in <a href="https://medium.com/hello-thirteen23">Design after next</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fight Echo Chambers With Better UX]]></title>
            <link>https://medium.com/hello-thirteen23/fight-echo-chambers-with-better-ux-1e234d5e7146?source=rss-99c1b5aef37------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e234d5e7146</guid>
            <category><![CDATA[echo-chamber]]></category>
            <category><![CDATA[diversity-in-tech]]></category>
            <category><![CDATA[society]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[social-science]]></category>
            <dc:creator><![CDATA[Nikki Clark]]></dc:creator>
            <pubDate>Fri, 11 Mar 2016 04:18:22 GMT</pubDate>
            <atom:updated>2017-03-02T14:21:37.188Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X5_-gqtTJaEHklKH7A6Raw.jpeg" /></figure><h4>Four Design Techniques for More Inclusive Communities</h4><p>Here’s a situation you’re probably familiar with: your aunt/uncle/second cousin joins Facebook, you feel socially obligated to “friend” them, and now have to deal with their barrage of political rants that make you squirm. Thanks to the wonders of the internet, the topics you carefully avoid at holidays now show up one-sidedly in your feed when you least expect them. At some point, you start to associate Facebook with negative feelings and awkward interactions.</p><p>Designers are then tasked to fix this issue. These designers know the value of empathy, the importance of recognizing users individually and solving for their problems. They want users to feel happy while using the service. The solution? Build an algorithm that “learns” what people like to see, and cater the content they see to maximize what makes them happy. So Facebook filters out that little bit of political dissent from popping up unexpectedly in your day, and instead shows more posts from friends who care about the same issues as you do. Isn’t that the kind thing to do?</p><p>You see where this is going: eventually, you start to find yourself surrounded by yes-men with similar opinions, and the feed starts to build an echo chamber which slowly looks less and less like the world it was originally meant to mirror.</p><blockquote><strong><em>Echo chambers aren’t an artifact of design neglect, they are the outcome of UX best practices.</em></strong></blockquote><p>When the content a user sees is shaped by their own clicks, likes, and views, we feel like we’ve given the power back to the user. We absolve ourselves from responsibility. The problem is that we haven’t told users <a href="https://medium.com/@paminthelab/how-to-design-for-your-algorithmic-self-757c7df601e2#.wrgdfnfuf">how the power works</a>, or how to escape it. And they <a href="https://www.ted.com/talks/eli_pariser_beware_online_filter_bubbles?language=en">are</a> <a href="http://www.slate.com/articles/news_and_politics/frame_game/2010/05/bubble_think.html">trying</a> <a href="http://www.wnyc.org/story/buzzfeed-professional-internet-readers-break-bubble/">to.</a></p><p>As designers, in trying <em>not</em> to make decisions for our users, we’ve accidentally made a very large one.</p><p>If we truly want to give power to our users, it’s only fair to give them the power to opt out. This doesn’t mean forcing them out, it means building the tools and environments they can use if they want to.</p><p>To empower users to escape their own echo chambers, I’ve been thinking about four main techniques designers can apply:</p><ul><li>Expose Groups</li><li>Curate Wisely</li><li>Encourage Conversation</li><li>Give Underserved Communities a Platform</li></ul><p>Let me break these down.</p><h3>1. Expose Groups</h3><p>Lots of designed experiences already use groups to sort users and personalize content. Whether a user is in one group or twenty, and whether the groups are formally named or not, groups are an easy way for a experience to provide “smart” suggestions with relatively little effort.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QY0YJMWfVb5EwJ2y_Fv3wQ.png" /><figcaption>I picked my least embarrassing Netflix groups for this example.</figcaption></figure><p>Netflix does this well: when you’ve been added to the “Action &amp; Adventure Movie” group, you can see the top titles suggested for group members. And because the groups you’re assigned to show up on your homepage, it’s easy to understand how Netflix is categorizing you.</p><p>But then, this happens:</p><p><em>Action &amp; Adventure movies show up on your homepage -&gt; You watch more Action &amp; Adventure movies -&gt; You’re added to similar groups -&gt; The process starts over -&gt; You are now forever watching Action &amp; Adventure movies</em></p><p>What if you’d like to start watching travel documentaries? Or foreign films? In streamlining the product, Netflix has removed ways to explore groups you’re not a member of. Sure, you could use the search, but a blank form field is a high barrier to entry when you don’t know exactly what you’re looking for. No wonder, then, the social explosion around the discovery of “<a href="http://mashable.com/2016/01/11/netflix-search-codes/#99Jkd1n3aZq3">hidden Netflix codes</a>” as a way to view groups you’re not a part of.</p><p>Being able to see other people’s groups is surprisingly engaging: it allows users to explore new interests in a “safe” environment. For groups that don’t include sensitive data, like categories of content, music genres, or likes, giving users access also allows them a lot of power to explore new interests.</p><blockquote><strong>Takeaway:</strong> Allow users to see how they have been grouped, and to explore groups they are not a part of. Displaying the groups used doesn’t have to clutter the interface, as it can be offered as a secondary means of exploration.</blockquote><h3>2. Curate Wisely</h3><p>Not everyone wants to hunt through hundreds of hidden Netflix codes. For those that don’t, it is common for algorithms or curators to analyze a user’s behavior to craft recommended content.</p><p>Recommended content is almost always based on what users already like. If Spotify knows a user likes HipHop, it will share new HipHop tracks in their Discover Weekly playlist. If Google Now sees a user searching for polling locations, it will provide regular updates on the primaries and debate schedules.</p><p>But what if content suggestions were intentionally curated to encourage exploration?</p><p>We already have the tools we need to do this well. Finding existing trends in data could help reveal areas where encouraging exploration would be the most successful. Data trends could also help pinpoint commonalities across different types of content. Our Spotify HipHop listener might enjoy Alternative R&amp;B suggestions more than Country ones. Maybe an indie film director finds common ground in a designer’s process or workflow. Maybe a scientist finds commonalities in an artist’s gut instinct.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QKtA1Am-OJ4rfgoaQTO5MQ.jpeg" /><figcaption>The Great Discontent has been successful with a wide variety of creative individuals because the content focuses on commonalities across disciplines. Who knew a sculptor would have things in common with a fashion designer? Oh right, the humans curating it did.</figcaption></figure><p>The most effective way for this to work would be for algorithms to pinpoint connections, then humans could interpret them. Not all data trends are inspiring, and algorithms will find useless correlations. With the data sorting out of the way, however, humans are free to pattern-match and provide data-backed recommendations for other users.</p><blockquote><strong>Takeaway:</strong> Use data trends and human curators to encourage exploration in new ways that are likely to be of interest to the user. Start with what users have in common and go from there.</blockquote><h3>3. Encourage Conversation</h3><p>Facilitating genuine conversation between strangers can be one of the most effective tools to help users break out of their echo chambers. As one might expect, unfortunately, this is easier said than done.</p><p>One technique for doing this is encouraging conversation in public groups around a common, generic interest. The more diverse voices available, the better. This could be groups for neighborhoods, schools, or even cat videos. Moderation is important to keep these diverse crowds civil and positive. If a user is actively looking to break out of their echo chamber, these public spaces can be used as a safe environment for them to test the waters.</p><p>Another technique is to have a more formal question-and-answer style conversation, like Reddit’s AMAs (Ask Me Anything.) Usually in this scenario, the person answering questions from the crowd has some sort of unique life circumstance. The forced structure in this case may make it easier for hesitant users to participate.</p><p>These techniques are most effective if the user is getting extra value out of the service by engaging. With that said, consider the type of community and motivation of the users before encouraging conversation. Strangers bonding over a cancer diagnosis are likely to get value out of conversation, whereas strangers who happen to both wear red shoes probably will not.</p><blockquote><strong>Takeaway:</strong> Encourage conversation between different types of users. Build a community of respect and moderate consistently, and build “safe” spaces for conversation to happen. Discourage cliques. Find ways that this type of conversation is valuable to users.</blockquote><h3>4. Give Underserved Communities a Platform</h3><p>Exploration can also happen on it’s own if you set the stage right. If designers work to provide a platform for smaller, underserved communities, their message can be amplified to people who might not otherwise hear it. Encouraging this behavior helps build a culture that values open-mindedness and discourages echo-chambers, without the designer stepping in to play god.</p><p>For this to work effectively, the designer must:</p><ol><li>Help the average user locate these underserved communities</li><li>Establish a code of conduct to protect potentially vulnerable groups</li></ol><p>A code of conduct should include a combination of norms, written terms of use, swift action to remove and punish harassment, and potentially, additional “powers” granted to the vulnerable to protect themselves.</p><p>The podcasting world is a great example of this working well. Buzzfeed’s Another Round podcast, which is hosted by <a href="https://twitter.com/heavenrants">Heben Nigatu</a> and <a href="https://twitter.com/brokeymcpoverty">Tracy Clayton</a> and focuses on race and gender issues, has a large and diverse audience.</p><blockquote><em>“We get a lot of emails white listeners, that say, ‘you know what I’m just so glad to be able to sit in on these conversations… I’ve never had access to them before.” — </em>Tracy &amp; Heben, <a href="https://soundcloud.com/anotherroundwithhebenandtracy">Another Round</a></blockquote><p>Tracy and Heben aren’t responsible for educating the masses, but if they do want to share their message, designers are able to give them the tools to do so. Highlighting this podcast next to, say, NPR’s Planet Money, would encourage new demographics to tune in and expand their own online world.</p><blockquote><strong>Takeaway:</strong> Find underserved communities and highlight their work. Designers have the power to make niche messages accessible to the masses. Let users choose which communities matter to them.</blockquote><h3>This is Just a Start</h3><p>If we truly care about our users, building paths out of the experiences we’ve designed are necessary. As a community, I’d love to see more discussion around trusting and empowering our users to shape their own experiences. Giving them the tools to do the job is just the first step.</p><p><em>Do you have other UX strategies for breaking down echo chambers? I’d love to hear them. Hit me up on Twitter: @nikkic1ark</em></p><p><em>If you like this, I’d really appreciate a ❤ to help other people like you find it more easily. If you hate this, that’s cool too. We can still be friends.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e234d5e7146" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hello-thirteen23/fight-echo-chambers-with-better-ux-1e234d5e7146">Fight Echo Chambers With Better UX</a> was originally published in <a href="https://medium.com/hello-thirteen23">Design after next</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>