<?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 Carlos Duque on Medium]]></title>
        <description><![CDATA[Stories by Carlos Duque on Medium]]></description>
        <link>https://medium.com/@carlosaduque93?source=rss-153e7d23e88e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*RyCXya7pDb3KUIP9RI3Rsg.jpeg</url>
            <title>Stories by Carlos Duque on Medium</title>
            <link>https://medium.com/@carlosaduque93?source=rss-153e7d23e88e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:44:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@carlosaduque93/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[Case Study: Optimizing Player Gameplay]]></title>
            <link>https://carlosaduque93.medium.com/case-study-optimizing-player-gameplay-14b6b41b8b84?source=rss-153e7d23e88e------2</link>
            <guid isPermaLink="false">https://medium.com/p/14b6b41b8b84</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Carlos Duque]]></dc:creator>
            <pubDate>Fri, 07 Jan 2022 12:55:37 GMT</pubDate>
            <atom:updated>2022-01-07T12:55:37.149Z</atom:updated>
            <content:encoded><![CDATA[<p>Have you ever gone home ready to play video games to relieve some stress, just to find out that equipping gear from your inventory is like working? Going through youtube, Reddit, and other social media platforms to find what gear works best for your character can feel like a second job. It is very tedious.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B301sDMnx7QOlAHjBABMOQ.jpeg" /></figure><p><strong>Overview</strong></p><p>Role: UX Designer<br>Goals: The goal is to help destiny players equip the right gear for their missions.<br>Deliverables: User Research, Affinity Mapping, User Flows, Hypothesis, User Scenario, Usability Testing, Lo-Fi Wireframe MockUps</p><p>Ishtar Commander is an app that allows players that play the game Destiny to view their in-game inventory, achievements, missions, etc, and transfer it to the actual game itself. I’ve reached out via Reddit, discord, and other gaming community platforms to ask a couple of questions to gamers that play Destiny. Every gamer thrives differently when playing this game, making their experience with Ishtar Commander different from each other.</p><p>After talking to gamers, I have been able to grab a few insights into their experience with the current app. It has led me to find out that there are similar apps that function the same and are compatible with Destiny as well. I asked about various things about Ishtar Commander and the other apps, such as managing inventory, achievements, missions, etc. I’ve come to realize that finding out what gear/weapon is a struggle in the Destiny community. Ishtar Commander does not have a suggestion for a recommendation section in their app that will enhance their equipment for their in-game objective.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4BNaRqSVzn5miebqkH0p4g.jpeg" /></figure><p>Looking through similar games, the inventory was so much alike that I could not find any inspiration. I then ventured off to play different games and came across a particular game that has a very similar feature and that is LOL (League of Legends). Every time you want to upgrade or purchase equipment in LOL, the gear itself states what it is good against/with. It could be good to defeat a particular enemy or state that this gear further enhances another gear you may have equipped.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4tSYJHMtKKd1lk06UcpGBw.jpeg" /></figure><p><strong>Customer Problem</strong>:</p><p>Destiny players either ignore or take a very long time on their inventory because there are no suggestions on what gear/weapon is best suited for their objective. Players want to be able to equip the best gear/weapon in order to dominate the game without having to think about it.</p><blockquote>We believe that adding a recommendation section on the gear of choice will result in optimizing gear efficiently because better enhanced gear will help dominate the initial in-game objective.</blockquote><p><strong>User Scenario #1</strong>:</p><p>User comes home from a long day of work expecting to relax by playing their favorite game Destiny. They turn on the game to complete the next objective. The first thing the user opens is the inventory to optimize gear in the Ishtar Commander app. The character has a lot of gear and the user is not sure which one to equip. User doesn’t want to waste time trying to figure out what is the best gear, so they move on to the in-game objective. Their character keeps dying due to a lack of power in gear. User is now frustrated that they should’ve spent the time optimizing their gear.</p><p><strong>User Scenario #2</strong>:</p><p>User comes home from a long day of work expecting to relax by playing their favorite game Destiny. They turn on the game to complete the next objective. The first thing the user opens is the inventory to optimize gear in the Ishtar Commander app. The character has a lot of gear and the user is not sure which one to equip. The user starts going through social media platforms, youtube, etc to find the best gear for the next objective. After spending an hour or so researching, the user only has a few mins to play and relax.</p><p>Below I have cogitated a user flow that would demonstrate how to reach from the login page to the gear manager with suggested recommendations. All that was added was the suggested recommendations. I did move a few pages around because they were repetitive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o2djNR3HjFnxebANjobM6Q.jpeg" /></figure><p>I tested out a couple of wireframes to see how Destiny players would be able to optimize their gear efficiently. In the first set of wireframes, users took a bit of time trying to find out where the recommendation section was. Users, 1–3 gave up trying to find it because it required a bit of effort to search for the section implemented. Users 4 &amp; 5 were determined to use the new feature even though it took a bit of time to find.</p><p>The wireframes were not as successful as I hoped for. Thinking back, users struggled to look for the extra page, which led me to think of a potential solution. I removed the extra step and placed the recommendation feature on the same page as the gear. This way players are able to reference quickly which gear would be best for their in-game objective.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*vrrqCtMPDuxmWN_8yyVftQ.png" /></figure><p>I then asked the same users to test the new set of wireframes again. This time, users were able to optimize their gear efficiently when the suggested section was right below the weapon perks section.</p><p>After much usability testing, I made a low-fidelity and mid-fidelity prototype of M.V.E. Here are is a concept of what the final page would be like.</p><p>In conclusion, gaming can suck if you don’t have the right gear. Destiny players want to be able to optimize their gear efficiently to help dominate their in-game objective. It was trial and error to discover what would be the best option for players to enhance their gear. I don’t expect users to use this feature every time but it will definitely help for the many that are not sure what to equip on their character.</p><p>As a designer, my work isn’t done. The next steps would be to continue to gain user feedback on the product and reflect their thoughts in new iterations.</p><p><strong>Contact Me:</strong></p><p>If you like my thought process and would like to collaborate, contact me at caduque0906@gmail.com</p><p>LinkedIn: <a href="https://www.linkedin.com/in/caduque0906/">https://www.linkedin.com/in/caduque0906/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14b6b41b8b84" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Solving User Experience Problems For Opticians]]></title>
            <link>https://medium.com/design-bootcamp/solving-user-experience-problems-for-opticians-dd2c7f1fbe9?source=rss-153e7d23e88e------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd2c7f1fbe9</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Carlos Duque]]></dc:creator>
            <pubDate>Tue, 23 Mar 2021 13:22:55 GMT</pubDate>
            <atom:updated>2021-03-31T06:25:19.520Z</atom:updated>
            <content:encoded><![CDATA[<h3>Case Study: Solving user experience problems for opticians</h3><figure><img alt="Optician calculating insurance with pen and paper" src="https://cdn-images-1.medium.com/max/1024/1*LwRic5M_dmmL-JI7G3KfsA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@homajob?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Scott Graham</a> on <a href="https://medium.com/s/photos/insurance-calculations?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p><strong>Overview</strong><br>Role: UX Designer<br>Team: Lead Designer<br>Goals: The goal of this project is to make the application of insurance discounts simple for opticians.</p><p>Opticians are technicians trained to design, verify and fit eyeglass lenses and frames, contact lenses, and other devices to correct eyesight. Most opticals use a program called M.V.E. (My Vision Express) to enter patient information, schedule appointments, create lab orders, medical billing, etc.</p><p>To understand what issues opticians were dealing with, I’ve asked a few opticians to navigate me through M.V.E. With the permission of both the opticians and clients, I also watched a live sale and navigation of M.V.E.</p><figure><img alt="Optician using MVE" src="https://cdn-images-1.medium.com/max/984/1*zjYSXXF7O5AJe-IY8dh47Q.jpeg" /></figure><p>At first glance, M.V.E was overwhelming. The call to action buttons was small, confusing, and disarray. Opticians were quick to create an order and make a sale to get to the next client. Most clients were returning clients with either a balance or credit in their file.</p><p>One optician stated, “Clients either have balances or credits because we either over or undercharge them through the insurance.”<br>Another optician mentioned, “Calculating the insurance discount is easy by hand, but when applying it on M.V.E., it’s confusing where to input the discount. Sometimes it comes out to a different amount than what we calculated on hand.”</p><p>After a couple of questions on M.V.E. opticians have shown frustration towards the insurance discount section. When reviewing the clients’ insurance, the insurance will state what kinds of discounts can go towards the eyewear. Allocating insurance discounts become confusing and always a different amount from using pen and paper.</p><figure><img alt="Affinity Mapping research on MVE" src="https://cdn-images-1.medium.com/max/1024/1*CCLkVOyKCxamPNi0KjODBw.jpeg" /></figure><p><strong>User Problem:</strong></p><p>Users need to allocate clients’ insurance discounts accurately and quickly.</p><blockquote>We believe that restructuring the insurance allocation section will result in efficient and accurate discounts because allocating the insurance can be confusing and come out to a different amount when done on pen and paper.</blockquote><p><strong>User Scenario:</strong></p><p>A client walks into an optical ready to purchase eyewear with their vision insurance. The optician asks all sorts of questions to recommend the best possible eyewear needs. The optician opens MVE on his laptop to start allocating the insurance discounts. After allocating the insurance, the optician collects payments and submits to the insurance. The insurance replies a few days later, just for the optician to find out that they under or overcharged the client.</p><p><strong>User Flow:</strong></p><p>I started the ideating process by creating a user flow to visualize how to reach the insurance discount section. MVE User flow Control has a lot of repetitive sections that were combined in the variant.</p><figure><img alt="Control and variant flow chart of MVE" src="https://cdn-images-1.medium.com/max/1024/1*ziCrz4alqT9AMpAuZ1-ocw.jpeg" /></figure><p><strong>Wireframe:</strong></p><p>I began the next step to solving this problem. I created wireframes that would best suit the opticians. Providing a client’s insurance benefits, I’ve asked 5 users to discount the client’s eyewear purchase with the wireframes.</p><p>While all users were able to allocate the insurance discount accurately, users took a very long time to complete the task. To minimize the amount of time taken to allocate insurance discounts, I compared how insurance benefits were structured. I modified the wireframes to be similar to clients’ insurance benefits. Users were then able to allocate to complete their tasks quickly and accurately.</p><figure><img alt="MVE wireframe for usability testing" src="https://cdn-images-1.medium.com/max/1024/1*uqWtQPXUYUBymV0wkbmORg.png" /></figure><p>After much usability testing, I made a low-fidelity and mid-fidelity prototype of M.V.E. Below is the before and after of what the final prototype would be.</p><figure><img alt="Before &amp; After MVE Order Form" src="https://cdn-images-1.medium.com/max/1024/1*WmlG65jjkSIdCAsdnRF4Zg.png" /></figure><figure><img alt="Before and After Insurance Allocation Form" src="https://cdn-images-1.medium.com/max/1024/1*XKmt9ybY4uGnhTqIVmzyQg.png" /></figure><p>In conclusion, there were many buttons and inputs cluttered together that confused users to allocate insurance properly. Restructuring the insurance allocation section resulted in efficient and accurate discounts because allocating the insurance can be confusing and come out to a different amount when done on pen and paper.</p><p>Although my work isn’t done yet, the next steps would be to continue to gain user feedback on the product and reflect their thoughts in new iterations.</p><p><strong>Final Prototype:</strong></p><p>Check out the final prototype!</p><p><a href="https://xd.adobe.com/view/6b2b6a5f-f3de-41e1-9d71-3071d276d2b3-3e78/?fullscreen">https://xd.adobe.com/view/6b2b6a5f-f3de-41e1-9d71-3071d276d2b3-3e78/?fullscreen</a></p><p><strong>Contact Me:</strong></p><p>If you like my thought process and would like to collaborate, contact me at caduque0906@gmail.com</p><p>LinkedIn: <a href="https://www.linkedin.com/in/caduque0906/">https://www.linkedin.com/in/caduque0906/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd2c7f1fbe9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/solving-user-experience-problems-for-opticians-dd2c7f1fbe9">Solving User Experience Problems For Opticians</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MTA Commuter Pain Points]]></title>
            <link>https://carlosaduque93.medium.com/mta-commuter-pain-points-609be7222873?source=rss-153e7d23e88e------2</link>
            <guid isPermaLink="false">https://medium.com/p/609be7222873</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-writing]]></category>
            <dc:creator><![CDATA[Carlos Duque]]></dc:creator>
            <pubDate>Wed, 10 Mar 2021 00:18:40 GMT</pubDate>
            <atom:updated>2021-03-16T13:28:34.261Z</atom:updated>
            <content:encoded><![CDATA[<p>Have you ever swiped your MetroCard at a train station just to find that it has insufficient balance? Then you find out the Kiosk is only accepting coins? Using the MTA Kiosk is the only form of payment for our Metrocards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HD7zfY94mMlcN0PBcwcR1A.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@asaelamaury?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Asael Peña</a> on <a href="https://unsplash.com/s/photos/mta?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p><strong>Overview</strong></p><p>Role: Lead UX Designer<br>Goals: The goal is to decrease wait time in entering the train station.<br>Deliverables: User Research, Affinity Mapping, User Flows, Hypothesis, User Scenario, Usability Testing, Lo-Fi Wireframe MockUps</p><p>The MTA (Metropolitan Transit Authority) has many problems in all areas from the train itself to their app. With a couple of questions based on commuters’ experience with the MTA, the MY MTA app, and a description of their daily commute, I was given much insight into what an issue at the MTA is. I created an affinity map to help me organize the information gathered from the interviews performed. Commuters expressed their thoughts on train delays and their experience with the MTA kiosk.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EtUuKDO6CHJ6VI9zD4ZBqg.png" /></figure><p>This led me to research a few companies that are very similar to the field of transportation such as Uber, Citi Bike, and ZipCar. I looked for specific features such as a method of transportation and a method of payment. These companies provide a traveling service by either bike or vehicle and use either a digital wallet or a more efficient kiosk. After much research, I discovered that the MTA does not have a form of online payment to refill their MetroCards as their competitors do.</p><p><strong>Customer Problem:</strong></p><p>Commuters are late catching their trains because of the inefficiencies of the MTA kiosk. They need to be able to refill their MetroCard and get to their destination without problems or delays. Users want to be able to refill their MetroCards online using their credit cards.</p><blockquote>We believe adding a digital wallet will result in a more efficient way to refill MetroCards because kiosks are inefficient, frequently under maintenance and the lines are long.</blockquote><p><strong>User Scenario:</strong></p><p>A commuter rushed to the train station and swiped his MetroCard at the turnstile. The turnstile states the commuter has an insufficient balance. The commuter had to refill their MetroCard at the kiosk. There was a line at the kiosk and it was only accepting coins at the time. The commuter couldn’t afford to be late to work, so they spent $30 on a Lyft instead of spending $2.75 for a 15-minute train ride.</p><p><strong>User Flow:</strong></p><p>I started the ideating process by creating a user flow to audit and visualize the number of steps upon logging in to the behavior of refilling MetroCards. After the user flow audit, I mocked up potential flows that address the hypothesis by minimizing the number of steps required to accomplish the user goal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sCOYZt-MYgkSFMgJxIkjew.jpeg" /></figure><p><strong>Usability Testing:</strong></p><p>I tested a couple of wireframes to see if users would be able to refill their MetroCard efficiently. To determine efficiency, I timed every user how long they took to reach the end goal.</p><p>Users 1- 4 were asked to rush to refill their MetroCards as if they were running late to work. This set of users showed frustration towards the mocked-up wireframes, averaging around 10 to 25 seconds to refill their MetroCards.</p><p>User 2: “Why are there so many buttons?!”</p><p>Users 5–8 were asked to take their time refilling their MetroCards. These set of users were able to easily refill their MetroCards and averaged around 10 to 20 seconds</p><p>If a commuter were to be in a rush to arrive at work on time, the amount of time taken to refill a MetroCard and enter the station would result in a delay. I needed to shorten that time frame so that users can enter the train station quicker. I noticed that every user expected certain buttons to be in certain locations of the app which I did not intend for.</p><p><strong>Wireframes</strong>:</p><p>I went back to the wireframe and made a few changes from the testing. With a limited amount of buttons, users were less frustrated and averaged about 5 to 10 seconds to refill their MetroCard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ww3M8XouI0eiQKz9Xw4LrA.png" /></figure><p>After much usability testing, I made a low-fidelity and mid-fidelity prototype of the MY MTA app. Below are a few concepts of what the final prototype would be.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m8DTG9JdvQqh9QVRS_zUNg.png" /></figure><p><strong>Conclusion:</strong></p><p>In conclusion, the double diamond method brought this prototype to fruition. It was a road map for me to discover and define the problem, as well as develop and deliver potential solutions. I produced a strong hypothesis, user flows, wireframes and observed how users interacted with the wireframes. I learned that not every user behaves the same within various circumstances. Based on their responses, I was able to go back and refine my designs.</p><p><strong>Next Steps:</strong></p><p>As a designer, my work isn’t done. The next steps would be to continue to gain user feedback on the product and reflect their thoughts in new iterations.</p><p><strong>Final Prototype:</strong></p><p>Check out the final prototype!</p><p><a href="https://xd.adobe.com/view/ea098d37-e0dd-4b80-9b7b-b71ce096bfb7-bf5a/?fullscreen">https://xd.adobe.com/view/ea098d37-e0dd-4b80-9b7b-b71ce096bfb7-bf5a/?fullscreen</a></p><p><strong>Contact Me:</strong></p><p>If you like my thought process and would like to collaborate, contact me at caduque0906@gmail.com</p><p>LinkedIn: <a href="https://www.linkedin.com/in/caduque0906/">https://www.linkedin.com/in/caduque0906/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=609be7222873" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>