<?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 Jonathan Lee on Medium]]></title>
        <description><![CDATA[Stories by Jonathan Lee on Medium]]></description>
        <link>https://medium.com/@jonleenj?source=rss-93616ae021eb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*DAObApT_fQEFnB0cXhQZyQ.jpeg</url>
            <title>Stories by Jonathan Lee on Medium</title>
            <link>https://medium.com/@jonleenj?source=rss-93616ae021eb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 00:17:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jonleenj/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Designing Eatery’s Map View]]></title>
            <link>https://medium.com/cuappdev-design/designing-eaterys-map-view-cfebe679a257?source=rss-93616ae021eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/cfebe679a257</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[eatery]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Jonathan Lee]]></dc:creator>
            <pubDate>Fri, 06 Jan 2017 04:06:28 GMT</pubDate>
            <atom:updated>2018-01-10T06:10:04.665Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_4w_cEjFNtnHn20dKVMCZg.png" /></figure><blockquote><strong>Role</strong>: Designer &amp; UX Researcher<br><strong>Team</strong>: 2 designers, 3 iOS developers<br><strong>Project Duration</strong>: 5 weeks</blockquote><h3>Designing Eatery’s Map View</h3><p>Eatery is an iOS app developed by the Cornell App Development project team funded by Cornell’s Computer Science Department. The app helps students easily look up on-campus dining hall and cafe menus. Prior to Eatery’s adoption, students relied on tediously visiting each campus eatery’s website for menu information.</p><p>With Eatery’s 2.0 update planned for the end of the semester, I was given the task of designing a map feature for the app.</p><h3>Understanding the User — Does a Need Exist?</h3><p>Before beginning the project, I organized a brief meeting with the PM to discuss the motivation behind a map feature. The PM said the CS department requested an update by the end of the semester and he felt a map was very common amongst similar apps.</p><p>This explanation, however, failed to reveal if the implementation of a map view would solve a real problem for our users. Thus, I determined user research was necessary moving forward.</p><h4>Who Is Our User?</h4><p>In order to design for the user, I had to first determine who our main user was. With no collected data on the class year of our users, I turned to activity trends and additional resources and determined <strong>first-year students</strong> were our primary users based on the following:</p><ol><li>Cornell advertised Eatery to freshmen during orientation which resulted in a huge increase in user activity (green portion).</li><li>The level of sustained user activity post-orientation (red line) remained significantly higher than that of last semester (blue line).</li><li>24 of the 29 research survey responses were from first year students.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3b__y00WtVkTj63igdlqpw.png" /><figcaption><strong>Diagram A</strong> — User activity data from the app store reveal freshman as the main user base</figcaption></figure><h3>Key Research Findings</h3><p>To better understand our users, another designer on Eatery, Sara, and I released a survey to Cornell students. Survey results can be found <a href="https://paper.dropbox.com/doc/Eatery-User-Research-Fall-2016-3bzRgX5YS00HRxjtq4Bbj">here</a>.</p><p>We found the following:</p><ol><li>Most users use the Eatery app when they are hungry.</li><li>Users went through similar thought processes when navigating the app:</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OEmf-nuJ58WWDrzrylNXeA.png" /><figcaption><strong>Diagram B</strong> — General User Flow determined from surveys</figcaption></figure><p>3. Most users go back to the same places they eat out of convenience.</p><p>However, when prompted, students expressed they were interested in eating elsewhere but <strong>the main problem was that they were unaware of what other eateries existed along their daily commute.</strong></p><h3>The People Problem</h3><blockquote>Students want to find new places to eat, but they have a hard time doing so because it requires extra effort to go outside of their normal, comfortable habits.</blockquote><blockquote><strong>Objective</strong> — Design a solution that reduces the work and effort necessary to discover new eateries that fit a user’s needs.</blockquote><h3>Exploring Map View Benefits</h3><p>Conducting some market research, I looked to apps like Yelp, Foursquare, and even Google Maps to see what benefits a map view would provide.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sd2khNz9fyGoJv91Qd0TEQ.png" /><figcaption><strong>Diagram C </strong>— Yelp’s map view provides spacial and directional awareness</figcaption></figure><p><strong>Spacial/Directional Awareness</strong> <strong>—</strong> Research on Eatery’s user flow showed that students care about what is open and nearby before they even consider menu options. A map view of eateries has the advantage of representing this information visually which provides spacial awareness that can combine with their own knowledge about the terrain to help make better judgements.</p><p><strong>Convenient Discoverability — </strong>A map view provides the opportunity to discover new eateries along a user’s usual route. This is significant because it promises the least inconvenience by allowing the user to deviate from their usual schedule as little as possible. This reduces the effort required to try a new eatery nearby, thus increasing the likelihood of said event.</p><p><strong>Learning New Environments — </strong>A map not only helps freshmen learn their way around campus, but it can also help all students when classes change each semester. Changes in classes often means changes in their route that may bring users to unfamiliar areas, prompting their need for information about surrounding eateries.</p><h3>Exploring User Flows via Personas</h3><h4>Meet Jeffery:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UFE4SXifUWSZnAVjltz6QA.png" /><figcaption><strong>User Flow A — </strong>attempts to access map view from the current homepage layout with no designated map button.</figcaption></figure><p><strong>Exploration Notes:</strong></p><ul><li>The map view is supposed to help users choose where they want to eat from eateries nearby. Flow A is flawed because users are forced to pick an eatery first before they see spatially related information.</li><li>Getting directions should be the last step after users make their selection.</li></ul><h4>Revisiting Jeffery’s User Flow</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CUHW2Mcmu9MgF8bfp76DeQ.png" /><figcaption><strong>User Flow B</strong> — revisits Jeffery’s user flow by bringing forward the map view into the opening screen.</figcaption></figure><p>User Flow B resolves the previous issue with Flow A by providing access to the map view from the home page. This allows users to leverage the map view without having to “commit” to an eatery first.</p><h4>Meet Tina and Samantha:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xA-hGn1RM6MK8cRwrmyjUA.png" /></figure><p><strong>[Tina]</strong> has very little time to eat and knows she wants to go to a cafe. As such, she opens the app, enters the map view, and selects a set of filters that matches her needs. After clicking an eatery pin for more info, the rest of the flow remains the same.</p><p><strong>[Samantha]</strong> is planning to meet with a friend for lunch. Her friend tells her the name of where they’re going. Unfamiliar with the eatery’s location, she enters the name into the search bar and the map shifts to the eatery with the pin already selected. The rest of the flow remains the same.</p><h4><strong>Exploration Notes:</strong></h4><ul><li>Preview pop-up cards avoid tedious back-and-forth screen changes between the map and eatery menu pages.</li><li>Filters speed up the searching process by reducing options to those that fit the user’s specific needs.</li><li>Search bar reduces time spent navigating the map manually when users already have a planned destination in mind.</li></ul><h4>Choosing a User Flow to Pursue</h4><p>Combining the insights from exploring different user flows with the general user flow derived from user research, I chose to focus on User Flow B as it represented the most logical, fundamental flow:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d-1f6WzGK_B4vzFTH0YPMw.png" /></figure><h3>The Current Eatery App</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*__alioQX5W7w_MqkrlJfXA.png" /><figcaption><strong>Diagram D </strong>— Current homepage with only the top two corners available for navigation</figcaption></figure><h4>Transition to a Bottom Navigation Bar</h4><p>With “Sort” and “Guide” occupying the top corners and with the anticipation of new features including a Debit Balance, it became clear more real estate for navigation was needed. A tab bar seemed the most effective as it:</p><ol><li>Provides adequate room to reorganize the layout of current features.</li><li>Allows room for new features in the future.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vAZhCpfP8X3eMP6S83TxhA.png" /><figcaption>Tab bars allow room for future features</figcaption></figure><h4>Guide vs. Map View Placement</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9fV2T6_NyZiPzi7uNLrdGg.png" /><figcaption><strong>Diagram E</strong> — Guide lets users compare dining hall menus with ease</figcaption></figure><p><strong>Guide’s Tab Bar Placement —</strong> I chose to move Guide from the top right corner to the bottom tab bar because its function was significantly different and independent from other features. This was not the case for Map View.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*riufogLQJu4pkSKEhtSXKw.png" /><figcaption><strong>Diagram F</strong> — Navigational tab bar is reserved for independent features</figcaption></figure><p><strong>Map View’s Corner Placement — </strong>With the tab bar reserved for independent features, I decided to place Map View on the top right corner <em>within</em> the Eatery tab because it offered a visual representation of the same information found in the default list view. Additionally, by placing map view in the corner, users can swap between map and list views with minimal effort.</p><h3>Confirming User Flow is Sound</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M6GpKYA-7dOVqyUG47h4fQ.png" /><figcaption><strong>Diagram G </strong>— Mock up combining all previous design decisions up to this point</figcaption></figure><p>After exploring different user flows and changes to the current homepage layout, I sought to confirm that my decisions thus far would yield a workable user experience. Designing the mock up above of the general user flow showed that it was logically sound, but also revealed areas that needed to be worked on further.</p><h3>Simplifying the Preview Card</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I4lle6LfNQexF7WNECJf5g.png" /><figcaption><strong>Diagram H</strong> — Preview card design explorations</figcaption></figure><p><strong>1. Removing the Image</strong><br>After consulting with other CUAppDev designers, I presumed an eatery’s interior/exterior appearance was not a top deciding factor for users. By removing the image, more attention is be drawn to more important details.</p><p><strong>2. Keeping it Simple</strong><br><em>Card 1b</em> was chosen as it best served the purpose of a preview — displaying priority information. Nothing more, nothing less.</p><p>Blue buttons were dismissed as they drew too much attention towards info of equal (menu) or lesser importance (directions) relative to preview details.</p><p><strong>3. Context Guides Intuition</strong><br>Columns 2 and 3 were explored because I was initially worried that users would not realize the card was clickable. However, I quickly realized that within the app experience it’s clear these cards are something you interact with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JhdPJIUGKfog65ztmPVocw.png" /><figcaption>Yelp also expects users to interact with their preview card.</figcaption></figure><p>Eatery helps students find a place to eat. Students prioritize what is open, nearby, and has desirable menu options (<em>in that order</em>). With that in mind, it makes sense that a user would click the preview card as it follows a logical sequence:</p><ol><li>Users enter map view to see what is open and nearby.</li><li>Finding a promising eatery, they click the pin in hopes of more info.</li><li>Already having their focus on the card, users would presumably tap the card to try to access a menu, <em>the next piece of information they’d want</em>.</li></ol><h3>Finalizing the Product for Eatery 2.0 Launch</h3><h4>Closed Eateries Shown by Default</h4><p>When considering the default map view, I contemplated whether to show or hide closed eateries. To make my decision, I referred back to the problem statement which highlights the goal of improving discoverability for users. With that in mind, I decided to display closed eateries by default to provide users with awareness of all existing eateries around them. This minimizes the chances of overlooking a favorable eatery that’s closed at the moment.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FqkeKyz-TSKw%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DqkeKyz-TSKw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FqkeKyz-TSKw%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a9ff148080198ae954869b7d7f8fb130/href">https://medium.com/media/a9ff148080198ae954869b7d7f8fb130/href</a></iframe><h3>Reflections and Future Considerations</h3><h4>Revisiting Map Traversal</h4><p>At the time of Eatery’s 2.0 release, the only ways to traverse the map view are manually dragging the map around or jumping to a specific eatery via search. It would be great to implement a way to hop between campuses quickly. Some ideas include:</p><ol><li>Being able to type in a campus into the search bar.</li><li>Adding navigation buttons that behave like “Re-center” that bring you to the campus.</li><li>Shifting the map when a user selects a campus filter. (May cause issues when a user selects multiple campuses. Requires further exploration)</li></ol><h4>Exploring Other Non-Map Solutions</h4><p>Due to the time sensitivity of my situation and eagerness to push out a Map View feature by the PM, I had to deviate from my usual design process. In doing so, I was unable to invest necessary resources into ideating solutions and instead worked on supporting an assigned solution.</p><p>Fortunately, the map view had many benefits in play that supported its design. If I were to do it again, however, I would make sure I spent adequate time exploring other solutions and consider their tradeoffs before settling on any one particular idea.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cfebe679a257" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cuappdev-design/designing-eaterys-map-view-cfebe679a257">Designing Eatery’s Map View</a> was originally published in <a href="https://medium.com/cuappdev-design">AppDev Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Four Things Learned from a Design Critique with Facebook]]></title>
            <link>https://uxdesign.cc/four-things-learned-from-a-design-critique-with-facebook-c72c14b985a8?source=rss-93616ae021eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/c72c14b985a8</guid>
            <category><![CDATA[facebook]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[facebookdesigncrit]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Jonathan Lee]]></dc:creator>
            <pubDate>Tue, 09 Aug 2016 01:01:30 GMT</pubDate>
            <atom:updated>2016-08-22T19:05:45.952Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QfIRWx6pHFrPOeqhK4wwIw.jpeg" /></figure><p>A few months ago, I shared my first <a href="https://medium.com/@jonleenj/designing-nearspace-ec40893c814c#.9tjhoiicd">case study</a> for <em>Nearspace</em>, a workspace discovery app I mocked up for an introductory product design class, and was selected by members of Facebook’s design team to engage in a <a href="https://medium.com/facebook-design/peek-inside-a-facebook-design-critique-c4833efda26e#.yvineadsz">virtual critique session</a>.</p><p>The session was very productive and thought-provoking — it challenged many of my design decisions as well as highlighted areas of my design process that required additional refining.</p><p>I wanted to share with the online community some reminders and lessons I took away upon reflecting on my experience.</p><h4><strong><em>Clearly define your problem and audience, then commit.</em></strong></h4><p>Having a clear cut definition of your problem and target audience is like having a solid foundation to build a house on. Without it, you risk designing a “shaky” or poorly defined product and set yourself up for going off course.</p><p>Often times it’s the most obvious things that we unintentionally undervalue. Thinking back to my early stages of ideation, I realize I was working with too broad of a problem statement. I knew I wanted to design an app that would help people find places to get work done, but I lacked a set idea on how I wanted to specifically execute that. As a result, each iteration of my design strayed further away from any one focus.</p><p>This leads me to the second part of this takeaway— <em>commit</em>.</p><p>Once you’ve decided on your focus, commit to it. This doesn’t mean, though, to be stubborn and ignore other possible paths your product can go down. Rather, commit to one specific idea and iterate on it instead of wavering between multiple ones. For example, the Facebook team frequently pointed out that my latest mock up “wasn’t really highlighting the problem”. I incorporated unnecessary features that did not add value to the solution for speed and efficiency, such as irrelevant filters and social capabilities, all because I did not take the time to pause and formally commit in one direction.</p><p>By trying to please every type of user I could think of, I failed to please the one user the product was intended for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V5LI0g_Az2p2_cT5NUAVYA.png" /><figcaption>Preliminary design mockup for Nearspace</figcaption></figure><h4>Formulate an information hierarchy. Reflect it in your design.</h4><p>Just as equally important as having a clear definition of the problem, an information hierarchy is key in determining what information has priority over others. This concept was new to me. Before our critique session, I understood that certain pieces of information were more important than others, but never had I taken the time to formally construct an information hierarchy. As a result, my design suffered:</p><blockquote><strong>Geoff:</strong> …consider thinking through what information you’re surfacing… To me, it seems like distance and name are probably the two most important factors that I want to see in a list. Right now, the distance is actually the most reduced of all elements on the page… Think about all the things that you’re going to be considering and then, again, how they play into your information hierarchy.</blockquote><p>With the selling point of my app being the ability to find a nearby workspace quickly, it made little sense for me to have the distance tucked into a corner in tiny font.</p><p>Another idea the team and I explored was minimizing the size of the pictures and to instead use that space more effectively by bringing forward information of higher priority. In doing so, there becomes a lesser need for a filtering system as the most commonly desired information would be shown in the front of the app as opposed to being hidden behind another screen change. This, in turn, significantly reduces friction and provides the average user with a smoother experience.</p><p>So remember, frequently refer back to your information hierarchy and understand that space is a valuable resource. Don’t waste it.</p><h4>Product design before visual design.</h4><p>This concept was not a new one to me, but one that was difficult for me to take to heart due in part to a recent experience.</p><p>When I was applying for summer internships last Fall, I noticed a number of companies looking for UX designers that seemed to really be looking for visual, UI, or graphic designers. Based on job descriptions and my interactions with employers, I began to get the impression that they were more concerned with my ability to “make things pretty” than they were with my ability to make things functional. As a result, I began to reconsider the distribution of importance between visual design and product design.</p><p>Fortunately, that was all clarified by the end of my critique with the team and my original understanding of good design was reaffirmed. Instead of critiquing my app’s visual design, a majority of our time was spent exploring how the product would be used and collaborating on changes to the product design that would compliment said use.</p><p>There was a lot of merit in shifting our focus towards product design. That’s <em>not </em>to say visual design is not important (it still very much is), but a pretty app alone does not translate to a successful product. Had we solely reviewed my mockup for its visual appeal, we would have missed the core of what makes a product successful — the user experience. Jasmine expressed this perfectly when she said:</p><blockquote>“You can have the best looking app, but if it doesn’t work, no one is going to use it.”</blockquote><p>Be careful not to fall into the trap of getting too caught up in visual design and remember that beautiful aesthetics alone will not compensate for a poor user experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FAVES0rvI01mzW6PjJ1KJA.jpeg" /><figcaption>Credit to <a href="https://medium.com/u/5158fb419488">Andrew Aquino</a></figcaption></figure><h4>Share your designs and ideas with others <em>verbally</em>.</h4><p>The benefit of sharing your designs and ideas verbally is that it forces you to analyze your decisions on the spot. Doing so shouldn’t be a difficult task when you’ve spent enough time mapping out the reasoning behind your decisions. However, it’s when it <em>does </em>become difficult that areas requiring additional processing are revealed.</p><p>For instance, at the start of our critique session, the team asked me to provide context for my design. This included background on what problem I was trying to solve, who I was solving it for, and how my product would act as a solution. Simple right?</p><p>To my surprise, I could sense that my thoughts were scattered as I initially spoke. There were some ideas that I had difficulty expressing eloquently and some questions that I simply did not have a fleshed out answer to. However, as more questions were asked and I heard my own responses, things began to click. Questions I had no clear answer to in the beginning became obvious. I was able to reconcile pieces of information that appeared to be unrelated to form a greater understanding and ultimately fill in missing gaps that would have otherwise gone unnoticed.</p><p>Speaking out loud really does make all the difference. It brings forward your conscious and even subconscious thoughts that were stored in the back of your head and places them before for you, making it easier to organize. Things become unclouded, you begin making new connections, and you’re able to reorient yourself towards designing a better product.</p><h3>Closing Thoughts</h3><p>Facebook is doing something great here with these open design critiques. It’s not everyday that you see such a renowned group reaching out to the community so openly and honestly.</p><p>Having the opportunity to collaborate with some of the best designers in the industry has been an invaluable experience. I was able to gain insight into how critiques are carried out in a professional setting and have been able to transfer what I have learned into leading my own design critiques at my current internship. On top of that, it has helped me improve my design process and has overall made me into a significantly more aware designer.</p><p>To my understanding, Facebook plans to continue their open design critiques. Based on my positive experience, I would highly recommend anyone considering this to submit their designs, especially if they are someone just getting into product design as I was. I understand that doing so could be a daunting task, but believe me, it is well beyond worth it. These designers I have had the pleasure connecting with have been some of the most genuine and considerate individuals I have ever met. They <em>want</em> to help the design community, so let them!</p><p>I hope my honest reflection on my critique session with Facebook provided helpful advice and encourages everyone to continue sharing and learning from one another. I certainly still have a lot more to learn, but I look forward to using what I have gained from this experience as I move forward in my future growth and development as a designer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c72c14b985a8" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/four-things-learned-from-a-design-critique-with-facebook-c72c14b985a8">Four Things Learned from a Design Critique with Facebook</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing Nearspace]]></title>
            <link>https://medium.com/@jonleenj/designing-nearspace-ec40893c814c?source=rss-93616ae021eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec40893c814c</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[facebookdesigncrit]]></category>
            <dc:creator><![CDATA[Jonathan Lee]]></dc:creator>
            <pubDate>Sat, 14 May 2016 04:42:52 GMT</pubDate>
            <atom:updated>2016-05-26T15:46:08.103Z</atom:updated>
            <content:encoded><![CDATA[<p>Medium for finding nearby workspaces</p><blockquote>When I want to find a place to get work done, I want to know the “best” location, so I can maximize my use of time on work rather than searching for a fitting work environment.</blockquote><p><strong>Introduction: <br></strong>The following publication contains the progress I made on a small project over 3 months for a 1-credit course offered at Cornell University called Introduction to Digital Product Design.</p><p>It is important to note that this is my <em>first</em> time exploring UX Design and would love any critiques so that I can continue learning and polishing my skills. Thank you!</p><p><strong>Suggested Format:<br></strong>“<em>I am showing early/mid work around designing an app for quickly finding a workspace to complete projects or any last minute tasks, because it can often be a struggle to find ideal work environments efficiently. I am looking for feedback regarding my early designs and overall design process. There were no constraints to this project.”</em></p><p><strong>Problem:<br></strong>Too often do I find myself in the situation where I waste time traveling from place to place for an ideal work environment. Some factors (which I will term ‘fit factors’) that play into an unfitting work environment include limited seating, poor wifi, lack of outlets, distracting environments, poor lighting, uncomfortable heating/lack thereof, etc.</p><p><strong>Goal: <br></strong>Design a yelp-like app that suggests workspace for users through the use of search filters, reviews, etc.</p><p><strong>Target Audience: </strong><br>Anyone commonly found doing work in cafes, libraries, etc.</p><h4>User Interview — Key Insights:</h4><p><strong>College Student:<br></strong>- More likely to use when in unfamiliar towns/cities<br>- More reliable if there are reviews [requires large user base]<br>- Implementation of pictures are important to user<br>- Desires only “important” information [emphasis on simplicity]<br>- User wants to be able to know to how navigate the app within first or second use. [small learning curve]</p><p><strong>Key Insights/Thoughts Post-interview:<br></strong><em>Likely User Base:</em><br>* People in new/unfamiliar locations.</p><p><em>How to effectively grow a user base? <br></em>* Do research on this.</p><p><em>How to maintain a user base? <br></em>* If the app is used more by users who are in unfamiliar locations, how do I keep said users from ditching the app once they’ve become familiar with their new location or after they have created their own routine and are no longer in need for a search tool?</p><p><em>Simplicity vs Details: <br></em>*I need to distinguish between important/critical information that the majority of people would want to see, versus information that only a select set of people would.</p><h4>Market Research</h4><p><strong>Work Hard Anywhere (app)</strong><br><a href="http://workhardanywhere.com/">http://workhardanywhere.com/</a></p><p>Yelp-style app that gives you reviews on cafes and other working locations near you. Has a very clunky and unintuitive interface — concept is there, but a lot can be improved upon in regards to user experience.</p><p><strong>Croissant (app)</strong><br><a href="https://www.getcroissant.com/">https://www.getcroissant.com/</a></p><p>App that allows you to reserve seating at cafes and charges you for the amount of time of your stay. This addresses the issue of walking into a café and finding no seating available. It also addresses the market/business model issue caused by “<em>laptop hobos</em>”, people who stay in cafés for long periods of time to use its wifi while making minimal purchases (if any). Hence, both the customer and business benefit from this service.</p><h3>Explorations</h3><p><em>What is the scope of this project? [Low-Fidelity Exercises]</em></p><h4>Brainstorming</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*iDOJIw8A6qRsjUddu-thlA.jpeg" /><figcaption>Exploration of filter ideas</figcaption></figure><p><strong>Key Insights:<br></strong>All filters seem like viable options, however:</p><ol><li>The ones that seemed least important were lighting and temperature</li><li>Some filters, such as aesthetics, bring issues of subjectivity<br>- A unique implementation could be the use of 1-word reaction/emoji buttons (like those of Facebook) to convey subjective info. concisely.</li></ol><h4>Sketching Prototypes</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*VujAtkLNQjKEA6boxpHjgw.jpeg" /><figcaption>Prototype sketch of user finding a suitable cafe via filters.</figcaption></figure><p><strong>Key Insights:<br></strong>There are many ways to do one thing and each method should be explored. Some examples include:</p><ol><li>Should the homepage be a map-view or a yelp-like list view?</li><li>Is a map view even necessary? Do users ever use it?</li><li>What is the best way to organize/list the information when the user clicks on the desired location?</li></ol><h4>Personas</h4><p><strong><em>James</em></strong> is a college freshman unfamiliar with his school’s campus. He is looking for places to study outside of his dorm. He is very sociable and loves meeting new people which explains his love for cafes. However, as a hardworking student, he also wants to be able to get down to business and study for hours on end with no interruptions.</p><p><strong><em>Ruth</em></strong> is a driven businesswoman in her late 20s living in New York City. She is very focused on producing her best work and furthering her career. She often does most of her work in the office, but at times is in need of quick 1–2 hour work sessions to complete finishing touches on her reports and projects before presentation. She prioritizes convenience and efficiency in order to get the most amount of work done in the shortest amount of time.</p><p><strong><em>George</em></strong> is a 60 year old retired man living in the suburbs of San Francisco. He loves partaking in relaxing activities such as taking long walks and spending afternoon’s reading books. He is also a very caring grandfather who loves taking care of his grandchildren. What he is looking for is a place where he can read his books while being able to bring his grandchildren with him and have them occupied.</p><p><strong>Key Insights:</strong></p><ol><li>This exercise seems to again confirm that this app would be best suited to an audience who is new or unfamiliar with an area (James), with the new addition of someone who is looking for a quick spot to work at with little investment (Ruth).</li><li>College students seem to desire a combination of workability and sociability in their desired working locations. Hence, information regarding the setting’s noise levels, seating, and food (for social gatherings) may be of higher priority.</li><li>Busy business people are always in search of speed and efficiency. They are likely to prioritize seating availability and the distance of a particular work location. Food, ambience, and other factors may be off less importance.</li><li>The app may not attract much of the older population. Not only are a less of them tech-savy, but older people are known to be “stuck in their old ways”. This may cause them to find a work location they like and settle for it — this removes the function of the app which is to find new working locations that fits the user’s needs.</li></ol><h3>Medium Fidelity Models</h3><p>Interaction 1: Using filters to find a location of good fit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7NkJ2KUJ8CnoMfVRer5TUg.png" /></figure><h4>Critique Feedback Takeaways</h4><ol><li>Too many unnecessary buttons. No need for “More” or “Map” if these implementations hold unknown or little value.</li><li>Buttons seem a bit large.</li><li>Simply yes/no answers for certain filters may be inappropriate and can lack specificity.</li></ol><h3>High Fidelity Models</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UY2PfeloraAJrh2CKpzGBA.png" /></figure><h4>Updates</h4><ol><li>Removed “More” and “Map” buttons. May re-add when more functionality is determined.</li><li>Cleaned the bottom bar design and added icons to make functionality more intuitive.</li><li>Moved “Filter” button from the bottom bar to the right side of the header to conserve space. The placement and fact that it is the only button in that corner adds to the perception of importance as it is a primary function to be used frequently by users.</li><li>Replaced binary yes/no filter options with a rating system to increase specificity to better meet user’s needs and desires.</li><li>Extended the information boxes to the edges of the screen to remove eye strain caused by the higher levels of white space in previous iteration. This change also allows slightly more information to be fit in the boxes.</li></ol><h4>Future Iteration Thoughts</h4><ol><li>Figure out how to address ambiguity about noise levels, comfort, and other future filters. Is a 5/5 noise level indicating the location is very loud or very quite?</li><li>Are there any other filters or interactions to be put in the empty space between distance the filters?</li><li>Implement a “Clear Filters” button to save user time in readjusting filters.</li></ol><h3>Iteration 2</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tWZ_qTDiARaHi-h_r7yIjw.png" /></figure><h4>Updates</h4><ol><li>Added images to home screen for high fidelity. Also added “Map” feature on the top right — again, it might be unnecessary, but user testing will determine that.</li><li>Updated filter screen to make it more intuitive by providing limited user input, but covers enough information to satisfy an user (quantity vs yes/no where appropriate).</li><li>Filter screen also feels cleaner now with the use of buttons.</li><li>Filter screen also has a “reset” button on the top right corner now. May consider renaming it to “clear”.</li><li>Designed Profile page where users can view other people’s favorite locations and recent posts (reviews, pictures, etc).</li></ol><h4>Future Iteration Thoughts</h4><ol><li>Work on color choices. Home screen currently looks a bit convoluted / “dirty”.</li><li>Continue iterating on the profile feature. Since the main focus of the app is finding a place to work easily and quickly, we should consider whether a profile function is necessary (or what features within profiles can be scrapped).</li></ol><h4>Future Implementations</h4><ol><li>Finish designing the complete interaction of a user going from the home page to the filter, back to the filtered home page, selecting a location, reading descriptions of the location, clicking a directions button to pull up Google Maps to guide them.</li><li>Continue mapping out the “add” or “recommend” button. Or even consider scrapping that and only allowing the company to recommend places (though that opens up many more issues such as smaller places being neglected which is not what I had originally intended).</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec40893c814c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>