<?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 Kana McLaughlin (Saechout) on Medium]]></title>
        <description><![CDATA[Stories by Kana McLaughlin (Saechout) on Medium]]></description>
        <link>https://medium.com/@kanamclaughlin?source=rss-d6ce086c8510------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*_2Ngi5fhpzssJkheAlcsPA.png</url>
            <title>Stories by Kana McLaughlin (Saechout) on Medium</title>
            <link>https://medium.com/@kanamclaughlin?source=rss-d6ce086c8510------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 14:33:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kanamclaughlin/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[Designing a user-friendly process that inspires and motivates Siemens employees to share…]]></title>
            <link>https://medium.com/@kanamclaughlin/designing-a-user-friendly-process-that-inspires-and-motivates-siemens-employees-to-share-d72137e751a5?source=rss-d6ce086c8510------2</link>
            <guid isPermaLink="false">https://medium.com/p/d72137e751a5</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[siemens]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[ironhack]]></category>
            <dc:creator><![CDATA[Kana McLaughlin (Saechout)]]></dc:creator>
            <pubDate>Tue, 19 Mar 2019 17:20:30 GMT</pubDate>
            <atom:updated>2019-03-19T18:02:49.753Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GIObNQx_q1YRA0u9NCCKnQ.gif" /></figure><h3>Designing a user-friendly process that inspires and motivates Siemens employees to share innovative ideas</h3><p>For my final project at <a href="https://medium.com/u/b627b829fa3">Ironhack Berlin</a>, I challenged myself with a problem provided by Siemens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kw9ZsTZB7aAjKn4-rg3oxA.png" /></figure><h3>The Problem:</h3><p>Currently, the Siemens Mobility department has an idea sharing tool where employees can share their ideas. However, <strong>only one in ten employees use this tool</strong>, because the current solution does’t allow the employees to keep up with the status of their idea.</p><h3>The Goal:</h3><p>The client wanted a digital product that allows employees to share their ideas, track their status, and for managers to read, evaluate, select the best idea, and notify the employee whose idea is selected. They ultimately wanted to increase the number of suggestions sent by employees and have a more efficient and effective submission and selection process of ideas.</p><h3>My Role:</h3><p>This project was a two weeks project, and I worked in a group with three other UX/UI design students. I took part in communicating with the client on a regular basis.</p><h3>The Briefing:</h3><p>Two employees from Siemens mobility visited our class to explain the brief and provided us more information about Siemens. Following this briefing session, and our class had a quick kick-off HMW brainstorming session. The two employees helped us pick out the most adequate HMWs so that we could better align our understanding of the project with what they expected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tZmKrAuVqDc-35Ly-fcs2g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EKaanbOwS34K90agFEjIEA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lI5UuzukxhV9cfwO4tp9qQ.jpeg" /></figure><h3>Step 1: Getting to know the problem</h3><p>The Siemens team, <a href="https://medium.com/u/905913a24806">Jane</a>, <a href="https://medium.com/u/64fe7516b2be">Karoline</a> , <a href="https://medium.com/u/844c15040199">Kevin</a> and I, started to plan out our two weeks plan. We began by doing a <strong>competitive and business analysis</strong>, and collect as much information possible about idea sharing tools that were available in the current market.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aguHJpiNbhWiT6wwHixoAQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iv5C3pnZZKyL7tp7LJYbLw.jpeg" /><figcaption>Left window: questions for employees. Right window: questions for management.</figcaption></figure><p>Simultaneously, we communicated with the client to schedule interview appointments with employees at their office, and created questions for our <strong>interview guidelines</strong> for employees and managers. We believed that going directly to the office and interviewing the people will give us some insights not only about their perceptions on the idea sharing tool, but also about the office environment and company culture.</p><p>Prior to our visit to the office, we had several virtual conferences with the client as our main form of communication in order to ask more about the current tool. Some things we wanted to know from the client were:</p><ul><li>What the client values in one idea?</li><li>What the most important piece of information in an idea?</li><li>What is the MVP?</li><li>What are the current usability problems?</li><li>How is the reputation of the current tool?</li><li>What is the overall flow and look of the tool?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xbc5wnQS-RcFIOTTguCSUA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OgfdvvRR9agi_sd5oCKIlg.jpeg" /></figure><p>From talking directly to the client to ask for more detail regarding the problem and the current tool, we were able to refine our interview guides.</p><p>Some questions we prepared were the following:</p><h4>Questions for Employees:</h4><ul><li>What do you expect from sharing your ideas?</li><li>How do you decide whether or not to share an idea?</li><li>What motivates you to share an idea?</li><li>Do you recall a time when you participated in coming up with and sharing innovative ideas?</li><li>Can you walk us through how you use the current idea sharing tool?</li><li>How do you feel about colleagues, other than management, viewing your ideas?</li></ul><h4>Questions for Managers:</h4><ul><li>How do you currently give feedback to employees?</li><li>What are some things that frustrates you when giving feedback?</li><li>Currently, how are you motivating and engaging employees to submit ideas?</li><li>Currently, when faced with many ideas, what is your criteria for selecting the best ideas?</li><li>Do you think it is important for employees to be involved in the selection process of ideas?</li></ul><p>The next step was to conduct <strong>interviews </strong>at the Siemens office in Berlin. We were able to interview two people in person, and three others by phone in the following days. Our group distributed responsibilities for the interview, with two people in charge of asking questions and the other two writing down the interview notes. We also made sure to record the interview (after asking for permission to each interviewee) as part of our documentation process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qm6qx4R851Gph1wuCQNb2g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*053QXf11UQnTtfxYcDfiIA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tfW2tWYg2zeal0_9NkjN7Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0JaRld2myc-jCigDUHSBfA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vXM8rrQtDq9Wr_WyRQTcbw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N3YBcd3TlO62V-utaDJatg.jpeg" /><figcaption>Our experience interviewing on-site and off-site</figcaption></figure><h3>Step 2: Evaluating our Findings</h3><p>After the interviews were complete, we decided to place all our <strong>insights</strong> on one wall with post-its to create our <strong>affinity diagram</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sbNfdkcCOqRlX0wLkALZ9g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*LXJK0kcC7C7BxZwoTrjHIg.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IFM4e3uEVOcMHG0nBpHyOg.jpeg" /></figure><p>Once all the insights were posted on the wall, we started to sort each insight into related groups in order physically be able to see trends and relationships in our data. For each group, we thought about a header that captured the essential link among the ideas.</p><h4>Key insights:</h4><ul><li>With the current tool, submitting ideas is tedious because it is extra clicks away</li><li>employees talk with other colleagues during their coffee and lunch breaks, and feel that it is a great time and place to discuss ideas</li><li>current feedback loop is too long, and that discourages them from submitting ideas</li><li>When asked if they have used the current tool, not many employees had experience using the current tool</li><li>The current tool does not allow employees to keep notified with the status of their submission</li><li>biggest motivator to share idea is that their input is valued</li><li>The speed and quality of their feedback makes employees feel that their idea is valued, and consequently motivates them to submit ideas</li></ul><p>We then filled an empathy map to synthesize rational and sentimental aspects of employees and managers in order to reach an empathy level where we can look at the world through their eyes. Their perspectives and behaviors can help us better understand and make decisions throughout our decision process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7x_EcFld-HM9fXwrJpSkAw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eAgTXrtnblw_rhoMlFHcyQ.jpeg" /></figure><p>Creating a header for the groups helped a lot with the next step, which was to create <strong>HMW</strong> statements. It helped us see each insight in a broad sense, which allowed us to rephrase problems we saw into opportunities. We asked our teacher (thank you @<a href="https://medium.com/u/c974ad06498f">Murilo</a>) for feedback regarding the HMW we had, then we dot voted to see which HMW we wanted to proceed with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6VSWWHlwcbNTUpP2yGmvdQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Baoycw-8SBO7rDxiLZ9PqA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BWk0_anorMEzTqM7kdFzSw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Oikpjr3Bnsek_oKMcW5oUA.jpeg" /></figure><p>The HMW statement that our team decided on was:</p><h4><strong>How might we integrate sharing ideas part of the employees’ daily work life?</strong></h4><h3>Step 3: Getting Creative!</h3><p>With the insights we gained from research and the HMW statement we generated in mind, our next step was to get creative and start ideating. Our team used the <strong>crazy eight method</strong> where each of us generated eight rough ideas in eight minutes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KhiHWxGRuhDFn_K9Q_5cPg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pDplYGPV-5bSDexQhmWFIA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pUJcdGzA32GAMR5Ub7YaLg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BjDresodzHOnVbyaa4eP1Q.jpeg" /></figure><p>After sharing our ideas, we each polished one idea that we thought had potential. We shared our polished idea, and realized that each of us had a similar idea in mind. We decided to integrate the best parts of our ideas to generate one powerful idea.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1pGfQqy98NPwteNCZ_YEXg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uqaJvZH0VBsBaIW7Q5Rb8g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4MdkGS6BF09PX6be-JBNOA.jpeg" /></figure><p>The <strong>idea</strong> we generated was an <strong>interactive digital wall where employees can share and submit their innovative ideas, that will guide employees to a seamless idea submission process on a desktop tool.</strong></p><p>We believed that with the wall, it will spark interest, inspire, and motivate employees to submit their idea. The submission process for employees and feedback process will be designed to be user-friendly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ab2pR4pVyr9jKnFimE6amg.png" /></figure><p>The next step was thinking about what content we should include in our product. We started creating a <strong>site map</strong> to list out the necessary content for the interactive wall and the idea submission desktop tool (for employees and management), and then thought about what content belongs with each other in a way that is most easy to understand for users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*39-BjUqEVCa8yC7XfAostQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zZbG5YPax-13YMzDIrRgdw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mA2k9jE5L4KyITC5pqdfhg.jpeg" /></figure><p>To get a better idea of how the user would interact with the product, and ultimately the path a user would take to complete a task, we created <strong>user flows</strong>. It helped us detect potential pain points, and also helped validate our user journey. While the site map helped us figure out the content in our product, and the user flow helped us think about the order in which the user would see the content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I23mCWm3YS7-wbFM3beh-A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WRQA7blxPv-8bdKXp3nrag.png" /></figure><p>Our team additionally went to the Rittersport Museum and other locations where we could get inspired about how to design our interactive wall. This research helped us experience what was potentially possible with touch screens, as well as things we wanted to avoid when designing our wall.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nvMVtEcloy6oMkfjvChwvg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MXkdaabF3Tp3bSoK0itD-g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZauOBx_KrJsFoMz39T2rQg.jpeg" /></figure><h3>Step 4: Creating our prototype</h3><p>The next step was to start processing our idea into <strong>low-fidelity wireframes</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fxbFfo5TCZHDwAOh_auiog.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_QVsJ84YbHoyNIgnEfkPOw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3fW1xItaXl581QaxmOU_sA.jpeg" /></figure><p>Based on our low-fidelity wireframes, we created our <strong>mid-fidelity prototype</strong>. We made our prototype interactive in order to test with current employees to conduct <strong>usability tests</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k7UICYcHVKKVASIrfdNhdg.png" /><figcaption>Interactive wall mid-fidelity prototype</figcaption></figure><p>We scheduled an appointment with our client at their other office at The Factory, a share-office space, and we were able to test our prototype with two employees, as well as with three non-employees we found at the share office.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NslFyZvaMr8Iij4bOY_ECQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ruSX8LDs7JyNqXrr_MUr9Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zko3skW3R5oTLrgTcqX9Qw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*neo8AradwqD7f2bSaMRoRw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FeV9IM9ITZ4oIjda6-XScA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NCzX4d1cDoIi4ujWyabtgA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SHPNIyKs67JnmUeyK89Yeg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1XmrPm4FPGIr7iaILOBZkA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZvmNYif5aVKb3al2ICIHMQ.jpeg" /><figcaption>Our team testing our prototype</figcaption></figure><p>We discussed all the feedback we received during the usability test, and iterated our prototype to adjust our product to the needs of the user. Some interesting insights we gained were the following:</p><h4>Wall Feedback</h4><ul><li>The wall was not clear what it was, and the content was hard to understand what it was about</li><li>Having name of manager on the idea cards could negatively affect employees’ submission due to bias and/or fear of their judgement</li><li>After opening innovation challenge card, there should be more detail about the challenge instead of having to email yourself the details</li></ul><h4>Submission Tool Feedback</h4><ul><li>Feedback should be more prominent</li><li>Would be nice to be able to see more clearly when idea will be reviewed, and the upcoming steps</li><li>What counts as “resources”? People? Tools?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SchGRJ9MeqDLJNKgGqRoZQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FOZyLJLfJeEY_mgrbwaNvQ.jpeg" /><figcaption>Putting all the feedback we received on the wall</figcaption></figure><p>After applying changes to our prototype, we tested again.</p><p>Once we were confident with our mid-fidelity prototype, we designed our <strong>high-fidelity prototype</strong>. To keep the look and feeling of our product consistent with the Siemens brand, we used their brand guideline as our reference and designed our prototype accordingly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JEB6o9XGOXo_imvKGP756w.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xTZ_YqO2aH97pdgRK_y5YQ.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5rwcjbLX9V7Vb9-Ln0bqjQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CaTCftnAnZJUE153v0VVDg.gif" /></figure><h3>Step 5: Presenting our design to our Client</h3><p>We had the great opportunity to present our work and our design thinking process to our client. We received positive feedback, and look forward to the next steps to bringing our idea to life.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3SDe-clXth3nwEWXnj7Tmw.jpeg" /></figure><p>Additionally, our team was selected as one of the finalists for the Hackshow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EVQR1HjvRVwkJ5pS7TlOCA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DMLmhpVyhCJjdo9a4beKJQ.png" /></figure><h3>Final Thoughts &amp; Thank you’s</h3><p>This project challenged our team on many levels, as it involved an actual problem from an actual client. Communicating with the client on a regular basis and tackling the challenge under time pressure has made me a stronger UX/UI designer.</p><p>I’d like to thank my amazing team members <a href="https://medium.com/u/64fe7516b2be">Karoline</a>, <a href="https://medium.com/u/905913a24806">Jane</a> and <a href="https://medium.com/u/844c15040199">Kevin</a> for being such a great team to work with. Each of us brought in strong work ethic, passion, and dedication, and I can’t think of a better team to have tackled this challenge. We’ve come a long way, and although this final project brings us to the end of our Ironhack journey, I’m wishing you all the best of luck with the amazing opportunities waiting ahead. Thank you for the unforgettable two weeks.</p><p>Thank you to Haris Habib and Philipp Wehn, and everyone at Siemens involved in this project for your time and cooperation. We are excited about the next steps!</p><p>I’d also like to thank our wonderful teacher <a href="https://medium.com/u/c974ad06498f">Murilo</a> for being our guiding star and moral support. In times of despair, he was always there to point us to the right direction. I’m very lucky to have had you as our teacher. Thank you for everything.</p><p>And last but not least, <a href="https://medium.com/u/b627b829fa3">Ironhack Berlin</a> for giving us this valuable opportunity. Thank you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d72137e751a5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Maze: a webzine platform for aspiring young artists to network and gain exposure in the art scene]]></title>
            <link>https://medium.com/@kanamclaughlin/maze-a-webzine-platform-for-aspiring-young-artists-to-network-and-gain-exposure-in-the-art-scene-abc4c4f3cb0a?source=rss-d6ce086c8510------2</link>
            <guid isPermaLink="false">https://medium.com/p/abc4c4f3cb0a</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[éditorial]]></category>
            <dc:creator><![CDATA[Kana McLaughlin (Saechout)]]></dc:creator>
            <pubDate>Wed, 06 Mar 2019 23:34:04 GMT</pubDate>
            <atom:updated>2019-03-26T09:35:29.165Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zsjzq4ZjnR9hIpQsl5KyVw.jpeg" /></figure><h3>Background</h3><p>This was my fifth week at Ironhack as a UXUI student, and the second week learning about UI. Below, you can read about my progress throughout the week, and my attempt at design thinking :)</p><h3>The Challenge</h3><p>The challenge was to design a responsive online platform for a magazine, newspaper or blog directed to meet the needs and goals of one user persona that was provided.</p><h3>My Role</h3><p>This project was a six day project with a partner, and I had a great week working with <a href="https://medium.com/u/e285cff3f5fa">Noorida</a>. We were given a choice of user personas to pick from, and our task throughout the project was to deliver a consistent, branded and engaging experience. The focus of this project was the UI aspect of the design thinking process. For the final deliverable, we had high fidelity prototypes in iOS and desktop format, which we presented to our class.</p><h3>Design Thinking Process:</h3><h3>Step 1: Empathize</h3><p>Due to the fact that with this project user personas were provided, we took a look at the information hidden in the user persona and tried to research more about Paula. To further understand what kind of content Paula is interested in, we took a look at the webzines that she reads regularly (Vice, Rolling Stone and Man Repeller). Conducting a <strong>business and competitive analysis</strong> helped us understand the type of content, look and feel that Paula is attracted to. It also brought to our attention that the webzines were mainly for the focus of reading articles, and not much more.</p><h3>Step 2: Define</h3><p>As mentioned earlier already in the Empathize stage, our first step of this project was to choose a <strong>user persona</strong>. My partner I decided to go with Paula. The following are details of Paula.</p><ul><li>Paula, 19, wants to be an artist and connect with people (and aliens if they want to) around the world</li><li>she reads voraciously, everywhere, anywhere. In bed, public transportation, with friends, out loud, for her projects, etc.</li><li>she reads Vice, Rolling Stone, Man Repeller and other webzines</li><li>she reads content by most influential authors from her time, and shows off on Instagram.</li><li>her goal is to achieve her dreams of start being “someone” in the art scene, and have her first expo soon to start being “someone” in the art scene.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TGH4pCBnJvdRoCeuKyQEWA.png" /><figcaption>Paula’s persona</figcaption></figure><p>We thought back to Paula’s goal of wanting to be “someone” in the art scene, and wanted to integrate a solution to this problem in our webzine. We brainstormed some <strong>HMW</strong> statements, and decided on the following:</p><p><strong>How might we help Paula be part of the art scene internationally?</strong></p><h3>Step 3: Ideate</h3><p>After processing our HMW statement, we did a quick brainstorming session for ideation. The idea that we came up with that differentiates our website to competitors’ website is that we wanted our webzine to be a platform where young artists like Paula can directly contact artists. For example, if a user reads about one artist in an article, s/he can message the artist directly from the website. To keep the site simple and user-friendly as possible, we decided to eliminate any logging in process using social media accounts.</p><p>With our idea in mind, we wanted to figure out what pages were necessary to create a <strong>MVP</strong>. We started off writing content on cards that we thought were good to include, and we created our first <strong>site map</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bBJJALfKpae8lE4ZeARcnw.jpeg" /></figure><p>After eliminating some cards we thought were unnecessary, we used the remaining cards to execute <strong>card sorting</strong>. We asked four people to organize the cards in any way that they believed made sense. The results are as follows:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V2RN6oIx-5yb01rcypQyTg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q-bCKIzTVXwLefumXzwfGw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KapwNLcY6ZSMbQ_Rf6Rl3g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nR2h5F4Md5NEdQgdacjctg.jpeg" /><figcaption>card sorting results</figcaption></figure><p>Based on the results of the four card sorting and the insights we received, we refined our site map. We eliminated some cards to simplify our site map for good.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oGe32vnPbnsPibLBSxk3XQ.jpeg" /><figcaption>Our revised site map</figcaption></figure><h3>Step 4: Prototype</h3><p>Our next step was to create our <strong>low-fidelity prototype</strong>. We started off with very rough sketches on paper to have a quick idea of what content we wanted and on which page. After this step, we took photos of the sketches and made a quick low-fidelity interactive prototype on <strong>Sketch</strong>. This was done so that we could test what we had with several people, hear their feedback, and finally revise the prototype which allowed us to make quick adjustments without being too committed to the prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZUJAvZjx-U4X4yk48MBs5Q.jpeg" /><figcaption>our first low-fidelity wireframe</figcaption></figure><p>Following the low fidelity prototype, we then started to think about the <strong>UI</strong> of the website. We collected some images for our <strong>mood board</strong> to use as a reference for our design. As shown below, we gained inspiration from other websites that had a strong art feel. Visuals that are rich in color, and fonts that are simple yet bold, and easily legible were some components that we wanted our website to have as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6rRY7xPcVYbxZ_1C0QQShQ.png" /></figure><p>The mood board helped us identify the impression we wanted our website to have, and therefore we discussed what <strong>brand attributes</strong> we wanted for our website.</p><ul><li>motivational</li><li>energetic</li><li>imaginative</li><li>friendly</li><li>modern</li><li>artsy</li><li>cool</li><li>honest</li><li>supportive</li><li>successful</li></ul><p>These brand attributes helped us think about human characteristics that identify the physical, character, and personality traits of our brand. It ultimately helped us define the type of customer experience we wanted to deliver.</p><p>We then moved on to creating a <strong>style guide</strong> which included the primary and secondary color, fonts, buttons, input fields, icons, and also developed a name and logo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eiU4NfqWHcxVr_yHI3346Q.png" /></figure><p>For the primary color, we picked Pantone’s color of the year for 2019, a bright coral shade called “Living Coral”, and a blue that gave a good contrast. Because we wanted our webzine to be up-to-date with current trends, we wanted the primary color to reflect that element. We picked Maison Neue for the font, with the bold san serif font used for the purpose of headers, the san serif book weight for the body, and mono font for buttons.</p><p>Having the components of the website ready on the style guide, we integrated these into the mid-fi prototype we had made to develop a high fidelity prototype. We started off creating the home page in iOS format, and then applied the design to create one in desktop format. To work efficiently and be able to communicate about the design and any changes we made, we tried using Abstract to share the data between ourselves. Noorida primarily worked on desktop, and I worked on iOS.</p><p>Here is how our high-fidelity prototype turned out:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hsurjyYy4RDa2kllV2vgDw.png" /><figcaption>iOS high-fidelity prototype</figcaption></figure><h3>Step 5: Testing</h3><p>Finally, we wanted to test our high-fidelity prototype. We conducted a desirability test to determine if our responsive website reflected the brand attributes that we had. To test this, we conducted the <strong>Reaction Card method</strong>, in which we wrote twenty four cards with adjectives. Half of the cards consisted our brand attributes, and the other half attributes that we did not want our website to have.</p><p>Our strategy was to approach random individuals and explain to them that we were conducting some UXUI research for several websites. We made sure to not mention anything about the fact that we were designing the website to avoid any bias. We first showed them competitors pages, and asked them to pick out five cards that they believed best represented what they felt about the website. Then, we repeated the process with our website. We made sure that with all the websites (including our website), the logo was blurred to prevent any bias.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X75yv7a_uksFVLEuz2D3Mg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DHDHwOmIJfNbk2EOhhuDbw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uGpfVBg5OruxrmsX7MwQUQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hKOnnqJp1T3bohiDQIlBVw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fJbWmvcdquf7HoarYIc84w.jpeg" /></figure><p>From this testing method, the most frequently picked adjectives were the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p86niLHgcy2BBWlnCtarhQ.png" /><figcaption>Results from the Desirability Test</figcaption></figure><p>It was interesting to see how we were successfully able to visually communicate our brand attributes we were aiming for.</p><h3>6. Improving the Prototype</h3><p>Our final step before presenting our high-fidelity interactive prototype was to apply some animation effects. To do this, we used<strong> Principle</strong>. Since we did not want the animation to be too overbearing to the content of our website, we started off with small, simple effects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o6_qYXkGZXT1YLN5neVSFQ.jpeg" /><figcaption>Getting feedback from our TA Cesar</figcaption></figure><p>And finally, on Friday, we gave our five minute presentation about our design process to our class :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZtoLLYBPT3z8YEJxakyPPQ.jpeg" /></figure><h3>Final Thoughts &amp; Next Steps:</h3><p>Although my partner and I followed the design thinking as usual, this project was especially interesting because we started off picking one user persona instead of having to think of one based on research. As mentioned already, this was due to the fact that for this week, our focus was on UI over UX.</p><p>It was definitely a challenge having to create a brand from scratch, but it was one of my favorite parts of the project. During the process when we tested our high fidelity prototype, it was amazing to see how people felt about our brand, and how they felt the same exact thing as what we aimed for based on our brand attributes.</p><p>Our next steps for this project will be to think of additional features that would make our webzine more user-friendly to young artists like Paula. For example, one idea we integrated in our prototype was a tag feature. How this works is that keywords related to an article would be shown as “tags” at the end of the article. We saw this feature on multiple online editorial websites, and thought that it would allow our content to link to other similar content in our website. This would allow users to find and learn more about content they find interesting.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abc4c4f3cb0a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Easing the distance: a Netflix feature that would make watching content more collaborative even…]]></title>
            <link>https://medium.com/ironhack/easing-the-distance-a-netflix-feature-that-would-make-watching-content-more-collaborative-even-ef4bb7127303?source=rss-d6ce086c8510------2</link>
            <guid isPermaLink="false">https://medium.com/p/ef4bb7127303</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[app-feature]]></category>
            <category><![CDATA[netflix]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Kana McLaughlin (Saechout)]]></dc:creator>
            <pubDate>Sun, 03 Feb 2019 10:16:31 GMT</pubDate>
            <atom:updated>2019-07-25T09:39:37.601Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IjDQun79p0XoMZC2gapchg.jpeg" /></figure><h3>Easing the distance: a Netflix feature that would make watching content more collaborative even when continents apart</h3><h3>The Challenge</h3><p>The challenge was to create a chat feature that you can use with friends while watching the same content on Netflix.</p><h3>My Role</h3><p>This project was a four day solo-project. The feature designed to be added was a chatting feature on Netflix that would improve the users experience on the existing app. I focused on the ideation and prototype phase for this project.</p><h3>Design Thinking Process</h3><h3>Step 1: Getting to know the problem</h3><p>Because the topic was already determined, I started off conducting interviews to collect qualitative data in hopes of extracting insights. I did a total of seven interviews, and below are some questions that I asked.</p><ul><li>Do you have a streaming service that you use to watch shows/movies?</li><li>Do you watch the same shows as your friend?</li><li>Do you talk about the same shows with your friend? If yes, when/how?</li><li>Do you ever chat with your friend while watching the same content?</li><li>Have you ever wanted to watch something with your friend but could not?</li><li>In what way do you find the most enjoyable when chatting with your friend? (chat in person, message, pictures, emoji, gifs, etc.)?</li><li>How do you think being able to chat with your friend while watching the same show will change your experience?</li></ul><p>From the interview, the following are some of my quantitative &amp; qualitative findings.</p><h4>Quantitative data:</h4><ul><li>7/7 had Netflix</li><li>6/7 consciously watched the same shows as friends</li><li>6/7 talked about shows with friends in person</li><li>0/7 simultaneously watched content and messaged friend</li></ul><h4>Qualitative findings:</h4><ul><li>“being able to message my friend might make the experience more collaborative”</li><li>“Instead of figuring out when to go to the movie together, you can arrange to watch stuff at your respective homes”</li><li>“when my friends and I would meet up we would talk about shows face to face”</li><li>“we would recommend shows to each other”</li><li>“[having a messaging feature] would ruin my experience. I want to focus on the movie instead of chatting with someone”</li><li>“if you need to read subtitles, it would be annoying because reading messages would distract you a lot”</li><li>“I want to focus my attention to watching than having to type messages”</li></ul><h3>Step 2: Evaluating the findings</h3><p>When looking at the interview results, I wondered if this feature in the first place was even one that would improve the users’ Netflix experience. It seemed that the majority did not find the idea of messaging and watching something at the same time a pleasurable experience.</p><p>However, I then realized an interesting pattern, which was that the interviewees associated “chatting” with typing/reading words, and that the process of reading was time consuming and distracting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/1*Mqa_e2CtNb1t2zLYomA3_Q.gif" /></figure><p>If we look at the way people communicate through digital platforms, we not only type letters, but we also use other forms of communication like emojis.</p><p>This realization made me curious about exploring the potential of using emojis as the main form of communication for this feature between users.</p><h3>Step 3: Getting Creative</h3><p>Based on the insights, I developed a chat feature that would only use emojis. This is because emojis are useful tools that visually communicate emotions and requires no reading from users. The only downside to emojis is that it is very difficult to have a deep conversation, but from the interviews, 85% of people mentioned wanting to talk in person about the content they watched. So, this chat feature will primarily be used for the purpose of exchanging quick, visual remarks that represent what users are feeling in that moment, and would not require much thinking to use.</p><p>I also researched into Facebook and Instagram’s feature of users being able to react to content with emojis. I thought the idea of using emojis would be the best solution for users to communicate while watching without much effort and would cause the least distraction.</p><p>My idea was an integrated experience using a phone and a tv. Two (or more) users would be able to synchronize their respective television screens so that the timing of the movie would be simultaneous. This would all be controlled through the app. Once the movie is playing, users can exchange emojis as a form of communication.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E_6hWrMt-EDM8ntBJSMZ_A.png" /></figure><p>The job to be done for this feature is:</p><p><strong>When Julie is on a business trip and away from home, she wants to watch Netflix together with her boyfriend so she can maintain a healthy relationship.</strong></p><p>I proceeded to create the happy flow of one user (Julie).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SYcswxeEJqICLmgdgOFNqw@2x.png" /><figcaption>Happy flow of one user</figcaption></figure><h3><strong>Step 4: Creating the prototype</strong></h3><p>Based on the happy flow, I started off sketching out a low-fi prototype on paper to determine what elements were necessary to make this feature work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z0qesMY0KmDlWHPiUD9kbg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9GZYsSMUnCGPHO4lezYI9w.png" /></figure><p>I then proceeded to creating a high-fidelity prototype. My challenge here was to design a prototype that was consistent with the existing Netflix app. To do this, I had an interface inventory where I collected elements that made up the Netflix app that could be used as reference while thinking of the UI of the app. A big thank you to <a href="https://medium.com/u/844c15040199">Kevin</a> (who happened to be working on another feature for Netflix) since we helped each other with this step to save time! So, having the interface inventory as a good reference, here is what my high-fidelity prototype looks like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j5CpjvNBMx7oFgVAWRjGfA.png" /><figcaption>high-fidelity prototype for user 1</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h0V7shHl3iticgyzXnAKcw.png" /><figcaption>high-fidelity prototype for user 2</figcaption></figure><p>I created prototypes two users. For one user, who would be the primary controller while watching the content. This means that this user would be in charge of synchronizing the content with whoever s/he is watching with. This will be done by sending a code generated by Netflix. The second user would input the code given, and would have his/her screen synchronized. <br><em>*** Interactive prototype to be added shortly ***</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/754/1*5WuRwQQYHIAKj2YIWJytFA.jpeg" /><figcaption>presenting my idea to my classmates</figcaption></figure><h3>Final Thoughts</h3><p>This project was eye-opening in many ways. For one, the feature I worked on was one that was thought of by another classmate, and not my own idea. It put into perspective how in the real world, as UXUI designers, I would most likely be working to think of solutions to other people’s problems. It was a struggle for myself in the beginning to think of this solution, since during the interview phase the majority was very much against the idea of putting messaging and Netflix together. However, it was also through the interview that I found the insight that helped me create my solution. Thank you to <a href="https://medium.com/u/641c7cc7302e">Prateek</a> for the amazing feature idea- you helped me go through a very valuable experience :)</p><p>I also learned to prioritize and “think with my gut”. This was because we were only given four days to think of a solution to our feature. Unfortunately, this meant that I did not have the ideal time to test my product. I believe that will be my next step, which will help me improve my feature even more.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef4bb7127303" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ironhack/easing-the-distance-a-netflix-feature-that-would-make-watching-content-more-collaborative-even-ef4bb7127303">Easing the distance: a Netflix feature that would make watching content more collaborative even…</a> was originally published in <a href="https://medium.com/ironhack">Ironhack</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mooji: An affordable & engaging digital language learning platform for teenagers]]></title>
            <link>https://medium.com/@kanamclaughlin/week-3-e-learning-app-challenge-42f19b0729b2?source=rss-d6ce086c8510------2</link>
            <guid isPermaLink="false">https://medium.com/p/42f19b0729b2</guid>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[e-learning-for-kids]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[Kana McLaughlin (Saechout)]]></dc:creator>
            <pubDate>Sun, 27 Jan 2019 12:00:07 GMT</pubDate>
            <atom:updated>2019-03-29T19:26:07.931Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M8YImxbQfwkR09_3AfrndQ.jpeg" /></figure><p>For our third week as UX design students, our task was to create an e-learning app. Our challenge was the following:</p><p><strong>This project is about creating an online learning platform for 12–18 year old students. It will transform the in-person learning experience into a 100% digital experience that can be accessed by students at a lower cost.</strong></p><p>Without further ado, I’d like to explain the process of how I tackled this challenge.</p><h3>Background</h3><p>Smart People Inc. is an educational company that currently offers in-person language courses for children from 12 to 18 years old. Their main attraction is a summer camp where children can learn English or Spanish as a second language, and many teenagers join every year in different locations. The camp’s special program includes sports, outdoor activities, technology, humor, games and such.</p><p>Each camp is for four weeks, and each course has twenty activities and twenty lessons of which students get to decide which 10 they would like to take. All students receive feedback from other students and their coaches, and coaches follow the children’s progress in order to create the most adequate learning path together.</p><h3>The Challenge</h3><p>Due to the cost and time reasons, some students are unable to attend the summer camp but still want access to the curriculum.</p><h3>My Role</h3><p>I teamed up with another UX student, <a href="https://medium.com/u/33bd3499f0fa">Noémie</a>, to execute the design thinking process from the beginning to delivering a mid-fidelity prototype. We started on Monday had five days to carry out the project, and for the first time we did not have a schedule that we had to follow. Instead, we had to take leadership with planning when to do what to have our mid-fidelity prototype ready for Friday.</p><p>I’d like to explain the process of how we went through the design thinking process, why and how we decided to carry out certain methods, and the outcome of the mid-fidelity prototype.</p><h3>The Design Thinking Process</h3><h3>Step 1: Empathize</h3><p>In addition to the background information of Smart People Inc., we conducted a <strong>competitive analysis</strong> which allowed us to examine current competitions and potential competitors in the e-learning market. Below, you can see the feature comparison and branding comparison charts that compare Smart People Inc. to other language learning companies/institutions. The market positioning map gives a visual representation of where Smart People Inc. currently stands among competitors, and also highlights gaps in the market which could be turned into new opportunities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XyodPJsDeFOrLLPprdE1kg.png" /><figcaption>Brand Comparison</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2d0KiPkkkw47YjqSWmW_EQ.png" /><figcaption>Feature Comparison</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n9AsZwnnpqTI3XqgrkFS5Q.png" /><figcaption>Market Positioning Map</figcaption></figure><p>We then discussed how we should conduct our <strong>user research</strong>. Since this app is for students, doing research on students was one idea. The purpose of this app is to teach a language, therefore we also thought doing research on teachers was another option. Then we also remembered about the students’ parents, who were the ones making the financial decision. Ideally, conducting research on all three would be good to collect as many data, but due to only having five days, we decided to narrow it down to teachers. We figured teachers know both students and their parents well since they are constantly in contact with them at school, and also have knowledge on education.</p><p>Next, we had to decide which <strong>user research method</strong> to use. In order to gain <strong>qualitative data</strong> that would give us deeper insight, we felt that <strong>interviewing </strong>teachers would be the best method. Our challenge was then to formulate open-ended questions that would help us gain insight about students and education. Here are some of the questions we asked:</p><ul><li>What are the biggest struggles when teaching language to students?</li><li>How important do you think getting feedback is for students?</li><li>How would you give feedback to students?</li><li>What are the pros and cons of e-learning versus in-class lessons?</li><li>Have you ever used any e-learning tools? How do you feel about it?</li><li>What teaching material do you think works best for students (12–18)?</li><li>How do you differentiate activities from lessons?</li><li>How do parents like to be involved in their children’s progress?</li></ul><p>We interviewed a total of six teachers from around the world. An English teacher, History teacher, a middle school teaching assistant, Spanish teacher, and such people with a background in education.</p><p>Below are some <strong>insights </strong>we gained:</p><ul><li>“if students lose confidence, they tend to lose interest in the subject”</li><li>“repetition and feedback are very powerful when used together”</li><li>“material that empowers them and makes them take ownership of their learning” [works best for students]</li><li>students should learn on “their own pace”</li><li>“feedback is extremely important” and “has to be constructive”</li><li>students “need to learn theory to apply later in activities”</li><li>“focus on usage is far more important than focusing on perfect grammar”</li><li>“good idea to let students choose between reading, writing, speaking and listening because some people learn one way and some people learn better other ways”</li></ul><p>In addition to the interview insights, we were able to collaborate with other teams during this user research phase and share valuable quantitative data.</p><h3>Step 2: Define</h3><p>Based on the insights, we created an <strong>affinity diagram </strong>that helped us physically see trends and relationships in data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xytp8EBV6IqgjRnQKoHyfA.jpeg" /><figcaption>Noemie and I discussing our findings after sorting the insights into related groups</figcaption></figure><p>With the insights in mind, we then proceeded to create a <strong>user persona</strong> to set a common understanding of the final user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oFZbzvTVg06OjpvV0_C3dw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A4z4mWmhPod56xAAJgxGtw.jpeg" /><figcaption>Student User Persona</figcaption></figure><p>Next, we started to formulate <strong>How Might We</strong> statements in order to reframe problems as opportunities. We looked at the frustrations and motivations of the user personas that we created, and tried to frame those challenges into HMW statements that could be answered in multiple ways (which will be helpful during the <strong>brainstorm</strong>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n1_VE1scvltoeSraxKcFww.jpeg" /><figcaption>HMWs without any organization</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9eDnMW0IhcJWQocSj140Lw.jpeg" /><figcaption>HMWs after organization</figcaption></figure><p>After <strong>dot-voting</strong> (a democratic way by deciding on which HMW to proceed with), we agreed on the following statement:</p><p><strong>How might we help students feel confident and inspired learning a new language?</strong></p><p>We then created a <strong>user journey</strong> to further understand potential opportunities in moments of frustration of the user. Based on our qualitative and quantitative research, we developed a storyline of collective assumptions where the user, Adam, encounters moments of truths, or pain points, where he feels anxious or frustrated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yYFtRo5_ws2b51_FDFGQUQ.png" /><figcaption>User journey of Adam</figcaption></figure><p>As our last step of the define phase, we formulated our <strong>problem statement</strong>that defines the problem and captures the insights from our user research. The problem statement was:</p><p><strong>Students need to feel confident and inspired when learning a new language because the current teaching system is too traditional and not dynamic enough.</strong></p><p>We then created our <strong>hypothesis statements</strong> which would help us think about what results we should look in an experiment. The statement was:</p><p><strong>We believe creating an interactive and fun app for students will achieve our goal of making them confident and inspired when learning a language. We will know we are right when students successfully achieve their language goals and students give a high satisfaction rating to the app.</strong></p><h3>Step 3: Ideate</h3><p>We kicked off our ideation phase with a <strong>brainstorm</strong> session where we put potential solution ideas on the wall. Then, with the HMW statement at the core, we created a <strong>mind map</strong> from those ideas by grouping the similar ideas together, which helped generate more ideas. The non-linear thinking involved in this process helped us find more meaning in our topic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nI84n6WZAkD78hpAtt3hnA.jpeg" /><figcaption>Brainstorm</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wsjz19dqFOTvDnXPH5LnfQ.jpeg" /><figcaption>Ideas from brainstorming grouped to form a mind map</figcaption></figure><p>With many thoughts and ideas, the next step was to turn them into original, creative solutions to our problem. While timing ourselves for eight minutes, we attempted to think of eight potential solutions doing the <strong>crazy eight</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GgRUa7rkn1U4-DW6vESY2A.jpeg" /><figcaption>Crazy eight</figcaption></figure><p>Then, we each picked one idea that we thought had the most potential to solving our problem, and elaborated on our idea during the <strong>concept sketch</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ietFZhXD5k3GTgDdTJLg2Q.jpeg" /></figure><p>Noemie and I discussed each of our concept sketches, and felt that working on one single feature of using a pet avatar as part of the app would be the best solution for the problem we wanted to solve. The avatar would grow based on the progress of the student. To proceed with this idea, we created a <strong>site map</strong> for the app to figure out what contents we wanted in the app, and which pages the content belonged to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4wJesi-sHhbCV6qw_QG6Gg.jpeg" /><figcaption>Our initial site map</figcaption></figure><p>To see if our site map made any sense for users, we did an <strong>open card sort </strong>as a way to help us structure the <strong>information architecture</strong> of our product. We approached people that were not part of our UX class and asked them to organize the cards in any way that they thought made sense, and that there was no right answer. We also asked them that they can omit or create new cards if they wanted to. Here are some of the open card sorting results:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DodgRTK1Ut9Qpnu-Ruvr_A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jult4OZpO8lSEICx_1afEw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jrWUCpSCXdmjN7uIJzq4uQ.jpeg" /></figure><p>Based on the feedback we gained from the open card sorting, we revised our site map:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2hW2Jm_xsKWu9DCMukvfrw.jpeg" /><figcaption>our revised site map</figcaption></figure><p>We then proceeded to think of the <strong>user flow</strong> to think of the path(s) that our user would take to complete a task, and also to detect any pain points and simplify our solution quickly. So, we thought of the order in which the user would view and interact with our product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mmHCyAMowgxjlzh0OPMFBg.png" /><figcaption>User flow</figcaption></figure><h3>Step 4: Prototype</h3><p>Finally, here is the part that I enjoyed a lot- prototyping! We wanted to create a <strong>low-fidelity prototype</strong> and test it on as many people as possible, since it was the easiest and quickest way to find feedback and improve our prototype.</p><p>Referring back to our HMW, we thought about what kind of brand image we would like our app to have, and we wanted it to integrate these key elements into the prototype: friendly, intuitive, positing and inspiring. We also quickly created a brand character “Mooji” that makes the users’ experience with the app more approachable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zJfhcYgDLAicr6h33-ReUA.png" /><figcaption>our low-fi prototype content</figcaption></figure><p>We then tested the prototype on several people:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GCUeGXbaO2Mk_51xxnGqXQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*250y6eNERdjpA2tj_6kE1g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xmy9fGk2LYTeHJWOvv8lNg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pvCYynuuP3ZNhL5eH6KfOw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wE5QlP88E7CfmDHCE0ZRVA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YLZlwa9e-41g6rvQ0Xn_Ag.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1vw_fhBTarh7Rbo6Uwc_Ug.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CqLwzmXGppTHYx81SY821w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6m81xqoemVNW_17XdPVsLQ.png" /></figure><p>Here are some of the feedback we received:</p><h4><strong>Glows</strong> (what we did well):</h4><ul><li>flow was clear and smooth</li><li>it was a friendly experience</li></ul><h4><strong>Grows</strong> (what we should improve on):</h4><ul><li>too much text on some pages</li><li>some naming inconsistencies</li><li>some some words were confusing to understand</li></ul><p>After revising our low-fidelity prototype, we proceeded to make a <strong>mid-fidelity wireframe</strong>, and then an <strong>interactive prototype</strong> on <strong>sketch</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*va69uOBvSVPFKIGf1hFisg.png" /><figcaption>wireframe</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EWIG9LYuznCjYlzvbH-M4Q.jpeg" /></figure><p>On our fifth day of working, we presented our idea to our class. Because we only had five minutes to give our presentation, it was a struggle to find the best way to pick out the best, important components of our design thinking process. However, we were able to successfully deliver our presentation, and gain a lot of Mooji fans along the way :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oaa8P6mUk-wpiaFyukuHJQ.jpeg" /><figcaption>Noemie and I presenting our solution</figcaption></figure><h3>Final Thoughts</h3><p>The five days went by very quick, but looking back, we learned a lot, and accomplished a lot! Thank you to everyone (especially those who we interviewed) who helped us through the way. I’d like to also thank <a href="https://medium.com/u/33bd3499f0fa">Noémie</a> for being such a great partner to work with- the week was tough, frustrating and tiring at times, but we both felt so passionate about our product in the end.</p><p>Looking back at how we worked, here are some learnings that I would like to keep in mind for the coming projects:</p><ul><li>we wanted to try and find/do so many things; we should prioritize and eliminate what we need to do, or even collaborate with teams during the research phase</li><li>it was easy to drift off into thinking of ideas and solutions at the empathize phase; trust the process, and only focus on one step at a time</li><li>always, ALWAYS think about the user; we are not the user!</li></ul><p>To those who made it through reading this long process… thank you!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/501/1*yK0Fr3LytOe3gpoqGMVdEA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42f19b0729b2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[University of Virginia — Website Usability Report & Redesign]]></title>
            <link>https://medium.com/@kanamclaughlin/university-of-virginia-website-usability-report-redesign-91485a04519f?source=rss-d6ce086c8510------2</link>
            <guid isPermaLink="false">https://medium.com/p/91485a04519f</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Kana McLaughlin (Saechout)]]></dc:creator>
            <pubDate>Fri, 04 Jan 2019 13:07:26 GMT</pubDate>
            <atom:updated>2019-01-04T13:07:26.028Z</atom:updated>
            <content:encoded><![CDATA[<h3>University of Virginia — Website Usability Report &amp; Redesign</h3><p>For my final deliverable for the Ironhack course prework, the task was to do a case study on the usability of a university website, and propose changes that would solve the pain points that I would discover.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/725/1*de_xC1jVtjVCCC0rTiZkNg.jpeg" /></figure><p>I decided to choose the website of the <strong>University of Virginia</strong> for this case study, as it was the university I attended for my undergraduate studies. To give a short introduction of the University, the school is located in Charlottesville Virginia and was founded in 1819 by former President Thomas Jefferson as a public university. There are approximately 16,034 undergraduate students and 6,771 graduate students, with 16,788 total faculty and staff. The school offers 121 majors across eight undergraduate and three professional schools. The historic campus is ranked as one of the most beautiful campuses in the US, and is internationally protected by UNESCO.</p><p>Here is what the home page looks like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C6G_02dee7ECt5hsfYRw_A.png" /><figcaption>the University of Virginia website</figcaption></figure><p>To <strong><em>determine the usability</em></strong> of the website, I asked a friend several questions (written below) about the website as I kept track of how many clicks/where he clicked. Before we get started, let me give you some information about my friend:</p><ul><li>Name: David</li><li>Age: 27</li><li>Profession: Research Scientist designing executing and analyzing experiments</li><li>Language: Bilingual in English and German</li></ul><p>To start off the observation, I asked him <em>two questions</em> about the overall look/feel of the website.</p><p><strong>Q1: What do you think about the website? First impressions?</strong></p><ul><li>crowded</li><li>home page screams “sports”</li><li>blue and orange</li><li>navigation looks clear at the top</li></ul><p><strong>Q2: What do you think about the navigation of the site?</strong></p><ul><li>easy to understand</li><li>easy to use. Sometimes with other websites, their navigation is annoying since the drop down menu disappears easily, or changes easily to something you are not looking for. But with the university website, it was not a problem at all.</li></ul><p>Next, I asked him to do the following <em>three tasks</em> without using the site’s internal search feature. I kept track of the clicks he took to see how easily or difficultly he completed the task, and ultimately to observe pain points.</p><p><strong>Task #1: Find the school mascot</strong></p><p>Home page → about us → Go to about us → about us → Facts &amp; Figures → Admission → Sports &amp; Recreation → athletics→ Fans/’Hoo Crew→ Student Experience→ Fans/traditions → Cavalier mascot</p><p><strong>=</strong> <strong>Total: 11 clicks</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uOjUaqTWnTvh4f8sE6fS7g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IdPxs_8yWbH6rBDCTmA4qw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G2bH_oZIDhRzViEVoawW4w.png" /><figcaption>Home page → Athletics Page → Mascot information</figcaption></figure><p><strong><em>Pain Points:</em></strong> On the Sports &amp; Recreation page, there was a picture of the mascot but no information about it. But since he found it under a sport category page, he decided to click the Athletics button, which took him to another site that was simply dedicated to sports. Although the navigation at the top was easy to locate, some tabs had so many options below it (Athletics had 24 options, Fans had 23, etc). Having so many tabs and none clearly about the mascot made it even more frustrating for him to find the right page. Also, there was a button with a picture of the mascot again near the bottom of the athletics page called “Student Experience” but it did not open. In the end, he scanned through all the many options under each tab on the athletics page, and tried his luck with “traditions,” where he eventually found information about the university mascot as well as other tradition related information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W7SPbOJnS3LWMaTnJV5v6Q.png" /><figcaption>on the very right, the “Student Experience” button that did not open</figcaption></figure><p><strong>Task #2: Find if the school offers foreign language instruction for Arabic</strong></p><p>Home page → Academics → Undergraduate studies → Academics → Schools → College and Graduate School of Arts &amp; Sciences → Academics → Academic Department and Programs → Middle Eastern &amp; South Asian Language &amp; Cultures → Arabic</p><p><strong>=</strong> <strong>Total: 10 clicks</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eR26ncu_AMsMq_owRTA78Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*muT6e6bK2hwdd_GXVaWlig.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fNoi8Yu1rXz_PhY0koM_9g.png" /><figcaption>Academics → Schools → Middle Eastern &amp; Southern Asian Language &amp; Cultures</figcaption></figure><p><strong>Task #3: Find the nearest airport</strong></p><p>About us → Visit → Maps &amp; Direction → By Air → Charlottesville-Albemarle Airport website</p><p>= <strong>Total: 4 Clicks</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QJkO3NfCNMl4RiGzwrPrVg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DTEh-gzjGqSRCnOIikkVqg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BZRmDiUjcOTXTKuYCljScg.png" /><figcaption>Visit → Maps &amp; Directions → Charlottesville-Albemarle Airport website</figcaption></figure><p>Based on the observations I made of my friend as he navigated the website for the tasks, here are <strong><em>some pain points</em></strong> that should be taken into consideration when re-designing. Out of the three finding tasks I gave him, all three tasks eventually led to an external link (left the home page). With one out of the three (finding the nearest airport), the answer was immediately easy to find, as the external link simply led to the airport website. When finding if the school offers foreign language instructions for Arabic, we jumped from the homepage to the website for the Department of Middle Eastern &amp; South Asian Language &amp; Culture. From there, finding the Arabic section was straight forward. So, two out of the three finding tasks were rather easy.</p><p>The biggest problem my friend had was when he had to find the school mascot. Although the number of clicks (11) does not sound too much, the amount of time needed to skim through all the tabs took time, and as mentioned earlier, when a button with a picture of the mascot did not open, it made the experience a little frustrating for him. This task took about five minutes, when the others took less than three minutes.</p><p>My solution is to simplify the athletics page, as it is the page that has a lot of information and takes time to process. I will simplify the page by breaking up the tabs under each menu into meaningful subcategories, so that instead of finding many tabs that are broadly cluttered under just “Fans” in alphabetical order, users can identify what they are looking for in a more categorized way. Additionally, it would be useful to integrate some of the information into the home page as well, so that users won’t have to jump to another site to access the information they need.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z16qr2To2BfPe01m120GZw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g0Z0SOyUCC3PlRWoeWOqhw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yICltugrGxYv9h_6Q4fKog.jpeg" /></figure><p>This exercise has put many things into <em>perspective</em>- one mainly that even though a website may look nice, if users run into any difficulty finding something they want to know about, then all that is left in the end is the frustrating experience. It’s so important to put the users perspective and opinion into designing anything in order to accomplish a product that people feel <em>comfortable and confident</em> using. Initially, I thought it was all about the number of clicks that determine the usability of the website, but I was wrong- as long as the website gives a clear direction to the user where to go, it is a lot less confusing that users being left confused reading through everything on the page and having to guess what to click, which in many cases did not lead them to the right page.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=91485a04519f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wireframing Challenge]]></title>
            <link>https://medium.com/@kanamclaughlin/wireframing-challenge-30493cf1ba1?source=rss-d6ce086c8510------2</link>
            <guid isPermaLink="false">https://medium.com/p/30493cf1ba1</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Kana McLaughlin (Saechout)]]></dc:creator>
            <pubDate>Tue, 01 Jan 2019 21:29:22 GMT</pubDate>
            <atom:updated>2019-01-01T21:29:22.430Z</atom:updated>
            <content:encoded><![CDATA[<p>For this exercise, the challenge was to create simple wireframes that represent the flow of a product called emov. Emov is an electric car rental app that launched in December 2016, starting off in the city of Madrid. With already 40,000 users, they are planning to grow in other cities in Spain and Germany.</p><p>In order to understand wireframes more, I tried to reverse engineer the high-fidelity mockup screens for the app into low-fidelity wireframes. Throughout this exercise, I refered back to the IH Wireframing Kit as it provided useful elements while creating the wireframes.</p><p>Here are the seven screens that I reverse engineered:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yV7VMPjhsml9v45uD8V1sQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QzkTFDBwkZRQKDDlc5PIpg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hIrGM3uyUtIvoZaKyL-UJQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rrLq600P7iyfIoUoANplaA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z4tI5WQ7Y0HiqvznKvZHWw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M_wEQI36t0Az4LKt3KDKbQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gDD1vik9TFWBMB7WFGLfBA.png" /></figure><p>The exercise challenged me to think about not getting into too much detail, but rather minimizing the amount of information on the wireframes so it does not distract people from the main point, which was to show the flow of the product. Overall, the task was straight forward and I feel comfortable using Sketch each time I work on an exercise.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30493cf1ba1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kana_Design Thinking Exercise]]></title>
            <link>https://medium.com/@kanamclaughlin/kana-design-thinking-exercise-2cad9ee2bfc5?source=rss-d6ce086c8510------2</link>
            <guid isPermaLink="false">https://medium.com/p/2cad9ee2bfc5</guid>
            <category><![CDATA[payments]]></category>
            <dc:creator><![CDATA[Kana McLaughlin (Saechout)]]></dc:creator>
            <pubDate>Thu, 27 Dec 2018 21:40:02 GMT</pubDate>
            <atom:updated>2018-12-27T21:46:28.789Z</atom:updated>
            <content:encoded><![CDATA[<p>In this article I’ll be talking about a case regarding a bank client that is looking to shift into a more technological and user friendly company, and a potential approach that caters to their needs.</p><p>A little about the client company:</p><p><strong>Whole Bank</strong> is a traditional bank that offer a different way to save and manage money by giving customers innovative options such as virtual currencies.</p><p>Recently, they have realized that the conventional Credit/Debit System causes big inconveniences for their traveling customers. Typically, cards offer perks that make money transactions easy for people — customers do not have to carry cash, it takes less time to complete a purchase, and customers can easily get cash using debit cards at ATM machines. However, when customers travel, they run into <strong>problems</strong> like the following:</p><ul><li>customers may lose their cards</li><li>some some shops do not allow credit/debit card payments</li><li>physical cards are susceptible to damage</li></ul><p>In order to deal with these problems, Whole Bank wants to give customers access to a payment features via their mobile devices exclusively when traveling.</p><p>Using the <strong>Design Thinking methodology</strong>, I will be tackling the challenge Whole Bank faces and create a <em>user friendly</em> mobile app solution. The methodology consists of the following steps: <strong>Empathize</strong>, <strong>Define</strong>, <strong>Ideate</strong>, <strong>Prototype</strong> and <strong>Test</strong>.</p><ol><li><strong>Emphasize: </strong>To dive deeper into the problem and understand who I am designing this product for. This step helped me open eyes to situations and issues that have beyond my experiences, therefore will help me develop a better understanding of the customers’ unmet/ unarticulated needs. The following are several of the <strong>questions</strong> that I asked throughout my interview with five people:</li></ol><ul><li>Do you use both cash and credit card? Ratio? And what factors affect when you use what?</li><li>Any frustrating experiences using credit cards?</li><li>Regardless of the way of payment, what kind of problems do you run into when paying for anything?</li><li>How would you feel about using a mobile app instead of a credit card?</li></ul><p>2. <strong>Define</strong>: From asking the questions above, the five people interviewed provided me with several insights that highlight some <strong>pain-points.</strong></p><ul><li>some smaller stores/restaurants only accept cash</li><li>using credit card is so easy, that overspending is a problem</li><li>when overspending, banks can block card since it can be seen as “suspicious activity”</li><li>tracking usage of credit card is a burden often, because you need to look it up on your digital device</li><li>although very unlikely, card can get stolen</li><li>when using credit card, it’s difficult to divide payment with other people (for example, when eating with your friends at a restaurant and you want to divide up the total fee)</li><li>when traveling to another country, sometimes you don’t know how much to tip/ what is expected when tipping</li><li>sometimes, it’s difficult to get a feeling of how much you are paying with a foreign currency relative to the currency you are used to</li></ul><p>In addition to the questions above, I asked them about how they would feel about having a mobile app instead of using a physical credit card, and here are additional insights I gained:</p><ul><li>app should allow users to track their usage/spending</li><li>having in-between-user payment function would make dividing payments easy</li><li>finger print scan before payment would make app more reliable from security perspective</li><li>payment summary with a recommended amount of tip</li><li>in case of trouble with payment, easy access to bank’s customer service would be helpful</li></ul><p>3. <strong>Ideate</strong>: Based on the insights I have gained, I the reorganized information and sketched out three potential solutions that could solve pain points. Out of the three, I picked one that I felt would help travelers most when using the app.</p><p>4. <strong>Prototype</strong>: The “good” idea that I decided to go with from the ideate phase into the prototype phase was the in-between-user payment option. This feature would allow users to not worry about having to calculate how much each person would have to pay.</p><p>Here is a quick sketch of the prototype that tests to see if the function works.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*arJuSoNBFeHj3Px4w54Eog.png" /><figcaption>prototype sketch of app feature that allows in-between-user payments</figcaption></figure><p><strong><em>Takeaways from this exercise:</em></strong></p><p>This exercise has helped me realize that in order to create a “good product,” one of the important things to consider is to listen to the voices of potential users. Through the interview process, I learned things that I would have never thought of, and those led to ideas that would help me build a product that will make the lives of travelers more easy and enjoyable, and ultimately help Whole Bank shift into a more technologically advanced company.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2cad9ee2bfc5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>