<?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 AmberNechole on Medium]]></title>
        <description><![CDATA[Stories by AmberNechole on Medium]]></description>
        <link>https://medium.com/@ambernechole?source=rss-f7f1ba6dae13------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Pt-YoXoOx59MaWuIwK4zJA@2x.jpeg</url>
            <title>Stories by AmberNechole on Medium</title>
            <link>https://medium.com/@ambernechole?source=rss-f7f1ba6dae13------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 14:58:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ambernechole/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[10 Things I’ve Learned as a Product Designer]]></title>
            <link>https://medium.com/@ambernechole/10-things-ive-learned-as-a-product-designer-a219d15b186a?source=rss-f7f1ba6dae13------2</link>
            <guid isPermaLink="false">https://medium.com/p/a219d15b186a</guid>
            <category><![CDATA[designer]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[AmberNechole]]></dc:creator>
            <pubDate>Wed, 10 Jan 2024 00:04:46 GMT</pubDate>
            <atom:updated>2024-01-14T18:05:24.003Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N6BN9sz_3zVh5RpTMXE2bQ.png" /></figure><p>This is an article I’ve been meaning to write. It’s equal parts dissemination of understanding and personal reflection. The lessons weren’t always immediately apparent, but through repetition, flexibility, and a damn good community of mentors I found my way.</p><p>My intention is that I can help you snuff out insecurities more quickly than I did to uncover your confidence as a designer.</p><h4>1. Don’t Wait</h4><p>Don’t wait for someone to give you the authority to try or create something. If you have an intuitive nudge to do something, follow it. See how the team responds. Learn from it. This is how confidence is built. Not by outside validation you’re doing “it” right.</p><h4>2. Share your Screen</h4><p>Humans are visual creatures. When you’re presenting work, share your screen. Words are abstract. Words mean different things to different people. Whether it’s a design, a technical workflow, annotations, or a CRD share your screen for the love of god. For the chosen few who can follow without a visual, take a bow. For the rest of us, show your screen.</p><h4>3. Know your Expectations</h4><p>Meeting the deadline is not your only expectation. There are unspoken tactical and interpersonal expectations that are also included. Set up 1:1s with your leads and understand their expectations early and check in often. Do they like async or collabs? What are their strengths? Do they know yours? What are their expectations for someone in your role? How do they like things organized? Asking these questions tease out things that often remain unsaid in calls, but vented about in DMs.</p><h4>4. Log Your Day</h4><p>The rate that design moves keeps us running to the next deadline or project without much reflection. At the very least, make a shitty log. You made a list of stakeholder interview questions? Log it. You reviewed your team’s work? Log it. You audit apps? Log it. Having your work in your own words makes it easier to validate your experience and skills. The minutiae in the day is what makes<em> </em>us designers. Tracking it alongside the big accomplishments colors the story you tell about your work.</p><h4>5. Mentor or Manage</h4><p>A good mentor expands your mindset and thus your life. I’ve been blessed to spend my career with powerhouses who poured into me. Mentorship to me is the decision to invest in someone else’s growth as a practice. When I made the transition to management, my mentorship soared to a new level. Being a manager sharpened my role as advocate. I ask myself, how might I help facilitate <em>their</em> realization of their potential? How do I position them in the best position to succeed? How might I be better to make them so? Take advantage of these opportunities and see how you grow.</p><h4>6. Design (Think) Outside of Work</h4><p>As a social scientist turned designer, I struggled with seeing myself as just that outside of the 9–5. At work, we’re often limited by constraints. When we consciously create through applying our design minds to other challenges in our lives we start to naturally see patterns that crystallize as our unique approach to the work and world. Bring that back to work, and that’s ya sauce.</p><h4>7. Open your Mouth</h4><p>Being shut mouth takes more than it gives. That goes for promotions, PTO, to client presentations. If you’re in the room take advantage of it. Share your POV, connect and learn from your teams, practice presenting, and <em>yes, </em>ask the question. Your tongue is raw enough from biting it, take a risk and speak up! Don’t be afraid of the sound of your own voice.</p><h4>8. Take Notes</h4><p>Don’t solely rely on your PM to take notes. Things you peep are different from others, and that perspective presents a unique opportunity for account or team growth. Get in the practice of a note-taking system that works for you. Tracking facts, feedback, and opportunities springs new connections to improve your design that deliver on KPIs in an informed way.</p><h4>9. Build your toolkit</h4><p>As a designer, you find you’ll acquire tools overtime. A quick user test prepares you for a full fledged moderated one. A light audit prepares you for a discovery deck to sell in a new feature or product. Though I don’t subscribe to the “pay your dues” energy, there is absolute merit to <em>you just need time on job</em>. Repetition teaches you things that can’t be transferred through voice alone. You can study 10,000 UX/UI tools but not know when or why to use it. Knowing this is what sets you apart.</p><h4>10. Accountability = Confidence</h4><p>As a self-taught designer, I came with some insecurities. I spent too much time looking for design approval when I should’ve had a strong POV and stood ten toes. Design is series of subjective choices. Free yourself from the overthinking and make a choice with sound reasoning. Even in a perceived failure the beauty is making a fucking choice. Stop hiding behind design reviews, make your choice, take the feedback and GO.</p><p>Thanks for reading!</p><p>If you find these helpful, let me know. Would love to hear if something helped you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a219d15b186a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An actionable how to for conversational UI beginners]]></title>
            <link>https://uxdesign.cc/an-actionable-how-to-for-conversational-ui-beginners-c6c6057c4b61?source=rss-f7f1ba6dae13------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6c6057c4b61</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[conversational-ui]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[AmberNechole]]></dc:creator>
            <pubDate>Tue, 11 Sep 2018 04:31:03 GMT</pubDate>
            <atom:updated>2018-09-14T00:28:17.408Z</atom:updated>
            <content:encoded><![CDATA[<h4>For a job interview, I was given the exercise to create a script for a conversational UI based on a current application. After connecting the dots that conversational UI had everything to do with AI, voice, ML, and chatbots it a pure delight to try out.</h4><p>In this article, I document my design process behind this short exercise with the goal of outlining a potential process for beginners to use when practicing or designing for conversational UIs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/849/1*u1SbU21BWuPRaHL8H_Uljg.jpeg" /></figure><h4><strong>Researching Conversational UI</strong></h4><p>I started by reading this <a href="https://chatbotsmagazine.com/what-is-a-conversational-ui-and-why-it-matters-de358507b9a2">article</a> that describes conversational UI in-depth calling it “interacting with the computer on human terms.”</p><p>After this cursory search of conversation UI, it is clear that the technology is creating the infrastructure that increases a computer’s capacity to solve problems whiling conversing with humans as naturally as possible, and learning from it.</p><p>For example, you can barely tell the difference between this Google voice assistant and the front desk assistant at this salon. In the “age of assistance” we are demanding more experiences that do not disrupt the lived reality of our lives. The impersonal and restrictive syntax of past and present bots and voice assistants served a purpose as their focus was automating simple tasks like connecting you to your “party’s extension” or gathering basic information to support human representatives of the problem or purpose of your inquiry.</p><p>Now, chatbots, voice assistants, and similar technologies are training to reflect the same natural language patterns we use as humans. The goal is to make the technology indistinguishable from humans by being social and user-led, allowing the computer to give feedback to customer queries and inputs.</p><h4><strong>Choosing a Company</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/514/1*9HLu-zlCB_t7oOZ5oqkuVA.png" /></figure><p>This didn’t take long at all. I picked up my phone and started flipping through it’s screens. Considering the apps that built on search functions, I landed on Groupon. Surprisingly, I found no remnant of the chatbot or voice assistant technology in the app or desktop experience. I liked the idea of starting from scratch so I settled on Groupon as my company.</p><h4><strong>Setting the Tone</strong></h4><p>Once I chose Groupon, the next logical step was to find documentation on Groupon’s brand personality and voice. Luckily, being the consumer facing product it is, the website detailed five characteristics that described the “feel” of the brand and it’s commitment to the innovation the product.</p><p>I could have stopped here, but I wanted to add more depth to my understanding of the brand’s tone. I decided to make a “this NOT that” statement to define the intention of each characteristic. In addition to the statement I wrote a description clarifying the distance between the characteristics in the “this NOT that” statements.</p><p><em>Fun NOT Childish — </em>All touch points carry a touch of playfulness that resonate with mobilizing the customers ability to connect with great deals that enrich their lives. An energetic and dynamic experience that inspires not drains from “overdoing it.”</p><p><em>Clever NOT Condescending — </em>Take the guesswork out of getting good deals. Think about the things customers may overlook and use subtle cues to guide customer to their goal. Let their ‘aha’ moments intuitive and reinforce Groupon’s cleverness.</p><p>Using these statements as guiding principles, I created a container for the conversational UI.</p><h4><strong>Use Case</strong></h4><p>Next, I began weaving the story of my Groupon chatbot experience. My use case came first, <em>“I want to find and purchase a deal for entertainment so that I can take my family’s kids out for fun.”</em></p><p>If you wanted a deeper story that’s it — it’s the first thought I came up with so I challenged myself by seeing it through. Having a clear use case became the foundation for the conversation that met my user’s need.</p><h4><strong>User Persona</strong></h4><p>Now, it was time to think of who was speaking to the chatbot anyway. Who was the I? With a use case in hand, I created a fictional user persona that gave me the remaining context I needed to start the conversation UI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mMh2uycr44unhyY6ZM5LvQ.jpeg" /></figure><p>Meet Aaliyah.</p><ul><li>A 35-year-old woman with family in town for holiday at her house. She is new to Atlanta, GA, so she is only willing to go 10–20 miles away from her home. She doesn’t have a strong sense of what the kids in the family like, but promised them a night out in Atlanta so she needs help finding an age-appropriate activity.</li></ul><p>Based on my sister, I feel this persona was realistic and representative of a market of Groupon’s current users.</p><h4><strong>User Flow</strong></h4><p>How does the user get from their having a need to fulfilling a goal? By utilizing user flows, I was able to think through the conversation as if I was creating flows for a UI design. When we talk about user experience even a lo-fi flow can help define the scope of a particular feature and ensures key steps of the envisioned process are not missed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*PObdbvsqxxzt4FXk.png" /><figcaption><a href="http://hvdam.com/dialogue-for-conversational-ui/">http://hvdam.com/dialogue-for-conversational-ui/</a></figcaption></figure><p>Being this was an exercise, I went straight to my goal with minimal consideration to alternatives of my scenario. What if my bot couldn’t answer her question? What if my user didn’t have the answers the bot needed to make a decision?</p><p>Making sure you take time for these considerations is key when you develop scripts with real world application because the happy path is rarely the reality. A flow chart can help you plot the happy path and alternatives which together tell a more robust story.</p><h4><strong>UX Writing — the crux of Conversational UI</strong></h4><p>Unlike the other sections which follow my actions and thought processes, I’m going to use examples from my script, I share a few key insights to wrap up.</p><ul><li><strong>Actions Speak Louder than Words</strong></li></ul><p>Leverage the tone and personality characteristics in the actions of the UI. We get the most robust characters from good indirect characterization. That’s also true for people, you know — actions speak louder than words.</p><p>When thinking about how to bring in the traits from your research consider the “how” your bot does something. How does it ask a question? How does it respond when it’s stumped? How does it respond to an annoyed user? How does it communicate an error?</p><p>MailChimp is a good example with it’s quirky copy being reflective of it’s brand personality. The reality is I don’t remember the words at all. I remember the feel from the actions taken that create the experience — like the monkey hi-fiving you after a campaign.</p><p>Think about the feeling you want your customers to leave with. This is the most important.</p><ul><li><strong>Align the Language of Platform Experiences with the Script</strong></li></ul><blockquote>Aaliyah: Hello?</blockquote><blockquote>Dealbot: Hey Aaliyah, what kinds of deals are you looking for today?</blockquote><blockquote>Aaliyah: I need to find something to entertain a group of five kids for 2–3 hours tonight.</blockquote><p>A chatbot does not stand alone, it should speak the language of the website and app experience. It’s key for a Groupon chatbot to ask, “what deals are you looking for,” just like Facebook asks “what’s on your mind, AmberNechole?” Become aware of how the entire ecosystem of language that your script exists in and build with it in perspective.</p><ul><li><strong>Don’t Expect Human Kindness</strong></li></ul><blockquote>Dealbot: Would you like me to find similar activities based on relevant past orders?</blockquote><blockquote>Aaliyah: Yes.</blockquote><blockquote>Dealbot: Sounds good. I’ve sent you a couple options, am I going in the right direction?</blockquote><blockquote>Aaliyah: Kinda, the kids I’m with are a mix of teens and pre-teens. All the stuff for young kids should be excluded.</blockquote><p>In my first drafts, my user speaks to my bot like a regular person. Upon reflecting on the script, I realized that unless someone is talking to a bot for pure fun, they want to get a job done. I intentionally made her answers short, like ‘yes’ and ‘nope’ to juxtapose the bot’s characteristics.</p><p>In creating scripting for conversational UI, remembering the “customer is always right” is a good rule of thumb to design by. Your bot should reflect the best of your brand with an angry customer or a gentle one.</p><ul><li><strong>Display Your Bot Using Earlier Information</strong></li></ul><p>In brainstorming, especially before the data rips you to shreds, it’s good practice to show your bot using earlier information to make a decision. It reflects continuity in your design and understanding of the dynamic nature of chatbots and voice assistants. They are constantly learning how to respond to new questions and using past information to make inferences like you and I.</p><blockquote>Dealbot: Paintball Park has a deal for $49 for 12 open-play passes with safety gear and gun rental for 12 people ($420 value). It does have some stipulations, Compressed air and paint not included and a minimum 500 paintball purchase per person required. Additionally, it is not recommended for children under 13 without parental consent. There is no food at the venue. I can help you find a deal if you’d like.</blockquote><p>In the above script, my bot recalled an earlier “input” of the user saying this:</p><blockquote>Aaliyah: Kinda, the kids I’m with are a mix of teens and pre-teens. All the stuff for young kids should be excluded.</blockquote><p>Did you catch what my bot did? Aaliyah said she had a mix of pre-teens and teens. The bot doesn’t know the exact ages, but due to the ‘string’ pre-teen it triggers the response “it is not recommended for children under 13 without parental consent.” Although subtle, I thought it was important to have to reflect it’s ability to make informed decisions about existing deals based on a customer’s information.</p><ul><li><strong>When You Get Stuck, Switch Directions to Refresh Your Brain.</strong></li></ul><p>This one is for you, not the UI. Just like writing a story or article, if you get stuck start on the other end. I think scripting is especially cool to do this with because meeting yourself in the middle can show blatant inconsistencies or the perfect integration of problem and solution. UX writers get writer’s block too, so it’s important to change perspectives and use design-thinking strategies to facilitate your scripting.</p><p>That’s it for this one guys! Clap it up for me if it was helpful and feel free to ‘school’ me on conversational UI. I love to learn.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c6c6057c4b61" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/an-actionable-how-to-for-conversational-ui-beginners-c6c6057c4b61">An actionable how to for conversational UI beginners</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[A journey into Afrocentric UX]]></title>
            <link>https://medium.com/black-ux-collective/a-journey-into-afrocentric-ux-2709a3534521?source=rss-f7f1ba6dae13------2</link>
            <guid isPermaLink="false">https://medium.com/p/2709a3534521</guid>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[black-in-tech]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[AmberNechole]]></dc:creator>
            <pubDate>Mon, 03 Sep 2018 00:47:27 GMT</pubDate>
            <atom:updated>2019-07-29T01:44:05.161Z</atom:updated>
            <content:encoded><![CDATA[<p>Sitting in my African American Psychology class, I was introduced to Design Experience and Thinking in a guest lecture Skype session by <a href="https://medium.com/u/543b03c8cad2">Shayna Atkins</a>, product consultant and founder of <a href="http://atkinscoordination.com/">Atkco Inc</a> and <a href="http://thequeensbrunch.com/">The Queens Brunch</a>.</p><p>Probably 5 seconds after the terms rolled off her tongue, I was on her website and searching for anything I could find on this topic. Naturally, I came upon user design experience and instantly fell in love with the idea of solving problems by meticulously crafting experiences in a collaborative and dynamic process. I saw my coursework and this new concept merge together in a way that utilized my analytical skills while activating my desire to be creative.</p><p>At the time I found UX, I was on track to graduate with a Bachelor of Arts in African American studies — I found myself at a peculiar disadvantage from peers studying STEM or going to art and design schools.</p><p>Of course, doubt set in, despite my intuition screaming yes to my heart. What is the value of hiring me . . . an African American studies major without a robust portfolio of beautiful designs — how do I sell that? What is the value of this degree in a field of User Experience? I mean people had history degrees, but African American studies? That’s a hard sell.</p><p>Despite many should haves and wishes, I began to accept the blatant reality of where I was in life and conviction to move into UX. I was shown this path for a reason and it unexpectedly provided a new way to apply concepts I thought up in college but did not yet have a vehicle of expression.</p><p>I started having meetings, going to events, attending General Assembly courses in UX and product management, learning Sketch, getting a subscription to Adobe Suite, reaching out to UXers on LinkedIn, having Facebook chats, coffee meetings, replying to endless email chains with program directors, UX designers, mentors, new connections, and even family — I began writing myself into user experience, my coursework laying the foundation for me to seal gaps current user experience theory failed to fill.</p><p>When I picked up <a href="https://miscmagazine.com/">MISC</a>, “a journal of strategic insight and foresight,” and ironically enough the design edition, I began to become inspired about what design and technology could mean for me despite not having a Computer Science or Graphic Design degree. The articles in the magazine showed me just how much I could get into going from IOT and Sonic Experience design to bio-design, and democratizing innovation. That was one thing I craved in academia, to see my work directly impact people and the way they live their lives. With UX, my research and strategy could behind technology that had a social impact — I fell in love with the opportunity to do so.</p><p>I now felt I wasn’t pretending to do UX, excited I saw a clear path of progression for myself. This was the point I felt that I “belonged to the journey”, as my teacher would say. I felt myself move into alignment and my past experiences crystallize as a foundation to my current position.</p><p>Dispelling my insecurity new thoughts arose — if technology is becoming human-centered, how is “human” being defined? If you are not considered “human” for centuries, why would there be an emphasis on incorporating your experiences and history into the things you use daily?</p><p>I started asking questions, Why does Siri and all her variations sound white? Why don’t some <a href="https://mic.com/articles/124899/the-reason-this-racist-soap-dispenser-doesn-t-work-on-black-skin#.6MVoQTfhJ">soap dispensers</a> work for me? Why are black people being <a href="https://www.wired.com/story/when-it-comes-to-gorillas-google-photos-remains-blind/">labeled as gorillas</a>, and why did Google have to <a href="https://www.theverge.com/2018/1/12/16882408/google-racist-gorillas-photo-recognition-algorithm-ai">“fix” it </a>by removing gorillas from being recognized? Why did the <a href="https://www.theguardian.com/technology/2016/mar/24/tay-microsofts-ai-chatbot-gets-a-crash-course-in-racism-from-twitter">Microsoft chat bot</a> turn into a neo-nazi and why does it’s successor <a href="https://qz.com/1340990/microsofts-politically-correct-chat-bot-is-even-worse-than-its-racist-one/">Zo</a> avoid all things deemed “politically incorrect” and on TOP of that can’t tell me slavery is bad? And why the hell does she says “those people” after I ask the question?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/635/1*Q69ZcvFZCgyv3gcBpni09A.png" /><figcaption>From my FB Messenger</figcaption></figure><p>When it boiled down, I realized I was highly valuable to a team. My expertise in African American studies helped me to hone an awareness of the biases and systems that are responsible for the technology I just mentioned. It groomed me to read between the lines and recognize the subtle effects of homogenous teams and companies that promote the exploitation and commodification of the vulnerable.</p><p>Furthering my research on UX after this insight, I realized that it is a differentiating factor in companies that will survive in the future. But what’s the point of well crafted experiences that are racist, sexist, homophobic, classist, and ableist? <strong>Ya’ll need a sista.</strong></p><p>Just like in academia, no matter the subject or experience, if the lens of analysis reduces the humanity of a people or eradicates their perspective it reflects the bias of it’s creator.</p><p>Therefore by de-marginalizing the black experience, it is inevitable that technology will develop the capacity to become aware of and deal with oppressive systems.</p><p><strong>There was my space,</strong> tapping into it I thought of Molefi K. Asante’s concept of Afrocentricity “a paradigm based on the idea that African people should re-assert a sense of agency in order to achieve sanity.” The perspective locates the suppressed histories and experiences of the African Diaspora to place them at the center when evaluating social, economic, political, psychosocial and spiritual phenomena.</p><p>Afrocentric research developed its core tenants being (1) the research impacts the community positively and (2) the community actually desires the research / project being executed. Is that not user experience?! To create what the user needs by asking them and developing an experience with the product be delightful and solve their problems. Yup, that was it. As a researcher and lover of strategy this was my spot.</p><p>I want sane people and sane technology, if the AI can understand oppressive systems it’s cool with me. But seriously, when you view social phenomena from the black experience, you become much more aware of the interlocking nature of oppression that situates blackness at the bottom of the “hierarchy.” This led me to write the article <a href="https://medium.com/@ambernechole/inter-web-tionality-checking-our-design-97f34a730b68">Inter[tech]tionality: Checking our Design</a>, which is a foundational concept that drives my UX work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*-XDURKEz_8SpgdMdfbqqPA.jpeg" /><figcaption>Gerald Williams, “Message from a Giant — Garvey”</figcaption></figure><p><em>So as I come to the *almost* one-year mark as a UXer, I have listed the principles that keep me grounded in why I got into UX.</em></p><ol><li>I value my sanity over conformity, and do not erase my blackness or any other identity I express.</li></ol><p>2. I do not shrink itself for the possibility to become visible in the future.</p><p>3. I do not concern myself with superficial conversations of “we will do better” and corporate multiculturalism.</p><p>4. I draw on the activist roots of black liberation, and reject greedy attempts to use technology to enslave.</p><p>5. I share information and enable others to begin their own journeys in technology.</p><p>6. I bring my perspective and the perspectives of those absent from the room.</p><p>So what does that mean for UX, design thinking, and more importantly me as an African American Studies graduate working as an UXer?</p><p><strong>It means, solving old problems and actually getting the answer right.</strong></p><p>That right there is value.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2709a3534521" width="1" height="1" alt=""><hr><p><a href="https://medium.com/black-ux-collective/a-journey-into-afrocentric-ux-2709a3534521">A journey into Afrocentric UX</a> was originally published in <a href="https://medium.com/black-ux-collective">Black 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[7 Things I Learned Creating an Accessibility Guide for Designers]]></title>
            <link>https://blog.prototypr.io/7-things-i-learned-creating-an-accessibility-guide-for-designers-4715af78f68a?source=rss-f7f1ba6dae13------2</link>
            <guid isPermaLink="false">https://medium.com/p/4715af78f68a</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[intertechtionality]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[AmberNechole]]></dc:creator>
            <pubDate>Sun, 26 Aug 2018 05:45:08 GMT</pubDate>
            <atom:updated>2018-08-27T08:42:25.751Z</atom:updated>
            <content:encoded><![CDATA[<p>A couple months ago, I was tasked with researching and documenting the <a href="https://www.w3.org/TR/WCAG20/">Web Content Accessibility Guidelines </a>(WCAG) for a group of user experience and graphic designers.</p><p>WCAG’s defines it’s purpose this way:</p><blockquote>Web Content Accessibility Guidelines (WCAG) 2.0 defines how to make Web content more accessible to people with disabilities. Accessibility involves a wide range of disabilities, including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities. Although these guidelines cover a wide range of issues, they are not able to address the needs of people with all types, degrees, and combinations of disability. These guidelines also make Web content more usable by older individuals with changing abilities due to aging and often improve usability for users in general.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/887/1*0dPT27VguEF2E4sKxUZGpQ.png" /><figcaption><a href="http://The skill of designing for accessibility isn&#39;t meant to be &quot;sexy,&quot; it&#39;s an ethical principle of design. The things we find &quot;sexy&quot; across industries often reflect a privileged user, one with the right characteristics, class, opportunity, and ability. When we talk about users with disabilities, the conversation gets less &quot;sexy&quot; for most people. Why? We must decenter the normalized user, that has no mobility, visual, cognitive, or social impairments and think about those who would have trouble with our designs and interfaces for various reasons.">Testing Xperts</a></figcaption></figure><p>The current version is WCAG 2.0, which builds on WCAG 1.0. The document outlines the principles, guidelines, and success criteria that empowers technologists and stakeholders to employ best practices for creating accessible web interfaces.</p><p>With that context, I’ll dive into the seven things I learned.</p><h4>7. Most designers have not read WCAG</h4><p>Upon interviewing a particular designer, I asked the question — “Out of 100, what percentage of designers do you think have read WCAG?” Her genuine answer — “. . . 5%,” and that was “being optimistic.”</p><p>The fact that the majority of designers have not touched WCAG led me to a couple assumptions: (1) Designers are not aware that the document exists, (2) Beauty and ingenuity takes precedent over functionality and accessibility, and (3) If they are aware, the length of the document deters most from reading it, even making them feel they are “wasting time.”</p><p>For a document to attempt to bridge the gap in information about accessibility, it was shocking to know that it was underutilized and even unknown.</p><h4>6. Accessibility != ‘color contrast,” even if it feels that way</h4><p>When I inquired about easy wins for accessibility, color contrast came up every time. This in itself was positive, but in conjunction with online research I found that accessibility is minimized to a conversation of color contrast.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*DLmdNRPuvPhQ40B2n9NgrA.png" /><figcaption><a href="https://accessibility.colostate.edu/color-contrast/#1506964235778-24a9e456-6e13">Colorado State University</a></figcaption></figure><p>My assumptions in this point lie in scalability, gender balance, and subject matter. Companies (especially scaled ones and those that wish to scale), whether conscious of WCAG or not, know that users experience various states of vision and they want these users on their interfaces. If you develop an interface that cannot be conveyed to a particular set of users, you lose their business — point blank.</p><p>My second assumption is that because color blindness affects men greater than women, (1 in 12 men versus 1 in 200<strong> </strong>women experience color blindness) in a field that is male dominant, it makes sense that men would design for something that affects a large number of them, creating a large conversation around it.</p><p>For designers, color is a large aspect of the work they oversee. In the various manifestations a choice of color arises, color-contrast exists within this wheelhouse. In addition, I found color contrast tools though simplistic in nature, can be easily utilized as plugins and online tools. I even found this cool <a href="https://indesignsecrets.com/viewing-color-blind-previews-of-pages.php">Adobe feature</a> that shows designers their work depending on various states of color-blindness.</p><p>Although this is a win for low vision and color-blind users, it minimizes the other aspects of WCAG. So say it with me — just because you are tagged for accessibility issues with color contrast, does not mean it is the sole aspect of accessibility that deserves your team’s attention.</p><h4>5. Accessibility is not “sexy . . . it’s a trend that never happened”</h4><p>At an UX event, I asked about accessibility and was told it was a “trend that never happened.” Is this Mean Girls? Are we Gretchen trying to make fetch happen?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*4592nRGrxFGyW7jWoYEqbw.gif" /></figure><p>The skill of designing for accessibility isn’t meant to be “sexy,” it’s an ethical principle of design. The things we find “sexy” across industries often reflect a privileged user, one with the right characteristics, class, opportunity, and ability. When we talk about users with disabilities, the conversation gets less “sexy” for most people. Why? We must decenter the normalized user, that has no mobility, visual, cognitive, or social impairments and think about those who would have trouble with our designs and interfaces for various reasons.</p><p>When we develop use cases for main features, we should be developing cases that solve problems for users experiencing accessibility issues. To adequately support our users, what appears “sexy” to us or our teams should not be a deciding factor.</p><h4>4. Accessibility is seen as reworking, red tape, and restriction</h4><p>When the word accessibility wafts into the ears of designers and developers, it is connected to backtracking, rework, and rolled eyes. Accessibility issues flagged at the end of a process when the design is living creates massive amounts of waste. Therefore anything to do with accessibility develops a negative perception and conversations about it is avoided at all costs or experienced in contempt.</p><p>Accessibility obtains the reputation of “red-tape” in industries that are mandated by the government to adhere to <a href="https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards">508 IT accessibility regulations</a>. Governmental agencies, educational institutions, and transportation companies are some examples of entities governed by 508. For designers in these industries, designing for accessibility is not an option it’s a requirement. Therefore, accessibility can become a checkbox, rather than a mindful consideration.</p><p>As restriction, designers are unable to utilize some color schemes, interactions, visuals, language, and reading orders simply because they are not accessible. As designers, here is where we choose sides — do we value visual appeal or accessibility? The answer to this question defines our trajectory and how we think about the impact of our designs on those who will interact with them.</p><p><strong>3. ARIA labels create conversation and a robust experience</strong></p><p>ARIA labels are an invisible coding element used to “<a href="https://stackoverflow.com/questions/22039910/what-is-aria-label-and-how-should-i-use-it">define a string value that labels the current element</a>.” In other words, it offers those using screen readers more context to labels that appear on the screen.</p><p>ARIA labels create conversations between UX designers and developers, two roles whose work has major implications for accessibility. When teams are large or departments rarely interact, ARIA labels can be used to express the intent of UX decisions to developers. With a better understanding of design decisions, developers are better supported to convey the intentions of UXers and can further refine ARIA labels to convey valuable information to users with screen readers.</p><p>This conversation empowers designers and developers to craft ARIA labels used in development in a way that offers low vision and blind readers with more context where necessary to provide an optimal experience. For instance, a graph would normally be read off in the order it appears on the screen. A screen reader’s functionality does not connect the graph with information in prior paragraphs or create a story for the user using the graph. An ARIA label can solve this problem offering these users a more holistic experience that considers how they will receive the information.</p><h4><strong>2. Accessibility is not always given visibility under the umbrella of inclusion</strong></h4><p>In a conversation about inclusion, we need to talk about accessibility. When inclusivity becomes a conversation solely about race and even gender identity and sexuality, we erase disabled designers, developers, and more who exist within the intersections of these identities.</p><p>In conferences and conversations where accessibility is the topic, we must train ourselves to step out of the code and design, ensuring there are representatives of disabled users on our teams, conferences, events, and usability tests.</p><p>Like anything, talking about the people we want in the room does only so much. Make moves and noise to ensure these people are beside us.</p><p>Don’t tack on disabled users as an after thought, create a space for <em>them</em> to be heard and create<em> their </em>narrative.</p><h4>1. Accessibility-first is the best way to design for accessibility.</h4><p>Hate having to re-do work? Want to be a good human and cater to a group of users often forgotten? Want to be ethically responsible as a technologist and designer?</p><p>Design <strong>accessibility-first</strong>. Doing so is beneficial to all users, ensuring a highly functional and accessible experience. You guarantee all users despite ability can access information effectively and efficiently.</p><p>When you put accessibility-first, you create a mindful and aware ethos on your team that dissolves the “design for designs sake” mindset and centers multifaceted users in the forefront of our minds.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff51076%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Ff51076%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Ff51076%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href">https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4715af78f68a" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/7-things-i-learned-creating-an-accessibility-guide-for-designers-4715af78f68a">7 Things I Learned Creating an Accessibility Guide for Designers</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Inter[tech]tionality: Checking our Design]]></title>
            <link>https://medium.com/@ambernechole/inter-web-tionality-checking-our-design-97f34a730b68?source=rss-f7f1ba6dae13------2</link>
            <guid isPermaLink="false">https://medium.com/p/97f34a730b68</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[intertechtionality]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[people-of-color]]></category>
            <dc:creator><![CDATA[AmberNechole]]></dc:creator>
            <pubDate>Fri, 29 Dec 2017 02:38:25 GMT</pubDate>
            <atom:updated>2018-08-26T05:55:08.076Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Check Yourself: Evaluate your intentions and plans before you go and fuck up someone’s life with your subsequent actions.</strong></p><p>In 2018, designers should be openly “checking ourselves” when creating.</p><p>When I first published this article, I was immersing myself in UX and connecting user-centered design and Afrocentric research methodology.</p><p>Now, nearly six months later, I wanted to refresh the article because (1) I just completed an internship at a design agency as a user experience designer and (2) I came across a tweet that voiced my sentiments perfectly.</p><h3>Stephan Rosger on Twitter</h3><p>Designers should be able to pick apart and identify sociological, political, environmental repercussions of a design (and the company commissioning the design) just as well as they can pick apart code, typography, colour, or layout.</p><p>I thought it was important to include one of the rebuttals of this tweet. Not because I want to put this person on blast, but because this is what many people may think.</p><h3>Bruno Maag on Twitter</h3><p>@Rosger I like the sentiment but we&#39;d never get out of Uni. We&#39;d have to study sociology, political and environmental sciences, and whilst we&#39;re at it why not behavioural as well? Let&#39;s focus on design, solving the given problem.</p><p>Having a lens on design that is sociological, political, and environmental should be expected — especially when we are tasked to solve problems that affect users.</p><p>For too long, people have created our physical and psychological world without care for the people in it. Social constructs that maintain systems of oppression are parallel to the social infrastructure created to separate people geographically based on race and class.</p><p>As designers, if we don’t think critically about how what we design will affect our users, we allow our ego to overrule the user’s needs.</p><h4>The Fact of the Matter</h4><p>As designers of any type, we must understand how a global history of white hegemony and patriarchy, affects the way we live and create the experiences we are in charge of.</p><p>The truth is, user centered design will never be user friendly if the people in the room (1) Look the same and (2) fail to adequately capture the context of users.</p><p>Ideas from respected cultural designers (scientists, scholars, artists, explorers+) designed theories and frameworks that served as the backbone for things like phrenology and social darwinism labeling black and brown bodies as less than in human hierarchy. Early American psychologists created <a href="http://www.pbs.org/wgbh/aia/part4/4h3106t.html">drapetomania</a> to explain an enslaved person’s desire for freedom.</p><p>When we solely “solve the problem” in a way that fails to capture the humanity of our users and their unique intersections of identity we perpetuate the same systemic racism found in the subjects of science, art, politics, medicine, and more.</p><h4>Design Reflects Those Designing</h4><p>In a field like UX, where creative and functional thinking meet, it is disappointing that it reflects the same inequality and short-sited thinking of most research. Sentiments aside, it does not surprise me.</p><p>In 2016, <a href="https://medium.com/u/50e39baefa55">Fabricio Teixeira</a> shared these demographics about the design field as a whole answering the question “Is diversity a problem in the design industry,” his answer — yes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1002/1*alodcxnkrzjcezhDYb3waw.jpeg" /><figcaption>Source: <a href="https://www.designweek.co.uk/issues/25-31-january-2016/what-does-the-design-industry-look-like/">Design Week</a></figcaption></figure><p>In 2017, Triangle User Experience conducted research involving their own UX professionals, Ladies That UX-Durham, and the surrounding public. Although in a specific geographic range, the findings suggest a trend in both design and UX markets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/641/1*bsr7AciJ-qD12gUKzVXouQ.png" /><figcaption>Source: <a href="https://triuxpa.org/resources/Pictures/Triangle%20UX%20Salary%20Survey.pdf">Triangle User Experience Association</a></figcaption></figure><p>Unsurprisingly racial identity of UX professionals is overwhelmingly Caucasian (90.4%). The final 10% includes Black or African-American (5.5%), Asian (4.8%), and Hispanic or Latino (3.4%). Gender on the other hand fared better in this survey and may suggest that depending on the city gender differences can fluctuate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/583/1*O-IH7B5X6aMLvl-2UV6vTw.png" /><figcaption>Source: <a href="/service/source: Triangle User Experience Association">Triangle User Experience Association</a></figcaption></figure><p>Now what does this have to do with user centered design? If the designers in the room look the same, have similar life experiences, and aren’t questioning why they are the only ones in the room — WE HAVE A PROBLEM.</p><p>Design companies that are overwhelmingly white and male in C-Suite positions reflect the diversity of clients and ethos of that company. If you are not in the room, how can your experience be accurately leveraged?</p><p>In short, marginalized people are not in design spaces, it’s likely they are not getting designed “for” and will not be in the designer’s mind because they do not have their perspectives or life experiences.</p><h4>My Idea: Inter[tech]tionality</h4><p>After having my first immersive UX experience and doing work on my own the layers of my education and experience paint a clear picture.</p><p>Theories found in humanities courses that center in the experiences of marginalized people should be THE required reading material for any type of user experience work. In these articles, scholars deconstruct hegemonic identities of marginalized people creating space for self-determination and developing narratives true to their experiences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MtYts0uWUCH-_-hHFp8e_w.png" /><figcaption><a href="https://miriamdobson.com/2013/04/24/intersectionality-a-fun-guide/">https://miriamdobson.com/2013/04/24/intersectionality-a-fun-guide/</a></figcaption></figure><p>If you have not heard of the term intersectionality, in short it is the idea that — people are an amalgamation of various identities and cannot be divided between them. Depending on the intersection of these identities one can experience marginalization in a heightened manner.</p><p>If you want to read more, the term was fleshed out by lawyer Kimberlé Williams Crenshaw in <a href="https://chicagounbound.uchicago.edu/cgi/viewcontent.cgi?article=1052&amp;context=uclf">this</a> article and popularized in Patricia Hill Collin’s <a href="https://www.feministes-radicales.org/wp-content/uploads/2010/11/Patricia-Hill-Collins-Black_Feminist_Thought__Knowledge__Consciousness__and_the_Politics_of_Empowerment__Perspectives_on_Gender.pdf">Black Feminist Thought.</a> Both are great resources to start understanding the basis of inter[tech]tionality.</p><p>My idea is to actively apply intersectionality to the design thinking process creating a more holistic view of users, rather than seeing them compartmentally and only in the context of our products. Users use different applications and devices, they utilize various machines and have habits, and they also identify in a certain way and come from a unique intersection of identities. For effective UX, you must assess the whole person.</p><p>In my future work, I am interested in developing what inter[tech]tionality can mean for tech and design spaces — especially as an African American woman.</p><p>With inter[tech]tionality, we take conscious responsibility for our creativity and it’s outcomes.</p><p>We do not shy away from uncomfortable conversations about race, class, language, gender, sexuality, accessibility, and other pivotal questions.</p><p>We do not erase people because we don’t want to be “bothered” or “bogged down” by their perceived complexity.</p><p>We stop seeing accessibility as red tape, and start thinking about people of different mobility, neurological diversity, and physical ability.</p><p>We recognize that our field is mainly white and male and it’s necessary to advocate openly for see diverse identities in the room — and not all in one person.</p><p><strong>In a global community where identity is being flushed into a continuum, designers cannot afford to continue allowing old narratives to inform their decisions or solutions to their problems.</strong></p><p>The nature of UX is not static — it’s iterative processes should inform not only design decisions but also our personal ethos.</p><p>To “think” like our users, we must be honest about our internal biases preventing us from seeing stereotypic generalizations, skewed psychological frameworks, and unauthentic voice reflecting the gap demographically in the designers present in the industry.</p><p>So, it’s not the point of thinking “black,” “asian,” “hispanic,” or “queer” — its the point of allowing folks with intersectional identities take up space in design as a way to create more bold, inclusive, and culturally relevant design, interfaces, and user experiences.</p><p>While we must define our audience, it should not be at the expense of another’s identity and voice.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97f34a730b68" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>