<?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 Alex Yam on Medium]]></title>
        <description><![CDATA[Stories by Alex Yam on Medium]]></description>
        <link>https://medium.com/@alex.yam.fl?source=rss-cdb0bf20aec5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*2EvAneBzUTqXKv3x.</url>
            <title>Stories by Alex Yam on Medium</title>
            <link>https://medium.com/@alex.yam.fl?source=rss-cdb0bf20aec5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 13:43:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alex.yam.fl/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[Renovating Your House? Get your home designs from RENOVAID~]]></title>
            <link>https://medium.com/@alex.yam.fl/renovating-your-house-get-your-home-designs-from-renovaid-bd349f3e6407?source=rss-cdb0bf20aec5------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd349f3e6407</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Alex Yam]]></dc:creator>
            <pubDate>Mon, 14 May 2018 02:01:22 GMT</pubDate>
            <atom:updated>2018-05-15T04:30:30.458Z</atom:updated>
            <content:encoded><![CDATA[<h4>UXDI-10 P5 : Working in a team and utilising our knowledge on a client facing project</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lRzCWK7zYyl8uvmJclIG0w.png" /></figure><p>With Project 4 under our belt, we were directly given our Project 5 groupings and who would be our clients as well. A initial meeting has been arranged for the teams by the instructors for us to meet the clients, but before that the teams were given our project briefs with information details.</p><h4>Project brief</h4><p>Our client has requested that we do not mention their name and we shall respect that. All that we shall mention is that they are a startup that wants to provide homeowners refined design ideas by paying a professional fee that which they can start their home renovation with.</p><p>From the project brief, we had to do our own research and prepare an agenda with any questions that we have for our clients.</p><h4>Meeting with the client</h4><p>With the client meeting, we clarified on the objectives and expectations of the project. We also agreed on the communication method and the frequency of it as well.</p><p>Following that, our team sat down to discuss on our thoughts on the project objectives and the expectations within our own team. Next up was to discuss on what we would focus on achieving and the methodologies to deploy for this project.</p><h4>Website analysis</h4><p>From our project brief, the client has provided us with some websites that are based overseas as some examples. We analysed the websites to find out how their services worked and took note of certain key features that might be possible to contextualize to the needs of Singapore homeowners.</p><p>We also researched to see if there are any competitors in the local market space that already provides this service.</p><h4>User Research</h4><p>For the user research phase, we decided on the target user demographics to focus on homeowners who were starting out in the renovation process, in the midst of the renovation process and those that have recently finished their renovation works. We also drew up a interview guide with a list of questions for ourselves to refer to.</p><h4>User Research Synthesis</h4><p>We managed to interview a total of 17 users over the next few days. The team got together to synthesis the interviews and came up with an affinity map that helped us understand the behaviors and needs for home owners in Singapore.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ck6ZLURNlIeuYgEz." /></figure><p>Based on the findings, we came up with three user personas.</p><blockquote>1)Upgrading to a second home.</blockquote><blockquote>2)First time homeowner looking to renovate.</blockquote><blockquote>3)Looking to renovate one of the rooms in parent’s home.</blockquote><h4>Co-creation Workshop</h4><p>With our preliminary user research findings, we arranged for a co-creation design studio workshop with our clients. To prepare for it as a team, we discussed on how the workshop’s flow and objectives should be.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CxYx-Abhf7e4tqbjUjzy4g.png" /></figure><p>We conducted the workshop and started off with presenting our preliminary user research findings and the three personas. Following that, some team brain-writing exercises to warm up the creative juices.</p><p>From there, we divided the clients in to three groups, with each group drafting up a storyboard for one persona. With that storyboard, we shifted the groups around to now work on discussing the possible problems or opportunities that might occur during the created storyboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7bTFf2o5Mxsrdpbu2eS5HQ.jpeg" /></figure><p>To end it off, we shifted the groups yet again to now work on possible solutions to address the problems or opportunities. With the workshop conducted, we thanked the clients for participating and got feedback that the clients enjoyed the workshop while learning about their colleagues a little more than before the workshop.</p><p>I felt that it was a very good learning experience for us as well, about how important the flow of the workshop is.</p><h4>Post workshop synthesis of results</h4><p>The team got back together to work on synthesizing the results from the workshop to finalize on the direction of the project.</p><p>From the three persona’s, we decided to focus on the persona that is a first time homeowner looking to renovate the house.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T1LoBfJ52ODbRfrNNCmkRw.png" /></figure><p>With that focus, we drew up a customer journey map detailing the processes that our persona will go through with the possible problems and/or opportunities that arises from it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eR870-3tmETRqqlbXBIrMw.png" /></figure><p>Following that, we gathered the solutions and ideas generated from the workshop to discuss what would be feasible and applicable to the local market context. After the team’s discussion, we came to a conclusion and prioritized these three features out of the bunch.</p><blockquote>1) Style Generator — Difficulty in finding design inspiration</blockquote><blockquote>2) Ad-hoc Expert Services — Unwilling to pay for unnecessary services</blockquote><blockquote>3) Sub-contractor Listings — Difficulty in finding specialized contractors</blockquote><p>From there, we could begin work on digitizing a prototype.</p><h4>To Figma or to Sketch</h4><p>As the design lead, I was given the opportunity to define the style guide for the prototype as well as which platform should we work on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lxr7MjVU381g-KCKS8mtnQ.jpeg" /><figcaption>Figma Design Tool</figcaption></figure><p>We heard about Figma as a viable alternative to Sketch, and I began to research a little about Figma. To find out that the UI will be familiar to Sketch users, also an exciting feature was the real time collaboration between teams and the ability to do prototype in Figma as well. It’s also an web application with a desktop web app for both Windows and Mac users. But one fact is that it does not have the vast number of plugins that Sketch has, so pros and cons I guess. The team asked for my decision and therefore we went ahead with Figma.</p><p>With that, I focused on getting one key screen for the team to use as a template while the team worked on the presentation portion. With my template ready, we worked on digitizing the key screens and getting our version 1 up. While merging and linking up the screens, It hit me that the design lead’s role is important in making sure the whole prototype is consistent in style. I really am grateful to my team mates for supporting me and giving me this opportunity in this role.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/866/1*wNnv6BiAcCQbIT3Wb_zTSA.gif" /></figure><h4>Usability Testing</h4><p>Once the prototype was completed, we went ahead to arrange appointments for usability testing. We wanted to get feedback not only on the prototype but the idea behind it as well. From the 7 users whom we tested with, the general feedback can be synthesized to the following statements.</p><blockquote>I would prefer a designer who can oversee the project from start to finish</blockquote><blockquote>I would need to see some past works to determine if they’re credible.</blockquote><blockquote>We’re not comfortable with paying the full amount without any guarantee of service.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/525/1*0P75kluQsK5_9-NHxMQmQg.png" /></figure><h4>Iterations</h4><p>From the feedback, we iterated our prototype and as well as the service idea.</p><p>To address the payment concerns, we added options to pay a 10% deposit or talk to a consultant.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hz2T9yEOCBht--MBp9exRQ.png" /></figure><p>As for the credibility, we opened up the portfolio page that can be filtered or sorted accordingly for users to browse through.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/857/1*MDiMIhPpHQrJHlFebiG-hQ.png" /></figure><h4>What’s Next</h4><p>After the iterations, we concentrated on the presentation deck. As we already had decided on the presentation flow, it was a matter of adding the content to each section and splitting the sections between the team.</p><p>For the last section of the presentation, we elaborated on the next steps that our clients can proceed on to further validate this service feasibility. Lastly, we thanked the clients for the opportunity they gave us for this project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/817/1*VNG7DKTJ2oBPWa62rhAl8w.gif" /></figure><p>And Project 5 has come to a close along with the UXDI course as well.</p><p><a href="https://www.figma.com/file/PYQcvJeDAYkSMQwjkUSlSO54/UXDI10-P5-ABDL-Prototype?node-id=31%3A60"><strong>Click here for the prototype link~</strong></a></p><p><a href="https://docs.google.com/presentation/d/1fcsGknKq2IBNHHmZTHnvKnEiWAHFoAQgwZfLyGTH5ns/edit?usp=sharing"><strong>Click here for the presentation deck~</strong></a></p><h4>Reflections</h4><p>It’s been one hell of a roller-coaster with many twists and turns, but I have to say with each twist and turn there’s been a lesson to learn from and hopefully I can apply those lessons in not only my working life but my personal life too!</p><p>As always, communication and time management between the team is so very important that I cannot stress those points enough.</p><p>It’s going to be exciting times for myself, stay tuned for what’s next!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*f30oeSeu6rQVQibr." /><figcaption>Photo by <a href="https://unsplash.com/@whitney_wright?utm_source=medium&amp;utm_medium=referral">Whitney Wright</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Thank you to those for taking the time to read all the way here, here’s some cookies for you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd349f3e6407" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Revamping of the SBS Transit Website]]></title>
            <link>https://medium.com/@alex.yam.fl/revamping-of-the-sbs-transit-website-66c4d49f0f18?source=rss-cdb0bf20aec5------2</link>
            <guid isPermaLink="false">https://medium.com/p/66c4d49f0f18</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Alex Yam]]></dc:creator>
            <pubDate>Sun, 22 Apr 2018 14:05:15 GMT</pubDate>
            <atom:updated>2018-04-22T14:05:15.843Z</atom:updated>
            <content:encoded><![CDATA[<p>UXDI-10 Project 4</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Vhr8TTgtWmXqXzR8." /><figcaption>Revamp of SBS Transit Website</figcaption></figure><p>Another two weeks, yet another project accomplished.</p><p>Recently we had a lecture on Agile methodology, our lecturer clarified with us that the reasoning behind our project timelines was to let us familiarize with the pacing of sprints which typically spans from two to four weeks.</p><p>Once again, our team grouping was randomized but the most amazing thing happened. Against incredible odds, the team compromised of the members of project Snapchat with an addition into the team. We were definitely scratching our heads on the odds of this pairing that occurred. Wasting no time, we moved on to the project brief.</p><h4>Project Brief</h4><p>This time our project brief is a little different, the teams were assigned a company’s website to revamp and our teaching assistants were simulating as the point of email contact client. We received a project brief that contained a short introduction of the company, the problems, main requirements, timeline and the criteria for awarding the project. If we had any questions to clarify, we only had until the end of the day to email the client.</p><p>Also one key difference between the past projects, was that this is to be considered a pitch in order to secure the project.</p><h4>Clarification with Client</h4><p>We quickly got together as a team to discuss expectations within the team and went ahead to discuss the items that we needed clarifications on. With that, we drafted an email and sent it. I felt that this is an important process, as it was the first albeit small step in the transition to working on UX projects in the working environment.</p><h4>Website Analysis</h4><p>Before we even begin on thinking of how to revamp the website, we needed to know what we were dealing with. We took time to visit the existing website, trying to find out what SBS Transit(henceforth known as SBST) was trying to provide to commuters via the website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/815/0*T0MJdf73BSN-MJ59." /></figure><p>With just a little time spent navigating the website, there were a number of glaring issues that was just screaming at us. Font sizes that was way too small, broken features and links right on the home page, multiple entry points via the top level navigation into the exact same page. The list goes on, and we shall leave the critique to the users themselves.</p><p>But just before we move on to usability testing on the existing website, we sourced for transport related websites that will serve as good examples for us. The ones that stood out to us was Transport for London and Amsterdam’s GVB, their clarity and knowledge of what the users required to access upon accessing the website was made clear on the design of the webpage. So much so we could see certain websites emulating the style in their own way, for example, Singapore’s SMRT and Hongkong’s MTR.</p><h4>User Research</h4><p>For this phase, we had to decide the methodologies that we wanted to deploy in order to gather the relevant data.</p><p>With that in mind, User Interviews to understand the commuters travel needs and pain points</p><p>Card Sort as we wanted to re-organize the top level navigation of the home page</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Cdp3BpgapGSlpFXQ." /><figcaption>Card sorted</figcaption></figure><p>Usability Testing on the existing SBST website to identify how well can the users perform key services.</p><p>We also did research on the business model of SBST as well, where we found out more on the Bus Contracting Model which helped us understand the relationship between the Ministry of Transport and the Transport Operators. This is important as only then we can start to understand SBST and what it offers to the commuters.</p><h4>Synthesizing of Research Findings</h4><p>With the user interviews, we plotted an affinity map which helps us decide on the common needs and pain points that most commuters have. Which in turn assisted us in prioritization of the features that were essential for commuters.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MZLHp846-RePpjwI." /></figure><p>On card sorting, we conducted both an online and a physical card sort test. With the findings, we found out how would users group the various information into catergories that made sense to them.</p><p>On the usability testing on the existing website, we also made use of contextual inquiries in order to see how does a typical website visitor would navigate on the site.</p><h4>Wireframing for version 0</h4><p>With all the findings, we proceeded to prepare the wireframes for our prototype. As we were a team of 4, even though we worked on previous phases together, still each of us might have different images in our heads of how it might look like.</p><p>We decided to try out doing a design studio between the team, which meant that each of us drew up a sketch of key screens within a time-box of a few minutes at the same location. Once we were done sketching, each of us presented our sketches and received feedback for it.</p><p>I personally felt that this really helped in getting everyone to convey their mental image of the prototype and made everyone have a connection with the final product.</p><p>With this digital wireframe, we proceeded to perform some usability testing with some willing users and got feedback about the key services feasibility, be it positives or negatives.</p><h4>Prototype version 1</h4><p>With the feedback, we proceeded to iterate as well as refined the fidelity of the prototype.</p><p>With the iterations done, we proceeded to perform one more round of usability testing to validate the changes and the general look and feel of the website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*S96W8mGAwjcm6Deh." /><figcaption>Desktop version of the home page</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/0*wfo5_hBy15A4ME_1." /><figcaption>Mobile version of the home page</figcaption></figure><h4>Presentation preperation</h4><p>Although this section is at the bottom, it didn’t meant that we only started to work on the presentation at the end. We had drafted out the presentation all the way back on Day 1, with headers from our project plan which helped to guide us through the project as well.</p><p>With each phase of the project, we entered the data from each phase as well. We decided to employ GIF images to better showcase the comparisons between the existing website and our proposed website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/322/0*AiHrtbCORDOY1lU5." /><figcaption>Journey Planner</figcaption></figure><p>As for the commuter journey map, we spent a substantial amount of time to decide how we would present the findings on user research. In order to make it simple for the audience to understand, we drew up a customer journey map to let them visualize in a easier to digest manner. We even thought up a small little skit to go along with the presenting of this section, which I felt was the key to us winning the best presentation award as it made our fellow mates laugh a little and was more memorable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1Y3buwjbaifMnQJXQKAaJg.png" /><figcaption>Customer Journey Map</figcaption></figure><h4>Reflections</h4><p>The increasing difficulty in project 4 compared to the past 3 projects was certainly felt between the team, where we had more factors to consider from both the user end and the business end and how we could balance the two ends.</p><p>It’s been an fruitful two weeks and I would not have swapped my team mates for anyone else in the world.</p><p>As always things to improve on:<br>Presentation skills, <br>Time management, <br>Effectively conveying your thoughts and ideas to others,<br>Digital Prototyping skills,<br>Presentation preparation</p><p>If you’ve made it this far yet again, Thank you for the support!</p><p>Onwards to Project 5!~</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66c4d49f0f18" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making Snapchat More Usable!]]></title>
            <link>https://medium.com/@alex.yam.fl/identifying-problems-and-or-opportunities-with-an-existing-mobile-application-snapchat-33f00b9d43fe?source=rss-cdb0bf20aec5------2</link>
            <guid isPermaLink="false">https://medium.com/p/33f00b9d43fe</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Alex Yam]]></dc:creator>
            <pubDate>Sun, 01 Apr 2018 07:57:24 GMT</pubDate>
            <atom:updated>2018-05-15T09:19:01.679Z</atom:updated>
            <content:encoded><![CDATA[<h4>UXDI-10 Project 3 : Identifying problems and/or opportunities with an existing mobile application</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*S3vARyWb5zyJA64WALE58A.jpeg" /></figure><h4>Project Brief</h4><p>Project 3 has begun and passed in a blink of two weeks. Once we got our team groupings, we found out we had to choose an existing mobile application available in the market and work on identifying if there are problems and/or opportunities with the application.</p><p>After a little discussion between the team, we decided to go with the Snapchat mobile application. Personally, I have not used Snapchat before but I do know about the basic features that it has to offer and it’s core audience is mostly for the younger generation. I felt that it would be a good experience and also an interesting challenge to learn about an application that I would never have thought to use.</p><p>Following that, we drafted out a project plan to list our objectives and timeline to adhere to it during the project phase so as to keep ourselves paced and make sure we don’t spend too much time on dwelling on an activity.</p><h4>First Impressions — Expert Review</h4><p>So first up, we needed to learn all we could about Snapchat by installing the application and just playing with the features. We definitely could see a few problems with the application, namely the affordances for ease of navigation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/225/1*CfYV8XskhHJfvWn6uPi96Q.png" /></figure><p>Next we researched a little more on Snapchat’s business model, usage statistics and any other related news on Snapchat. It gave us a good insight on Snapchat’s company, Snap, and how their business and revenue model is structured. The usage statistics also helped us in narrowing down our target audience, while we found out about competitors to Snapchat as well.</p><h4>Competitive Analysis</h4><p>We narrowed down to our research on three other mobile applications that are similiar in terms of functionality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*w4Qc-MizI6bV7geS0P9f7A.png" /></figure><blockquote>Facebook Messenger, Whatsapp Messenger and Instagram</blockquote><p>For all the applications, we drafted out a list of tasks to be performed on each of them to test the ease of usage and navigation. This gave us an insight on the strengths and weaknesses of each application, and each application’s unique selling point.</p><h4>User Research</h4><p>After the research and analysis, it was time to gather our target users to interview about Snapchat. We focused on getting users who are using Snapchat actively and those who previously used but have stopped using the application.</p><p>After performing the interviews and transcribing the voice recordings, the team got together and discussed on the findings. We went ahead to use the methodology called affinity mapping in order to find out common categories based on the comments by the users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CH2eHS__3TfLor6dkuQR6g.jpeg" /><figcaption>Affinity map</figcaption></figure><p>From those categories, we focused on three that had the most comments. Firstly was on the “Stories” feature which might not an issue but are what users collectively agreed that it’s a core reason of using Snapchat, which is find out what their friends are sharing and the happenings in their lives.</p><p>Secondly was on the unfiltered/informal vibe that the chat features offer to the users, features like disappearing messages after bring read, the filters and lenses to create interesting and quirky media to share with friends.</p><p>Thirdly was the average usage time an user will spend on the application itself is about 3–5 minutes per session.</p><p>To address the three focus categories, we wanted to improve on the experience of viewing “Stories” from friends while updating the informal and fun direct messaging platform. Also to think of ways to increase the average time spent while in the application.</p><h4>Use Flows</h4><p>With the three focus areas, we created a task for each of the areas to work on.</p><ol><li>Viewing of Stories</li><li>Personal Messaging</li><li>Discovering new content</li></ol><p>With each task, we worked on the core feature and added features and/or improvements to it.</p><p><strong><em>Viewing of Stories</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*EfaQlmafma8lpS2QZ4-Lng.png" /></figure><p>In the current implementation, chats and user stories are combined into a single page. In order to chat with friends, users have to scroll through a long list of stories which might or might not be posted by the people they want to talk to.<br>Based on our previous findings, we found that users who want to use Snapchat as a direct messaging platform don’t necessarily also want to see stories. As such, we decided to separate the two functions into two separate pages.<br>One more finding is that the users don’t really go to the discover page anymore and from our business model analysis, we discovered that most of snapchat’s business revenue derives from the sponsored content. So combining Stories and the sponsored content onto one page, where users can view stories and sponsored content, we believe it will benefit both users and the business model.</p><p><strong><em>Personal Messaging</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*P30y5Agmxazhg8VVDjRieA.png" /></figure><p>We focused on improving the personal messaging feature to enhance the user experience that snapchat will provide since very active users were using Snapchat as a messaging app. <br>With the current system, chats were organized in a confusing manner which did not make sense to our users, making it difficult for them to find the people they want to chat with. We introduced two ways of sorting users, ‘by chronological order’ and ‘by hot friends’ (friends with streaks and starred) with a tabbed function, making it easier for users to find exactly who they want to chat with.</p><p><strong><em>Discovering new content</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/754/1*La-URlL0IztolI6Rs872yQ.png" /></figure><p>For this portion we decided to shift the focus of the discovery page to see stories from events happening rather than friends’ locations which users commented on it being very creepy and a perceived invasion of privacy. Also active users would occasionally activate the current function but do not use it as much because it is not presented as an important feature due to its low discover-ability, it also makes it difficult for first time users to find the feature because it is hidden behind a gesture with no indication.</p><h4>Prototyping</h4><p><strong><em>Version 0</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ki5M8NZ7hHLKy2mcUq6SKA.jpeg" /></figure><p>With the use flows drafted out, we worked on getting a paper prototype out quickly so that we could use it to do our first round of usability testing with a number of task to perform. It was a good decision as we could quickly churn out feedback about the usability of what we designed before moving on to the digitizing of our prototype. We further refined the prototype with the feedback and proceeded to digitize the prototype using Sketch.</p><p>First we defined the art style by getting a few of the key frames with the various elements up. Then we went ahead to split the key frames between the team. Once we done with our part, we compiled the frames into a master file. My afterthoughts is that the collaboration and combining portion of the prototype could have been more streamlined as we had to save and edit multiple versions of the file.</p><p><strong><em>Versions 1 &amp; 2</em></strong></p><p>With the first digital prototype, we managed to find users to perform another round of usability testing with the same tasks from the first test. Which was very helpful, as it definitely helped to get feedback from the user’s perspective in which we would have not noticed as easily.</p><p>Feel free to take a look at our prototype at this <a href="https://invis.io/DCGKWBLHZ79#/287604625_Take_Photo-New">link</a>, I’d appreciate your feedback and comments~</p><h4>Presenting our project</h4><p>With our research and prototype done, finally we had to do up our presentation. It’s really not as easy as it sounds, to condense all our findings and our justification of our prototype to within 15 minutes. I do feel that this is an important skill to brush up on, as it prepares us for our future working experience where another person’s time is hugely valuable and they will only spare you a limited amount of time to present your thoughts and ideas.</p><p>Our presentation deck is located <a href="https://docs.google.com/presentation/d/1pJvtOhMPjGjPTfUCjA4L__KktXNnbEpAYlN2PaxZ2bs/edit?usp=sharing">here</a> if anyone is interested!</p><h3>Reflections</h3><p>Overall, I had a very interesting time with this project even though I had to learn about an application that I had never expected to use. I really appreciate my team members on what we’ve done and learnt together, they definitely made the experience much more fun and enjoyable along the whole journey.</p><p><em>On-going list of things for myself to improve on;</em></p><ol><li>Presentation skills</li><li>Time management</li><li>Effectively communicating my ideas and thoughts</li><li>Focusing on the task at hand</li></ol><p>Thanks to everyone that has read all the way to this section!</p><p>For now, onwards to project 4!~</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-iKM-ZRPPZ2BMqmv9U1jXw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6IrhKn16UpYatgvk4kqreQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=33f00b9d43fe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The NUS Business School Website Needs An Update!]]></title>
            <link>https://medium.com/@alex.yam.fl/redesign-of-the-information-architecture-and-key-pages-of-a-school-college-website-cb2f003dbe9a?source=rss-cdb0bf20aec5------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb2f003dbe9a</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Alex Yam]]></dc:creator>
            <pubDate>Sun, 18 Mar 2018 08:54:25 GMT</pubDate>
            <atom:updated>2018-05-10T05:28:03.717Z</atom:updated>
            <content:encoded><![CDATA[<h4>UXDI Project 2 : Redesign of the Information Architecture and key pages of a school/college website</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3GQTiixrs2ncnxD_." /><figcaption>Photo by <a href="https://unsplash.com/@benkolde?utm_source=medium&amp;utm_medium=referral">Ben Kolde</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The start of week two was also the beginning of our project two as well, we were tasked to redesign a school/college website. Once we were paired up in our teams of two, we got to find out what schools was assigned to each sets of team. As for my team, we were assigned to the National University of Singapore(NUS) Business School website together with two other teams for a total of 6 people. We had the option to combine our efforts for the project but the final deliverable was to be worked on with your partner.</p><p>We quickly scanned through the existing website and immediately took up the opportunity to worked together for the research portion as the website was quite a mess. Fragmented, micro-sites and broken links are just a few words to describe the site.</p><h4>Understanding the personas</h4><p>Besides the website, we were given three personas as an accumulation of three different kinds of users who would visit a school/college website.</p><p>1Mark, someone who is looking to join the school as a full time student.</p><p>2 Jessica, a current student in the school.</p><p>3John, an working adult looking for options to improve his skillsets at the school.</p><p>All three have different needs and pain points to consider and factor into the redesign of the website. Our design had to incorporate all three personas but for our prototype, we had to showcase key frames for addressing one persona’s needs and pain points.</p><h4>Gathering the inventory</h4><p>So first up in order to redesign, we need to get familiar with the existing content and understand both the users that will visit the website and the clients that handle the website. We spent quite a chunk of time looking and listing down the website and it’s links, and I have to say that it’s good reason why the NUS Business School website has 6 members grouped up for the research portion while the other school websites have 4 members grouped together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l7ywC4yNeqc5aAuAHhBKUw.jpeg" /><figcaption>Website surveying</figcaption></figure><p>With 6 members, we sieved through the website by splitting the sections between ourselves and consolidating to create the full inventory of what the website has. Along the process, we definitely learned more on the various programs and services that the school has to offer. What we learned also was that it’s not easy to find the information that a visitor would expect on navigating the site, granted the information is massive and different portions are handled by the different offices of NUS.</p><p>From this point onward, our group of six split up into our teams of two to continue the project.</p><h4>Sorting the unsorted</h4><p>On drawing up the content inventory, the next step was to figure out how to reorganize the data so that it would easier for the user to find the required information in the least amount of steps as possible. We went ahead with deploying the method called hybrid card sorting to help us understand how others would organize information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eGjDCaTr11bkNe4nVg_O5w.jpeg" /><figcaption>Our valuable participants</figcaption></figure><p>The process to create the card sort test was not as simple as expected, we had to think carefully on the category names and the items to be sorted under those categories. As it was a hybrid card sort, the participant could also add new categories as well. We then proceeded to arrange for 6 users to participate in our card sort test.</p><p>After the physical card sort testing, we could sort of visualize how we wanted the flow of data to be organised but it was hard to make out the actual results of the test. We decided to make use of an online platform called Optimal Workshop to help us compile the card sort results to make more sense of the data. From there, we sat down to discuss how our information architecture would look like and drafted our first sitemap.</p><h4>Tree Testing time</h4><p>With our sitemap drafted, we deployed a method called tree testing to evaluate our sitemap structure and whether users would be able to understand and locate the information required. We do this by setting a few tasks for the user and observing if they are able to find the correct tree branch from the root. Thankfully, Optimal Workshop has an online tree test platform for us to utilize.</p><p>Once we set up the tree test survey, we sent it out to 12 users who agreed to participate. After performing the survey and analyzing the results, we refined our sitemap by adjusting the architecture and even renaming categories.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S8YnDkupbVQu8fCbhaO8tg.png" /><figcaption>Optimal Workshop results</figcaption></figure><h4>Reviewing as an expert, heuristically</h4><p>While the tree test survey was ongoing, we utilized the time to perform analysis on other school/college websites to identify standard features and best practices. While looking through the different sites with so many styles and variations of layouts, it was a good learning experience as a user to see what I personally thought was good and bad. One difficulty was actually trying to keep it unbiased and unopinionated though, hopefully I can remind myself down the road.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*qUEW6Rptam7Ct7lWDePipg.png" /><figcaption>Clemson University — Mouse over interaction</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/818/1*Gv2L8c12Hb5inolStoeTZA.png" /><figcaption>Texas University — Nice call to action buttons</figcaption></figure><h4>Axure-ing interactions on prototype</h4><p>With our refined sitemap, we can proceed to creating our prototype! First thing first, we did a hand drawn sketch that would be used as an style guide for the whole website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oEhHmoWhpJ_gWMZL_jlrcw.png" /><figcaption>Prototype done on Axure</figcaption></figure><p>Next step is to digitize the sketches using Axure, we had just learnt the tutorials so there was a little learning curve on the initial page. Once we got the first page up, we had an easier time drawing up the other pages. Applying the interactions that we wanted was quite the task but still manageable. I hope to improve in using Axure as it really is quite useful in creating interactive prototypes.</p><h4>Testing the Usability, with users</h4><p>With our first prototype functional, we arranged for users to help with our usability testing. The insights we got was really important as it helped us spot design issues that we would have never spotted on our own. With those insights, we iterated and refined the design twice after managing to find time to conduct two separate sessions of usability testing.</p><p>Here is the link to the prototype; <a href="https://82ykv8.axshare.com/#c=2">https://82ykv8.axshare.com/#c=2</a></p><p>Do leave a comment if there is any feedback on it~</p><h4>It’s time to present our findings</h4><p>While working on the prototype, we also worked on the presentation slides. We had 10 minutes as a team to present our proposal which includes a refined sitemap and the interactive prototype. 10 minutes is actually not as long as you think, we have to manage the details that we want to talk about in a client orientated presentation.</p><p>As it approached our turn to present, I still got nervous and felt that I could have done better to convey the points that I had on my findings and about the prototype. After presenting, watching the other teams presentations is always a good learning experience. I hope to apply the knowledge learnt in my upcoming presentations.</p><p>The link to the presentation is located here; <a href="https://drive.google.com/open?id=1ChJXW4IEYrwwQ-Mygjzz5caRWUrsxUjoDzdQhgeDZTU">https://drive.google.com/open?id=1ChJXW4IEYrwwQ-Mygjzz5caRWUrsxUjoDzdQhgeDZTU</a></p><h4>Reflections</h4><p>Overall the whole project is definitely a strong learning experience that I aim to add on my repertoire to aid in my future projects. I still would like to point out that I need to improve on my user interactions, usage of Axure tool and my presentation skillset.</p><p>Onward to Project 3!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb2f003dbe9a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Foodie 4 Vegetarians]]></title>
            <link>https://medium.com/@alex.yam.fl/uxdi-10-project-1-vegetarian-foodies-e718fd9149f2?source=rss-cdb0bf20aec5------2</link>
            <guid isPermaLink="false">https://medium.com/p/e718fd9149f2</guid>
            <category><![CDATA[uxdi-10]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[uxdi10-redux]]></category>
            <dc:creator><![CDATA[Alex Yam]]></dc:creator>
            <pubDate>Sun, 04 Mar 2018 08:30:05 GMT</pubDate>
            <atom:updated>2018-05-15T08:44:37.591Z</atom:updated>
            <content:encoded><![CDATA[<h4>UXDI-10 Project 1 — Updated with Version 2 Prototype~</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-stoad_3b3pVs-sCnfJU_g.jpeg" /></figure><p>The first week of my UXDI course has flew past, together with project 1 as well. Right on day 1 of the course, after the intro lesson we were briefed on Project 1 and what was to be expected, deadline was the end of the same week as well!</p><p>The topic that chosen for me was on Food, we then had to interview our partner and at least 2 other persons about their needs and desire around the topic. Based on that, we had to define a problem, design a solution and build a interactive prototype for a mobile app.</p><h3>User Research</h3><p>Before getting my interviewees, I decided to sit down and think of the questions that I would like to ask. Since the topic was on food in general, I knew that if I didn’t think through carefully on my questions I would get insights and opinions from just about anywhere. But on the same hand, if my questions were too specific it would lead to it being leading or complicated.</p><p>So after giving it some thought, I settled on questions related to preferences on eating outside or eating at home and any recent memorable experience on it, be it good or bad.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U1becfvLX9e-Vq-K-FkcxA.jpeg" /><figcaption>Discussion Guide</figcaption></figure><p>So armed with that discussion guide I did my interviews and I have to say, we need to be prepared to throw away the initial questions as the direction of the interview can go anywhere based on the interviewee’s reaction and answers. Oh! I also proceeded to get into the habit of doing voice recordings for the interviews, I personally felt that constantly jotting down notes really breaks the flow of the interview.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0GW7HmJt-n5WNJqR2-du3Q.jpeg" /><figcaption>Interview with my Partner, Anna</figcaption></figure><p>In total, I interviewed 4 users and also was interviewed by them as well. On the last interview though, I could remember the feeling of drifting off and “stoning”. This portion is a really new experience for me, hopefully I build on this and can improve my interview skills.</p><h3>Synthesizing the data</h3><p>With the data from the user interviews, everything was most definitely all over the place and it took quite a while to sort out the usable data. Firstly I had to listen back to the interviews to see if I missed anything out and also to review my questions and the way it was asked.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EBCaXpn0mE1q3R1V4I1wAw.jpeg" /><figcaption>Affinity Map</figcaption></figure><p>On building the affinity map, Our lecturer advised us to use an “I” statement to label our groupings for this project and I think that really helped to filter out the usable data from opinions which might be biased based on the person’s personal experience. As this was the first project with topic that is very broad, we were told to just pick on issue to work on. I personally felt that doing this made me relieved as it didn’t apply any of the practices that we were taught which would have made the problem defining a lot more difficult.</p><h4>Problem Statement</h4><blockquote>Vegetarian users need a common platform to look for and recommend vegetarian food options because existing apps are lacking in features and the community is small at the moment.</blockquote><h4>Solution Statement</h4><blockquote>The solution would be to design an app that fulfills the requirement of easing the process of sourcing vegetarian food options. The App will also include features that strives to reward both the app user for posting reviews and eating places for being reviewed to generate awareness for improving their business recognition.</blockquote><p>I went ahead with this issue as it seemed to be a genuine concern for vegetarian person on sourcing for food places to meet their needs, I was fortunate enough to have 2 vegetarians out of the 4 interviewees which helped in narrowing down my scope. I myself am not being a vegetarian, knew that I had to do my own research on the current app choices and more on vegetarian food options as well.</p><h3>User Flows</h3><p>Next up was to design the app, but to do that I drew up simple user cases in order to help me visualize the app. Something a little more familiar to me, I have to say.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aqP8Kg7DhXAmPcozagojTQ.jpeg" /><figcaption>Use Case: Looking for Vegetarian food place</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/862/1*UcGgrWo4O6CYvyuCYY02JQ.jpeg" /><figcaption>Use Case: suggesting of new food place</figcaption></figure><h3>Wireframes</h3><p>So first up, hand sketching for the app. Coming from a non design background, so please excuse my woeful hand drawings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vih-QRI6UCUyuipvmJVdDg.jpeg" /><figcaption>Hand Sketch: Looking for vegetarian food place</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LFQdhnyZtfezkvdfmmuegg.jpeg" /><figcaption>Hand sketch: Suggesting a new food place</figcaption></figure><p>For the next step, I went with the option of hand drawing the prototype as I was not familiar with the digital tools and was factoring in the time constrain of the deadline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tqyRg5kefeMmsweH3kmS8Q.jpeg" /><figcaption>Main page and List of food places</figcaption></figure><h3>Interactive Prototyping</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/446/1*BdCKpp731Ue9jn4MuSHcQg.png" /><figcaption>Prototype on InVision</figcaption></figure><p>The prototype would definitely have looked much more presentable if it was done digitally, something that I hope to allocate more time on this section. Along with the prototype, we had to prepare a 5 minutes presentation as well. Another area where I am not familiar with and hope to improve on in future, it was so nerve racking while waiting for my turn to present. I managed to get some feedback that I will try to factor in future.</p><h4><a href="https://www.figma.com/file/0C25SxgWnLeICY34yBmbWCU7/Foodie-4-Vegetarians">Version 2 of the prototype is up!</a></h4><h4><a href="https://projects.invisionapp.com/share/U8G47IK46RZ#/screens/282362888_01_-_Main_Screen">The Prototype Version 1 is available at this link if anyone is interested:</a></h4><h4><a href="https://drive.google.com/open?id=1bNir-dTLVkxV1ui2E4ZhEBu4azYjPgaz">The presentation slides link as well:</a></h4><h3>Reflection</h3><p>Looking back on the first week, I felt that tried my best to apply the practices that was taught to us onto the project and in actual fact, i believe that the lessons does help us along the whole of the UX design flow. Project 1 did its job well in giving us a small taste of how it is to work on a UX project. Hopefully I can get more feedback from the lecturer and facilitators in the coming week to see how I fared in their point of view.</p><p>I enjoyed the journey of the project and at this point of time, the things that I should improve on are my interview skills, time management and the skills for digital sketching. And those are only the things that I know of, so much more to learn and try.</p><h4>Thanks for reading if you made it this far!</h4><h4>Onward to the next project and the UX world!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*um-hKx-f2fyN2PVg6MsmpQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e718fd9149f2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>