<?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 Kash Ehsan on Medium]]></title>
        <description><![CDATA[Stories by Kash Ehsan on Medium]]></description>
        <link>https://medium.com/@kashehsan?source=rss-356579361cf5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*l_RQGyyC-sYd_1a8CJX40Q.jpeg</url>
            <title>Stories by Kash Ehsan on Medium</title>
            <link>https://medium.com/@kashehsan?source=rss-356579361cf5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 22:57:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kashehsan/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[Coupon Codes and Checkout Woes]]></title>
            <link>https://kashehsan.medium.com/coupon-codes-and-checkout-woes-bc3e2566a676?source=rss-356579361cf5------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc3e2566a676</guid>
            <dc:creator><![CDATA[Kash Ehsan]]></dc:creator>
            <pubDate>Thu, 10 Sep 2020 19:34:49 GMT</pubDate>
            <atom:updated>2020-11-30T16:40:50.723Z</atom:updated>
            <content:encoded><![CDATA[<p>Adding a coupon code feature to a checkout process: how hard could it be?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b9PlXGgaCZ5jFqDCh8CW9w.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@rupixen?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">rupixen.com</a> on <a href="https://unsplash.com/s/photos/discount?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>This week, I tackled a common checkout flow feature: coupon codes. After all, a free trial is one of the best ways to get a user hooked, and a coupon code is an easy way to give users free or discounted access.</p><p>I had 2 major considerations:</p><ol><li>Given that not all users will have a coupon code, how could I integrate this in a way that wasn’t distracting, but also easy to find for users who do need it</li><li>Business objective: capture users’ credit card information so that they don’t experience an interruption of service when the coupon code expires.</li></ol><h4>Option 1: Alongside Credit Card Information</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qvzEcvLfM87h1UFYgKA3pg.png" /></figure><p>This was my first idea — adding a coupon code field and button to the existing Payment Information page. This way, all payment-related tasks can be performed on this page.</p><p>Pros: only only page stands between the user and access to the service.</p><p>Cons: it’s not exactly a simple page, and there’s a lot going on. The coupon code field and button almost feel too prominent? What if users see the coupon code field/button and think that it’s required, that they’re missing something? Let’s see if we can declutter this page a bit.</p><h4>Option 2: Separate Checkout and Payment Pages</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*djksKKge87_nvzc3bK8nWA.png" /><figcaption>Checkout summary, then the hard part: credit card details</figcaption></figure><p>Since the first idea felt a little too cluttered, I thought about separating the checkout summary and payment details. On the Summary page — a list of charges, and option to add a coupon code (and see the coupon code reflected in the payment total). Following that — credit card details. Based on checkout flows and best practice to avoid user drop off, it made sense to ask for credit card information as the last step.</p><p>Pros: Each page remains simple, with one clear action per page. Users have a chance to pause before entering payment details and review their purchase.</p><p>Cons: Adds a new page into the flow, and more taps required before checking out.</p><h4>Where to go from here?</h4><p>Personally, I think option 2 makes more sense — while it does add an additional screen into the flow, it allows users to see exactly what they’re getting and pause before committing to the purchase. Now, it’s up to the stakeholders and developers. Let’s see what they think!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc3e2566a676" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Demos on a Shoestring]]></title>
            <link>https://kashehsan.medium.com/product-demos-on-a-shoestring-62abaa5b0111?source=rss-356579361cf5------2</link>
            <guid isPermaLink="false">https://medium.com/p/62abaa5b0111</guid>
            <dc:creator><![CDATA[Kash Ehsan]]></dc:creator>
            <pubDate>Sat, 05 Sep 2020 16:38:19 GMT</pubDate>
            <atom:updated>2020-09-05T16:38:19.666Z</atom:updated>
            <content:encoded><![CDATA[<p>Adding Director, Producer, and Editor to my Skills</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RC5DKrS90We0hxIY8M_QSg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@jakobowens1?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jakob Owens</a> on <a href="https://unsplash.com/s/photos/movie-shoot?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>This week at my internship, I was asked to create a product demo video ahead of our soft launch. It made sense, considering that I worked closest to the product aside from the developers (who had more than enough on their plate). One slight issue: I had never made a product demo before. How hard could it be though, I figured? I’ll just record my phone screen and talk about what I was doing. Spoiler alert: I was in for a short crash course in screenwriting, directing, and editing.</p><p>I started by writing out a list of the features to highlight and a script. But as anyone who’s tried to write a script for a presentation knows — what you write out on a script doesn’t necessarily come across as natural when you’re saying it out loud. Combined with actual actions on a screen, some lines needed to be improvised to match the pace of the action.</p><p>After I had a semi-finalized script, I ran into the need for some special effects. I was hoping that the video could somehow show where I was tapping on the screen — similar to how Figma prototypes show the movement of the mouse and taps using a translucent circle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/356/1*nMUSyCH2T8_4P5dm7boZDQ.gif" /></figure><p>I thought about recreating the app screens I wanted to show right in Figma, but that proved to be far too tedious (considering I had 3 different videos to make). I did not have the original designed screens, only the test apps from the developers.</p><p>I searched tutorial after tutorial, article after article and it seems like there’s no easy way to show taps/touches on an iPhone screen while screen recording. There are methods to hack Assistive Touch features, but <a href="https://www.youtube.com/watch?v=DAXxgBo-Mr4&amp;ab_channel=Zoheb">this particular method</a> did not work well for me. It was limited to only showing taps, and didn’t allow for scrolling/dragging. There were other methods that involved adding code to the app itself, but I was definitely not going to explore that route considering I had a day to do this.</p><p>Alas, I settled for a simple screen recording where I tried to describe what/where I was tapping as much as I could, and moving at a pace that would allow viewers to absorb the information.</p><p>Next up: editing. I haven’t really edited videos for precision before, so I didn’t realize just how tedious it would be! I’m sure the seasoned pros have more efficient methods of going about it, but editing involved so much of hearing the same clip again and again that I grew very tired of my own voice. Editors of music and media, I have SO much respect for you.</p><p>While filming product demos aren’t strictly part of the typical UX “toolkit,” I thought this was still a really productive exercise for me as a designer. It pushed me to really think through how a user would interact with the product, and enabled me to look through a critical lens at the task flows.</p><p>Request for developers/designers/Apple: please make a feature to show taps/touches on iPhone screens!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=62abaa5b0111" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Flexibility: underrated, very needed]]></title>
            <link>https://kashehsan.medium.com/flexibility-underrated-very-needed-8a14519c308?source=rss-356579361cf5------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a14519c308</guid>
            <dc:creator><![CDATA[Kash Ehsan]]></dc:creator>
            <pubDate>Sun, 30 Aug 2020 02:35:07 GMT</pubDate>
            <atom:updated>2020-08-30T02:35:07.497Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fx1aeqX2_IIg-_NjK-rOEg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@pankajpatel?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Pankaj Patel</a> on <a href="https://unsplash.com/s/photos/choosing?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>This is a a bit of a sequel to my earlier <a href="https://medium.com/@kashfiaehsan/overwhelmed-by-insights-7bcaeb0ede5b">post</a> about usability testing and gathering insights at my UX internship. As I mentioned, the interviews I conducted were the only monitored usability testing that had been performed on the app. There was more than a handful — perhaps an armful — of actionable feedback that I gathered. When it came time to organize these and make some sense out of what to tackle and what to shelf for the future, I went with an Effort vs. Impact matrix: what would make the most or least impact for users, plotted against the highest effort for product/developers to implement.</p><p>I thought I had it all planned out — go for the low hanging fruit first (high impact, low effort) and work on the high impact changes in the meantime. My first mistake: making assumptions about developer effort without actually speaking to a developer first. My second mistake: assuming nothing would get in the way.</p><p>Needless to say, things got in the way: we switched developer teams (from one offshore agency to another), ran into legal issues (nothing major, but it added steps to the user onboarding process), and my area lost power and internet for a week. When I got back on solid ground, much of my time was consumed by catching up the new developers, and designing a new task flow to ensure compliance. My beautiful Effort vs. Impact matrix was nowhere to be seen.</p><p>As I was working closely with the new developers to get them up to speed, they identified an armful — no, maybe a truckload — of bugs that were caused by the old developers. We also had to incorporate a new task flow that involved input and coordination from our board of advisors and CEO — this proved to be harder than we expected. It involved rework on the part of the developers, and they were not happy.</p><p>Lessons learned for me: what sounds like “low effort” for me might not necessarily be so for developers. Before I decide to label any change as such, it would be wise to consult those who will also be putting in effort to the cause. Moving forward, I’ll try to be more thoughtful about the implications of a potential change I’m considering — keeping in mind that my design doesn’t sit in a vacuum.</p><p>Case in point: a completely redesigned home page layout might be aesthetically pleasing (and I might have had my heart set on it for my portfolio), but the amount of work it will require to redo the whole navigation might not be worth it for a beta test. I will aim to be flexible, because even though my designs may be user-driven, they may not be the optimal solution in a world where both I and the developers have a limited amount of time and resources.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a14519c308" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Expectations vs Reality]]></title>
            <link>https://kashehsan.medium.com/expectations-vs-reality-2fdc91d32550?source=rss-356579361cf5------2</link>
            <guid isPermaLink="false">https://medium.com/p/2fdc91d32550</guid>
            <dc:creator><![CDATA[Kash Ehsan]]></dc:creator>
            <pubDate>Sun, 23 Aug 2020 20:31:38 GMT</pubDate>
            <atom:updated>2020-08-23T20:31:38.158Z</atom:updated>
            <content:encoded><![CDATA[<p>Or, “What I ordered vs what arrived”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IlzdVa_Sm-LgJgCr.png" /></figure><p>Over the past several weeks, as I’ve been working on a side project that involves actual developer involvement, and it’s not as easy as handing off a prototype and annotated wireframes.</p><p>As a group of 4 designers, we brought a LOT of ideas to the table, and thought through multiple user stories and features. For a product that didn’t even have a landing page yet, our designs included the flows for different user personas, multiple tasks, and even a settings page.</p><p>When our developers took a look at the mockups, there was definitely a *record scratch* moment. In order to ship a minimum viable product, we had to scale the features way down. From multiple user personas and several pages, we stripped the features down to about 3 pages, and 2 real tasks that users can perform.</p><p>Was this process disheartening? Not entirely. It was more like a much needed reality check. Outside the world of Material Design UI kits and pretty Figma mocks, <strong>coding </strong>an actual product takes considerable time and effort — hence, the minimum viable product. What is the simplest way to allow users to accomplish a single task that is at the core of the product?</p><p>Our team of designers had jumped the gun a little — we had designed for much more than just a MVP. Back to the drawing board we went, taking features out and reconfiguring a simpler layout. But, that doesn’t necessarily mean all our work upfront was for nothing — as our MVP is coded and shipped, we’ll have a version 2, 3, and 4 ready to go!</p><p>As we gather feedback from users, we can integrate features and pages as needed, as they make sense for the product. We might still need to make tweaks, but a bulk of the work is already done. We won’t need to scramble to design pages that will eventually be needed and are essential, like settings or user profiles — we already have a blueprint for those.</p><p>Overall, did we go a little overboard for an MVP? Yes. Would I do it again? Absolutely.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2fdc91d32550" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stacks on Stacks]]></title>
            <link>https://kashehsan.medium.com/stacks-on-stacks-a7309006a924?source=rss-356579361cf5------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7309006a924</guid>
            <dc:creator><![CDATA[Kash Ehsan]]></dc:creator>
            <pubDate>Sat, 15 Aug 2020 16:40:03 GMT</pubDate>
            <atom:updated>2020-08-15T16:40:03.232Z</atom:updated>
            <content:encoded><![CDATA[<p>How to incorporate a new feature into my workflow?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GEY0Z_fWmBhNdxXodGYUew.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@robsphotos?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Rob Sheahan</a> on <a href="https://unsplash.com/s/photos/stacks?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>As an Adobe XD fan, I wanted to like their new feature Stacks. XD has so many features that are specifically created to ease a UX designer’s workflow, like Component States and Repeat Grid, that I had expected their new Stacks feature to be similarly revolutionary. I gave it a try last week (<a href="https://medium.com/@kashfiaehsan/what-are-stacks-in-adobe-xd-3196a93a1047">here’s</a> my first foray into Stacks), and again this week with a few Behance challenges. Unfortunately, it fell short of my expectations.</p><p>Basically, Stacks allows you to rearrange items in a group without having to manually adjust the spacing in the layout. The items are arranged in a grid-like way, where they can swap spaces with each other and snap into place if moved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WYloiADvOfK2HQzaFzOERg.gif" /></figure><p>I can see how this would be useful — if you have elements that are roughly similar sizes and could potentially be placed in multiple areas on a layout. I found it helpful when reviewing a layout with a team member, and showing them different layouts on the fly, because the elements could be easily swapped.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/420/1*ygwfnrkcbsjCTEtDkvtCzQ.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/424/1*MG0N9z6rU0qt34ANgt1ttA.gif" /></figure><p>I think I’ll tend to think of Stacks as an extension of the Repeat Grid feature. Overall, it’s lackluster compared to the other innovative features I know and love in Adobe XD. Stacks isn’t bad — it just isn’t spectacular either.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7309006a924" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What are Stacks in Adobe XD?]]></title>
            <link>https://kashehsan.medium.com/what-are-stacks-in-adobe-xd-3196a93a1047?source=rss-356579361cf5------2</link>
            <guid isPermaLink="false">https://medium.com/p/3196a93a1047</guid>
            <category><![CDATA[adobe-xd]]></category>
            <category><![CDATA[behance]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[prototyping]]></category>
            <dc:creator><![CDATA[Kash Ehsan]]></dc:creator>
            <pubDate>Thu, 06 Aug 2020 23:26:00 GMT</pubDate>
            <atom:updated>2020-08-06T23:26:00.961Z</atom:updated>
            <content:encoded><![CDATA[<p>A newer feature to explore</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cwQIyGU5IAj_qE_oI99VmA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@eklektikum?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Iva Rajović</a> on <a href="https://unsplash.com/s/photos/stack?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Simply because it lacks the powerful real time collaboration capabilities of Figma, Adobe XD has become my second go-to prototyping tool (sorry, Sketch). Its Component States, Repeat Grid, and quick prototyping tools make it one of the easiest tools to use. I noticed that XD recently added a new feature: Stack. What is Stacks all about?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/234/1*zsVj2aNcT4sjkFjncOU9Tg.png" /><figcaption>Stack sits right within the Layout section</figcaption></figure><p>Stack allows you to swap different objects in a group with one another, and they “snap” together on top of or beside one another — like objects in a stack. I could see this being useful for objects in a list, or a row, where objects might need to switched around to test different placements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/394/1*SNvru38JfM6U4WC7rrm58w.gif" /><figcaption>Swapping feature descriptions quickly using Stack</figcaption></figure><p>An ideal workflow to create a list or row of identical items would probably consist of using Repeat Grid to create the objects, then customizing them, then Stack to reorder if needed. I can definitely see the utility of using Stack for quick layout changes, as long as the padding and spacing of elements is also easily adaptable.</p><p>Overall, Stack didn’t impress me as much as Component States or Repeat Grid did, but it’s still a cool feature! Maybe I just need more time to get acclimated with it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3196a93a1047" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Communicating for Handoffs]]></title>
            <link>https://kashehsan.medium.com/communicating-for-handoffs-d8fd5822363?source=rss-356579361cf5------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8fd5822363</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[mobile-app-design]]></category>
            <dc:creator><![CDATA[Kash Ehsan]]></dc:creator>
            <pubDate>Sun, 02 Aug 2020 17:22:08 GMT</pubDate>
            <atom:updated>2020-08-02T17:22:08.802Z</atom:updated>
            <content:encoded><![CDATA[<p>Conveying Ideas to Developers</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9zYed1mYoaQBkboxsI82BA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@charlad?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Charles-Adrien Fournier</a> on <a href="https://unsplash.com/s/photos/developer?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>In a perfect world (like those described in academic settings), developers will wait for high fidelity, pixel perfect, annotated mockups from designers, complete with a fully functional prototype that illustrates their ideas. Alas, reality is never as perfect as the theoretical situations painted in classrooms, and we have to find ways around it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/1*3owmEJsNd7PXVL8yumVleQ.png" /><figcaption>Annotations written with precision and care, only possible with ample time</figcaption></figure><p>In the tiny startup UX design role I jumped into, there was no real handoff process with developers. About a year ago, a freelance designer created high fidelity mockups which were given to an offshore development team. Since then, the developers have mainly worked off the original designs and updates conveyed over a variety of mediums: email, Word docs, and Google Slides. There were also no major design changes done — mainly bug fixes, and language/content edits.</p><p>Having completed my own audit and a usability test of the product, I knew we were in for some major changes. However, without an established process for handoff, I didn’t know how my designs would actually end up in the hands of users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nNtxuycN6DqsDEM9sOz46w.png" /><figcaption>Google Slides with screenshots: it gets the job done</figcaption></figure><p>The Google Slides deck with app screenshots and requested edits was working for typos and minor changes, but I wasn’t sure that it would work for a task flow change, or full redesign of a page.</p><p>I ended up creating a Figma document with detailed annotations of each screen and the associated interactions. Due to time constraints, I wasn’t able to create a prototype to illustrate all of the interactions. We also struggle with time zone barriers, so much of our communication is asynchronous.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/789/1*_yySzNZB7WDrIayvhh0CxA.png" /><figcaption>Hopefully this is detailed enough?</figcaption></figure><p>In the coming weeks, I’m aiming to establish a better, standardized handoff process with developers. This is one of those things that is impossible to learn in an academic setting, and now I see why: it will always differ from situation to situation, from company to company.</p><p><em>How do you handle hand offs? I’d love to learn any and all techniques!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8fd5822363" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Overwhelmed by Insights]]></title>
            <link>https://kashehsan.medium.com/overwhelmed-by-insights-7bcaeb0ede5b?source=rss-356579361cf5------2</link>
            <guid isPermaLink="false">https://medium.com/p/7bcaeb0ede5b</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[usability-testing]]></category>
            <category><![CDATA[user-testing]]></category>
            <dc:creator><![CDATA[Kash Ehsan]]></dc:creator>
            <pubDate>Sun, 26 Jul 2020 00:33:27 GMT</pubDate>
            <atom:updated>2020-07-26T00:33:27.717Z</atom:updated>
            <content:encoded><![CDATA[<p>Feedback is great — but what if you have <em>too much?</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UxlU7I27s2ErHhKrSmgt1w.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@charlesdeluvio?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Charles Deluvio</a> on <a href="https://unsplash.com/s/photos/feedback?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>As I described in <a href="https://medium.com/@kashfiaehsan/user-centered-not-designer-centered-design-ca4542357756">this post</a>, I recently started a UX design internship and conducted a usability test for the product, a mobile app. There had been no formal user testing done until this point, so I really wanted to put some solid research practices in place.</p><p>The testing went fairly smoothly, aside from some technical hiccups and difficulties with remote mobile testing. We ended up with 8 participants, and they each performed 6 key tasks with the mobile app.</p><p>Because I wanted to gather as much feedback as possible in this round, we ended up with <strong>a lot</strong> of insights and potential changes. Honestly, it was a little overwhelming. In the academic settings where we conducted usability tests, the products and tasks themselves were small and contained enough that most of the insights were easily implemented. That was not the case here.</p><p>Because we tested most major features of the app (except for a few which are still in development), and asked for open ended feedback — our participants supplied a plethora of thoughts and insights.</p><p>We had to visualize and organize our data in some way beyond a spreadsheet. For this case, I chose a to plot suggested changes on a matrix, ranking each change on 2 axes: effort and impact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/711/1*sDvH7z6GOWygEdk3-NyNDg.png" /><figcaption>Each color of sticky note refers to a different task</figcaption></figure><p>The level of effort referred to both design and development effort, and impact was determined by how often a particular issue was brought up by test participants, and their general feeling towards that issue.</p><p>The effort vs impact matrix definitely helped organize our thoughts, but it was still fairly overwhelming to look at as a whole. From there, we decided to focus on the tasks that were rated the lowest in terms of “ease of completion” (we had asked participants how easy it was to complete each task, on a scale of 1 to 5, 5 being very easy). Essentially, we are assuming that redesigning elements of the “worst” tasks will lead to the most improvements in usability. This will also help keep us focused — we’re not thinking about different parts of the app all at once, only on specific parts one at a time.</p><p>For a small UX team of 2 with only 24 hours in a day, this segmented approach seems to be the most sensible plan of action. If anyone has any better ideas, I’d love to hear them! Drop them in the comments if you wish.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7bcaeb0ede5b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[User Centered, not Designer Centered Design]]></title>
            <link>https://kashehsan.medium.com/user-centered-not-designer-centered-design-ca4542357756?source=rss-356579361cf5------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca4542357756</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[mobile-testing]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[user-testing]]></category>
            <dc:creator><![CDATA[Kash Ehsan]]></dc:creator>
            <pubDate>Fri, 17 Jul 2020 20:20:16 GMT</pubDate>
            <atom:updated>2020-07-17T20:20:16.787Z</atom:updated>
            <content:encoded><![CDATA[<p>Even if you fit the user persona, you’re not designing for yourself</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P4GoBUZPR28FMlVkt6PRrw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@plhnk?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Paul Hanaoka</a> on <a href="https://unsplash.com/s/photos/mobile-phone?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I recently started a UX design internship, and my first order of business was completing an audit of their current product. I used the app as I would if I was a user — and I very well could be. I am solidly in their target user base, and I’ve used similar products before. I definitely had my designer hat on as well, but I was mainly looking at the product as me.</p><p>Having finished an initial audit, I gathered a hefty list of heuristics principles violations, unintuitive buttons, navigational inconsistencies, and more. If I stopped there and jumped into Sketching (whether analog or digital), I probably could have generated some perfectly acceptable solutions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uJ7uijA2eurqLs_XxXjO-w.jpeg" /><figcaption>Not so fast, we’re not there yet! Photo by <a href="https://unsplash.com/@uxindo?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">UX Indonesia</a> on <a href="https://unsplash.com/s/photos/thinking?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>At this point, I had a choice to make — start designing, or conduct more research. Sure, I was a potential user — but I was only a sample size of one. Acceptable, not great. Why should I settle for acceptable? As I’ve learned from designing in the past several months, your designs are only as good as the research behind them.</p><p>I decided to conduct a round of usability testing with the current app. This took about 2 weeks, from planning to sourcing users to synthesizing insights. In addition to highlighting new issues, much of what we learned validated what I had highlighted in my own audit. This made my case stronger for redesigning those particular pages and flows.</p><p>While we never directly asked what users would want to see, often our testers just offered potential solutions as they would want to see them. Thank you users, for unknowingly participating in our ideation session as well!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1fJ3nlqEv5Ll2TntfMmyDg.jpeg" /><figcaption>Turns out our testers didn’t want to stick around to Sketch. Photo by <a href="https://unsplash.com/@nickmorrison?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Nick Morrison</a> on <a href="https://unsplash.com/s/photos/your-work-matters?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Another unintended result of testing: gauging general interest in the product itself. To remove testing bias, we sought out individuals who would fit the user persona, but were unfamiliar with the app. Despite this being their first time with the app, a majority of our testers responded extremely positively to the concept. While the purpose of the usability test was narrowly focused on understanding whether users can accomplish certain tasks within the app, enthusiastic feedback was just a cherry on top!</p><p>Of course, this wasn’t exactly a shocking revelation — our founder and the company’s early backers knew this. But it was the first time that a testing participant told me that they were rooting for me, and that my work was important. I wouldn’t have experienced this firsthand if I hadn’t invested time into testing, and that in itself made the 2 weeks of research worth it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca4542357756" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Remote User Testing for Mobile: Getting Creative]]></title>
            <link>https://kashehsan.medium.com/remote-user-testing-for-mobile-getting-creative-206e6c6b356b?source=rss-356579361cf5------2</link>
            <guid isPermaLink="false">https://medium.com/p/206e6c6b356b</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[mobile-ux]]></category>
            <category><![CDATA[usability-testing]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[mobile-app-testing]]></category>
            <dc:creator><![CDATA[Kash Ehsan]]></dc:creator>
            <pubDate>Thu, 09 Jul 2020 21:13:59 GMT</pubDate>
            <atom:updated>2020-07-09T21:13:59.424Z</atom:updated>
            <content:encoded><![CDATA[<p>When in person testing is impossible, how can we cheaply test mobile apps?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/751/0*mhfVb11cQSXJF8T2" /></figure><p>This week, I started a UX design internship at a very small startup. By very small, I mean bootstrapped and equipped with a rudimentary mobile app. My job is to test and improve this first version of their app. I completed my own audit of the app, but I knew that <strong>user </strong>experience is nothing without <strong>users —</strong> I needed to get more perspectives.</p><p>But what’s a good story without some conflict? In this case — I had neither the original designs nor a shareable prototype, just the app as it currently stands on the app store. I could ask potential users to download and use the app on their phones while I observe them. Due to the pandemic, this was not possible.</p><p>So how can I observe people use their mobile phones when I can’t sit next to them? My searches for “remote mobile user testing” yielded results that were just advertisements for user testing services, or required software downloads.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/731/1*IILU3Krhua_l68hoPMt33A.png" /></figure><p>As a bootstrapped startup, we couldn’t use professional user testing services. We considered taking screenshots of the current app and uploading those to InVision to reverse engineer a clickable prototype that would work on a computer. However, this seemed extremely tedious. The most obvious answer would be to mirror a phone screen on a computer, then use screen sharing on Zoom or Google Meets to observe their actions. As far as I knew, there’s no “screen share” feature on mobile phones like there are on computers.</p><p>Or is there?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/811/0*otTIyF-J9BoNyPFB.jpg" /><figcaption>Quicktime Player to the rescue</figcaption></figure><p>Turns out, there is a way to mirror an iPhone screen to a Mac. It’s actually very simple, and uses Quicktime Player, which comes preinstalled on all Macs (<a href="https://www.youtube.com/watch?v=6y9RKjhAdRU">link</a>). Unfortunately, some interested testers didn’t have a Mac, but we still sourced enough participants for this round of testing.</p><p>We didn’t have time to test whether the iPhone mirroring would work on a PC with Quicktime Player installed — that’s on our to-do list for next time. Perhaps we will find a different method altogether or a workaround for the next round of testing. For the time being though, Quicktime Player has saved the day.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=206e6c6b356b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>