<?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 Sam on Medium]]></title>
        <description><![CDATA[Stories by Sam on Medium]]></description>
        <link>https://medium.com/@sammc1999?source=rss-31e18cb6ad55------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*2J_Se6E-xoecxTAL5o38Uw.jpeg</url>
            <title>Stories by Sam on Medium</title>
            <link>https://medium.com/@sammc1999?source=rss-31e18cb6ad55------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 16:03:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sammc1999/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[Leveraging AI magic: streamlining UX design for a financial planner’s website]]></title>
            <link>https://medium.com/design-bootcamp/leveraging-ai-magic-streamlining-ux-design-for-a-financial-planners-website-redesign-e36980069314?source=rss-31e18cb6ad55------2</link>
            <guid isPermaLink="false">https://medium.com/p/e36980069314</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[chatgpt]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Sam]]></dc:creator>
            <pubDate>Thu, 17 Aug 2023 18:05:36 GMT</pubDate>
            <atom:updated>2023-09-03T16:20:59.422Z</atom:updated>
            <content:encoded><![CDATA[<h4>How I use ChatGPT to streamline my UX design process</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cVlikh3-QLg8fC3SCWUjpA.png" /><figcaption>Hero Image — Text reads: ChatGPT &amp; UX Design — <a href="https://unsplash.com/@ilgmyzin">source</a></figcaption></figure><p>Where to begin? ChatGPT seems to be taking over the world, especially the design world. Here’s how I use it to expedite my UX process and most importantly — keep the stakeholders and users at the centre of the decision making.</p><p>So, what first? Well, for the purpose of this experiment I wanted to push the boundaries of what Chat (yes I call it Chat now, a proper noun, a person, place or <em>thing</em>?) can do. I was intentionally hands off when it came to each step of the process that follows to see what it was capable of by itself.</p><p><strong>Step 1: Tell ChatGPT that they’re a UX design expert and that you need its help (badly).</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kkVaevVBfiGTow8WrCb2Pg.png" /><figcaption>Screenshot of me telling Chat that it’s an expert in UX design</figcaption></figure><p><strong>Step 2: Ask it for questions for your interview.</strong></p><p>When interviewing anyone who is seeking a new website for their business, it&#39;s important to gather information about their specific needs, target audience, and goals. Here are some questions you can ask to get started:</p><blockquote>1. What is the primary purpose of your website? Is it to generate leads, provide information, facilitate client communication, or something else?</blockquote><blockquote>2. Who is your target audience? Can you describe the ideal client or customer you want to attract?</blockquote><blockquote>3. What sets your financial planning services apart from competitors? What is your unique value proposition?</blockquote><blockquote>4. Can you outline the key services or offerings you provide to clients?</blockquote><blockquote>5. Do you have any specific branding guidelines or existing marketing materials that need to be considered in the website design?</blockquote><blockquote>6. What are the main goals you want to achieve with the new website? Examples could include increasing conversions, improving user engagement, or enhancing brand visibility.</blockquote><blockquote>7. Are there any specific features or functionalities you would like to include on your website? This could be online appointment scheduling, client login portals, financial calculators, or any other relevant tools.</blockquote><blockquote>8. Do you have any preferences for the visual style of the website? Are there any existing websites or designs that you find appealing?</blockquote><blockquote>9. How frequently do you plan to update or add new content to your website? Will you require a content management system (CMS) for easy updates?</blockquote><blockquote>10. Have you conducted any research or gathered user feedback regarding your existing website or desired improvements?</blockquote><blockquote>11. Do you have any specific budget or timeline constraints for the website project?</blockquote><blockquote>12. Are there any legal or compliance considerations that need to be addressed in the website design or content?</blockquote><p>An Appendix of all the questions is available at the bottom of this article.</p><p><strong>Step 3: Do the interview — ask the questions.</strong></p><p>I can’t speak to the soft skills required to keep the conversation flowing in a 1:1 interview with a stakeholder. Perhaps you can learn more <a href="https://www.nngroup.com/articles/user-interviews/">here</a>. I can say that it’s incredibly important to get as much information from your client as possible, the greater depth of their answers and the more they know about their business needs, the better.<strong><em> </em></strong><em>This won’t always be the case, that’s where your soft skills as a listener come in.</em></p><p>Everything that I’ve learned over the years has been relatively intuitive — listen earnestly, ask questions, make eye contact, use appropriate physical and auditory cues to alert the interviewee that you are in fact — listening. “Mmhmm” is a personal favourite of mine.</p><p><strong>Step 3.5: Record the interview</strong></p><p>I’ve used Microsoft Word to dictate and transcribe interviews in the past, it does an alright job, there are better options available. Google Meet and Microsoft Teams also have built in transcription that’s pretty solid for virtual meeting (you have to enable it, as it’s off by default). Another path would be to record an in-person conversation with a desktop microphone and transcribe it after the fact with software like <a href="https://dovetail.com/help/transcribe-video-and-audio/">Dovetail</a>, this can also be done using Microsoft Word by uploading the MP3 file after the fact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VLv0gfJMvvTQ0jka7Q4INg.png" /><figcaption>Asking ChatGPT for help!</figcaption></figure><p><strong>Step 4: Punch it into Chat and gape in awe!</strong></p><p>Okay, that was a bit facetious, you need a good prompt. Typically, I ask Chat to surmise the conversation in a few hundred words and to hit the main points at the end in bullet form. This gives a good overview with which to start your research.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*STaknIHFYOPxJPyeGpVfJQ.png" /><figcaption>ChatGPT summary of the interview</figcaption></figure><p><strong>Step 5: What about the clientele?</strong></p><p>Me? I dunno… What do you think Chat?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CtsIbE73Y4KzhFihAi51yg.png" /><figcaption>Summary of the clientele</figcaption></figure><p><strong>Step 6: The Persona!</strong></p><p>Ask Chat to create a persona using the data gathered during the interview stage. This comes out in text format, but you can use any number of persona templates in Figma to visualise this info for the purpose of documentation. I like <a href="https://www.figma.com/community/file/881830156311997001">this</a> one. It is important to specify that the persona be based on existing or potential clientele depending on what the client has specified during the interview.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vbrLAWK3ycCLv0gT2idvqg.png" /><figcaption>User Persona based on interview insights created by ChatGPT</figcaption></figure><p><strong>What did I do with all this information?</strong></p><p>From here, you might wonder, what can I do now? I certainly did, my search led me to this <a href="https://www.figma.com/community/plugin/1228969298040149016/Wireframe-Designer">plugin</a> by <a href="https://www.figma.com/@chenmu">Chenmu Wu</a>. A truly wonderful tool. From here, I asked Chat to come up with some typical journeys that this user might go on as they peruse the site. Specifically I asked it to write the user journey that Katherine might take.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_dOUhF-kBHgiIjqAnCiRQQ.png" /><figcaption>An example of one user journey that Chat wrote</figcaption></figure><p>What if i ask for screen flows? <em>Nay</em>, Demand!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8s5uC94nFfDRdkIO4yo-7Q.png" /><figcaption>Tuning the output for input into the Figma Plugin</figcaption></figure><p><strong>Step 7: The Wire-frame</strong></p><p>After this I prompt the model to write a wireframe prompt for the plugin mentioned earlier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5SGQWc-wVttHLfAo9fGnhQ.png" /><figcaption>Wireframe prompts created by ChatGPT</figcaption></figure><p>From here, I could feed this into Wireframe Designer in Figma. Do you see where I’m going with this…?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dg9osfoerfs6EdmXOVQV1w.png" /><figcaption>Figma wireframe first draft</figcaption></figure><p>Not a bad first draft, but we can dial it in a little more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*shRzN2Kf7uPvs2z7AIssyg.png" /><figcaption>Wireframe designer context field</figcaption></figure><p>Wireframe designer has a context field where I can feed it the persona that we developed earlier! You can also specify mobile vs desktop outputs.</p><blockquote><em>@</em><a href="https://twitter.com/WCMuu"><em>chenmuwu</em></a><em> on X (formerly Twitter), I’d love to see further development of this plugin — specifically the ability to easily create multi page flows would be incredible, and to have a history option of the prompts given would be great too.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wCEVMf8XKHYFWKRfvD9HIA.png" /><figcaption>Figma Screenshot of UI Mockup</figcaption></figure><p><strong>Step 8: Apply your Design System / Visual Design Skillz</strong></p><p>Not my best UI work, but certainly not my worst. As a proof of concept, this is incredible work that can be completed in a fraction of the time that it normally takes.</p><p><strong>Step 9: Profit???</strong></p><p>Use that saved time to design 10x more websites, just kidding, go touch some grass you desk jockey, pet a dog, step on a crunchy dry leaf!</p><p>In all seriousness, this is a great way to speed up your UX process, all the PM’s out there will hate me for suggesting this shouldn’t make the business more productive. It should be used to speed up tedious work.</p><p>To all the IP folks out, at least give me some credit for this. A footnote at the bottom of your site would be nice.</p><p><strong>Summary of the process:</strong></p><p>- Treat ChatGPT as a UX design expert and seek its help.<br>- Ask ChatGPT to provide interview questions for client discussions.<br>- Conduct the interview with clients to gather specific website needs and goals.<br>- Record the interview for accuracy and efficient note-taking.<br>- Request ChatGPT to summarise the conversation<br>- Create a user persona using ChatGPT’s insights from the interview data.<br>- Ask ChatGPT to generate typical user journeys <br>- Ask ChatGPT for obtain wireframe prompts <br>- Refine and input wireframe prompts into Figma’s Wireframe Designer.<br>- Apply design skills to refine the UI and create a proof-of-concept.</p><p><strong>Conclusions and thoughts:</strong></p><p>This AI powered process allowed me to complete a proof on concept design in a few days, whereas for this level of research, it may have taken multiple weeks. I believe this would be increasingly useful if you were interviewing multiple stakeholders on a more complex project. As a proof of concept I believe this case study demonstrates the capabilities of utilising AI in any given UX design process.</p><p>It’s only a matter of time before someone adds the capabilities of ChatGPT to their product — Dovetail? Miro? They all have basic “insights” but these mostly differentiate between positive and negative interactions. Miro can theme by sentiment but I believe only it uses keywords to distinguish data points and does not holistically analyse the entire data set.</p><p><strong>Moral Implications:</strong></p><p>As someone new to the UX field, this new techisn’t particularly foreign to me as my process isn’t as refined as that of someone with more experience. In saying that, I mean that the idea of using AI as a compliment to my skillset is not bad one. I believe that “doing it the hard” way is simply slower, this process allows me to streamline the tedious parts, the very nature of which is slow and dull. Coding data to extract relevant insights is time consuming and not always an objective process, especially if you’re one designer working alone. It also allows me to focus on the important thing — the person using the product. The end user should always be championed by the UX designer, this is especially important as we move into the age of AI generated interfaces and products where the promise of tailored UX is great, but potential for failure is high.</p><p>Having said all that, the need to verify the information that an AI model like ChatGPT exports, is incredibly important. Knowing your data, and paying attention to any discrepancies is key. This should not replace a UX designer/researcher, not in its current state. Give it… 6 month, <em>maybe</em>.</p><p><strong>Appendix:</strong></p><p><a href="https://chat.openai.com/share/ba556fad-508a-461e-bc21-53243d2bf4ad"><strong>Link to full Chat </strong>— https://chat.openai.com/share/ba556fad-508a-461e-bc21-53243d2bf4ad</a></p><p><a href="https://www.notion.so/ChatGPT-Interview-Questions-175da954b5d4436686c27ce8c8d28d1b?pvs=4"><strong>List of Full Questions </strong>— https://www.notion.so/ChatGPT-Interview-Questions-175da954b5d4436686c27ce8c8d28d1b?pvs=4</a></p><p><a href="https://www.nngroup.com/articles/user-interviews/"><strong>Learn more about interviewing </strong>— https://www.nngroup.com/articles/user-interviews/</a></p><p><a href="https://www.figma.com/community/plugin/1228969298040149016/Wireframe-Designer"><strong>Figma Wireframe Design Plugin </strong>— https://www.figma.com/community/plugin/1228969298040149016/Wireframe-Designer</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e36980069314" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/leveraging-ai-magic-streamlining-ux-design-for-a-financial-planners-website-redesign-e36980069314">Leveraging AI magic: streamlining UX design for a financial planner’s website</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Met Eireann Redesign — Part 5: Teamwork & Collaboration]]></title>
            <link>https://medium.com/@sammc1999/met-eireann-redesign-part-5-teamwork-collaboration-2d7ba8fa1dba?source=rss-31e18cb6ad55------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d7ba8fa1dba</guid>
            <dc:creator><![CDATA[Sam]]></dc:creator>
            <pubDate>Sun, 30 Jan 2022 21:08:58 GMT</pubDate>
            <atom:updated>2022-03-15T15:34:24.421Z</atom:updated>
            <content:encoded><![CDATA[<h3>Met Eireann Redesign — Part 5: Teamwork &amp; Collaboration</h3><p>This blog details the critique of our teamwork and collaboration.</p><p><strong>Roles</strong><br>At the start of the project we decided on our roles based on our strengths, and decided that each of us would step up a certain phase of the project. Lauren tackled the research and definition portion of the project, Niamh spearedhead the design and iteration and I took on the testing methodology portion of the project. We elected a leader, Lauren that would be the ultimate decision maker, however we generally agreed after our discussions and this was never necessary.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EkYT4bvogUIX_mcQnlzBxg.png" /><figcaption>Team roles</figcaption></figure><p><strong>Teamwork</strong><br>We worked well as a team, generally agreeing on our design decisions unanimously, where there was debate we weighed up the pros and cons based on what we thought would be most useful to the users. Throughout the project, we shared our work in collaborative workspaces; research in <em>Miro </em>and<em> </em>design in <em>Figma</em>. We used <em>whatsapp </em>to communicate what we were working on and when tasks would be complete.</p><p>We scheduled weekly video calls via teams to plan and discuss the work that we had done in the week prior. In retrospect, we should have reserved these meetings for key decision making, deciding on a format pre-meeting as often, working later and later into our meetings caused us to have post meeting burnout.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U3pKUcVkOId7rpMoCGlV0g.png" /><figcaption>Our weekly meeting channel on microsoft teams</figcaption></figure><p>A number of our weekly calls evolved into workshops as we often worked together on Figma to design the prototype. Again, had we decided on a format for the weekly meeting, and made an itinerary through a shared word doc we could have made these meetings vastly more efficient. This is key learning I will take forward regarding remote teamwork.</p><p><strong>Key learnings</strong><br>Being prepared and annotating content are key when working remotely within a team. At certain points, we worked together on the same features of the app to move the project along quicker. Lauren and I worked on the map portion of the app whilst the Niamh worked primarily on the news pages. This approach made things move a little faster and we bounced ideas of each other rapidly. In retrospect this was an incredibly useful way of working collaboratively.</p><p><strong>Key learnings</strong><br>Preparation and annotated sharing of content are essential when working remotely. At one point, we worked in smaller subgroups to rapidly make advancements in the design. This approach made communication fast, and so we rapidly innovated solutions to usability issues. Upon reflection, we could have worked more with the existing app and potentially found more cost-effective design improvements. However, given that finance was not considered with this project, I am happy with the redesign, as testing indicated significant usability and satisfaction improvements to the app.</p><p><strong>Conclusions</strong></p><p>In conclusion, we were very happy overall in how we worked together as a team. We definitely could have made some adjustments to the way we worked, however we never would have known these things if we hadn’t experienced them first hand.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d7ba8fa1dba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Met Eireann Redesign — Part 4: Testing & Evaluation]]></title>
            <link>https://medium.com/@sammc1999/met-eireann-redesign-part-4-testing-evaluation-93f5792e6d53?source=rss-31e18cb6ad55------2</link>
            <guid isPermaLink="false">https://medium.com/p/93f5792e6d53</guid>
            <dc:creator><![CDATA[Sam]]></dc:creator>
            <pubDate>Sun, 30 Jan 2022 20:30:17 GMT</pubDate>
            <atom:updated>2022-01-30T21:02:27.678Z</atom:updated>
            <content:encoded><![CDATA[<h3>Met Eireann Redesign — Part 4: Testing &amp; Evaluation</h3><p>This blog will cover the testing portion of the project, the lead on which was undertaken by myself. It also covers the changes that we made to the prototype following our testing.</p><p><strong>Testing Methodology</strong></p><p>The testing methodology consisted of the following key steps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OxtGuXT_HjvEqCK_kJJ5vw.png" /><figcaption>Testing methodology</figcaption></figure><p><strong>Pre-test questions</strong></p><p>The pre-test questions were a series of simple questions devised to get the user talking during the testing process and also to gather some basic demographic information, whilst we didn’t test a large data set this was useful nonetheless to establish best practice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bkmhtx3vI9FNPqEcx4tYPg.png" /><figcaption>Pre-test questions</figcaption></figure><p><strong>Plan</strong></p><p>The general plan of the testing procedure was as follows; Pre-test questions, Give User Task and ask them to complete it, repeat as necessary until each task was completed. If the user was unable to complete the task we decided on a case by case basis whether or not to give them a prompt in order to allow them to complete the task. Once the tasks portion of the test was completed we asks the user some post-test questions. These questions were primarily qualitative in nature, questions like “<em>What did you think of that task?” </em>or <em>“You struggled at this point, why was that?”. </em>We also asked for any general feedback that the users might have.</p><p><strong>Post Test SUS Questionnaire</strong></p><p>We also followed up the test with a short post test questionnaire using the SUS questionnaire. We used this to gather quantitative data on the usability of our app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*msqIvcqBH-Y3Yjy-71vW2A.png" /><figcaption>Tasks we asked the participant to complete</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qAjkBqSoeSwWG8UOYTk2pg.png" /><figcaption>Post Test Questionnaire Results</figcaption></figure><p>The results of the post test questionnaire were generally positive with the majority of users agreeing that the system was generally easy to use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pcCQT-LP-I7a6yNNPkGVlg.png" /><figcaption>Key pain points</figcaption></figure><p><strong>Key Pain Points</strong></p><p>The primary key pain point that users struggled with was the searching functionality from the homepage. We revised this element and performed a short unmoderated test using the Maze platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oPZBX3fZDkmNgRLw4Uf2aw.png" /><figcaption>Changes made</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j2ZNLEmqKCDxAsBghd37aw.png" /><figcaption>Maze Results</figcaption></figure><p>The results from the maze test were overwhelmingly positive, all participants being able to complete the task at hand.</p><p>References</p><ul><li><a href="https://www.nngroup.com/articles/measuring-perceived-usability/">Beyond the NPS: Measuring Perceived Usability with the SUS, NASA-TLX, and the Single Ease Question After Tasks and Usability Tests</a></li><li><a href="https://maze.co/guides/usability-testing/script/">How to Write an Effective Usability Testing Script &amp; Example</a></li><li><a href="https://www.nngroup.com/articles/usability-testing-101/">Usability (User) Testing 101</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=93f5792e6d53" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Met Eireann Redesign — Part 2]]></title>
            <link>https://medium.com/@sammc1999/met-eireann-redesign-part-2-a9b717f300ed?source=rss-31e18cb6ad55------2</link>
            <guid isPermaLink="false">https://medium.com/p/a9b717f300ed</guid>
            <dc:creator><![CDATA[Sam]]></dc:creator>
            <pubDate>Sun, 30 Jan 2022 20:07:56 GMT</pubDate>
            <atom:updated>2022-01-30T21:08:40.218Z</atom:updated>
            <content:encoded><![CDATA[<h3>Met Eireann Redesign — Part 3 : Design &amp; Iteration</h3><h3>Introduction</h3><p>This blog will cover the design process that was undertaken as a part of the redesign of the Met Eireann weather app and give insight to our decision making as it relates to the progression of the project. It will cover ideation, sketching, initial prototyping and final prototyping. Testing will be covered in a subsequent blog.</p><p><strong>Ideation</strong></p><p>Ideation came from our analysis of the current offering from Met Eireann. Information was generally hard to access, it wasn’t clear what was navigation vs what was information. Lack of certain information , that Met Eireann had access to, like pollen information was not available on the app. It was also lacking some features that are commonplace across many other apps, take a maps functionality for example.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SB7x9IJyVAbd1LArK0CGiQ.png" /><figcaption>Key findings of our user survey data &amp; desk research</figcaption></figure><p><strong>To be task flows</strong></p><p>From the research we did on the current task flow of the app, we established new to-be user flows. These were designed with functionality in mind that was core to the frustrations of our proto-personas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kX3zJig_0OJ8AlNb6ECWxg.png" /><figcaption>example of a to-be task flow</figcaption></figure><p>From these flows, we sketched ideas on how these might be solved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JN4M21vpZzxyzkTc405PNg.png" /><figcaption>Task flow sketches — goal — to check the weather on Sunday in a specific location</figcaption></figure><p>The drawing up of the to-be task flows was integral to the sketches we produced to solve these tasks flows. Had we just jumped into sketching and designing we would have been lost. The sketching stage also proved invaluable as it allowed us to quickly know out ideas without getting into the fine details of the UI which would’ve slowed us down.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j-yMZrWB3BqqagDm4L6zuA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zq8R7Np26GagF3CIaRkKHQ.png" /><figcaption>Examples of task flow sketches — Lauren and Niamh’s respectively</figcaption></figure><p>This sketching stage ended with us deciding on what would be the core flows when we came together as group. This also allowed us to feedback to one another on the screens themselves. It was decided then which screens we would take, and design in a low fidelity prototype.</p><p><strong>Prototyping-prototype 1</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dBzidkjt4e92UNmsmUHpjQ.png" /><figcaption>The initial wireframe/low fidelity prototype of the Met Eireann app</figcaption></figure><p>Once the sketching phase was complete we moved onto produced a low fidelity wireframe/prototype using Figma. This was produced primarily by Niamh, as she was spearheading the design/prototyping phase of the project.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Doembed%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2FnkKUNdxHOmZL6Si38w4AH9%2FMet-Eireann%3Fpage-id%3D0%253A1%26node-id%3D203%253A7627%26viewport%3D241%252C48%252C0.58%26scaling%3Dscale-down%26starting-point-node-id%3D203%253A7627%26show-proto-sidebar%3D1&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FnkKUNdxHOmZL6Si38w4AH9%2FMet-Eireann%3Fpage-id%3D0%253A1%26node-id%3D203%253A7627%26viewport%3D241%252C48%252C0.58%26scaling%3Dscale-down%26starting-point-node-id%3D203%253A7627%26show-proto-sidebar%3D1&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2Fd45810af-e5fb-472d-b410-bd74d99ba841%3Fheight%3D450%26bucket%3Dfigma-alpha&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=figma" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/da25b02c447f17b15906b37cec1f097f/href">https://medium.com/media/da25b02c447f17b15906b37cec1f097f/href</a></iframe><p><strong>Design System</strong></p><p>It was understood that we would need to devise a design system in order to properly brand the app and make it consistent across all pages. Decisions around colour, icons, buttons and illustration styles were made by Niamh as she had stepped up during this portion of the project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BCF0GG09XjBD-8rJct9YUg.png" /><figcaption>An example of the design system components</figcaption></figure><p><strong>Prototype 2</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Doembed%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2FnkKUNdxHOmZL6Si38w4AH9%2FMet-Eireann%3Fpage-id%3D0%253A1%26node-id%3D378%253A8115%26viewport%3D241%252C48%252C0.19%26scaling%3Dscale-down%26starting-point-node-id%3D203%253A7627%26show-proto-sidebar%3D1&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FnkKUNdxHOmZL6Si38w4AH9%2FMet-Eireann%3Fpage-id%3D0%253A1%26node-id%3D378%253A8115%26viewport%3D241%252C48%252C0.19%26scaling%3Dscale-down%26starting-point-node-id%3D203%253A7627%26show-proto-sidebar%3D1&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2Fd75ff2bb-7112-4483-9c30-3855b477faa1%3Fheight%3D450%26bucket%3Dfigma-alpha&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=figma" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/a7c28f55b6c3fb0d39a2b0b2b96f8217/href">https://medium.com/media/a7c28f55b6c3fb0d39a2b0b2b96f8217/href</a></iframe><p>The second iteration of our prototype was based on visual research initially undertaken by the whole team but then concluded by Niamh.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vooECd49rfTBOtDHK5HRsg.png" /><figcaption>A snapshot of the visual research undertaken by the team.</figcaption></figure><p>References</p><ul><li><a href="https://www.nngroup.com/videos/design-systems/">Design Systems and Their Benefits (Video)</a></li><li><a href="https://www.nngroup.com/articles/paper-prototyping-cutout-kit/">Paper Prototyping: A Cutout Kit</a></li><li><a href="https://www.nngroup.com/articles/wireflows/">Wireflows: A UX Deliverable for Workflows and Apps</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a9b717f300ed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Met Eireann Redesign — Part 2]]></title>
            <link>https://medium.com/@sammc1999/met-eireann-redesign-part-2-b981d3f23491?source=rss-31e18cb6ad55------2</link>
            <guid isPermaLink="false">https://medium.com/p/b981d3f23491</guid>
            <dc:creator><![CDATA[Sam]]></dc:creator>
            <pubDate>Sun, 30 Jan 2022 18:58:04 GMT</pubDate>
            <atom:updated>2022-01-30T21:08:10.588Z</atom:updated>
            <content:encoded><![CDATA[<h3>Met Eireann Redesign — Part 2: Team Charter</h3><h3>Introduction</h3><p>This blog covers the plan of our team’s approach to the project, including, the team charter, project plan, timeline and roles &amp; responsibilities.</p><p><strong>Team Charter</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sWfncXFSaD8phXU_KqcqTA.png" /><figcaption>team charter</figcaption></figure><p>A team charter was created to define the skills, areas for growth and kind of designer that each of us is. We used the “designer test” to identify what our strengths might be when it came to contributing to the team effort. <em>See link </em><a href="https://mycreativetype.com/"><em>here</em></a><em>.</em></p><p><strong>Project Plan</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1WKogdP1_dkWTc5Em8U9nQ.png" /><figcaption>project plan made in miro</figcaption></figure><p>We devised a project plan that helped us to understand the different stages of the project that we would undertake. We attempted to mirror the double diamond design process in our project planning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D5urfgVvL7p-PeuBUYeVaA.png" /><figcaption>project goals</figcaption></figure><p><strong>Project Goals</strong></p><p>We had some overarching project goals that were based on our initial, low fi analysis of the Met Eireann app. Primarily we focused on the 1st goal, with the 3rd goal being secondary and so on. Our third goal was orientated around cutting down on the text content of the current app.</p><p><strong>Roles</strong><br>Our roles within the project was oriented around what we wanted to each personally achieve, and also around our current strengths. In a number of the phases we worked individually and then came together to collect our insights and refine them. We worked together very efficiently as a team, each stepping up at intervals, to take charge on a particular section of the project.</p><p><strong>Research</strong><br>The research phase of the project was worked on as a group, but primarily the lead was taken by Lauren, organising the Miro board for each of to input the research we had gathered.</p><p><strong>Ideation</strong><br>We all individually worked on sketches for ideas on improving the app, tasks were based on what was important to our user personas. Then we came together as a group, and decided on what screens were key to complete the task and refine the screens.</p><p><strong>Prototyping</strong><br>To ensure that we would work quickly, we split our prototype into various user flows which we then tackled individually. We prioritised flows that were critical to usability and were new to the users.</p><p><strong>Testing</strong><br>The testing portion of the project was primarily undertaken by myself. I devised our testing methodology and distributed it to the team, which we gave feedback on to refine and improve.</p><p>References</p><ul><li><a href="https://medium.com/productboard-design/how-we-wrote-our-design-teams-charter-together-37807fa6d0ab">How we wrote our Design team’s charter, together</a></li><li><a href="https://www.nngroup.com/articles/pm-research-plan/">Research Plans: Organize, Document, Inform</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b981d3f23491" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Met Eireann Redesign — Part 1]]></title>
            <link>https://medium.com/@sammc1999/met-eireann-redesign-part-1-ae8a64dd7bbf?source=rss-31e18cb6ad55------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae8a64dd7bbf</guid>
            <dc:creator><![CDATA[Sam]]></dc:creator>
            <pubDate>Sun, 30 Jan 2022 18:07:19 GMT</pubDate>
            <atom:updated>2022-01-30T21:12:05.138Z</atom:updated>
            <content:encoded><![CDATA[<h3>Met Eireann Redesign — Part 1: Research</h3><h3><strong>Introduction</strong></h3><p>As part of the seconded module of my MSc. in User Experience Design: User research and interaction design, I worked on a group project to redesign the Met Eireann App. The group consisted of Lauren, Niamh and myself. All the information that we used to inform our design decisions was generated through our own user research methods, as we did not have access to any information from Met Eireann itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-yhKY9ipSQXJ-LXFya3kow.png" /><figcaption>Met Eireann Homepage — Redesign</figcaption></figure><h3><strong>Research Methodologies</strong></h3><p>We used a number of different research methodologies to gather insights on what users might need/want from a redesigned Met Eireann app. We focused on qualitative methods initially to understand and empathise with our users. Then the focus shifted towards quantitative methods in order to ascertain how important the various problems were to establish a hierarchy in terms of problem solving. This proved to be invaluable as the qualitative methods filled in the gaps in the quantitative and vice versa. Had we only focused on one our research would have been left lacking.</p><p><strong>Usability Heuristics Analysis</strong></p><p>Initially a usability heuristic analysis was undertaken on a number of apps, to see what kind of problems we could tackle when it came to this project. We looked at one app individually, including Ticketmaster, Thejournal.ie and of course Met Eireann which we ended up choosing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pKMVNS-HyE6fSAzCv7vWXQ.png" /><figcaption>Usability Heuristic Analysis’ of the three services</figcaption></figure><p>The UHA’s(usability heuristic analysis’) were useful in understanding where these applications/services were failing to comply and give us a general direction on where we might go with the redesign. The Met Eireann app failed in multiple categories which gave us a wide scope of view for redesign potential.</p><p><strong>Competitor Research</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GLO10o6pCOQD29rxWdGDRw.png" /><figcaption>Competitor Research — best &amp; poor capabilities</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*--ncYM-UWvMMYv1UehIp1A.png" /><figcaption>Competitor Research — best and worst practices</figcaption></figure><p><strong>Interviews</strong><br>Interviews were semi-structured which allowed for the gathering of both qualitative and quantitative data. It also allowed us to examine the data quantitatively and understand the various responses we had. Some of the key findings we had included that users were more likely to use the built in app on their mobile device, this prompted us to follow some of the standards these apps use. A number of users were completely unaware that Met Eireann even had a mobile app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TJTYSTq53M5gk1w66tnvYQ.png" /><figcaption>semi structured interview questions &amp; answers — key takeaways</figcaption></figure><p><strong>Surveys</strong></p><p>A number of surveys were also undertaken to inform our design decisions, these were done to gather quantitative data on what kind of use cases people had when it came to their weather app of choice. A total of 4 surveys were circulated to over 100 people. The 4th and final survey was combination of the previous 3, this was done to further probe into the results of the previous 3. It was also circulated to the largest group of over 117 participants. We also wanted to all have a chance at creating a survey, to understand the pitfalls through experience and then improve on our group survey.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R3SmYyX6YyHlIvI-RiE8XA.png" /><figcaption>Initial 3 surveys</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VM7BiHnsFDnFZiFUDH4GXA.png" /><figcaption>Group Survey — Results</figcaption></figure><p><strong>Identified Problems</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rOmr0TJtA4hfZi6W2IXmlw.png" /><figcaption>How might we statements</figcaption></figure><p>The primary HMW (how might we statement) was “how might we- let people know when the weather is about to take a turn, for anyone that needs to go outdoors so they can make effective plans.” This was the general HMW statement, there were others that are more focused on our specific personas.</p><p><strong>Stakeholder mapping</strong><br>As a group, we considered all the various types of users that our redesign could focus on, ranging from low to high impact. We worked together to create a stakeholder map, that allowed us to empathise with users we might not have previously considered. This was a prompt for us to create our proto-personas, that were based on some insights from our surveys.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/988/1*8iyokmROao-aQCaJycSoTw.jpeg" /><figcaption>Stakeholder map</figcaption></figure><p><strong>Personas</strong><br>We each created a persona individually and then came together to discuss the differences between them. An iteration of each was created to improve them, and to contrast them against each other to cover more ground.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wlKT63s930Ug9m-fy6RNkA.png" /><figcaption>The iterated personas</figcaption></figure><p>Each persona was based on key information from our surveys and interviews. For example, the “Piaras — outdoorsy type” had specific wants around weather data of specific locations, so searching and rainfall radars was very important to them.</p><p><strong>Empathy Mapping</strong></p><p>We also each created empathy maps around each of the personas, that helped us to create empathy with our proto-users. It gave us insights into the frustrations that they feel with the current offering.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cl3p4UvAjlworYrDgFNYaQ.png" /><figcaption>Empathy Map of user persona Piaras (see appendix for all empathy maps)</figcaption></figure><p><strong>Customer journey mapping</strong><br>We performed a customer journey map of the current app, that allowed us to understand the main pain points of the current customer journey. It also prompted us for areas to improve upon and new features that we could introduce.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z_MMtXW7gYy38FAyCn0DXg.png" /><figcaption>Current customer journey map (see appendix for all CJM’s)</figcaption></figure><p><strong>User Scenarios — to be</strong></p><p>To be user scenarios were created based our personas needs within the application, this gave us more prompts on new features that could design to improve their user experience. It also helped us to create tasks that users would complete within the app that would help us create task flows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DTUQLucUQ8s4fWUM3qJMmA.png" /><figcaption>To be- user scenario (Piaras)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NF2EQZvVM4EaGHKdlkUDfg.png" /><figcaption>Storyboard of To Be Scenario</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kX3zJig_0OJ8AlNb6ECWxg.png" /><figcaption>Task Flow Analysis — To be Scenario</figcaption></figure><p><strong>Appendix</strong></p><p>Interviews:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*67IUUga6aghR3W61tHnZpA.png" /><figcaption>Laurens user interview results</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ESMwoGCITcWD02XlGfh4RA.png" /><figcaption>Niamh user interview results</figcaption></figure><p>User Personas:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*msYhQetoRKYKXqCuJxwzug.png" /><figcaption>User persona — Lauren</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0VznqqdnLeD_VUeliv2nKg.png" /><figcaption>User persona — Niamh</figcaption></figure><p>User Empathy Maps:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u84dGE54nTpYT3uRo8GkLQ.png" /><figcaption>Empathy map — Lauren</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FWbxh3v3KUyjgy2hzhlOwQ.png" /><figcaption>Empathy map — Niamh</figcaption></figure><p>Customer Journey Maps:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yODwbh4y394FD7YAFlIMYg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o1UmHZBkE8YrqZ7YhzvSJA.png" /><figcaption>Customer Journey Maps — Lauren &amp; Niamh</figcaption></figure><p>Task Analysis:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_P4vySvoVsRhBJI2rOWHZg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F8P__N8nhQsNO_14XLcCfg.png" /><figcaption>Task Analysis — Lauren &amp; Niamh</figcaption></figure><p>References</p><ul><li><a href="https://www.nngroup.com/articles/user-interviews/">User Interviews 101</a></li><li><a href="https://www.nngroup.com/articles/empathy-mapping/">Empathy Mapping: The First Step in Design Thinking</a></li><li><a href="https://www.nngroup.com/articles/wireflows/">Wireflows: A UX Deliverable for Workflows and Apps</a></li><li><a href="https://www.nngroup.com/articles/ten-usability-heuristics/">10 Usability Heuristics for User Interface Design</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae8a64dd7bbf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing A Carbon Tracking Shopping App: Evaluation & Reflection]]></title>
            <link>https://medium.com/@sammc1999/designing-a-carbon-tracking-shopping-app-evaluation-reflection-6737dda3b509?source=rss-31e18cb6ad55------2</link>
            <guid isPermaLink="false">https://medium.com/p/6737dda3b509</guid>
            <dc:creator><![CDATA[Sam]]></dc:creator>
            <pubDate>Mon, 08 Nov 2021 23:10:20 GMT</pubDate>
            <atom:updated>2021-11-08T23:10:20.232Z</atom:updated>
            <content:encoded><![CDATA[<p>In this blog I will reflect on the project as a whole, including team management, research, prototyping and a critique of our final prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MkSkH946F6wC4kTGqJX-PA.png" /><figcaption>Our Team Miro Board — <a href="https://miro.com/app/board/o9J_lsPKZ9M=/?invite_link_id=611947301414">https://miro.com/app/board/o9J_lsPKZ9M=/?invite_link_id=611947301414</a></figcaption></figure><p><strong>Team Management</strong></p><p>All though we didn’t meet as frequently as I would have liked, I think we worked quite effectively as a team. Our meetings tended to be concise, focusing on what needed to be done, but I do feel we were always a little behind the other groups on the project. We used Miro to share our work and ideas, which was very helpful for giving each other tasks to complete, once it was uploaded to Miro it felt done.</p><p><strong>Prototyping</strong></p><p>I do think we could have, however, collaborated more effectively on the prototypes that we created. It was dificult to collaborate effectively on the paper prototypes, as of course they’re a physical medium and we could only work on those in person. Having an in person meeting would have potentially a way to work around this. However, having just one person work on the final paper prototype was definitely more efficient to get it over the line, even if it had it’s drawbacks.</p><p><strong>User Research</strong></p><p>As I mentioned in a previous blog, our user personas were based on our assumptions, and they were only useful to a certain extent. I think if we had done a basic survey, or interviewed some people we would have owned the personas more, as once we had finished them and created tasks from their scenarios, we really had little use for them after that. We also never went back and tested our designs against the primary persona to see how they might have found problems with it, nor did we test it against a secondary persona we had in the mix early one, which also could have been a great way to find flaw in our designs and would have been a good contrast to our primary personas needs.</p><p><strong>Testing</strong></p><p>Our testing methodology was quite loose, and not easily repeatable. During our testing we found it dificult not to lead the user down the right path. As such, none of our users were actually able to complete their tasks. We also learned the limits of paper prototyping, being unable to prototype interactivity and feedback to the user. This made our testing dificult as one of the key components of our task require interactivity and feedback. Had we made a digital wire-frame, we might have had more luck with this portion of the testing.</p><p><strong>Our Final Design</strong></p><p>Following our testing, we found numerous flaws with the proposed prototype, primarily our comparison system was clunky, and unclear as to how it worked. We added a small on boarding session that explained the carbon coin system, which all our participants had found confusing. Generally, we cleared up the user interface and stripped it down to it’s essential components that made the flow through it a lot easier. We also did an impromptu test on this new iteration, by no means a comprehensive test, but we found that the flow was generally a lot easier for the user.</p><p><strong>What did I Learn</strong></p><p>Investing in more in-depth user research would have been supremely beneficial, and given more weight to our design decisions. I think, if we had more clearly defined personas based on interviews and research, we would have looked back to them more.</p><p>I learned a lot about the do’s and dont’s of user testing, the testing process itself is almost something that needs to be tested itself in order to conduct a proper test.</p><p>I thoroughly enjoyed the paper prototyping as a means to quickly test design solutions, but understand it’s limitations, it definitely has a specific use case, which was good to learn through experience.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6737dda3b509" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing A Carbon Tracking Shopping App: Prototyping]]></title>
            <link>https://medium.com/@sammc1999/designing-a-carbon-tracking-shopping-app-prototyping-c75a8c3ec1e5?source=rss-31e18cb6ad55------2</link>
            <guid isPermaLink="false">https://medium.com/p/c75a8c3ec1e5</guid>
            <dc:creator><![CDATA[Sam]]></dc:creator>
            <pubDate>Mon, 08 Nov 2021 18:21:49 GMT</pubDate>
            <atom:updated>2021-11-08T18:21:49.911Z</atom:updated>
            <content:encoded><![CDATA[<p>After our research phase of the project was completed we moved onto the prototyping portion of the project. Based on the context provided by our fictional user scenarios we decided we wanted to prototype the task of comparing items in-store via the app to understand their carbon impact.</p><p>We started with a simple task analysis of what this could potentially look like. This also provided some requirements for the screens we might need to design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YgtB_89BnLF5-Y8IlnrRug.jpeg" /></figure><p>After this we moved onto a task flow analysis to better understand the screens we would need to design alongside the features we would need to prototype for our paper prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HJJeoVGkyxCFqNw9m3ruWw.jpeg" /><figcaption>Task Flow Analysis</figcaption></figure><p><strong>Problem Statement</strong></p><p>Problem statements define the problem that the design intends to solve, something to measure your design solution against.<a href="https://www.nngroup.com/articles/problem-statements/">(Nielsen, 2021)</a> Our user needs statement:</p><p><em>“Users need an easy way by which to compare the carbon footprint of a item to another, and to easily ascertain the difference between them.”</em></p><p><strong>Paper Prototype</strong></p><p>Once we had our problem statement and task at hand, we began prototyping potential solutions to the problem.<a href="https://www.nngroup.com/articles/paper-prototyping/">(Nielsen, 2003)</a> We came up with a carbon coin system based on the average amount by which every person on the planet needs to reduce their carbon emissions by in order to stop global warming. The carbon coins act as a wallet with a monthly allowance, with users being able to spend the coins as they purchase items.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7TfMfnsuasJJWijrDZYMvg.jpeg" /><figcaption>Our first paper prototype</figcaption></figure><p><strong>Testing</strong></p><p>During the testing of our first prototype we were aiming to test a few different tasks, primarily the task:</p><blockquote>“Compare the carbon footprint of a few items and add the one with the lowest footprint to your basket.</blockquote><blockquote>In this scenario, we need you to try and compare a few items to each other under their carbon footprint, and then add the one with the lowest carbon footprint to your basket. Take your time, there are no wrong answers.”</blockquote><p>We handed the user a piece of paper with this task written on it for them, and asked them to read this aloud, this was to get them into speaking aloud as we also wanted them to talk aloud what they were thinking as they worked their way through the task we had set them. After testing, we asked the user for any big problems they’d had completing the task or any suggestions they may have had for the design. Our testing methodology was based on a few principles of testing laid out by the Nielsen Norman group. <a href="https://www.nngroup.com/articles/usability-testing-101/">(Nielsen Norman 2019)</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*BFfNA3W1qnavuXIfsw39Mg.png" /><figcaption>Testing Our Paper Prototype</figcaption></figure><p><strong>Results</strong></p><p>We learned a number of things from testing our paper prototype, primary a number of errors made by users due to the design of the application. They are listed in the diagram below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aF4P2SG-sGzzqwBGKGf7iw.jpeg" /><figcaption>Test Results</figcaption></figure><p>Primarily we learned that the comparison system we had designed was too clunky, and hard for users to use in order to compare products. We made some refinements to the design as you can see in the images below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E4GIs2j2EC1gGdZCzGrNdQ.jpeg" /><figcaption>Comparison system UI was streamlined, and the carbon coin was made the primary point of comparison</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4NlXJP7BZ6XnTeGdtQsnsw.jpeg" /><figcaption>The UI of the product page was streamed lined and simplified</figcaption></figure><p><strong>Refined Prototype</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fmarvelapp.com%2Fprototype%2F5fg3b4e%3Femb%3D1%26&amp;display_name=MarvelApp&amp;url=https%3A%2F%2Fmarvelapp.com%2Fprototype%2F5fg3b4e&amp;image=https%3A%2F%2Fmarvel-live.freetls.fastly.net%2Fserve%2F2021%2F11%2F7dae1a05ece84eeb8bece0a833a2e551.png%3Fquality%3D95%26fake%3D.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=marvelapp" width="452" height="925" frameborder="0" scrolling="no"><a href="https://medium.com/media/4646620b513e9dcd52790d8a1314d87a/href">https://medium.com/media/4646620b513e9dcd52790d8a1314d87a/href</a></iframe><p><strong>References</strong></p><p>Norman Nielsen Group (2021)- <em>Problem Statements in UX Discovery </em>(Web Source) Link- <a href="https://www.nngroup.com/articles/problem-statements/">https://www.nngroup.com/articles/problem-statements/</a></p><p>Norman Nielsen Group (2003)- <em>Paper Prototyping: Getting User Data Before You Code </em>(Web Source) Link- <a href="https://www.nngroup.com/articles/paper-prototyping/">https://www.nngroup.com/articles/paper-prototyping/</a></p><p>Norman Nielsen Group (2019)-Usability Testing 101(Web Source) Link- <a href="https://www.nngroup.com/articles/usability-testing-101/">https://www.nngroup.com/articles/usability-testing-101/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c75a8c3ec1e5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing A Carbon Tracking Shopping App: User Research]]></title>
            <link>https://medium.com/@sammc1999/designing-a-carbon-tracking-shopping-app-user-research-2308c3a8c7f2?source=rss-31e18cb6ad55------2</link>
            <guid isPermaLink="false">https://medium.com/p/2308c3a8c7f2</guid>
            <dc:creator><![CDATA[Sam]]></dc:creator>
            <pubDate>Mon, 08 Nov 2021 16:58:04 GMT</pubDate>
            <atom:updated>2021-11-08T16:58:04.835Z</atom:updated>
            <content:encoded><![CDATA[<p>After we had familiarized ourselves with various shopping applications and understand the frustrations that came with some of them we decided to conduct some more research and channel this into proto-personas and scenarios. It was decided we would make proto-personas as this is a method that allows the design team to empathize with the users later on in the process, as prescribed by the Nielsen Norman group. <a href="https://www.nngroup.com/articles/persona/">(Nielsen 2015)</a></p><p><strong>Task Analysis</strong></p><p>Initially we decided to conduct a “could-be” task analysis of what it would look like for users to purchase items whilst checking the carbon footprint of said items. We did this in order to better understand what this could potentially look like as a solution to the problem we had set out to solve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1WTXVSUjrWO6iXIb5Y4eGA.jpeg" /><figcaption>Task Flow Analysis — Purchasing an item whilst sorting by carbon footprint</figcaption></figure><p><strong>Personas</strong></p><p>The personas that were created were fictional personas, based on some assumptions that we made on behalf the potential user base that we were looking at. The reason for this was the time constraint we faced in our user research portion of this project. However they still served as a useful device for us to better understand the needs of our potential user base. (<a href="https://www.interaction-design.org/literature/article/personas-why-and-how-you-should-use-them">Dam, R., &amp; Siang, T. Personas, 2020</a>)</p><p>We developed two proto-personas in the end, they both included user goals, needs, motivations, pain-points, confidence with technology, and general points about their knowledge of the environmental impact of their carbon footprint. The personas embodied our assumptions and created empathy for the designer. We refined our individual personas into two final personas representing two different groups of people, our primary persona, and a secondary persona to contrast against the former.</p><p>Mary-Primary Persona- A mum with two young children, concerned about her shopping habits regarding the impact of her carbon footprint on her children’s future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7wYGkkm05o2eT7DWznICBg.png" /><figcaption>Mary — Primary Persona</figcaption></figure><p><strong>Scenarios</strong></p><p>In order to better understand where and how our potential product might be used, use case scenarios were written to better understand the context of where and when it might be used, giving us clarity on what would need to designed in order to meet the goals of our users.<a href="https://www.nngroup.com/articles/ux-stories/"> (Nielsen, 2017)</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6r-CMKmvoEsXq49SqxnsCw.jpeg" /></figure><p>The scenarios that were written gave us a good sense of the problem that of which we wanted to tackle and provided context along with requirements for our design.</p><p><strong>Reflections</strong></p><p>The task analysis that was undertaken could have been improved, each team member looked at different tasks to analyze, by looking at the same task, within the same app, we would have different data on the same task to look at, giving us a wider view on the same problem.</p><p><strong>References:</strong></p><p>Norman Nielsen Group (2015)- <em>Personas Make Users Memorable for Product Team Members </em>(Web Source) Link-<a href="https://www.nngroup.com/articles/persona/">https://www.nngroup.com/articles/persona/</a></p><p>The Interaction Design Foundation. <em>Personas — A Simple Introduction</em> (Web Source) Link: <a href="https://www.interaction-design.org/literature/article/personas-why-and-how-you-should-use-them">https://www.interaction-design.org/literature/article/personas-why-and-how-you-should-use-them</a></p><p>Nielsen Norman Group. (2017). UX Stories Communicate Designs (Web Source) Link: <a href="https://www.nngroup.com/articles/ux-stories/">https://www.nngroup.com/articles/ux-stories/</a></p><p><strong>Appendix</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pvojoRF61cPLNFwhr4O40Q.png" /><figcaption>Initial Proto Persona</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VTI_SSR-FapFcNorxku13w.png" /><figcaption>Initial Proto Persona</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eT7XtC5eYBmL0NKguIlfNw.jpeg" /><figcaption>Initial Scenario -Catelyn</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vcY87fi_sHy3cjctL2PARA.jpeg" /><figcaption>Initial Scenario -Tonya</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2308c3a8c7f2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing A Carbon Tracking Shopping App: Introduction]]></title>
            <link>https://medium.com/@sammc1999/designing-a-carbon-tracking-shopping-app-introduction-c69d1fc122cc?source=rss-31e18cb6ad55------2</link>
            <guid isPermaLink="false">https://medium.com/p/c69d1fc122cc</guid>
            <dc:creator><![CDATA[Sam]]></dc:creator>
            <pubDate>Mon, 08 Nov 2021 14:28:44 GMT</pubDate>
            <atom:updated>2021-11-08T17:49:49.986Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Introduction</strong></p><p>As part of the first module of my MSc. in User Experience Design: Fundamentals of UX Design, I was tasked with iteratively designing and evaluating a paper prototype for a shopping application that would allow users to see the carbon footprint associated with items they are considering purchasing and to monitor the carbon footprint of their shopping habits over time. The application could be a desktop or mobile application.</p><p>The project spanned just over five weeks, with the first week being used to evaluate similar shopping apps in terms of their usability and to understand how they measure up against the heuristic principles laid out by Jakob Nielsen and other user experience design principles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sF1Px60E89qguil3oQIoPA.jpeg" /><figcaption>Crazy 8’ s— A workshop actively undertaken to quickly sketch out potential solutions</figcaption></figure><p><strong>Our Process</strong></p><p>Throughout the duration of this project, a design thinking model was utilized in order to make more efficient use of the time allotted and rapidly testing ideas. Design thinking is a theoretical framework that places the needs of the user at the center of decision making and design choices. <a href="https://www.interaction-design.org/literature/article/what-is-design-thinking-and-why-is-it-so-popular">(IDEO,2020)</a> There are five phases to design thinking, primary amongst them is empathizing with the user in order to better understand their problems and needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YT-ZJSqNRLQjMv1_bbesmg.png" /></figure><p><strong>Heuristics Analysis</strong></p><p>In order to better understand the problems faced by users within shopping applications it was decided that a heuristics analysis would be undertaken to examine the ways in which these kinds of apps could be improved. A heuristics analysis is a test by which you measure the compliance of a system against the ten usability principles laid out by Jakob Nielsen.(Nielsen 1994)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XvhAlo-RVwq850MIDPmomg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BHM2qYQyW9AElJ_gHNdPvg.jpeg" /><figcaption>Heuristics Analysis of Depop App</figcaption></figure><p>One tenet upon which the system failed in the analysis that I undertook on the Depop App was that of error prevention. The system does not inform you that you are about the make a purchase, and as such when I was testing the checkout flow, I accidentally purchased an item. There was also no way to undo said purchase easily afterwards and so it failed under heuristic number nine, helping users recover from errors.</p><p><strong>References:</strong></p><p>IDEO . (2020). <em>What is Design Thinking and Why Is It So Popular?</em>. [Web Source] Link: <a href="https://www.interaction-design.org/literature/article/what-is-design-thinking-and-why-is-it-so-popular">https://www.interaction-design.org/literature/article/what-is-design-thinking-and-why-is-it-so-popular</a></p><p>Nielsen Norman Group. (1994, Updated 2020). <em>10 Usability Heuristics for User Interface Design</em>. [Web Source] Link: <a href="https://www.nngroup.com/articles/ten-usability-heuristics/">https://www.nngroup.com/articles/ten-usability-heuristics/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c69d1fc122cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>