<?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 Jaciel Reyes Giraldo on Medium]]></title>
        <description><![CDATA[Stories by Jaciel Reyes Giraldo on Medium]]></description>
        <link>https://medium.com/@jacielrg?source=rss-3a58eea96d53------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Ih8hzz-QRxxq0Qnm.jpg</url>
            <title>Stories by Jaciel Reyes Giraldo on Medium</title>
            <link>https://medium.com/@jacielrg?source=rss-3a58eea96d53------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 20:39:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jacielrg/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[Adding a feature to Slack: Automatic Replies]]></title>
            <link>https://medium.com/@jacielrg/adding-a-feature-to-slack-automatic-replies-3d6be56bd8f3?source=rss-3a58eea96d53------2</link>
            <guid isPermaLink="false">https://medium.com/p/3d6be56bd8f3</guid>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[visual-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[uxui-design]]></category>
            <dc:creator><![CDATA[Jaciel Reyes Giraldo]]></dc:creator>
            <pubDate>Tue, 11 Jun 2019 19:00:10 GMT</pubDate>
            <atom:updated>2023-09-20T12:37:50.453Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JgzaTQec5arKYIviwPVRaA.png" /></figure><h4>An exercise on understanding and improving a product.</h4><h3>Background</h3><p>Slack is a very popular set of cloud based team collaboration tools. It offers powerful features in a well designed, easy to use interface that enable teams to communicate and work not only efficiently, but also more pleasantly. The app integration capabilities inside Slack allow users to extend the platform’s functionality greatly, but even then the current mobile app lacks certain basic features that would make it an even more powerful tool. One of such features is automatic replies.</p><h3>The problem</h3><p>In our now “always connected” world where the rhythm of life is vertiginous and everyone carries a smartphone in their pocket, a workplace focused tool like Slack can become overwhelming, overloading users with work related notifications 24/7 and ultimately breaking the necessary balance between work and leisure. Even turning off notifications during certain hours or setting your status to “do not disturb” may not be enough, as direct messages and mentions often bypass notification settings. It’s human nature to feel compelled to respond when addressed to, and feeling your phone vibrate or watching notifications pile up on your screen is very stressful.</p><h3>The objective</h3><p>The objective of this project is to give Slack users a little peace of mind. By allowing them to set automatic smart responses for those moments when they are unable or unwilling to reply, they can mitigate that creeping feeling of ignoring someone who’s trying to get in touch with them. And on the other side, users trying to reach someone who’s not available can get better information that allows them to manage their expectations on when or how can they contact that person.</p><h3>Research</h3><h4>1. The competition</h4><p>Slack’s main competitors in the market offer very similar features in terms of communicating availability. They all allow to set the user status to basic options such as “in a meeting” or “do not disturb”, sometimes tied to a specific timer, and a few even allow users to set a custom status with a user defined text string. Additionally, all platforms can extend their functionality via app integrations and bots, but none of them allow users to set automatic replies in their mobile apps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3xSqBBs20hmjnW-uJiXl5w.png" /></figure><h4>2. The users</h4><p>To better understand the problem and gain insights into the users needs and expectations for a feature such as “automatic replies”, a series of interviews were conducted. The main insights gained from the interviews were:</p><ul><li>Users want to communicate useful information on an automated reply, not just a simple “I’m not here” message.</li><li>Most users don’t care for the “Set a Status” feature in Slack. Less than half of them have ever changed their status, and they don’t even notice when someone changes it.</li><li>Automated replies are most interesting for users who work in teams that are scattered along multiple time zones.</li></ul><p>A short survey was conducted alongside the interviews. The data gathered with the survey was consistent with the interviews in subjects such as the lack of importance of the “Set a Status” feature, and showed that a higher percentage of people use Slack on iOS devices than on Android. Because of this, I decided to design the feature based on the iOS version of the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sMvZ8awwBV9WMSgtKL57wQ.png" /><figcaption>Survey results highlights</figcaption></figure><h3>Definition</h3><h4>1. Design objectives</h4><p>Based on the insights gained during the research phase I defined three main design objectives:</p><ul><li>The feature must be as simple to use as possible, allowing users to set replies quickly and easily, but must also have depth, with useful tools for power users.</li><li>Slack users can simultaneously be in several different threads or channels with discrete needs. Because of this, the feature should allow flexibility on who are their automatic replies directed to.</li><li>The “Set a Status” feature in Slack already contains some of the tools that can be very useful for automatic replies, such as a calendar based duration. For this reason, the new feature should enhance the usefulness of “Set a Status” and encourage its use.</li></ul><h4>2. Personas</h4><p>Two User Personas were defined to encompass the scope of the project. The main Persona, “Chuck, the IT guy”, covered the main design objectives, while “Amanda, the manager”, served as a waypoint to verify that the solution worked for different usage scenarios.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y9jwb4AXh4JH96tkMi_t2A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QU2e3f614-9_upy2hTAJag.png" /></figure><h4>3. User Stories</h4><p>To illustrate the usage scenarios of the feature for the Personas, I wrote a user story for each of them:</p><blockquote>Chuck is on medical leave for a week. He knows from experience that most of the service requests he gets are for small problems that can be fixed by doing simple things like restarting the computer, so he wants to give his coworkers some basic troubleshooting tips, mostly because he doesn’t want to find a big pile of service requests when he comes back.</blockquote><blockquote>Amanda has a long flight ahead of her. She’s traveling from Barcelona to Melbourne, so she’s probably going to be out of coverage for a day. She wants to point her sales reps to one of her assistant managers if they need to contact her while she’s flying.</blockquote><h4>4. User Flow</h4><p>Defining the user flow for the feature was one of the most critical parts of the process. Slack already has many powerful productivity tools that can be very useful for automatic replies, such as adding file attachments to messages, or setting a temporary status. It was important to incorporate such tools in the feature, but in a way that didn’t add unnecessary complexity or length to the user flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gcXwQ4sIQbkgkg5rtTrFgA.png" /><figcaption>Annotated User Flow</figcaption></figure><h3>Wireframing, prototyping and iteration</h3><p>After defining and simplifying the user flow I could begin designing the feature. Deciding the location of the feature inside the app was pretty straightforward, as the options menu in the Slack app already has a dedicated section for features that are closely related to automatic replies, such as “<em>Set a Status</em>” and “<em>Do Not Disturb</em>”. At first, I wanted to name the feature “<em>Replybot</em>” because it would behave similarly to the “<em>Slackbot”</em> (Slack’s configurable personal chatbot) in that it would be a kind of AI helper, but testing quickly showed that users were confused by the name, so I went back to call it simply “<em>Automatic Replies</em>”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*-G0NnHl5jFics5g-cB0baA.png" /><figcaption>Location of the feature inside the options menu</figcaption></figure><p>As for the structure of a reply, It is composed of the following tools and options:</p><ul><li><strong>Write a message</strong>: The body of the message. It will include the normal Slack message composing options such as hyperlinks, mentions, images and file attachments, etc.</li><li><strong>Set a Status</strong>: A custom Status that will be enabled as long as the reply is active.</li><li><strong>Set Duration</strong>: Defines a specific time frame during which the reply will be active.</li><li><strong>Set Channels</strong>: Defines specific channels that will receive the reply.</li><li><strong>Set People</strong>: Defines specific users that will receive the reply.</li></ul><p>The first<strong> low fidelity wireframes</strong> were focused on trying to organize all the main feature tools and options in the “reply creation” screen. The biggest challenge at this stage was to make that layout very simple, clean and uncluttered. Testing showed that the best solution would be to have a series of buttons, each of which would open a specific tool or option.</p><p>The <strong>medium fidelity prototypes</strong> were fundamental to test and refine the user flow and happy path. During testing, the first iterations showed that various options for creating replies were buried too deep inside tool pages, so users didn’t even realize they were there. This problem was particularly evident for the “Set duration” option, which was nested inside the “Set a Status” tool, where many users didn’t bother to look. To try to solve this problem, the next iterations implemented a “wizard” format that forced users to go through every step and every tool in order to create a reply. This approach was also found to be flawed during testing, because it made the reply creation process very long and tedious. The solution was to go back to an improved version of the “reply creation” screen where each tool is a button that opens in a new screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LGekyX9vL9kDuaLOzG5-bg.png" /><figcaption>Low and Medium fidelity wireframes</figcaption></figure><p>The focus of the <strong>high fidelity prototype</strong> was to understand the <em>design system</em> of the <strong>Slack iOS app</strong>, including interaction models, fonts, iconography, color palette, components, etc., and use it to seamlessly integrate the “Automatic Replies” feature into the user interface.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mt7oxKpLr2_8QhHr7DTz2Q.png" /><figcaption>Relevant elements of the Slack design system</figcaption></figure><p>A video demo of “Automatic Replies” for Slack on iOS:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fb0xybyfbq0A%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Db0xybyfbq0A&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fb0xybyfbq0A%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/830c1ece389bb477f28a26a7ab1b9aee/href">https://medium.com/media/830c1ece389bb477f28a26a7ab1b9aee/href</a></iframe><h3>Conclusions</h3><p>Overall, this project was an interesting exercise on understanding and applying an existing design system from a visual perspective, but more importantly, from an interaction and information architecture perspective. The Slack iOS app has a very particular gesture based interaction model that can seem confusing for new users but becomes very fluid and fast as you understand it. Perhaps as a consequence of said interaction model, the information architecture of the app suffers when it comes to some “secondary” elements, such as the options menu. This is particularly relevant for this project because as it turns out, the options menu is precisely the most adequate location for the automatic replies feature.</p><p>If I were to develop this project further I would probably take a deeper look into the information architecture of the entire app, and try to find a better structure for those elements that seem out of place or hard to find in their current location.</p><p><em>Thank you for reading.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nrVmeW7QKnfFfg7kiZYqnQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d6be56bd8f3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ultra Local Records — not your conventional e-commerce]]></title>
            <link>https://medium.com/@jacielrg/ultra-local-records-not-your-conventional-e-commerce-21bfaab50a54?source=rss-3a58eea96d53------2</link>
            <guid isPermaLink="false">https://medium.com/p/21bfaab50a54</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[information-architecture]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[usability-testing]]></category>
            <category><![CDATA[e-commerce-website-design]]></category>
            <dc:creator><![CDATA[Jaciel Reyes Giraldo]]></dc:creator>
            <pubDate>Sat, 04 May 2019 11:10:21 GMT</pubDate>
            <atom:updated>2019-05-04T20:50:49.026Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uXMGhjqJq0DUOvLj4fUB5g.jpeg" /></figure><h3>Ultra Local Records · not your ordinary online store ·</h3><h4>A Local e-commerce Case Study</h4><blockquote><em>“Think global, act locally”</em></blockquote><p>From this sentence, we started our second project of the Ironhack UX/UI Bootcamp. We were asked to design an e-commerce website for a local business, the kind of place that can be affected negatively by the growing trend of online shopping.</p><ul><li><strong>Group: </strong><a href="https://medium.com/u/717008794d93">David Cruz Fuentes</a>, <a href="https://medium.com/u/e6be6d45ca7e">Chiara Dapor</a> and <a href="https://medium.com/u/3a58eea96d53">Jaciel Reyes Giraldo</a>.</li><li><strong>Timing: </strong>3 weeks.</li><li><strong>Goal: </strong>To design an e-commerce for a local store, in order to improve their online presence to be more competitive in the market.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*okof7salTOCPtKC4u1OJRg.jpeg" /></figure><p>We were very lucky to be able to work with “<strong><em>Ultra Local Records</em></strong>”, a very unique record store born 6 years ago, a product of the passion for music of its founders Carme and Raul, with the simple goal of <em>promoting local music</em>.</p><p><em>Ultra Local Records </em>is not only a vinyl shop, it’s a magical, immersive world made up of music lovers and friendship. Is the to-go meeting point for the music lovers of Poblenou and, in general, for those who feel a passion for local music. The most prominent spots in the store are reserved for local artists, of which you can find a lot of albums in vinyl, CD and cassette format. <em>Ultra Local Records </em>also has a radio program hosted by Carme and Raul called<a href="https://youtu.be/FT7C1SxSvJE"><strong><em>Hip Hip Ultra</em></strong></a>, and live performances in-store almost every weekend, mainly of local bands. On top of that, <em>Ultra Local Records</em>has its own music festival every year: <em>Microclima Sound!</em></p><p>There is a strong community of people around <em>Ultra Local Records</em>. They call themselves “<strong>la parroquia</strong>” (the parish), and they are a group of music lovers, friends of the owners, friends of the shop, and members and fans of local musicians. All of them have a strong emotional connection, as well as feelings of admiration and respect <em>Ultra Local Records</em>, it’s owners and their passion. They define the store as “<strong>THE temple of local music</strong>”, and they always buy all their vinyls there to support it.</p><p>We talked with Carme, who’s 50% of the soul of <em>Ultra Local Records</em>. She is a very easygoing and passionate person who conveyed the essence of <em>Ultra Local </em>to us in a very natural way. It’s been 6 years since Raul and her opened the store and nothing about it has changed, except the fact that they unconsciously created, little by little, a network of contacts between bands, labels and clients which became the engine of their activity. In fact, Carme defines her shop as an “<strong>oracle</strong>”, <em>a perpetually open door where a lot of people comes asking for advice, to play music, drink a beer or simply to hang out</em>. This is the most important thing about <em>Ultra Local Records</em>for her, way more important than revenue. This philosophy is clearly reflected on the business goals of <em>Ultra Local Records</em>, which in Carme’s own words are:</p><blockquote><strong><em>“No cerrar y que al menos uno de los dos pueda dejar su trabajo para dedicarlo a la tienda / Not close and that at least one of the two can leave their work to dedicate entirely to the store”.</em></strong></blockquote><p>What <em>Ultra Local Records </em>is for Carme:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9P99JLgHTyrOzq_q" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kY31ip--oUC1dqUf" /></figure><p><em>Ultra Local Records</em>has a very fragmented online presence; they use<a href="https://www.facebook.com/Ultra-Local-Records-270410556408977/">Facebook </a>,<a href="https://www.instagram.com/ultralocalrecords/?hl=es">Instagram</a>and<a href="https://twitter.com/ultralocalrec">Twitter</a>to promote upcoming events (they design their own flyers) and new product arrivals. They also have a<a href="http://ultralocalrecords.blogspot.com/">website</a>with barebones (and sometimes outdated) information, and a profile in the<a href="https://www.discogs.com/seller/ultralocal/profile">Discogs</a>platform, which they use to sell online.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zCj1UTSHV0BITwTx" /></figure><p>Online sales are a lot lower than those of the physical store, and the owners don’t seem interested in (or don’t know how to) enhance their online store to increase their sales volume.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fHWBn48Mu34Dju5v" /></figure><p>To understand the business needs of <em>Ultra Local Records,</em>we identified some competitors that aim at the same target audience (in terms of buying online). They are mainly vinyl shops, and each of them has interesting features that we will consider for our e-commerce.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3kTCeV9v6yOt9ZrwVvxiPA.png" /></figure><p>The most significative one is the <strong>Market Positioning Map</strong>, that shows the current position of <em>Ultra Local Records</em>in the orange circle (strongly focused on local artists, with a lot of emphasis on their values even to the detriment of sales) and where we want to move it with our project (more open to international artists without losing their focus on the locals, more balance between their values and sales growth).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*em-4v8rrIZ_Rbua4" /></figure><blockquote><em>Create a consolidated online presence that transmits the values of Ultra Local Records, enables economic growth and fulfills their mission of promoting local music.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Stm90C3kHmp_AglX" /></figure><p>After our analysis and some interviews, we created two different Users Personas that represents the main users of our website:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*tQe7bq-5_refr8--" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*yrG5_VKc6316GE5H" /></figure><h3>INFORMATION ARCHITECTURE</h3><p>To define the information architecture of the website, we did two card sorting experiments:</p><ul><li><strong>On the first experiment</strong>we focused on defining the <strong>general structure</strong>of the website’s features and main sections. As a result we settled on <strong>four main sections</strong>: <strong>Shop</strong>, <strong>Video</strong>, <strong>Events</strong>, <strong>Artists</strong>.</li><li><strong>The second experiment</strong>was focused on the <strong>online store structure</strong>. Product categories, filters for music based on genre, artist, label, etc. The sheer amount of keywords and filtering options turned out to be overwhelming, overly complicated for most users, and ultimately unnecessary given the scope of Ultra Local, so we decided to refocus and do a third experiment.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dhzmGxHleawiQyx0DzVjAw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BJHJ4O8UgztGcwkA0cXSbw.jpeg" /></figure><ul><li><strong>The third experiment</strong>’s objective was <strong>simplification</strong>. We did a quick round of guerrilla interviews to understand people’s behavior when they search for music online, particularly on streaming services, and apply the insights obtained on the filtering system of the store. and based on our findings we were able to reduce the amount of categories and filtering options for the experiment. The result was a unified storefront where all of the products would be presented, and a simplified filtering system with only <strong>five groups</strong>: <strong>Category</strong>(Music, Books, Merchandising), <strong>Format</strong>(Vinyl, CD, Cassette), Genre (sorted by popularity), <strong>Artist</strong>(A-Z), <strong>Year</strong>(by decade, most recent first</li></ul><p>With the information architecture defined, we were able to move on and create the site’s map:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*81fraT_bX1x08F_x" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7RCyx-SO1inka83H" /></figure><p>We created two different user flows based on our user personas:</p><p><strong>Task 1/Jordi: Shopping. </strong>Jordi wants to buy a birthday present for his friend who’s super into classic rock, so he goes into the shop to search for the perfect vinyl:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uX4i2wxq4IZnlAPi" /></figure><p><strong>Task 2/ Monste: Events and Social. </strong>Montse has a friend coming over to visit for the weekend, and she wants to take her to a concert at her favorite place: <em>Ultra Local Records</em>. She goes to the website to find out if there’s a concert coming up next weekend:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iNydQ8KyYMUq1w42KzEHDQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2PBlD0TknVBh30j5" /></figure><p><strong>A.</strong>The user wants to buy a birthday present for a friend who’s super into classic rock. He goes into the shop to search for the perfect vinyl.</p><p><strong>B.</strong>The user has a friend coming over to visit for the weekend, and she wants to take her to a concert at her favorite place: Ultra Local Records. She goes to the website to find out if there’s a concert coming up next weekend.</p><p><strong>C</strong>. The user went to a concert at Ultra Local and loved the band but can’t remember their name. The user visits the website to find the band’s name in the event post, and discovers the band’s profile in Ultra Local’s database, including their albums available to buy in the shop</p><p><strong>D</strong>. The user has a band and a friend recommends Ultra Local Records to sell their album because they accept everybody on the store. The user visits the website to create an artist profile and contact with Ultra Local Records to sell the album.</p><p><strong>E</strong>. The User wants to watch videos of some awesome concerts she went to at Ultra Local. On the website she discovers that they also have video of their radio show, “Hip Hip Ultra”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WoZNLp4SzpYFdino6naHOg.jpeg" /></figure><p>We started the wireframing process by proposing layouts for the homepage. Our first proposals were pretty standard, inspired on very popular online stores with similar products, such as Fnac, Amazon, and Discos Paradiso. The proposals were adequate in terms of layout and usability, but we felt that they didn’t capture the unique spirit and vibe of Ultra Local, so we discarded them and went for more bold, unconventional layouts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mcjNGRuKv-MLIAPO2BB0Bg.jpeg" /><figcaption>Initial layout proposals. Functional, but they don’t feel like Ultra Local!</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o_CRjUO8G3I6_l7rP9zJlg.jpeg" /><figcaption>More audacious layout proposals. That’s more like it!</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D_aNOQnZrNYiZdIAIzoJEA.jpeg" /></figure><p><strong>1. HEURISTICS</strong></p><ol><li>The first layout proposals were based on an interaction through pop-ups to access the different contents of the website and did not maintain a consistency and generated rigidity in the information architecture.</li><li>Did not meet 3 and 4 of the Heuristics “the 10 usability principles of Jakob Nielsen”</li></ol><p><strong>2.USABILITY</strong></p><ol><li><strong>The search button</strong>was isolated from the rest of the navigation elements and users could not find it.</li><li>Solution: <strong>Put the search button inside the shop</strong>in the upper right corner.</li><li><strong>The submenu</strong>of the store that appeared on the left was an interaction different from the rest of the interactions on the web and generated visual noise.</li><li>Solution:<strong>Remove the submenu</strong>and enter the subcategories of the products inside the store selection filters.</li><li>Users forget to select <strong>the format filter</strong>when they are looking for music inside the store.</li><li>Solution: On the product page add the <strong>mandatory format selection</strong>option.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PT9ZS5xL_-wVxw-ljXwvFg.jpeg" /></figure><p>After solving the problems found in the usability tests, we created a mid fidelity prototype to test the layouts, interactions and user flows of the two specific tasks we defined for our Personas:</p><p><a href="https://projects.invisionapp.com/share/PRRQWZJKMFU#/screens">Click here to view the project `ULTRA LOCAL RECORDS - shopping user flow`</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zKJsB8AZd9lUr5f-lY8DCQ.jpeg" /></figure><p>Finally, we created a first approach at how the finished website would look like, in this case the homepage:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GRPNJc_CCAeJr2Vb93sd7Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SMKKUj7k0KtoEPuy" /></figure><ul><li>Throughout the project, and specially during the testing phases, we learned a lot of important aspects of information architecture and usability. Ideas that seemed great to us turned out to be totally inadequate from the users perspective, and the final product looks nothing like what we had imagined when we started drawing the first low fidelity wireframes.</li><li>But of course this project is far from over. There’s still a lot of work that needs to be done before we can say the Ultra Local website is finished, and the most important ones are:</li><li>Create user flows for all sections of the website.</li><li>Continue testing the mid-fidelity wireframes.</li><li>Create wireframes for all screens in every format (desktop, tablet, smartphone).</li><li>Continue testing and refining the design of the filters bar in the shop.</li><li>Continue the Development of Wireframes in High Fidelity.</li></ul><p>… and of course bring our project to <em>Ultra Local Records</em>and present it to <strong><em>Carme </em></strong>and<strong><em>Raul</em></strong>!</p><p>We hope you liked our project, and don’t forget: see you at <em>Ultra Local Records </em>next Saturday at 01:00 pm for a concert, or on the 30th of May for the <strong><em>Microclima Sound Festival</em></strong>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21bfaab50a54" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Usability case study and redesign]]></title>
            <link>https://medium.com/@jacielrg/usability-case-study-and-redesign-ce54858a170d?source=rss-3a58eea96d53------2</link>
            <guid isPermaLink="false">https://medium.com/p/ce54858a170d</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[usability]]></category>
            <dc:creator><![CDATA[Jaciel Reyes Giraldo]]></dc:creator>
            <pubDate>Sun, 17 Mar 2019 18:45:57 GMT</pubDate>
            <atom:updated>2019-03-17T18:45:57.588Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/887/1*8EZEURwPelCmIiMTx1-OSA.png" /></figure><h3>About Virginia Tech</h3><p>Virginia Tech (VT) is a technology oriented university located in Blacksburg, Virginia. It has around 35000 students, and it ranks 46th for university research in the United States. It offers 110 bachelor’s degree programs and 170 master’s and doctoral degree programs, and it has facilities not only in the US but around the world.</p><p>The university motto, <em>Ut Prosim</em> (That I May Serve), represents the vision that the “Hokies” (members of the VT family) are agents of change in the world, pushing the boundaries of knowledge in order to make a difference in the world.</p><h3>Problems found</h3><p>During the interviews, the main issues raised by the users were:</p><ul><li>Navigation is confusing, some important sections such as the list of available courses were not clearly named or easy to find. None of the interviewed were able to find if the school offers Arabic language courses.</li><li>The color palette is very sober and “old”.</li><li>Some sections eliminate the navigation menus completely, forcing you to go back using the browser’s back button. The merchandise store is particularly problematic for the navigation, as it’s a completely separate website that takes you out of the university website and has a totally different navigation design.</li></ul><h3>The problem to solve</h3><p>The most important problem that I identified during the interviews is the difficulty to find a clear and comprehensive list of available courses. This is a very important feature for prospective students trying to decide if it’s the right school for them.</p><h3>The solution</h3><p>Add a “Courses” button in the main navigation bar. The button will open a comprehensive list of all the courses available in the School, and a powerful system of filters to help visitors find the courses they are interested in.</p><p>The filters system will work using tags or keywords that the user can stack to narrow down his/her search. The tags will not be rigid. This means there will not be a long list of pre-established tags. Instead, the user will be able to write any relevant keyword or term into a text field and add it as a tag by hitting the add button (or the return key on a keyboard). The system must be smart, as in it has to be able to recognize the user defined tags and filter the courses list accordingly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DLY2PQmrHLuAPHrdHT4WUg.png" /></figure><h3>Lessons learned</h3><ul><li>Even big technology universities can have serious usability issues on their websites.</li><li>College and university structures vary greatly depending on the country or culture. What might seem intuitive for an american student in terms of usability for the college website can be very hard to understand for an european person trying to navigate the same website.</li><li>The usability differences between desktop and mobile websites is very noticeable, and it is very important to address it in order to find a balance between “display real state” and functionality. In this sense, the popularity of mobile browsing is having a negative effect on the navigation of desktop websites, which could have a lot more options due to their format.</li><li>Curious fact: University mascots are not necessarily well defined characters. They can be just loosely defined random animals represented differently in different events, media, etc.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce54858a170d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wireframing challenge]]></title>
            <link>https://medium.com/@jacielrg/wireframing-challenge-1c70984b500a?source=rss-3a58eea96d53------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c70984b500a</guid>
            <category><![CDATA[wireframing]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Jaciel Reyes Giraldo]]></dc:creator>
            <pubDate>Sun, 17 Mar 2019 17:04:05 GMT</pubDate>
            <atom:updated>2019-03-18T11:52:30.731Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jusOy8zx90evXRSUzEaCSw.png" /></figure><h3>Insights</h3><ul><li>Reverse engineering an interface helps you understand a lot of the usability decisions of the original designers</li><li>Wireframing is very useful to identify unnecessary elements in the interface, as well as to evaluate the importance of certain features.</li><li>The lack of colors/graphics is a way to help you focus on the navigation and flow of the app instead of the aesthetics.</li><li>Because of the way sketch works, it doesn’t seem clear to me that wireframing is a lot faster than hi-res visual design.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c70984b500a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Visual design exercise]]></title>
            <link>https://medium.com/@jacielrg/visual-design-exercise-4f554960a310?source=rss-3a58eea96d53------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f554960a310</guid>
            <category><![CDATA[sketch]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[visual-design]]></category>
            <dc:creator><![CDATA[Jaciel Reyes Giraldo]]></dc:creator>
            <pubDate>Sun, 17 Mar 2019 16:53:03 GMT</pubDate>
            <atom:updated>2019-03-17T16:55:38.573Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VmH1QWi-dXJX3oRIwTWVLA.png" /></figure><h3>Insights</h3><ul><li>Using Sketch can be confusing for experienced users of Adobe software, because many features/functionalities work similarly, while others work very differently.</li><li>Sketch is very straightforward and easy to use.</li><li>The compatibility of Sketch with “industry standard” applications such as Photoshop and Illustrator is very bad, even when exporting files as PDF.</li><li>It is very important to keep layers and objects organized when you work, as the layers, panel can become very confusing to use if you are not organized.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f554960a310" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design thinking excerise]]></title>
            <link>https://medium.com/@jacielrg/design-thinking-excerise-f3283bd01b04?source=rss-3a58eea96d53------2</link>
            <guid isPermaLink="false">https://medium.com/p/f3283bd01b04</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Jaciel Reyes Giraldo]]></dc:creator>
            <pubDate>Sun, 17 Mar 2019 16:39:38 GMT</pubDate>
            <atom:updated>2019-03-17T16:39:38.458Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>About the company and the project</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/379/1*AMl_n8dE7805-fYP_u1I9w.png" /></figure><p>Whole Bank started operations in Framingham, a small town in Massachusetts, United States. Their goal was to offer a different way to save and manage money by giving customers innovative options such as virtual currencies. Carol Holmes is currently in charge of the Innovation Department of Whole Bank.</p><p>The objective of the project is to provide a way for traveling customers to pay for products and services using their phones instead of physical cards during their trips. The solution must be integrated into Whole Bank’s mobile app.</p><h3><strong>Problems found</strong></h3><p>The most recurring problems I identified during the interviews were the following:</p><ul><li>People are unsure if paying with their phones is reliable.</li><li>Mobile banking apps can be confusing and difficult to use for many people because of the large amount of functionalities that they include.</li><li>Many users don’t understand how mobile payment works.</li><li>Mobile payment functionality is often offered as a stand-alone app, separate from the main mobile banking app.</li><li>Young people are more open to adopt mobile payment and leave their physical cards at home.</li></ul><h3>The problem to solve</h3><p>A lot of people, specially seniors, and even if they feel comfortable using smartphones, are reticent to adopt mobile payment systems because of difficulty to use, perceived lack of safety/reliability, and often because they simply don’t know it’s an option.</p><h3>The solution</h3><p>The idea is to create a mobile payment solution that is easy to use, fast to access, information rich, and reliable.</p><p>The main elements of the solution are:</p><ul><li>A redesigned home screen on Whole Bank’s mobile app with four clear, easy to access “areas”: 1.Online banking, <strong>2.Mobile Pay</strong> (the solution), 3.Find physical offices, 4.Correspondence.</li><li>A very visual, simple to use <strong>Mobile Pay</strong> interface that uses the card’s pin number or the phone’s biometric scanner (if available) as a security measure to authorize payments.</li><li>Comprehensive information on the cards usage, so the users can keep track of their expenses and feel confident about the <strong>Mobile Pay</strong>.</li><li>Powerful control settings for the cards inside <strong>Mobile Pay</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*afbpDIcos1j8XRjUmhcobQ.png" /><figcaption>Paper prototype for <strong>Mobile Pay</strong></figcaption></figure><h3>Lessons learned</h3><ul><li>People are very cautious when adopting new technologies when it has something to do with their money.</li><li>Mobile banking apps in general need to improve A LOT.</li><li>Mobile payment systems have a lot of untapped potential.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f3283bd01b04" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Visual note-taking exercise]]></title>
            <link>https://medium.com/@jacielrg/visual-note-taking-exercise-784310e712de?source=rss-3a58eea96d53------2</link>
            <guid isPermaLink="false">https://medium.com/p/784310e712de</guid>
            <category><![CDATA[visual-note-taking]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Jaciel Reyes Giraldo]]></dc:creator>
            <pubDate>Sun, 17 Mar 2019 15:33:47 GMT</pubDate>
            <atom:updated>2019-03-17T15:36:29.607Z</atom:updated>
            <content:encoded><![CDATA[<h3>Visual note-taking</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rBPbR5F0ZSzRDN2plQzTag.png" /></figure><p>Taking notes in a visual way felt very natural for me. It helped me comprehend the information that was being transmitted in a more broad manner, and it allowed me to connect the different ideas exposed in the video to create a comprehensive mental image of the implications of small design changes to digital design elements that are used by millions of people on a global scale.</p><p>It also made the video more engaging, as re-watching it while going over the notes allowed me to add “layers” of important information that went unnoticed on my first watch, but stood out very vividly on successive replays.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=784310e712de" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>