<?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[Artificial Design - Medium]]></title>
        <description><![CDATA[Stories about designing experiences - Medium]]></description>
        <link>https://medium.com/the-artificial?source=rss----34a226120b8c---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Artificial Design - Medium</title>
            <link>https://medium.com/the-artificial?source=rss----34a226120b8c---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 02:16:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/the-artificial" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Five Ways to Avoid Being Reactive]]></title>
            <link>https://medium.com/the-artificial/five-ways-to-avoid-being-reactive-d2bec48199ca?source=rss----34a226120b8c---4</link>
            <guid isPermaLink="false">https://medium.com/p/d2bec48199ca</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[consulting]]></category>
            <category><![CDATA[five-things]]></category>
            <category><![CDATA[collaboration]]></category>
            <dc:creator><![CDATA[Shannon E. Thomas]]></dc:creator>
            <pubDate>Fri, 28 Feb 2020 15:46:07 GMT</pubDate>
            <atom:updated>2020-02-28T15:30:12.163Z</atom:updated>
            <content:encoded><![CDATA[<p>Dealing directly with stakeholders can be a challenge. From gathering input to getting commitment for a design, the various opinions and methods of communication can be maddening. Good design requires patience and time. While gathering input from stakeholders is both necessary and valuable, allowing yourself to be reactive to their demands and concerns can take a toll on the final product.</p><p>In situations where the pressure is on, here are five things you can do instead of reacting:</p><h3>Take a deep breath.</h3><p>When confronted in a meeting or call, it’s easy to react quickly and in a way that will be reason for regret later. Maybe a developer doesn’t like an aesthetic choice that ties together the entire design system, or maybe an executive has a question about how to integrate a technology you’re unfamiliar with.</p><p>Take a deep breath in.</p><p>The developer may not understand the design system and the executive may not see that her request will delay launch by another nine months, but despite this, they both likely want to make the product the best it can be.</p><p>Consider what is being asked of you. Are you comfortable committing to a solution? If you are, great. Commit. If not, think about what you need to be confident.</p><p>Exhale.</p><h3>Ask questions.</h3><p>If you need to know more about a situation before providing a response, ask questions.</p><p>If you’ve taken a deep breath and a request seems off-the-wall crazy to you, get to the bottom of the situation by asking questions. Take a curious stance instead of a skeptical one, and ask what makes a stakeholder not like rounded corners, why a developer prefers a different solution than the one presented, or what brings up a specific concern for an executive.</p><p>Questions can also give you a moment out of the spotlight if you just need to formulate a response. Try something general about users’ behaviors, technology constraints, or business needs. While stakeholders respond, take another few deep breaths.</p><h3>Make your needs known.</h3><p>Consider what is being asked of you, and what you need to feel confident in providing a solution. If you need more time to explore alternative design solutions or if you need access to an expert, inform the room. You don’t need to get deep into the details, but you should ask if you need help setting up a meeting with someone or getting support from another team.</p><h3>Communicate a plan.</h3><p>Once you have answers to your questions and have made your needs known, set expectations for how long it will take to find a solution. If you’re dependent on someone else for input, make this clear. And if you don’t feel confident in committing to a solution, commit only to next steps.s</p><h3>Set a precedent.</h3><p>The more often you react to a question or demand, the more your colleagues will expect it. You might get a reputation for being reactive, or worse for making rash decisions in the moment. Instead, cultivate a reputation of being responsive and thoughtful. Commit only when you can, and make it clear what you need when you can’t. Stay focused on the work, the plan, and next steps. Rinse. Repeat.</p><p>Not only will these tactics help when managing stakeholders and their expectations, they will also keep you afloat when an asshole inevitably infiltrates your team. Reacting to ego and judgement only amplify the problems; whereas staying calm and prioritizing the quality of the work keeps the conversation progressing in a positive way.</p><p><em>Originally published at </em><a href="https://shannonethomas.com/2019/04/08/do-not-react.html"><em>https://shannonethomas.com</em></a><em> on April 8, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2bec48199ca" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-artificial/five-ways-to-avoid-being-reactive-d2bec48199ca">Five Ways to Avoid Being Reactive</a> was originally published in <a href="https://medium.com/the-artificial">Artificial Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Five Things to Avoid Saying]]></title>
            <link>https://medium.com/the-artificial/five-things-to-avoid-saying-49a7bb4b9e5?source=rss----34a226120b8c---4</link>
            <guid isPermaLink="false">https://medium.com/p/49a7bb4b9e5</guid>
            <category><![CDATA[five-things]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[Shannon E. Thomas]]></dc:creator>
            <pubDate>Fri, 28 Feb 2020 15:45:47 GMT</pubDate>
            <atom:updated>2020-03-01T08:27:54.112Z</atom:updated>
            <content:encoded><![CDATA[<p>Whether you are a consultant working with a client, a designer trying to integrate with a team of developers, or a creative director managing teams made mostly of designers, working with other humans can be messy or magical depending on the communication. Saying the right thing can inspire and motivate those around you. Saying the wrong thing can suck the energy out of a room and the life out of a project.</p><p>Here are a few common easy-to-avoid energy killers:</p><h3>“That’s not my problem.”</h3><p>There are two times when this phrase is commonly used. Perhaps you simply don’t want to do something. You might think that it’s beneath you or that it’s not your job. Even if the request doesn’t fall squarely in your realm of responsibility, supporting the team does. Accept the request understanding that your flexibility will be recognized by those around you.</p><p>Or perhaps you’re asked to do something outside of your sphere of influence. It’s not always easy to take on more responsibility or to tackle the new, but the designer who does will get more opportunities. Be honest about the situation and the request, and focus on getting what you need to conquer the problem rather than on making it someone else’s.</p><p>Try instead: <em>I might need some help with that.</em></p><h3>“Just tell me what you want me to do.”</h3><p>This phrase often slips out when a designer is frustrated, and it usually comes with the unmistakeable overtones of belligerence. Perhaps you’ve been asked to solve a problem that you just can’t figure out, or perhaps everything she comes up with is met with a negative reaction. Whatever the reason, reducing design to its execution is a dangerous move that could leave creative directors or clients thinking of you as a production designer. Instead of requesting explicit instruction, try asking questions and seeking examples for more clarity. If there’s somebody else who has more confidence, ask for their support in finding a solution.</p><p>Try instead: <em>Could we work through this problem together?</em></p><h3>“It’s done.”</h3><p>The ability to see flaws in anything is often referred to as the designer’s curse, and it’s what keeps us striving to always make things better. Claiming that a design is “done” communicates not that there is nothing left to explore or improve, which is rarely the case, but rather that you cannot see anything left to explore or improve. When tackling a challenge, always have an idea of what finished is as well as an idea of what you’ll do to improve the design should you have extra time. And if you find yourself stuck, seek input over approval.</p><p>Try instead: <em>I feel confident about the work, but would appreciate a fresh pair of eyes.</em></p><h3>“I didn’t know.”</h3><p>This phrase is commonly used when the designer is hit with a critique or requirement that she didn’t see coming. While it may be true that she didn’t know, phrasing it this way also abdicates responsibility for knowing. Take an active stance towards knowledge. Ask questions and confirm your understanding, and the focus will move from the potentially embarrassing thing you didn’t know to your ability to understand and accommodate new constraints.</p><p>Try instead: <em>Could you tell me more about that?</em></p><h3>“That’s how it’s always done.”</h3><p>This phrase often comes after questioning a specific decision in a design, and when it is uttered without any hint of sarcasm, the speaker is usually peddling in bullshit. While it may be true that something is usually done a certain way, this defensive phrasing comes across as an excuse rather than an explanation. Bring your audience along for the ride and talk about why something is done the way it is, why the convention exists, and why you chose to implement it that way in your design. And if you don’t have any of that, have a laugh and offer to try it a new way. After all, we should never resist trying new things.</p><p>Try instead: <em>I’ve never done it that way before, but let’s see if it works.</em></p><p><em>Originally published at </em><a href="https://shannonethomas.com/2019/03/17/avoid-saying.html"><em>https://shannonethomas.com</em></a><em> on March 17, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49a7bb4b9e5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-artificial/five-things-to-avoid-saying-49a7bb4b9e5">Five Things to Avoid Saying</a> was originally published in <a href="https://medium.com/the-artificial">Artificial Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Five Successes]]></title>
            <link>https://medium.com/the-artificial/five-successes-9382787ab4ea?source=rss----34a226120b8c---4</link>
            <guid isPermaLink="false">https://medium.com/p/9382787ab4ea</guid>
            <category><![CDATA[agencylife]]></category>
            <category><![CDATA[five-things]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[lessons-learned]]></category>
            <category><![CDATA[agency]]></category>
            <dc:creator><![CDATA[Shannon E. Thomas]]></dc:creator>
            <pubDate>Sun, 30 Sep 2018 10:28:48 GMT</pubDate>
            <atom:updated>2018-09-30T13:14:53.288Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d_P9pSnDeWPmwT_bYrs3Fw.png" /></figure><p>The past five years have been a roller coaster as Hans and I struggled in the downs and reveled in the ups of having a small boutique agency. As we entered our fifth year, we began to ask ourselves <em>What’s next?</em> without any obvious answer. In many ways, we’d done what we set out to do, and had come to the surprising realization that neither of us was enjoying it. In short, the experiment had run its course, and it was time to move on.</p><p>With the decision now months in the past, I’m spending my last afternoon in our lovely little Herengracht studio. All of our employees have new jobs, most of our furniture has found new homes, and what remains is packed into boxes. Saying goodbye is hardly easy, but I also cannot help but feel a sense of pride and accomplishment for the thing that we built.</p><p>So without further ado, here are five of my proudest accomplishments of the past five years.</p><h3>Creating a Safe and Challenging Environment</h3><p>When we founded The Artificial, Hans and I set out to create an environment where our employees would be challenged to do their best work for clients while also creating a safe space for exploration and room to learn from failure. Safe and challenging were goals we kept in mind while recruiting, when planning projects, and when choosing clients. In hiring, we filtered out candidates who came across as ego-driven and focused on finding designers who were curious and passionate; when creating proposals for clients, we always made room for experimentation and collaboration beyond standard client deliverables; and when we found ourselves working with clients who proved more challenging than productive, we hastily ended those relationships.</p><p>As an accident The Artificial ended up being almost entirely female, something we became known for. Before long, our applicant pool was over 75% women. This was a far cry from the 25% female agency I had left behind.</p><h3>Leaving our Clients with Higher Expectations</h3><p>Many of our clients decided to work with us despite low expectations of agencies. We took our responsibility as a trusted partner seriously, and impressed clients with not only the quality of our work, but also with the openness of our process. The care we put into bringing our clients along for the journey of design helped elevate both the conversation and the work itself.</p><p>It was gratifying to see our clients happy, but even more to see them adopting our methodologies and deliverables in their own internal processes.</p><h3>Making Time for Side Projects</h3><p>Over five years, we had dozens of side projects, both published and unpublished. It was through these side projects that we experimented and played outside the bounds provided by client work. When work was busy, we tried to make time for side projects, and when work was slow, we used side projects to better ourselves. Some favorite side projects include <a href="https://www.toicon.com/">to [icon]</a> where we explored visual systems of pixel perfect metaphors, <a href="https://theartificial.com/cocktails/">Friday Cocktails</a> where we practiced our bartending skills, and our annual holiday books (<a href="https://theartificial.com/blog/2017/01/16/sinterklaas-book.html">2016</a>, <a href="https://theartificial.com/blog/2017/11/28/holiday-gids.html">2017</a>) where we designed for print instead of for pixels.</p><h3>Experimenting with Process and Methodology</h3><p>Throughout side projects, we not only experimented with the product of design but also with the process of design. We regularly tried out new tools and buzzword methodologies to see how we could improve our process and approach for client projects. Looking back on the past five years of work, it’s clear that we got better with age.</p><p>I’m now capturing these processes into a book based on my learnings from The Artificial, learnings not only about process, but also about how people learn new processes.</p><h3>Providing a Leg Up for our Employees</h3><p>One of the truest measures of success for any workplace is whether or not it leaves its employees better for having worked there. For most of our employees, I can say that we did this. It’s in the success of former Artificers that The Artificial lives on, and it’s a joy to see these talented women conquer the design world — teaching and mentoring others.</p><p><em>Originally published at </em><a href="https://artificial.design/blog/2018/09/28/successes.html"><em>artificial.design</em></a><em> on September 28, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9382787ab4ea" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-artificial/five-successes-9382787ab4ea">Five Successes</a> was originally published in <a href="https://medium.com/the-artificial">Artificial Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Artificial Conversations: The Art of Feedback]]></title>
            <link>https://medium.com/the-artificial/artificial-conversations-the-art-of-feedback-78e2ff315130?source=rss----34a226120b8c---4</link>
            <guid isPermaLink="false">https://medium.com/p/78e2ff315130</guid>
            <category><![CDATA[critique]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[artificial-conversations]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[agencylife]]></category>
            <dc:creator><![CDATA[Shannon E. Thomas]]></dc:creator>
            <pubDate>Mon, 26 Mar 2018 11:20:44 GMT</pubDate>
            <atom:updated>2018-03-26T11:01:44.468Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZmBZr5MCUQKo0X3sgW20aw.png" /></figure><p>This week we discussed <a href="https://www.thnk.org/insights/the-other-side-of-the-stick-how-to-receive-feedback/">this article</a> on receiving creative feedback.</p><p>Critique is an important part of any design process, yet it’s not something we’re formally taught to do, and it’s something many companies don’t take seriously. Critiques can cause anxiety, they seem to encourage reactiveness, and they might even result in rifts amongst design teams.</p><h3>Get feedback early and often.</h3><p>Manjari brought up how important it is to get critique when you’re able to do something about it. As the maker of the thing being critiqued, it’s your responsibility to solicit feedback so that you have time to incorporate feedback. If you’re not getting feedback, be afraid. It’s likely that the feedback is still there, waiting to be uncovered.</p><p>Ariane brought up that critiques aren’t just a moment for getting feedback, they’re also important for inclusion. Getting people into a room together means hearing voices that might not always be heard. With many voices comes some risk, so it’s important to help everyone understand what feedback is useful.</p><p>Manjari doubled down on this point. Scale is important. Getting big-picture feedback as the details are being worked out can cause major disruption, and may need to be disregarded to maintain the project’s schedule.</p><p>Hans observed some cultural differences with critique — and how the Dutch seek consensus, while Americans lean towards progress. Critique sessions should not only be about gathering input, but also about making that input into something that has clear next steps to maintain momentum.</p><p>Manjari mentioned how valuable it is to end a feedback session by enumerating next steps. This ensures both alignment and that actions will be taken.</p><h3>Understand where feedback is coming from.</h3><p>Not all critique is created equal. Natalia mentioned that she frequently disregards feedback that considers only the giver’s tastes without consideration for the user or the design system. Hans agreed. To fail to consider the context is lazy. Ariane believes the critique should be civil. After all, being aggressive towards a person isn’t likely to make the work better. Manjari added that ambiguous critique like <em>“Maybe you should try something else.”</em> fails to provide insight into either the problem or the solution.</p><p>Good critique considers its context, and it seeks to help the person presenting their work move forward. But what else? Ariane added that she’s more likely to trust the critique that comes from a person that she trusts. In other words, someone with expertise is more likely to speak from that broad knowledge rather than their own narrow perception.</p><p>Natalia mentioned how important it is to write feedback down even if you don’t agree with it. Not only can this help keep the presenter from getting caught up in the reaction, it also provides documentation to come back to later — even if it’s only to say, <em>“This was bad feedback.”</em></p><p>Ariane mentioned how critiques provide an opportunity for discussion, and how important it is to use this time to understand the <em>why</em> behind a person’s feedback. Getting to <em>why</em> isn’t always easy, and sounding inquisitive without coming across as reactive to criticism can be a struggle.</p><h3>Be considerate when providing feedback.</h3><p>One of my favorite quotes about critique comes from the Pixar movie <em>Ratatouille</em>.</p><blockquote><em>In many ways, the work of a critic is easy. We risk very little, yet enjoy a position over those who offer up their work and their selves to our judgment. We thrive on negative criticism, which is fun to write and to read. But the bitter truth we critics must face, is that in the grand scheme of things, the average piece of junk is probably more meaningful than our criticism designating it so.</em></blockquote><p>As someone offering critique, it is important to remember that the person being critiqued has likely thought about the work more than you. Your critique is not only of the thing you’re looking at, but also the intentions behind it. For this reason, it’s important to seek an understanding of their reasons when providing feedback.</p><p>Natalia pointed out that much criticism focuses on the negative, and that pointing out mistakes is not only demoralizing, it’s often not terribly helpful to improving a design.</p><p>Ariane mentioned that providing feedback with a reason is important. It’s likely that the presenter has their own reasons, and hearing the <em>why</em> behind a piece of criticism can help refine intentions, not just the output.</p><p>Ariane also mentioned that providing good feedback means understanding the context. Often a thorough understanding of intentions and decisions can lead to more compelling feedback.</p><p>Did this conversation change anything for The Artificial? I suspect our already strong critique culture will just get stronger. As a studio, we seek feedback often, and we’re considerate when providing it to each other. When sharing work, we’re good at integrating new ideas and exploring opinions that don’t agree with our own, even if it’s only as a counterexample to the choice we’ve made.</p><p>It’s only natural that our internal attitudes towards critique extend towards our external relationships with clients. We work closely to maintain an open channel for feedback; we seek to create opportunities for conversation between teams; and we provide teams with provocations that drive decisions. And much like a critique, listening and understanding <em>why</em> is vital to making good decisions on behalf of our clients and users.</p><p><em>Originally published at </em><a href="https://theartificial.com/blog/2018/03/26/feedback.html"><em>theartificial.com</em></a><em> on March 26, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78e2ff315130" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-artificial/artificial-conversations-the-art-of-feedback-78e2ff315130">Artificial Conversations: The Art of Feedback</a> was originally published in <a href="https://medium.com/the-artificial">Artificial Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Artificial Conversations: Undesigned Success]]></title>
            <link>https://medium.com/the-artificial/artificial-conversations-undesigned-success-93afddd3eb4c?source=rss----34a226120b8c---4</link>
            <guid isPermaLink="false">https://medium.com/p/93afddd3eb4c</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[artificial-conversations]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Shannon E. Thomas]]></dc:creator>
            <pubDate>Mon, 19 Mar 2018 17:00:37 GMT</pubDate>
            <atom:updated>2018-03-19T17:00:30.130Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mCm8NCPMaybz-Kc7r1qTZg.png" /></figure><p>This week we discussed <a href="https://www.fastcodesign.com/90160960/the-design-theory-behind-amazons-5-6-billion-success">Amazon’s success</a> despite their lack of overt design.</p><p>Ariane expressed some surprise at how websites with such little design effort could have so much success. Manjari brought up how many of these websites — from Alibaba to Booking.com, were born from a functionality-first approach. In the case of Amazon, this function was conversion, and the optimization is a design of sorts.</p><h3>Designing for everyone means looking less designed.</h3><p>Manjari mentioned that sites that target a specific user end up leaving many others behind, and of course this hurts conversion. Companies like Airbnb take a more design-oriented approach, and they end up feeling more exclusive and less for everyone.</p><p>Kamila brought up a recent struggle with the Ikea website. Perhaps because it was born of the store’s inspiration-first showroom approach rather than the user’s need to find a thing, it’s incredibly difficult to find products of a specific type or solutions for a specific problem. In the end, it was easiest for Kamila to search Amazon to get a list of options side-by-side.</p><p>And as Manjari pointed out, perhaps shopping has become more about convenience than leisure. When we want inspiration, we can visit stores like Ikea or websites like Pinterest. When we want to buy something, we have Amazon.</p><h3>Just because it’s not polished, doesn’t mean it’s not designed.</h3><p>While Amazon’s sites lack the polish of Apple’s, they are still designed. Natalia brought up a teacher who once told her, <em>If the aesthetics aren’t good, at least make it consistent.</em> This consistency is evident in the different vendor pages, which Amazon insists remain feeling like Amazon. The consistency of the experience helps the user understand that she doesn’t need to worry who is fulfilling his order — it will still feel like Amazon.</p><p>Ariane brought up how the consistency helps build trust. After two orders, the user knows what to expect. After more orders, she knows that Amazon is a better experience than most other retail experiences she’s had. While the website may lack polish, the design of the user’s experience of getting the perfect product certainly is.</p><h3>Design is more than a website.</h3><p>Natalia brought up that, while their site is not as beautiful as it might be, Amazon’s apps are more traditionally well designed. Downloading an app is a type of conversion, and this commitment helps Amazon know what sort of user they need to design the optimal experience for. Then the experience can get more specific and more designed.</p><p>Manjari brought up how Amazon has designed their entire organization in a way that builds great products. They believe in self-investment, and seek new ways to deliver great experiences to users. This sort of organizational design is often the most difficult (and has the greatest influence), and should not be overlooked just because a company’s website isn’t beautiful.</p><p>Did this conversation change anything for The Artificial? Mostly it reinforced what we already know. Great experiences encompass many touchpoints, and every touchpoint has its own demands an constraints. For companies that work at the scale of <em>everyone</em>, the lack of a defined user means the lack of an opinionated design, which is easily mistook for no design at all.</p><p>As designers, we spend a lot of time designing, empathizing, and making decisions for the user. Yet it can be difficult to truly put the user in control. Because giving the user more control means giving up some of our own.</p><p><em>Originally published at </em><a href="https://theartificial.com/blog/2018/03/19/undesigned.html"><em>theartificial.com</em></a><em> on March 19, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=93afddd3eb4c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-artificial/artificial-conversations-undesigned-success-93afddd3eb4c">Artificial Conversations: Undesigned Success</a> was originally published in <a href="https://medium.com/the-artificial">Artificial Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Artificial Conversations: Something Is Wrong]]></title>
            <link>https://medium.com/the-artificial/artificial-conversations-something-is-wrong-1f083212870?source=rss----34a226120b8c---4</link>
            <guid isPermaLink="false">https://medium.com/p/1f083212870</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[algorithms]]></category>
            <category><![CDATA[artificial-conversations]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Shannon E. Thomas]]></dc:creator>
            <pubDate>Tue, 13 Mar 2018 09:11:25 GMT</pubDate>
            <atom:updated>2018-03-07T11:12:52.784Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZmBZr5MCUQKo0X3sgW20aw.png" /></figure><p>This week’s Monday morning conversation revolved around James Bridle’s article <a href="https://medium.com/@jamesbridle/something-is-wrong-on-the-internet-c39c471271d2">Something is wrong on the internet</a></p><p>This article inspired a conversation that was part shock and part reflection. How is it that we have children watching content that’s made for them yet completely inappropriate? How is it that the only humans involved in some of these interactions are the children doing the consuming?</p><p>Several Artificers chatted with friends and family with children to better understand how kids were interacting with technology. The article was forwarded. The shock was shared.</p><p>More important than the shock was our reflection. As designers of systems, how do we fix the internet?</p><h3>Empathize with those who would exploit the system</h3><p>Manjari brought up how things have scaled more quickly than anyone had anticipated. Ariane followed up wondering how we could have anticipated the bots. Hans countered — can we really blame the bots when we have humans behind so much abhorrent content (for both children and adults)?</p><p>Technology often has unintended consequences, and anticipating these consequences is not always something that designers take enough responsibility for. While none of us have fully fleshed out evil personas, several of us have worked on projects where we explicitly considered <em>what could go wrong</em> as well as <em>who might exploit this and how</em>. Being able to empathize with evil-doers is a designer’s responsibility.</p><p>Manjari brought up that it’s not only designers who should be seeking to protect users from harm. Everyone on the team — from the business stakeholders demanding features to the engineers maintaining a system’s security — needs to understand the risks to the user and take some responsibility for safeguarding against the worst intentions.</p><h3>Take responsibility for the system</h3><p>Ariane mentioned that her friends with kids had no idea what content existed, and that they were quick to trust if something was labeled for kids that it would also be safe for kids. In many cases, a clear and obvious warning about the content could help companies and parents come to an understanding before children are shown potentially harmful content.</p><p>Transparency paired with control could go a long way. Natalia brought up parental controls that force some involvement from the parent — either in selecting approved channels or specific types of content. Giving parents the control to approve specific channels would not only help moderate the market, it would also force bots to create content that appeals to parents and not just children.</p><p>Kamila suggested that we should consider still having humans involved in moderation. Tech companies often blame the algorithm to avoid taking responsibility themselves. Taking back the responsibility might cost more money both in terms of moderators and the inevitable PR battles that come from censorship claims — but taking responsibility could also lead to a more aggressive attitude in solving the inappropriate-content problem.</p><p>Hans had a more cynical approach: follow the money. If a content distributer’s income comes from advertisers, make it so that advertisers have more control over what their ads appear next to. This would also force content to appeal to more discerning minds than those of 3 year olds.</p><h3>Give the power (and the responsibility) back to users</h3><p>Providing unfettered access to content creates problems, even when the content is high quality. Nathalie recalled that her mom used to make her clean her room before a show came on. Because shows came on at a time, this created a sense of urgency to complete a chore. As a young child, she learned to deal with constraints and deadlines.</p><p>By eliminating the barriers to consumption, have we removed something more important? Hans brought up how internet porn has affected teens’ ideas of sex and Manjari mentioned how relationships in Japan have suffered in recent years as men are having more digital relationships with fake females.</p><p>We all have memories of waiting for a commercial break to run to the toilet or having to rewind a VHS to catch something we missed. All of these little inconveniences were opportunities for learning. How might we design these back into our experiences of content consumption?</p><p>Ariane mentioned a service that provided discounts and rewards to students who didn’t check facebook during school hours. Perhaps if we cannot enforce constraint, we should instead reward discipline.</p><p>Did this conversation change anything for The Artificial? Aside from all of us being a little less naïve now, we’re also sure to consider users with nefarious intentions alongside our other personas when designing experiences.</p><p><em>Originally published at </em><a href="https://theartificial.com/blog/2018/03/05/somethingwrong.html"><em>theartificial.com</em></a><em> on March 5, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f083212870" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-artificial/artificial-conversations-something-is-wrong-1f083212870">Artificial Conversations: Something Is Wrong</a> was originally published in <a href="https://medium.com/the-artificial">Artificial Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Artificial Conversations: Ethical Design]]></title>
            <link>https://medium.com/the-artificial/artificial-conversations-ethical-design-c2f0f214a1de?source=rss----34a226120b8c---4</link>
            <guid isPermaLink="false">https://medium.com/p/c2f0f214a1de</guid>
            <category><![CDATA[artificial-conversations]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-ethics]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Shannon E. Thomas]]></dc:creator>
            <pubDate>Tue, 13 Mar 2018 09:11:01 GMT</pubDate>
            <atom:updated>2018-03-26T14:19:47.760Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xlJrQeRkE3dIVapijntLsQ.png" /></figure><p>This week we discussed design ethics as presented by <a href="https://2017.ind.ie/ethical-design/">ind.ie</a></p><p>Conversations around design ethics are hardly new, and best practices abound for how to respectfully engage in design for humans of diverse origin, context, and need. These best practices often look at design more as a process than an outcome, and this is where the Ethical Design pyramid presented by Aral and Laura differs. It suggests that ethical design should be built on a platform of ethical technologies — starting with a foundation that embraces human rights, building on that foundation with a respect for human effort, and finishing with an effort to create an appropriate (or delightful) human experience.</p><p><em>Why?</em> and <em>How?</em> are the obvious next questions — questions left unanswered by the Ethical Design Manifesto. Do decentralization and openness really make a design ethical? There was a universal feeling of wanting to see more examples of how the manifesto might be applied to make better decisions.</p><p>With this, we reflected on our own experiences, both personally and as a company, to evolve our own thinking around the ethics of design.</p><h3>Know where your empathy is coming from.</h3><p>Hans brought up that there are many ways to define “us” and “them”. While often simplified to a culture, a region, or a demographic, users could be as specific as “bankers at ABN AMRO in Amsterdam” or as generic as “Expats”.</p><p>Natalia brought up how dangerous it is to design as an outsider. From an outside perspective, Mexican design might seem full of pink and gradients. But designing for México means understanding that tastes vary based on class, education, etc. This might mean narrowing focus to better understand a specific user type, or it may mean broadening your perspective to understand the nuance of a culture.</p><h3>Seek the expertise you need.</h3><p>Having the right amount of relevant perspectives is important when designing. Kamila mentioned that having a target group design for themselves is likely to fail, as not all target groups will have the right expertise to design a product.</p><p>And of course, not all designers have the expertise in a specific field or context to create relevant experiences. Hans brought up an Artificial client — Philips Male Grooming. As a company of women, we rely heavily on research and on Hans’s personal experiences to design experiences appropriate to the men using those products.</p><p>Kamila followed up with an obvious example — women’s toilets. Even with the amount of available feedback, women’s restrooms continue to be designed with the same inadequate requirements as men’s.</p><p>Manjari brought up Google Messaging in India, and how their design process ensured a deeper-than-research understanding of the context. She brought up how valuable partnerships can be for smaller agencies when approaching unfamiliar contexts.</p><p>Knowing a thing isn’t as important as understanding a thing, and as designers, it’s important to know the difference…as well as our own limitations.</p><h3>Design isn’t finished when a product ships.</h3><p>Kamila brought up a project where we were working to design a connected hospital experience. Throughout the project, the team was working with hospitals to better understand what was happening in the operating room. For us, this meant a few surprising (but necessary) changes in requirements.</p><p>I mentioned how every hospital was likely to be slightly different, and how designing to accommodate human effort would mean designing for each specific context.</p><p>Natalia brought up how important testing is so that design can refine a product alongside the input of actual users.</p><p>Manjari, again struggling with the specificity around design’s responsibilities, mentioned that design would be stronger as a discipline if we insisted that it continue beyond the delivery of the design itself. We have a responsibility for the things we put into the world, and we shouldn’t wipe our hands clean once we’ve captured our intentions via documentation.</p><p>This point is an important one to the ethics of design, mostly because it means disrupting our usual way of working. Creating a design is not enough. Shipping a design is not enough. As designers, we need to follow through to see how our intentions (which are at best design hypotheses) are used, misused, and appropriated by users.</p><p>Did this conversation change anything for The Artificial? We are opinionated and have strong points of view about how to ethically approach design, but we are also young, and so many of those views remain untested. As an agency, we will continue to seek work and to structure projects in ways that prioritize the user’s relationship to the things we design. And we will continue to iterate on our process so that we can be more conscientious in our approach, more thorough in our execution, and more ethical as an agency.</p><p><em>Originally published at </em><a href="https://theartificial.com/blog/2018/03/12/designethics.html"><em>theartificial.com</em></a><em> on March 12, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2f0f214a1de" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-artificial/artificial-conversations-ethical-design-c2f0f214a1de">Artificial Conversations: Ethical Design</a> was originally published in <a href="https://medium.com/the-artificial">Artificial Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Artificial Conversations: Normal Design]]></title>
            <link>https://medium.com/the-artificial/artificial-conversations-normal-design-d8f265e8304d?source=rss----34a226120b8c---4</link>
            <guid isPermaLink="false">https://medium.com/p/d8f265e8304d</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[artificial-conversations]]></category>
            <dc:creator><![CDATA[Shannon E. Thomas]]></dc:creator>
            <pubDate>Mon, 26 Feb 2018 15:46:43 GMT</pubDate>
            <atom:updated>2018-02-26T15:46:01.212Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mCm8NCPMaybz-Kc7r1qTZg.png" /></figure><p>This week’s Monday morning conversation revolved around Frank Chimero’s blog post <a href="https://frankchimero.com/blog/2017/plainness-and-sweetness/">Plainness and Sweetness</a></p><p>We were one person short today, but that didn’t stifle the conversation. We all started generally agreeing with Chimero — plain, normal, vanilla design is important. But then we got into what <em>normal</em> means, and the conversation got much more interesting.</p><h3>Normal is a trend.</h3><p>What makes normal <em>normal</em>?</p><p>Most of us started off the conversation adamantly agreeing with Chimero’s statements about defending plainness in design, but as the conversation progressed, Natalia pointed out that the very idea of what’s normal is a trend. After all, the typefaces used as an example of plainness in the post are by one of the trendiest foundries just as normcore is a trend in fashion.</p><p>Manjari brought up Frank’s assertion that Helvetica is a cliché. For a designer or a population growing up without the Roman alphabet or ideals of minimalism, western clichés are likely foreign and unfamiliar. Vanilla is subjective.</p><p>Furthermore, what’s normal to an expert or practitioner is often not what’s normal to users. Sure, we can all recognize Helvetica. But can our parents? Perhaps as designers we should worry less about what is normal and more about where recognizably abnormal begins.</p><h3>Normal changes with time and place.</h3><p>Does normal apply to interaction as well as to aesthetics?</p><p>Kamila brought up that sticking to common patterns is more important in some situations than others. For example, when designing for a hospital, what’s expected is more important than when creating other consumer experiences. We worked on an interface for hospital workers last summer, and, while we were a touch disappointed that the most basic option (in both interaction and aesthetics) was chosen, it makes sense considering the stress of such a high-stimulation environment. It’s also worth noting that being basic didn’t make the design any less beautiful.</p><p>Hans brought up the industrial design concept of Super Normal (also mentioned in Chimero’s post), and how it’s often mistaken as minimalistic. Super Normal is instead the type of normal that is defined by use. As Naoto Fukasawa says, “…perhaps the continuation of a good relationship that has been around for a long time is better than anticipating something new.”</p><p>So obviously what’s normal changes with context, and understanding our users’ contexts is what makes research on any design project so important.</p><h3>Normal needs to be balanced.</h3><p>How do we push beyond normal, and how do we know when we’ve pushed too far?</p><p>Natalia brought up a situation after a design jam where she struggled to present a concept because it had become so complex. In short — if it’s hard to explain, it’s likely abnormal.</p><p>Hans suggested that we can see how far from normal interaction is by knowing how much of our design guidelines fall outside of the standard Android development guidelines or iOS HIG.</p><p>As a way of working, Natalia mentioned that it’s important to go too far from normal, then to return, and to repeat until balance is achieved.</p><p>This cyclical process might seem obvious, but in practice it’s rare. Many design processes start with interaction design (wireframes) and move into visual design, failing to establish a consistent idea of normal. <em>Normal</em> and <em>special</em> are applied at layers that reflect the organization of design teams rather than being considered holistically for the experience being designed.</p><p>Did this conversation change anything for The Artificial? It certainly validated our way of working. Rather than starting with wireframes and layering on the visual design, we start with a normal for both interaction and visual design and layer on what makes the experience special. After this conversation, I suspect we’ll all be a bit more intentional with this process, and we’ll watch more carefully for the boundaries between normal and abnormal (or familiar and unfamiliar).</p><p><em>Originally published at </em><a href="https://theartificial.com/blog/2018/02/26/normal.html"><em>theartificial.com</em></a><em> on February 26, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8f265e8304d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-artificial/artificial-conversations-normal-design-d8f265e8304d">Artificial Conversations: Normal Design</a> was originally published in <a href="https://medium.com/the-artificial">Artificial Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Artificial Conversations: Should Designers Code]]></title>
            <link>https://medium.com/the-artificial/artificial-conversations-should-designers-code-e4ba2aee6535?source=rss----34a226120b8c---4</link>
            <guid isPermaLink="false">https://medium.com/p/e4ba2aee6535</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[artificial-conversations]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Shannon E. Thomas]]></dc:creator>
            <pubDate>Mon, 19 Feb 2018 16:20:19 GMT</pubDate>
            <atom:updated>2018-02-19T16:28:02.928Z</atom:updated>
            <content:encoded><![CDATA[<p>This week’s Monday morning conversation revolved around Alan Cooper’s four-part article: <a href="https://medium.com/@MrAlanCooper/should-designers-code-f7b745b8cd03">Should Designers Code?</a></p><p>This conversation got off to a slower start than others. There was a general agreement with his article, along with a bit of surprise at just how opinionated Cooper’s stance was.</p><h3>Empathy for each other starts by getting to know each other.</h3><p>Kamila pondered how odd it is that we seem to expect designers to code, but somehow that we would never expect a developer to do design. Perhaps if we are to have a mutual respect for each other, we should start with a more inclusive process.</p><p>Everyone agreed that having everyone involved from the beginning of a project is a good idea. Ariane believes it’s a good idea to start collaborative processes by understanding the team. What is everyone responsible for? Natalia mentioned that it’s also important to know what people care about. After all, sometimes responsibility and passion aren’t aligned.</p><p>If we start every project by getting to know each other, then we’re sure to be more inclusive in our decision making processes and we’ll likely be less defensive when someone disagrees with a decision we’ve made.</p><h3>Communicate the why along with the what.</h3><p>Natalia mentioned how frustrating it is to give a developer a design only to get back something completely different a week later. But perhaps that was the problem — there was no conversation in between.</p><p>Kamila put forth that designers should help developers understand design decisions. This way when the design needs to change based on development constraints, it can be done understanding the priorities of the design. To which Ariane brought up The Artificial’s design guidelines, which often capture such decisions.</p><p>By capturing our reasoning, we can ensure that nobody makes or remakes decisions in a vacuum. This might be done in a PDF or it might be done in a wiki — the most important thing is that it’s in a place where everyone from developers to business partners can access it.</p><h3>Good conversation beats good documentation.</h3><p>Ariane made a second point about our design guidelines — they’re overwhelming. There are so many small decisions make up even the simplest of screens, and in many situations, this leads developers to ignore the documentation entirely.</p><p>Hans pointed out the exception: when we take the time to walk through the guidelines together. To this, Manjari brought up a previous experience where it wasn’t until everyone was in a room together that everyone finally began to share the same understanding of the thing they were trying to build.</p><p>Conference calls and Slack conversations can help keep a team aligned, and, especially for teams working across timezones, keeping these channels open is essential to a project’s success. But even more helpful is getting everyone together in a room together.</p><p>Did this conversation change anything for The Artificial? While we’re still enthusiastic about learning to code, our individual motivations may have changed. And now we’re motivated by something else — collaborating in ways that help us all have more empathy for each other.</p><p><em>Originally published at </em><a href="https://theartificial.com/blog/2018/02/19/should-designers-code.html"><em>theartificial.com</em></a><em> on February 19, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4ba2aee6535" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-artificial/artificial-conversations-should-designers-code-e4ba2aee6535">Artificial Conversations: Should Designers Code</a> was originally published in <a href="https://medium.com/the-artificial">Artificial Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Artificial Conversations: Technology and the Scope of Design]]></title>
            <link>https://medium.com/the-artificial/artificial-conversations-technology-and-the-scope-of-design-6b6a78431bf7?source=rss----34a226120b8c---4</link>
            <guid isPermaLink="false">https://medium.com/p/6b6a78431bf7</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[artificial-conversations]]></category>
            <dc:creator><![CDATA[Shannon E. Thomas]]></dc:creator>
            <pubDate>Mon, 19 Feb 2018 16:18:03 GMT</pubDate>
            <atom:updated>2018-02-19T16:28:33.099Z</atom:updated>
            <content:encoded><![CDATA[<p>This week’s Monday morning conversation was inspired by our recently published <a href="https://theartificial.com/blog/2018/02/08/connection-flows.html">connection flows</a> blogpost. We began by discussing the article itself, and then the reasons why the article was important. We wondered why designers so often didn’t seem interested in the technology behind connections, and Natalia brought up that she always felt that those sorts of technical decisions were out of scope.</p><p>This brought up an even more important question than “How do things connect?” — Why do designers often consider the technology that so often defines our designs out of our design scope?</p><h3>There’s just too much to know.</h3><p>To Natalia’s point, it’s not a surprise that designers often believe that technology decisions are something beyond their influence when the decision is often made before design is even engaged. Often, we take this as part of the brief. The app will run on iOS and Android and the product will connect via Bluetooth. Even when the tech decision is bad for user experience, we tend to accept them as a necessary evil. We spend many painful hours designing sub-par solutions to try to hold together a broken experience. We might even complain to each other about how much the technology sucks.</p><p>But we’ll often avoid the people who matter most — the people who made those decisions in the first place. Why is that?</p><p>Kamila mentioned that she’s always assumed that because technologists spend so much time around technology that they have a deep understanding that will always be out of a designer’s (or novice’s) grasp. It’s true. At first, it’s hard to know what questions to ask a technologist (or Google) to get answers that will help you understand the technology behind a thing.</p><p>Ariane mentioned that she struggles with this not because she’s intimidated by it, but because she’ll lose herself in the questions that only lead to more questions. While some of us are likely to draw the scope too conservatively, she might forget to draw it at all!</p><h3>Our role defines our scope.</h3><p>Manjari mentioned that she thought roles often set us up to think that certain things were beyond our influence. Obviously the best person to make a decision about technology would be the person with technology in their title.</p><p>Rather than allowing our role to define our curiosity, we should let it guide us to expertise. As designers, we can trust technologists to always have the best answer, or we can trust them to help us understand why the recommendation is right for the product. Asking a technologies why one answer is better than another, or what tradeoffs a solution makes, or what research was done in coming to their solution will almost always result in the designer having some knowledge that she didn’t have going into the project. Sometimes these questions might even lead to finding a better solution.</p><h3>Design programs have a lot of room for improvement.</h3><p>Designers considering technology outside of their scope is hardly uncommon, and so we began to ask, “What can universities do differently?” Our various backgrounds provided us with a variety of insights.</p><p>Kamila studied industrial design, and for every class had to build a product. She didn’t render a thing and then send it off to someone else to make as we often might in the digital world. Her program prepared her for this by giving her access to many different types of manufacturers where she could learn about working wood or metal or fabric.</p><p>Similarly, Natalia’s program forced her to print and cut and bind books. Working with a printshop to understand the constraints of their inks is not terribly unlike working with a developer to understand the constraints of a particular platform. But then for the digital classes, the program just required design files.</p><p>Ariane did a lot of research and wrote a lot of papers. She makes a face when she says this, wondering why they didn’t make more.</p><p>Manjari perhaps had the most relevant experience in that she would work within teams of different disciplines to create functioning prototypes.</p><p>My own school experience has led me to believe that working with someone a few years ahead of you is one of the best ways to learn. I was less intimidated to ask grad students for help than I was professors, and their recent experiences and failures were often valuable for my own understanding.</p><p>Did this conversation change anything for The Artificial? Absolutely. We’re less likely to accept technology solutions without understanding why they were made, and we’re more likely to ask questions so that we can fill out our own understanding.</p><p><em>Originally published at </em><a href="https://theartificial.com/blog/2018/02/12/designer-scope.html"><em>theartificial.com</em></a><em> on February 12, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b6a78431bf7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-artificial/artificial-conversations-technology-and-the-scope-of-design-6b6a78431bf7">Artificial Conversations: Technology and the Scope of Design</a> was originally published in <a href="https://medium.com/the-artificial">Artificial Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>