<?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 Quinn Keast on Medium]]></title>
        <description><![CDATA[Stories by Quinn Keast on Medium]]></description>
        <link>https://medium.com/@quinnkeast?source=rss-3e06b42dd370------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*SyzlUfDeqIYhiWErDAAR5A.png</url>
            <title>Stories by Quinn Keast on Medium</title>
            <link>https://medium.com/@quinnkeast?source=rss-3e06b42dd370------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 02:08:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@quinnkeast/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[The gesture and the instruction]]></title>
            <link>https://uxdesign.cc/the-gesture-and-the-instruction-4f90d5a6b8f5?source=rss-3e06b42dd370------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f90d5a6b8f5</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[editor-picks]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Quinn Keast]]></dc:creator>
            <pubDate>Wed, 10 Jun 2026 17:33:07 GMT</pubDate>
            <atom:updated>2026-06-11T21:45:36.627Z</atom:updated>
            <content:encoded><![CDATA[<h4>Making-feel, result-feel: Two kinds of design work, two kinds of tired</h4><figure><img alt="An abstract painting done with ink, with stark black gestural brushstrokes on a white canvas." src="https://cdn-images-1.medium.com/max/1024/0*cXjbS5U0TOQtdAWo.jpg" /><figcaption>Photo by <a href="https://unsplash.com/@heijnsbroek_abstract_art?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Fons Heijnsbroek</a> on <a href="https://unsplash.com/photos/abstract-black-and-white-ink-painting-with-bold-brushstrokes-DqC6LG7Epvg?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>My day-to-day <em>movements</em> have changed. I’m doing a lot of product design work with agent-based workflows, and I’m noticing more than anything that my body is moving differently in the act of design.</p><p>My career has been largely in canvas-based tools, creating and moving and manipulating visual and UI designs spatially. I’ve been a developer alongside my design praxis in some form or another since 2008, so when LLMs and agentic coding workflows really kicked off, it felt very natural to jump into those tools and do what I was already doing, faster.</p><p>But lately, the act of design has been tiring me out in a way that it didn’t before.</p><p>Every tool becomes an extension of the user’s body. The user develops a spatial relationship with each tool.¹ In design school, we learned how to use pencils, pens, brushes, knives, and a whole bunch of materials and mediums before we were allowed to touch a computer. Mastery of one tool carries forward into other tools, but every tool has its own shape and movements that must be learned.</p><p>When a tool is an extension of the body and mind, you’re the actor applying the tool to achieve, near unconsciously, what the body and mind intend.</p><p>There’s a feedback loop where information comes back through your hands as you work and direct and change the course of creation. Schön describes this as “a conversation with the materials of a situation.”²</p><p>It’s established that people think differently when writing by hand versus when they’re typing. Handwriting recruits a broader network of motor, sensory, and cognitive processes, while typing engages less and leaves you more passively cognitively engaged.³ And note that typing is still direct, in that you type the words you mean. Prompting is another step removed, closer to dictating to someone who paraphrases you. If handwriting to typing already costs something, then the prompt takes that one step further.</p><p>As a designer iterating madly in a canvas-based tool, the way I engage with the canvas affects how, and how deeply, I engage with a problem.</p><p>When the things you’re designing are themselves spatial — relationships of hierarchy and attention and movement — manipulating those things spatially is engaging with the problem directly, such that the moving <em>is</em> the thinking.⁴</p><p>But when the tool is an agent, the agent introduces a layer of abstraction between your body and mind, and the design; you aren’t directly making your mark on the design, but rather, you’re providing verbal instructions as to how to do so.</p><p>Big tool shifts have happened before, from the graphic designer’s drawing board to Photoshop, from hand-drafting to AutoCAD, even from Sketch to Figma. Each meant reskilling and churn and fatigue. You might argue these already introduced abstraction; the mouse is an abstraction of the pencil. But each still stayed continuous with the hand: I move, the proxy follows, and feedback still came through.⁵ The making-feel carried through each of these shifts, because the channel was still gesture.</p><p>The agent is the first shift that moves the making out of gesture and into language. I no longer manipulate a proxy whose movements mirror my own; I describe an outcome, and hand off the specifics to a system that decides them. The change is from gesture to instruction. It’s not another kind of canvas or another kind of pencil, but rather handing the pencil to an assistant and describing what you want the pencil to do.</p><p>The act of prompting forces you to articulate into language what the hand knew without speaking — and, as Polanyi observed, “we know more than we can tell,” so that articulation is always incomplete.⁶</p><p>This isn’t inherently good or bad. The agent lets me build complex interactive prototypes I can feel out, in the lived outcome, in a way that a static mockup or Figma prototype simply can’t. It brings me closer to the result and what it’s actually like to use. Call that the result-feel, against the making-feel I’d always felt working in the canvas.</p><p>Making-feel is generative, where the thinking happens in the producing. Result-feel is evaluative, where I react to the result and how it feels to use. It’s no less engaged, but it’s a different type of engagement.</p><p>The agent is right for workflows that serve the result-feel. Spatial design workflows better serve the making-feel. They’re different layers for different problems.</p><p>When you hand off the pencil, the agent takes the making-feel. You stop feeling the result through your own hands as you make it, and the thinking that the canvas used to draw out automatically becomes something you have to articulate and supply on purpose. When you hold the pencil, the directness forces engagement. The feedback comes back through your hands, and you can’t not do the thinking. That friction <em>was</em> the thinking.</p><p>When I’m tired from using spatial design tools, I’m flow-tired, from my mind, body, and problem working in one loop. What I’m feeling right now is depleted-tired, where that loop is broken, and instead of engaging physically with the act of making, I’m translating. It’s a different kind of moving, a different kind of making, and a different kind of thinking.</p><p>There’s two questions in my tiredness, and they have different answers.</p><p>If it’s a mismatch, in reaching for the agent when the problem wanted the canvas, will that fade, as I learn which problems belong to which layer, and prompting becomes a more well-worn tool?</p><p>Or is it a permanent cost, the tax that comes of translating tacit knowing into explicit instruction, of forcing what the hand knew into spoken words, every time, even when the agent is the right tool? That cost wouldn’t fade with skill, because it’s inherent to the tool itself.</p><p>I think it’s both — and it’s the latter that I keep thinking about.</p><ol><li><em>Evidence shows that tool use remaps the neural representations of body shape and reach, effectively incorporating the tool into the body schema. </em><br> Maravita, A., &amp; Iriki, A. (2004). Tools for the body (schema). <em>Trends in Cognitive Sciences</em>, 8(2), 79–86. <a href="https://doi.org/10.1016/j.tics.2003.12.008">https://doi.org/10.1016/j.tics.2003.12.008</a></li><li>Schön, D. A. (1983). <em>The reflective practitioner: How professionals think in action</em>. Basic Books.</li><li>Marano, G., Kotzalidis, G. D., Lisci, F. M., Anesini, M. B., Rossi, S., Barbonetti, S., Cangini, A., Ronsisvalle, A., Artuso, L., Falsini, C., Caso, R., Mandracchia, G., Brisi, C., Traversi, G., Mazza, O., Pola, R., Sani, G., Mercuri, E. M., Gaetani, E., &amp; Mazza, M. (2025). The Neuroscience Behind Writing: Handwriting vs. Typing — Who Wins the Battle? <em>Life</em>, 15(3), 345. <a href="https://doi.org/10.3390/life15030345">https://doi.org/10.3390/life15030345</a></li><li><em>The idea that manipulation itself is the thing is an aspect of the extended-mind thesis: that cognition can extend out through the body and the medium it works in.</em><br>Clark, A., &amp; Chalmers, D. (1998). <em>The extended mind</em>. Analysis, 58(1), 7–19.</li><li><em>The sense of acting on the work itself through a proxy that mirrors your movements is described by Hutchins, Hollan &amp; Normal as directness, decomposed into distance (how far intention sits from the system’s actions) and engagement (the feeling of operating on the objects rather than describing them).</em><br>Hutchins, E. L., Hollan, J. D., &amp; Norman, D. A. (1985). Direct manipulation interfaces. <em>Human–Computer Interaction</em>, 1(4), 311–338. <a href="https://doi.org/10.1207/s15327051hci0104_2">https://doi.org/10.1207/s15327051hci0104_2</a></li><li>Polanyi, M. (2009). <em>The tacit dimension</em>. University of Chicago Press. (Original work published 1966)</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f90d5a6b8f5" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/the-gesture-and-the-instruction-4f90d5a6b8f5">The gesture and the instruction</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[AI: Seasoning, not the main course]]></title>
            <link>https://uxdesign.cc/ai-seasoning-not-the-main-course-8788a9f577d8?source=rss-3e06b42dd370------2</link>
            <guid isPermaLink="false">https://medium.com/p/8788a9f577d8</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[future]]></category>
            <dc:creator><![CDATA[Quinn Keast]]></dc:creator>
            <pubDate>Wed, 13 Sep 2023 12:44:57 GMT</pubDate>
            <atom:updated>2023-09-14T00:26:32.623Z</atom:updated>
            <content:encoded><![CDATA[<h4>The best applications of AI will be hyper-contextual and invisible</h4><figure><img alt="Magical sparkling stars on a black background" src="https://cdn-images-1.medium.com/max/1024/1*4RcpVCm-nzgvEfMhKUtB0A.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@billy_huy?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Billy Huynh</a> on <a href="https://unsplash.com/photos/W8KTS-mhFUE?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I have come to believe that AI usually isn’t magic, it’s obfuscation.</p><p>My hypothesis is that the best applications of AI will be those that are hyper-contextual and invisible.</p><p>Few products will succeed by virtue of being “AI-first,” “AI-driven,” “AI-${adjective}”. Instead, AI should be used like seasoning that brings out the flavours: to accentuate an underlying, tangible, and sensible system.</p><p>Several folks have discussed how <a href="https://www.geoffreylitt.com/2023/03/25/llm-end-user-programming.html#chat-is-an-essentially-limited-interaction">chatbots are the wrong interaction paradigm</a> for <a href="https://stream.thesephist.com/updates/1668617521">almost every product</a> for a variety of very good reasons. I think the conversational analogy was wildly successful for OpenAI and others, and ultimately contagious, because of two factors: first, the chatbot pattern is self-contained and has an immediate feedback loop. Second, it showcased the “magic” to the world beyond tech folks through a very familiar conceptual model that made it easy to <em>play</em> — to use AI for the sake of using AI.</p><p>Many products in this initial rush to experiment with AI responded by created their own chatbot equivalents in their own product (or by invisibly replacing humans in existing chat surfaces, which is its own topic). But the goal of using these products is not to use AI for the sake of using AI.</p><p>Squishing in a chatbot or other feature that positions its identity around its inherent AI-ness doesn’t make for a great product or tool. It’s a layer of obfuscation in front of your tool. And, particularly if your product provides any kind of productivity outcomes, it explicitly de-tool-ifies your tool.</p><p>Then it isn’t a tool — it’s a novelty.</p><p>Instead, we should think of AI as an underlying technology that makes existing or new products <em>better at what they already do</em>.</p><p>Users should not have to care that the product uses AI. They should care that, in the context of whatever they’re trying to do, they can now do it faster and better, and in some way, they get value out of it that they couldn’t before.</p><p>The real magic is found in hyper-contextual, invisible applications of AI that enhance great tools.</p><p>—</p><p><em>Originally published at </em><a href="https://quinnkeast.com/writing/ai-is-seasoning"><em>quinnkeast.com/writing/ai-is-seasoning</em></a>.</p><p><a href="https://quinnkeast.com/">Quinn Keast</a> is a partner &amp; designer at <a href="https://caribou.co/">Caribou</a>, and also a product designer at <a href="https://airplane.dev/">Airplane</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8788a9f577d8" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/ai-seasoning-not-the-main-course-8788a9f577d8">AI: Seasoning, not the main course</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[Perceived effort: Cycling, work, and the power of momentum]]></title>
            <link>https://quinnkeast.medium.com/perceived-effort-cycling-work-and-the-power-of-momentum-11ba57d78184?source=rss-3e06b42dd370------2</link>
            <guid isPermaLink="false">https://medium.com/p/11ba57d78184</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[team]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Quinn Keast]]></dc:creator>
            <pubDate>Fri, 23 Jun 2023 09:28:43 GMT</pubDate>
            <atom:updated>2023-06-23T09:28:43.900Z</atom:updated>
            <content:encoded><![CDATA[<h4>Cycling into the wind is hard</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-NTL8ifNB541vTl8.jpg" /><figcaption>Photo by <a href="https://unsplash.com/@xokvictor?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Viktor Bystrov</a> on <a href="https://unsplash.com/s/photos/tempelhof-cycling?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I’ve been cycling a lot lately. Cycling’s got it all for people like me who like data and kit and bits and pieces: you’ve got your bike, you’ve got your computer, and it all orchestrates together to feed you a real-time stream of your speed, cadence, and power.</p><p>There’s a big field in southern Berlin called Tempelhofer Feld. It’s an old airport, abandoned after the fall of the Berlin wall, but the fields, runways, and curtains remain, reclaimed as a huge public space. It makes for a great cycling circuit: smooth tarmac for an almost 5km loop, and not a car in sight.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TLASRSkoCM15VPcH.jpg" /><figcaption>Google map of Tempelhofer Feld from above. Look how huge it is.</figcaption></figure><p>It’s also windy. It’s relentless.</p><p>Going in one direction, the wind at my back, it’s a blast. I watch my computer as I crank up to more than 45km/hour, nailing the cadence, and can’t resist dropping another gear to push my power ever higher. I’m within a gasp of 50km/hour with nothing but the lycra on my back.</p><p>Then I turn the corner and into the wind. Even though I’m exerting the exact same amount of effort, as measured by my power, my speed plummets. I’m lucky to hit 20km/hour.</p><p>It has an immediate psychological impact. With the wind at my back, I could see and feel the result of my effort. My speed, the feeling of the world whipping by, feeds into my energy, making it easier to keep pushing myself hard. But cycling into the wind, putting out the exact same effort, it becomes harder and harder to maintain my output.</p><p>I feel so <em>slow</em>.</p><p>It’s a feedback loop. The faster I felt, the easier it felt to keep pushing. The slower I felt, the harder it was to stay motivated.</p><p>I feel this same principle in my work, too. When I can see and feel the results of my effort, it’s easier to dig in. It’s easier to keep pushing. That’s the wind at my back.</p><p>But when the results of the work isn’t as visible or immediate, it can feel frustrating. This often happens when tackling more complex problems that take a lot of time and effort to solve. It can feel like pedaling into the wind — we’re putting in the same amount of energy but don’t feel like we’re getting anywhere. And that makes it harder and harder to keep going.</p><p>Knowing that this feedback loop exists, one approach is to create conditions for visible momentum and outcomes from the work we’re doing. For designers and product teams, this might mean setting shorter-term goals, looking for Minimum Lovable Product iterations, and focusing on rapid learning. All these things create that sense of forward motion and the positive feedback cycle.</p><p>It’s not always practical or possible for everything to be visibly awesome. Some things are Hard Problems. Some things take time and hard work without much visible progress until the critical breakthrough. This takes discipline. Putting in the effort, even when it doesn’t feel like it’s paying off.</p><p>But a cyclist who only rides into the wind can’t push through on discipline alone. They need a vision — something to aim for. It might be the triathlon they’re training for, or the promise of the Biergarten at the end of the ride. The same goes for our work: we need a clear vision of what we’re working towards and how this stretch against the wind is going to get us there.</p><p>And then there’s the team. In cycling, just as in work, riding into the wind is a different experience when you’re riding in a group. Grinding into the wind together (and griping about it after) can give back motivation the wind saps away.</p><p>This vision, the team around you, your own discipline, and those wonderful moments when you turn the corner and the wind’s at your back, are what get us through.</p><p><em>(Don’t forget the crosswinds. No matter how hard you push when cycling into the wind, crosswinds blowing wildly from unexpected directions are dangerous. For a cyclist, it can mean a crash, or at the very least, cutting the ride short. But in your work, it can lead to burnout or looking for new opportunities.)</em></p><p>—</p><p><em>Originally published at </em><a href="https://quinnkeast.com/writing/cycling-feedback-loops"><em>quinnkeast.com/writing/cycling-feedback-loops</em></a><em>.</em></p><p><a href="https://quinnkeast.com/">Quinn Keast</a> is a partner &amp; designer at <a href="https://caribou.co/">Caribou</a>, and also product designer at <a href="https://airplane.dev/">Airplane</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11ba57d78184" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design syntropy]]></title>
            <link>https://uxdesign.cc/design-syntropy-334080295f47?source=rss-3e06b42dd370------2</link>
            <guid isPermaLink="false">https://medium.com/p/334080295f47</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ideas]]></category>
            <category><![CDATA[design-syntropy]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Quinn Keast]]></dc:creator>
            <pubDate>Fri, 23 Jun 2023 09:25:14 GMT</pubDate>
            <atom:updated>2023-06-26T10:28:34.872Z</atom:updated>
            <content:encoded><![CDATA[<h4>A concept embracing the evolving nature of design work and the unique roles of design artifacts and design systems</h4><figure><img alt="A macro-like, abstract photo of cellular shapes almost like bubbles in the ocean." src="https://cdn-images-1.medium.com/max/1024/1*98-VwiJJ6TLMTKmVNKzmlw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@0asa?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Vincent Botta</a> on <a href="https://unsplash.com/photos/84PTCoyzRBA?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>There’s a concept that I’ve come to refer to as “design syntropy.” It’s related to the creation and use of design artifacts — all those things we create as designers and product managers and engineers as we shape a product or concept.</p><p>Most design artifacts are temporary sources of truth. They help guide our thinking, collaboration, and decisions while a project is underway. But their “truthfulness” has a short shelf life.</p><p>I’ve often wondered and have been asked which design artifact is the “source of truth” for something in a product, and honestly, I don’t think that’s a realistic or even desirable goal.</p><p>I think design has a quality of syntropy, an antonym to entropy. Unlike entropy, which suggests a natural decline into chaos and disorder, syntropy represents the idea of order, evolution, and the ability to bring together ever-increasing complexity to create something new.</p><p>In product design, our work creates ripple effects, influencing areas of the product that we might not have directly touched. This is design syntropy. A design artifact left untouched doesn’t descend into chaos, but it may slowly drift out of alignment with the reality of the product, while the thing it represents evolves on its own, indirectly influenced by changes elsewhere in the product.</p><p>Design artifacts represent a source of truth only in a moment of time.</p><p>This isn’t a problem to solve, nor a flaw to correct — it’s just the nature of design work. Design artifacts are a record of a project’s journey, showing us the thought processes, tradeoffs, and context of decisions. Great design artifacts multiply collaborative impact across a team and help to build momentum. Ultimately, they’re a form of documentation — and in that capacity, that’s why even simple sketches and breadboards convey immense value.</p><p>In the long run, the real source of truth is the design system. A good design system is enduring even as different projects come and go. The design system needs to stay aligned with the product, and it needs active maintenance, documentation, and champions.</p><p>I don’t like the idea of design artifacts automatically updating to mirror changes in the design system. This might sound appealing on paper, but in practice, it tends to break the value of the artifact as a record of the project’s context and history.</p><p>Design syntropy as a concept embraces the evolving nature of design work and the unique roles of design artifacts and design systems.</p><p>—</p><p><em>Originally published at </em><a href="https://quinnkeast.com/writing/design-syntropy"><em>quinnkeast.com/writing/design-syntropy</em></a>.</p><p><a href="https://quinnkeast.com/">Quinn Keast</a> is a partner &amp; designer at <a href="https://caribou.co/">Caribou</a>, and also product designer at <a href="https://airplane.dev/">Airplane</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=334080295f47" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/design-syntropy-334080295f47">Design syntropy</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[The language of collaboration (and the phrase that gives you superpowers)]]></title>
            <link>https://uxdesign.cc/the-language-of-collaboration-and-the-phrase-that-gives-you-superpowers-6686ddfc4594?source=rss-3e06b42dd370------2</link>
            <guid isPermaLink="false">https://medium.com/p/6686ddfc4594</guid>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[collaboration]]></category>
            <dc:creator><![CDATA[Quinn Keast]]></dc:creator>
            <pubDate>Sun, 07 Nov 2021 10:52:51 GMT</pubDate>
            <atom:updated>2021-11-07T11:21:49.401Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to create great collaborative environments</h4><figure><img alt="Wall of unlegible sticky notes." src="https://cdn-images-1.medium.com/max/1024/1*XaWOc7w9905k7MQqUJ526w.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@patrickperkins">Patrick Perkins</a> | Unsplash</figcaption></figure><p>You have a superpower.</p><p>You can spark collaboration. You can create inclusion. And you can do it with just a few words.</p><p>For the last two years, I’ve been working remotely and asynchronously. When your team works asynchronously, artifacts are everywhere: written docs, design documentation, pre-recorded videos, pull requests, and every flavour of digital canvas you can think of.</p><p>But artifacts don’t drive collaboration. You do.</p><p>All communication involves a sender and a receiver. Sometimes there’s more than one receiver. It’s the sender’s job to be understood — not the receiver’s job to understand. Whenever you’re driving collaborating with others, you’re the sender. As the sender, you create and shape the collaborative space. And the language of collaboration **builds trust and creates space** for others.</p><p>The same sentence can be phrased in two ways: subjectively, or factually.</p><p>Put subjectively: <em>“I think this is a good choice.”</em></p><p>Put factually: <em>“This is a good choice.”</em></p><p>Each approach creates a different collaborative context.</p><p>The subjective statement is presented as an opinion. This invites collaboration. Opinions can be explored, challenged, and changed.</p><p>The factual statement is presented as, well, fact. This shuts down collaboration. Taking a contrary position to a fact is a different dynamic from taking a contrary position to an opinion.</p><p>The <em>intended</em> meaning might be “(I think) this is a good choice.” But leaving it unsaid and implicit puts responsibility on the <em>receiver</em> to understand it correctly. And when working asynchronously — and with collaborators with different cultural backgrounds, languages, or physical or mental abilities — this leads to misunderstandings, tensions, and exclusion.</p><p>Instead, use phrases like:</p><ul><li>“I think that…”</li><li>“I feel that…”</li><li>“To me, this feels…”</li><li>“I’m not sure…”</li><li>“I’m worried that…”</li></ul><p>Consider these two quotes:</p><ol><li>“In Q1, 10% of our customers used this feature. 23 customers shared feedback saying they found it hard to get started. The onboarding is confusing. When I look at Competitor’s version of this feature, they do a lot more than we do to create learning moments. We need to do the same.”</li><li>“In Q1, 10% of our customers used this feature. 23 customers shared feedback saying they found it hard to get started. I think the onboarding is confusing. When I look at Competitor’s version of this feature, I feel that they do a lot more than we do to create learning moments. I think we should explore doing the same.”</li></ol><p>The first quote states a set of facts:</p><ul><li>10% of customers used this feature in Q1</li><li>23 customers found it hard to get started</li><li>The onboarding is confusing</li><li>Competitor does more to create learning moments in their parallel feature</li><li>We need to create more learning moments in the onboarding</li></ul><p>The second quote separates fact from opinion:</p><ul><li>10% of customers used this feature in Q1</li><li>23 customers found it hard to get started</li><li><strong>I feel</strong> Competitor does more to create learning moments in their parallel feature</li><li><strong>I think</strong> the onboarding is confusing</li><li><strong>I think</strong> we should explore creating more learning moments in the onboarding</li></ul><p>The first quote creates a <strong>constrained collaborative space</strong>. It’s prescriptive, and implicitly shuts down contrary viewpoints. If any of the collaborators disagree with the proposed action (“create learning moments in the onboarding like Competitor does”), then they have to push back and argue their case from a factual basis.</p><p>The latter creates a <strong>starting point for collaboration</strong>. It sets out a factual basis from which opinion follows, and frames opinions as a personal interpretation to be explored, built on, or challenged altogether. Someone might suggest, “Perhaps it’s not the onboarding at fault, but instead the information architecture underlying the feature?” Or they might respond that, “What Competitor is doing feels to me like a solution for a different problem than what we’re trying to solve.”</p><p>Boom. Collaboration everyone can feel good about.</p><p>A tricky thing is that every discipline — design, engineering, finance — has its own best practices and rules of thumb. As a group, a discipline may share a factual understanding of these things. But outside the group, these things may not be known or understood to be best practices or rules of thumb at all, which means that something stated factually, may be interpreted by someone outside of the group as “a subjective opinion, stated factually.”</p><p>This sets up the collaborative environment for tension as each collaborator misunderstands and questions the next. If someone states one opinion as a fact, how are others to know that these other things stated as facts are actually facts, and not opinions framed as facts to influence the collaborative context in their favour?</p><p>Sometimes, this means looking back at your own work for those decisions that you know are based on a best practice, but might be seen as subjective to those who aren’t familiar with those same best practices. In product design, we make a lot of implicit decisions based on things like gestalt theory, attention, and much more. Surfacing these moments with concrete rationales helps to make these implicit decisions explicit.</p><p>Over time, this builds trust.</p><p>Note that with trust comes shortcuts. The more trust a group has established, the more shortcuts they will take in their language around collaboration. But whenever the group changes in some way, whether that’s a new team member, or a new project space, or whenever the group is collaborating with others outside the group, it’s critical to use the language of collaboration to keep a positive collaborative environment.</p><p>Some of the biggest barriers to collaboration is the feeling that one’s contribution isn’t meaningful, that feedback isn’t sought, or that one isn’t empowered to contribute.</p><p>You can create space for collaboration with just one phrase:</p><blockquote>“What do you think?”</blockquote><p>This phrase marks the moment as a starting point for collaboration. It’s an invitation. It’s an assurance that feedback is valued and wanted.</p><p>“What do you think?” is a superpower.</p><p><a href="https://quinnkeast.com/?source=post_page---------------------------"><em>Quinn Keast</em></a><em> is a partner &amp; designer at </em><a href="https://caribou.co/"><em>Caribou</em></a>, <em>and also product designer at </em><a href="https://sourcegraph.com/"><em>Sourcegraph</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6686ddfc4594" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/the-language-of-collaboration-and-the-phrase-that-gives-you-superpowers-6686ddfc4594">The language of collaboration (and the phrase that gives you superpowers)</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[Email addresses are a pain in the ass]]></title>
            <link>https://quinnkeast.medium.com/email-addresses-are-a-pain-in-the-ass-35bcd0170b6d?source=rss-3e06b42dd370------2</link>
            <guid isPermaLink="false">https://medium.com/p/35bcd0170b6d</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Quinn Keast]]></dc:creator>
            <pubDate>Fri, 30 Apr 2021 12:56:23 GMT</pubDate>
            <atom:updated>2021-04-30T12:56:23.196Z</atom:updated>
            <content:encoded><![CDATA[<p>Personal email addresses are weird and a pain in the ass.</p><p>I used a raw gmail address for years for my personal email, while keeping my professional consulting work separate using our consultancy’s domain. Hey excited me not only because of their opinionated manifesto about email, but because the idea of having a @hey.com email address for my personal email was super tantilizing.</p><p>Email addresses inherently mark a person as belonging to whatever the domain happens to be. Have an @gmail.com address? You’re a gmail user. Have a @aol.com address? You’re about twenty years behind the times. @hey.com was neat: it didn’t feel like it represented a product or service. It was almost like an independent concept. Hey! Personal email!</p><p>But this whole implied <em>belongingness</em> of email addresses is a pain in the ass because when your @whatever is tied up with a specific provider, <em>you</em> are tied up to that specific provider. So when Basecamp releases a new opinionated manifesto about things that have already been covered in great detail on Twitter and are fundamentally at odds with my own values and expectations, it means that I’m left with the question of “Do I want to continue to demonstrate my <em>belongingness</em> to the values represented by my personal email address?”</p><p>I already changed my personal email address everywhere once. Doing it again is gonna be a huge pain in the ass.</p><p>Which reinforces that I<em> really should</em> just have a personal email address that’s my own, independent from any given email provider, so that I can change providers at any time and absolutely nobody cares and I don’t have to go through this whole pain in the ass.</p><p>The brilliant thing is email lets you do this. Anyone can take a domain they own and give themselves an email address, and suddenly, who gives a hoot who’s actually <em>providing</em> it?</p><p>But boy, email addresses, by which I mean <em>domain names for email addresses</em>, are a gigantic pain in the ass.</p><p>I already don’t use my professional email as my personal email. I have my own domain for my personal slash professional life, quinnkeast.com, but it’s super weird to use as an email address.</p><p>See, email addresses have a built-in affordance for the whole idea of <strong>person</strong> at whatsit dot whatever.</p><p>Let’s say I use my personal domain for my personal email address. quinn@quinnkeast.com is accurate but also feels very strange. hey@quinnkeast.com, hello@quinnkeast.com, et cetera aren’t <em>bad</em> but they’re <em>weird</em>, like you’re sending a note to a robot or a form or something instead of the <strong>person</strong> at whatsit dot whatever.</p><p>So let’s instead suppose I want to get a whole fresh new domain specifically to use for my personal email. Well, that’s a pain in the ass too.</p><p>There’s pretty much no domains available for any kind of sensible TLD. And the new generic TLDs are fun to think about, like quinn@enormous.pizza, but the vast majority of these TLDs don’t afford whatsoever that they make up a domain. I gotta write this email out by hand on forms and stuff and in other languages — not just on the web — and I gotta feel confident people always, 100% of the time, know that my email address is quinn@enormous.pizza and not assume it’s <em>just a bad joke</em> and it’s actually quinn@enormous.com or quinn@enormous.pizza.com. I don’t need that kind of stress and second-guessing about why I haven’t received important emails from whatever important paper-driven specialist professional I’m waiting to hear back from.</p><p>And even if I do find a good .com domain and set myself up with a personal email address like quinn@enormous.com, well, then I have to deal with the pain in the ass of implying that I belong to or represent a company called Enormous, and it ultimately just doesn’t <em>feel</em> like a personal email address.</p><p>I don’t really have a solution to this. I don’t think there’s a product opportunity here, frankly, because the vast majority of users fundamentally don’t really care what their email’s domain is. Maybe I care too much about what my email address is.</p><p>And yet — like it or not — my personal email address represents me, as a person, and I wish it wasn’t such a pain in the ass.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35bcd0170b6d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[These are Design Principles for real-time captions in video calls]]></title>
            <link>https://uxdesign.cc/these-are-design-principles-for-real-time-captions-in-video-calls-325b8906767e?source=rss-3e06b42dd370------2</link>
            <guid isPermaLink="false">https://medium.com/p/325b8906767e</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[remote-work]]></category>
            <category><![CDATA[t]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Quinn Keast]]></dc:creator>
            <pubDate>Sun, 03 May 2020 10:50:14 GMT</pubDate>
            <atom:updated>2020-05-09T13:21:49.975Z</atom:updated>
            <content:encoded><![CDATA[<h4>Here’s a set of design principles for creating usable and inclusive real-time captions in video calling platforms.</h4><figure><img alt="An active video call session underway with many participants, but no captions." src="https://cdn-images-1.medium.com/max/1024/1*RyLECd5dvXoDuPSeTd2uqA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@charlesdeluvio?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Charles Deluvio</a> on <a href="https://unsplash.com/t/work-from-home?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Over the last few months, workplace conversation and communication has adapted to the rise in remote work by shifting largely to some form of video calling. For people living with hearing loss, video calls are broadly inaccessible and exclusive. But we’re at a threshold where the technology exists to make these tools accessible to everyone. <a href="https://meet.google.com/">Google Meet</a> now has real-time captions. Other real-time speech-to-text tools like <a href="https://otter.ai/">Otter</a> are flourishing.</p><p>The challenge: real-time <a href="https://uxdesign.cc/captions-in-video-calls-better-accessibility-but-harmful-side-effects-625d416f81af">captioning in video calls is a new problem space with its own risks, challenges, and opportunities</a>. If we get it right, we’ll create more accessible and inclusive platforms and workplaces. If we get it wrong, we can create frustration, stigma, and lasting social and professional damage. That’s why we need clear and considered design principles to guide our efforts.</p><p><strong>These are design principles I’ve identified that I believe any implementation of real-time captioning in video calling should adhere to.</strong> These principles together provide a positive, usable, and inclusive experience for participants who rely on captions for accessibility.</p><h3>Design Principles for Real-Time Captions in Video Calling Platforms</h3><ol><li><strong>Captions for video calling are their own medium with their own challenges.</strong> <br>The purpose and context that surrounds video calling is very different from watching television or movies. Treat captions for video calls as a unique challenge with its own context, constraints, and opportunities.</li><li><strong>Captions are content. Everything else is context.<br></strong> A video call still works if someone’s video is turned off because the audio is the content. Captions are the direct alternative to audio for those who rely on captions. This means captions should be prioritized over all else for people relying on captions. Captions should never be hidden or obscured.</li><li><strong>Protect the equality of all participants.<br></strong> The act of using captions must not distinguish an individual from other conversational partners, such as by the direction of their gaze in relation to the screen and the subsequent perception of eye contact. Someone relying on captions should be indistinguishable from someone relying on audio.</li><li><strong>Don’t single out the use of captions.<br></strong>When joining a video call, all participants are aware that they are sharing their audio and video with other participants. Each participant can choose to share or not share their audio and video. People relying on captions should not be singled out as using captions, as captions aren’t recordings: they’re an alternate form of audio that other participants choose to share.</li><li><strong>Caption preferences must be equal to video and audio preferences.<br></strong> Never put people in a position where they have gaps in accessibility. Give people control over enabling captions before they enter a conversation, and expose caption preferences alongside video and audio preferences both inside and outside an active call. And respect their choices: if someone chooses to use captions, remember that choice for the next call.</li><li><strong>Prioritize something over nothing.<br></strong>Humans are incredible at using context to derive meaning. Machine learning has a long way to go. That’s why we should prioritize something over nothing. If the speech-to-text engine isn’t confident in a specific transcription and is likely to make adjustments with further context, deliver it anyway with confidence indicators and make corrections as they become available.</li><li><strong>Protect the integrity of conversation.</strong> <br>Don’t change what was spoken for the sake of brevity. Filler words like “um” and “uh” are a natural and functional part of conversations. Real-time captions for video calls aren’t transcriptions and meet different needs.</li><li><strong>Provide extra context when possible.<br></strong>People who rely on audio in video calls can identify who is talking, their emotional tone, and easily detect their own name among noise. Find ways to provide this context that people relying on captions may be missing.</li><li><strong>Provide constant and clear feedback about what’s happening.<br></strong> A real-time speech-to-text system is an inherent black box. That’s why there needs to be constant feedback about what the system is doing: whether it’s actively taking in audio, whether it’s processing audio, and whether it’s lagging or in real-time. Knowing that the system was aware something was said, but that it couldn’t transcribe it, is useful information that can provide context that humans can use to derive useful meaning.</li><li><strong>Proactively provide feedback to all conversational partners when captions are slow or failing to work.<br></strong> Don’t make it the user’s responsibility to interrupt and inform others when the captions aren’t working. Provide feedback to all participants and allow everyone to contribute to creating an inclusive environment.</li><li><strong>Provide fallbacks for all users when captions experience a failure.<br></strong>Text-based messaging places all participants on equal ground when captions experience failures such as network or processing errors. Make sure text-based messaging is available and usable to all participants.</li><li><strong>Provide access to the complete conversation.<br></strong> People who use audio in video calls can look away, dismiss a random notification, or close a window without losing track of the conversation. People relying on captions must have this same flexibility. Requiring constant and undivided visual attention to avoid missing content is unfair for people that rely on captions. In practice, this means giving people who use captions the ability to go back and see what they missed.</li><li><strong>Protect privacy in ongoing conversations.<br></strong> When someone joins a video call already underway, they don’t have access to what was already said unless the call was recorded. The same should apply for captioning. People should only have access to the caption history from the point when they joined the conversation.</li><li><strong>Prioritize offline processing, and clearly explain how privacy is protected during processing.<br></strong> Give all participants information and assurance around how audio is processed and converted into text and what privacy implications exist as a result. Encryption and data concerns should apply equally to captions as to audio and video processing and streaming.</li><li><strong>Design captions for readability.<br></strong> Treat captions as text content and design for readability using design heuristics. The beginning of each line should have a fixed location that lets users predictably direct their gaze, with sensible defaults for line length (about 45–75 characters) and line height (about 140%). Text should automatically scroll at the end of each line.</li><li><strong>Captions must be accessible in themselves.<br></strong> Like any other text content, people must have control over the size, colour, and font choice used for captions. Some people may have difficulty reading smaller text, while others may rely on specific font choices. Use sensible defaults that meet accessibility guidelines, but provide individual control and choice.</li><li><strong>Captions must be movable and adjustable.<br></strong> People relying on captions may need to relocate the caption element to meet specific individual needs that we may not be able to predict. Provide a sensible, well-designed default, but provide the ability to pop-out, move, and adjust the caption element according to individual needs.</li></ol><h3>Living Principles</h3><p>These principles represent my own perspective on how to design inclusive real-time captioning for video calls. As we collectively explore this problem space, I fully expect these principles will need to be adjusted and expanded in response to new insights and opportunities.</p><p>I’m publishing these principles on <a href="https://github.com/quinnkeast/design-principles-for-realtime-captions">Github</a> under an MIT license, with the idea that these principles represent a foundation that we can build on together.</p><p><strong>Contribute on Github:</strong> <a href="https://github.com/quinnkeast/design-principles-for-realtime-captions">https://github.com/quinnkeast/design-principles-for-realtime-captions</a></p><p><strong>Read also:</strong> <a href="https://uxdesign.cc/captions-in-video-calls-better-accessibility-but-harmful-side-effects-625d416f81af">Captions in Video Calls: Better Accessibility, but Harmful Side Effects</a></p><p><strong>If you are working on this problem space, I want to join you. </strong><a href="/service/mailto:hello@quinnkeast.com"><strong>Let’s have a conversation</strong></a><strong>.</strong></p><p><a href="https://quinnkeast.com/"><em>Quinn Keast</em></a><em> is a UX Designer + Partner at </em><a href="https://caribou.co/"><em>Caribou</em></a><em>, a user experience strategy and design consultancy.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=325b8906767e" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/these-are-design-principles-for-real-time-captions-in-video-calls-325b8906767e">These are Design Principles for real-time captions in video calls</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[Captions in video calls: better accessibility, but harmful side effects]]></title>
            <link>https://uxdesign.cc/captions-in-video-calls-better-accessibility-but-harmful-side-effects-625d416f81af?source=rss-3e06b42dd370------2</link>
            <guid isPermaLink="false">https://medium.com/p/625d416f81af</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[remote-work]]></category>
            <dc:creator><![CDATA[Quinn Keast]]></dc:creator>
            <pubDate>Sat, 02 May 2020 13:51:07 GMT</pubDate>
            <atom:updated>2020-05-03T11:48:23.959Z</atom:updated>
            <content:encoded><![CDATA[<h4>Google Meet’s captions represent accessibility possibility, but are fundamentally flawed by an ethical design problem.</h4><figure><img alt="A photo of a Macbook with the author in a Google Meet call on the screen. Macbook is next to a dog on the table." src="https://cdn-images-1.medium.com/max/1024/1*dHxFMqrow6SaKfJEGrTYLA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@moob?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Ayla Verschueren</a> on <a href="https://unsplash.com/t/work-from-home?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>With the rise of remote work in the midst of a pandemic, my working world is more accessible than ever before. But I find myself more dependent than ever on one of the most inaccessible forms of communication: the video call.</p><p><a href="https://quinnkeast.com/readme#errata">I’m deaf as a post</a>. My hearing loss got worse throughout my childhood, which, as a side effect, helped me develop strong lip-reading skills. In practice, I can’t turn the sounds I hear into actual words that I can understand, so I rely on lip reading in conversations and meetings.</p><p>Early in my career, conversations took place over emails, instant messaging, or in person. These forms of communication worked well enough for my needs, and I was able to grow and thrive in my role.</p><p>I’ve been very fortunate over my career to work with companies with inclusive approaches to hiring and working. Some companies have been happy to hold remote interviews using instant text messaging or shift to in-person conversations. My teammates have defaulted to written communication and go out of their way to make sure our meeting environments include everyone. But these are situational adaptations for my specific needs and rely heavily on compassion and consideration from my team.</p><p>Over the last few months, workplace conversation and communication has shifted largely to some form of video calling. Even two years ago, this new reliance on video calls would have excluded me entirely from the working world and sidelined my growth and development. But the last couple of years brought exponential improvements in real-time speech-to-text.</p><p><a href="https://meet.google.com/">Google Meet</a> now has real-time captions. Other real-time speech-to-text tools like <a href="https://otter.ai/">Otter</a> are flourishing.</p><p>However, Google Meet’s approach to captions has a profound flaw: it’s designed to mimic captioning for movies and television — which has an insidious side effect that must be addressed.</p><h3>Video calling isn’t great for anyone</h3><p>The New York Times recently published an article titled “<a href="https://www.nytimes.com/2020/04/29/sunday-review/zoom-video-conference.html">Why Zoom is Terrible</a>,” which digs into the shortcomings inherent to video calling platforms that can leave us feeling <em>“isolated, anxious, and disconnected.”</em><br>Among other issues (I strongly recommend reading the article), it singles out the issue of eye contact:</p><blockquote>Video chats have also been shown to inhibit trust because we can’t look one another in the eye.</blockquote><p>The <a href="https://dl.acm.org/doi/abs/10.1145/1240624.1240846">original study</a> behind this statement concludes that <em>“… the use of systems that introduce spatial distortions negatively affect trust formation patterns.”</em></p><p>When captions are shown at the bottom of a window, the effect is magnified. While a viewer with typical hearing might be direct their gaze at their conversational partners (or themselves) around the middle of their screen, someone relying on the captions will be looking at the very bottom of the same screen.</p><p>This causes viewers to unconsciously perceive the person relying on captions as <em>“uninterested, shifty, haughty, servile, or guilty.”</em></p><p>Compare these two screenshots: in the first, gaze is directed at the conversational partner, just above the middle of the screen. In the second, gaze is directed at the captions, at the bottom of the screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v2NQnw_2kkKTl3RHeVc2oA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZRn5wlkSEm4OV9GZxBMoDw.jpeg" /><figcaption>Which of these conversational partners appears active, engaged, competent, and trustworthy? The effect is magnified in large group conversations, where it’s easier to see the odd-person-out who doesn’t appear to be paying attention.</figcaption></figure><p>This is a bigger issue than a design problem: it’s also an ethical design challenge.</p><h3>An ethical design challenge</h3><p>On one side, real-time speech-to-text like Google Meet’s implementation makes these calls accessible to those living with hearing loss (and with inclusive design principles in mind, a wide range of others with situational or temporary needs).</p><p>On the other side, the current design implementation may be causing unintentional and permanent social and career damage for those same individuals.</p><p>A solution that actively harms those it purports to help, intentionally or otherwise, is not an inclusive or ethical solution.</p><h3>What needs to be done</h3><p>Short-term, I call on Google Meet to revisit their approach to captioning immediately. At the very least, the way Google implements captions in the platform should put those relying on them for inclusion on equal ground with their conversation partners.</p><p>Meanwhile, if your company defaults to video calls, I call on you to challenge “why.” I believe it would be better for companies to switch to <em>any</em> form of written communication before leaning on video calls.</p><p>Not only would this create a more inclusive environment for those living with hearing loss, but it would also create a more positive working environment for everyone by collectively shifting away from synchronous, reactive communication and towards asynchronous, considered communication. <a href="https://basecamp.com/guides/how-we-communicate">(Basecamp’s guide to internal communication</a> is a model of inclusive communication foundations.)</p><p>While I have a hacked-together solution that is helping me address this issue, it’s hacky, unreliable, and expensive. Worst of all, it places my ability to <em>belong</em> into the hands of a private company that may not exist tomorrow.</p><p>That’s why, long-term, I believe we need system-wide, open-source, included-by-default solutions to real-time speech-to-text captioning. These solutions should be distinct from any specific application and designed from the bottom-up to deeply consider the human impact and side effects of the decisions we make in design.</p><p>We’re at a threshold where the technology exists to create a truly inclusive world for those living with hearing loss. Let’s do it together — and get the details right.</p><p><strong>🔔 Update:</strong> <a href="https://medium.com/@quinnkeast/these-are-design-principles-for-real-time-captions-in-video-calls-325b8906767e">These Are Design Principles for Real-Time Captions in Video Calls</a></p><p><strong>If you are working on this problem space, I want to join you. </strong><a href="/service/mailto:hello@quinnkeast.com"><strong>Let’s have a conversation</strong></a><strong>.</strong></p><p><a href="https://quinnkeast.com/"><em>Quinn Keast</em></a><em> is a UX Designer + Partner at </em><a href="https://caribou.co/"><em>Caribou</em></a><em>, a user experience strategy and design consultancy.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=625d416f81af" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/captions-in-video-calls-better-accessibility-but-harmful-side-effects-625d416f81af">Captions in video calls: better accessibility, but harmful side effects</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[We cancelled our user research because of the coronavirus]]></title>
            <link>https://uxdesign.cc/we-cancelled-our-user-research-because-of-the-coronavirus-f39b33c9cfdf?source=rss-3e06b42dd370------2</link>
            <guid isPermaLink="false">https://medium.com/p/f39b33c9cfdf</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[coronavirus]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ethics]]></category>
            <dc:creator><![CDATA[Quinn Keast]]></dc:creator>
            <pubDate>Thu, 12 Mar 2020 13:12:55 GMT</pubDate>
            <atom:updated>2020-03-19T20:24:26.858Z</atom:updated>
            <content:encoded><![CDATA[<h4>Here’s why, and why you might want to do the same.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ss_HNiC8_siHXp6oe3ozCA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@soroushkarimi?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Soroush Karimi</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p><strong>🚨 <em>Before you read this article:</em></strong></p><p><em>The COVID-19 pandemic evolved so quickly since I wrote this article, that I’d like to preface it with some additional context and to respond to some questions.</em></p><p><strong><em>Why did I write this article?</em></strong></p><p><em>We cancelled our research on Monday, March 9. I wrote this article on Wednesday, March 11 and published it in the morning on Thursday, March 12.</em></p><p><em>At the time of writing, the pandemic and global response was only beginning to pick up. The majority of companies had not yet responded to the evolving situation by asking their employees to work from home when possible.</em></p><p><em>Our decision to cancel our user research came ahead of the global response. At the time, it was not yet clear how quickly and how badly the situation would escalate.</em></p><p><em>I wrote this article because I was in a position to make the decision to cancel our in-person research activities we had scheduled for the week. Not everyone in our field has the same decision-making capacity in their position. My hope was that by sharing this story while the pandemic was in its earlier stages, other researchers or designers would have another company’s story that they could use as an example to push for their own company to change their plans. </em>If a single reader was empowered to make or push for change as a result of this article at the time it was published, I consider myself to have succeeded as a writer.</p><p><em>Of course, the pandemic accelerated so quickly that this article and its goals are already quite outdated.</em></p><p><strong><em>Why didn’t / don’t we just do remote research?</em></strong></p><p><em>My team already does remote research to great effect, and we certainly plan to re-do this research study adapted to a remote research format. However, at the time we made the decision to cancel our research, we didn’t only have to decide what to do about our research: we had to decide what to do about ourselves. Our team was visiting our company’s New York City office from our home base in Berlin. Ultimately, we decided to leave NYC and return home the following day.</em></p><p>No research project takes priority over your team’s health and safety.<em> Adapting our research project on the fly for a remote format was, quite appropriately, the last thing on our mind.</em></p><p>It’s been a hell of a week.</p><p>For the last two months, my team has been planning a series of user testing sessions in our New York City office, to test some of our latest ideas with our American customers.</p><p>We love doing user testing with our customers, not only because we get to meet and get to know the people that use our product, but because it involves inviting them to our office’s test kitchen and asking them to cook a meal.</p><p>A few weeks ago, rumblings around the coronavirus (COVID-19) began to pick up steam. Our product and design team is based in Berlin, and as the virus was not yet in Germany or the USA, we decided to move ahead with our planning and made the trip to New York City two weeks ago.</p><p>We had a productive first week with the New York team, running workshops and sharing stories while recruiting and preparing for the research sessions scheduled for the following week. We were planning to conduct ten 2-hour sessions throughout the week.</p><p>During the week, it was clear that the coronavirus was a growing concern, as the first few cases began to arrive in the USA and New York state.</p><p>On Sunday, March 8, <a href="https://www.pix11.com/news/coronavirus/avoid-crowded-subways-work-from-home-if-possible-cuomo-says-amid-coronavirus-concerns">New York Governor Andrew Cuomo urged New Yorkers to stay away from workplaces and public transportation</a>.</p><p>On Monday, March 9, we checked in as a team to decide how to proceed.</p><p>Each of us shared our concerns. We felt that health and safety aside, we faced an ethical challenge around continuing ahead with in-person user research.</p><p>While there were no mandatory guidelines around travel and commuting set out by the city or state governing bodies, we knew that by continuing with the study, we would be asking participants to travel to the office, potentially exposing them to transmission along the way. While folks might choose to travel anyway and could always choose to cancel on their own, we’d be creating an incentive to making a choice that they might not otherwise choose to make.</p><p>Unfortunately, as the sessions rely on a physical kitchen environment, we couldn’t adapt on the fly to a remote testing setup.</p><p><strong>That’s why we decided, together, to cancel all of our research sessions.</strong></p><p>On the surface, this was a difficult decision. The research project was months in the making and involved a lot of time, energy, and spent costs. But as soon as we looked at the broader context and our ethical obligations as designers, researchers, and product managers, the decision was easy.</p><p><strong>Why am I sharing this story?</strong></p><p><a href="https://medium.com/@tomaspueyo/coronavirus-act-today-or-people-will-die-f4d3d9cd99ca">The coronavirus continues to spread</a>. Workplaces around the world are being asked to have their employees work from home. But as I write this article, it’s just a “recommendation.”</p><p>We were in a position to decide to cancel our research ourselves. Not everyone is in that position. I hope that by sharing our story, you will be more empowered to make the same decision yourselves if you find yourself in a similar situation.</p><p>In the coming weeks, we’re going to adapt our research plan and find ways to test our ideas using remote research techniques. While we may not get exactly the same insights as if we held our sessions in our own kitchen environment, we will absolutely still learn a lot! And, we’ll find it easier to do remote research in the future, because we’ll have had the time to sit down and figure out how to make it work best for us.</p><p><em>Originally published at </em><a href="https://quinnkeast.com/writing/we-cancelled-our-user-research-because-of-the-coronavirus/"><em>https://quinnkeast.com</em></a><em>.</em></p><p><a href="https://quinnkeast.com/?source=post_page---------------------------"><em>Quinn Keast</em></a><em> is a UX Designer + Partner at </em><a href="https://caribou.co/?source=post_page---------------------------"><em>Caribou</em></a><em>, a user experience strategy and design consultancy.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f39b33c9cfdf" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/we-cancelled-our-user-research-because-of-the-coronavirus-f39b33c9cfdf">We cancelled our user research because of the coronavirus</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[Stop relying on gut decisions and define your principles]]></title>
            <link>https://uxdesign.cc/stop-relying-on-gut-decisions-and-define-your-principles-4761b43d9a09?source=rss-3e06b42dd370------2</link>
            <guid isPermaLink="false">https://medium.com/p/4761b43d9a09</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Quinn Keast]]></dc:creator>
            <pubDate>Thu, 26 Sep 2019 12:24:04 GMT</pubDate>
            <atom:updated>2019-09-26T23:05:04.585Z</atom:updated>
            <content:encoded><![CDATA[<h4>What do you do when you have to make a decision where there’s no obvious right answer?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xTUUsRUHVtYsj0MJsQFcyQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@joshstyle?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Joshua Coleman</a> on <a href="https://unsplash.com/s/photos/stomach?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p><strong>It can be paralyzing.</strong></p><p>Not only do you have to decide between equally valid options, you have to commit to your decision and be prepared to defend it.</p><p>It’s a challenge that products teams deal with every day.</p><p>Thankfully, there’s a solution.</p><p>First, let me ask you a question: on which side of your car is the gas tank cover?</p><h3>Why is your gas tank cover on [that] side of the car?</h3><p>Not every car has the gas tank cover on the same side.</p><p>You might imagine the most aesthetically-pleasing location for the gas tank cover is in the middle of the back. Or perhaps it could be hidden altogether, and only revealed when it’s time to fill up.</p><p>If we look back on car design through the ages, we can see automobile manufacturers have explored all kinds of design approaches just like those. Many cars would integrate the filler behind the back license plate, or even into the centre of the back hatch, like the Chevrolet Corvette C4.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dOp5N05ohS7OD0LZNwJbow.jpeg" /><figcaption>Photo from <a href="https://commons.wikimedia.org/wiki/File:Chevrolet_Corvette_C4_rear_view.jpg">Wikimedia Commons</a>. That little rectangle on the top of the back hatch covers the fuel tank filler.</figcaption></figure><p>Others, like the Bel Air, hid it behind a hinged taillight.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N0uQVfMOHJOF1duPH2jfgw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tJCwkaZYapdau3xSuS1efQ.jpeg" /><figcaption>Photos from Wikimedia Commons: <a href="https://de.wikipedia.org/wiki/Datei:Chevrolet_Bel_Air_1956_4door_Sedan_front.jpg">Left</a> and <a href="https://commons.wikimedia.org/wiki/File:1956_Chevrolet_Bel_Air_Fuel_Filler.jpg">Right</a>. The taillight flips down to expose the fuel tank filler.</figcaption></figure><p>Unfortunately, these elegant solutions turned out to be a practically poor idea, as the gas fillers had a habit of busting open and spilling gasoline everywhere and catching fire in even minor fender-benders.</p><p>As a result, regulations around gas filler locations evolved to specify in very narrow terms where the filler can be located, in the name of minimizing safety concerns.</p><blockquote>Current regulations demand the filler be at the widest part of a car, inboard of any crumple zones, and safe from dripping onto any hot exhaust bits or electrical wiring. This generally means the filler needs to be on one or the other sides of the car, and relatively near the passenger compartment.<br><em>Source: </em><a href="https://jalopnik.com/why-some-cars-have-gas-tank-fillers-on-the-left-or-the-1792790492"><em>Jalopnik</em></a></blockquote><p>When you account for how these constraints shape today’s car design decisions (not on the back, inboard of crumple zones, and safe from wiring), you’re left with one big decision to make: does the gas tank cover go on the driver’s side, or the passenger’s side?</p><p>There’s no right answer to this decision, but the decision still has to be made.</p><p>Toyota chose to put the cover on the driver’s side. Volkswagen and Chrysler put it on the passenger side.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9iq6R7cn7wiX4pZ4KMshWw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y0am0VofUPfofXb6vQm6TA.jpeg" /><figcaption><strong>Left: </strong>Toyota with gas cap on driver’s side. <strong>Right:</strong> Volkswagen with gas cap on passenger side. (Wikimedia Commons: <a href="https://commons.wikimedia.org/wiki/File:Toyota,_Paris_Motor_Show_2018,_Paris_(1Y7A1784).jpg">Left</a>, <a href="https://de.m.wikipedia.org/wiki/Datei:2017-03-07_Geneva_Motor_Show_0827.JPG">Right</a>)</figcaption></figure><p>How did these companies make their decision?</p><p>The website <a href="https://jalopnik.com/why-some-cars-have-gas-tank-fillers-on-the-left-or-the-1792790492">Jalopnik</a> asked these automakers this very question, and heard a variety of answers.</p><p>Volkswagen and Chrysler both stated they chose to put the cover on the opposite side of the car from the driver, which inherently places the car between the driver and the rest of traffic while they’re fuelling up, shielding them from other vehicles.</p><blockquote>“Volkswagen passenger cars always on the right (passenger) side to keep the filling person away from the street/lane traffic.”<br><em>Source: </em><a href="https://jalopnik.com/why-some-cars-have-gas-tank-fillers-on-the-left-or-the-1792790492"><em>Jalopnik</em></a></blockquote><p>Toyota, on the other hand, chose to put the tank on the driver’s side, for the driver’s convenience.</p><blockquote>“In our case it is based on company policy for customer convenience. In other words, we don’t want the customer to have to walk around [the vehicle].”<br><em>Source: </em><a href="https://jalopnik.com/why-some-cars-have-gas-tank-fillers-on-the-left-or-the-1792790492"><em>Jalopnik</em></a></blockquote><p>There’s no right answer for this decision. But each company still made the best decision — for them.</p><h3>How do we make the right decision when there’s no right answer?</h3><p>When we design the user experience in our products and services, we often find ourselves needing to make these kinds of decisions: decisions where there’s no right answer.</p><p>We do the research: we learn everything we can about our users and their context and needs, and we learn about the business and technological constraints that we must operate within, and we apply the lenses of human-centred design to narrow down our problem space.</p><p>We craft the architecture: we deeply understand the mental models, flow of information, and how entities can move and change over time.</p><p>We apply the heuristics: the basics of inclusive, lasting, and usable visual and interaction design.</p><p>Usually, the right decisions become clear. Often, we make these decisions subconsciously, without even realizing that we’re making decisions.</p><p>Other times, we stall out. Even after going through all of the requirements, applying the heuristics, and exploring the mental models, there’s nothing that directs us to a clear “right” decision.</p><p><strong>When that happens, we have to make the best decision.</strong></p><p>Most experiences usually have a series of “best decisions” that ultimately shape the experience.</p><p>The strongest experiences stand out, because they’re internally consistent with themselves.</p><p>But how do we make these decisions, and make them consistently?</p><p>Unfortunately, when individuals and teams are faced with making a decision, they’re all too often left trusting their gut.</p><h3>The fragility of gut decisions in product design</h3><p>As we’ve learned from ongoing research into cognitive psychology, when our gut tells us something, we should listen. Cognition and emotion are closely tied.</p><p>Whether we’re aware of it or not, we’ve all internalized a set of values and concepts that help us identify what “feels right” when we have to make a decision that has no clear right answer.</p><p>Teams that work closely together may align on a similar set of unspoken internal values that help them make these gut decision together, or they might look to a leader who they rely on to make those kinds of decisions on behalf of the team.</p><p><strong>But we can’t rely only on gut decisions.</strong></p><p>When culture shifts as people leave or join the company, or as the competitive or societal landscape changes, or as new priorities come down from on high, these internalized values easily ebb and flow.</p><p>Before long, inconsistencies and contradictions begin to surface in the product experience.</p><p>Relying on gut decisions is a fragile way to work.</p><h3>Gut decisions at scale</h3><p>Take another look at what the car makers had to say.</p><p>Volkswagen, a brand known for their commitment to <strong>safety</strong>, chose to put the fuel cover on the passenger side, to <em>“keep the filling person away from traffic.”</em></p><p>Toyota, a brand known for their commitment to <strong>convenience</strong>, chose to put the fuel cover on the driver’s side, because they <em>“don’t want the passenger to have to walk around the vehicle.”</em></p><p>Did either of these brands make the wrong decision?</p><p>No.</p><p><strong>But even when their team didn’t have a clear “right” decision, they had a clear “best” decision.</strong></p><p>Their decisions were the right decision — for them. Because they knew their principles.</p><h3>Principles help us make the best decisions</h3><p>We have to define and apply our <strong>principles</strong>.</p><p>Principles help us to express our shared vision and values. Good principles are simple, broadly applicable, and capture what is most important to both our business and our users.</p><p>Principles give our team direction, help us to resolve ambiguity, and give each member of the team confidence in their ability to make the best decision when the time comes to make a decision.</p><p>Principles give us a path for embracing and applying inclusivity, sustainability, and ethics in our work.</p><h4>Principles at the brand level</h4><p>Principles can be defined at the brand level, creating a set of principles that are shared by an entire company.</p><p>Southwest, one of the most-liked airlines in the world, embraced the idea of “love” as one of their core brand principles, and put people and their employees first.</p><p>Today, their brand values are captured as “the Southwest Way:”</p><blockquote><strong>Live the Southwest Way</strong><br>Warrior Spirit<br>Servant’s Heart<br>Fun-LUVing Attitude</blockquote><blockquote><strong>Work the Southwest Way<br></strong>Safety and Reliability<br>Friendly Customer Service<br>Low Costs</blockquote><blockquote>Source: <a href="http://investors.southwest.com/our-company/purpose-vision-values-and-mission">Southwest</a></blockquote><p>Employees are encouraged to make decisions guided by these shared principles. And it works: as <a href="https://www.underconsideration.com/brandnew/archives/new_logo_identity_and_livery_for_southwest_airlines_by_lippincott.php">Brand New reports</a>, while <em>“other airlines have suffered bankruptcies and layoffs, Southwest has remained profitable for 41 consecutive years.”</em></p><h4>Principles at the product level</h4><p>Principles can also be defined at the product and team level, creating a set of values that guide a single product or discipline.</p><p>My own team at <a href="https://marleyspoon.de/">Marley Spoon</a> is in the midst of a re-imagination of our mobile app, and we set out to define our own principles together to guide our work.</p><p>These are our principles:</p><blockquote><strong>Treasure time.</strong> We help people enjoy cooking and to try new things, while spending their time on the things they enjoy. When the app fits in, it must be a purposeful use of time.</blockquote><blockquote><strong>Users in control.</strong> Minimise uncertainties, prevent surprises, and reduce the mental load of decision-making to give people control over their experience.</blockquote><blockquote><strong>Everyone can cook.</strong> Our products are used by a worldwide community of all abilities. Anticipate the stress cases and design for inclusion so that everyone can cook.</blockquote><blockquote><strong>Fits like the perfect kitchen.</strong> Like the perfect kitchen, everything has its place and time: everything’s easy to find, intuitive, and supports the task at hand.</blockquote><blockquote><strong>Trustworthy.</strong> Trust must be earned, and it’s reciprocal: for people to give us their trust, we must give them transparency.</blockquote><p>We’re not alone.</p><p>Some of the best product teams in the world work together to define, capture, and share their principles.</p><p>Take Airbnb:</p><blockquote><strong>Unified:</strong> Each piece is part of a greater whole and should contribute positively to the system at scale. There should be no isolated features or outliers.</blockquote><blockquote><strong>Universal:</strong> Airbnb is used around the world by a wide global community. Our products and visual language should be welcoming and accessible.</blockquote><blockquote><strong>Iconic:</strong> We’re focused when it comes to both design and functionality. Our work should speak boldly and clearly to this focus.</blockquote><blockquote><strong>Conversational:</strong> Our use of motion breathes life into our products, and allows us to communicate with users in easily understood ways.</blockquote><blockquote><a href="https://airbnb.design/building-a-visual-language/">Source</a></blockquote><h4>When to use brand and product principles</h4><p>Sometimes, brand and product principles are interchangeable. If your company only has one product, it should probably have a shared set of principles.</p><p>Other times, a company may have many products. When this is the case, the company should probably have a unifying set of brand principles that guide the company as a whole and unite their products, as well as product-specific principles tailored to individual product contexts.</p><p>There’s no one-size-fits-all — you need to find the right principles for you and your team, together with your team.</p><p>When you do, you’ll be able to make decisions faster: instead of endless debate or analysis paralysis, you’ll be able to ask, <strong>“What choice most aligns with our principles?”</strong></p><p>Whatever your answer may be, you’ll have made the best decision.</p><p><em>In a followup to this article, I’ll be sharing a simple but effective workshop that you can run with your team to craft your principles. I’ll add a link here when it’s available!</em></p><h4>Thanks for hitting the 👏 if you enjoyed this article! It’ll tell me to write more like this.</h4><p><a href="https://quinnkeast.com/?source=post_page---------------------------"><em>Quinn Keast</em></a><em> is a UX Designer + Partner at </em><a href="https://caribou.co/?source=post_page---------------------------"><em>Caribou</em></a><em>, a user experience strategy and design consultancy.</em></p><p><strong>References</strong></p><ul><li>Jalopnik: <a href="https://jalopnik.com/why-some-cars-have-gas-tank-fillers-on-the-left-or-the-1792790492">Why Some Cars Have Gas Tank Fillers On The Left Or The Right</a></li><li>Brand New: <a href="https://www.underconsideration.com/brandnew/archives/new_logo_identity_and_livery_for_southwest_airlines_by_lippincott.php">New Logo, Identity, and Livery for Southwest Airlines by Lippincott</a></li><li>Airbnb: <a href="https://airbnb.design/building-a-visual-language/">Building a visual language</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4761b43d9a09" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/stop-relying-on-gut-decisions-and-define-your-principles-4761b43d9a09">Stop relying on gut decisions and define your principles</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>
    </channel>
</rss>