<?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 Keli McCreadie DiRisio on Medium]]></title>
        <description><![CDATA[Stories by Keli McCreadie DiRisio on Medium]]></description>
        <link>https://medium.com/@kdirisio?source=rss-cb8e725755c5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*9H2T3OAP0ieLAfCmehcalQ.jpeg</url>
            <title>Stories by Keli McCreadie DiRisio on Medium</title>
            <link>https://medium.com/@kdirisio?source=rss-cb8e725755c5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 09:26:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kdirisio/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[When Assumptions Get in the Way]]></title>
            <link>https://medium.com/@kdirisio/when-assumptions-get-in-the-way-dc860dc46cfd?source=rss-cb8e725755c5------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc860dc46cfd</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[inclusion]]></category>
            <category><![CDATA[diversity]]></category>
            <category><![CDATA[empathy]]></category>
            <category><![CDATA[education]]></category>
            <dc:creator><![CDATA[Keli McCreadie DiRisio]]></dc:creator>
            <pubDate>Thu, 10 Jan 2019 15:50:31 GMT</pubDate>
            <atom:updated>2019-01-10T15:50:31.248Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rDw_aerWpw93sT7H8DiccQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/rNqB4zmatUs?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Eneida Hoti</a> on <a href="https://unsplash.com/search/photos/empathy?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>We hear words like inclusion and diversity all of the time. We listen to it on TV, online, in social media. As a professor, I take workshops and classes on these issues. I am an Assistant Professor of Graphic Design and Interactivity at Rochester Institute of Technology, and inclusion and diversity are very important as we have a large contingent of international students, and we have one of the largest deaf communities on a college campus. RIT has more than 1,100 deaf students, on a campus of over 19,000.</p><p>As I teach students about <strong>user experience (UX)</strong>, I spend a lot of time teaching my students about <strong>empathy</strong> and what it means to be empathic. We as visual communicators need to put ourselves in our users’ shoes and try to feel what they feel and think how they think. We need to be able to understand their motivations — to be able to design effectively we need to focus on the user experience.</p><p>I want my students to learn how to define their audience and how to create a successful user experience. I stress how important it is to ask questions: What motivates the user? What are their wants and needs? The answers to these questions are what will guide their design decisions. I often ask my class, <br>“How do we design a website or an app or a printed page if we don’t know who our end user is?”.</p><p>I tell my students that the days of designing for design’s sake are gone; we now create with a purpose, and we must know how to convey a specific message to our user. We as designers need to take the time to learn about our audience and design for them, through research, questions, testing and repeating the process.</p><p>Last year I was teaching a class that I have taught many years before, Motion Graphics. I was getting ready to introduce a project that was a class favorite, kinetic type, where the students could use animated type to relay the message of a spoken word piece or the lyrics of a song. “Kinetic typography refers to the creation of moving type. It is an animation technique that is used to make lettering expand, shrink, fly, move in slow motion, grow and change in numerous ways for the user.” (<a href="https://designshack.net/articles/typography/kinetic-typography-an-introductory-guide/">designshack.net</a>). Shortly before class started, as I was double-checking my assignment sheet, it hit me: I have three deaf students in my class. <em>How could I ask them to animate type to a song or a spoken piece when they have never heard either one?</em> The same project I had been using for years would not work for these students.</p><p><strong>MAKING ASSUMPTIONS=MAKING MISTAKES</strong></p><p>I often have deaf students in my classes, but until that moment, I guess I had never <em>really</em> thought about what they needed. I have learned over the years how to tailor my teaching style to benefit both deaf and hearing students, making sure that everything is thoroughly explained and understood, but a project of designing a printed poster does not hold the same challenges as working with motion, which usually incorporates sound. On the fly, I came up with what I thought was a perfect solution: in addition to the song or spoken piece, students could choose to animate a poem. That way, there would be no sound, it was open to interpretation. The deaf students wouldn’t feel singled out, as anyone could choose that option. I was impressed with my forward-thinking, for about three seconds, until my students proved me wrong.</p><p>After I presented the project to the class, and one of the deaf students, Tom, called the interpreter and me over to tell me what he was thinking. He couldn’t wait to animate a spoken word from a favorite movie, one of the Harry Potter movies. I stood there in shock as the interpreter told me what Tom was signing. Here was a student who was deaf and non-verbal but he couldn’t wait to work on the project with sound. The two other deaf students started signing, and the interpreter told me that they were going to animate a scene from a movie and a song. I stood there, speechless, as they all signed excitedly to each other.</p><p><strong>TIME TO PRACTICE WHAT I PREACH</strong></p><p>How could they do this successfully when they can’t hear? And it hit me: I needed to use an empathic approach, and put myself in their shoes. By doing this, I could find out how they would tackle this project. So I did what I had been teaching my students to do to be empathic: I asked them. “How do you animate this when you can’t hear it?” They were so excited to tell me how they planned to create their project. I noticed that the rest of the class was listening in on the conversation, so I opened the discussion up to everyone, and the interpreter spoke to the class. The student who was animating the song, Margaret, would study the lyrics, and feel vibrations on her computer to get the ‘feel’ of the song. Tom, who was doing Harry Potter knew the look and feel of the movies. Marcus, the third student, said that he knew the film he was using from the closed-captioning and he wanted to approach it as a way to design a better method of captioning.</p><p>I watched the hearing students asking questions of the deaf students. The interaction between the students was fascinating! I stepped back and let the students talk with each other. I realized that I was so focused on making sure my deaf students felt included when I changed the project that I never stopped to think how I might be causing them to feel like they didn’t belong, by singling them out with a “non-hearing” option. One of the problems for deaf students in classes is they are often unintentionally segregated, as they usually sit together so they can see the interpreter or me or the screen in the front of the room. They often can’t converse with hearing students without the help of an interpreter. As crucial as inclusion is, I realized that I might have inadvertently been creating the opposite position.</p><p>Listening to the conversation around me, I started to question my assignment specifications. I never thought about how to animate something that most of us take for granted. Then I started thinking: is it possible to animate a song or spoken word with only animation and no sound? I asked the class, and this started a lively discussion. The hearing students were intrigued by the concept and asked the deaf students questions about how they watch movies or listen to music, and how they comprehend the message. They asked questions about captioning and what works and what doesn’t for someone who depends on the text on the screen. The deaf students were so enthusiastic to share how they do things, and the hearing students were fascinated with the methods that the deaf students used and they took for granted.</p><p>As the class was talking about hearing versus non-hearing, I came up with an idea: create a motion graphic with sound and then the same graphic without sound. Would it be as successful? I asked the class what they all thought and every single one of them was excited by the concept.</p><p>Five weeks later and students presented their kinetic type project with sound vs. no sound, with surprising results. Surprisingly, most students preferred the projects without sound as it allowed them to draw their own conclusions about the mood of the piece. The critique was one of the liveliest ones I have had in my years of teaching, as the deaf students could be the experts on designing without sound.</p><p><strong>WHAT I LEARNED</strong></p><p>As much as the students learned through this process, I learned so much more. A few takeaways that I now implement in all of my teachings:<br>-Never assume you know what your students (or your employees or customers) want.<br>-Never assume what any of them need.<br>-Try to put yourself in their shoes, but if you can’t, don’t be afraid to ask questions to find out their motivations. Listen to their answers and implement them.<br>-Get feedback from your audience along the way, find out if what you are doing is working and if it’s not, change it.<br>-Never make assumptions about what someone can do. Instead, assume that if they can’t do something, they will figure out a way to challenge themselves and accomplish the task.</p><p>By putting myself in my students’ shoes, employing empathy, and by asking questions, I learned to ask all of my students what they needed and wanted. As a bonus, they began to ask each other. The deaf students were excited at the opportunity to try something different and to push themselves, and the hearing students were excited to try something they hadn’t given much thought to before. This experience had a profound effect on me, in both my teaching and my professional practice. I’m not afraid to ask questions, many questions, and to admit that maybe I don’t know everything. It’s my user who has the answers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc860dc46cfd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>