<?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 @kingsidharth on Medium]]></title>
        <description><![CDATA[Stories by @kingsidharth on Medium]]></description>
        <link>https://medium.com/@kingsidharth?source=rss-ea17deaeaa97------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*vcHaLa2cLlwsdLIPDZqwRg.jpeg</url>
            <title>Stories by @kingsidharth on Medium</title>
            <link>https://medium.com/@kingsidharth?source=rss-ea17deaeaa97------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 04:44:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kingsidharth/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[Industry Review 2020: changes in design, products, & consume behaviour]]></title>
            <link>https://uxdesign.cc/industry-review-2020-changes-in-design-products-consume-behaviour-d8b4996fdba1?source=rss-ea17deaeaa97------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8b4996fdba1</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[trends]]></category>
            <category><![CDATA[consumer]]></category>
            <dc:creator><![CDATA[@kingsidharth]]></dc:creator>
            <pubDate>Sat, 18 Jan 2020 15:38:24 GMT</pubDate>
            <atom:updated>2020-01-20T15:58:51.383Z</atom:updated>
            <content:encoded><![CDATA[<h4>Trends that will affect designers, product folks, and people in tech.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ld2QCM9zBLMT6FazgAnc9Q.png" /></figure><p>I use near years as an arbitrary check-point to reconcile thoughts, notes, and ideas gathered over the last year, and the year before that. Reflecting at and adding from the notes a year before, hopefully, makes sure that good ideas go forward, and short-term noise is easy to spot &amp; drop.</p><p>I feel these changes will have a significant impact on designers, product managers, and people working in tech. These trends are intertwined, it’s hard to decipher which one comes first.</p><p>Of course, I could be wrong. There’s a ton of bias including groupthink, and recency bias — so take it with a big bag of salt.</p><h3>1. Structure of Design &amp; Product Teams</h3><p>Companies &amp; startups scaling up the traditional design methods, team structures, specializations, team-mixes, and goals — seem to be coming to similar answers.</p><p>In my conversations with designers at several companies, here are some notable changes:</p><ul><li><strong>UX Research</strong> is a separate department (not tied to the design department), serving research needs of the company at large. Often touching upon aspects traditionally covered by market research</li><li>While <strong>UX + Product Designer</strong> or end-to-end<strong>Interaction Designers</strong>, both, remain popular depending on the culture &amp; problems of the company/product/service</li><li><strong>Visual Communication Designers</strong> are making a comeback, including motion designers &amp; content designer — a role traditionally server by Art Departments. Why is this happening? Along with a rewned interesting in people from animation, gaming, and film-making who are experts in gaminification, motion design, character design, etc.</li></ul><p>Which brings us to the next trend:</p><h3>2. The Comeback of Content-First &amp; Communication Design</h3><p>More companies are realising that on the internet, you’re in the content-attention-action business, from e-commerce to building platforms — it’s all content.</p><p>Amazon is content, email is content, Instagram is content, heck all your enterprise tools are also content.</p><p>There is no escape. Features are not the big game anymore unless you have an AI that works. (We all know Siri is dumbest of all; Cortana doesn’t count)</p><p>So how do you differentiate, if not with features? Make content &amp; make it more consumable &amp; binge-able.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FW22cJ8Ug3Ncy2E22b7%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Foriginals-W22cJ8Ug3Ncy2E22b7&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FW22cJ8Ug3Ncy2E22b7%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="348" frameborder="0" scrolling="no"><a href="https://medium.com/media/2d5d761ec4fccc2b982411b38f3a1c76/href">https://medium.com/media/2d5d761ec4fccc2b982411b38f3a1c76/href</a></iframe><h3>3. Social &amp; content is not done yet; it’s just getting started</h3><p>If you have a social media platform fatigue, brace yourself because there’s far more to come. With more and more platforms embracing and winning with mixed media content and spawning new micro-communities, I feel we need at least twenty more social networks!</p><p>What’s mixed-media content?</p><p>Think of an Instagram story: it can be a video, audio, text, and some more.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F385638666%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F385638666&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F847840399_295x166.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="504" height="896" frameborder="0" scrolling="no"><a href="https://medium.com/media/1aebca3efeedddee607c58d030acaa94/href">https://medium.com/media/1aebca3efeedddee607c58d030acaa94/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F385641356%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F385641356&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F847844560_640.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="720" height="1280" frameborder="0" scrolling="no"><a href="https://medium.com/media/c282637f9c13a13d1c6659aa2eba2fb6/href">https://medium.com/media/c282637f9c13a13d1c6659aa2eba2fb6/href</a></iframe><p>TikTok’s authoring tools allow you to make even better videos. It’s seriously mind-blowing what you can make with TikTok on the fly.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FapoVa0gwER8%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DapoVa0gwER8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FapoVa0gwER8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c35fe453693ff1124fbe1cd3c717f0d6/href">https://medium.com/media/c35fe453693ff1124fbe1cd3c717f0d6/href</a></iframe><p><a href="https://www.tiktok.com/@kingsidharth_/video/6756910348537810178">Here’s a video</a> I made combining clips on Primer Rush (mobile version of Primer Pro) and <a href="https://www.tiktok.com/@kingsidharth_/video/6779870106777292034">here’s what I shot directly on TikTok</a>.</p><p>The one on TikTok took far less time and was easier to sync to the music.</p><p>Stories are not just photos; they are the new age mixed-media content. From Snapchat, IG, TikTok to Fireworks — we are yet to see the explosion of content, social, and other platforms.</p><p>Heck, if <a href="https://substack.com/">Substack</a> could reinvent newsletters (and we thought this war was over), everything is still open for disruption.</p><h4>Subtrend: Voice, Loops, &amp; Micro Content</h4><p>The TikTok format of music/voice and video loops is going to have a significant impact on how consumers consume content.</p><p>Product pages with a series of TikTok anyone? We aren’t even starting to scratch the surface. The TikTok format will be very relevant for anyone who wants to communicate anything online (all of us?) and product-marketing.</p><p><a href="https://vm.tiktok.com/4NGrD9/">Is your brand loopable?</a></p><h4>Subtrend: Audio + Tactile</h4><p>We’d also see an explosion of smart voice-UI applications and even some tactile UI picking up (3D Touch, Apple Watch feedback, etc.). Tacklike works way better in public and for personal stuff (I don’t want a ringing reminder for medicines, just my watch to vibrate in a particular sequence).</p><p><a href="https://medium.com/u/9347969c9b98">Dhvanil Patel</a> <a href="https://dhvanil.com/airpods-pro-and-the-future-of-augmented-audio/">explores this in detail on his blog</a>.</p><p>All this new content, both from consumption and creation pov, will be fueled this next change:</p><h3>4. 5G &amp; Wifi 6 for Designers &amp; Product People</h3><p>Let’s not get into what these are. What it means is more devices, always online, reliability, with low latency.</p><p>The reduced latency will allow the computationally heavy stuff to move to the cloud (someone else’s computer). We’d see true smart cars, enterprise-grade smart security, real-time remote medical assistance, mind-blowing mobile-games, new age educational content, and crazy new authoring tools.</p><p>We already see Google Stadia. Although Google over-promised and under-delivered with 5G &amp; Wifi 6 — google’s promise of 4K@60FPS gaming on mobile could become real.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FGzEIu368ht4%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DGzEIu368ht4&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FGzEIu368ht4%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/886b0b8065a75a8588cdc5a278f609a7/href">https://medium.com/media/886b0b8065a75a8588cdc5a278f609a7/href</a></iframe><p>5G &amp; Wifi 6 will also allow platforms to be live first. Imagine TikTok where you can only go live first and then post what you made live (Interesting fact: Snapchat already tries to differentiate between content produced on the app vs off the app, etc.)</p><p>Maybe for the first time, you could wear a VR headset and see a live game with a screen that sucks less.</p><p>Which brings us to the next significant change:</p><h3>5. Usable AR content &amp; applications</h3><p>Oh no! Not another post about AR &amp; VR is coming — and it never does.</p><p>It’s not here. My VR Headset lays in the corner which most content and the best apps already consumed, and the new content is coming in at a super slow rate.</p><p>But with Apple making considerable leaps in AR, from games to Measurement app — it feels like it should already be here.</p><p>One of the biggest applications we’ll see is probably in data and education:</p><ul><li>Our brains can’t imagine 10,000 vs 1,000 vs 100 but what if I could show you?</li><li>What if I could show you how all the elements in the periodic table look like?</li></ul><p>The most significant limitation for VR and AR is not the consumer-side tech; you can get a Google VR Cardboard box dirt cheap. But the creation of tech &amp; content remains expensive.</p><p>Now that I can create 4K video on my iPhone (cheapest reliable 4k video-camera in the market folks), you will see me making and posting more content in 4K. But till I can just point and create VR content with my app, the content production will suffer on VR platforms.</p><p>The story can be a little different for AR, though! There are also rumours of Apple eventually launching AR glasses that will come to replace the iPhone over the decade. Not saying it’s going to happen — but we’re going to see more push in this direction!</p><p>So content platforms, mixed media, low-latency, and AR — looks like designers will be busy. We may have one of our next big obsessions already in the works:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F1SrckSJvGc8%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D1SrckSJvGc8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F1SrckSJvGc8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/7b29fe7db1781b891c698d041f2dd2e1/href">https://medium.com/media/7b29fe7db1781b891c698d041f2dd2e1/href</a></iframe><p>Plus there will be <a href="https://medium.learningbyshipping.com/ces2020-primordial-soup-of-innovation-208571f15c94">crazy new screens and mediums to design for</a>.</p><p><a href="https://medium.learningbyshipping.com/ces2020-primordial-soup-of-innovation-208571f15c94">#CES2020: Primordial Soup of Innovation</a></p><h3>6. Neomorphism</h3><p>Skeuomorphism was about mimicking reality. Neomorphism is about taking inspiration from reality and imagining new materials that exist purely in our digital lives.</p><p>While we are in very nascent stages, over time, designers will have to imagine new “materials” that users can interact with new and exciting ways.</p><p>Adding signifiers for AR/non-AR use, or more interaction, rich touch screens will continue to demand us to imagine new interactions and feedback.</p><p>Google’s Material design laid the foundation for it long back, with things like “Fab” button becoming ubiquitous among utility apps. We are just getting started here, folks.</p><p>But like always, this could be rendered just another trend rather than a major move.</p><h3>Abhinav on Twitter</h3><p>For designers jumping on the hot new trend</p><h3>7. Mobile is the new Hub</h3><p>Remember the days when a Mac or PC was your main hub to which all devices connected? As IOT continues to slip into our lives bit by bit — with an extended, yet failed, pushed to make even our toilets smarted — mobile will be the new hub.</p><p>With Apple leading the way with A13 — mobile chips will continue to get better.</p><p>This opens up a whole new world of even bigger possibilities:</p><ol><li>Real Video Editing on iPad</li><li>End-to-End Music Creation with multi-device attachments</li><li>4K Live Videos from Mobile Devices (almost all flagship phones of big phones now have 4K videos)</li></ol><p>This future won’t come all at once, of course.</p><h3>8. Private Design Mentors</h3><p>As traditional educational institutes continue to fail to prepare students for real real-world; the internet is cutting out the middle-men (as it does in everything).</p><p>Designers, Engineers, Science Educators, Digital Marketers are taking to various social media platforms from YouTube, LinkedIn, Instagram, Twitter, Medium to teach &amp; share the nuances of the craft for those who listen.</p><p>More senior designers, who find it difficult to build content online, are instead starting to take students, Jr. designers as remote interns (some paid, other free). Mentorships mostly include assignments, one-on-one sessions about specific issues the designers are dealing with.</p><p>However, as the trend catches on — we’d see Dunning-Kruger effect, mixed with the economic incentives — where a lot of impractical or lousy advice will be sold en-mass.</p><p>Information Asymmetry beats us often. However, this time, folks are seeking out mentors in people who are already working in the industry rather than going for people who started teaching without any experience in the industry.</p><p>As always, the quality of the outcome will depend on the research students do before taking up courses or mentors.</p><h3>10. Difficult Discussion</h3><p>This year brought out some critical discussion on #designtwitter and in the design community at large. We do need to become more mature as a community to live what we preach — empathy.</p><p>The most important discussion we’ve started is that of <a href="https://mailchi.mp/dcb646602f04/then-golden-rule-in-design-ethics-64n3">consequences of our grand designs</a>.</p><h3>11. The Sacred Unit-Economics</h3><p>The unit-economics aware investors are here to stay. Product and design departments will have more participation, as this is likely to become the new norm.</p><p>It will become even more important for designers to learn about the basics of business. Asking questions to your friends in the product departments may be a good start. Also this <a href="https://www.amazon.com/What-Wants-Know-Expanded-Updated/dp/0553417789/ref=sr_1_1?crid=3GQNLMGXJ6HGM&amp;keywords=what+the+ceo+wants+you+to+know&amp;qid=1579360890&amp;sprefix=what+the+ceo+w%2Caps%2C338&amp;sr=8-1">excellent</a> <a href="https://www.amazon.in/What-CEO-Wants-You-Know/dp/1847942164/ref=as_li_ss_tl?crid=2VUI4TSYTFMWZ&amp;keywords=what+the+ceo+wants+you+to+know&amp;qid=1579360821&amp;sprefix=what+the+ceo+want,aps,269&amp;sr=8-1&amp;linkCode=sl1&amp;tag=ksgen-21&amp;linkId=719d3e3f78e969b9f52ff71600b078be&amp;language=en_IN">book</a>.</p><p>This “trend” has deep undercurrents in the turbulence of global-economy. I will spare you the details of trade-war, global slowdown stuff you can find online.</p><h3>12. Data-Informed not Data-Driven</h3><p>As we realise biases of data, consumers become more aware of what data companies and apps ask for — and as we understand most of our traditional stats methodologies multiply biases — we’ll find companies, product &amp; design departments will move their stance from data-driven to data-informed.</p><p>You want data to inform you and still allow space for bets and innovation, instead of multi-variant testing every shade of blue in existence.</p><p>We will continue to see a demand for a more balanced approach than <a href="https://matthewstrom.com/writing/ab-testing-paradox">A/B testing your way out of everything</a>.</p><p>This article was written from the notes I tool for webinar with TapChief on “Product &amp; Design Trends in 2020” you can watch the full video here:</p><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=facebook&amp;url=https%3A//www.facebook.com/tapchief/videos/625086924903516/%3Fredirect%3Dfalse&amp;image=https%3A//i.embed.ly/1/image%3Furl%3Dhttps%253A%252F%252Fscontent-iad3-1.xx.fbcdn.net%252Fv%252Ft15.5256-10%252Fp200x200%252F74599087_625150391563836_5558796117593817088_n.jpg%253F_nc_cat%253D108%2526_nc_ohc%253DFAzhMtn8nw4AX8Y9lgu%2526_nc_ht%253Dscontent-iad3-1.xx%2526_nc_tp%253D1002%2526oh%253Db8f77a4d428ef17e449f8cd7406aa3e0%2526oe%253D5E9B5733%26key%3Da19fcc184b9711e1b4764040d3dc5c07" width="600" height="600" frameborder="0" scrolling="no"><a href="https://medium.com/media/be9db64d31ccd47e553408af56b59233/href">https://medium.com/media/be9db64d31ccd47e553408af56b59233/href</a></iframe><p><em>Originally published at </em><a href="https://www.64notes.com/2020-industry-trends-tech-design-product/"><em>https://www.64notes.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8b4996fdba1" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/industry-review-2020-changes-in-design-products-consume-behaviour-d8b4996fdba1">Industry Review 2020: changes in design, products, &amp; consume behaviour</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Frameworks: tame massive scope & complexity]]></title>
            <link>https://uxdesign.cc/design-frameworks-ux-problems-24ce3141de54?source=rss-ea17deaeaa97------2</link>
            <guid isPermaLink="false">https://medium.com/p/24ce3141de54</guid>
            <category><![CDATA[design-management]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[design-framework]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[@kingsidharth]]></dc:creator>
            <pubDate>Wed, 30 Oct 2019 13:06:03 GMT</pubDate>
            <atom:updated>2019-11-01T10:59:54.964Z</atom:updated>
            <content:encoded><![CDATA[<h4>Case study in building a design framework for millions of tickets.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TeR9uhcVh2OX_miq1fJPOA.png" /></figure><p>Millions of customers from over 120 countries use <a href="https://www.headout.com/">Headout</a> every month to book experiences like guided tours, attractions, and activities.</p><p>We have over 5,000 listed products; each may have several partners fulfilling the experience. For these products, we generate more than 5,000 types of tickets on our platform.</p><p>This is how most of these tickets looked like:</p><figure><img alt="Original Headout Ticket — where most information was communicated using text that customers wouldn’t read." src="https://cdn-images-1.medium.com/max/853/0*mB1ch0ivOgxizC4H.png" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FnjAjh98E1PUha%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Faint-nobody-got-time-for-that-oh-lord-jesus-its-a-fire-njAjh98E1PUha&amp;image=http%3A%2F%2Fgiphygifs.s3.amazonaws.com%2Fmedia%2FnjAjh98E1PUha%2F200.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="243" frameborder="0" scrolling="no"><a href="https://medium.com/media/ca675e8c2a12339d5a3f7d7fa9df219d/href">https://medium.com/media/ca675e8c2a12339d5a3f7d7fa9df219d/href</a></iframe><p>Customers were missing out on their experiences because of bad ticket design! The most critical of these issues were:</p><ol><li>For print tickets, customers were missing out that they had to print it</li><li>When the customers received a mobile ticket they would reach the location only to find out their network/internet does not work</li><li>Customers were missing out on the location they’re supposed to reach</li><li>Customers were not able to locate the Bar Code, QR Code, or the partner ticket ID required to access the experience</li></ol><p>The content &amp; marketing team did an audit &amp; redesigned the ticket:</p><figure><img alt="Improved version of the Headout ticket; where the map &amp; meeting point is visual, but information is still hard to find." src="https://cdn-images-1.medium.com/max/826/0*vuBjG7gFKApRs6Pd.png" /></figure><p>There were some improvements. However, the problems wouldn’t go away.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F3o7aTskHEUdgCQAXde%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fquentin-tarantino-pulp-fiction-vincent-vega-3o7aTskHEUdgCQAXde&amp;image=https%3A%2F%2Fmedia4.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExZnV3cWExbXlvdmg5YmdoMDNmZnZoaGxwaWo4MmZqd3locTFvZm9rNiZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2F3o7aTskHEUdgCQAXde%2Fgiphy_s.gif&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="187" frameborder="0" scrolling="no"><a href="https://medium.com/media/e89468bc9c3079c927471690191806b7/href">https://medium.com/media/e89468bc9c3079c927471690191806b7/href</a></iframe><p>At first glance, we see several issues like:</p><ol><li>That QR Code looks like a way to access the 5% discount; it’s not — the on-ground staff scans it to validate the ticket</li><li>Most people will skip the text (it’s critical to read it)</li><li>Maps look better, but there is visual noise and the contrast ratio doesn’t survive a black &amp; white printing</li></ol><p>With an ever growing number of listings, tickets, and use-cases we needed something more robust.</p><p>Let’s redesign the tickets, right?</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FxUOxf8R29PSTtF6PE4%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Forchfilms-everything-beautiful-is-far-away-xUOxf8R29PSTtF6PE4&amp;image=https%3A%2F%2Fmedia1.giphy.com%2Fmedia%2FxUOxf8R29PSTtF6PE4%2Fgiphy.gif%3Fcid%3D790b76110762d4ddd5479dc86c837ab758f824963caf42d8%26rid%3Dgiphy.gif%26ct%3Dg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="243" frameborder="0" scrolling="no"><a href="https://medium.com/media/a5f5c7c843149cef2e815c5b22f8430d/href">https://medium.com/media/a5f5c7c843149cef2e815c5b22f8430d/href</a></iframe><p>Sure. Let’s start by taking a look at the information we are communicating. Here’s a list (most of) the variables that go into a ticket.</p><figure><img alt="A short sample of the full list of variables/bits of information that go into making a ticket." src="https://cdn-images-1.medium.com/max/1024/0*2lGQ4Ij-v-v4eak4.png" /></figure><p>Most of these variables have at least two states (Present &amp; Absent); some have 4+ states &amp; several ways to represent the data.</p><p>That’s 30+ variables with at least 27x2 = 54 states.</p><p>Our simplest ticket uses 7 variables (7x~2 states = ~14 states) from the list. That’s ~3,432 combinations. [ <a href="https://en.wikipedia.org/wiki/Combination">C(n,r)</a> =&gt; 14!/(7!(14–7)!]</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fc7PcKQlOqZ8Ws%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Freaction-mrw-gpa-c7PcKQlOqZ8Ws&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fc7PcKQlOqZ8Ws%2F200.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="185" frameborder="0" scrolling="no"><a href="https://medium.com/media/d832bbbcc1cdbf5058962e69ec75ee9c/href">https://medium.com/media/d832bbbcc1cdbf5058962e69ec75ee9c/href</a></iframe><p>With the remaining 20+ variables — There are at least ~1,84,756 combinations that exist!</p><p>Of course, not all these combinations would be realistic, but even if we were to take a conservative estimate, only 10% are realistic; that leaves us with at least 1,800 additional combinations to design for.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FvysUmffUa9o4g%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fangry-anger-sheldon-vysUmffUa9o4g&amp;image=https%3A%2F%2Fmedia1.giphy.com%2Fmedia%2FvysUmffUa9o4g%2F200.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="245" frameborder="0" scrolling="no"><a href="https://medium.com/media/5879410b3b14735ac352d44f78ab6cc2/href">https://medium.com/media/5879410b3b14735ac352d44f78ab6cc2/href</a></iframe><p>We need a better way than iterating each possible combination. Or checking if it’s realistic.</p><h3>Taming the Beast</h3><h4>Using Qualitative Data in Design Process: Support Tickets, Chats, NPS Comments, App Store &amp; Play Store Ratings, etc.</h4><p>We create design frameworks to manage complex problems like these. What’s a framework, and how do you create one? Let’s learn by building one!</p><p>We are in the process of building our Design System. The goal of the building this system is to aid designers in:</p><ol><li><strong>Understanding the problems:</strong> For this, we use design frameworks</li><li><strong>Iterate solutions:</strong> For this, we make component libraries and style guides like — UI Kit, Print style-guide, Ad style-guide — which are all documentation of constraints &amp; decisions</li></ol><h4>We start with problems. When in doubt, focus on understanding the problem better.</h4><p>Some context can help us tame the ticket madness. This is where stories of our customers, who used these tickets, came in handy. We didn’t have to look too far — the customer ops. team had detailed stories of these customers, and we had NPS comments &amp; support tickets raised by the customers.</p><p>These stories &amp; narratives can help reveal insights, and validate our hypothesis.</p><p>Let’s take an example of 3 such NPS comments that illustrate this well:</p><figure><img alt="3 example NPS comments from Headout customers, which help us refine the meeting point problem." src="https://cdn-images-1.medium.com/max/1024/0*C7JwOiizRvhh6crx.png" /></figure><p>The meeting point is trouble.</p><p>We can see clear patterns; and use customer’s own words &amp; actions to map their state of mind, abilities, reality, problems, and the flow of events.</p><figure><img alt="How we can find patterns in the NPS comments." src="https://cdn-images-1.medium.com/max/1024/0*OW0D3X5G0hhP1bzJ.png" /></figure><p>At this point, we have a fair amount of data, stories, and evidence for the next step:</p><p>Our old friend — mapping. Here are 3 example maps we could draw:</p><ol><li>Customer who bought the ticket over ~24 hours before the experience</li><li>Customer who purchased the ticket within less than ~24 hours before the experience</li><li>Customer who purchased a combo which may generate a single, two or more tickets ( this leads us back to #1 &amp; #2 as sub-journey maps)</li></ol><p>Let’s see what use-cases emerge, as we try to map our customers’ journey:</p><figure><img alt="Example User Journey map of what all problems the customer may encouter when they do a booking more than 24 hrs before exp." src="https://cdn-images-1.medium.com/max/1024/1*q6obVpqIuMiUmCpDKyRl_w.png" /><figcaption>Example User Journey Map: This helps us find, study, and manage use-cases.</figcaption></figure><p>As we draw our timelines, we get a better view of what happened before &amp; after the problem(s), and how these events relate to each other.</p><p>Designing for the happy path may seem like an obvious step, but what happens on the unhappy paths are constraints for the happy path.</p><p>E.g; Customer reaches the meeting point and realizes they had to print the ticket — there’s nothing they can do now. We can proactively solve this issue by marking the tickets, emails, and remind our customers to print the ticket well-in time.</p><figure><img alt="User Journey Map can help us understand, anticipate, &amp; prevent customer problems." src="https://cdn-images-1.medium.com/max/1024/1*oXUykx0LOIusXdypA-dY1w.png" /><figcaption>Mapping can help us figure how the problem evolved and where it could be solved/prevented.</figcaption></figure><p>This exercise gives us:</p><ol><li><strong>Use-cases:</strong> that we’ll design for, including the problem statements we started with. We use the information/variables and their various states &amp; representations to solve these problems</li><li><strong>User Concerns:</strong> that allow us to make “groups” of these usecases, which, further, allows us to:</li></ol><ul><li>Control &amp; document side-effects (shared use-cases and/or information)</li><li>Allow us to prevent the problem; rather than “fixing” it with reactive support</li><li>Prioritize which user-concerns should we iterate, test, or deliver first (based on frequency, cost, urgency, etc.)</li></ul><p>Let’s pick one concern from our map above — <em>“Where do I need to go?”</em> — to illustrate:</p><figure><img alt="We map variables and their states &amp; representations to User Concerns that we derived from User Journey Maps." src="https://cdn-images-1.medium.com/max/1024/0*J-6-iDhTZPhatVnt.png" /></figure><h4>The First part of our Ticket Design Framework is the definition of the problem landscape.</h4><p>Now, we can ask useful questions to our teams (data, tech, category, support), like:</p><ol><li>How often does this happen?</li><li>How many tickets do we generate every day with these vs these iterations?</li><li>What’s the typical count of people per booking?</li></ol><p>Or to our customers (not verbatim):</p><ol><li>What happened after you got your tickets?</li><li>How did you make sure you’re at the right spot?</li></ol><p>This helps us prioritize and tame the scope of work.</p><p>Now we start to study how these variables relate to each other, and we can make guidelines around how to best design for them.</p><p>Let’s take the example of these variables &amp; the states they may exist in:</p><figure><img alt="Example of making mini-systems to manage information." src="https://cdn-images-1.medium.com/max/1024/0*JVcThy9SdqqEdEjM.png" /></figure><p>Let’s say we have to add another variable to this structure:</p><figure><img alt="Adding another variable is a breeze." src="https://cdn-images-1.medium.com/max/1024/0*FKKiTZ8wGNxT2-4u.png" /></figure><p>Well, that was easy! Also, at this point, we can check for all side-effects.</p><p>Let’s go one step further — what’s the best way to communicate <em>Validity</em>?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RPnxYKSHfzqioGr1.png" /><figcaption>Writing the full date is the best way to communicate validity (for print). We can explore options, document the final decision and the reason for that decision.</figcaption></figure><p>Not only the were we able to understand the problem, the solution (communicate information), and architect the information, but this also allowed us to think harder about the small details.</p><p>This makes iterations more meaningful, and you can quickly check them against your problem statements.</p><h3>Iterating for Solutions</h3><p>Remember our meeting point problem? This is the new version:</p><figure><img alt="Improved meeting point on the Headout Print Ticket." src="https://cdn-images-1.medium.com/max/1024/1*qsPa_ao0oswnAd038OQCHw.jpeg" /><figcaption>An iteration to solve the Meeting Point problem on the Headout Ticket</figcaption></figure><p>Some improvements include:</p><ul><li>Meeting point with landmarks (A &amp; B) in picture and map format</li><li>“Reach Here” is clearer than “Location”</li><li>A link to Google Maps on the mobile &amp; email version, and a scannable QR code to open the link in Maps on the print version.</li><li>Clear instructions on whom/what to find when you reach the meeting point; we often try to include photos of the guide</li><li>Landmarks described in easy to show/say words to help customers locate the meeting point; should they feel lost</li></ul><p>Our guides were hard to spot — another problem highlighted by the NPS comments. So we designed T-shirts for our guides:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*_gdomeR2sZEVIxqs.jpg" /><figcaption>Our brand colour is easy to spot in Europe; where most people wear neutral colours. Name of the City &amp; word “Headout” are visible in front, the word “Guide” at the back (which doubles up as a discount code).</figcaption></figure><p>Here’s what the final tickets look like:</p><p><strong>Example Print Tickets:</strong></p><figure><img alt="Photos of Sample Headout Print Tickets." src="https://cdn-images-1.medium.com/max/1024/0*tW12-SuGH7gO8gG8.jpg" /><figcaption>Sample print tickets (we are still optimizing map colours for B&amp;W print).</figcaption></figure><p><strong>Mobile Ticket Prototype:</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F369376167%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F369376167&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F826303761_640.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="672" height="1366" frameborder="0" scrolling="no"><a href="https://medium.com/media/c8e48bc0cc207a4ce8c455ebf1a9d011/href">https://medium.com/media/c8e48bc0cc207a4ce8c455ebf1a9d011/href</a></iframe><h3>Why use Design Frameworks?</h3><ol><li>Document problems &amp; nuances</li><li>Understand, tame &amp; prioritize the vast scope</li><li>Separate the problem from the solution: We can keep trying different solutions &amp; ideas, without losing sight of the problems. We can test &amp; measure our iterations against these problem statements &amp; use cases.</li><li>This also helps inform Product KPIs and Non-Functional Requirements (for ya’ll PM’s out there).</li><li>Document &amp; understand feedback: Did we get the problem wrong or the solution doesn’t work? Or some other solution is better because of x?</li><li>Help us solve better, by allowing us to isolate the relevant parts and dig deeper</li></ol><p>Here’s (almost) the entire process visualized:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F369376066%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F369376066&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F826303610_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/80c868176a192ff770c40380c0e1e54c/href">https://medium.com/media/80c868176a192ff770c40380c0e1e54c/href</a></iframe><p>Do you see the value of using Design Frameworks at your organization? Does your Design System document problems? What are the parts you find useful or unusable?</p><p>Let me know <a href="https://www.twitter.com/kingsidharth">on twitter</a>.</p><p><strong>PS:</strong> This article is a result of the <a href="https://twitter.com/kingsidharth/status/1175348098584858624">conversation on twitter</a>, followed by a video:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FKHKkF8efyMo%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DKHKkF8efyMo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FKHKkF8efyMo%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/81fde1d368e38f52392263bab91b8a8b/href">https://medium.com/media/81fde1d368e38f52392263bab91b8a8b/href</a></iframe><p><em>Originally published at </em><a href="https://www.64notes.com/design/design-framework-ux/"><em>https://www.64notes.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24ce3141de54" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/design-frameworks-ux-problems-24ce3141de54">Design Frameworks: tame massive scope &amp; complexity</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to make sense of Inherited Design]]></title>
            <link>https://uxdesign.cc/how-to-make-sense-of-inherited-design-17b7495362bb?source=rss-ea17deaeaa97------2</link>
            <guid isPermaLink="false">https://medium.com/p/17b7495362bb</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[t]]></category>
            <category><![CDATA[user-personas]]></category>
            <dc:creator><![CDATA[@kingsidharth]]></dc:creator>
            <pubDate>Mon, 26 Aug 2019 08:17:26 GMT</pubDate>
            <atom:updated>2019-09-21T13:31:40.068Z</atom:updated>
            <content:encoded><![CDATA[<h4>How not to throw baby with the bath water.</h4><p><a href="https://www.headout.com/">Headout</a> sells experiences (e.g., tours, attractions, events, live shows) across the world. Millions of customers find &amp; book experiences with us using our websites and apps (products). I recently joined the Headout team to solve design &amp; product problems.</p><p>We found ourselves amid countless requests for “small design changes” that need attention “asap”. Years of such small design changes done asap had resulted in a fragmented, hard to manage design. There was clear design debt, and we couldn’t keep defaulting on it.</p><p>The products support eight languages, and all products evolved with their unique design — from interactions, features to aesthetics. The fragmented state of the design looked like a series of oddly made decisions. The underlying reasons for the design decisions were not clear.</p><h3>The Inevitable Redesign</h3><p><strong>Let’s throw everything away and start from scratch! Amiright?</strong> There were too many problems to solve after all, with new ones emerging each day. If this situation sounds familiar, you’ve inherited a product at a high-growth startup, and you may have arrived at a similar conclusion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DwoZKnmkFMw9nk0J.png" /></figure><p>However, there’s a problem with that conclusion. It suffers from <a href="https://en.wikipedia.org/wiki/Survivorship_bias#In_the_military">survivorship bias</a>.</p><p>Only a live design gets bugs! Unless we’ve evidence that the design is utterly failing its purpose the design works. Overmore, if we’ve successfully added new features to the design for years — the design is extensible and robust.</p><p>It’d be crazy to throw away a system this good without studying it. Not studying it would add unknown risks for the user experience and the business.</p><p>The first step was to study the existing design and find the good (helps the user), bad (user doesn’t care), and ugly (deters the user). While going through the process of studying &amp; redesigning the existing products at Headout, I took notes and here’s what I learned.</p><h3>Let’s begin this process!</h3><p><a href="https://uxdesign.cc/ux-auditing-a-guide-to-empowering-design-decisions-feec9d05e548">Design audits</a> are a powerful tool to study existing products and how customers interact with it.</p><p>However, halfway through writing the audit goals, I realised my mistake. I was missing critical steps. I didn’t know who the customer was. Who were they, and why were they using our product?</p><p>I knew nothing.</p><p>So I turned to another design tool — the one that helps us study, understand, and model our customers (with their nuances and market realities) — <a href="https://www.nngroup.com/articles/persona/">User Personas</a>.</p><h3>User Personas without big teams or budgets</h3><p>We didn’t have months, and a large team to conduct detailed research. Existing UX methodologies are compelling, but they fail in agile and startup environments — where clarity is iterative &amp; asynchronous.</p><p>With the years of data to study, we took an iterative approach to draw our (provisional) personas:</p><ol><li>The existing design</li><li>Recorded user sessions for several critical flows</li><li>Labelled &amp; structured customer support communication (chats, emails, call recordings)</li><li>Data for marketing funnels and their learnings in the paid &amp; organic channels</li><li>Existing knowledge of people who’ve been running operations, customer support, and the marketing department</li><li>Relevant research published by airline, hospitality, credit card, and other companies</li></ol><p>Interview with stakeholders gives us models (that different teams use to understand business or the customer) and a starting point.</p><p>Data from sessions recordings, customer support tickets, recorded calls, NPS rating, App Store/Play Store ratings — helped us verify the initial models and add more details. This process gave us a list of 20–25 attributes that affected the customers, and therefore, our business.</p><p>Finally speaking to 10+ potential users (people who took experiences abroad in the last 6 months, regardless of Headout) helped us reduce the 20–25 attributes to just 7:</p><ol><li><strong>The motive matrix</strong>- Social, Knowledge, Location/Physical, and Leisure. Different flavours of the motive take the front-seat as the user’s journey evolves</li><li><strong>Time at hand / Schedule</strong>: flexibility/rigidity in schedule</li><li><strong>Cost sensitivity</strong></li><li><strong>Specificity / Preferences:</strong> Language, Cuisine, and other preferences</li><li><strong>Comfort level:</strong> Distance from home city/town &amp; prior experience</li><li><strong>Who’s booking:</strong> Is the customer booking themselves? Do they make the decision?</li><li><strong>Who’s accompanying:</strong> Who all are coming along for the experience with the customer?</li></ol><p>These are all the factors that <em>can</em> affect a customer’s decision. These are not “independent variables” (Eg: Cost sensitivity &amp; specificity are heavily co-related); these attributes describe all possible information that a customer would consider while deciding to buy from headout.</p><p>Speaking to the customers also revealed our key-attribute — one attributes that disproportionately affects all other attributes — “Who’s accompanying”. All other factors (price sensitivity, motive, etc.) change depending on who is accompanying the customer.</p><p>Using this insight, we draw our user categories (not personas):</p><ol><li><strong>Lone Drifter:</strong> heading out alone</li><li><strong>Partners:</strong> heading out with the special someone</li><li><strong>Groups:</strong> friends, family, coworkers,</li><li><strong>Family with Kids:</strong> kids change everything</li></ol><p>There are several personas in each user categories, but not all prefer us. From here, specific stories of the customers help fill in details, affinities, and help us narrow down to our provisional personas:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NJoXVG3OsW1AeU9a.png" /></figure><p>Now that we finally have our user, can we begin the audit?</p><p>Not yet. We may know that Sam &amp; Rue are likely to land-up on Headout. We don’t know a lot — when do they do this? How many times do they interact with us? What are the different stages of this story? During this evolution, how did different features of Headout become relevant to the customer?</p><p>We knew the characters, and maybe even a little about their motives &amp; settings — but we are missing their stories.</p><p>E.g., Is Sam more likely to use our search feature than Rue? When would they use it? Would their behaviour be the same?</p><p>To help us understand how the customers’ journey evolves, and what information/action is necessary at what stage, we turn to another excellent design tool — UX Maps.</p><h3>Mapping the territory before building a city</h3><p>There are two specific maps we used — Experience Maps and User Journey Maps.</p><p>Think of experience map has the full-picture story outline. How was the customer’s life before, after, and regardless of Headout? What happens way before the customer even decides to go for experience? How does the journey evolve?</p><p>Experience Map gives us the framework to split the customer story in logical part, see various factors that affect customer’s psychology, and when we zoom-in to specific customer-product interactions — we begin to draw our high-resolution “User Journey Maps”.</p><p>A journey map tracks a specific persona, performing tasks to achieve a specific goal (Sue searching for experience, Pam booking for her and her friends). We detail out each step they take throughout their journey.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pZgJSkl420o-SN7I.png" /></figure><p>With this clarity — we can finally make an exhaustive list of “use cases” — the feature or flow we are auditing, must be measured against these use cases. (Eg: For the search feature, the use cases could be results, global results, no results, multi-lingual, and so on)</p><p>Using this list of use-cases, we can go through each feature and flow and objectively measure how good/bad/ugly the existing design is for the mentioned use-case.</p><p>A report on how well the existing design covers the given use-cases would be our audit report. Finally, we are ready.</p><h3>Design Audits to study, learn, and document existing behaviours &amp; design</h3><p>Coming back to our use cases — this is what a rough derivation looks like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bcjQTj81x7rhpCMR.png" /></figure><p>The questions depend on the goal of your audit, and of course, the background work we’ve done so far.</p><p>We used customer support tickets, customer feedback, stakeholder feedback, recorded session, and some first principle thinking to answer the audit question.</p><p>The result was a lengthy list — what works, what needs improvement, and what’s broken. However, not all issues are equally important.</p><p>We need some way to validate further and prioritise our list. We did this in two steps:</p><h3>Putting the Audit Results in Action</h3><p>First, we rated each step, interaction, and state (within a feature or a flow) on a simple scale:</p><p>-1 — deters the user</p><p>0 — works but needs improvement</p><p>1 — works well as it is</p><p>This helped us rank what parts are more broken than the other (as per the audit).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*P-JeHQVhea1nkCJz.png" /></figure><p>Second, we use conversion and funnel data to see validate &amp; find further patterns in user behaviour. (E.g.: The audit may find step X is broken in the funnel, but how many people get stuck there or abandon? Can we measure the behaviour in some way?)</p><p>These steps helped us focus on the critical problems, keep related issues in mind, and ignore the rest.</p><p>Now we finally understand how the existing design works, and why it works. We also understand the dependencies and edge cases better. Now we can begin to redesign.</p><p>We have much to start our redesign:</p><ol><li><strong>The User Journey Maps:</strong> to help us see the overall problem the design must solve for</li><li><strong>The Use Cases:</strong> from the user journey map, give us a full range of cases to design for</li><li><strong>The Existing Design:</strong> especially the parts that work well (don’t fix what’s not broken)</li><li><strong>The List of Problem Statements:</strong> from the audit report, the parts that don’t work in the existing design</li></ol><p>Now we can make informed decisions about how to redesign each workflow, use case, step, component, and state.</p><p>At this point, we can go back to storyboarding or journey mapping to make sense of audit data; we can also think about a style guide, component library or a design system. However, that topic and the process of redesign deserves a separate post.</p><p>There’s a pattern of questions that repeatedly emerges during the process:</p><ul><li>Should we redesign this</li><li>Should we throw this away?</li><li>Should we keep this to redesign later?</li><li>Should we merge the duplicate functionality here?</li></ul><p>I use the following decision tree to help me find the answer:</p><h3>4R Decision Tree: Should you replace, redesign or refine?</h3><p>You’d need the audit to answer these questions. If you didn’t audit a particular design/feature/element — don’t redesign it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6B4K9PnVNmIB5nhy.png" /></figure><ol><li>Remove whatever hampers the user</li><li>Replace duplicate &amp; weak features with single powerful ones</li><li>Redesign dead-ends</li><li>Refine &amp; reintegrate what works with the rest of the system</li></ol><p>If the answer is not clear or doesn’t feel right, there could be two reasons:</p><ol><li>You need to break down the feature/state/element further and ask the questions again</li><li>Your audit is missing some critical information</li></ol><h3>Closing</h3><p>During my first 60 days at Headout, I took notes of my thoughts, questions, ideas, and discussions. This post consolidates my learnings from those first 60 days.</p><p>The tools I’ve shared here are age-old, and the design industry swears by them. However, instead of following a checklist blindly — I wanted to (re)discover what tools are relevant and why.</p><p>The short deadlines and a small team forced us to rethink how to break free from the prescribed templates, checklist, and processes and find something that works for our market, customer, and business realities.</p><p>Most important — study the existing design and how your customers use it before you redesign.</p><p>How do you make sense of inherited design? Do you use any of the tools I shared? How have you tweaked the process to improve the quality &amp; relevance of the outcome — both in design artefacts &amp; final designs?</p><p>Let me know in the comments or on <a href="https://twitter.com/kingsidharth">twitter</a>.</p><p><em>Originally published at </em><a href="https://www.64notes.com/design/inherited-design-redesign/"><em>https://www.64notes.com</em></a><em>.</em></p><p>Hear or watch the article here</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F4e9rfgrW3Vo%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D4e9rfgrW3Vo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F4e9rfgrW3Vo%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/2946d67f6760daead802f347df4de587/href">https://medium.com/media/2946d67f6760daead802f347df4de587/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fw.soundcloud.com%2Fplayer%2F%3Furl%3Dhttps%253A%252F%252Fapi.soundcloud.com%252Ftracks%252F679967660%26show_artwork%3Dtrue&amp;url=https%3A%2F%2Fsoundcloud.com%2Fkingsidharth%2Fhow-to-make-sense-of-inherited-design-learning-ux-design-kingsidharth&amp;image=https%3A%2F%2Fi1.sndcdn.com%2Fartworks-000596584550-k6dunq-t500x500.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=soundcloud" width="800" height="166" frameborder="0" scrolling="no"><a href="https://medium.com/media/95913392830077a6bb128f28e4d0bf25/href">https://medium.com/media/95913392830077a6bb128f28e4d0bf25/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17b7495362bb" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-to-make-sense-of-inherited-design-17b7495362bb">How to make sense of Inherited Design</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Solving problems & defending margins with just a link: Smart Links]]></title>
            <link>https://kingsidharth.medium.com/smart-links-product-building-d8b5f21c43db?source=rss-ea17deaeaa97------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8b5f21c43db</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[payments]]></category>
            <category><![CDATA[india]]></category>
            <dc:creator><![CDATA[@kingsidharth]]></dc:creator>
            <pubDate>Wed, 20 Feb 2019 13:36:10 GMT</pubDate>
            <atom:updated>2019-02-22T07:27:08.991Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F5BG85JpYCGDBVhhjiYLpw.png" /></figure><h4>Instamojo’s next innovation in link-based commerce:</h4><p><a href="https://www.64notes.com/design/online-payments-for-indian-businesses/">Payment Links</a>, launched in 2016, achieved the product-market fit for Instamojo. Lakhs of MSMEs use Payment Links to collect payments every day.</p><p>Our products are self-explanatory; we spend no money on activating a customer. 80% of our customers adopt our DIY products within 55 minutes of Signing up.</p><p>Payment links &amp; buttons are on the customer’s website; before the competition picks up the phone to call.</p><p>Customers always want more. We love that about our customers — they expect Instamojo to get better. Speaking to them we learned that Payment Links are good but <em>“it could be better”</em>. ❤️</p><h3>The Problems</h3><p>Businesses use Payment Links to close sales. Their customers raise a query over a call, WhatsApp/Instagram chat, SMS, etc. They send Payment links to their customer once the price is final.</p><p>As these businesses grow, they become complex. New departments, processes, and software emerge. Payment Links often need tech-effort to make it work.</p><h4>From being a pain-killer, Payment Links could become a pain.</h4><h3>Making sense of customer requests</h3><p>Our customers range from individuals to companies serving pan-India. We were getting hundreds of feature requests from them.</p><h3>The customer is always right — about the problems they face and they trust professionals to find the right solutions.</h3><p>While taking note of their feature requests, we discussed:</p><ol><li>Why they wanted the feature. What problem would it solve for them?</li><li>How do they solve the problem today?</li><li>If we had the feature today, what else would they need to switch from their existing solution?</li></ol><h4>It’s not enough to take a feature request and build it. There will be no adoption if the switching cost is high.</h4><p>Speaking to them, we learned these were the most important problems they wanted <em>us</em> to solve:</p><ol><li><strong>Dynamic payment amount &amp; timing:</strong> Eg: Advance payment for a commissioned work, early bird/discounted tickets for an event, etc</li><li><strong>Data collection with payment:</strong> Businesses have a stack of departments to deliver the end results. Each department needs data to work. Eg: warehouse, shipping, admission department in school/colleges, etc</li><li><strong>Looking professional &amp; trustworthy:</strong> businesses wanted to change the design &amp; content. This would ensure consistency with their brands</li></ol><p>Out of the umpteen feature requests, we chose to prioritise 15 critical ones. How do we fit that without making everything overwhelming?</p><p>How do we fit this…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/746/0*sxvg_M59GtVhbVkN.png" /><figcaption>Some of the features that we prioritized for Smart Links v1.</figcaption></figure><p>…into this…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/970/0*zMor7P9nyeQBIMdD.png" /></figure><p>…and keep the experience easy &amp; simple?</p><p>Our design team, <a href="https://www.linkedin.com/in/mohamed-omair-ansari/">Mohamed Ansari</a> &amp; <a href="https://www.linkedin.com/in/sreenathkotteri/">Sreenath Kotteri</a>, took this challenge and created magic for our customers. (<a href="https://uxdesign.cc/smart-link-invisible-by-design-497a1365de7c?source=user_profile---------2------------------">Mohamed talks about interaction design process detail here</a>).</p><p>Creating a Smart Link is as simple as creating a Payment Link (renamed to Quick Links).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*88oRq0wCXxc8f8hv.png" /></figure><p>When creating a Smart Link:</p><ul><li>Business critical features come first. Eg: amount, expiry date, etc</li><li>Everything else is optional and grouped where the feature had similar end results. Eg: Data collection features are in one group</li></ul><p>While it’s simple, it covers everything our customers asked for:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GGhUduwIShry6wp3.png" /></figure><h3>The “Smart” in Smart Links</h3><h4>Smart Links are not about more features. They are smart because they understand the intention behind the feature.</h4><p>Let’s take a feature request from our list earlier:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/762/0*CO6vyiDGo-qolAry.png" /></figure><p>At first, the problem seems to be simple — give a checkbox to collect GSTN?</p><p>But the real problem is invoicing. There are other data required for invoicing, apart from the GST Number:</p><ol><li>Billing Address (important for GST Invoicing)</li><li>Shipping Address (sale of a product that requires shipping)</li><li>Billing &amp; Shipping Addresses may be different.</li><li>Company Name</li></ol><p>By clicking one checkbox, the business can take care of all these use cases:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*qlo8B82CD27_EorR.png" /></figure><p>By clicking one checkbox, businesses can collect everything required to generate a GST invoice.</p><p>This creates a problem for the payment experience. The customer making the payment would have to fill 10 fields:</p><p><strong>Shipping Address:</strong></p><ol><li>Street Address</li><li>State</li><li>City</li><li>Pincode</li></ol><p><strong>Billing:</strong></p><ol><li>Street Address</li><li>State</li><li>City</li><li>Pincode</li><li>GSTN</li><li>Company Name</li></ol><p>Smart Links take care of that as well. The only mandatory fields for the customer are the address fields. Everything else is optional:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/829/0*7fbsePGUdzLjGJot.png" /><figcaption>The customer making the payment only has to fill what’s necessary. Businesses can ask for lot of details without overwhelming the customer.</figcaption></figure><h4>Every feature in Smart Links is smart like that 😎.</h4><h3>Results</h3><h3>Within 60 days of launch, 7% of our monthly active users (MAU) adopted Smart Links with zero budget spent on marketing.</h3><p>They created beautiful Smart Links:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6cBUsDvVSde-AA2M.png" /></figure><p>We saw better adoption in the categories we researched &amp; targeted with Smart Links. Smart Link users are serious and more likely to use our value-added services.</p><h3>Defending margins</h3><p>Smart Links solve problems for lakhs of businesses and their customers. It also adds to Instamojo’s competitive advantage in the payments business.</p><p>Consider two things:</p><p><strong>First</strong>, there are companies dedicated to solving the problems we aim to solve with Smart Links. (Dynamic Pricing, Data Collection, and Landing Pages)</p><p>Most of these companies offer their software on a subscription model (SaaS). MSMEs have an unpredictable cash flow and don’t like a monthly/yearly subscription fee. The software is often too complicated to understand &amp; use.</p><p><strong>Second</strong>, the payments business is a low-margin business. With high competition in the market, most payment products suffer margin erosion. Especially when focused on big-ticket customers, where the customer has the pricing power.</p><p>Smart Link solves both these problems:</p><p>For the MSME, it brings the essentials from SaaS products at a predictable price. Pay when you use — they pay 2% + Rs.3 per transaction — no subscription, no upfront cost.</p><p>When they can afford the paid SaaS products, they use webhooks to integrate Payment Links with their favourite products.</p><p>…</p><p>For our customers, we are more than a payment gateway, shipping gateway, or loan gateway. We are partners in their business.</p><h3>While our competition has to slash prices to acquire &amp; retain customers, our customers are happy to pay more for the problems we solve.</h3><h4>Credits</h4><ul><li>Interaction Designer — <a href="https://medium.com/u/c0795dab5d6a">Mohamed Ansari</a></li><li>Product Designer — <a href="https://medium.com/u/2173a49b75e4">Sreenath Kotteri</a></li><li>Engineers — <a href="https://medium.com/u/a85536dbf98e">Ruchita Lodha,</a> Adesh</li><li>Thanks for editing the post — <a href="https://medium.com/u/73d6046bc359">Rapti Gupta</a></li></ul><p><em>Originally published at </em><a href="https://www.64notes.com/design/smart-links/"><em>www.64notes.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8b5f21c43db" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Next Day & Instant Payouts: habit building credit lines for businesses]]></title>
            <link>https://kingsidharth.medium.com/next-day-and-instant-payouts-credit-line-ux-5e81c7bcb6fe?source=rss-ea17deaeaa97------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e81c7bcb6fe</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[credit]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[@kingsidharth]]></dc:creator>
            <pubDate>Tue, 12 Feb 2019 03:47:11 GMT</pubDate>
            <atom:updated>2019-02-12T03:47:11.734Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2iDDybL7oAqPISFdnxUHKA.png" /></figure><h4>Making of credit lines that disbursed over ₹100 million in 60 days of launch</h4><blockquote><em>“It takes too long for the money to reach my account.”</em></blockquote><p>Businesses use Instamojo to receive a payment. It takes up to 3 working days for the money to hit their bank account (payout). Settlement cycles are an industry standard (<a href="https://www.investopedia.com/ask/answers/what-do-t1-t2-and-t3-mean/">T+3 settlement cycle</a>).</p><p>This delay is not a problem for a business with sound financial management and a steady cash flow, for a small business, cash can dry up fast. The problem hits hard when:</p><ul><li>The business requires cash to buy inventory</li><li>When the salaries and payables come due</li><li>When digital payments is the only sales channel (most digital payment instrument follow the T+3 cycle) Holidays and long weekends</li></ul><h3>Surviving the Cash Crunch</h3><p>Credit lines from banks are inaccessible to small businesses. For a bank it’s not profitable to focus on small customers. Business owners are also not keen on the lengthy paperwork that a bank requires; they’d rather focus on their business.</p><p>Instead, small businesses use personal savings to start the business and profits to grow it. Family is the only credit line, if they are well-off.</p><h4><strong>Our customers were not asking for faster payouts, they were asking us for a short term credit line to fund their business.</strong></h4><h3>Solving the puzzle</h3><h3>Why can’t the money come faster?</h3><p>Instamojo gets settled in cycles up to T+3 business days. We couldn’t transfer the money if it wasn’t there. Banking infrastructure and regulations are often the bottleneck of innovation in our industry.</p><p><a href="https://www.linkedin.com/in/manik-singla-8a9a0332/">Manik Singla</a> came up with — <strong>Next Day &amp; Instant Payouts</strong>. As the name suggests, these products allow businesses to get money in their bank accounts next day or instantly.</p><p>Here’s how we solved some key problems:</p><h3>Where will the money come from?</h3><p>Our partners (banks &amp; gateways) take up to T+3 days to settle the money to us and sometimes it can take even longer. We cannot send someone the money that doesn’t exist!</p><p>Credit/loan was the most obvious option. Lending money is the easy part, but recollection is hard. Especially when cash flow of the person/business paying back is unpredictable.</p><h3>How much should we lend?</h3><p>These products were targeted towards businesses with cash-flow problems. The cash-flow problems make them a good customer for a credit-line but also deters their ability to pay.</p><p>Our customers had the answer — <em>“Just give me the money you owe me in advance.”</em></p><p>They needed the money when an order came in. <a href="https://www.accountingtools.com/articles/what-is-invoice-discounting.html">The credit limit was the payments they received</a>.</p><h3>When and how will the the repayment happen?</h3><p>The loan is considered repaid when the T+3 cycle is completed. Instamojo receives the money from the upstream partners and settles it to the lender.</p><h3>How much will it cost?</h3><p>When we spoke to our customers they were clear -the <strong>price should be predictable</strong>. It makes the decision making easier.</p><p>For <strong>Instant Payouts</strong> it is 1% of the payout amount. However, for low-margin businesses the price was a deal breaker.</p><p><strong>Next Day Payouts</strong> comes to the rescue — <strong>get the money in your bank tomorrow for just 0.25%</strong>. Now businesses can solve most of their cash flow problems with a little planning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/716/0*ado_nl44wIB31RXy.png" /><figcaption><strong>Next Day Payout</strong> is as simple as flipping a switch:</figcaption></figure><h3>How will we send the money on bank holidays?</h3><p>The standard way to send money to banks is NEFT/RTGS. NEFT doesn’t work on holidays 🤷‍♂️😭.</p><p>We considered IMPS which works 24x7. Every payment could be instantly sent to the bank account. That could work if you’re receiving 10 payments <em>a day</em>. It’d be a lot to deal with if you get 10 payments <em>a minute</em>.</p><p>So bundle them up? Sure but the transaction limit on IMPS is ₹2,00,000. So even more transactions?</p><h4><strong>We turned this design challenge into user delight.</strong></h4><h3>Money at the click of a button</h3><p>We explored the idea of scheduled payouts. Eg: payout all the payments 6 times a day.</p><p>But could we do better? It still may not solve the ₹2,00,000 limit problem. Another concern was the 1% charge. Businesses might not want to put that on auto-pilot.</p><p><strong>We decided to make it a voluntary experience</strong>:</p><ol><li>Select the transactions you want a payout for</li><li>Check charges &amp; fee</li><li>Click a button…</li></ol><h4><strong>…and the money hits your bank account! Nothing is more delightful than money coming in.</strong></h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FpvY0STGS2WQ%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DpvY0STGS2WQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FpvY0STGS2WQ%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/88cbc1a0ee632a4a005451d57e7d26e9/href">https://medium.com/media/88cbc1a0ee632a4a005451d57e7d26e9/href</a></iframe><p>This approach has three advantages:</p><ol><li>Users get to choose the exact amount they want to payout</li><li>We can limit each payout to Rs. 2,00,000 (solving the IMPS problem!)</li><li>Our risk analysis system gets more time to flag risky transactions</li></ol><p>That’s not all, Instant payout is also a habit building product.</p><h3>The Habit Loop</h3><p>Habit loop is based on <a href="https://en.wikipedia.org/wiki/Classical_conditioning">Pavlovian conditioning</a>: A cue that triggers you to take an action and the action has a predictable reward.</p><p>Do this several times over and it will become a habit. You can <a href="https://amzn.to/2SqjCkN">read more about habit loop here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/982/0*bOAfybv2Wbhxh9e4.png" /><figcaption>Simple representation of a <strong>habit loop</strong>. The habit loop is based on <strong>Pavlovian conditioning</strong>.</figcaption></figure><p>With Instant Payouts, this is what the habit loop looks like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZCK2GBoTlPWL8jpK.png" /><figcaption><strong>Instant Payouts</strong> makes a habit loop: customers get a cue when they receive a payment, click a button and receive money in their banks instantly.</figcaption></figure><h3>Results</h3><p>Customers love Instant Payout and Next Day Payout.</p><p>Businesses with low-margins or steady cash-flow prefer to switch on Next Day Payouts and forget about it. Others love Instant Payouts:</p><blockquote><em>“I love Instant Payout, it’s the icing on the cake.”</em></blockquote><blockquote><em>- A baker who uses Instamojo</em></blockquote><h4><strong>Within 60 days of launch we disbursed ₹10+ Cr in loan to our customers. This number has grown over 150% since then.</strong></h4><h3>sampad swain on Twitter</h3><p>Excited to share, #mojoCapital crossed a huge milestone of INR 100+ million #SachetLoans disbursed &amp;amp; recovered within 2 months of launch 💪🏽🚀🇮🇳</p><p>4 months later we disbursed ₹100+ Cr in total:</p><h3>sampad swain on Twitter</h3><p>SachetLoans now in the Rs 100+ crore club (annualized). We have already disbursed &amp;amp; recovered Rs 26 Cr+ in just 4M of launch in Sept18 💪🏽🚀(Probably the fastest growing credit product in 🇮🇳fintech market if not the world 🌎)</p><h4>Credits</h4><ul><li>Next Day &amp; Instant Payouts were envisioned and built by <a href="https://www.linkedin.com/in/manik-singla-8a9a0332/">Manik Singla</a> &amp; <a href="https://twitter.com/@sampad">Sampad Swain</a> and is now managed by by Karthik Vajapeyajula. Insights shared in the post come from their analysis</li><li><a href="https://medium.com/@sreenathkotteri">Sreenath Kotteri</a> was the product and motion designer</li><li>Thank you for proof-reading &amp; editing — <a href="https://twitter.com/hiway">Harshad Sharma</a> &amp; <a href="https://medium.com/@Rapti">Rapti Gupta</a></li></ul><p><em>Originally published at </em><a href="https://www.64notes.com/design/next-day-and-instant-payouts/"><em>www.64notes.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e81c7bcb6fe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[(Re)Design for Business Products: Instamojo Rebranding Case Study]]></title>
            <link>https://kingsidharth.medium.com/re-design-for-business-products-instamojo-rebranding-case-study-f51663533dd?source=rss-ea17deaeaa97------2</link>
            <guid isPermaLink="false">https://medium.com/p/f51663533dd</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[india]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[redesign]]></category>
            <dc:creator><![CDATA[@kingsidharth]]></dc:creator>
            <pubDate>Mon, 17 Dec 2018 11:05:14 GMT</pubDate>
            <atom:updated>2018-12-17T11:05:14.568Z</atom:updated>
            <content:encoded><![CDATA[<h4>Redesigning &amp; rebranding products that people use every day</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YQLP3I0Jp_WErWMcBQFf3A.png" /></figure><p>In August this year (2018), <a href="https://www.instamojo.com/blog/our-big-reveal-introducing-the-new-instamojo/">we launched Instamojo’s new brand (along with a new line of products)</a>. As a part of the rebranding, we redesigned our products across the web and mobile platforms.</p><p>There were many questions to answer, like:</p><ul><li>How much should the design, interface, and experience change?</li><li>How will it affect the business and experience of our existing customers? How much time will they spend retraining their staff?</li><li>How long will it take to conceptualise, iterate, test, and deliver? How much time do we have?</li><li>How many people would we need?</li></ul><p>We had 45 days to get everything done.</p><h3>When do we need a redesign?</h3><p>Let’s talk about when a redesign is unavoidable.</p><p><strong>First—</strong>if the business or product is pivoting. A fundamental shift in the nature of problems or target user mandates a redesign.</p><p><strong>Second—</strong>when the design problems are costing the customer or the business. In most cases, both happen together and do damage before they get noticed.</p><p>The best approach, in both scenarios, is to start from scratch — the user. Anything else would increase the cost further.</p><p><strong>Third—</strong>is rebranding—a shift in tone and identity of the business. It could be a complete overhaul including a name change. Or a refinement of the original brand.</p><p>In the first case, when the brand is changing completely, it may require the design team to delve deeper and rethink all the mental models from scratch. As a result, everything could change—the structure, language, tone, interface, visuals, etc. The scope for such a redesign exercise depends on why the redesign was done in the first place.</p><p>But in the second case, when you’re refining a brand that already works, an iterative evolution of design is a better approach. This helps preserve the nuances and learnings from past.</p><p>Here, “<a href="https://alistapart.com/article/redesignrealign"><em>realign</em></a><em>”</em> is a better term than “<em>redesign”</em>.</p><p>That was the case with Instamojo. We were building on top of our existing brand. We were amplifying what worked, our “Design for India” approach, and realigning our messaging to what mattered most to our customers.</p><h3>How deep did we need to go to redesign?</h3><h4>Our customers’ needs were the most important. Instamojo is used by lakhs of businesses who have a staff of 100s and 1000s — all of whom have learned Instamojo workflows and depend on them every day to get their job done. If we changed one button, several businesses would stop functioning.</h4><p>This is why you don’t see a radical redesign in products built for work or enterprise. Even if they do go through a major redesign, they are always versioned to prevent the shock of switching costs.</p><p>You can redesign, for example, Twitter without such concerns. Sure, your users and marketing departments might hate you for a bit. But no one’s life would change dramatically. (WhatsApp is the opposite).</p><p>Bad redesigns can even kill a vitamin app, especially <a href="https://medium.freecodecamp.org/why-most-redesigns-fail-6ecaaf1b584e">when users hate it</a>. It’s most likely because you were thinking of your needs more than your users’.</p><p>We were redesigning Instamojo in two phases:</p><ol><li><strong>Rebranding</strong>: To be launched with mojoCon and our new brand (this was to be done within 45 days)</li><li><strong>Long-term redesign for scale</strong>: Iterative improvements in the product, design, and experience to make the product more scalable</li></ol><h4>Rebranding</h4><p>Rebranding the public facing Instamojo properties was the first priority. While the marketing and the communications design teams started working on the language, tone and messaging of Instamojo, the product design team was iterating to realigning our design system to the new brand aesthetics.</p><p>While our design system, grown over the past 4 years, deserves a full post; our component library was changing the most. It has several layers:</p><ol><li><strong>Brand</strong> — basic brand identity and usually the first order derivatives (UI colours, type scales, etc.)</li><li><strong>Base</strong> (Elements) — Divs, type usage, shapes, the basic indivisible visual units of the interface</li><li><strong>Objects</strong> — Units which are made up of several elements. Eg: Buttons, Fields, Cards, Tables, etc.</li><li><strong>Components</strong> — Reusable interface models that have a lifecycle and several states. Eg: Cards, Menus / Navigations, Tabs, etc.</li><li><strong>Templates &amp; Flows</strong> — a full structure/layout that is made up of several components</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ofFCXn-3ilFhbY3j6-L5Bg.png" /><figcaption>The older version of the <strong>component library</strong> a part of the <strong>design system</strong> we use at Instamojo</figcaption></figure><p>We have another component library for our public facing landing pages that was rebranded in parallel. Design systems not only help us improve the quality but also deliver faster.</p><p>A living design system helps you:</p><ol><li>Estimate &amp; prioritise the work and scope</li><li>Covers the risk of missing something critical</li><li>Preserve knowledge</li></ol><p>In fact, every progressive iteration gives you a chance to fix past mistakes.</p><p>For example, this was our earlier colour palette:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rsk3zGsEiOmHuOyo7Ae-2w.png" /><figcaption>Instamojo’s old brand colour palette till July 2018</figcaption></figure><p>And this is our new palette:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wH4bwZ_SZa9mAz9JYHv2eA.png" /><figcaption>The new Instamojo brand colour palette launched in August 2018</figcaption></figure><p>And here is the palette we derived from our brand colours:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hc5jpHpose6sEVSQwXdA1g.png" /><figcaption><strong>UI Colour Palette</strong> derived from the brand colour palette</figcaption></figure><p>As discussed earlier, our primary concern was minimising re-learning for our existing customers. What is it that our users hard learned? What would they need to relearn?</p><h4>Procedural Memory</h4><p>Our learning, especially the user-interface learning, heavily relies on muscle-memory (a type of <a href="https://en.wikipedia.org/wiki/Procedural_memory">procedural memory</a>). This is the same sort of memory we rely on to accomplish things like touch typing, cycling, etc.</p><p>There are two relevant parts for our discussion on understanding memory and learning:</p><ol><li><strong>Spatial Memory</strong>: Simply put, spatial memory helps you recall where things are. This is also how you remember what switch is for what purpose in your house. (<a href="https://en.wikipedia.org/wiki/Spatial_memory#Long-term_spatial_memory">Read More</a>)</li><li><strong>Visual Memory</strong>: How things look — relative contrast, size, shape, etc. This is how we learn to read the script of a language and get better at it.</li></ol><p>Since we were not changing the basic structure and architecture of the products, that took care of the spatial memory.</p><p>For visual memory, we focused on the relative contrast of visual components. Either retaining or improving their relative contrast.</p><p><strong>For example,</strong> our buttons for positive, negative, and neutral actions had different contrasts. We improved the relative contrast between the buttons while translating them into our new design system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1B1tjnSbcD7VpNgPRO3Aew.png" /><figcaption>We improved the relative contrast and visual hierarchy for the buttons in our component library</figcaption></figure><p>Moving up the layers, executing and testing all along the way, we accomplished the redesign in 45 days 🔥</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1ifSGv3KK4MfeIYuhPIGfA.png" /><figcaption>Some sample screens from our Android product</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TxZLg1qE7cilIVevmwGOlQ.png" /><figcaption>Sample screens from our desktop web product</figcaption></figure><p>We were a team of 5 including–3 designers (Animesh, <a href="https://medium.com/u/e1741a4c7899">Mj</a>, and <a href="https://medium.com/u/2173a49b75e4">Sreenath Kotteri</a>), 1 engineer (<a href="https://medium.com/u/efdaf6d11d19">Priya Choudhary</a>) and, I. Plus we received all the support we could ask for from the mojo family.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LjAcF6FnpXuh2sS2wXzlqQ.jpeg" /><figcaption>Press coverage of mojoCon 2018, where we launched our new brand and new products. (<a href="https://www.india.com/business/instamojo-expands-its-product-portfolio-launches-mojoxpress-mojocapital-3264199/">Source</a>)</figcaption></figure><p><em>Read more </em><a href="https://retail.economictimes.indiatimes.com/news/industry/instamojo-launches-mojocapital-mojoxpress-in-jaipur/66751325"><em>here</em></a><em> and </em><a href="https://www.livemint.com/Companies/W0L5o2YKBMbf9XxWZEnStM/Instamojo-targets-1-billion-in-transactions-by-2019.html"><em>here</em></a><em>.</em></p><h3>Long-term redesign for scale</h3><p>While designing is a constant exercise, there is design debt to be paid. Simple law of numbers — when the user-base increases rare use-cases become common. The design starts to feel stale and I don’t mean “it’s so 90s” stale. I mean “it’s too painful!” stale.</p><p>We took this opportunity to repay some of the design debt. We are redesigning the business-critical parts of the product in reverse order of usage. This ensures the least relearning for the user. It also gives us buffer to make mistakes as we move towards redesigning heavily used products and features.</p><p>We combine these releases with major product updates or new product/feature launch. The excitement and curiosity of a new product/feature can help with user inertia.</p><h3>“How do I delete this?”</h3><h4>On Instamojo, a merchant can create a Payment Link they can share with their customers to accept payments. There’s a dashboard where the user can manage all their links. Untill earlier this year, we did not allow the users to delete their links. You could switch it off &amp; on. But you couldn’t delete it.</h4><p>While there were a lot of reasons for making this design decision, the most important ones were:</p><ol><li>We couldn’t delete records of something that was sold; it’s hard to refer to them, etc.</li><li>A typical user wouldn’t have more than 100 links (that was true up until a year ago)</li></ol><p>The second reason vanished as we grew multifold. Users had thousands of links. “How do I delete this” for some got so out of hand that they had to create multiple accounts with us just to escape their links 😞. This is a typical example of design debt and if not fixed in time can cost the business a lot.</p><p>We fixed this and several other problems during this redesign. We discovered critical problems by talking to the users (something <a href="https://medium.com/u/c0795dab5d6a">Mohamed Ansari</a> does the best) and going through months of support tickets.</p><p>Today, all payment links are deletable and editable. Something we wouldn’t be able to pull off if not for the resources and scale.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xFjSwHLG-Xef2TWAKHURjg.png" /><figcaption>Our users can now finally delete thousands of redundant links!</figcaption></figure><p>But the dashboard screenshot doesn’t begin to tell the story of the relief our users felt. Here’s how our users reacted by deleting payment links after we launched the feature:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n9yJw6aTkeclU39dAQEyPQ.png" /><figcaption>Deleted Payment Links event spiked after the launch of the feature</figcaption></figure><p>Now that’s a redesign users love.</p><p>We’ll continue to realign the product &amp; design to our customers’ need. For us, redesigning is a continuous process, something we do every day.</p><p>These awesome people helped me edit and tame this post: <a href="https://medium.com/u/e1741a4c7899">Mj</a>, <a href="https://medium.com/u/a85536dbf98e">Ruchita Lodha</a>, <a href="https://medium.com/u/b08a4d69b916">Harshad Sharma</a>, and <a href="https://medium.com/u/73d6046bc359">Rapti</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f51663533dd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing Online Payments for Indian Businesses]]></title>
            <link>https://uxdesign.cc/instamojo-designing-online-payments-for-indian-businesses-375c5edeb509?source=rss-ea17deaeaa97------2</link>
            <guid isPermaLink="false">https://medium.com/p/375c5edeb509</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[payments]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[startups-in-india]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[@kingsidharth]]></dc:creator>
            <pubDate>Wed, 04 Oct 2017 10:46:30 GMT</pubDate>
            <atom:updated>2017-10-20T21:08:34.314Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*txd2y70qYC6GCqxKq3WXyg.png" /></figure><h4>Lessons &amp; challenges in designing a digital product experience for underserved businesses.</h4><p>In the past, a simple computer would need an entire room. Today, you can wear 100 times that power on your wrist. Thanks to technology and the disruption it brings, computers have evolved from enterprise undertakings to consumer products.</p><p>Back in 2012, when <a href="https://www.instamojo.com/">Instamojo</a> started, online payments &amp; ecommerce infrastructure were still enterprise services/departments. They were beyond the financial and technical reach of micro, small, and medium-sized businesses.</p><p>If you wanted to get an online payment gateway, you’d need to negotiate with the banks &amp; gateways. You’ll need a team of engineers to integrate with terrible APIs. None of them would even talk to you, unless you commit to lakhs worth of transaction a month. Only big companies could afford to give their customers an option to pay online.</p><p>There were no wallets, no #DigitalIndia, and our government wasn’t launching a new payments app every month. Most businesses relied on cash &amp; cheques. NEFT was a city-folks thing. Even PayTM was a mere recharge website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gSTIZWL9w2nGEL2J.png" /><figcaption>Today’s Popular Fin-tech startups, back in 2012</figcaption></figure><p>Instamojo started with an aim to simplify payments and ecommerce. We wanted to make payments as simple as sharing a link.</p><p>Upload your file, put a price, and you will get a link. Put that link in your email, blog, SMS, practically anywhere. Your customers can click &amp; pay. You’d get the money directly in your bank account. It was that simple! There was no paperwork involved anywhere in the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Lw8huRP5QdAAMRvg.png" /><figcaption>Instamojo, Early 2012</figcaption></figure><p>At that point people compared our product to <a href="https://gumroad.com/">Gumroad</a> &amp; PayPal. We admired both. Gumroad did the same thing — sell digital files. PayPal was the king of online payments back in the day.</p><p>But over the years we learnt that what works for the western audiences doesn’t necessarily work for Indian audience. The demographic, abilities, tech, language, mental models, regulations — everything changes.</p><p>We gradually expanded beyond payments for digital files and now we manage more than just payments for over <a href="http://www.moneycontrol.com/news/business/startup/instamojo-raises-fund-from-japans-payments-firm-anypay-2363617.html">300k businesses</a> (at the time of writing). Each day our customers teach us how to make our product and business better. While most learnings are domain specific; some had big impact, three stand out the most:</p><ol><li>Language &amp; Mental Models</li><li>Structuring the product to keep it lean and future safe.</li><li>Usability vs. Aesthetics, priorities for a young startup.</li></ol><h3>Mind Your Language</h3><p>In early versions of the product, you’d create an <em>‘Offer’</em> to sell on Instamojo. The <em>Offer</em> could be a digital file, event ticket, or a service. You’d get a link for your offer to share with your customers. Your customers could pay with their cards or net-banking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1010/0*9QZ4P2PGXBNFxaBM.png" /></figure><p>We were careless with words, but our early adopters were forgiving. Most were looking for a solution like Instamojo desperately and were happy that we existed. But we hit a ceiling when we tried to reach beyond the tech-savvy audience and grow our user base to beyond 20,000 merchants.</p><p>For some we worked out fine, but a lot of people were expecting us to bring them customers. They were comparing us to Amazon &amp; Flipkart. We weren’t that. We made several attempts to fix our ‘pitch’ — “Your customers”, “turn your audience to customers”, etc. Nothing changed.</p><p>After talking to several existing &amp; potential customers, we realised:</p><ol><li>People who were using us said that they were using Instamojo to ‘collect payments’.</li><li>People who mistook us for a marketplace like Amazon or Flipkart. They were unhappy that we were not bringing them ‘sales’ and not ‘selling’ their products.</li></ol><p><em>“Sell”</em> &amp; <em>“Payment”</em> have different meanings. Words are important.</p><p>You’re not going to be present in person to explain what your product does, words do it for you. From landing pages, to forms &amp; buttons, words tell the user what’s going on. Words tell the user what the product is about and what it can do.</p><p>Our iterations with functional copy worked the best. After several iterations over the months, this is what Instamojo looked like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KpZv3b859BPwfhy0.png" /><figcaption>‘Offers’ changed to ‘Payment Links’</figcaption></figure><p><em>Offers</em> became <em>‘Payment Links’</em>. You create &amp; share <em>‘Payment Links’</em> to collect payments. Simple! Yet took us over 20,000 customers and 2 years to reach here.</p><p>This was a small change in product and a big paradigm shift that altered our customers’ experience. How do we know? We never again had to explain why we were not bringing them sales and why there wasn’t a ‘Search’ option on Instamojo. No one asked anymore.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sjD2n1T-WqyntHZc.png" /></figure><p>It changed how we pitched our product, and what people expected of it. Today, our customers teach us how Payment Links can be used. 🙏 ❤️</p><p>Another lesson on the importance of words &amp; language came after we made a small addition to our Dashboard. We added a unit to display aggregate sales and transaction numbers with the title ‘Last 30 days’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/0*cFIEBA8lFwONkGYi.png" /></figure><p>We deployed the change at night, next morning there was a barrage of customer emails and calls asking if we were shutting down Instamojo or their account with Instamojo. 😱</p><p>“Why last 30 days?! What happened?”</p><p>‘Last 30 days’. Last has a lot of meanings and the customer is always right.</p><p>A small change deployed under a minute made the problem go away. We changed it to ‘Past 30 days’, the confused emails and phone calls stopped. Words are design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aiEt9CRY3onYPlvleL0Yag.png" /></figure><p>Rest two are choices that, in retrospect, worked well for the product. You’d notice that the earlier versions of Instamojo looked right out of Web 1.0 world. It looks empty and unpolished as compared to how it looks now:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4d-CThNND_au7HH-.png" /><figcaption>Instamojo Web Product &amp; Aesthetics over the years</figcaption></figure><p>It was a conscious choice to keep it empty &amp; looking like the way it did. The choices weren’t based on what looked good or what was trendy. They were based on priorities, costs, and resources at hand. It helped us ship &amp; evolve fast, and maintain the product with low time &amp; effort.</p><h3>Structuring the Product</h3><p>There’s often a temptation to fill up your new product to make it look more ‘mature’ and avoid the ‘emptiness’. You try to fill up the empty space with features and complexity that your product doesn’t even need.</p><p>Most of the decisions at this point are made on big assumptions with almost no data. Every item in navigation, every “segment” or “vertical” a product has is a decision that brings even more decisions with it. Keep it so simple that you’re almost ashamed.</p><p>Products are like trees. They don’t grow in a day or a year. They are constantly evolving to respond to their environment &amp; interactions. If you fluff-it up today, there won’t be any room left when the real growth comes.</p><p>You will have a lot of paradigm shifts as you design your product, layer-by-layer, over the years. Keep a lot of room for errors. It’s easier to iterate and completely change a simple product. This emptiness is your margin-of-safety, the more the better.</p><p>During 5 years of evolving our product, we’ve had no problems adding more verticals to our product. The product is still evolving today without any notable issues in this regard.</p><h3>Usability &amp; Aesthetics</h3><p>When I joined Instamojo I was the first designer. And the in-house front-end person. For about 2 years I was designing &amp; coding-up the product with Django templates (they’re horrible), javascript, and CSS.</p><p>I had 2 big priorities:</p><ul><li>Design a product that makes sense to the user.</li><li>Make a product that works &amp; ship it fast.</li></ul><p>For a designer, its very tempting to make it look like a million dollar product. It’s tempting to apply everything you’ve ever learned. After all this is what you wanted, to build a product from scratch and do it right. Functional and beautiful like no one has seen &amp; done before.</p><p>But soon you will realise that you’ve taken on a mammoth task. Just to make sure that it makes sense and is functional takes a lot of work. There are endless layers of details that you will miss out and add over time. The requirements &amp; scope of product will change every other day.</p><p>Making it obvious is the goal. Obvious is hard. Sticking to usability principles is the only way to guarantee that your interface is obvious to most people.</p><p>In most cases, it means sticking to the medium’s default design choices — be it web, android, or iOS. Sure you won’t trend on dribbble, but your product will be used. That’s everything.</p><p>Having simple UI &amp; interaction patterns also helps keep the code base small &amp; maintainable. This means speed, which is an advantage your startup should not lose. Plus, your product developers will love you for that.</p><p>For some products, however, aesthetics are a need; not a luxury. Specially <a href="https://www.entrepreneur.com/article/230736">vitamin products</a>. But for a pain-killer product like Instamojo, usability was way above the priority list.</p><p>It was more productive to invest time &amp; effort improving language, understanding mental models, and information architect; than investing it in aesthetics.</p><p>There will come a time when that will change. Aesthetics, visuals, interactions do become important as you try to establish a brand and appeal to a larger audience.</p><p>At about 1 Lakh customers, we started investing in those aspects of product &amp; design. At that scale, we left our early adopter phase way behind and were reaching to merchants who were bringing their businesses online for the first time. Including a majority of non-tech savvy customers, who behaved more like consumers. (Therefore expected a consumer product).</p><p>We upgraded visual &amp; interaction patterns of the product to take it closer to a consumer product than a developer MVP and redesigned our mobile experience. Doing that while staying true to the usability principles is difficult, but we had <a href="https://twitter.com/hvpandya">Hardik</a> who did an awesome job.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/932/0*Wa8RLGbD_7zaiEP-.png" /></figure><p>At the same time, we invested more in understanding our customers. Several people including <a href="https://twitter.com/apurv">Apoorv</a>, <a href="https://twitter.com/iamnam24">Namrata</a>, <a href="https://twitter.com/dalanMendonca">Dalan</a>, and our customer facing teams spent time talking to our customers, testing out prototypes, and improving our product to a point where it could serve double the customer base.</p><p>During customer interviews and field visits, customers emphasised our product and services were ‘easy’ to start with and use. That’s where our claim to be <strong>India’s Easiest Way to Collect Payments Online</strong> came from.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2shPsJzZTWxkt01X.png" /><figcaption>Instamojo Homepage, 2015</figcaption></figure><p><strong>PS:</strong> Thanks <a href="https://twitter.com/Rapthing">Rapti</a> and <a href="https://twitter.com/dalanMendonca">Dalan</a> for editing this. Twice.</p><p><strong>PPS:</strong> We are <a href="https://www.instamojo.com/careers/">hiring</a>.</p><p><strong>PPPS:</strong> ❤️ Some screenshots were possible because <a href="https://archive.org/web/">WayBackMachine</a> exists.</p><p><em>Originally published at </em><a href="https://www.64notes.com/design/online-payments-for-indian-businesses/"><em>www.64notes.com</em></a><em>.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=375c5edeb509" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/instamojo-designing-online-payments-for-indian-businesses-375c5edeb509">Designing Online Payments for Indian Businesses</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>