<?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 Mandi Gonzalez on Medium]]></title>
        <description><![CDATA[Stories by Mandi Gonzalez on Medium]]></description>
        <link>https://medium.com/@redheadlatina?source=rss-66adf09177c0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*I1Xm6buw-4uysq7u2OxtNg.jpeg</url>
            <title>Stories by Mandi Gonzalez on Medium</title>
            <link>https://medium.com/@redheadlatina?source=rss-66adf09177c0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 10:58:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@redheadlatina/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[Experiencing IBM Design Thinking]]></title>
            <link>https://medium.com/@redheadlatina/experiencing-ibm-design-thinking-fa1d520c3bf9?source=rss-66adf09177c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa1d520c3bf9</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ibm]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Mandi Gonzalez]]></dc:creator>
            <pubDate>Tue, 02 Feb 2016 01:30:08 GMT</pubDate>
            <atom:updated>2016-02-02T01:30:08.801Z</atom:updated>
            <content:encoded><![CDATA[<p>Last week I attended an IBM Design Thinking workshop held at the University at Michigan. And if I had to summarize what I learned into one word, it would definitely be<strong> “empathize”</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/0*wxtAc3NvaDI9BLOz.jpg" /></figure><h4>A New Approach to Thinking</h4><p>IBM Design Thinking is not an old concept to IBM. In fact, it was introduced in 2011, initially inspired by IDEO’s way of thinking, and has recently released a new version of its “design thinking” process, all focused on creating experiences made for the user in mind. Every product should always have the user in mind, so you have to wonder what’s stopping some companies from taking a more user-centered approach to product development.</p><p>So, IBM knows what’s good! I was pretty impressed to see a company this large understand the importance of user-centered design. The workshop I participated in brought together students from the Stamps School of Art &amp; Design &amp; the School of Information, and ran for about 3 hours.</p><p>To start the hands-on portion, we were given a persona of a financial advisor in her later 30s, seeking to better understand millennials in order to connect with them better with their wealth management. I liked seeing this persona because it addressed this stakeholder that isn’t thought of in the context of this problem. It was also the hardest to empathize with, given everyone in the group was still in school and is still a millennial, but that’s what made it challenging and interesting, too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*1lLkT-_M67V2CzmxZbGHOA.jpeg" /><figcaption>Our scenario and persona we were given to work with.</figcaption></figure><p>Now the fun part begins…..Empathy mapping!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*HnvHbdvdZISmeC-QBSpgBw.jpeg" /><figcaption>Empathy mapped with grouped themes within.</figcaption></figure><p>What does the user say, do, think, and feel in the context of their work? This question gets answered with the empathy mapping exercise &amp; boy, what a great way to empathize with the user.However, we were all making assumptions about this persona (and it was super challenging to do so, too, given we don’t know what an actual financial advisor does in the day-to-day), but with the hopes that we could validate them later (that is, if your company has the time and resources to do so).</p><p>All in all, this is super cool stuff. I really felt like I was in her shoes. This is the stuff I definitely want to implement this type of empathizing in later projects.</p><p>Once the empathy map was done, we then grouped the post-its into themes. And then once themes were established…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3D4603nA6p4hrGTD-YKgNQ.jpeg" /></figure><p>We scoped how the user could live out this scenario of connecting with millennials by elaborating on the actual steps they would take, what they do, how they think, and what they feel at each step. This helped us see where pain points could possibly exist for the user. For example, as she tries to connect with people in her network, she might be thinking “did I do this right?” and feeling anxious in the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*klvgSg0jEhnSv2eFWDZ7RA.jpeg" /><figcaption>Grouping and pain point seeking.</figcaption></figure><p>The last step in this design thinking workshop was to take those pain points and translate them into possible solutions. Who are the kinds of people that could benefit from this solution, apart from our persona, but relevant to them? What kinds of solutions are we proposing? And lastly (and unfortunately not pictured below), what is the “wow” factor that sets this proposed solution apart?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*cxBLvVUIdbvOiXWG4uL5ew.jpeg" /></figure><p>This was the fun part for me, since it was time to use the “thinking” and “empathizing” that we did about our user and translate that into solutions. I love this idea of having a “wow” factor that needs to be measurable, too.</p><h4>In Summation…</h4><p>I had done empathy mapping before, but not in this context of seeing how empathy mapping, the very first step, can ultimately assist in the creation of the design solutions. I left the workshop feeling super inspired, looking forward to seeing how I could take this particular user-centered approach and apply it to the projects I’m working on this semester and beyond.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa1d520c3bf9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Music Shuffling — A Design Decision]]></title>
            <link>https://medium.com/@redheadlatina/answering-design-decisions-part-1-46be1fad2554?source=rss-66adf09177c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/46be1fad2554</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[music]]></category>
            <category><![CDATA[shuffle]]></category>
            <dc:creator><![CDATA[Mandi Gonzalez]]></dc:creator>
            <pubDate>Tue, 17 Nov 2015 22:41:24 GMT</pubDate>
            <atom:updated>2015-11-17T22:42:06.150Z</atom:updated>
            <content:encoded><![CDATA[<h4>Why does the “shuffle” feature exist on music listening platforms?</h4><p>The answer can be as simple and obvious as “it can be for people that have no idea what to listen to.”</p><p>But I think there might be more to it.</p><p>One day I was looking at all of my 50+ Apple Music Playlists. To be clear, I don’t claim to have the largest music library in the world, but I’ve been curating music since the early 2000s (elementary school days!) and I’ve amassed quite a diverse library. With the addition of Spotify in my life, it’s made my life more complicated. As an avid music listener, this large amount of music can be overwhelming.</p><p>There was a particular day where I had no clue what to listen to. I decided to take a look at my 90s Nostalgia playlist since I hadn’t really accessed these songs in a long time. Once I started looking at song titles, I started to play sample of the songs in my head. It was involuntary and I subsequently ended up not listening to a majority of the songs on that playlist that day. That’s no fun. I then decided to use the shuffle feature enabled on the entirety of my playlist. It then became a much more enjoyable music listening experience, not knowing what to expect next, but knowing you’ll most likely enjoy the song since you downloaded it yourself.</p><h4>The Answer</h4><p>The Answer? The element of surprise. Not knowing what to expect next. I believe it’s what makes the radio really appealing, other than discovering what’s the latest and new in music. Recall versus Recognition. It’s easier to recognize what a particular song will sound like by looking at its title rather than recalling it out of thin air (I think).</p><p>They should do this with Netflix. They should do this with your refrigerator. Think of the times you looked through the Netflix database and could never decide what to watch. Think of the times you looked at your refrigerator, filled with food, and leaving it empty-handed.</p><p>Imagine the shuffle feature being applied to other products other than your music libraries. Shouldn’t it be fun to not know what to expect next?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=46be1fad2554" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Guerrilla Usability Testing at a Startup]]></title>
            <link>https://medium.com/theuxblog/guerrilla-usability-testing-at-a-startup-63c36ec1ec4f?source=rss-66adf09177c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/63c36ec1ec4f</guid>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Mandi Gonzalez]]></dc:creator>
            <pubDate>Thu, 09 Jul 2015 18:08:16 GMT</pubDate>
            <atom:updated>2016-10-03T06:04:47.501Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q4tEovH0qCQp9um9Y8EkkQ.jpeg" /></figure><p>My UX partner and I conducted these guerrilla usability tests in downtown Ann Arbor, MI. We had never done these kinds of tests before, having been used to scheduled tests, so it was a little daunting. There are a couple of great articles on the web regarding tips and tricks on how to effectively do guerrilla usability testing that helped me out. However, the more tests we did, the more confident we became, and we had developed our own strategies, from approaching strangers to wrapping up the tests.</p><h4>How to pick out potential users</h4><p>Approach folks that are by themselves, and not in the middle of a conversation with someone else. If you can sneakily glance at their computers, see if they are on social media. If they are, they will likely have time to speak with you since Facebook isn’t quite as important as that paper they are supposed to be writing. Take a look at their body language, too. Do they look tired? Are they laying their hand on their head? <em>The idea is that you don’t feel as though you are interrupting them doing something important.</em></p><p>Make sure you don’t discriminate, either. Out target audience is incredibly broad, so we made sure to get a representative set of users. However, being so close to campus meant we were running into more students than usual (regardless of age), so it’s best to note that as a constraint.</p><h4>Approaching Potential Users</h4><p>As current master’s students, we found it helpful to introduce ourselves as “master’s students interning at a startup” versus simply saying “we are interns.” I guess they are more trusting of you since the University of Michigan is a little bit more popular than our new startup that they’ve never heard of before.</p><p>When asking them to help you, try to stay away from saying the words “evaluate” or “test”. You don’t want users to immediately start thinking they are going to be tested on. Instead, we found it helpful to frame it by asking them they had time to answer a couple of questions about the app. <em>Make it as casual and friendly as possible.</em></p><p>Also, don’t forget to smile. :)</p><h4>Starting the Test (after they have said yes)</h4><p>It might sound a lot, but have your “moderator script” memorized completely (if you are having trouble memorizing it, it might be because it is too long, which in that case, you should probably make it more concise). However, it is okay to have it printed out just in case. Otherwise, <em>memorize to make your communication with the user more comfortable.</em> If you have a note taker with you, they should have their laptop open already (during the “approach” stage).</p><p>If it is a mobile prototype you’re testing, make sure to put your smartphone on airplane mode. You don’t want the user to be interrupted by any message notifications.</p><p>You want to be cognitive of time, right? These are users that are volunteering their time for you, so don’t waste away 3 minutes with introductions and set-up. Be prepared. Turn those 3 minutes into 30 seconds. Alternatively, you can have your note taker setup everything while you give more info about the app and test to the user.</p><h4>After the Test</h4><p>If it is a 5 minute test, there’s no need for incentives. If it is a 15–20 minute test, you may need to buy a couple of $5 Starbucks Gift Cards for users taking out that much time to do the test. Of course, make it clear during the approach phase that you will be giving out these gift cards if they participate.</p><p>Also, don’t be afraid to give them your business card (more reason to have business cards in your wallet!). It gives them some more trust about what they just participated in and it gives them the ability to contact you if they were pretty starstruck by the prototype.</p><h4><strong>Wrap-Up</strong></h4><p>Be aware that this isn’t a comprehensive lists of things to know about when doing these guerrilla usability tests. A simple Google search will get you a lot of great resources on the topic, but it is only really until you get started on these tests do you start to figure what works and what doesn’t. I’m an introvert, so having these particular strategies helped me reduce the light anxiety I get from doing these types of “non-scheduled” tests. Not only that, but with all this experience doing tests, I can say confidently that I am a much more experienced UX researcher now than I ever was before.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=63c36ec1ec4f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/theuxblog/guerrilla-usability-testing-at-a-startup-63c36ec1ec4f">Guerrilla Usability Testing at a Startup</a> was originally published in <a href="https://medium.com/theuxblog">theuxblog.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Interning at a Startup — Part 1]]></title>
            <link>https://medium.com/@redheadlatina/interning-at-a-startup-part-1-67ed77283360?source=rss-66adf09177c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/67ed77283360</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Mandi Gonzalez]]></dc:creator>
            <pubDate>Sun, 28 Jun 2015 20:39:42 GMT</pubDate>
            <atom:updated>2015-06-28T20:39:42.904Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m learning a whole lot as a UX intern at JOOL Health this summer, a new mobile health startup founded by Dr. Vic Strecher (if you get a chance, read Vic’s book <em>On Purpose: Lessons in Life and Health From the Frog, Dung Beetle, and Julia.)</em>. Here’s some background: there’s research to support the idea that having a life purpose and living by it will help you live a longer, healthier life than those who don’t.</p><p>The app that we are developing at JOOL Health seeks to help people do just that. And so far it’s amazing.</p><h4><strong>The Work Environment</strong></h4><p>This work environment is one I’ve never worked in before. My previous internship experiences had me working in cubicles, mostly all day long.</p><p>The JOOL experience is quite different. As I describe it, everyone is working in the same room, at a really long table. We do have our own spots at this table, but there’s no walls or doors to hinder the collaboration that ends up happening at this table. I love it so much that it might become a factor when I start looking for some UX Jobs in the spring.</p><h4><strong>UX Testing</strong></h4><p>My fellow UX partner and I have been doing a lot of UX testing and prototyping lately. And we’ve been learning so much about it that we know coursework wouldn’t have completely taught us about.</p><p>For starters, we have learned that even the most subtle cues in body language can tell a lot about the feelings of a user while they are using an app. It’s one of those things that make in-person testing much more valuable than remote testing. We’ve had quite a few user rest their head on their hand while using our prototype; could this mean that using the app might be more tedious than expected? Maybe. It could be an opportunity to delve deeper in the post-session questions.</p><p>We are also slowly learning how to develop the best user test plan that we can. I made a realization about how the flow of the questions we ask at the end of the test can inadvertently prime the users to answer some questions differently. For example, say we wanted to know how users are defining the purpose of the app. We’d ask a question like that towards the beginning of the post-session questionnaire, not the end, right? If we did so towards the end, we might inadvertently answer that question for them if we had to be more clear about a particular question towards the beginning. UX Research is a type of science that I need to do more reading on, in addition to reflecting more on the actual UX tests that I moderate or take notes on.</p><h4><strong>What’s Next?</strong></h4><p>I am still learning more and more about UX through this internship experience at JOOL Health. I love that UMSI (Michigan’s School of Information) is encouraging us to be reflective about our experiences. I sure am learning a lot from them.</p><p>I can’t wait to learn even more in the next 2 months.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67ed77283360" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>