<?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 Kyle Simpson on Medium]]></title>
        <description><![CDATA[Stories by Kyle Simpson on Medium]]></description>
        <link>https://medium.com/@kylesimpson?source=rss-b1a69dee778d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*1-D_F8zpAM6qmGxa.</url>
            <title>Stories by Kyle Simpson on Medium</title>
            <link>https://medium.com/@kylesimpson?source=rss-b1a69dee778d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 10:08:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kylesimpson/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[Device Prototyping]]></title>
            <link>https://medium.com/@kylesimpson/device-prototyping-7479e5da7c96?source=rss-b1a69dee778d------2</link>
            <guid isPermaLink="false">https://medium.com/p/7479e5da7c96</guid>
            <category><![CDATA[prototyping]]></category>
            <dc:creator><![CDATA[Kyle Simpson]]></dc:creator>
            <pubDate>Thu, 25 May 2017 23:12:33 GMT</pubDate>
            <atom:updated>2017-05-25T23:12:33.201Z</atom:updated>
            <content:encoded><![CDATA[<p>This week in HCDE 210 we worked on deice prototyping. Using prototyping kits called littleBits, we started off with a tutorial on how to use the kits, and quickly moved into creating basic prototypes for one of three potential user bases. The user group my partner and I decided to think about was pet owners who are concerned with their pet’s activity levels.</p><p>We started out by thinking of typical ways people get pets mobile. We noticed that most pets respond to light and or sound, so we wanted to incorporate these into a prototype. Before we got to actually putting pieces together, we wanted to draw out a potential situation where a sound/light system might come in handy. We thought of the following system and solution. Under a pet’s bed, there will be a button that counts each time the pet lays down. One the button is clicked three times (meaning that the pet has sat three times) a sound will play. This interaction looked like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wVR473wJHNSgqMqlRAVBiA.jpeg" /></figure><p>Now that we had a basic idea for what we wanted our solution to do, we had to begin to prototype. We first thought about the littleBit pieces we had and how they could work together to perform our function. We came up with the following schematic that would do exactly what we wanted:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m-Lwl9LA-FrksWrN5-417Q.jpeg" /></figure><p>This sketch easily translated into a physical prototype that looked like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c7d8U-uzsIzGjuOprh9NPg.jpeg" /></figure><p>Notice that in the physical prototype, we decided to add a light element that would only play when the speaker started playing. We thought that combining sound and light would be more likely to attract the attention of the animal, so we added the functionality.</p><p><strong>Big Picture</strong></p><p>Looking at the prototyping process as a whole, I really enjoyed getting to use littleBits. I think that the kits are perfect for beginners who want to really easily connect pieces and learn about circuits, plus these kits made prototyping super easy for us. Meanwhile, they were durable and portable, so we didn’t have to be overly concerned about accidentally breaking one of the pieces.</p><p>As a bit of a side note, the studio setting and the whiteboard tables made ideating really convenient and efficient, especially for this activity. My partner and I not only had a great time ideating through potential solutions, but felt empowered to erase everything and start over if something wasn’t working quite like we thought it would. I think that the setting was perfect for this week’s studio, and I wish that everyone experimenting with littleBits had the experience my partner and I had in the studio.</p><p><strong>Looking Ahead</strong></p><p>Thinking about potential applications of this process in the future, I am highly considering buying a littleBits kit myself just to have around to play with in my spare time. I think that these kits opened up a whole new world of ideating and easy-prototyping for me, and I hope to think of some cool new ideas in the future.</p><p>Meanwhile, I think that loads of prototyping situations could benefit from using littleBits. A lot of times, in this class and in professional settings, there is a need for an easy, medium-fidelity prototype, and I think that littleBits has nailed the middle ground of being easy to use and actually functional. On the other hand though, I don’t think littleBits would have been much use a few weeks ago when we were primarily working on interface development since the littleBits aren’t programmable, so they definitely have a limit in their usability.</p><p>All in all, this was definitely the coolest studio session we have had in this class. Getting hands-on experience with a really cool, and really easy, prototyping medium was an incredible experience, and one I hope to get again soon.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7479e5da7c96" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Data Visualization]]></title>
            <link>https://medium.com/@kylesimpson/data-visualization-2ac8273824c5?source=rss-b1a69dee778d------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ac8273824c5</guid>
            <category><![CDATA[data-visualization]]></category>
            <dc:creator><![CDATA[Kyle Simpson]]></dc:creator>
            <pubDate>Thu, 18 May 2017 22:42:40 GMT</pubDate>
            <atom:updated>2017-05-18T22:42:40.544Z</atom:updated>
            <content:encoded><![CDATA[<p>This week in HCDE 210, we got some practice doing data visualization. As a precursor, data visualization and data science are two of the programming fields I love the most, so I was obviously excited to work with Tableau this week.</p><p>At the beginning of the week, we were given the City of Seattle’s 911 Incident Response data set which was full of interesting fields, reporting everything from stray animals to burglaries. Given this data set, it was our job to think about a group of users who would find this data set useful in answering some potential questions of theirs. When I say potential questions, I do mean potential, as we did not have the opportunity to meet with any of our user groups to see what questions they actually have, so we all did our best to make some safe assumptions to what they all might be curious about.</p><p>The user group I chose to work with was the Cascade Bicycle Club. Being an avid bike rider myself, but not a member of the CBC, I already had some questions on my mind that I’m sure the CBC would also be curious about. A few of the questions I wanted to try to answer included: 1) where do most of the bike thefts happen around the U-District, 2) on what day do most of the motor vehicle accidents happen around the U-District, and 3) in which month is harassment lowest in the U-District? With these three questions in mind, I utilized the 911 Incident Response data set to create some visualizations to help answer these questions.</p><p>The first visualization was made to see where most bike thefts occur around the U-District. I used the latitude and longitude recorded from the 911 data, and paired that with the number of reported incidents. What the following visualization displays is the number of reported incidents (denoted by size of the circle) in relation to where they occurred geographically, as well as a brief commentary on the data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/732/1*Fz4xO9kVEnyT-2HvPt3tFw.png" /><figcaption>Visualization created thanks to the City of Seattle’s 911 Incident Response data.</figcaption></figure><p>The second visualization was made to see the weekdays when most motor vehicle accidents occur around the U-District. As a bike rider myself, I was specifically curious about this information as I would not want to ride on days when motor accidents are more likely to occur, seeing as I could easily be hurt in the process as many drivers ignore cyclists. So, after filtering the 911 data for only motor accidents, and changing the event date to specify by weekday, the following visualization was produced.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*ac2oUbmaXS874xivcys9aw.png" /><figcaption>Visualization created thanks to the City of Seattle’s 911 Incident Response data.</figcaption></figure><p>The third and final visualization was made to see in what months harassment cases were the lowest around the U-District. As a cyclist, we are prone to harassment by drivers, pedestrians, and other cyclists, so knowing this information might be helpful in planning out cyclist community events and other long rides. Looking again at the total number of reported incidents in the U-District, this time broken down by month, the following visualization was created.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*c6ln7GFAAlsHKvNnV0NikA.png" /><figcaption>Visualization created thanks to the City of Seattle’s 911 Incident Response data.</figcaption></figure><p><strong>High-Level Reflection</strong></p><p>My absolute favorite part of this assignment was getting the opportunity to work with Tableau and doing more data visualization. Data science is something I am incredibly passionate about, so I love to work with numbers at any chance I get. I have a bunch of experience working with R, a function-based data analysis programming language, and their data visualization packages, but when I heard that we were going to get to work with Tableau, I was beyond excited.</p><p>Reflecting on my experience using Tableau, I mostly enjoyed the experience and Tableau’s user interface, and my only complaint was that the program was too templated. Having a lot of experience working with a very customizable platform for data visualization, I at times felt trapped by the options available to create visualizations. However, I definitely understand that Tableau is a great introductory platform for people who are just getting started with data viz, who don’t want to learn a bunch of programming. The moral of the story here is that while I was slightly bored with the basic functions Tableau offers, I appreciated the fact that anyone could log on and create some really cool, and interactive visualizations, with relative ease.</p><p><strong>Moving Forward</strong></p><p>Looking to the future, I definitely want to do more with data science and data visualization. While I am not sure that I will use Tableau as my first choice of visualization software, knowing the basic functions will be of use if needed in the future. I think that a lot of projects could potentially be bolstered with the use of data visualizations, and interactive ones as an added bonus. Since humans are inherently visual creatures, and vision is our highest fidelity sense, structuring arguments around visualized data is an incredible superpower to wield, and one that should be done responsibly. With intuitive and east to learn visualization tools like Tableau, it is even more important that we be verifying our information, and to remember that just because something looks pretty doesn’t always mean that it is correct. We should be using data for social good, and not just to promote our own agenda, and I hope that Tableau will help many in their quest to use data for social good.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ac8273824c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[User Research]]></title>
            <link>https://medium.com/@kylesimpson/user-research-293b5e82fc66?source=rss-b1a69dee778d------2</link>
            <guid isPermaLink="false">https://medium.com/p/293b5e82fc66</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Kyle Simpson]]></dc:creator>
            <pubDate>Thu, 04 May 2017 22:47:09 GMT</pubDate>
            <atom:updated>2017-05-04T22:47:09.947Z</atom:updated>
            <content:encoded><![CDATA[<p>This week in HCDE 210 we worked on our user research skills. Doing user research is all about understanding the true needs or the user, with the ultimate goal of making more informed design decisions to make a better end product. Our challenge for the week was to go and do user research by observing commuters and taking notes of their behaviors, what we called “practices”. We were specifically looking for commuting “practices”, and these practices could be categorized as any of the following: “(1) physical and mental activities of human bodies, (2) the material environment, (3) artifacts and their use, (4) contexts, and (5) human capabilities, affinities and motivation”. I found that reminding myself of the definition as I was conducting my research helped me to be on the look out for more nuanced behaviors, so the specificity of the prompt was more helpful than hindering this week.</p><p>So I chose to observe commuters bussing, specifically from the two bus stops on the corner of NE Campus Parkway and University Way, from about 5:30 to just after 6:15 on Wednesday May 3rd. The 49 and 70 routes stop at one bus stop, and the 65, 75, and 372 stop at the other. I was standing among the commuters waiting for their busses, taking notes in the yellow books we got from class. For the most part, I wrote down entire thoughts as I observed behaviors, because for me, the entire thought helps me remember exactly what I was observing, rather than making a sketch or writing random words. Here are a couple of pages of notes that I took from the almost 45 minutes I spent observing commuters:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-gigp38jIcgUatpFwg190Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0Db4cL50V5b99QpcPz6zVA.jpeg" /></figure><p>From these pictures you can see a few of the observations I made. Some of the more interesting/notable ones include that it was a majority of female riders waiting for busses, that most people were on some kind of electronic device, and that the 65, 75, and 372 busses were more popular than the 49 and 70.</p><p><strong>Reflection</strong></p><p>I found that doing observation-based user research was incredibly informative. I had done some previous user research, but it was completely through the use of a survey. The use of a survey was perfect for the particular type of data we were looking for, but there was an obvious disconnect between my research team and the participants. Doing observations and making notes of behaviors was a very different, and very helpful form of research. While “in the field” I definitely felt connected to those who I was surveying. I was putting myself in their shoes and entering their realm, which created very unobstructed data. There is always the possibility that my own biases obstructed the ways in which I was able to observe those around me, however, reminding myself that I may be looking at a situation in a biases manner helped me regain perspective.</p><p>After spending time observing commuter behaviors, I have a couple of questions about ways to improve people’s commutes. First, I’m curious how we might redesign bus stops to encourage riders to sit next to each other (or at least not avoid each other), or to redesign to make the space seem more welcoming to riders. One of my biggest take-aways from my observations was that riders did not want to interact with other riders, and also that everyone seemed to be bothered by the presence of other riders. If there was ever one person sitting on a four-person bench, it was very rare that anyone else decided to sit next to them. I noticed similar trends on the busses in that no one wanted to sit next to anyone else, so I wonder if there are any design choices that could be made by observing the motives behind why riders chose to interact with other riders.</p><p>I also can’t help but note something I could have changed about where I observed from that could have potentially created better, maybe more unbiased observations. So I mentioned earlier that I stood among the commuters at they waited for their busses. Because of this, I was more inclined to notice what was happening directly around me, and pay less attention to what was happening on the outskirts of the crowd. I think that if I had positioned myself slightly further away with a better vantage point of the entire crowd that I might have gathered some more interesting observations.</p><p><strong>Thoughts for the Future</strong></p><p>I think that user research is invaluable when trying to understand a potential user base, and what they might need from a potential solution. In my two experiences of performing user research (the survey and making observations) I think that both provided data that the other did not. In the survey, we mostly gathered quantitative data (the numeric responses that help us understand a demographic), and in the observation, I mostly gathered qualitative data (things I watched and interpreted that don’t necessarily give numeric data). Each method of research was beneficial alone, but I think that a wholistic research method would combine both, gathering qualitative and quantitative data.</p><p>I think that for any project where you are creating a product of some sort, user research can be beneficial. No one person knows all the answers to a problem, and no one person understands all the problems or needs of every potential user. Doing user research is one of the best ways to learn about all of these things, and I would recommend doing research to everyone in the process of creating a product.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=293b5e82fc66" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ideation]]></title>
            <link>https://medium.com/@kylesimpson/ideation-1cba69d660a9?source=rss-b1a69dee778d------2</link>
            <guid isPermaLink="false">https://medium.com/p/1cba69d660a9</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Kyle Simpson]]></dc:creator>
            <pubDate>Thu, 27 Apr 2017 23:33:02 GMT</pubDate>
            <atom:updated>2017-04-27T23:33:02.015Z</atom:updated>
            <content:encoded><![CDATA[<p>This week we worked on the ideation process. In a basic sense, ideation is the rapid generation of ideas, and we used a couple of techniques to help curate the rapid generation. First, we welcomed wild ideas. Often times these led to the best solutions to a nuanced problem, so allowing for wild thinking was necessary. Second, we were reaching for quantity. When creating a massive number of ideas, it is statistically more probable to come up with a good one, so making tons of sketches is important. Finally, we wanted to combine and improve multiple ideas, to make a multi-faceted idea that could be better suited to solve our design problem. Taking these techniques, we were tasked with sketching various solutions to solve a problem for the mayor of Greenville.</p><p>So the mayor of Greenville has tasked us with coming up with a bunch of ideas to solve the problem of accessible transportation in Greenville. The assignment was open, meaning that we were not limited in the medium of our solution. It could be anything from a mobile application, to physical structures, and the freedom was helpful. We were first asked to come up with 10 divergent sketches of various potential solutions to the problem, and then take the most promising initial sketch to turn into 10 new convergent sketches branching off from the most promising initial sketch.</p><p>Looking through my initial 10 sketches, I had a few mediocre ideas, but most of them ended up being unhelpful. At times, I forgot that I was supposed to be ideating for accessibility, so some of my sketches got a little off topic. For example, the following sketch was one of my really bad ideas</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YRId4Xl-nzK0IMUVAuD_cg.jpeg" /><figcaption>Divergent Sketch #9</figcaption></figure><p>In this sketch, it was my idea to have GPS trackers on each employee’s car and an interface that let their managers know if they were going to be late to something, and for what reason. I now realize that this was super off topic, because it does not solve any accessibility problem, and maybe even creates a micro-management problem within a company. Needless to say, this was one I quickly disregarded.</p><p>Switching gears, there were a few very promising sketches that I thought could be potential solutions. My first idea was to have a wheelchair-chaining service where you just connected a wheelchair to a system and then ride behind a car for your commute.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1hfuvB7kHip3DtP71esHIA.jpeg" /><figcaption>Divergent Sketch #1</figcaption></figure><p>This would solve a few problems. First it would reduce carbon emissions since there would be less cars on the road, plus it would make commuting more accessible for the mobility impaired. I decided that this was not the most promising idea though, especially since this might cause more traffic accidents which would be the opposite of increasing commute time.</p><p>The idea I thought was the most promising was this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QCCQe1dM4DyQgehsdEsz3Q.jpeg" /><figcaption>Divergent Sketch #2</figcaption></figure><p>My thought was that these tubes would have multiple purposes, and could be specially fitted to meet many needs. They could also be either above ground or underground, so there are some options as to what people want to look at every day.</p><p>Now that I had decided on a most promising sketch from my initial trials, it was time to make 10 different iterations of the same idea. Most of these consisted of above-ground and underground options, but I think I ended with a pretty good solution. But before we get there, here is one of the really bad ones:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cgFANz01oEtQiCdZOWKJZA.jpeg" /><figcaption>Convergent Sketch #7</figcaption></figure><p>Again, I had an issue of getting off topic in the middle of these sketches, and this one really didn’t serve many purposes other than decreasing a need to walk between neighboring houses. This idea did not solve an accessibility need, nor was it even related to traffic. This idea is what some call a “dud”.</p><p>Finally though, I came to a good solution. This solution highly improved traffic around schools, and gave parents extra time for their commutes:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xIVNbfWtngjIdCRnxZZyXQ.jpeg" /><figcaption>Convergent Sketch #10</figcaption></figure><p>Basically, these would be underground pressurized tubes that would pick up students from various places around neighborhoods and get them to school quickly and safely. This would also give parents a lot of extra time on their commute since they would no longer have to drop their kid off at school. This could also be extrapolated to other cities where school transportation is even more scarce, helping to create a more educated society.</p><h4><strong>Thoughts on Sketching</strong></h4><p>I think that sketching is one of the most useful ideation techniques around. I have some experience with other forms (plain writing out of ideas, early on high-fidelity mach-ups, etc.), but the ease, cost effectiveness, and speed that comes with sketching has been unmatched. It’s so easy to just sketch an idea while you’re thinking about it, keep it in a journal or post it somewhere, and have a cheap, fast reference to an idea. The IDEO video is one great example of how sketching is invaluable to a team of designers trying to iterate through hundreds of ideas within a few hours. They could really easily draw a thought and present it, and since most people are visual learners, it helped immensely to be able to see the intent behind a verbally communicated idea.</p><p>I also think that it’s important to note that you don’t have to be good at drawing to effectively sketch an idea. I am a terrible artist, but sketching isn’t quite art. Sketching is a fancy way of taking notes that involved slightly more than a doodle to help communicate the idea. You can take a look at all of my drawings and see that none of them are particularly well done, but each of them, along with some form of written hint, effectively communicates the idea I had in my head.</p><h4><strong>Moving Forward</strong></h4><p>I think that sketching is really helpful almost every time a group, or even an individual, needs to rapidly think through multiple design ideas. Whether it be for divergent or convergent ideas, sketching can improve the process.</p><p>I am currently working on my application for the Informatics major, and part of the application is a single page PDF answering some questions. The PDF can include anything you want as long as it is 3MB or less, and sketching has been really helpful while I try to design my submission. First and foremost, I have been using sketching to think through various placements of text around the page, and using a small journal has been really helpful for me to visualize placement on a smaller medium. The ability to quickly, easily, and cheaply iterate through literally dozens of different ideas has been a crucial part of my ideation process, and hopefully ends up being beneficial at the end.</p><p>While sketching may be appropriate in some contexts, I think that it can also pose a problem in some situations. When you think of project teams, especially at the UW, most of them are incredibly diverse. A diverse team is super beneficial for the flow of new ideas and the generation of specialized solutions, however, not all of these teams function or are productive in the same ways. The process of sketching assumes some pre-existing abilities, like the ability to move your arm enough to draw. I’m sure there are some teams made up of non-fully abled people, so in this case sketching might not be the most effective mode of expressing ideas. While this may be an extreme case, it is still one to consider, and is still a potential case where sketching would not be useful.</p><p>In summation, for me in most ideation-related situations, sketching is my new go-to medium to express ideas and communicate thoughts. Sketching is extremely cost effective, really easy, and very time efficient, and will be my primary mode of ideation moving forward.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1cba69d660a9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Usability Testing]]></title>
            <link>https://medium.com/@kylesimpson/usability-testing-11080eb7bcd4?source=rss-b1a69dee778d------2</link>
            <guid isPermaLink="false">https://medium.com/p/11080eb7bcd4</guid>
            <dc:creator><![CDATA[Kyle Simpson]]></dc:creator>
            <pubDate>Sun, 16 Apr 2017 02:05:11 GMT</pubDate>
            <atom:updated>2017-04-16T02:06:34.605Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Introduction</strong></p><p>This week in HCDE 210 we learned about how to do usability testing for products. Something new I learned about usability testing was that it has nothing to do with how competent the users are, and everything with how intuitive the design of the product is. This took some getting used to while thinking of questions to ask in the usability tests, but ultimately gave me a better perspective on how to test products on users.</p><p>Our task was simple, design a usability test to test the design of any microwave we wanted (for my group partner and me, it ended up being the one that was most convenient to us).</p><p><strong>The Test</strong></p><p>Our test was designed to specifically test the input design, door mechanism, and disassembly process. We wanted to try to get a wholesome view of the microwave as a whole, and thought that testing these three different aspects would do just that. The first task we created asked the participant to set the cook time for 2 minutes, the second task asked them to open and close the door, and the last task asked them to remove the disk inside the microwave. From these tasks, we would collect the time it took to complete the task, a scale from 1–10 on how difficult it was for them to complete the task, and a yes or no with explanation of whether or not they were satisfied with the interaction. These three forms of data would help us better understand what was going on inside the minds of the participants while they were completing the tasks, as well as allow for constructive feedback and comments about the design. Below is a picture of what the rubric for our test looked like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GNaIiYQjVyI_OrSx10K89Q.png" /></figure><p>We decided to hold our test in Lander Hall on the fourth floor where a microwave was at our disposal. This microwave was a GE Profile 307KM00862, which is apparently the standard microwave put in all the residence halls. Our hope was that sitting in the lounge we would get a variety of users who may have or may have not used the microwave before, and luckily it turned out that way. Our first participant ended up being a friend of Jun’s (my group partner) who had no experience operating the microwave before. The second participant ended up being an old roommate of mine who apparently lived on Lander 4 with experience operating similar microwaves. And the last participant was a random person who lived on the floor who had a lot of experience operating this specific microwave.</p><p>During the first test, I was the moderator while Jun took notes. We switched during the second test, and again during the last test.</p><p><strong>Results</strong></p><p>Here are the results from the first participant:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4VpQMItF-ZN7-VMZeiBAqA.png" /></figure><p>The main thing this participant had to say was that the labels to the buttons were very confusing which didn’t make sense at first. It took this participant significantly longer to complete the first task than the other participants, solely because they couldn’t figure out which button corresponded to which function.</p><p>Here are the results from the second participant:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_TAMVl-7tzQidnmSHn7ZKQ.png" /></figure><p>The main thing this participant had to say was that the knob that set the time was way too touchy. They turned the knob half a rotation and the time shot up much higher than they expected. This was a major issue for this participant and made for one dissatisfied user.</p><p>Here are the results for the last participant:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bFhg-dD-Qq30HFA6rD-Pjw.png" /></figure><p>The primary complaint from this participant was that the disk was too heavy. This participant had slight trouble removing the disk with one hand, and had to use the other hand suddenly while removing it so they did not drop the disk. Other than this though, this user had a lot of experience with this particular microwave and was otherwise satisfied.</p><p><strong>Take-Aways and Improvements</strong></p><p>Looking through the data we collected from our tests, we noticed two main issues with the microwave. First was that the labels were unclear. The labels and buttons were stacked closely together, which led to problems for our first participant. Making these labels more distinct or putting them directly on the button they correspond to would be a good solution to this problem. The second problem was that the knob was too touchy. This led to dissatisfaction from our second participant because the knob didn’t perform like they expected. A good solution to this problem would be to slow down the response time on the knob, making it less responsive but more intuitive to the user.</p><p>Another thing we noticed about our test that may have impacted the results slightly is that the area we had set up to test was not enough for the microwave door to open fully. We left the microwave in the alcove it is usually set up in, which made opening the door fully almost impossible without putting unnecessary stress on the door hinges. This definitely impacted the second participant, who was the one who pointed out the flaw to us, and potentially impacted the third participant who almost dropped the disk because it did not easily come out of the door.</p><p><strong>About the Technique</strong></p><p>I talked briefly about the technique earlier, but I want to go into more detail here about how it influenced our test. So the technique was specifically usability testing. This meant that we had to be very sure not to be testing the abilities of the user, and rather test the design of the product. While designing the test, we had to be very sure that we didn’t ask the participant anything we could test without a user, and also stay away from ability-based tasks. Initially, this was a challenge as both Jun and I immediately thought about all the ways we could test the abilities of the microwave, but did become easier as we thought about the test from a more design-centered approach. As for running the actual test, I actually really enjoyed it. There was something novel and new about asking questions about a task we often find mundane. It was strange to be thinking about microwaves in a different way, and I could tell our participants felt the same. They were often struck by the seeming ease of the tasks, and had trouble thinking deeply about the action they had just performed. This to me was interesting. Looking at a microwave from a different perspective was not something I thought would be so intriguing.</p><p><strong>Moving Forward</strong></p><p>In my day to day life, this entire technique is not something I could see myself using regularly, however some of the practices involved with usability testing are potentially applicable elsewhere. While moderating the tests, I noticed that I was much more prone to give reassuring affirmation to the participant. While they were explaining their reasoning behind an action or rating, I noticed myself saying “uh huh”, or “yeah” often. I’m not completely sure why I found myself doing this, but I think it had something to do with making sure the participant felt supported in sharing their opinion with us. This can easily be reapplied to my job as a campus tour guide, or as a teaching assistant. Giving reassuring feedback I’m sure makes others feel more comfortable in strange situations, so these could potentially be good applications of this piece of the technique.</p><p>Final Thoughts</p><p>This has been my favorite activity thus far in HCDE 210. Something about getting user feedback seemed oddly satisfying, even though I had no stake in their feedback. I am curious to see how this skill plays a factor down the line in later activities, and am excited to potentially reapply this newly learned ability. I will also include a link to the video where Jun and I talked more specifically about participant responses below.</p><p>https://youtu.be/wVaXV6vinEI</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11080eb7bcd4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Interaction Design]]></title>
            <link>https://medium.com/@kylesimpson/interaction-design-ea512f1feb01?source=rss-b1a69dee778d------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea512f1feb01</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Kyle Simpson]]></dc:creator>
            <pubDate>Thu, 06 Apr 2017 03:24:52 GMT</pubDate>
            <atom:updated>2017-04-06T03:24:52.515Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s HCDE 210 lab, we did an Interaction Design activity meant to lay the groundwork for our low-fidelity draft sketching skills, as well as get us in the habit of thinking about users throughout our design process.</p><p>In this activity, we were given free range on a user base but had to design a mobile application that could help scientists catalog some form of wildlife. A few things we were asked to think about while thinking about our solution included: who is your user base, why should they care about your application, why should they continue to use your application, how will you design your solution to serve your user base, and how will you be recording data to help the scientists?</p><p>Given that it is Spring and the University of Washington is home to a lot of ducks, I wanted to center my application around cataloging ducklings in the U-District. There are always ducklings around Drumheller Fountain, Rainier Vista, and the Quad during Spring, so I figured an app that would let students and visitors to the UW help scientists catalog the number of hatchlings would be really cool. To keep users interested, the app offers free bubble tea from Oasis after each 5 unique submissions. Ideally, users would be walking around the U-District and whenever they see a duckling they will pull out their phone to help catalog that specific duckling. To help manage the potential for multiple submissions of the same duckling, the application utilizes a unique algorithm that detects ducklings in each picture and compares it to all other known ducklings so repeats cannot be recorded.</p><p>The low-fidelity application I created is very similar to many camera apps, however it does allow users to input more data that the picture alone could offer us.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*47e1cInUzINUVyDH3YejJw.png" /></figure><p>As you can see, there are text boxes where users can input things like injuries, discolorations, cuteness factor, and any other notes relevant for scientists to catalog. Many of these may not be noticeable from the picture submitted, so I thought it important to include places for users to input such data. While the cuteness may seem silly, another way we hope to keep users interested is by compiling all of the cutest duckling pictures to start an Instagram to show off some of the data our users are collecting. We hope this will keep users coming back and submitting more photos, and also potentially attract new users who want their pictures featured on our page.</p><p>Another important visualization aspect I wanted to include was a progress bar for users to see how close they are to their next free drink.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/1*UCXnXmJuq0wDPrUf4sSXLA.png" /></figure><p>On this page, users can visually see their progress to the 5th submission, as well as interact with our application in a few more ways. First, users can see their past photos so they have access to all their previous submissions. I wanted users to remember the ways they have contributed to our repository, as well as have a way to save old pictures if they ever want them in the future. Second, users can revisit the tutorial to refresh their memory on how to navigate the application because I thought it would be important to users to have the ability to go through this again for any reason. Third, users can view a map with directions to Oasis bubble tea, just in case they didn’t want to open a whole new application to figure out how to get there. And finally, users can return to the camera to take more pictures so we can keep them engaged, as well as have an easy way to return to the main function of the application.</p><p>Reflecting on the process we took while designing our applications, I really enjoyed the speed and flexibility paper prototyping brought to interaction design. I have worked through some interaction design using web-based tools before, and it always seemed very slow and clunky to redesign a piece that needed fixing. With paper prototyping, I had the exact opposite experience. Being advised to stay away from technology during this process, I found it very easy to jot down notes as I thought about what to create, how to create it, elements that might be useful, and common techniques that make things flow well. Using a pencil and paper also allowed me to make mistakes, fix them easily, and iterate through multiple designs rapidly. I never felt tied to any particular element of my designs, because it was so easy to erase them and create a new piece in its place. With my previous experience in web-based prototyping, I definitely felt obligated to keep certain pieces that took a while to implement, but with paper prototyping I was able to freely design anything.</p><p>I also really like Marvel and the interface they provide for stitching together basic wireframes from the paper prototypes. It was very easy to add pictures, connect them using the hotspots, and figure out the best way to make the elements flow together. I also noticed that some of the limits of Marvel actually helped me design a better product. For example, at one point I was trying to connect one screen to two potential other screens, and Marvel’s inability to do so helped me notice that there were better ways to flow through the interaction I wanted. Because of this I was able to create a more logical interaction.</p><p>Thinking about other applications of paper prototyping, the biggest way I see myself implementing this technique is while writing papers. Currently my process for writing a paper is to just sit down and start writing with no plan in mind or direction of thought. I think it could be really useful to use the idea of making small “sketches” of arguments on individual Post-It notes to better plan and map out how to structure my arguments. Using something that is neither permanent nor very structured could be super useful when it comes to formulating my argumentative structure. Slightly more broadly, I think this technique could be useful anywhere that quick, low-fidelity brainstorming is needed. I can’t say enough how much I like the idea of being able to easily destroy bad ideas and iterate through multiple good ones to get to something that might actually be useful.</p><p>To be honest, I can’t think of too many places where an approach like this wouldn’t be appropriate. Like was mentioned on the first day of class, everything is designed (theoretically) so this process could be useful just about everywhere. One small, potential place this might not be incredibly applicable is in a space where you aren’t trying to completely “reinvent the wheel” so to speak. If a designer is just trying to tweak a current feature to make it more useful, then this might not be incredibly helpful since there is already a working design that just needs minor improvements.</p><p>If you would like to see the entire application to get a better feel for what exactly I created, a link can be found here: <a href="https://marvelapp.com/g7iei76/screen/26729342">https://marvelapp.com/g7iei76/screen/26729342</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea512f1feb01" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[User Centered Design Charette]]></title>
            <link>https://medium.com/@kylesimpson/user-centered-design-charette-478d5a4c9827?source=rss-b1a69dee778d------2</link>
            <guid isPermaLink="false">https://medium.com/p/478d5a4c9827</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Kyle Simpson]]></dc:creator>
            <pubDate>Thu, 30 Mar 2017 21:45:11 GMT</pubDate>
            <atom:updated>2017-03-30T21:45:11.826Z</atom:updated>
            <content:encoded><![CDATA[<p>As our first day in the HCDE studio, we were put through a charette. A charette is essentially an intense period of design and planning used specifically for coming up with ideas quickly and putting them “through the ringer”. The whole group was given an existing product and our end goal was to create either a new product or a new feature with the needs of a group of users in mind. The product we started with was an in-car display, typically situated near the center console in a car. In most cars they look something like the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*540cffG1XiNyN9QueaG10A.jpeg" /><figcaption>Picture taken from HowStuffWorks.com (url: http://electronics.howstuffworks.com/gadgets/automotive/car-gps-accidents1.htm)</figcaption></figure><p>Displays like the one shown above range in features. They can be as simple as having only GPS capabilities, all the way to having entire web browsers and WiFi capabilities.</p><p>While some users might enjoy offering wireless internet to the passengers in their cars, not all users want or need such advanced features. In our teams, our initial task was to think of all of the potential users who might interact with a car display. Some of the more interesting users included: the elderly, new drivers, new parents, mailmen, and pet owners. With one of these users in mind, teams then had to make lists of needs and utilities each one of the groups might need or want.</p><p>My group focussed on mailmen. Not knowing too much about the real wants and needs of a mailman, we had to think a bit outside of the box when it came to the responsibilities a mailman holds, as well as things their job typically entails. This was honestly one of the hardest parts for our team. Not having a solid user persona influenced some of our ideation, and because of this we had to make some initial assumptions and think slightly farther outside the box than we might have liked.</p><p>After thinking about the normal tasks a mailman performs, we thought about how an in-car display could potentially streamline parts of the job to eliminate some of the stress in our user’s life. We came up with a few different ideas including a GPS system, a notification system to help keep track of package delivery, and a better heat-control system within the vehicle for potentially perishable packages. After some thought, we decided to morph the first two ideas to create a modified GPS system that would help track package delivery.</p><p>The intention of the system was to function like a GPS system where each respective mailperson had the ability to chose the route they were going on, and as they approached each house or multi-mailbox they would get a notification detailing what exactly had to be delivered, whether that be mail or packages. The tracking system then came into play when at the bottom of the notification, the mailperson would have to select from one of three options detailing what was delivered, either “All mail and packages”, “Everything but packages”, or “Nothing delivered”. This system would help the system overall keep better track of when mail and packages are delivered, and also has the potential to be exported so that home owners can see when their mail was delivered as well as what was delivered. The logic flow of the system would look something like the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dOdfmRagWTSAHGY4anHTDg.jpeg" /><figcaption>Picture taken from in-class team work.</figcaption></figure><p>Reflecting on the charette process as a whole, there were some parts I enjoyed more than others, but as a whole I found it to be a useful exercise in ideation. Like I mentioned earlier, the most difficult part of the process was exploring the needs of our user without knowing very much about the user. A strong user persona would have been incredibly useful when we were brainstorming solutions to a problem, as well as knowing how to design the product. I think that an important step in the process was missed by not giving the chance to do a tiny bit of user research to find out exactly what our user experiences in a day. Meanwhile, I thought that the speed of the process as well as the pressure to create a product by the end of an hour meant that we were much more creative in our solutions. We were often forced to think very far outside the box which translated into a better end product. By thinking about some of the weird solutions to a problem, we were able to find some grains of truth that helped progress our thoughts.</p><p>The charette process was actually an awesome way to create fresh ideas in a short amount of time. Lately outside of school and work I have been struggling with finding fun ways to spend my time and make unique memories with friends, and I think that in a way I could use the charette process to find new ways to spend my time. Getting together a group of friends to quickly think of fun, potentially weird, ways to spend a Saturday could actually be a really fun way to try new things. I think that charettes could also be helpful in the UW Leaders program, a program I participated in last year, when the mentees are thinking about their leadership practices. Often the young leaders struggle to find a project that both means something to them and also demonstrates their potential, so applying the concept of intense, rapid ideation could reap a lot of benefit within the program.</p><p>After going through one charette focussed around user experience design, I am excited to do others. The unpredictability these activities bring is incredibly fun and engaging from a student perspective, and I hope that the rest are just as stimulating as the first.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=478d5a4c9827" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Process Blog]]></title>
            <link>https://medium.com/@kylesimpson/process-blog-a6fa1b9292a8?source=rss-b1a69dee778d------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6fa1b9292a8</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[life]]></category>
            <dc:creator><![CDATA[Kyle Simpson]]></dc:creator>
            <pubDate>Thu, 30 Mar 2017 03:57:46 GMT</pubDate>
            <atom:updated>2017-03-30T03:59:02.592Z</atom:updated>
            <content:encoded><![CDATA[<p>Throughout my Spring quarter at the University of Washington, I will be blogging about my experiences in HCDE 210. HCDE 210 is one of four classes I am taking in preparation to apply to the Informatics major, and my intent was to learn about the differences between the Informatics and HCDE programs at the UW. I hope to end the quarter with a strong understanding of the differences and similarities, as well as end with some new skills I might not have learned without taking an HCDE class.</p><p>I will be continuously adding to this thread as I reflect upon my experiences, so check back often for updates!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6fa1b9292a8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>