<?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 Mai Thao Charlotte Nguyen on Medium]]></title>
        <description><![CDATA[Stories by Mai Thao Charlotte Nguyen on Medium]]></description>
        <link>https://medium.com/@mtng?source=rss-f7aff3658ba6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*JcMMn7WLQYIA3c-KFrHlkw.jpeg</url>
            <title>Stories by Mai Thao Charlotte Nguyen on Medium</title>
            <link>https://medium.com/@mtng?source=rss-f7aff3658ba6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 05:42:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mtng/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[Hashtags and emojis: when two communication trends communicate]]></title>
            <link>https://medium.com/@mtng/hashtags-and-emojis-when-two-communication-trends-communicate-15bc6b99c47d?source=rss-f7aff3658ba6------2</link>
            <guid isPermaLink="false">https://medium.com/p/15bc6b99c47d</guid>
            <category><![CDATA[information-architecture]]></category>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[hashtag]]></category>
            <category><![CDATA[emoji]]></category>
            <category><![CDATA[user-generated-content]]></category>
            <dc:creator><![CDATA[Mai Thao Charlotte Nguyen]]></dc:creator>
            <pubDate>Mon, 26 Nov 2018 10:34:18 GMT</pubDate>
            <atom:updated>2018-11-26T10:38:21.427Z</atom:updated>
            <content:encoded><![CDATA[<p>Hashtags emerged as a tool for collaborative organization of information in shared online environments, driven by user-generated content tagging (also called <a href="https://www.oreilly.com/library/view/information-architecture-for/0596000359/">social classification</a>). The information on the Web is more abundant than ever, and the language shifts and progress due to external factors, such as the influence the Web has on slang and common abbreviations. The result is the rise of the digital language, where people can express their thoughts and motivations through words, but also explicitly express their emotions through emojis.</p><p>In early 2000, smileys were integrated to the digital keyboard, and have continued to develop to more expressive and interactive emojis. Apple submitted the <a href="http://www.unicode.org/reports/tr51/#Introduction">first official proposal</a> to adopt emoji character to the Unicode Standard in 2009. <a href="https://www.wired.com/story/guide-emoji/">It was accepted and indexed because the increasing popularity was too hard to ignore</a>. A total of <a href="https://emojipedia.org/faq/">2823 emojis (Emoji 11.0)</a> have been enlisted to the <a href="https://unicode.org/emoji/charts/full-emoji-list.html">Unicode standard</a> since and represent things such as facial expressions, food, drinks, animals, activities and more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kVdJUk-ORT5HXgb2dTickQ.png" /><figcaption>Picture: Screenshot of emojis from <a href="https://getemoji.com/">GetEmoji</a>.</figcaption></figure><p><a href="https://socialmediaweek.org/blog/2016/11/future-of-emoji-fastest-growing-language/">Emojis are listed as one of the fastest growing languages in the world</a>. Controversies around diversity and cultural inappropriateness is one reason to how the language continues to expand at such high speed. With every release, more diversity of people and cultures are represented on the emoji keyboard. Popularized by the youths around the world, emojis adds to a humorous and engaging adjunct to the online experience and has become a nonverbal, expressive form of communicating. Supplementing text with emojis can help provide important information to clarify the message similar to how body language and hand gestures clarify speech. For instance, adding a laughing emoji or kissing emoji at the end of a sentence can disambiguate the emotional state of the message.</p><h4>Hashtags + emoji = ❤️</h4><p>Hashtags and emojis are both popular concepts on the Web, and in 2015, Instagram allowed users to hashtag emojis in their posts. During a one month period following launch, <a href="https://www.curalate.com/blog/the-top-100-most-popular-instagram-emojis/">Curalate</a> analyzed the total photo count of hashtagged emojis. The single red heart emoji (❤️) was tagged more than half a million times during the count period and has been tagged more than 25,4 million times today!</p><p>From a user’s standpoint, hashtags are easy to create and easy to discover content that is “trending,” or related to a topic of interest. After its entry to Twitter, other social media applications followed and implemented hashtags as it allowed users to generate and categorize content themselves. The system recognizes the tag after publication and matches the content with similar submissions from other users. On Twitter, hashtags allow users to participate in conversations about any topic and has attracted a lot of attention to social movements. #Metoo and #Blacklivesmatter are two among many examples of social media movements that have created public engagement and conversations. By combining hashtags with emojis, people can convey both intention and emotion explicitly rather than implicitly using only words. For instance, #😡 can explicitly replace #mood #angry.</p><p>Why should we even bother to use emoji hashtags in the digital environment? Firstly, hashtags help us determine what type of content a post contains in the digital environment. Secondly, emojis are fun to use, and nothing describes an image of a dog better than #<strong>🐶</strong>. Finally, and most importantly, user-generated tags can include misspellings, ambiguous terms, and acronyms. People create categories that are silly, narrow, or shouldn’t be a category at all. With emojis, no misspellings need to be accounted for, making emoji hashtags a useful tool for optimizing the search engine. The advantage is as simple as performing a search on a specific emoji always will retrieve the correct list of content, independent on the device. For instance, 🤩 is standard in Unicode so all devices can read the symbol. It is just not possible to misspell it as there only exists one of that emoji.</p><h4>Implications of hashtagging emojis</h4><p>When used correctly, hashtags allow for more accessible and fluid navigation between objects, authors and similar content. However, knowing a concept differs from understanding it. If users created hashtags for their intended purpose of categorization and discovery, they would have been able to navigate to what they’re looking for immediately. But as no guidelines have been created describing how to apply hashtags in a social environment correctly, users might have to browse through irrelevant and miscategorized content.</p><p>Enabling hashtags of emojis might add a new layer of complexity to the system because of the semantics of emojis. The emoji language is extremely diverse regarding facial expressions. Eight emojis is named “Smiling Face […]” in the Unicode Standard! Which smiling face do you chose to tag your content correctly? Studies have shown that people ascribe different meanings to emojis due to demographics like age, gender, and cultural differences. <a href="https://link.springer.com/chapter/10.1007/978-3-319-07863-2_38">Some researchers</a> have also concluded that design strongly affects the recognition of emotions. Per se, emoji use depends on complex factors like content and structure. <a href="https://dl.acm.org/citation.cfm?doid=3184558.3186344">Zhao et al.</a> conducted a study in 2018 concluding that people in different regions have a different diversity in emoji selections and different understandings of the emotions of the same emojis. For instance, “Face with Tears of Joy” (😂) is interpreted as having both positive and negative meanings. Additionally, some emojis tend to appear in the middle of sentences, and some more likely to appear at the end of the sentences.</p><p>Even with an international encoding standard, emojis are not universal. Like many conventions, emoji design comes with a certain amount of what <a href="https://skemman.is/bitstream/1946/6366/1/cognitive_design_a4.pdf">Ian Watson</a> calls “wiggle room.” As companies develop different technologies, they create own sets of emojis according to Unicode’s standards. For instance, “Face with Hand Over Mouth” emoji differs quite between Apples and Facebooks design. Apple’s interpretation of the emoji looks skeptical, while Facebook’s emoji looks more satisfied or flirty. The different design could add to miscategorized content when people hashtag emojis as the emoji could be interpreted differently by individuals on different devices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vC7SKqcP2BwQP4IaFjnKEw.png" /><figcaption>Two different design interpretations of “Face with Hand Over Mouth.” Apple’s emoji could be interpreted as more skeptical, while Facebook’s emoji could be interpreted as more satisfied or in a flirty mood.</figcaption></figure><h4>Emojis = #🤔#😕#🤯?</h4><p>Though the ambiguity of emoji semantics, one emoji interpretation contains less ambiguous information than its name. Like in the previous example with “Face with Hand Over Mouth,” the five words can be interpreted differently by people. However, applying a specific design convey more meaningful information.</p><p>Hashtags and emojis create precise groupings of content, in addition to engaging users to categorize content in a fun way, when used correctly. Advantages of incorporating social tagging in your platform are that it reflects people’s interests and emotions. With user-generated tagging, platform dynamically organizes the content and generates a fluid navigation experience for users.</p><h4>Should emoji hashtags be implemented in your system?</h4><p>User-generated tagging already pose implications to the notion of a database. Adding the emotional variable of emojis on top of that adds to the idea that it can include any category of interest. When designing the information architecture on a platform, it is essential that social classification fits the site and fulfills its purpose of making the content easy to navigate and discoverable, or whether it will become a cluster of unreachable content.</p><p>If the user group is homogeneous with the same understanding of how hashtags should be applied and the same semantic understanding of emojis, social tagging is advantageous to implement in the platform. The homogeneity would allow for a structured classification system. However, social media users consist of a highly heterogeneous group, and their intentions for generating tags varies from contributing to categorize content, to increase their own social media popularity. With the heterogeneous nature of websites and users, it might impose difficulties and misguided attempts to design an information architecture that fits all.</p><p>With the notion that social tagging and the new trend to tag emojis increase the complexity of content organizing, organizations need to carefully consider advantages and disadvantages, and find new ways to handle the structural implications of the information environment posed by user-generated tags.</p><p><em>This post is written as part of my assignments in the course User-centered Information Architecture.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15bc6b99c47d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nå kan organisasjoner opprette egne spleiser!]]></title>
            <link>https://medium.com/hei-spleis/n%C3%A5-kan-organisasjoner-opprette-egne-spleiser-aba949b8c5c0?source=rss-f7aff3658ba6------2</link>
            <guid isPermaLink="false">https://medium.com/p/aba949b8c5c0</guid>
            <category><![CDATA[crowdfunding]]></category>
            <category><![CDATA[organisasjoner]]></category>
            <category><![CDATA[folkefinansiering]]></category>
            <category><![CDATA[crowdfunding-platforms]]></category>
            <category><![CDATA[spleis]]></category>
            <dc:creator><![CDATA[Mai Thao Charlotte Nguyen]]></dc:creator>
            <pubDate>Thu, 02 Aug 2018 14:23:09 GMT</pubDate>
            <atom:updated>2018-08-02T14:23:09.770Z</atom:updated>
            <content:encoded><![CDATA[<p>Gjennom sommeren har vi vært et lite team med studenter hos Spleis som har jobbet med å gjøre det mulig for organisasjoner å opprette og administrere egne spleiser (innsamlinger). 🎉</p><p>Alle organisasjoner hos Spleis har fått et eget grensesnitt som kan brukes til å engasjere givere til å støtte organisasjonens prosjekter og hjertesaker. En beskrivelse av organisasjonens formål og visjon kan være med å motivere givere til å dele og spre budskapet videre! 🙌</p><p><strong>Profilsiden 👀<br></strong>Profilsiden gir en enkel oversikt over innsamlinger opprettet av organisasjonen, innsamlinger opprettet av andre ildsjeler til organisasjonen, samt avsluttede innsamlinger. Her kan du legge inn en beskrivelse av organisasjonen som vil være synlig for brukerne av Spleis. Dette vil gi et inntrykk av organisasjonen din samtidig som du kan vise fram innsamlingene.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2H8jTI2BJk8Dp1nf3h-vxg.png" /></figure><p><strong>Oversikt over innsamlinger til organisasjonen 📋<br></strong>Innsamlinger gir brukere med administratortilgang en mer detaljert oversikt over alle innsamlinger som er opprettet, som trenger godkjenning før utbetaling og utbetalingsstatus på avsluttede innsamlinger. Du kan også finne statistikk over hvor mye penger som er blitt samlet inn totalt hos Spleis, antall publiserte innsamlinger, samt hvor mange innbetalinger som er blitt gjort.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aZ5jBlYfWA-ZMrGEXzQ4rQ.png" /></figure><p><strong>Medlemmer og tilgangsstyring 👥<br></strong>Flere medlemmer av en organisasjon kan få mulighet til å opprette innsamlinger på vegne av organisasjonen, der en administrator kan invitere flere medlemmer ved e-post. Dette åpner for samarbeid blant medlemmer i organisasjonen, der flere kan dele på ansvaret. Alle som er medlem av organisasjonen har også mulighet til å endre pågående innsamlinger som er opprettet. Medlemmer kan navigere seg til organisasjonssiden fra Min side under “Mine organisasjoner”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IbtkiTSqJd9C14ok-awDsQ.png" /></figure><p><strong>Hvordan registrer jeg organisasjonen min på Spleis?<br></strong>En organisasjon blir opprettet når en initiativtaker oppretter en innsamling til organisasjonen. Organisasjonens kontaktperson blir satt som eier når han eller hun er blitt verifisert, og har dermed mulighet til å opprette nye spleiser som organisasjonen og legge til flere medlemmer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kuXWSmxiSm_JPrJdeY-uQA.png" /><figcaption>Organisasjoner som finnes på Spleis i dag!</figcaption></figure><p><strong>Hvordan oppretter jeg en innsamling som en organisasjon?<br></strong>Er du medlem av en organisasjon kan du velge å starte en spleis som deg selv eller som organisasjonen. Superenkelt! 👏</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yvraiPXy-mEt2YPn4abjSA.png" /></figure><p><strong>Så hva venter du på? Start en spleis til din organisasjon — som din organisasjon! </strong>😁</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aba949b8c5c0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hei-spleis/n%C3%A5-kan-organisasjoner-opprette-egne-spleiser-aba949b8c5c0">Nå kan organisasjoner opprette egne spleiser!</a> was originally published in <a href="https://medium.com/hei-spleis">Hei Spleis!</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DroneHub— the design process of the digital platform]]></title>
            <link>https://medium.com/@mtng/a-drone-platform-the-design-process-5e27dc614bd0?source=rss-f7aff3658ba6------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e27dc614bd0</guid>
            <dc:creator><![CDATA[Mai Thao Charlotte Nguyen]]></dc:creator>
            <pubDate>Thu, 07 Jun 2018 14:03:21 GMT</pubDate>
            <atom:updated>2019-01-11T09:31:30.268Z</atom:updated>
            <content:encoded><![CDATA[<p><em>By Sabina Niewiadomska, Lam Kim Khoi, Giovanni Pignoni and Mai Thao Nguyen.</em></p><p>Drones are increasingly employed for many innovative applications mainly to solve humanitarian challenges and challenges with urban transportation. E.g. the company ‘Zipline’ provides lifesaving deliveries such as medicines and vaccines using drones. An ambulance drone has been created by TU Delft University which is designed to speed up emergency response.</p><p>In this project, you are expected to follow a user-centred design process to create a platform (in other words a service) that brings together drone enthusiasts, researchers and end-users of the innovations using drones.</p><h3>Week 1</h3><p><strong>1. Learning about the drone community.</strong></p><p>To get an understanding about the drone community, the team saw the need for gathering insights about the domain by searching for information from drone forums, websites, tutorials and research, in addition to joining a few social media groups on Facebook. All the different platforms had different goals, and the team looked after what value was offered on these. The list of web pages is listed below.</p><p>Forums/Websites:<br><a href="https://dronelife.com/">https://dronelife.com/</a><br><a href="http://www.nodecampaign.org/">http://www.nodecampaign.org/</a><br><a href="https://www.reddit.com/r/drones/">https://www.reddit.com/r/drones/</a><br><a href="https://www.dronethusiast.com/">https://www.dronethusiast.com/</a><br><a href="https://www.fai.org/world-cups/drone-racing">https://www.fai.org/world-cups/drone-racing</a><br><a href="http://www.dummies.com/consumer-electronics/drones/how-to-use-social-media-to-meet-drone-enthusiasts/">http://www.dummies.com/consumer-electronics/drones/how-to-use-social-media-to-meet-drone-enthusiasts/</a><br><a href="https://phantompilots.com/">https://phantompilots.com</a><br><a href="https://www.dronevibes.com/">https://www.dronevibes.com/</a></p><p>Tutorials:<br><a href="https://www.instructables.com/howto/drones/">https://www.instructables.com/howto/drones/</a><br><a href="https://www.youtube.com/results?search_query=how+to+drones">https://www.youtube.com/results?search_query=how+to+drones</a></p><p>Facebook groups:<br><a href="https://www.facebook.com/AerialSociety/">https://www.facebook.com/AerialSociety/</a><br><a href="https://www.facebook.com/groups/quadcopters">https://www.facebook.com/groups/quadcopters</a><br><a href="https://www.facebook.com/NODECampaign/">https://www.facebook.com/NODECampaign/</a></p><p>Research:<br><a href="https://www.researchgate.net/search.Search.html?type=publication&amp;query=drones">https://www.researchgate.net/search.Search.html?type=publication&amp;query=drones</a></p><p>We continued by conducting a competitive analysis by listing features, strengths and weaknesses to the different websites. We identified DroneVibes as our biggest competitor, as it is described as “the internet’s number one growing community for drone enthusiasts”. We listed up all the features on the website, and design strengths and weaknesses. In a website that has a lot of features, aiming to account for many different user needs, we found it difficult to distinguish the user base clearly. It is an online community for drone enthusiasts, but it is difficult to explicitly state the goal of the website. Besides, with the limited time on the project, creating such a complex architecture would not be possible. We decided to keep the website for inspiration later in the project.</p><p>In the project description, scoping the terms “drone enthusiast”, “drone researcher” and “end-user” was difficult as we did not know what characteristics that could define them. To gather more insights, we decided it would be necessary to ask users of the different platforms what type of “users they are”. Reddit has a subreddit about drones, with over 39.000 followers. We decided to create an open question to the followers, with the aim of scoping the terms to recruit the appropriate participants for the following activities. Before publishing, we asked the course leader to look through, and quality check the text and questions in order to collect valuable information.</p><blockquote>Hello there, we are a group of Interaction Design Students from the Norwegian University of Science and Technology (NTNU).</blockquote><blockquote>As part of a research project, we started the development of a platform which aims to bring together drone enthusiasts, researchers, investors, and end-users to facilitate innovation.</blockquote><blockquote>We are turning to the community here as we would like your opinion to understand what could be a missing link in the development of successful collaborations.</blockquote><blockquote>With collaboration we include everything from finding funds for a project, contacting experts, accessing technical resources to sharing your own expertise.</blockquote><blockquote>Your inputs are greatly appreciated.</blockquote><p>Two of the group members created an account in order to try publishing the post. However, one week after, we had to give up trying to publish, as neither was approved by the system as “active members”. We did, however, manage to successfully publish the post on different drone forums but did not receive any meaningful responses. It was therefore decided to focus on establishing contacts with people that are currently working with drones, or use and/or builds hobby drones.</p><p><strong>2. Creating user profiles.</strong></p><p>With the stage of learning more about the drone community, we tried to categorise the users of the different platforms as primary, secondary and tertiary users. As we did not have a specific set of characteristics to create the “ideal user”, we decided it would still be beneficial to try and scope down the terms, and instead fill in the characteristics we did not know about yet after the user requirement activities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3u3QNvAOMfnsgJI10q7GCg.png" /><figcaption>Initial user profiles.</figcaption></figure><p><strong>3. Establishing communication links with drone enthusiasts and researchers.</strong></p><p>With limited resources and knowledge about drone enthusiasts, we used the user profiles to set requirements for recruitment of participants for interviews:</p><ul><li>Within the user age of 18–55</li><li>Have built or builds drones</li><li>Have done research with drones or are currently doing research with drones</li><li>Are a part of a drone community or wants to be part of drone communities</li></ul><p>People that were asked to participate did not have to fulfil all the requirements, as it was used by the group as a guideline for who to make contact with. We contacted administrators on different social media groups and journalists. Additionally, we tried asking people on NTNU Gjøvik campus, however, as all the other group had been reaching out to students before us, we did not find it expedient to ask the same people. It was important for the group to establish contact with people in the drone community outside student campus, so we composed invitation emails and sent it to students and lecturers at NTNU and MIT, and other professionals working in companies as NRK and</p><p>LocalHawl (Kongsberg Defence &amp; Aerospace). The email was created in both Norwegian and English.</p><h3>Week 2</h3><p><strong>4. Preparing for the interviews.</strong></p><p>Eleven people in total replied to our interview invitation, but only seven said yes to participate. We created a timetable to keep track of the scheduled time and date and decided to set the deadline to finish all interviews by the end of week 3. A consent form and a general interview guide were developed, to assure that the key questions were asked to all participants. With all participants that had agreed to participate, we researched their background in order to make the questions relevant to each participant.</p><h3>Week 3</h3><p><strong>5. Conducting the interviews.</strong></p><p>Throughout the week, we conducted interviews online, over the phone and face to face. All the interviewees found the topic interesting, and with the broad range of characteristics and experience, different needs and problems related to drone activities were revealed. Not all team members were able to participate in all the interviews, but we were always at least two during the interviews. The advantage of conducting interviews between 25–30 minutes was that more people could participate, however, it is also a disadvantage as information might have been lost due to the limited time. Additionally, we realised the barrier of language could bias the data, as some participants did not answer directly to the asked question. Nevertheless, conducting interviews was both informative for the group to enhance the knowledge of the domain, and valuable as it revealed what the “ideal” drone community would be. After finishing with the last interview, the group gathered to summarise the findings and suggest solutions for each case.</p><p>We had an interview with the leader of NRK Luftfoto. He was very enthusiastic about our project, and we were invited to visit their workplace. We took the opportunity to ask if it would be possible to conduct a usability testing of the final prototype with them. With a busy schedule the following month, we were able to schedule a visit Monday 6th June. Our goal was to have a working interactive prototype that could be tested by then.</p><p><strong>6. Analyzing the collected data with affinity diagram.</strong></p><p>We decided to proceed with analysing the data from the interviews with affinity diagram, to structure the data. Each of us agreed on a set of rules to follow during the exercise to fully benefit from using the method. It was reminded by several of the group members to keep an open mind to be creative throughout the whole activity, and that no idea or hypothesis would be criticised. Post-its were distributed to all, and we set a time cap on 20 minutes to create the cards. To avoid biasing each other, the activity was done individually and quietly. Key points, quotes, observations, etc. were written down, and a total of 46 cards were generated. When everyone had finished, the cards were shuffled and posted on the wall. We read the text out loud, and if anyone had a similar card, they were placed together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*we_SXork5P69s3GeSTHv_w.jpeg" /><figcaption>Sorting the cards.</figcaption></figure><p>After the groupings were finished, a discussion of each group was necessary in order to label them. We sat a time cap on 10 minutes to label all the groups with a title or description. We then continued to walk through the diagram together. Some cards were placed in other piles as they were duplicates or didn’t fit with any of the other groups. Some of the biggest piles were subdivided to make the diagram more meaningful. The final diagram contained nine groups: Jobs, Sharing resources, Interests/goals, Regulations, Reliable information/research, Profile, General information, Shop, and Education.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YkH77y4NDeTAyOrE7zd0Cg.jpeg" /><figcaption>Finished affinity diagram with labeled groups.</figcaption></figure><p>When the activity was finished, we tried to figure out what type of website this would be. The complexity of the website would be impossible if all the groups were to be applied in the site. It would become a copy of the competitor, DroneVibes, with no clear user group or goal in the website. By prioritising the needs based on the data collection, the team focussed the project on three most common user needs to guide the team towards a viable project. The groupings that were prioritized was: sharing resources, reliable information/research, and profile.</p><p><strong>7. Scoping and defining the concept.</strong></p><p>Defining the scope of a project is necessary to establish objectives. By defining the project’s objective, allocating tasks would be a more straightforward task. Based on the three groups we had prioritised from the affinity diagram, each team member tried to make sense of the three groups and define the concept for the website. This was done for all of us to communicate our ideas and hypothesis without being biased from each other. Finally, we discussed and defined the concept together:</p><blockquote>A digital platform where drone enthusiasts and researchers can share their research, resources and knowledge. It is a platform which focuses on social and professional networking. It is a place where they can learn from each other, contact each other and find inspiration.</blockquote><p><strong>8. Redefining the user profiles and creating personas and scenarios.</strong></p><p>After the interviews, we had a more precise definition of the terms “drone enthusiast”, “drone researcher” and “end user”. By clearly defining the terms, we needed to update and redefine the initial user profiles in order to create personas. The term «drone enthusiast» was defined by the group as any person that has an interest in learning about drones, keeping up to date about the technology, building drones themselves, wants to be part of a drone community with an engagement and interest in sharing their experience and knowledge. The term «drone researcher» includes users working hands-on with drones technology both academically and professionally in businesses on a daily basis. The drone researchers are likely to also fit with the term «enthusiast». The term «end-users» involves every user who, professionally or not, uses drones in his activities (without being necessarily involved in the technology).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XfZ6o8kDb_XCsXuGbKKQ6Q.png" /><figcaption>The redefined user profiles.</figcaption></figure><p>One persona and scenario was created to fit the user profile, representing specific users of the platform. We also created a scenario for each persona, making sure that the content implemented in the design phase would meet the persona’s needs and satisfy their goals of using the platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*K8RTaw6MDNVD3Pz_Ijv31g.png" /><figcaption>Persona and scenario — drone enthusiast.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*lJYgri6fLibHXOegjOJrdA.png" /><figcaption>Persona and scenario — drone researcher.</figcaption></figure><h3>Week 4</h3><p><strong>9. Preparing and planning for online card sorting.</strong></p><p>Based on the cards from the affinity diagram, the team assembled to plan for the online card sorting. With a deadline only a few weeks away, we needed to finish the activity by the end of week 4, to have time to prototype and test with users. Additionally, with the scheduled meeting with NRK Luftfoto, we needed to have a prototype to test with. We agreed on conducting an open sort as it is beneficial during the early stages of the design process. It would be a computerised sort due to time limitations, as we needed to gather data from many users. We would also save time preparing the data for analysis. Finally, it would be executed remotely, enabling the team to collect data from the participants without being limited geographically.</p><p>We started with brainstorming content that could be a part of the information architecture. Everything was written on a whiteboard before the group discussed the difference between a content (red underline), and an action (green underline). The total time of 1,5 hours was spent on this activity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cytb2MgJAmoGLjuUX8Ccbw.jpeg" /><figcaption>Brainstorming of the content for the drone platform.</figcaption></figure><p>We continued the process of testing a variety of free computerised card sort programs. The disadvantage with the free programs was that some were limited to only 20 cards, and some could only be distributed to a limited number of users. After trying and comparing different programs, ProvenByUsers was picked to execute the card sorting research. This online tool provided essential functions for participants and data analysis for researchers, such as similarity matrix and dendrograms.</p><p>The total number of cards was 92 when all the cards were plotted in the programme. Baxter, Courage and Caine (2015) have found it best to limit the number of objects to be sorted to 90 cards or less. Duplicates were removed, and the final number of cards to be sorted was 87. With a large number of cards, the longer it will take for participants to finish, which could discourage the participants. We found it beneficial to conduct a pilot test before sending the link to participants, to reveal possible errors in the system.</p><p>A description of the objective and an instruction manual was created for the programme, to help the participants if they were stuck on a task, or forgot their options.</p><blockquote><strong>Description</strong><br>Thank you for taking the time to complete our card sorting exercise.</blockquote><blockquote>This study aims to evaluate the information architecture of the website we are developing and will help us understand how to organise the content to facilitate the end-users to find what they are looking for.</blockquote><blockquote>The digital platform that we are designing aims to enable drone-related researchers and enthusiasts to share experience, projects and resources.</blockquote><blockquote>The secondary aim of the platform is to serve as a CV/portfolio, showcasing personal expertise and possibly find relevant job/collaboration opportunities in this specific field of interest.</blockquote><blockquote><strong>Instructions</strong></blockquote><blockquote>Each card has a piece of content in our proposed website. After you have reviewed all the cards, please begin sorting those you feel can belong together into groups. There are no right or wrong answers. There can be multiple ways to group the contents; please provide us with the groupings that you feel make the most sense.</blockquote><blockquote>While sorting, you can:</blockquote><blockquote>- Drag cards from the left to the right side of the page to create a new group. Groups can be renamed by clicking on the name.</blockquote><blockquote>- Drag the items from the left into the best-suited groups on the right.</blockquote><blockquote>- We encourage you to duplicate content that you feel belong to more than one group (double-click on the card you want to copy and move it to the groups you think it belongs to).</blockquote><blockquote>- If you feel a card doesn’t belong in any of the groups (or you do not understand its meaning), you are free to leave it unsorted.</blockquote><blockquote>- When you have completed your sort, make sure you have named all the groups. You can use a single word, phrase or a sentence; you can also comment on each group if you want to add any information.</blockquote><blockquote>- We expect you to end up with between 5–7 groups of cards. It is OK if you end up with more or less, but feel free to use these numbers as rough guidelines.</blockquote><blockquote>-When you are finished, please click the “I’m done” button on the top of the window to save your answer.</blockquote><p>One Interaction Design student was asked to participate in the pilot testing. He was asked to “think-aloud” while sorting and finished after 15 minutes. All cards were sorted, in addition to a few being duplicated. He did not find it difficult to sort the cards. However, the instruction text was a bit confusing. Before sending the link to participants in the user population, the texts were refined.</p><p><strong>10. Analyzing the results from card sorting.</strong></p><p>By the end of week 7, a total of 13 participants had finished the activity. The results were plotted with a use of R programming language to make a dendrogram, to evaluate and make sense of the groupings. The category names varied substantially between participants, but a structure did emerge from the data. The structure reflected what we already had expected, and with a clearer understanding of how the content should be structured, we started sketching out wireframes for the website.</p><p><strong>11. Sketching, creating wireframes and storyboards.</strong></p><p>With a clearer view of the information architecture, we could start sketching wireframes that could help the users to find information or accomplish tasks with ease. Creating sketched before prototyping with digital tools was good for everyone in the team to visualise ideas, and share thoughts. After a few rounds of iterating on the sketches, it was decided to illustrate how the users would reach a goal through storyboarding. The scenarios created earlier in the process was applied to the storyboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DdXBgVpJqbzcDSdSVjX8Eg.png" /><figcaption>Mock-ups and storyboarding.</figcaption></figure><p>By using storyboarding, we were able to visualise how the system flow would be, for the user to reach their goal on the site. To ensure that everyone in the team understood what the requirements of the web site means, a couple of requirements activities were conducted.</p><p><strong>12. Clarifying the system requirements.</strong></p><p>We decided to choose some methods to clarify the system requirements. Not only would it be beneficial for everyone in the team to clearly understand the system requirements, but also a good way to fully structure the information architecture of the website. We decided to start by creating a use case diagram. It is focused on the user goals of the system, specifically the user-system interaction. It was therefore beneficial to develop a use case, to see the system in the user’s perspective, and all the possible actions on the site. The use case diagram was printed and discussed again by the team. Changes were directly made in the paper format, before updating and finalising it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p6XtS-qvLOShylHmZG5NVQ.png" /><figcaption>Use case diagram.</figcaption></figure><p>We followed up with creating a class diagram. The difference between use case diagrams is that a class diagram describes the system’s structure. This was beneficial for the group to focus on the attributes of classes that should be represented through the design, as well as supporting the database creation. Having the class diagram made it easier for us during the prototyping phase, as we could quickly make sure that every page in the prototype had the correct attributes.</p><p>In addition to the storyboarding, we decided to do a hierarchical task analysis to get an understanding of what the users are trying to achieve, why, and how. It does not scale well with real tasks as they are complex in nature, however, it gave us an image of the system’s complexity and what actions to design and account for.</p><p>Finally, to have a clear sense of the service, we decided to create a business model that could later be pitched to interested parties after the project end.</p><p><strong>13. Prototyping in Figma.</strong></p><p>By the end of week 4, we needed to prototype the web site with more details, in order to avoid delays in the project. As we already had used Figma as prototyping tool in the scale-project, we found it easy to continue working with that tool. We started by sketching some wireframes before adding contents to it. Before prototyping the interactions, we wanted to conduct a cognitive walkthrough to ensure that all interactive buttons would do what the user expected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GC0TPCFUK0b9ehZXg8Itow.png" /><figcaption>Sketching of wireframes in Figma.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-nSdY7zMWr7JNOVNvziX-Q.png" /><figcaption>Early prototype in Figma.</figcaption></figure><h3>Week 5</h3><p><strong>14. Cognitive walkthrough with an interface expert.</strong></p><p>To evaluate the quality of the first prototype, cognitive walkthrough was chosen, to have an interface expert review the site. It is recommended to have more than one expert to review the prototype, however, with the limited time on the project, it was only possible to conduct the method with one expert.</p><p>The digital prototype was printed out in A3-paper format to ensure readability. We divided roles, where one was the facilitator and the two note takers. A plan was created, to ask questions to the participant while he was interacting with the prototype. The session took place in NTNU Gjøvik library, and the total time of the activity was 45 minutes. The objective of the activity, the concept, the users and the scenarios were presented before he started interacting with the prototype.</p><p>After finishing the activity, we thanked the participant, and a debrief session with everyone in the team followed. The results of the cognitive walkthrough were that visible flaws in the interface, such as confusing words and inconsistent/misleading layouts were discovered. We realised that some of the interactions needed to be changed, as it did not correlate with what he had expected. Wordings and layout needed to be changed to ensure that the system was speaking the user’s language. We also needed to decide whether the heart-icon for bookmarks needed to be changed, as the expert mentioned it could be confused as with a “like”-function. The tested prototype did also include badges but needed to be removed as the expert said it could lead to a lot of content that lacked quality. The cognitive walkthrough allowed the team to understand and prototype interactions in the user interface that would make sense for the users of the website.</p><p><strong>15. Redesigning and prototyping the interface in Adobe XD.</strong></p><p>Before conducting another round of testing, we needed to improve the interface based on the results of the cognitive walkthrough. We would have continued to use Figma as the design tool as it supports real-time collaboration. However, when presenting the wireframes in Figma to interact with, they were presented in a scaled format and would not allow scrolling. This could have biased the results during testing with users. Therefore, we decided to prototype in Adobe XD as this problem did not occur. In order to get good feedback on the prototype, we needed to provide the content with text and images. One team member had the responsibility to sketch and prototype in Adobe, while the others prepared and created content for the website, the heuristic evaluation worksheet and consent form.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hRNTcpbnOGVz1dS2yjmcDw.png" /><figcaption>Prototyping in Adobe XD. The arrows indicate the possible interactions of the interface.</figcaption></figure><p><strong>16. Heuristic evaluation.</strong></p><p>To create a website with good user experience, we wanted to conduct a heuristic evaluation. The chosen heuristics to be compared was Nielsen’s ten heuristics for user face design. A description of each heuristic was provided with the worksheet, in addition to an example. Eight UX experts were asked to participate, six were recruited from the Master’s programme in Interaction Design from NTNU Gjøvik, and two from the Master’s programme in Informatics: Design, use and interaction from The University in Oslo. To avoid delays in the schedule, the experts were asked to return the evaluation worksheet within two days. At this time, many students were occupied with final exams. However, six UX expert participated the evaluation within the deadline.</p><p>The team was assembled to analyse the worksheets. The average rating on each heuristic was calculated from all the tasks. We then continued by reading and comparing the feedback on each heuristic. This resulted in a list of elements that needed to be added, fixed or removed to adhere to all the heuristics. The total rating of the website was above average, almost meeting the standard. We decided to create more content as About, Community rules and FAQ to meet the “Help and Documentation” heuristic.</p><p><strong>17. Creating a high-fidelity prototype.</strong></p><p>At the final stage of the design process, we wanted to conduct a usability testing on a high fidelity prototype. Adobe XD and Figma had been useful tools to create clickable mockups of the interface. However, they did not scale well as more pages were introduced on the website, as the structure of links got overly complicated in Adobe XD. Additionally, a limitation of using Adobe XD or Figma was that it does not support responsive elements. It was therefore decided to use a production-ready framework tool, Foundation.</p><p>A downside to prototype in this way was that it requires prior knowledge of HTML, CSS and JavaScript, which meant that the group needed to divide tasks as we could not collaborate real-time. Two of the group members with prior knowledge to HTML, CSS and JavaScript was responsible to prototype the website, while the other two planned and prepared for the visit in Oslo, developing a usability test plan and consent form.</p><p>The final day of week 5, the prototype was ready. Everyone in the team conducted the usability test tasks to test the interaction, and make sure that everything in the system was clickable and consistent.</p><h3><strong>Week 6</strong></h3><p><strong>18. Visit NRK Luftfoto and testing the prototype with a drone expert.</strong></p><p>Monday 4th June, the group went on a visit to NRK Luftfoto in Oslo. We were invited to learn more about how they work, about the systems they use for reporting and monitoring the drones, maintenance, and some of their projects. Additionally, we were able to conduct a usability test of the prototype with a drone expert. This was an excellent opportunity to test whether the system is usable by a user from the intended user population.</p><p>The usability test session lasted for about half an hour, and the user completed all but one task with a high success rate the first time. Each task was performed under one minute. The source of error on one of the tasks was due to the used terminology. The main flaws of the interface design were the user profile page. His thought was that the website would be useful as a portfolio, making it easier for companies or other clients to hire people with the right certification. It would be essential to include the pilot registration number, operator category and drone models they had experience with, as it would be valuable information for people to find the right person for a job position or a research project.</p><p>After finishing the session, the leader of the department and the drone pilot told us they had a good impression of the concept, and a good solution to connect drone enthusiasts and researchers. We were asked who would be taking over the project after the course end, and he recommended the group to contact UAS Norway. Before leaving the location, we invited to test their drone flying simulator. Flying a drone was a lot harder than expected, which was the reason to why they trained pilots over a six months period. This was because the equipment is expensive, and for training the pilots to think safety before anything else.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sLeiIOc9A9oWxCTS2NZPgQ.jpeg" /><figcaption>Testing out the drone flying simulator</figcaption></figure><p>By the end of that day, the developers addressed the interface flaws that had been discovered during the usability test. This would create a better user experience of the website. Additionally, we wanted to conduct a final usability testing with a drone enthusiast. We made a few changes to the usability test plan and recruited one participant.</p><p><strong>19. Usability testing with drone enthusiast.</strong></p><p>As improvements had been made to the prototype, we wanted to evaluate whether the prototype’s features were in conjunction with the user’s mental model of a website. It was important this time that the facilitator didn’t specifically state, e.g. “bookmark an article” or “follow the author”. To understand whether the participant could recognise the “follow”-feature, the facilitators phrased the question “if you read an article and felt that you liked its author, what would you do”. The participant successfully clicked on the follow-button as an answer.</p><p>There were some points that the participant was unsure of. For example, when clicking on “Bookmark”, he noticed that the icon changed from outline to full-fill black icon, but he was not sure if that article was actually saved in the bookmark list. Another instance, when looking at the “Job Offers” in the personal page, the participant confused “Not sure if I offer these jobs or they are the ones I bookmarked”.</p><p>His impression of the website was that it fit his mental model, as its composition and contents appeared in conjunction with what he expected. Some elements caused confusion as the bookmark, as it did not provide feedback that content was saved. Additionally, other design features needed to be changed based on the user’s feedback.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1009/1*R4-XPJk_dMaTZW7xFWFQ_w.png" /><figcaption>The final prototype.</figcaption></figure><p><strong>20. Closing the project.</strong></p><p>After a debrief of the usability testing, the developers improved the prototype based on the user’s feedback. With only three days left before the project delivery, the team closed the prototyping phase and focused on reflecting and finalising the projects.</p><p><strong>Links and code</strong></p><p>The prototype is available on a web site:<br> <a href="http://www.giovannipignoni.com/drones/">http://www.giovannipignoni.com/drones/</a><br> <br>The code is available on GitHub: <br> <a href="https://github.com/aniWeyn/dronesHighPrototype">https://github.com/aniWeyn/dronesHighPrototype</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e27dc614bd0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Redesign of a bathroom scale — the design process]]></title>
            <link>https://medium.com/@mtng/redesign-of-a-bathroom-scale-the-design-process-a31c6bfe75a3?source=rss-f7aff3658ba6------2</link>
            <guid isPermaLink="false">https://medium.com/p/a31c6bfe75a3</guid>
            <dc:creator><![CDATA[Mai Thao Charlotte Nguyen]]></dc:creator>
            <pubDate>Thu, 07 Jun 2018 14:01:07 GMT</pubDate>
            <atom:updated>2019-01-11T09:31:01.924Z</atom:updated>
            <content:encoded><![CDATA[<p><em>By Sabina Niewiadomska, Lam Kim Khoi, Giovanni Pignoni and Mai Thao Nguyen.</em></p><p>The problem description was to redesign a bathroom scale. The bathroom scale is almost a part of the interior in people’s home and is used to keep track of important health metrics. The design is quite similar, but the functionality varies. How to measure the data, and how to present it to the users in an intuitive and simple way is a challenge. The objective has been to design for greater user experience, following some constraints imposed on the redesign:</p><ol><li>It should be a stand-alone instrument.</li><li>It cannot be mediated by the internet/ubiquitous computing.</li><li>It cannot interact with other gadgets (or instruments).</li><li>Data input should only be made by humans, not by instruments in the vicinity.</li><li>Everyone in the physical proximity of the instrument should be able to input data into it, but not simultaneously.</li><li>The size should not be significantly different than a standard scale.</li></ol><h3>Week 1</h3><p>1. Analysis of competitors.</p><p>To gather insights on the variety of models of bathroom scales on the market, a selection of products was analysed. We did this in order to understand our competitors, in addition to getting an overview of the most common functionalities offered, and potential improvements for making a scale that is more valuable and desirable for the users. The products were chosen based on ratings and popularity on Amazon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/954/1*UjmLqet977PxWIQgOc3_tw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3NT9to5YKv34wuBTt9PzFw.png" /></figure><p><strong>2. Choosing the methods for requirements gathering.</strong></p><p>To get an understanding of who the users are and the context of use, different methods were conducted to identify the user goals of the product. Firstly, we defined the target user group and did an online survey to gather initial information. After that, more various tools were employed to explore users’ thoughts, concerns and needs. These methods ensured the user-centred design concept for this project.</p><h3>Week 2</h3><p><strong>3. Identifying the user profiles.</strong></p><p>Based on the design brief, we created the initial user profile. It was also the crucial step in the design process that helped the team to explore the target user group. After collecting more data from research activities, the user profile will be amended.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/898/1*CNU9O9yDr4P6-BTlA9AF8w.png" /><figcaption>Initial user profiles for the scale.</figcaption></figure><p><strong>4. Online survey</strong></p><p>A scale can be used for different purposes, and the user group could include everyone, from newborns to elderly. It means that there is going to be more than just one user profile for a scale. In order to make the scope manageable, the team decided to collect data within the user group between the age of 18–64. We chose 18 as the minimum age due to parental consent to participate. The questionnaire aimed to map the use of bathroom scales, what health metrics people keep track of and to find what user group we would design the scale for. The survey was shared on social media, and we asked students on NTNU Gjøvik Campus to participate.</p><p>Twenty-eight people participated in the survey between the age of 22–39 years old. The majority of the participants did not follow a diet, and 32% of the participants did not own or use a bathroom scale, be it a private or public scale. Data shows however that participants that own and/or use a scale frequently use it for keeping track of their progress to monitor the effects of training and diet.</p><p><strong>5. Brainstorming and paper-prototyping</strong></p><p>After conducting the survey, we did a review of the results and analysed it to define a minimum viable product (MVP). The advantage of establishing an MVP was that we were able to identify what the absolute minimum of the product would be acceptable for our target persona to accomplish a goal. We then determined which features that should be implemented for it to create a better user experience of our product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7f1dDbJj72khfj5dHpffAQ.jpeg" /><figcaption>Comparison between minimum viable and premium features for the scale.</figcaption></figure><p>During the brainstorming session, the team discussed concepts, possible solutions, usability, and essential functionalities. There were some user experience and features that need to take into account:</p><ul><li>Achieving goals with ease</li><li>Promote good/healthy behavior</li><li>Personalized avatar</li><li>Electric trackpads</li><li>Detachable screen</li><li>Simple and understandable output data</li><li>Touch screen vs. buttons</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cQIJyeCiGqrRRVrVPVIiCg.jpeg" /><figcaption>From the brainstorming session.</figcaption></figure><p>The team sketched out some content for the screens on paper. Sketching on paper made it easier for the team to iterate on the design. A Raspberry Pi 3.5 Inch Touch Display was ordered for the screen as the screen for the scale as well as a set of 4x50kg sensors. To avoid limiting the creative process to designing for touch with fingers, the team discussed other possible ways to interact with the scale, as toe-touch, touch pads, buttons as well as the weight/balance/movement of the user on the scale itself. Buttons were sketched, and cardboard was cut and used as the scale.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KV0-6VYCf32GeP9D-ixY5g.jpeg" /><figcaption>Paper prototype of the scale’s interface.</figcaption></figure><p><strong>6. Testing the paper-prototype.</strong></p><p>Before deciding on the type of interaction for the scale, the team prepared and conducted a pilot testing of the design with a user that fit the user profile.</p><p>This testing session helped the team to understand the flow, whether or not buttons were preferable, intuitive, and if its functions were performed as what the user expected it to do.</p><p>After the test, the team decided to ordered trackpads and a screen with the same size as the prototyped screen. As online orders took time and the project had a time constraint, we proceeded with the purchase though we knew there should be more tests conducted before making a final decision on the screen size. However, the team realised there was the need for more user input on what to include in the scale, another research activity was planned — Focus group.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/702/1*XBs6qr9vcQ08KsPkwunifQ.png" /><figcaption>From the early testing of the paper-prototype with a user.</figcaption></figure><h3>Week 3</h3><p><strong>7. Conducting a focus group.</strong></p><p>The team decided to conduct a focus group as we wished to have an insight of how people using a scale, what could make it a better instrument, and explored which paper prototype version responded correctly to users’ need.</p><p>We generated a focus group plan which consisted date, location, duration, possible participants, and most importantly — discussion topics. The plan also included necessary preparation of tools and instruments, such as consent form, sticky notes, voice recorders, camera, laptop for displayed questions, etc. On the central part of the activity, we divided into six sections, which were Warm up, Introduction, Key Topic 1, Key Topic 2, Testing of the paper prototype, and Wrap up.</p><p>We planned to conduct the focus group with around eight people and tried to look for participants around Gjøvik area. The location was decided to be in one of the group members student home to make the environment feel more comfortable. There were nine people responded that they could join our research. However, when it closed to the date, three people informed us that they were unable to take part in, and we had six participants at the end. There were two males and four females. They were NTNU students whose ages range from (20 to 28) with different backgrounds — two Masters of Applied Computer Science, two Bachelor of Civil engineering, one Bachelor of Occupational Therapy, and one Bachelor of Web Development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-MsM2aRxZ5GsYmAW" /><figcaption>Preparing and setting up for the focus group session.</figcaption></figure><p>Drinks and snacks were provided to participants, and the team thanked for their attendance. We distributed papers for them to create name tags and signed consent forms. We also broke the ice by asking where they are from and got everyone to know each other for a more comfortable discussion later. After making sure everyone was ready, we moved on to the introduction part.</p><p>We introduced our team members and each person’s role: Mai was the moderator, she spoke in Norwegian and translated to English since some participants preferred to communicate in Norwegian; Giovanni took care of the voice recorder and taking photos; Sabina and Khoi were notetakers, one was in charge of Norwegian and the other one copied English comments. After that, we gave them a brief about the focus group activity and discussion rule “All ideas are useful and please speak one at a time”. Though participants were acknowledged about the project when they received the invitation of taking part, we updated them again “We are designing a bathroom scale for personal use, and we seek to understand what you want and need in this product. Your inputs are valuable for making the scale more useful and enhance user experience”. We also let them know how many parts the activity would include.</p><p>Although it had been mentioned in the consent form regarding confidentiality of taking part in the research, the right of leaving anytime, voice recording, and photo taking, we restated to ensure their comfort. After everyone was clear about the concept and rules, we carried on to the first topic.</p><p>Participants were informed that there are no right or wrong answers and if they had no idea or did not experience with something, they were free to mention that. After that, the moderator raised one by one question and displayed it on a laptop. By this way, participants could refer back to the screen if they did not listen well or forget what the question was.</p><p>Is there anyone in the room that use a scale? At home or in the gym or other places? The overall answer was “Sometimes, mainly at home”. Other student mentioned that she used it at the pharmacy “that scale also measures my height and BMI”, she added.</p><p>In the next two questions, the moderator requested everyone to write each answer separately on Post-it Notes:</p><blockquote>What data would you expect to read from a bathroom scale?</blockquote><p>The list of desired data was generated from participants: Body Fat, Weight, Progression, Body Water, BMI.</p><blockquote>What other data do you gather to collect information about your health?</blockquote><p>The results were sleeping track, jogging track, step meter, and some other functionalities that the person recalled from Fitbit, such as pulse meter, training activities, eating habits, setting goals, water consumption. However, one participant commented that those functions were provided by Fitbit, she herself did not use them all. “I do not expect to read that information from the scale. Scale tends to be simple”, another person added on.</p><p>After participants had completed the health data listings, we collected all the notes and pasted them on the wall for more precise observation. Then, we informed them that each person had five dots and they were supposed to make dote voting on the health data which they think needs it to be included in the scale.</p><p>We picked the three categories, which received most votes: Weight, Body Fat, and Progression, to further discussion. While weight absolutely had to be included in the scale, we asked the focus group members why they thought that Body Fat and Progression should be incorporated as well. Someone commented that “In comparison with BMI, Body Fat is more relevant and more precise to follow”. The rest also agreed that it would be beneficial to track the monthly progress of Weight and Body Fat for a long term. We gave them the next question “What are you expecting to see as progress? In other words, how do you want to see the data?”. Participants responded that if they only see results displayed as numbers, it may not be understandable and misleading. For instance, “If I told my mom that she has 68% Body Fat, she would wonder is it good or bad, is it too much?”, one person commented. “That fact does not mean you are overweight. So, the data should be more understandable when people see it”, “I suggest to have more feedback about body fat as it is more relevant and not easy to understand”, the group expressed their thoughts and gave us more useful resources.</p><p>During the discussion of the key topic number two, we tried to understand how a scale works according to the users’ mental model and what the negative and positive feelings of interacting with it were. “Can you describe steps of the bathroom scale that you have been using?”, We asked the group. One person replied “It should display zero at first. I will press start by my foot, then stand up on the scale”. “I do not want to bend down, interact with my feet. Maybe I will need a remote control”, another one stated further. The others also mentioned some facts about what they like and dislike of using a scale: “I prefer a simple scale. When I need to set up my height and weight as a first-time user, it should take less than 5 minutes”, “It should be easy to hide somewhere and durable, in case a kid jump on it”. For the unhappy experience, someone shared that he felt cold when stepping on the scale in the mornings. Many members of the group also raised the fact that people mostly had a negative feeling when using a scale as they did not get the desired number. However, they would love to see the progress no matter it showed a negative or positive movement. When being asked about the good and bad points of displaying charts, all participants said that they like to keep track with graphs, they agreed that charts and graphs were helpful for following one’s progression.</p><p>In the next discussion, we inquired the group regarding the remote screen, we would like to investigate whether people prefer buttons or touchscreen. Four of six participants chose touchscreen while the other two leaned to the buttons version. Explain for the selection of buttons, one person commented that “Touchscreen will have problems with battery, that is why I prefer buttons”, another member gave suggestion “Wireless charging when the screen on the scale, maybe”. Though selecting buttons option, they also shared the concern that “too many buttons are confusing, iWatch has only one button to change views”. We realised that those who preferred buttons version were MAC students. From their expertise, they foresaw the problem of battery. If this issue could be solved, they agreed that touchscreen was more convenient for being used.</p><p><strong>8. Redefining user profiles and personas</strong></p><p>The participants who took part in the online survey and focus group were in the ages from 22 to 40. Therefore, the team redefined the user profiles to match with the collected data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*0ETzzWApGTrhC-NlzibMvg.png" /><figcaption>The revised user personas.</figcaption></figure><p><strong>9. Creating a persona and scenario.</strong></p><p>To specify a typical user, the team created a fictional character and scenario. This technique helped not only the team to step out and look into actual users’ needs but it also made sure the whole team worked on the same target object.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Kz3eC-M4LcWWeEG6" /><figcaption>Persona and scenario–Scale user.</figcaption></figure><p><strong>10. Creating use cases.</strong></p><p>The team generated a use case diagram which defined functionalities and features for the bathroom scale. The original information was collected through user-research activities, such as online survey, focus group, and paper prototypes testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XxJBRj6qmP0BC0fO" /><figcaption>Use case for the scale.</figcaption></figure><p><strong>11. Prototyping mockups in Figma</strong></p><p>Based on the feedback from the previous methods, we started to design wireframes by using an online program Figma. The scale interface did not include colors, as we intended to focus on the visibility of the text. By having a strong contrast between text and background, users would more easily read the data.</p><p>During the prototyping process, there were many questions we need to consider: Should there be only some places users can use the touch? How many buttons/choices on each screen? How many users to include in the system? We also focused on how to make the interaction intuitive, especially when users having interaction with toes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0t1oQPytEfpY2Ipu" /><figcaption>The mockup of the screens created in Figma.</figcaption></figure><h3>Week 4</h3><p><strong>12. Technology and technical specifications for the prototype.</strong></p><p>To create a tangible prototype, we used a piece of recycled wood to make the scale base. Other implements included:</p><ul><li>Raspberry pi 3 B</li><li>Raspberry pi compatible 3.5” LCD screen</li><li>HX711 Amplifier A/D module.</li></ul><p>These devices ensured the prototype would work like an actual scale. The Figma based interface was connected to the Raspberry pi to show other functionalities and tasks, such as loading screen, age and height inputs, create new profile, reading health data progress, and so on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7s44V7NFMXHXd-pZ" /><figcaption>The first wooden prototype with Raspberry pi installed.</figcaption></figure><p><strong>13. Usability testing on the first wooden prototype.</strong></p><p>The test plan was created to make sure the team would explore as much as possible problems from this activity:</p><ul><li>Participants: 5–10</li><li>Responsibilities: One moderator, two notetakers.</li><li>Date and location: During May 2018, NTNU Gjøvik</li><li>Equipment: Computer/Laptop, consent form, printed format of the usability test plan, the prototype, candy.</li></ul><p>Test tasks:</p><ul><li>Task 1: Step on the scale and create a new user. What is your body fat percentage?</li><li>Task 2: Your user profile is number 5. Step on the scale and find your monthly weight progress.</li><li>Task 3: Your user profile is number 2. Step on the scale and find your yearly body fat progress.</li></ul><p>Qualitative measurements:</p><ul><li>Completion rate</li><li>Error free rate</li><li>Time on task</li><li>Subjective measures</li></ul><p>Questions:</p><ul><li>What is your impression of the scale?</li><li>How was your experience with the scale?</li></ul><p>Seven participants were recruited at the end. The results showed that:</p><ul><li>The user-pages were very confusing.</li><li>A person commented on the wooden base that it was a lot bigger in size than the normal scale.</li><li>Participants were surprised when they saw the weight value, they thought it reflected their actual weight (even though we repeatedly said the wireframes were completely static and numbers were fake). For that reason, we saw the need to get real measures.</li><li>Some participant did not realize that the whole screen was a touch-interface</li><li>Balance might be a problem when someone lifted up their feet to interact with the screen.</li></ul><p><strong>14. Iterative design workshop with users.</strong></p><p>The first wooden prototype was put together very quickly and with cheap-recycled material to allow for quick physical iteration. In order to improve the physical design of the prototype, two users were invited to participate in a design workshop with the group. We started the session with an introduction to the product as the prototype was already working. We showed the Figma based interface, and while the users interacted with it, they were asked to use the think-aloud protocol to identify issues in the the interaction as they emerged from the user’s flow of thoughts.</p><p>Various issues emerged during the exercise, and improvements to the on-screen text was needed to obtain sufficient readability. Together with the participants, a series of iterations on the mockups of the screen was created. In order to make it more visible that the user could interact with the screen using the toe, a pulsating foot icon with the copy “toe-touch” was implemented. To highlight that the screen and the base were indeed detachable, it was experimented with the physical shape of the base, adding finger sized cut-outs on the bottom and ultimately on the sides of the screen. Furthermore, an instructional screen was added as the first step when creating a new profile, depicting the screen and the base and suggesting to pick it up to input the data.</p><p>We did also agree that the scale would be more preferable if it had automatic profile recognition. The machine would pick the three most close profiles comparing the measurements and show them on the screen. The user would have to confirm the correct profile to allow for errors in recognition. Finally, the participants suggested to add dots on the botton of the “results”-screen to reveal the presence of more content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lo1mEP6FDwVYdB5tIfL_rQ.png" /><figcaption>Changes to the Figma prototype.</figcaption></figure><h3>Week 5</h3><p><strong>14. Finalizing the whole scale and the interface</strong></p><p>An “upgraded” prototype was created to bring the better experience for users:</p><ul><li>A piece of good quality wood was cut as the standard size of the scale and set together.</li><li>3d-printing machine was used to produce the case that protect the screen display.</li><li>Sensors 4x Weight Sensor (Load cell) 50kg were install. The sensors would measured the true weight of users and displayed it on the screen.</li><li>The interface was finalized (the pink area in the picture below indicates interaction areas).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XhbiBMsPlM_56HTR" /><figcaption>The base of the final prototype, shaped using a CNC machine.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5wUMnYYwST7C0Vzn" /><figcaption>The final interface design in Figma. The pink ares indicate where the user’s can interact with the screen.</figcaption></figure><p><strong>15. Conducting usability testing with users on the final prototype.</strong></p><p>The final prototype was tested in 2 different locations, in NTNU cafeteria and at the bathroom of one of the team member house where the focus group research was conducted previously. One participant from the focus group was invited to test the product, in addition to the user that tested and interacted with the paper prototype. The total number of participants for the testing was 7.</p><p>The team tested if participants used the scale as participants in previous testings (bending down to use the finger to interact with the screen), and if new errors appeared during task performance. All participants were repeatedly informed that the team was testing the usability of the scale, not their personal skills. The same tasks with the first usability testing were given, however, the tasks were rephrased to avoid providing participants with clues:</p><ol><li>Step on the scale and create a new user. Do you remember your user profile number?</li><li>Step on the scale and select your user profile number. Find your monthly weight progress. Could you explain your weight progression during the last months?</li><li>You have been using the scale for a while. Step on the scale and select your user profile number. Find your yearly body fat progress. Can you explain you body fat progression throughout the year?</li></ol><p>After participants had finished their tasks, they were asked to share their interaction experience and thoughts regarding the scale. All comments were noted and prepared for debriefing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/668/1*tl9t8-mS1u9M564FWYqKHQ.png" /><figcaption>The set up of the scale for usability testing at NTNU Gjøvik Cafeteria.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*pz9_6YZuvs3Lv4GsrUX8aQ.png" /><figcaption>Usability testing in a natural setting.</figcaption></figure><p><strong>16. Finalizing and closing the project</strong></p><p>After the final usability testing had been completed, the team conducted the summative evaluation which encompasses time on tasks, number of errors, completion rate, satisfaction, and conversion. These elements helped us to understand how the accessibility of the prototype and what needs to be improved. These aspects were reflected in detail in the project report.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*oFSSdauXKQRtvla5i7mmHQ.png" /><figcaption>The final prototype with the screen installed.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*lwQ0ojYrOaQ_Qo5Oqby3BA.png" /><figcaption>The underside of the final prototype showing the electronics and sensors.</figcaption></figure><p>A short video montage was produced to present the interaction and various configuration of the prototype, and it is visible on youtube <a href="https://www.youtube.com/watch?v=DGvyeJQl-vI&amp;feature=youtu.be">https://www.youtube.com/watch?v=DGvyeJQl-vI&amp;feature=youtu.be</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a31c6bfe75a3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>