<?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 Sugato Banerjee on Medium]]></title>
        <description><![CDATA[Stories by Sugato Banerjee on Medium]]></description>
        <link>https://medium.com/@sugato.b?source=rss-96651152f0c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*l8QcX2NwRVQTSNvGwfJCpg.png</url>
            <title>Stories by Sugato Banerjee on Medium</title>
            <link>https://medium.com/@sugato.b?source=rss-96651152f0c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 23:56:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sugato.b/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[How no code borrows from games to alleviate the pain of work]]></title>
            <link>https://uxdesign.cc/how-no-code-tech-built-its-16bn-citadel-turning-work-into-games-sugato-banerjee-4bf16404d6c0?source=rss-96651152f0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/4bf16404d6c0</guid>
            <category><![CDATA[gaming]]></category>
            <category><![CDATA[no-code]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Sugato Banerjee]]></dc:creator>
            <pubDate>Tue, 11 Apr 2023 09:56:02 GMT</pubDate>
            <atom:updated>2023-04-15T11:15:57.720Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>Far from the hype of ‘gamification’, no code platforms quietly copied their best ideas from game mechanics, adding to an advancing mission to turn all work into play.</em></h4><figure><img alt="Animated graphic showing characters having fun while working" src="https://cdn-images-1.medium.com/max/796/1*T7PTM6RNNMqT3sHxJAUoPg.gif" /></figure><p><strong>Contents</strong></p><ul><li><a href="#add7">TL;DR — Summary</a></li><li><a href="#1951">Our Connection To Games</a></li><li><a href="#9dc8">Finding The Games Within The Work</a></li><li><a href="#c6e2">Building Games Worth Playing</a></li><li><a href="#c8d6">What No Code Stole From Games</a></li><li><a href="#b32f">The Future Of Work Is Play</a></li><li><a href="#6c25">Bonus Picks — 5 Must Reads</a></li></ul><h3><strong>TL;DR</strong></h3><p>The market for no code is <a href="https://www.globenewswire.com/news-release/2022/07/31/2489071/0/en/Low-Code-Development-Platform-Market-Size-Was-Valued-at-USD-16-Billion-in-2021-and-Will-Achieve-USD-159-Billion-by-2030-growing-at-28-8-CAGR-Owing-to-the-Growing-Need-to-Accelerate.html">sized at 16bn$</a> (2021) and is slated to grow at a blistering 29% every year to breach 160bn$ by 2030. Is no code a tech revolution or an approach which was been evolving steadily all along? No code’s beating heart was built on the foundation of how we play games, and spoiler alert: the current state has been a long time in the making. The no code industry has already inhaled the codex on games, learning how to alleviate the pain of work. We’ll be wise to copy the approach and study our connection to games in building the next generation of work tools.</p><h3><strong>Our Connection To Games</strong></h3><p>It&#39;s a matter of historical record that when Mark Twain created his account on Medium way back in June of 1896, he was flying well under the radar. After spending a few days not making any headway being accepted into Medium’s writer monetization program, he was stumped. In a fit of unmetered rage, he logged off, cleared his cookies, and uninstalled Chrome. After almost a month of playing hard to get, he circled back to publish his first story (well more like a quip).</p><blockquote><strong>Love what you do, and you’ll never work a day in your life. Work and play are just words used to describe the same thing under differing conditions.</strong></blockquote><p>It&#39;s widely speculated if this was a case of Twain’s understudy pushing Publish prematurely on what was actually a research stub. But Twain never posted his expanded thesis, and for the large part, the post remained ignored by the audience. It didn’t receive any claps.</p><p>Four decades later, Dutch historian <a href="https://en.wikipedia.org/wiki/Johan_Huizinga">Johan Huizinga</a>, was looking for inspiration for his new book and discovered Twain’s micro-post in his feed (a recent algorithm change at Medium prioritising short-form content was partly to blame).</p><figure><img alt="One clap added to Mark Twain’s Article by JH" src="https://cdn-images-1.medium.com/max/173/1*qcx4K31q78NvHPXeW9257A.png" /></figure><p>It clearly made an impression on JH, as the book which went on to be published later in 1935 was named ‘<a href="https://en.wikipedia.org/wiki/Homo_Ludens">Homo Ludens</a>’. Loosely translated — humans love to play. In an exclusive launch interview (circa 1935) organized by the publishers, JH spoke extensively about his inspirations, going on to claim that our culture itself is generated from play. Unsurprisingly, the as-yet-obscure quote by Twain shot to fame shortly after.</p><figure><img alt="Tim_cook60 entered the chat" src="https://cdn-images-1.medium.com/max/588/1*Spb9BZJc66H5RwMD9BjZ0w.png" /></figure><p>It wasn’t until May 18th, 2019 that Apple CEO Tim Cook entered the chat, taking a cold hard stare at Twain’s original research stub. Dismissing Twain’s thesis as <a href="https://www.cnbc.com/2019/05/18/apple-ceo-tim-cook-if-you-love-what-you-do-you-will-never-work-a-day-in-your-life-is-total-crock.html">total hokum</a>, Cook argued that when passion collides with a job to be done, working hard is a natural outcome. The larger the collision, the easier the hard work becomes. Work is always work. There are no playful shortcuts. Pack accordingly!</p><p>I believe what Tim meant was — when you enjoy doing the jobs (no pun intended), the effort you put into working befits the sense of purpose, accomplishment and emotional alignment you get out of it. The jobs become games worth playing. Although I’ll add a disclaimer here — any job can <em>be a game</em>, but not for everybody. People have intrinsic differences, which leads them to evaluate some games as more worthy than others.</p><p>If you have any doubts about how much toil people volunteer for while playing casual games, look no further than <a href="https://en.wikipedia.org/wiki/Gloomhaven">Gloomhaven</a>. Launched in 2015 on Kickstarter, the board game has 17 playable characters, 95 missions, numerous scenarios, a breathtaking collection of playable elements including cards, tiles and tokens, not to mention the “fun” of optimizing your inventory while managing personal side-quests. The rule book itself runs into a hulking 82 pages; I’ve completed entire courses at college reading fewer pages than that. It’s quite likely that the seasons will have changed by the time you step outside after finishing this game. Perhaps not so “gloomy” is that the game went on to sell more than <a href="https://www.ign.com/articles/2018/08/03/gloomhaven-has-sold-roughly-120000-copies-60000-more-being-printed-gen-con-2018">120,000 copies</a> and has been received with widespread acclaim; some even going so far as to call it the <a href="https://www.wargamer.com/gloomhaven/review">best board game of all time</a>!</p><figure><img alt="3 players playing a game of Gloomhave in an elaborate large table littered with cards, tokens and other stuff" src="https://cdn-images-1.medium.com/max/960/1*rCh8efsF-GAspn7PQ86GLw.jpeg" /><figcaption>Playing a game of Gloomhaven. Image Credit: <a href="https://www.reddit.com/r/Gloomhaven/comments/a4rkmq/new_board_game_table/">u/larrydcarter</a> on Reddit</figcaption></figure><p>All this might sound like a crazy exception, and partly it is, but it really isn’t as out there as you might expect. There are dozens of <a href="https://gamerant.com/longest-tabletop-games">similar games</a>, each with its own devoted fan base.</p><p>Another disclaimer is warranted — increasing difficulty of gameplay is inversely proportional to player reach. You might be able to recruit fewer and fewer participants (albeit more fanatical ones) as your game becomes more and more complex. It sounds reasonable that this should be the case right? The longer it takes for players to “find their own game within the game” the higher the odds it will have a smaller (and perhaps more fanatical) audience. This is a choice you make as a game designer.</p><p>But how can the knowledge of games help inform the design of work, the thing we spend a third of our lives doing?</p><h3><strong>Finding The Games Within The Work</strong></h3><blockquote>If you want to build a ship, don’t drum up people to collect wood and don’t assign them tasks and work, but rather teach them to long for the endless immensity of the sea.</blockquote><blockquote>— Antoine de Saint-Exupéry</blockquote><p>Just remember how satisfying it feels to finally complete a long overdue inbox cleanup, or check off that last item on a todo list, the momentary catharsis you experience when you’re designing that pristine structure for a shared project folder (before your colleagues get their claws in). These feelings are the results of game mechanics we unconsciously invent to eat a task at hand. It’s just the way we’re wired to get painful stuff done.</p><p>On the other hand, there is a limit to how well we can manifest these mechanics for each task, and it doesn’t work most of the time (unless you’re in a version of OASIS in <a href="https://en.wikipedia.org/wiki/Ready_Player_One_(film)">Ready Player One</a>, in which case I’d love an invite). Ask a teen to start saving and investing pocket money and that&#39;s immediately labelled a chore (no game). Then ask them to fire up Death Stranding on their PC, and they’re totally game. Ask Dad to choose and he’ll jump at the chance to check on his investment portfolio and get busy re-allocating funds between asset classes. Who in their <a href="https://www.thegamer.com/death-stranding-music/">right mind</a> would want to play a Sisyphean porter delivering mail where the core challenge involves walking hours, balancing heavy cargo, and delivering mail on their back? That’s 60 hours of my life I’m never getting back.</p><p>The task obviously has an intrinsic affinity with an individual. It’s not the same for everyone, and we saw this in the case of our board games as well. Does this mean we can’t ever make playing Investor a worthy game for teens?</p><p>The answer is an emphatic yes!</p><p>As students of our user&#39;s behaviour, our job is to understand that the drive to see the ‘game in the task’ is innate. Unlike in the case of Gloomhaven’s 82-page rule book, where the product targeted a niche audience, the solutions we’re looking to build need more mass appeal — general games. This really aligns well with the current wave of product-led thinking in building products. So we’ll do it by leaning heavily on designing the mechanics of our product so that users can cross over into game territory within our product as quickly as possible, with no extra help.</p><figure><img alt="Graphic showing work as an abyss while the user needs to make a leap to reach Game-topia where playing is the way to stuff down painlessly" src="https://cdn-images-1.medium.com/max/637/1*PSH4a1rb1ErsoXb6Ec4IuQ.png" /><figcaption>Games can alleviate the pain of work</figcaption></figure><p>I can’t stress enough how different this approach is from “gamification”. To me, that’s a term often used to depict the retrograde tactic of building the product first, and later waking up to solve a user retention problem. It makes the whole thing into a sellable framework for consultants. Honestly, anyone whose been in the “gamification” business long enough knows, it solves nothing long-term and drives user habits towards the wrong thing.</p><p>Eric Klopfer, Professor at the Education Arcade at MIT puts it aptly.</p><blockquote>The problem with this approach is that it merely creates chocolate-covered broccoli. The learning and outcomes aren’t tied in any way to the game dynamics. And this simply is not effective in promoting learning or change in any way.</blockquote><p>A game isn’t a magical ploy or a tactic to make broccoli interesting. Rather it’s an outcome you achieve only when your user feels joy in — chomping broccoli; hold the dips!</p><p>Well enough about that now. I just had to get that out of my system.</p><h3><strong>Building Games Worth Playing</strong></h3><p>In the evaluation stage of any product, there’s a brief window of exploration in which a user will suspend judgement and invest time and effort in the hope of the game emerging. In product speak, we know this as the window of evaluation or time to value — beyond which, the user will either decide to abandon further investment (drop off) or become convinced of the value and label the experience as worthwhile (activation). The longer the window a product requires, the larger the risk of losing the user before reaching point activation.</p><figure><img alt="Graphic showing the window of evaluation within which users other drop-off or reach the activation point" src="https://cdn-images-1.medium.com/max/429/1*vfwgqXqhJQlvoN-MS-MFzg.png" /></figure><p>This is an oversimplification. Let&#39;s slow down for a moment to see a bit more detail.</p><ol><li>The point of activation is not a preset point in your user&#39;s journey which you know or plan for before launch, rather it’s a collection of events which the user has experienced which are highly correlated to long-term engagement. If you could directly ask your users, this would be the point at which the whole thing started “feeling like a game”</li><li>The time span of the activation window will vary among user cohorts. Yes, people are different; remember the preset affinity we spoke about earlier? But in general, when you group users into unbiased cohorts the differences should even out, otherwise, there’s something worth investigating there</li><li>If you have more than a single feature in your product, the activation window isn’t one single event but a repeating cascade</li></ol><figure><img alt="Graphic showing the activation cycle for a multi-feature product" src="https://cdn-images-1.medium.com/max/687/1*vtn9HZ7Z0v-PhdIS4eLiDQ.png" /><figcaption>Activation as a continuous cycle</figcaption></figure><p>Now you already know why most no code platforms really shine — they drastically undercut the need for prior knowledge, while still helping you get productive outcomes fast (within hours if not minutes). Unbeknownst to the end user, behind the scenes of those intuitive GUIs, these platforms adopt some pretty uncommon common-sense mechanics to make it feel like a more approachable game. These have the effect of reducing the size of the evaluation window by orders of magnitude and opening up the game, from being accessible to only 1% of people (coders) to almost anyone who can work a mouse.</p><p>There’s a prominent democratisation of access angle here which is what we’re interested in this article. But don’t be fooled for a moment, this isn’t as much about speeding up time to value, ROIs for coders and developers who are scrambling to build their no code competencies to meet demand.</p><h3><strong>What No Code Stole From Games</strong></h3><p>Although there isn’t a common theme or recipe describing all the no code tools out there, each one leans more heavily on one mechanic over another, there are some recurring traits we’ll talk about now. Don’t look at it as an exhaustive list of mechanics though, and I’ll look at adding more over time. ‘Social collaboration’ is a key mechanic which I’ve deliberately omitted as it deserves a larger treatment in itself.</p><p><strong>1. Sprinkle surmountable challenges</strong></p><blockquote>Verily, I say unto thee, if thou removest the user friction, they shall journey on through more swiftly, that they may reach the point of activation with great haste.</blockquote><blockquote>— Unknown</blockquote><p>The common wisdom says removing user friction is a good thing. It reduces deviations from expected behaviour and keeps the user on a steady drumbeat towards Mt. Activation. What we often miss is the flip side(because it seems to have none). <a href="https://medium.com/u/e4694c74f521">Chelsea Thrupp</a> has a <a href="https://uxdesign.cc/why-friction-is-not-the-enemy-of-good-ux-4dbdb042230b">brilliant take</a> on the trade-offs for friction as implemented in TikTok or Tesla which is relevant here. In our zeal to remove too much friction, we can actually rob the user of the satisfaction of accomplishment. Friction when introduced in a planned way can make the user start feeling invested (think stick) in your product. Games understand all too well, which is why they often use two different scales of challenges. They can often introduce notoriously expansive quests or missions, and then at a smaller “daily scale” they keep pricking with small tactically placed friction like managing inventory, and completing side-quests. These allow the user to experience success regularly, and alleviate the burden of exploring the larger challenge.</p><figure><img alt="A man walks with a backpack and a potruding extension (his animated compass) on a mountainous wasteland" src="https://cdn-images-1.medium.com/max/640/1*XaicgNv9tx11QRGq17YQug.png" /><figcaption>A still from Death Stranding (video game). The compass and backpack are your only tools.</figcaption></figure><p>In the Death Stranding universe, you wake up in a world filled with existential problems needing urgent solving — freeing the country’s president-designate being held by a terrorist, delivering crucial cargo over long distances (in manual mode aka walking), and a <a href="https://en.wikipedia.org/wiki/Amerigo_Vespucci">vespuccian</a> megatask of reconnecting an America now gone dark. It also imposes several surmountable challenges to help lock down your focus and keep you from getting disoriented. You can carry a limited load so you need to prioritise your backpack inventory to survive (or usually die). You have limited endurance and balance, so you can’t go on steep terrain. Rain is a dangerous time accelerant which hyper-ages anything it touches and thins the membrane between the world and that of the dead, so plan ahead to stay far from rainfall. Got it? It even turns your bladder into something you need to manage as a weapon to fend off ectoplasmic entities along the way. These mechanics are not accidental. They’re deliberate constraints placed as a continuous stream of micro-challenges (read ‘good friction’) which offer you a chance at satisfaction at every turn, all the while progressing onwards in the larger mission.</p><p>Now let’s see how Zapier does this beautifully with somewhat less audacity. In Zapier, you can create Zaps (steps of interconnected actions) to build workflows and solve a problem like automating a large repetitive task. But each logical step is constrained to a selection from one of 26 prefabricated blocks.</p><figure><img alt="Graphic showing a blank space in a workflow within Zapier where a block must be added" src="https://cdn-images-1.medium.com/max/705/1*pindgbkvMnq4MlIaeBSS7A.png" /><figcaption>Creating a Zap in Zapier by selecting from prefab blocks</figcaption></figure><p>These constraints keep the beginner from going nuts trying to learn a hundred open canvas ways of implementing one action, something insurmountable. You have the pleasure of stringing together multiple blocks (each simple to understand in themselves) to get the result you want. The problem of creating the entire workflow might be hard, but selecting a block along the way, dragging and snapping it into place at each step isn’t. With each blocky step forward you construct one of the walls of your own bespoke Lego house. You experience the joy of overcoming a surmountable challenge, all the while proceeding towards your larger goal, getting more and more invested in the platform, and prone to activation. Just imagine how satisfying Zapier would be if it decided to eliminate all friction and pre-build the entire library of automations itself. It would also mean having a paltry 1000 instead of the millions of automations, it’s users have hand-built over the years by investing their own time on the platform.</p><p>🕹️ <strong>Zapier</strong> has over 3mn users and is a <a href="https://www.forbes.com/sites/alexkonrad/2021/03/08/zapier-bootstraps-to-5-billion-valuation/?sh=13c780f11c8e">5bn$</a> platform built on breaking large problems down into surmountable challenges.</p><p><strong>2. Create permanent scaffolding</strong></p><p><a href="https://en.wikipedia.org/wiki/Scaffolding">Scaffolding</a> is a term commonly used in construction. These are the metal or wooden grid of hollow pipes and beams which are mounted around a structure being erected, making it easier for workers to access difficult-to-reach parts of the building. These are usually temporary and come off after the project is complete.</p><p>In the software world, you constantly see scaffolding in games and productivity tools where a dense or complex function is abstracted into a simplified super layer.</p><p>Traditional mouse and keyboard work best for playing top-down perspective games like Diablo 3. The situation changes drastically when players join in from consoles like Playstation and Nintendo Switch have joysticks to control motion and aim. Studies have shown that console controllers are at a disadvantage compared to PC mice. So what do we do, Diablo 3 implements something called ‘<a href="https://www.esports.net/news/aim-assist-in-fps-the-case-for-and-against/">aim-assist</a>’ for console players which scaffolds the usability gap and helps console gamers have an ‘even’ experience. It’s fair to say how even this scaffolding really is, is <a href="https://www.pcgamer.com/would-you-play-an-fps-with-a-controller-if-aim-assist-helped-you-win-more/">hotly debated</a>.</p><figure><img alt="A screen grab from Diablo 3 showing the ‘auto aim activated’ as an overlay" src="https://cdn-images-1.medium.com/max/1024/1*LLNz6Qg4GTp34qu74LH0jw.png" /><figcaption>Diablo 3 enables auto-aim for players using console type game controllers</figcaption></figure><p>With Teleport (a no code webpage designer), there’s an example I like to give for scaffolding — how you can create a button animation for a web page. So elements in HTML have these states for defining how the element’s appearance changes when a user interacts with it. Coders implement this interaction in the underlying CSS code using something called pseudo-classes. But Teleport doesn’t want you to learn CSS. Using a graphical interface, it facades the underlying complexity, making customizing the appearances for all the interaction states as simple as clicking a button. This is an example of permanent scaffolding, where the abstraction layer is frozen on top of an underlying functionality to simplify interaction and boost speed.</p><figure><img alt="TeleportHQ’s graphical editor is shown with a clickable easy way to switch button states" src="https://cdn-images-1.medium.com/max/1024/1*kHoz599Bu7QiCpPbEJ3csw.gif" /><figcaption>TeleportHQ hides a web page’s inner CSS complexity of changing a button’s colour when a mouse hovers over it, with a simple graphical editor</figcaption></figure><p>This might seem similar in intent to constraints, and it is, but the approach is to create a 1:1 replica of the underlying functionality.</p><p>🕹️ <strong>TeleportHQ</strong> is an exciting new web design tool fighting against the no code tide of vendor lock-in, allowing you to port your work to any platform. They recently closed a <a href="https://teleporthq.io/blog/teleporthq-raises-2-5-million-in-seed-funding-from-one-capital">2.2mn$ funding round</a>.</p><p><strong>3. Disclose complexity progressively</strong></p><p>Progressive disclosure is a well-understood interaction strategy where the system initially reduces choices for the user to select from by only showing the most relevant options. Over time additional features or options may be exposed. New users benefit from this approach facing less need for upfront investment and reduced chances of getting overwhelmed and consequent drop off. From our multi-featured product activation example earlier as well this seems to fit in perfectly as a continuous process of discovery.</p><p>While tutorials or training episodes are used in many games, almost all games use a system of levels to ramp up the complexity as players get more conversant with an environment.</p><figure><img alt="Screen showing a speedy new purple enemy being introduced to the user at level 33" src="https://cdn-images-1.medium.com/max/640/1*1xmCqfPs1EcVwYtI0wX2sA.png" /><figcaption>Bomber Friends (mobile) ramps difficulty progressively by introducing new and faster enemies at higher levels.</figcaption></figure><p>A good example of progressive disclosure within Bubble (a no code for full-stack web apps) is the plugin system. Using plugins, Bubble keeps its core interface simple, while keeping additional features hidden away. As users come across a use case which requires a plugin, they can simply choose to add it from Bubble’s vast marketplace.</p><figure><img alt="A screen grab of Bubble.io’s marketplace of plugins" src="https://cdn-images-1.medium.com/max/680/1*jZYM9Uns5TTv7NGI46K4FA.png" /><figcaption>Bubble’s marketplace include both official and community contributed plugins. Add only what you need</figcaption></figure><p>As the user becomes comfortable integrating the first plugin into their project, they can add the next and the next, and the complexity grows progressively from there-on.</p><p>🕹️ <strong>Bubble</strong> has over 350 plugins and is one of the most feature-complete no code app development stacks in the market.</p><p><strong>4. Realtime Feedback</strong></p><p>Coders have it hard. Often they have a long wait between making a code change and then compiling, packing, integrating their change, and triggering the right scenario to finally render the impact. The cost of this is reduced experimentation, and developers tend to create changes in larger-sized chunks to reduce the overhead cost involved in rendering. Things have been easier lately with the advent of DevOps-friendly strategies like hot module reload for web or app development or Android Studios’ instant run, but games can wipe the floor with all of them when it comes to giving feedback en rapidé.</p><p>In Hearthstone, a turn-based strategy game, playing cards take on new meaning as they move around, glow, or fall asleep, literally acting out the actions you command them to make. Characters speak out loud with witty remarks, reaffirming when they get hurt or make an advance, and tooltips and overlays are thoughtfully scattered all over the interface to guide you about the next action. It just makes the whole experience that much more intuitive from the get go.</p><figure><img alt="Player in hearthstone dragging cards onto the deck to attack their opponents" src="https://cdn-images-1.medium.com/max/600/1*q0KFc0i5uGFss2e2F1oWvQ.gif" /><figcaption>Hearthstone breathes life into its cards with animations which create an almost tactile feeling of the character interactions</figcaption></figure><p>Carrd.co is a no code landing page generator. One of the things it also does is give proactive feedback between actions. Say you’re trying to move a stack of button elements, it will highlight the allowed drop points on the screen with subtle highlighter bars.</p><figure><img alt="A screengrab from Carrd.co showing how snappable edges light up when a user picks up an item to drag it to a new location" src="https://cdn-images-1.medium.com/max/975/1*WsdlSm3MgLhq157Ffz50zA.png" /><figcaption>Carrd’s interface prevents frustration by giving visual hints about where a user can successfully drag an element</figcaption></figure><p>With feedback in advance, the user can be clear about what options she has even before she can make a mistake. This kind of visual hand-holding is crucial to speeding up trial and error and allows the user more time for creative exploration. Ultimately this is a good user experience, especially for a user with no experience in layout organization.</p><p>🕹️ <strong>Carrd </strong>is a bootstrapped no code startup which scaled to +1m$ in ARR, and currently hosts over 4mn landing pages.</p><h3><strong>The Future Of Work Is Play</strong></h3><p>No code is a narrow subset of a larger category I like to call ‘playable tech’. These are products which are generally designed to obviate the need to understand the product itself and help users with little to no prior experience to start getting outcomes right away (even if they’re scratchy) and then iterate fast. No lengthy tutorials, no reading up user manuals, paging through lengthy how-to books, or taking an online class. Play tech is immersive, (good) challenging, backgrounded, continuously self-explicatory, and often built around engaging communities that expand the platform. They help the user adventure as far down the rabbit hole as they’d like, with an oxygen tank and a hard reset button.</p><p>The good thing is this kind of tech is becoming more and more ubiquitous in almost all domains— whether it’s Canva for graphic design, Memberstack for building monetizable communities, or Biteable for creating product explainer videos, Notion for organizing work, <a href="https://www.nocode.tech/tools">the list</a> is endless.</p><p>We’re in a full-blown arms race to background software and forefront outcomes and I for one can’t wait to see playable <em>tech over our work</em>.</p><p><strong>Bonus Picks — 5 Must Reads</strong></p><ol><li><a href="https://www.asktog.com/columns/011complexity.html">The Compexity Paradox — </a><a href="https://www.asktog.com/misc/mailer.html">Bruce Tognazzin</a></li><li><a href="https://www.resonant.games/">‘Resonant Games’ by Eric Kloper</a></li><li><a href="https://thebeautifultruth.org/life/creativity/constraints-creativity/">‘How can constraints enhance creativity’ by Arielle Domb</a></li><li><a href="https://bingschool.stanford.edu/news/mark-lepper-intrinsic-motivation-extrinsic-motivation-and-process-learning">‘Intrinsic Motivation, Extrinsic Motivation and the Process of Learning’ by Mark Lepper</a></li><li><a href="https://www.theatlantic.com/technology/archive/2011/08/gamification-is-bullshit/243338/">Gamification is bullshit by Ian Bogost</a></li></ol><p><em>Enjoyed this article, see something I missed or have a differing viewpoint? I’d love to hear from you. Let me know in the comments below.</em></p><p>Image Credits: Images by <a href="https://www.freepik.com/author/catalyststuff">catalyststuff</a>, <a href="https://www.freepik.com/author/upklyak">upklyak</a> on freepik</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4bf16404d6c0" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-no-code-tech-built-its-16bn-citadel-turning-work-into-games-sugato-banerjee-4bf16404d6c0">How no code borrows from games to alleviate the pain of work</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[Autosave stole my creativity, then tried to cover it up]]></title>
            <link>https://medium.com/design-bootcamp/autosave-stole-from-me-then-tried-to-cover-it-up-d5740bd39f59?source=rss-96651152f0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5740bd39f59</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[empathy]]></category>
            <category><![CDATA[visual-design]]></category>
            <dc:creator><![CDATA[Sugato Banerjee]]></dc:creator>
            <pubDate>Mon, 27 Mar 2023 13:44:43 GMT</pubDate>
            <atom:updated>2023-03-28T07:14:07.713Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hKd-oQeDZSXD-IiWQME67Q.png" /></figure><blockquote>By distancing me from my choice of saving (or not saving) my work, paternalistic implementations of autosave have weakened my ability to evaluate quick, explorative edits and dump them when they don’t work. The cost of creativity just went up.</blockquote><p>I pride myself on being an early adopter when it comes to trying out tech. I’m not bleeding edge by any imagination, so you won’t find me pulling early alpha software from Github or compiling my own Linux kernel any time soon. But show me a shiny new PowerToy for Windows and I’ll install it just for the kicks. Tease me with a snazzy waitlist page for a new Figma plugin, and my email is yours. If Gmail showed me a new banner asking me to enrol for experimental features (Labs), you can consider that banner clicked in <a href="https://www.pcworld.com/article/528196/article-6471.html">March 2009</a>. You get the drift.</p><p>So when autosave as a feature started becoming more universal to web apps, I was excited. Finally, I was rid of all those jarring “You forgot to save your changes” prompts. Those very prompts had saved my life on numerous occasions, but never again would I need to be obsessed with Ctrl+S’ing through every line, re-punctuation or reformat. It was just always there, ready to help, pleading to be taken for granted…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/594/1*7GxhRF8v4ccRMPoQWZBBgA.gif" /></figure><p>… and I did it, and it was good!</p><p>After almost a decade of experience living alongside this particular innovation, I’ve developed a bit more salted perspective on the matter. It’s been on my mind for a while before I could put my finger on it, but if you’ve read this far, I have an inkling you feel it too.</p><p><strong>Yeah, I Was This Stupid</strong></p><p>Everything is a web app nowadays, and more often than not, the autosave philosophy is baked right in as a hard default. I can’t seem to overemphasize how different this is from having a preset but user-changeable default, but I digress.</p><p>I have this Google Sheet I use to calculate my taxes. It’s quite a large document with several tabs and takes me quite a bit of time to update. So here I was — an hour into making some updates when I was struck by curiosity. What if I opted for the ‘New tax code’ as opposed to the ‘Old’ one this year — would I end up saving on tax? It was worth checking out. I opened a reference site and set out making a heap of changes. At the end of a long session of tab switching and furious refactoring, turned out, no, it didn’t save any money. Ughhh… quit browser!</p><p><strong>Undo Won’t Help You</strong></p><p>I didn’t come back to the document until the next weekend. When I did, I was greeted by a monster. Instead of the beautifully organized and formatted spreadsheet that I knew and expected, what bloomed before me was a disfigured toothless pirate, hacked-together cells, scrawls of temporary formulas everywhere and an ominous bottom line flashing the higher tax I had to pay with the ‘New tax code’. Of course, my immediate instinct to hammer on Ctrl+Z wildly yielded nothing. Google Sheets had already thrown away the undo history from last week. “Okay no problem, this is what version histories are for, and I know Google has ’em. So let’s do that”</p><p><strong>The Cover-Up — Version Histories Are Garbage</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/465/1*On46_Aow1lDccQ34HlSJvA.png" /><figcaption>An inscrutable minute-by-minute version history courtesy of autosave</figcaption></figure><p>This is where true grief actually struck me. The documented history had collected dozens and hundreds of versions, some within the same minute from the day I last edited the file. I slowly and cringingly moved down the version timeline, with each one showing fewer and fewer discernable differences from my memory of the original. I finally settled on restoring a version which felt sufficiently “familiar” to me as the work I had done before getting curious.</p><p>The truth is, to this day I have no way of being sure if I’ve done right by my taxes or stuck with a Frankenstein hybrid with undetectable bits of the new tax code hiding inside some cell or tabs of the old.</p><blockquote>Recently I found an even more nefarious scenario where autosave can actually corrupt my data altogether. Google Sheets has some incompatibilities with Excel in terms of formulae (e.g. FILTER), and I have some files on a shared folder on my desktop which are synced with Google Drive. Now whenever I open a file created in Excel on Google Sheets, the formulas get replaced with garbage dummy functions. To add insult to injury the file autosaves on me without warning and Drive faithfully syncs back the corrupted file back to overwrite the original on my desktop.</blockquote><p><strong>Autosave Just Raised The Cost For Exploratory Edits</strong></p><p>Yes. I know. My fault. I didn’t create a new file for doing all the dirty experimentation. I own that. But here’s what befuddles me about it the experience. <strong>Since when did it become okay to not differentiate between user-committed updates and autosave updates? </strong>More on this later.</p><p>After this incident, I’ve become extremely conscious of the higher cost of creating test changes or temporary edits. Earlier I could simply scribble to my heart’s content all over a document with my red “idea” crayon, knowing with certainty that I was just a single “quit” button away from resetting everything back to normal. It was like having a transparent glass overlay protecting my original until I was ready to commit. Now there was all this added ceremony in the default approach — create a duplicate file (or create a named “version”) like you would with photocopying a piece of paper first, before getting creative. This is screwed up to me. It’s clearly extra effort and subliminally feeds into fewer “quick experiments” when it doesn’t warrant the botheration of following through with the new “default” copy-then-scribble approach.</p><p><strong>Autosave Isn’t The Enemy. It’s The Implementation.</strong></p><p>For all this ranting, I’ll be the first one to admit that I don’t want to go back to an autosave-less (is that even a word?) world. I’m only saying that autosave as it stands today is an incomplete user experience, and there are some simple complementary features which should be considered alongside any autosave implementation.</p><ul><li><strong>Persistent undo</strong> — this one is so infuriatingly simple. When you’re saving a file without confirming the user&#39;s direct commitment, you should also compensate by providing a longer leash on undos. When you undo a change one step at a time, the visual UI actually jumps to each point of change to show you what changes you just undid. This kind of feedback just isn’t afforded while traversing a jumble of garbage (well we might as well call it that) auto-saved versions. It makes the recovery state so much more intuitive to achieve. Code editors like Visual Studio, now deceased Atom (long live the Atom) and especially Linux’s text editor VIM which by the way also featured autosave, actually invented persistent undo a long time ago. Heck, Google even has a <a href="https://patents.google.com/patent/US20140258228">patent</a> on this dating back to 2014, so am I really asking for the moon here?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h35Vwygk45uRH2sXFiQVcw.png" /><figcaption>Visual Studio Code restores the undo stack when you re-open a file</figcaption></figure><ul><li><strong>Differentiate between manual commits and autosave </strong>— again, this one is just a dash of the blindingly obvious. Bring back the option for users to create manual saves and create markers in the version history to highlight them separately from autosaves. I’d really like to know the stats on this one. In fact, let’s have a contest — how many people actually use the ‘named version’ feature as compared to the number of people who inadvertently hit Ctrl+S out of muscle memory to save their work? I’d wager the latter would win by a mile with a smile to boot.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/309/1*mRfSHpCXIC7RskUEBQcWmg.png" /><figcaption>How manual save points could be tagged and segregated</figcaption></figure><p>Ultimately, when a UX designer is bent on precluding a simple opt-out for autosave, it’s kind of important that he also has the vision to include these complements which leads to a more complete experience.</p><p>As always with great paternalistic design, comes great responsibility.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgrid.is%2Fembed%2Fsurprise-box-tqu29C1uR16w%3A3ro9nUaKw&amp;display_name=GRID&amp;url=https%3A%2F%2Fgrid.is%2F%40sugato.b%2Fsurprise-box-tqu29C1uR16w%3A3ro9nUaKw&amp;image=https%3A%2F%2Fgrid-is.imgix.net%2Fthumbnails%2Fb6abb6f4-2d6e-475e-b0fb-7ae8f6751a2b%2Fd99c9396-df28-4f5e-bae2-1cdbdf087ec8.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=grid" width="674" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/f125f23c72cb55a40df874682ad0958f/href">https://medium.com/media/f125f23c72cb55a40df874682ad0958f/href</a></iframe><p><em>Enjoyed this opinion piece, see something I missed or have a differing viewpoint? I’d love to hear from you. Let me know in the comments below.</em></p><p>Image Credits pikisuperstar, Freepik on Freepik.com</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5740bd39f59" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/autosave-stole-from-me-then-tried-to-cover-it-up-d5740bd39f59">Autosave stole my creativity, then tried to cover it up</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When traditional A/B testing just won’t scale]]></title>
            <link>https://medium.com/design-bootcamp/when-traditional-a-b-testing-doesnt-scale-3c09260e245a?source=rss-96651152f0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c09260e245a</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[a-b-testing]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[marketing-automation]]></category>
            <dc:creator><![CDATA[Sugato Banerjee]]></dc:creator>
            <pubDate>Wed, 22 Mar 2023 19:05:44 GMT</pubDate>
            <atom:updated>2023-03-28T07:16:48.380Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Enter Bandit A/B Testing — The Case For Moving Beyond Traditional A/B Testing" src="https://cdn-images-1.medium.com/max/1024/1*pvGJm5FaocwSPJ9gfcu3VQ.png" /></figure><blockquote>The traditional approach can be very expensive in terms of opportunity cost, and drives into a misplaced obsession with statistical significance over outcome. Bandits are a new way of A/B testing which thrives on maximizing returns in low sample sizes and large candidate pools for the price of a bit more statistical complexity.</blockquote><p><strong>Contents</strong></p><ul><li><a href="#8c99">TL;DR — Summary</a></li><li><a href="#4aa1">The Flash Sale (Interactive Case Study)</a></li><li><a href="#174d">Enter The A/B Bandits</a></li><li><a href="#aab2">What About Statistical Significance</a></li><li><a href="#961f">The Bottomline</a></li><li><a href="#0e54">The Catch! Increased Statistical Complexity</a></li><li><a href="#6600">Bonus Picks — 5 articles that will blow your mind about bandits</a></li><li><a href="#dcfa">Surprise Box</a></li></ul><p><em>This is an interactive case study. You might see a delay in loading interactive elements in what appear to be blank spots, especially if you’re on a phone. Be patient and wait for them to appear above the relevant captions.</em></p><p><strong>TL;DR — Summary</strong></p><p>Traditional A/B testing has a scalability problem. Chasing statistical significance for small but meaningful differences in performance can be slow and require extensive sampling. This can feed back into relying heavily on “manual heuristics” to narrow down variants, ultimately delaying the exploitation of findings.</p><p>Modern bandit testing algorithms for A/B tests are based on reinforcement learning and are much savvier at balancing the correctness of outcome and opportunity losses on time lost to experimentation. They can work with much smaller sample sizes and start optimizing for conversions from day one. Market leaders like Google and Netflix have been showing us the way for years, and now even medical trials for new drugs are being rethought in terms of ethics so fewer people have to be placed in the placebo control groups. These methods have also started emerging in more accessible settings like marketing automation platforms — Firebase, VWO, Optimizely, CXL, etc. The time of being comfortable with the obscurity of bandit methods might finally be coming to a much-needed end.</p><p>Classical A/B testing suffers from several scalability shortcomings. At its best, the scale of sample sizes needed for A/B testing can lead to reduced experimentation and poor candidate selection, and at its worst act as a tool for p-hacking. As seasoned product managers and marketers will tell you, they’re well aware of the shortcomings but in the absence of mainstream, alternates rely on these methods more heavily than they’re comfortable admitting. On the whole A/B testing can be particularly ill-suited for certain situations and just plain wrong in others.</p><p>Enough theory. Let’s dive into our case study.</p><p>Oh! Just one more thing, to make our case we’ll work backwards on this one. Instead of talking about solutions, we’ll first develop a benchmark of efficiency in A/B testing the classical way, and then we’ll see how bandits compare.</p><p><strong>The Flash Sale (Interactive Case Study)</strong></p><p>Imagine you’re a product manager at a SaaS startup building a nifty little app which allows customers to prospect leads directly from social media profiles. You’ve built a solid product and you’re super stoked to have gained almost 100 daily active users with your generous free plan. Good job!</p><p>Now you have an upcoming demo day with some potential seed investors next month. You want to put your best foot forward and show some commercial validation, by pushing some of your free app users to convert to the paid plan. You discuss it with your partners and decide that a flash sale with a sweet discount for your users would be the best way to go about it. So you get to work. You work out the marketing copy, code out some inobtrusive nudges with your app, and hit the Execute button. You’re smart, so you also have two variations of your copy running, in order to better maximize conversions. In the classical A/B setup, you’ll be divvying up your traffic as follows:</p><pre>**Variant A** 50 users/day<br>**Variant B** 50 users/day</pre><p>Seems reasonable, now let’s check back on our A/B test at end of day 1.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgrid.is%2Fembed%2Fa-b-test-article-21032023-day1-Dcv%3AT1PQThWTK%3AeyRHltvQ&amp;display_name=GRID&amp;url=https%3A%2F%2Fgrid.is%2F%40sugato.b%2Fa-b-test-article-21032023-day1-Dcv%3AT1PQThWTK%3AeyRHltvQ&amp;image=https%3A%2F%2Fgrid-is.imgix.net%2Fthumbnails%2F0dcbfe4f-53d0-4e15-932b-e7b244796dbd%2F2a34931c-2ab9-4e36-a73a-fdf7f5564dfb.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=grid" width="674" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/3efafb58025dd9baae9b2ab417e8d022/href">https://medium.com/media/3efafb58025dd9baae9b2ab417e8d022/href</a></iframe><p>So that’s no good, but our traffic is quite small so we weren’t expecting any miracles on day 1 itself. Let’s be a good little product manager, and check back after 4 days on how our sale is doing.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgrid.is%2Fembed%2Fa-b-test-article-21032023-day4-S2UhFMozR6KjJ2XavLgjyw&amp;display_name=GRID&amp;url=https%3A%2F%2Fgrid.is%2F%40sugato.b%2Fa-b-test-article-21032023-day4-S2UhFMozR6KjJ2XavLgjyw&amp;image=https%3A%2F%2Fgrid-is.imgix.net%2Fthumbnails%2F4b652114-ca33-47a2-a327-65dabcb823cb%2Fc0859e25-8c52-4319-9242-b1f76cc8f773.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=grid" width="674" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/5e5b3acfce96e3837bd5bfabfd4eee26/href">https://medium.com/media/5e5b3acfce96e3837bd5bfabfd4eee26/href</a></iframe><p>Hmm… we’re seeing a stable conversion rate for both prices, but it’s still not possible to say with a level of certainty that deal B is better than A. Notice that for a usual confidence level of 95%, the p-value needs to go below &lt; 0.05, and we’re weepily far away from that. Let’s not be jumpy yet. The demo day is still two weeks off and we can afford to come back again on day 10 and we’ll probably have better luck.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgrid.is%2Fembed%2Fa-b-test-article-21032023-day10-lM%3A3n9FpQmKa3WuSsFoI7Q&amp;display_name=GRID&amp;url=https%3A%2F%2Fgrid.is%2F%40sugato.b%2Fa-b-test-article-21032023-day10-lM%3A3n9FpQmKa3WuSsFoI7Q&amp;image=https%3A%2F%2Fgrid-is.imgix.net%2Fthumbnails%2F94cfb79f-d169-4262-9add-6b92b05a08ed%2Fc3a1ae35-e38e-47f7-9389-f34ba45a3e32.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=grid" width="674" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/83763629f15bb3f92fed0aacbbe42698/href">https://medium.com/media/83763629f15bb3f92fed0aacbbe42698/href</a></iframe><p>Ok so let’s regroup. At the end of 10 days, we reached 1,000 users and racked up 50 conversions, 20 from variant A, and 30 coming in from B.</p><p>So far, we’ve not assigned a monetary value to our conversions. Let’s do that now. We earned $100 for every converted customer during our sale. For our tally of 50 conversions, that’s $5,000 so far in 10 days. Nice. You can just see your pitch deck selling itself.</p><p>But wait, we’ve not yet optimized our campaign based on our performance stats. If you see the day 10 analysis, there’s no luck yet deciding a winner between the two. Your heart says variant B with its slightly higher conversions should be the horse to bet on, sadly your p-value is still &gt; 0.05 and the power hasn’t crossed the safety line of 80% either. So being logical we continue to distribute our traffic equally among the variants for now.</p><p>I’ll save you the trouble of doing it day by day. Here’s how the performance looks after you ran the experiment over 20 days.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgrid.is%2Fembed%2Farticle-21032023-day-wise-calc-nERzTRg9TZqyrzXERf_nEQ&amp;display_name=GRID&amp;url=https%3A%2F%2Fgrid.is%2F%40sugato.b%2Farticle-21032023-day-wise-calc-nERzTRg9TZqyrzXERf_nEQ&amp;image=https%3A%2F%2Fgrid-is.imgix.net%2Fthumbnails%2F9c44734d-183d-4d9a-b2af-35c445ffe711%2F5af455db-e2b8-493f-88b1-d57d58eca367.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=grid" width="674" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/a34a64f2989ef46e69cbd260f4242264/href">https://medium.com/media/a34a64f2989ef46e69cbd260f4242264/href</a></iframe><p>I can bet that you weren’t too pleased to see that the experiment only crossed the significance threshold sometime between the 16th and the 17th day. This left you almost no time to exploit the higher conversion rate of B which the experiment statistically proved during the 16-day exploration period.</p><p>But what did we really lose? We ran the campaign for almost 3 weeks and got 100 paying customers at the end. That’s $10,000 of revenue in the bank. We know the conversion rates between A and B were different by 2%. So over our total traffic volume of 2000 users during the experiment, 1000 users were exposed to A, which could have seen 20 extra conversions. That’s about $2,000 of missed revenues, and 20% higher than what we ended up with.</p><p><strong>Enter The A/B Bandits</strong></p><p>Multi-arm bandits, turn the A/B experiment structure (not the intent) on its head. In this approach, we’ll not wait till the nth day to take a decision. Instead, we’ll follow a simple pattern in which for every user session, our resident “bandit” or learner will decide which variant to show based on the past success rate of each variant and pick the one with the highest win rate so far. We’ll also add some entropy to the selection process by having X% portion of all selections being randomly chosen instead of always pinning the winning rate.</p><figure><img alt="The bandit algorithm works by dividing traffic between two strategies — bet on the leading candidates, and select a random candidate" src="https://cdn-images-1.medium.com/max/547/1*KypV1rogsttNdGBJ59RGGg.png" /></figure><p>If you see this setup, you’ll recognize right away that the bandit’s main job is to maximize returns from the get-go. It does this job diligently based on an expectation it builds from observing the past. Yes, there are going to be fluctuations in the conversion rate, and of course, the relatively small volumes of traffic going through every day make the measurements (especially initially) highly susceptible to error. But our bandit doesn’t care about statistical significance, he only cares about minimizing the regret of backing the wrong horse over the course of the experiment. By simultaneously exploring (remember the X% randomization I mentioned) and exploiting the variants in alternation, he ensures that most traffic is diverted to the variant which has the highest chance of taking home the prize. This is known as a regret-minimization approach to A/B testing.</p><figure><img alt="Traditional A/B testing has distinct explore and exploit phases. Bandit testing is able scale up exploitation from day 1" src="https://cdn-images-1.medium.com/max/1024/1*-cjyvUBxKahKK-41UidTJw.png" /></figure><p>As a reasonable product owner, you might say —</p><blockquote>“Aah, so you’re peeking at winning candidates based on incredibly small sample sizes (especially at the start), so chances are the test can easily be led astray towards false results.”</blockquote><p>This might be typified in a situation where say variant A hits a lucky patch on a particular weekend, and the bandit keeps feeding more hits to A instead of the better candidate B in the following days, thereby further re-inforcing A and ending up with a false result. Fair point. Let’s park that, and we’ll circle back to it. I promise!</p><p>Another concern you might have could be more ideological.</p><blockquote>“Hey! In a A/B experiment we’re trying to explore and achieve a statistically confident optimum result. We don’t mind losing some money during the experiment period, we’ll gain it back many times over once the experiment ends.”</blockquote><p>I’ll try to answer this with a question — Why do we have to choose? Why can’t we have the best of both worlds? Companies like <a href="https://analytics.googleblog.com/2013/01/multi-armed-bandit-experiments.html">Google</a>, and Netflix have already switched to using bandit approaches to optimise their content and ROI for many years. It’s about time these newer approaches climbed out from the niche and into the mainstream.</p><p>Let’s take a look at the same flash sale problem from the perspective of a bandit approach.</p><p>Below you can see the day-wise traffic distribution from a simulation I ran with the bandit approach.</p><pre>**Assumption**<br>Variant A&#39;s true conversion rate = 4%<br>Variant B&#39;s true conversion rate = 6%</pre><p>The bandit started off with no information about the win rate for either A or B, so on day 1 you can see both variants were getting near equal traffic. Then something happened; variant A hit a lucky patch and got off to a runaway start. You can see over days 2–5, the bandit is allocating more and more traffic to A (just as you had suspected would happen). But what happened on day 5? When the bandit started backing variant A to win with more traffic, suddenly the high conversion rate abnormalities in A started dying out in the face of more exposure, and fast! By day 6, you can see that the bandit has already latched on to B as the winning variant, and is diverting almost 80% of the traffic to it.</p><figure><img alt="Day-wise traffic distribution by the bandit" src="https://cdn-images-1.medium.com/max/1024/1*3232Hn_bS7ElrkABKGkaVg.png" /></figure><p>At the end of day 20, the bandit ended up directing almost 80% (1,600) of the cumulative traffic (2,000) to B over A. This means that compared to our earlier test, we ended up earning 2% more conversions on the +600 extra (30%) users that we sent B’s way instead of A. That’s an extra earning of $1,200 (12%).</p><p>Remember our ideal scenario where we could have netted $2,000 more? Well, we’ve now recouped more than half of that. Real money.</p><p>It’s not foolproof, and it shouldn’t be. The bandit operates on a margin of error the same as classical A/B testing. But don’t take my word for it. Use the simulator below (wait for it to load) to run the <strong>Flash Sales Problem</strong> using the bandit strategy as many times as you like and see the changes in the measured conversion rates and value saved in real time.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgrid.is%2Fembed%2Fa-b-testing-article-bandit-simulato-3BICSus%3ATXqU%3ADByfhBT4g&amp;display_name=GRID&amp;url=https%3A%2F%2Fgrid.is%2F%40sugato.b%2Fa-b-testing-article-bandit-simulato-3BICSus%3ATXqU%3ADByfhBT4g&amp;image=https%3A%2F%2Fgrid-is.imgix.net%2Fthumbnails%2Fdc12024a-eb3e-4d7a-94f8-30727e1053e2%2Fff0a89a1-72a6-4d21-9851-fce9a9b76a6f.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=grid" width="674" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/28689b6d9da45523777a651beac818ab/href">https://medium.com/media/28689b6d9da45523777a651beac818ab/href</a></iframe><p>Pretty neat.</p><p>The multi-arm bandit’s real strength is when you actually have several variants to test. Remember our A/B test is only as good as our candidate selection. In the real world, we might not have enough heuristics to narrow down to only two “good” solutions to test. A traditional A/B/n test would take n-times more traffic to test n-more variants, something we just couldn’t afford before. The bandit strategy side-steps this and feeds into a better way of building products by scaling to test multiple strategies when goodness for candidate shortlisting is not clear at the outset or the relative distances in effect are small (but meaningful).</p><p><strong>What About Statistical Significance</strong></p><p>Still the elephant in the room? Let’s address that now. Contrary to what I led you to believe before, the bandit strategy doesn’t necessarily run upstream of the traditional metrics of confidence intervals and power. Any method is worthless unless we get reliable results.</p><p><a href="https://medium.com/u/d418b99bedad">Shaw Lu</a> has a wonderfully detailed <a href="https://towardsdatascience.com/beyond-a-b-testing-multi-armed-bandit-experiments-1493f709f804">article</a> with the simulations on how well bandit testing achieves scale and accuracy. I’ll warn you that I found it a bit involved myself. To be further convinced, I built multiple bandit problem simulations and ran them dozens of times before writing this article.</p><p>Here are the results for a three-variant problem.</p><pre>**Long Term Simulation Trials**</pre><pre>**Variant A** has a true conversion rate of 5%<br>**Variant B** has a true conversion rate of 15%<br>**Variant C** has a true conversion rate of 10%</pre><pre>Sample size = 1,500<br>Trials = 20</pre><pre>Exploration (epsilon) decay method: Static inverse exponential<br>Exploration factor (residual): 10%</pre><p>You can see that I’ve chosen slightly larger differences among the variants, but also a much smaller sample size considering that the number of variants is now 3.</p><figure><img alt="Metrics from multiple simulation runs with a 3 variant bandit test showed 48% saving in conversions." src="https://cdn-images-1.medium.com/max/1024/1*gad04Z286SzWxtDa9O2KXQ.png" /><figcaption>Data from simulations show 48% saved conversions and statistical significance reached in each case</figcaption></figure><p>This isn’t a large enough simulation by any stretch of the imagination, but as a corroboration of the results from other results like the one from Google and @Shaw Lu, this works really well.</p><p>As was expected the bandit ends up choosing the correct winner B every time, and with a three-variant setup, saves up to 48% traffic compared to a traditional 33:33:33 split for an A/B/C test, by preferentially exploiting B.</p><p>What’s more impressive here is that the bandit even achieves statistical significance much faster than a traditional A/B/C setup would need.</p><p><strong>The Bottomline</strong></p><p>Let’s take a minute to regroup and discuss what the limitations and ideal areas of application are for bandits.</p><p>First, when do we not use bandit testing:</p><ul><li><strong>When there is a lag between presenting the variant to the user, and the measured conversion event — </strong>bandit testing relies on the constant feedback loop of win rates to optimize the next round. A lag in response (e.g. an email campaign) might lead to the incorrect spacing of inputs and wayward results.</li><li><strong>When you need just need statistical significance </strong>— because the bandit hoards traffic towards only the winning variant, the losing variants might never achieve statistical significance.</li></ul><p>Secondly, where does bandit testing really shine:</p><ul><li><strong>When we have small windows of opportunity, low volumes, or limited time frame for exploitation</strong> — examples are flash sales, ad campaigns, news headlines, or feature introductions for any startups with low user volumes</li><li><strong>For long-term testing, where the conversion rates are changing</strong> — bandit A/B testing by definition blurs the lines between testing and deployment. They can be designed to run in a “set-it-and-forget-it” mode over long tenures over which patterns of conversion can change. The random exploration feature keeps an eye on any improvements in previous losers and can give them a chance to recover if warranted.<br>e.g. especially useful for content recommender systems.</li><li><strong>When we have a lot of variants, when we need scale </strong>— the benefits over A/B/n testing multiply as the number of variants you want to test scale. Ultimately the quality of outcomes improves when we rely less on our biased heuristics to narrow down the candidate pool and more on exploration instead.</li></ul><p>Finally, if there’s no such thing as a free lunch, what’s the cost?</p><p><strong>The Catch! Increased Statistical Complexity</strong></p><p>Okay, so I lied to you. With what we’ve seen so far it does seem a bit too good to be true, isn’t it? So where’s the catch? As with everything there is one here too and it&#39;s that bandit testing is sufficiently involved. So much so that most people would run the other way if they had to sit through an explanation of how the bandit testing is actually set up. The exploration feature of the bandit (how the X% of randomization is determined at each step) is a crucial part of the success and efficiency of the testing and it took me quite a while to understand how that works myself. You can look through the bonus section if you’re interested in nerding out.</p><p>The bottom line for me is that regular A/B testing can be very mathematically dense as well. How often do you go about calculating the p-values or the sample size for your test manually? Never. We use ready-made calculators, tools and optimization software to do that for us. Our job is to set the right objective and maximize our returns. The hard statistics are probably best left to automation software and tools which already specialize in doing this. Platforms like Firebase, VWO, Optimizely, CXL, DynamicYield to name a few, already provide the necessary tools for you to start benefiting without becoming a stats wiz.</p><p>To close, what I’ve shared with you here is just the tip of the iceberg, but I invite you to take away the possibility of looking at the testing landscape anew. The next time you think about an A/B test you can discuss more efficient strategies like the ones we saw today, which allow for more variants, less wasted time, and as a consequence locking down better quality outcomes, and losing fewer opportunities.</p><p><strong>Bonus Picks — 5 articles that will blow your mind about bandits</strong></p><ol><li>Google: Multi-arm bandit experiments — <a href="https://analytics.googleblog.com/2013/01/multi-armed-bandit-experiments.html">https://analytics.googleblog.com/2013/01/multi-armed-bandit-experiments.html</a></li><li>Netflix: Thumbnail personalization using contextual bandits — <a href="https://netflixtechblog.com/artwork-personalization-c589f074ad76">https://netflixtechblog.com/artwork-personalization-c589f074ad76</a></li><li>Steve Hanov: 20 lines of code that will beat A/B testing every time — <a href="http://stevehanov.ca/blog/?id=132">http://stevehanov.ca/blog/?id=132</a></li><li>Bandit-Based Ethical Clinical Trials — <a href="https://ieeexplore.ieee.org/document/9715403">https://ieeexplore.ieee.org/document/9715403</a></li><li>Shaw Lu: Beyond A/B Testing: Multi-armed Bandit Experiments — <a href="https://towardsdatascience.com/beyond-a-b-testing-multi-armed-bandit-experiments-1493f709f804">https://towardsdatascience.com/beyond-a-b-testing-multi-armed-bandit-experiments-1493f709f804</a></li></ol><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgrid.is%2Fembed%2Fsurprise-box-tqu29C1uR16w%3A3ro9nUaKw&amp;display_name=GRID&amp;url=https%3A%2F%2Fgrid.is%2F%40sugato.b%2Fsurprise-box-tqu29C1uR16w%3A3ro9nUaKw&amp;image=https%3A%2F%2Fgrid-is.imgix.net%2Fthumbnails%2Fb6abb6f4-2d6e-475e-b0fb-7ae8f6751a2b%2Fd99c9396-df28-4f5e-bae2-1cdbdf087ec8.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=grid" width="674" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/f125f23c72cb55a40df874682ad0958f/href">https://medium.com/media/f125f23c72cb55a40df874682ad0958f/href</a></iframe><p><em>Enjoyed the case study, see something I missed or have a differing viewpoint? I’d love to hear from you. Let me know in the comments below.</em></p><p>Image Credits: Images by storyset, BiZkettE1 on Freepik</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c09260e245a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/when-traditional-a-b-testing-doesnt-scale-3c09260e245a">When traditional A/B testing just won’t scale</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Progress Bars For The Modern Age]]></title>
            <link>https://medium.com/@sugato.b/progress-bars-for-the-modern-age-3a758e71cac8?source=rss-96651152f0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a758e71cac8</guid>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[human-computer-interface]]></category>
            <dc:creator><![CDATA[Sugato Banerjee]]></dc:creator>
            <pubDate>Wed, 18 Jan 2023 05:53:04 GMT</pubDate>
            <atom:updated>2023-03-22T19:26:21.185Z</atom:updated>
            <content:encoded><![CDATA[<p>Originally Published: 10th August, 2018</p><p>1999 was the time of 7th grade bullies, a rap on the wrists for skipping class, and the famous Windows 95 — blue screen of death (lovingly BSOD — pronounced bee-sawed). Our computer science teacher had just now given us a class assignment. Build a program to implement a text-search algorithm in BASIC (an ancient programming language). Having the full hour to develop the program in the computer lab was probably the best part of my day. I’d decided to design a library cataloguing system, and the search feature would be used to find out the status of books in the database. After about a half hour of coding under the white light, and the air-conditioned (“clean room”) of the lab, it was done. I looked at the final program code on screen and reviewed the execution one last time. I enumerated some random book names in the database, and the expected search results popped up instantly. But wait… something was missing. It was a simple program, and still somehow it lacked that spark, or finesse that I wanted it to have (I was already imagining the damn thing as shrink wrapped CD-ROM cases sitting on store shelves).</p><p>Aha! I know what’s missing. I’ll add a progress bar to the search screen, and that will make all the difference. So I spent the next half hour or so looking up special ASCII characters on CharMap.exe, so I could make this…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*_ByVn3VK9Nd_wvTzRCraWA.gif" /><figcaption><strong>LibSYS 0.1 — I’m still looking for investors on this. If you’re a VC reading this… Call me!</strong></figcaption></figure><p>It was an intensely gratifying feeling to have that three second delay before the program spat out the results of a search. It was a fake, of course, but somehow it was satisfying that my program was complex enough that the computer needed three whole seconds to figure out the answer. Yeah! I was sure playing in the big leagues <em>now.</em></p><p>Almost twenty years later progress indicators as user feedback mechanisms have come a long way since Windows 95, in the age of the cloud. While the basic features and the way we use them have remained the unchanged, we now understand a lot more about why and how we respond to different kinds of feedback because of <a href="https://scholar.google.co.in/scholar?hl=en&amp;as_sdt=0%2C5&amp;q=progress+bar&amp;btnG=">extensive formal research</a> on the topic.</p><p>Which brings me to building the case for a better, more human centric device for progress indication in computers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/259/1*6uMaDkN3O4UWHqxtd1Me0w.gif" /></figure><p>It was an intensely gratifying feeling to have that three second delay before the program spat out the results of a search. It was a fake, of course, but somehow it was satisfying that my program was complex enough that the computer needed three whole seconds to figure out the answer. Yeah! I was sure playing in the big leagues <em>now.</em></p><p>Almost twenty years later progress indicators as user feedback mechanisms have come a long way since Windows 95, in the age of the cloud. While the basic features and the way we use them have remained the unchanged, we now understand a lot more about why and how we respond to different kinds of feedback because of <a href="https://scholar.google.co.in/scholar?hl=en&amp;as_sdt=0%2C5&amp;q=progress+bar&amp;btnG=">extensive formal research</a> on the topic.</p><p>Which brings me to building the case for a better, more human centric device for progress indication in computers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/786/1*TpomCYzD0XG6_JPCmBDnEA.png" /></figure><p>Sites like Cleartrip.com have been pulling this trick over on users for years. Whenever you search for a flight or a hotel on the travel portal you’re invited to watch a progress bar as it smoothly moves forward as more and more and more flight options are slowly populated in front of your screen. You can verify that this is indeed a fakebar by doing the following — as soon as the progress reaches about 50% disconnect your computer from the network. You will see that the progress bar continues regardless and all the flight options get populated just fine.</p><p>What Cleartrip has done so well, more designers should look to do. They’ve not only created a more thorough looking search process, which is so important to price-sensitive buyers who need to be assured that they’re getting the best possible deal. So ironically being a little duplicitous can build trust right into the system and brings value to the user, but the territory does come with its risks. If the deception is found out it can have a cascading and disproportionately more negative impact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/952/1*rIa2MS5cAYm8fcZdT3y62Q.gif" /></figure><p>Poor design like in the case of page transition interstitial screens (Yes I’m talking to you Tripadvisor) add no value to the user experience, are easily recognizable as deceit and show a lack of interest in understanding how basic human psychology works.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/494/1*GajLYajMwnECKkllIo7WvQ.gif" /><figcaption>Youtube’s page transition</figcaption></figure><p>I love <em>some</em> of the things Google is doing with it’s Material Design vision. One them is the page transition bar. It is in fact so subtly positioned that most users won’t even notice it at first. Google realised that when people click on a link within Youtube, they’d rather not do with the flash bulbing effect of loading a fresh page from blank. Instead they use asynchronous requests to populate the new content within the existing frame — thereby insisting on a sense of continuity to the whole experience. When the stage is set so well, the progress bar doesn’t need to be flashy — so it’s relegated to a position near obscurity where it adds sub-consciously to the users pleasure.</p><p>In some other cases, the user encounters a progress bar even without the designer planning for it be there. The humble <em>scroll bar</em> might be relegated to the ash heap of obsolescence for Macs (and their gesture touchpads), but they do still stand out on most PC’s. The scroll bar by virtue of acting as a control handle, also doubles up as a progress indicator of sorts by showing you how much farther you have to go in the page. When coupled with the rather common design of infinite scroll used in many applications nowadays, the jitter in the scroll bar position as new content is added at the bottom of the page mid-scrolling, can have disastrous consequences and totally breaks the very illusion of continuity it is trying to achieve. A clear case of how progress indicators need to be carefully tended to. I think the conventional approach of paginating content is a far more cohesive technique for large screen experiences, while infinite scrolls are more suited to smaller touch-only devices where the scroll bar itself is defunct. Conventional pagination also affords more accessibility friendly features allowing users to enjoy more non-linear experiences, where the content length is large.</p><p><strong>Vertical Integration</strong></p><p>Often I see find that for accomplishing a single task I’m presented with multiple progress indicators. Take the example of booting Windows. Over the years the process has seen a dramatic change for the better. In the early days of non-<a href="https://www.google.com/url?q=https%3A%2F%2Fwww.howtogeek.com%2F56958%2Fhtg-explains-how-uefi-will-replace-the-bios%2F&amp;sa=D&amp;sntz=1&amp;usg=AOvVaw1CzZ-siwKaLKHL0GeY54Le">UEFI</a> systems, yes way back in 2009 when Windows 7 was still a thing, we would be treated with at least 3 different progression screens — each with their own progress indicators (see image below).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*Lf-9IqXvqO7pWK06vlgU7Q.jpeg" /></figure><p>This sort of progression is completely counter-intuitive, since it’s taking the user along a cycle of anticipation and disappointment. Every progression screen inadvertently builds a crescendo of tension. When the screen transitions to another progression interstitial, it’s a kind of dishonesty which users take notice of.</p><p>The situation has improved since then, as the BIOS boot and Windows loading stages have been subsumed into a single integrated screen. But then you still wait after logging in before the OS loads your desktop and user specific settings, and sometimes if you’re lucky there’s a third wait when Windows decides to do some more mulling before it even shows the login prompt.</p><p>Now just imagine a workflow in which there could be a single login prompt at the very first step, followed by a single waiting screen in which the system — authenticates you, loads the OS, and then sets up your personal workspace. All of the intermittent stages would be eliminated.</p><p>There isn’t really a specific reason why applications don’t work in this way. It’s usually because there isn’t a concerted thought process towards design at a very early stage in a product. And these kind of decisions unless taken early become an uphill task to undo and therefore a low priority in development tracks. So usually we’re stuck with bolt-on improvements which can only partially mitigate the lasting effects.</p><p>In the case of web apps, this is now the right time for such an integration to happen. Traditionally all browsers have their own progress indicators to aggregate the status of activities occurring on the page. Unfortunately while the browser itself is executing the instructions on the application code, it has no clue as to how long it will take or even far how along the execution has reached. So the browser keeps showing a generic progress-less status indicator and the application itself which has access to the complete information may or may not choose to show a separate progress indication within its framework. What is possible and what should happen now rather than later is the evolution of a more deeply integrated structure for both the browser and the application to exchange information. This need goes beyond the realm of simple consistency in progress indication. It contributes to web applications becoming more deeply enmeshed with their host environments and is something of a necessity as they try to subsume more and more of traditional desktop app territory.</p><p><strong>Milestoning</strong></p><p>If you’ve taken an online survey or filled out a length online college application, you’ll be familiar with a sort of milestone bar which shows up at the top and counts the number of stages you’ve completed and what’s ahead. This kind of feedback in has been <a href="https://www.google.com/url?q=https%3A%2F%2Fwww.ncbi.nlm.nih.gov%2Fpmc%2Farticles%2FPMC2910434%2F&amp;sa=D&amp;sntz=1&amp;usg=AOvVaw0l8_ttRfFQ9EFMQZg4kfft">shown</a> to count towards increased user satisfaction while completing interactive tasks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*ISLCcw8AsUWv6wjsr_jIGA.jpeg" /></figure><p>The beauty of this type of progress indication is that it indicates a certain commitment towards the steps already completed — a sort of failsafe which whispers “it’s ok if you screw up, your efforts are backed up”. This is especially useful in interactive tasks where partial completions are normally expected and are immutable while progressing to a later stage at a different point in time.</p><p>Well it’s about time this sort of milestone representation made it’s way into more non-interactive tasks — where partial results are valuable, if not for anything else but to say that I’m creating a save point I can gracefully recover from. Say I was running a file maintenance script on my local hard drive, which had four stages, each of which takes thirty minutes to complete:</p><ul><li>De-duplicate files</li><li>Remove all files older than 1000 days</li><li>Update index with newly added files</li><li>Check for file integrity errors</li></ul><p>Now if for some reason, I had to restart the device while the 3rd stage was still in progress, I would look at the progress indicator (see below) and see that I would only lose about 1/3rd the work done in the 3rd stage and I would save repeating the previous two steps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/529/1*CerR9rI4bbW6elO-xGjj9w.jpeg" /></figure><p>Now that <em>would</em> be neat.</p><p><strong>Modelling for Time and Not Work</strong></p><p>Well this last one is more a rant than a solution to a problem, but I thought it best to get it out in the open. I think straight out the biggest gripe people have with progress bars is that they’re unpredictable and poor indicators of what they actually want to know — “how much time is this damned thing going to take”. I’ve read endless discussions on the internet (Read <a href="https://www.google.com/url?q=https%3A%2F%2Fdevelopers.slashdot.org%2Fstory%2F13%2F02%2F13%2F0026234%2Fask-slashdot-why-is-it-so-hard-to-make-an-accurate-progress-bar&amp;sa=D&amp;sntz=1&amp;usg=AOvVaw389m7_8SV81fyVmhSxZcLd">here</a> and <a href="https://www.google.com/url?q=https%3A%2F%2Fwww.howtogeek.com%2F139118%2Fhtg-explains-why-are-progress-bars-generally-inaccurate%2F&amp;sa=D&amp;sntz=1&amp;usg=AOvVaw0v5ZWlFSr7l34RJmu6-zAt">here</a>), on why it’s impossible to build a progress bar that actually understands time. I think we’re forgetting that this in fact is a real user need and although it’s a difficult problem to solve, it’s not insurmountable. I think most of the problem lies in software designers having bigger fish to fry!</p><p>Say you’ve created a video in an editing software and you’d now like to export a compressed view of the video into a shareable MOV file. The software gets about crunching, and there’s a progress bar showing the percentage of work completed. Now depending on the software, this percentage could be based on a calculation of the number of seconds of film that’s needed to be processed or the number of bytes of data to be compressed. However how does knowing this information help us plan our work in any way? The partially complete export at say 40% is useless anyways, since it would be garbled and unplayable, so why can’t we simply estimate the time requirement in advance?</p><p>Well there are a couple of factors at play here, so let’s take them one at a time.</p><ul><li>Work loads are computationally heterogenous — this is the first complaint most software designers have, that a certain amount of the work doesn’t use a proportionate amount of time. So apoplectic, are the moments when we’re installing a program and the progress bar gets stuck at 95% for what seems like ages. It just might be that the last 5% of the process takes almost 80% of the total time, but we can’t know that for sure in advance… or can we? Well we can’t know for sure, design is never really about perfect answers. It’s about proximate solutions and that’s what we <em>can</em> do. If it’s a predetermined workload like say installing a standard software package, then it’s possible to do a simulation of the execution time at the developers end and calculate the relate computational effort needed at each activity stage inside the load. This would hardly require more effort than a few simulation runs and could be entirely automated. This effort information could then be stored as meta-data along with the workload, and act as the correct weights to apportion for the length of the time needed on a new target system. In case the workload is not predetermined, like in the case of a video render or a file compression, we could rely on format specific machine learning algorithms to fingerprint the essential features of a file before-hand to arrive at a guesstimate about computational intensity required. This could then be translated in the context of a real-time performance assessment of the host system to arrive at an approximate ETA.</li><li>Computational resources are dynamic — it’s possible to measure the speed of execution of a work load in the past, but the future is indeterminate in that there is a constant flux in the number of resources the system will allocate to the process. Hence it should be impossible to calculate a ETA without it occasionally jerking back and forth. If you’re progress bar is tracking time, this would have the effect of the bar jumping backward occasionally which users would find disorienting. I have a basic problem with this contention that users would find a backward jump disorienting. Firstly I think users would find a progress bar stuck at 95% for hours on end equally disorienting. And secondly, that people would find it disorienting is a result of the status quo in the way the system works. People are used to progress bars which track for work completion rather than time. If you’ve completed 95% of the work, you can’t suddenly jump back to 20%, but in terms of a time value people are constantly attuned to negative changes — like a mapping app which underestimates the original travel time due to change in traffic conditions. So I believe it’s just a matter of standard shift and re-training, both of which require time and energy and most importantly a commitment.</li></ul><p>Well I think that’s enough nagging about progress bars for one day. Whether you agree that benefits outweigh the costs of making any of these changes or disagree, I hope that I’ve been able to create a sort of re-association with regards to the topic. It might seem nitpicky in parts, but I think with the kind of high ambition we’ve been sold on in the current age of user-centered design, I think we deserve to ask for the small things as well — the small things which stand out and shine through as markers of an intense and pathological love for the end-user.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a758e71cac8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Our DNA: Lost in Compression]]></title>
            <link>https://medium.com/@sugato.b/our-dna-lost-in-translation-9b333ac0a378?source=rss-96651152f0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b333ac0a378</guid>
            <category><![CDATA[dna]]></category>
            <category><![CDATA[information-systems]]></category>
            <category><![CDATA[compression]]></category>
            <dc:creator><![CDATA[Sugato Banerjee]]></dc:creator>
            <pubDate>Wed, 18 Jan 2023 05:42:34 GMT</pubDate>
            <atom:updated>2023-03-24T02:21:38.211Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OBGBY3Lc0NJ25r5fjXRs9w.jpeg" /></figure><blockquote><strong>What if we visualize DNA as an environment-dependent code designed for open-ended interpretation and a recipe for a multitude of possible outcomes.</strong></blockquote><p>Take any language — say English. Essentially it is a system for encoding the ideas we have in our minds, into a standardized form which can then be decoded and reconverted back to the original idea in the minds of others. Or so we think. In actuality, no encoding system is completely accurate, and of the decoding, we know from experience that people routinely form very different images in their mind from the words we convey to them. The ideas that we want to communicate are analogue, with very fuzzy borders and during encoding these get reduced to discrete standardized chunks called words on a best-fit basis. The lack of fidelity at both ends means that what we finally end up conveying in English, are at best approximations. The information that is lost can never be recovered, because the English language simply does not have the necessary vocabulary to possibly represent every thought we can come up with. This is true of any language, and in essence this type of encoding of information can be called a lossy compression system — in that it encapsulates the seemingly borderless canvas of an idea into a bounded frame.</p><p>Now take this same idea to the realm of DNA. Clearly DNA has a finite vocabulary made up of discrete words — adenine (A), guanine (G), cytosine ©, and thymine (T), the constituent chemicals. It would be easy to see the same encoding limitations that apply to English would also apply for DNA. The implications of this are profound — in that the living oxygen-breathing organism that you are right now, isn’t what your DNA intended — well not exactly, anyway.</p><p>Ofcourse the visualization of our little argument doesn’t move any further unless we’re able to understand how information losses and misinterpretations creep into the DNA coding processes during biogenesis.</p><p><strong>Decoding the genetic recipe to make the broth</strong></p><p>The process of converting coded DNA to biological processes is a complicated one, involving several stages. To become usable, first different parts of an organisms DNA (master plan) are selectively read to produce RNA (Ribo-nucleic acid), which are like part-specific blueprints. The RNA molecules are then further translated to produce the actual parts — chains of amino acids called proteins. These proteins are then deployed in specific ways to resolve the structure of the final organism. All the reading and translation activities are effected by special proteins collectively called <em>transcription factors</em> at the cellular level; they’re themselves created in much the same way.</p><p>To be able to translate the message encoded in DNA to a usable protein, the translator (transcription factors) within the cell must be able to decode the message to mean something within the environment of the cell — i.e. amino acids, and a specific order in which to string them together. The translator must ultimately be able to compare the amino acids at hand, with the symbolic representation coded in the DNA, and arrive at a Boolean answer — either yes or no to whether a specific candidate is the right choice for addition, next in the protein chain. By now you’ve realized that what I’m getting at is that there is an implied uncertainty here, contingent on the translator’s efficacy in this comparative process. Specialized as they are, they are limited by the discrete information they are provided in the DNA they’re reading off, and the information provided by the DNA which helped create the translator itself in the first place. Both of these domains are limited, and from what we can see from the size of DNA strands, quite a bit so.</p><p>The human genome has about 3 billion letters (consisting of A, T, C, and G), and that seems like plenty. Well there are in total only 20 known amino acids which are used to make any possible protein in the known biological universe, and we know in the world of RNA, each amino acid is represented by 20 words (well, actually there are 64, because of redundancies) of 3 letters each (e.g. AAC, GCA, UCU, etc). This implies that individually the words are simply page numbers which refer to a book. Read the word, find the page number, and then go to the book and read the detailed information on what amino acid I’m referring to. But which book are we talking about here — it’s the preconceived book of information already available with the translator. Since the translator itself is created by a reading of the DNA by a previous generation of translator (and subject to the same rules of the information encoding game), we could say that the DNA has in effect provided a primer to decode itself. This is a kind of self-referential cyclicality reminiscent of the chicken and egg story, but we won’t go into resolving that now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vr46vTrsOJD5K3egfV_kdw.png" /><figcaption><em>Image </em>: courtesy Khan Academy, read polypeptide = protein</figcaption></figure><p>The blueprint information for the translator would need to tabulate sufficient information to be able to fingerprint specific amino acids based on certain physical properties, and also provide a way to sense this information. There are an infinite number of unique chemical molecules in the world due to the permutations and combinations possible, and a strand of DNA is a whole chemical molecule in itself. The seemingly plentiful space available within the DNA, now begins to appear woefully limited for providing an accurate inventory of signifying properties to pick out 20 unique amino acids from an infinite pool of look-alikes.</p><p>Say you’ve got a collection of multi-coloured marbles in front you, and you’ve been told to pick out a blue marble from the bunch. You notice right away that there are several sizes of blue marbles — small, medium and large. So you ask for more instruction — you’re told, it’s the large variety you’re looking for. So now you go looking for a large blue marble, but then you notice that some of the large blue ones are chipped, while some others are dirty and yet some more are clean and undamaged. Once again you ask — and you’re told to look for dirty. But then you notice that some of the large dirty blue marbles are hollowed out, while others not. If you get the tilt of where I’m going with this, is that it’s possible to keep narrowing down on the correct specification for the marble we need, but in the end, there are too many possibilities and we have limited time, so we settle for an approximation which does the job — any large dirty blue marble is good enough for our purpose. In the same way, our genetic inventory encodes for positive factors in the search task. It’s an <em>inclusionary process</em> a sort of exaptation, by which molecules (marbles) which match certain criteria are selected, as opposed to an <em>exclusionary process</em> where we might eliminate marbles with specific properties and keep the rest. We follow this process simply because there are far too many possibilities to exclude.</p><p>Suffice to say that translation as predicated on the use standard words and finite space is better described as a <strong>process of exaptation</strong>, necessarily subject to the same limitation of lossy information compression as does a formal language.</p><p><strong>Moderating factors and benefits of language compression</strong></p><p>Environmental constraints would play a big role in deciding the level of granularity in our genetic information. Let’s consider a few of these for the moment.</p><ol><li><strong>Vocabulary — </strong>Like any language, the efficiency of compressing larger messages into standardized boxes is limited by the number of words in its vocabulary. As we now know that in the world of DNA, words are formed by combining 4 bases (alphabets — A, T, C or G) in sets of 3 amino acids, the possible number of permutation is 43 = 4 x 4 x 4 = 64. This means there is a hard limit of 64 possible words in the entire vocabulary of our genome. Now hold on… couldn’t we could join as many 3-letter words as we like to form sentences of any length, so theoretically there isn’t a limitation here at all, right? Well yes and no. Yes, the 64 words aren’t a hard limit on information storage capacity, but it does form a different kind of limitation — compression efficiency. The word limit is a hard ceiling on the storage capacity given a finite length of a sentence. Since the encoding and decoding process is always under the constraints of time and resource constraints, this translates into selective pressure on DNA to encode for messages which convey simpler information (refer to fewer and less complicated amino acids) as compared to more complex information (more amino acids which inhabit more complex functional domains).</li><li><strong>Availability — </strong>The process of evolution is limited by resources. In creating the recipe for a biological process, evolution is more likely to play with complex molecules already available in its environment rather than make them from scratch. The odds grossly favour the former over the latter, because of speed. Since complex molecules have a larger inventory of properties to permute over than simpler molecules or elements, it goes to show that evolution is pre-disposed to selecting substitutes (look alikes) more frequently than not.</li><li><strong>Parsimony in Molecular Fingerprinting — </strong>Once selected, a complex molecule itself might pose a large inventory of properties — structure, weight, polarity, chirality, isomeric state, shape and the list goes on. Evolution following the law parsimony (thriftiness), does not care about checking the other features of a molecule once it finds that a viable prototype can be built using a certain subset of properties — signifiers. Evolution is not an entity which prefers planning. It is better modelled as a system which eliminates negative outcomes by trying (loss minimizing), rather than a system which generates all possibilities and then selects positive candidates (profit maximizing). If it were the latter, then the list of signifiers would obviously become hugely expanded to differentiate the negative selection of the large number of sub-optimal candidates which have largely similar properties. This effect is similar to the limitation in vocabulary and they both work in conjunction to moderate each other.</li><li><strong>Efficiency of transmission — </strong>By creating references to pre-existing complex molecules in the environment, rather than include recipes from ground up, the DNA molecule itself is reduced in size. This shortened DNA would be more robust in several ways — say surviving trauma or difficult externalities or requiring less resources to transport, maintain or decode.</li><li><strong>Improved viability (exaptation) — </strong>In compressing the information in the DNA, evolution effectively creates the possibility of a theoretically infinite number of interpretations of the same coded message, depending on the conditions available in the environment at the time of gene transcription. In fact, the higher the level of vagueness in the compression, the lesser the granularity in fingerprinting molecules, and the more chance for substitutions to occur, and the transcription to proceed uninterrupted. Theoretically it would be possible for our human DNA, if unwrapped in the alien environment of Proxima b (a goldilocks zone planet orbiting the star Proxima Centauri, 4.2 light years away), to lead to the formation of an altogether different phenotypic species. But it’s easy to guess that in most cases a liberal interpretation (like in the case of an alien planet) is less likely to succeed in the long run due to the complex interlocking conditions necessary for self-sustainability. In which case the specified DNA variant is destroyed, and other more strict variants (with less compression) go on to possibly survive. However it’s quite a vivid picture when we see what this open-ended approach to encoding, can create in terms of exaptation to new environments. In a 2013 study, NASA published about Pseudomonas bacteria sent to the International Space Station, they noticed that under the conditions of micro-gravity the bacteria had developed a new kind of column-and-canopy structure which they’d never done on Earth. They’d also reproduced faster than the control samples grown under normal gravity.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/1*t8BpM-YgAcqybN9Xa3M2Mw.jpeg" /><figcaption><em>Image </em>: courtesy <a href="https://www.google.com/url?q=https%3A%2F%2Fwww.nasa.gov%2Fcenters%2Fames%2Fnews%2F2013%2Fbacteria-sent-into-space.html&amp;sa=D&amp;sntz=1&amp;usg=AOvVaw3SLe6Hvilf4sCnZ7UJ6BPj">NASA</a></figcaption></figure><p><strong>Are we our genes?</strong></p><p>Genetic information is at best described as a sketchy diagram, with a lot of gaps for uncertainty to creep in. As with most blueprints, it’s more akin to a half-completed jigsaw puzzle than a pre-rendered photographic depiction of an end product or a Mona Lisa. How the puzzle ends up looking is extremely contingent, on the conditions available in the environment in which the information is decoded. Since even within a homostatic environment substitutions are more likely to happen than not, it is safe to say that we’re approximated ghosts of the original intention (metaphorically) of our DNA.</p><p>All around us and within ourselves we see these approximations every day — we see the similarities and if we look closely the differences, but usually we are all close enough approximations that we’re all able to co-inhabit a standardized definition of the homo-sapiens species.</p><p>We’re now learning about how changes in methylation add an extra layer of information to information already encoded in the DNA, which could possibly pass on heritable information from parent to offspring (epigenetics), while the basic information encoded in the alphabets of A, T, C, and G which still form the bulk of the data hardly changes. But it seems the architecture of the DNA has a much larger mechanism for exaptation already built in — it’s language.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b333ac0a378" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stop! We’re making it too easy for Amazon and Flipkart]]></title>
            <link>https://medium.com/@sugato.b/stop-were-making-it-too-easy-for-amazon-and-flipkart-6a610fb8e3aa?source=rss-96651152f0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a610fb8e3aa</guid>
            <category><![CDATA[consumer-behavior]]></category>
            <category><![CDATA[e-commerce-business]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[ondc]]></category>
            <category><![CDATA[capitalism]]></category>
            <dc:creator><![CDATA[Sugato Banerjee]]></dc:creator>
            <pubDate>Fri, 02 Dec 2022 12:20:37 GMT</pubDate>
            <atom:updated>2022-12-31T05:48:57.456Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g5TeIwl4tVxgMOEgxIXeyg.png" /></figure><blockquote>TLDR; The Open Network for Digital Commerce (ONDC) currently in beta, is well-intentioned, revolutionary and a first-ever of it’s kind experiment anywhere in the world — take the power away from the large players like Amazon, and Flipkart, create a thriving multiverse of smaller sellers, apps and service providers who can deliver more innovation, competition and most importantly bring more buyers into the digital fold. It might just also be just the thing the e-commerce giants have been waiting for — a tax payer funded customer induction program at population scale.</blockquote><p>Okay, let’s talk. I just refilled my bottle of water, so we’re good for the next 15 minutes at least.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uQTdr7ukAAY8yOVxTIMi9w.png" /></figure><p>If you’ve never heard of ONDC I don’t blame you. It’s a different story when you have a browser history like mine. (Many things are different with a browser history like mine, but I digress). Google’s algorithm seems to have zero’ed in on me like a cluster of fruit flies, peppering me with at least three articles in my feed about this and that about ONDC almost every day. Here’s how they usually flow:</p><ul><li><strong>News feed story #1 </strong>— <strong>ONDC launches pilot in these new cities, check if…</strong></li><li><strong>#2 </strong>— <strong>ONDC CEO says, “</strong><a href="https://yourstory.com/2022/09/ecommerce-as-a-sector-will-become-irrelevant-ondc-ceo-t-koshy"><strong>e-commerce is now irrelevant with launch of …</strong></a><strong>”</strong></li><li><strong>#3</strong> — <strong>Restaurant owners in Bhopal shut shops to celebrate as the ONDC network becomes self-awa…</strong> <strong>Whaaaa?</strong></li></ul><p>The Open Network for Digital Commerce is being hailed as a revolution in the digital commerce space; something that will help re-invent the space and redistribute power within the system.</p><p>I agree.</p><p>Unfortunately, the next step is where I hit a giant question mark. I agree it’s disruptive; I’m not very clear what it is that it’s going to be disrupting. Here’s what mainstream news would have you believe — by creating an open and ubiquitous backbone for digital selling, the power of the large incumbent players will be diluted and a large number of smaller more nimble players will breed innovation and healthy competition. One analogy could be that the public roads and highway infrastructure is poor, so most of the large transporters invested in and walled off their own private roads. Create enough quality public access highways, and smaller transporters flourish.</p><p>It’s a very sane-ish sort of argument. Too bad it’s also incomplete.</p><p><strong>What’s wrong with this picture?</strong></p><p>Rather than upend the way the current online behemoths — Amazon, Flipkart (which have control over 62% of all online sales), ONDC will actually end up creating a giant customer acquisition funnel, speeding up what was a slow feeding process right now.</p><p>To understand this, I need to tell you a bit about how ONDC will work. Bear with me for just a moment here.</p><p><strong>Traditional Marketplaces</strong></p><p>Despite all the noise, the truth is while smartphone and consequently 4G penetration in India has <a href="https://www.statista.com/statistics/1229799/india-smartphone-penetration-rate/">crossed 50%</a>, less than 8% of India’s retail sales happen online. Yeah, surprising isn’t it! By the way, what were you expecting that number to be before I said it? <br>Say you are a carpet store owner who wants to get in on the e-commerce action. You sign on with one of the existing marketplaces, say Amazon, since you realise it’s so much harder to market your own superawesomecarpetstore.in. There’s no upfront costs (awesome), and Amazon charges you a fraction of the sales you make as commission (usually 10–20%, hmm… dicey). There might also be additional expenses for you to promote or advertise products and gain more eyeballs (wait, what did I just pay that commission for again?). Once a sale happens, Amazon collects the payment and shares the payout with you minus the commission. You then have a choice — handle logistics yourself, through an external courier, or let the marketplace’s own logistics handle everything (for a price). If your customer is pleased, chances are she leaves a good review for your product. This in turn makes your products appear more frequently in search results by other potential customers, leading to more sales and more happy customers. A virtuous cycle taking the reach of your easy wash, pet-friendly floor ware to epic new heights. And so it continues very happily, until one day you get a popup from your inbox.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O5hVvDNy8OIfG7DZrrycug.png" /></figure><p>Whoops! Sales tank and suddenly you’ve got no choice now but to cut prices or wind up on the platform and move elsewhere. If you do move, all those happy customer reviews you gathered over the years — good news — they’re gone! You have the happy job of starting from zero again. Now, who doesn’t love that.</p><p>It’s a highly touchy and disputed topic of exactly how much of Amazon’s business in India comes from these kinds of knock-off own brand (private label) products. Some reports put it as <a href="https://jmfl.com/docs/default-source/default-document-library/jmfl-ondc_disruption_or_evolution_02092022.pdf">high as 30%</a>, while others say it’s <a href="https://the-ken.com/story/amazon-made-for-india/">only 5%</a>. If you shakedown one of Amazon’s global execs, they might even tell you that private labels account for <a href="https://www.cnbc.com/2022/10/12/amazons-growing-private-label-business-is-challenge-for-small-brands.html">only 3%</a> of its overall revenues. So I’d chance that the India number is a shade closer to that lower estimate for now, but the intent is clearly to grow this figure substantially. The government has also tried to placate growing anger from smaller sellers over the private label epidemic, by barring marketplace players from marketing their own-brand products. As expected, players found a <a href="https://inc42.com/buzz/amazon-copied-bestselling-indian-brands-to-boost-private-labels-report/">way to side-step that</a>. The government is busy playing whack-a-mole with the <a href="https://www.moneycontrol.com/news/business/startup/draft-e-com-policy-amazon-flipkarts-private-label-products-may-become-a-thing-of-the-past-7069951.html">proposed e-commerce policy</a> which has been in the planning stage for the past 4 years without <a href="https://www.moneycontrol.com/news/business/economy/e-commerce-policy-remains-in-limbo-as-ministries-differ-provisions-carved-out-to-other-legislation-8898761.html">any end in sight</a>. It’s understandably messy.</p><p>Anyhoo… this is the blood-drippingly nightmarish scenario. The more likely possibility is that your success catches the eye of some larger carpet wholesalers (someone higher up the food chain) who decide to join the party, pressuring your prices into a similar trajectory from there on down. The story doesn’t end well for <a href="https://en.wikipedia.org/wiki/Kalia_the_Crow">Doob Doob</a> on that end either.</p><p><strong>Drumroll… Enter ONDC</strong></p><p>Its proposed that ONDC will work a bit like the UPI framework; it will be a backstage player providing the handshaking between numerous sellers and buyers all of whom might be using different apps to access what will be a unified shopping multiverse. So in essence we will have a common library of products — sellers having multiple apps from which to list their product catalogues (apps like GoFrugal, SellerApp, Dukaan), and buyers using familiar apps like PayTM and PhonePe to search and buy from these sellers. The customer feedback and reviews would be handled by a common ledger on the ONDC backbone itself (look Ma it’s portable), so it doesn’t matter if you as the seller decide to switch from SellerApp to Dukaan or vice versa, your online reputation remains intact (no starting from scratch anymore — your carpet store is safe). The logistics and delivery would again be a multiple choice question — you can choose to deliver yourself, or through some delivery partners available on the platform like Dunzo, Delhivery, or Shiprocket whoever fits the bill.</p><p>All of these activities — listing, buying, and shipping will be handled by the respective apps or service providers. ONDC acts like the connecting fluid between all these while allowing you to keep your connection to your seller reputation intact.</p><p><em>Of course I’m oversimplifying, there’s a lot more juicy detail to all this, and maybe I’ll do a follow-up article on that soon (let me know in your comments). In the meantime you can read </em><a href="https://www.linkedin.com/in/himanshu-saleria/"><em>Himanshu Saleria’s</em></a><em> overview of how ONDC is structured and </em><a href="https://medium.com/@himanshusaleria/ondc-explained-everything-about-open-network-for-digital-commerce-1050d7fb4dff"><em>here</em></a><em>.</em></p><p>You could argue that these kinds of options already exist. Yes, true. There’s a zoo of options available — seller-facing solutions like <a href="https://www.omnifynd.com/">Fynd</a>, and <a href="http://unicommerce.com/">Unicommerce</a> help you manage sales across multiple marketplaces through a single window, while <a href="http://mydukaan.io/">Dukaan</a>, <a href="http://shopify.com/">Shopify</a> and <a href="http://wix.com/">Wix</a> all help you create your independent digital storefront) and an equally large number of buyer-side apps exist. Even solutions for the portability of trust exist — think <a href="http://trustpilot.com/">Trustpilot</a> or <a href="https://www.reviews.io/">Reviews.io</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q2egRMAEJtcBaoRJKVS8Og.png" /></figure><p>Ok, my bad. I forgot to let on earlier. When I said disruption earlier, I meant a milder sort of disruption. The kind I feel here in Bengaluru around the end of October when the weather switches from light rains to <strong>mild</strong> haze.</p><p>Honestly, the big thing about ONDC is less about the new road building and more about the endorsement and sanctification. Yes yes, you’ll also argue that while solutions for trust portability also do exist, they’re not as well integrated with marketplaces. I mean you can’t really pull up your socks and integrate your reviews from Trustpilot into your Flipkart product listing. Flipkart has its own rating system, they own the road you’re on, so you have to play by their rules, remember.</p><p>See that’s the thing, there are always solutions available like there were smartphones in the early 2000’s (the Handspring Treo, and the Blackberry come to mind). But it wasn’t until Steve Jobs (fresh from the success of the iPod) unveiled the first-ever iPhone in 2007, that the game changed. The same is expected with ONDC. With the full blessing of the state behind this new “industry standard” system, it’s expected that players using the network will be able to beat the chicken-and-egg problem of building the seller base to attract buyers, or building the buyer base to attract more sellers in each micro-market. Things will move from a position of uncertainty to gaining the trust of first-time online consumers, faster. Much faster.</p><p>Just take a look at this <a href="https://www.livemint.com/companies/news/what-is-ondc-india-s-project-for-an-open-e-commerce-network-11654097068290.html">article</a> declaring ONDC’s own target of taking India’s e-commerce penetration from under 8% to 25% in just two years and engaging more than 900 million buyers within five years(up from the 190 million now). That’s almost a billion buyers to put it plainly. Yes — population scale! Hair raising just to think about it too. I think getting somewhere close to that number is highly possible since we saw this kind of trajectory happen once before with the adoption of UPI, and that was way back in the slower days of 2016 — when Google was still obsessed with naming Android versions after cookies and cakes, and airlines were still reprimanding passengers for not switching off their phones mid-flight We’ve really come a long way since then haven’t we? So it’s obvious to think things will be faster this time around.</p><p><strong>ONDC is fantastic. What’s the catch here?</strong></p><p>Here’s the deal. When you talk about onboarding a billion new customers online you can’t ignore the side effects. So far the premise of ONDC has been about removing dependence on platforms and empowering small shop owners, businesses, and traders to compete on a level playing field. Now consider this, why haven’t Amazon and Flipkart been able to make inroads into India’s heartlands? Why is the penetration figure still only 8%? Not for lack of trying, I can tell you that.</p><p>It’s about shifting mindsets and forming new habits about how people choose to spend their hard-earned income. This can take a long time and relies on building a large enough body of success stories (social proof) in every catchment area before the whole thing reaches critical mass. This is why Amazon and Walmart are pouring billions of dollars into India despite never having turned a <a href="https://economictimes.indiatimes.com/tech/technology/flipkart-has-shown-clear-proof-of-value-will-hit-profitability-walmarts-judith-mckenna/articleshow/92089947.cms?from=mdr">profit</a>. They’re trying to create enough of these success stories and they don’t mind the high cost of customer acquisition (right now), in the hope that at some point the reaction will go critical. In some urban catchment areas, things have already gone critical so to say. The proof of this is the proliferation of so many successful D2C digital brands which have grown dramatically in the last 5–6 years. They’ve all benefited from the mindset shift catalysed by these incumbents. This is a happy side effect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BKsu57YvNT63wEYAiNCXqg.png" /></figure><p>The ONDC initiative has something even these big boys don’t — state endorsement, and that’s not a small thing. So believe me when I say that ONDC will succeed where the incumbents have lagged behind so far.</p><p>Now comes the unhappiest side effect of all. Turns out ONDC’s biggest strength its reach, is also its biggest weakness.</p><p>Let me explain.</p><p>If we assume the homework of consumer mindset change is already done by ONDC, then who decides the winners and losers now? I would assume you already know. Um… free market forces?</p><p><strong>Right. Zero points for guessing that.</strong></p><p>Once the problem of access (mindset) has been removed it becomes a free-er sort of market. Remember what happened with your carpet store? The marketplaces have the business volumes and cash flows to set up massive cost-efficient logistics networks, and warehouses and enlist sellers who have no retail presence, no high rents, no wasted space, no courteous sales staff, and definitely no friendly neighbourhood ambience like your carpet store. I’m talking <a href="https://www.shiprocket.in/blog/guide-to-dark-stores/">dark store</a> sellers, and cloud kitchen operators. They could even (try to) directly negotiate better prices with wholesalers, or manufacturers, cutting out more of the middleman “inefficiencies” from the system by leveraging increased bargaining power (I’ll admit this particular gambit <a href="https://finshots.in/archive/amazons-foray-into-b2b-ecommerce/">hasn’t worked</a> particularly well so far). What they gain they share with consumers in the form of lower prices. Lower than what retailers or small kirana store owners (who are still labouring under the traditional value chain hierarchy), could ever afford to sell at. Even if you factor in the savings from platform commissions (10–20%) by selling directly on ONDC, that simply cannot compensate for the efficiencies gained with the kind of scale we’re talking about. While it’s still early days into the beta stage, a <a href="https://jmfl.com/docs/default-source/default-document-library/jmfl-ondc_disruption_or_evolution_02092022.pdf?sfvrsn=0">research study</a> found that prices from a particular seller for the same products were on average higher for buyers via ONDC than through platforms like Swiggy Instamart and Dunzo.</p><p>Unfortunately, this is where the intent of the disruption starts unwinding. The entire proposed framework of the ONDC hinges on the salvation of the traditional setup. The idea is that existing shop owners <a href="https://www.business-standard.com/article/economy-policy/ondc-starts-beta-test-in-bengaluru-over-161-orders-placed-on-day-1-122093001173_1.html">enlist</a> on the new network and continue to sell at the same prices (if not more) as they sold physically at their store, add on delivery costs on top and call it a day. That&#39;s exactly the opposite of how the large format marketplaces and their everyday-low-prices model operate. I can literally see the executives at Amazon and Flipkart drooling and frothing at the mouth as they watch events unfold in the next few months.</p><p>This copy-paste offline-to-online model will have an expiry date. It’s not happened so far due to the slow pace of change in mindsets and habits. But this is what ONDC and its partner ecosystem of apps will be attacking. As the system converts more and more first-time shoppers to the digital experience, the novelty and convenience of buying things will start wearing off. Buyers will soon start raising their heads and looking around. In fact, they might not even need to move their heads at all, there is already <a href="https://economictimes.indiatimes.com/tech/technology/onboarding-flipkart-amazon-may-provide-ondc-scale-and-credibility-report/articleshow/94005249.cms?from=mdr">speculation</a> that the big marketplaces might all end up joining the new network after all. Crazy right?</p><p>Once they do. Game over?</p><p>Well… not exactly. There is still one force standing in the way of big corp, that can save the underdogs yet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gni87SdKa2JoY5tKbrKsRg.png" /></figure><p>There’s nothing scarier for big bad online marketplaces than the red pill and low order values. The enemy of cost efficiencies, low order values ruin the fun by increasing the last-mile logistics costs. The last mile connect is the very reason why the traditional manufacturer — distributor — wholesaler — retailer model exists in the first place. And India is the ‘baap’ of low order values. Turns out the overall average order value on Amazon, even with today’s urban weighted buyer base is just <a href="https://inc42.com/buzz/profitability-remains-elusive-for-amazon-india-despite-over-6-5-bn-dollar-investment-bernstein/">Rs 800 ($10)</a>. The problem is more acute in tier 2, tier 3 and rural areas. Social commerce platforms like Meesho, Shopsy and Dealshare, which cater to more small cities have it even worse. Meesho for example has order values between Rs 400–500. And you need only imagine what it will be like for the markets our new network will be tapping. The “sachet economy” which has been hailed as the marketing invention of selling products in extremely low-value sizes began in 1983 but <a href="https://themorningcontext.com/chaos/the-problem-with-the-sachet-revolution">continues to be a painful economic reality</a> for much of India, where people still can’t afford regular pack sizes which are much more cost-efficient. It’s not something to be proud of but it’s a reality. Customers in these economic strata are best served by a fragmented network of small “mohalla” walk-in stores, the kind we will no doubt be seeing soon in ONDC marketing materials. It’s no credit to ONDC however, that the offline livelihoods of these store owners will remain protected for the foreseeable future since buyers would by definition stay priced out of reach for both organized marketplaces as well as small sellers when ONDC gets green-lighted.</p><p><em>What do you think would be a better way to reduce the dominance of large players/marketplaces in the e-commerce space? Let me know in the comments.</em></p><p><strong><em>Credits:</em></strong><em> Images by </em><a href="https://www.freepik.com/free-vector/set-cute-monsters-cartoon-funny-characters_33946935.htm#&amp;position=3&amp;from_view=user"><em>upklyak</em></a><em>, </em><a href="https://www.freepik.com/free-vector/water-flask-transparent-set_4329572.htm#&amp;position=7&amp;from_view=undefined"><em>macrovector</em></a><em>, </em><a href="https://www.freepik.com/free-vector/symptom-checker-doodle-vector-coronavirus-illustration_19595729.htm#&amp;position=1&amp;from_view=undefined"><em>rawpixel</em></a><em> on Freepik, </em><a href="https://storyset.com/web"><em>Web illustrations by Storyset</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a610fb8e3aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>