<?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 Aditya Aserkar on Medium]]></title>
        <description><![CDATA[Stories by Aditya Aserkar on Medium]]></description>
        <link>https://medium.com/@adityaaserkar?source=rss-d3bbddfe5821------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*zMhs_MnqyI1Qwjcnv2s01w.jpeg</url>
            <title>Stories by Aditya Aserkar on Medium</title>
            <link>https://medium.com/@adityaaserkar?source=rss-d3bbddfe5821------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 09:41:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adityaaserkar/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[Alas, Bombay is dead. Long live Bombay.]]></title>
            <link>https://adityaaserkar.medium.com/alas-bombay-is-dead-long-live-bombay-805b1880c1bc?source=rss-d3bbddfe5821------2</link>
            <guid isPermaLink="false">https://medium.com/p/805b1880c1bc</guid>
            <category><![CDATA[mumbai]]></category>
            <category><![CDATA[bombay]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[city-design]]></category>
            <category><![CDATA[india]]></category>
            <dc:creator><![CDATA[Aditya Aserkar]]></dc:creator>
            <pubDate>Sun, 05 Apr 2026 15:06:15 GMT</pubDate>
            <atom:updated>2026-04-05T15:06:15.861Z</atom:updated>
            <content:encoded><![CDATA[<h4>And Mumbai is taking its place.</h4><p>No, this article isn&#39;t published in 1994, it is 2026.</p><p>Mumbai. Construction.</p><h4>मुंबई कोणासाठी</h4><p>I’ve come to the realisation that Mumbai is the product with birds as target audience. Fantastic to look at from their vantage point, but full of shit when it comes to the ground.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*K2Lp0u_0r-t36iXl.jpg" /></figure><p>Social media is filled with drone shots of my beloved city. We’re making the city look mesmerising, in the birds eye view at least. Swanky new road networks, skywalks, and the hundreds of skyscrapers coming up each day. However, zoom-in a bit, and you start seeing the pinch <em>(hoping people get the pinch-to-zoom analogy).</em></p><p>Gone are the days when the affluent class used to sit shoulder to shoulder in a bus or a shared cab. Renowned actors sitting on the same table at Cafe Madras or Ramashray with a construction worker, and both being asked to vacate the table as soon as they finished eating to give place to people waiting outside in the sweltering humidity.</p><p>There is a new class emerging, correction, class was always there, but now they have been given a parallel universe to operate in. A parallel universe of cafes and bistros, of Bastian, of BKC, or Ambani cultural centre with suited staff every 20m paid to smile at you. The Bombay elite has been handed over a Mumbai. A Mumbai that they can bubble up their lives into. And the Bombay simpleton have been left out to perish. No amount of marble underground metro train is going to get into this Mumbai bubble. The appeasement of the rich has been too in-your-face to ignore. Mumbai, in my eyes, was the last standing batallion city of some semblance of equality of opportunity in this extraordinarily highly unequal country. But now, the othering has been complete. People asking me about facing racism in Europe, while simultaneously giving water to the 10 min grocery delivery boy in a separate steel glass that is kept at the side only to soon tell them to take the ‘service elevator’ back down their 53rd floor apartment where they can continue to feel above the rest of the downtrodden. People who want mixed breed dogs, but same caste marriages. People who will not allow the Dalit sculptor in the temple, right after he has finished sculpting the idol. The ‘<em>Driver, gaadi nikalo</em>’ class is ever increasing.</p><p>Mumbai was built by Kolis, Gujaratis, Marathis, Parsis, the Biharis, British, and everyone in the country who’s tax fed to her growth. Yes, the ‘<em>परप्रांतीय</em>’ built the city. You could be whoever you wanted to be in Mumbai. There was no ‘<em>तू जानता नहीं मेरा बाप कौन है</em>’ / ‘<em>Do you know who my father is</em>?’ And everybody within the country and beyond, was at awe by this simple inclusionary differentiation that Mumbai had to offer. And today, the levels at which discrimination has gone rampant, over language, spoken or written, different festivals being celebrated, almost like a which festival is louder, rather than being proud of the fact that the city has been welcoming so many diverse making their homes.</p><p>Oh! Zoomed-in too much? Lets pinch-out then.</p><p>I think this all was set in motion the day that the old busses went off the roads, now these smaller AC busses, completely devoid of character, demeanour have taken over with frustration on the driver’s seat. The kaali-peeli taxis, loosing their charm, and you start to see endless sea of Bangalore-style white roofs of cab hailing services that are slowly being cooked by their corporate overlords. The companies based in the US extract the last drop of money both from the passengers and the drivers, while simultaneously pitting them against each other, AC cab, non-AC cab, toll charges included, toll charges excluded, by the map, by the intuition, the flashpoints are endless. The lenghty conversations with the kaali-peeli drivers about life and epiphanies, are being replaced with the WagonR ubers simply on their phone every waking moment talking to another Hyundai Xcent ubers. To add to this, these drivers, call themselves drivers simply because they know the ABCs of the Accelerator-Brake-Clutch, but zero about discipline, empathy, civic sense, road safety, priotiry, and rules. They haven’t been around to have seen the disciplined Bombay that I feel that now am cremating. Certainly not the Bombay I left, but definitely the Mumbai I came back to.</p><p>Bombay was fast, but Mumbai is rushed. You could pause a bit in Bombay, but Mumbai, you would be trampled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*xe_DgIItQMEFSKfx" /><figcaption>Taxi Fabric, reminiscing times of not so long ago</figcaption></figure><p>Mumbai is becoming the Bangalored-Bombay, isnt it.</p><p>Atal setu, coastal road, new metro lines, new airport, open heart surgery of the city, but at what cost? Concretization of everything, remove mangrooves everywhere and then wonder why she floods every year. New roads are built, then they are dug up. Each contractor is an incarnation of Brahma-Vishnu-Mahesh all in one. Creating and destroying within a single month.</p><p>The politicians of course never really cared about the citizens, but now the turning point is that the citizens don’t seem to care about each other either. Systematically, the patience of the citizens have been tested through and through, and the ones emerged on the other side are now different. There’s noticible increase in ungratefulness, honking, decrease in road discipline, cheating tarrifs, etc. There is no measure of the mental torture that the perpetual construction and ever increasing costs are turning people against each other. Even if we let go of the shamelss Sitaraman saying that the rupee is doing good, the brunt can be absorbed by the citizens only to an extent.</p><p>It might be true that my frame of reference is tainted, after all, I left the city more than a decade ago. But perhaps, thats what has the power to give me an outsider’s view, while deeply caring about what was easily the best city in the world. Remember the frog in the boiling water experiment?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dUuqYFAXNkzrCCqh" /><figcaption>Mumbai being built for the birds, and the rich humans that fly over everyone</figcaption></figure><h4>All is not bad</h4><p>Of course, all is not bad, and I acknowledge the upliftment that we have seen just in our lifetimes. The caretaker I had as a child, has grandchildren who are now doctors and national level atheletes. Its heartwarming to see the families climbing out of the service class against all odds, but the today’s Mumbai, these odds are ever increasing. I remember the empathetic Mumbai that has also still preserved. I myself was pardoned metro tickets when I did not have change to give. My phone was not charging and the repair guy could have easily duped me with hundreds of rupees, but rather simply cleaned it for free. People are still alerting fellow bike riders if their side stand is open. But the issue is that they are riding on the footpath, isn’t it. {<em>Footpath (</em>/ˈfʊtpɑːθ/) (<em>noun): A dedicated vehicle-free paved area on both sides of the road for pedestrians to walk}</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h56roWTKWW6gVMZZHjcaIw.png" /><figcaption>We can only dream of livable cities with AI</figcaption></figure><p>Perhaps what is prompting me to really hit the publish button on this article, is the almost constant state of cough and fever I seem to have been in since arriving. The rampant construction dust everywhere, with the winter pressure concentrating it on the surface level. Don’t get me wrong, this was there last year as well, but this year’s winter migration for me has seemed to be a alarmingly different. Especially since my anger has been transformed into sheer disappointment and dejection. Bourn out of pollution, yes, but also that of the acceptance of the end of Bombay.</p><p>I keep getting questions from people how to leave the country, where it feels like the 35% tax that you pay, is simply thrown away. A key difference that I have seen is that most Indians really do tend to love India, no matter the government’s best effort to hate the daily life it provides. Most people at least want to leave, till the time all the construction work is complete so that they can come back to a city that hopefully can be categorised as livable. Escapism, perhaps; saving your own lungs, perhaps.</p><p>Mumbai is an ultra mega city. No other comes close. But the sense of belongingness is quitely dissappearing. And honestly, smaller efforts can bring it back too. Simply completing a project that has been taken up. Modiji comes to inaugrate every road, sure, thats his thing, but lets really make a project complete. Lets really make sure that the cement sacks are not just left there as some kind of a lane marker to slowly disintegrate into the air ultimately being eaten by you while eating your vegetables grown in sewage water by the train tracks. Accept that Mumbai is large, and is not just defined by SoBo, thoudsands of events that bring in flocks of people, can easily be established in all corners of the city. Someone living in Kanjurmarg, doesn’t need to come to Bandstand to feel that they belong to Mumbai. The hundreds of events that the city organises, can be distributed across and not concentrated to the lush and posh. The city has a pleathora of incredibly historically significant sites. Literally none of them are either maintained or promoted. They certainly mark the cornerstones of belongingness. There is so much potential in the city, and I think the spirit of Mumbai has to be redefined to the optimism that Mumbai will be a more equal, a more welcoming, a cleaner home for those who wish to live in it.</p><blockquote>The barrage of free public events that exist in the city, are only open for people who can afford them.</blockquote><p>The initial plan was to tell all of this to a kaali-peeli guy, but now that there is none to listen to my epiphany, I pen it down here for you.</p><blockquote>If you liked reading this, consider reading. About a different city I fell in love with, and made a home of:</blockquote><p><a href="https://adityaaserkar.medium.com/a-city-and-its-architecture-a22d7041e7fd">A city and its architecture</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=805b1880c1bc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The silent violence of job rejections]]></title>
            <link>https://adityaaserkar.medium.com/the-silent-violence-of-job-rejections-43141207dc36?source=rss-d3bbddfe5821------2</link>
            <guid isPermaLink="false">https://medium.com/p/43141207dc36</guid>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[hr]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[dystopia]]></category>
            <category><![CDATA[resume]]></category>
            <dc:creator><![CDATA[Aditya Aserkar]]></dc:creator>
            <pubDate>Sat, 20 Dec 2025 09:45:35 GMT</pubDate>
            <atom:updated>2025-12-20T09:45:35.031Z</atom:updated>
            <content:encoded><![CDATA[<h4>There is a version of unemployment that statistics do not capture.</h4><p>It is not idle. It is not passive. It is not a break.</p><p>It is months of motion without progress.</p><p>Applications sent late at night. Calendars filling with interviews. Portfolios rewritten again and again. Stories rehearsed until they lose their meaning. And still no role.</p><p>People are not just looking for jobs. They are trying to keep their lives from collapsing.</p><p>They lose weight from anxiety, not discipline. They delay dentist appointments. They calculate groceries more carefully. Buy spinach only when it is on discount. They are one broken dishwasher away from giving up. Some stop therapy because it quietly slips out of reach. Others cling to rituals: journaling gratitude, long walks, productivity hacks, anything that creates the illusion of momentum. A Hail Mary attempt, to bring back some semblance of sanity, some control.</p><p>For migrants, there is an additional clock ticking in the background. Visas, residency rules, expiration dates that turn rejection emails into existential threats.</p><p>And after all of this, the reply arrives.</p><blockquote><em>“Sorry, we went ahead with another candidate who matched our needs better.”</em></blockquote><p>No explanation. No signal. No learning.</p><p>Just silence, dressed as professionalism.</p><h3>A system that withholds information</h3><p>The modern hiring process is an invisible maze.</p><p>One hiring manager wants a Framer portfolio. Another insists on a PDF. One wants quantified business impact. Another assumes numbers are performative fiction.</p><p>Some value craft. Others value speed. Others value alignment with a leadership style they cannot articulate. Some roles are real. Some are already filled internally. Some exist only because process demands it.</p><p>Applicants do not know which reality they are entering.</p><p>They are told to tailor their CVs, personalize their cover letters, network strategically, post on LinkedIn but not too much, show confidence but not ego, seniority but hunger, opinions but obedience.</p><p>When rejection comes, it arrives without an action plan.</p><p>Because the system refuses to tell them what actually mattered.</p><h3>AI screening, human silence</h3><p>If billion-dollar companies can use AI to scan resumes, rank candidates, flag risks, and optimize pipelines, the least they can do is return a reason for rejection.</p><p>Not a coaching session. Not a paragraph.</p><p>A reason.</p><p>One sentence of truth.</p><p>Without feedback, people internalize failure as personal deficiency. They spiral. They overcorrect. They burn out. They doubt skills they have already proven elsewhere. And all of this happens while their parent’s are getting older. This is the real world.</p><p>This is not resilience. This is erosion.</p><p>Here are some things that you can do as a hiring manager, cause let’s face it, you will soon be on the other side too.</p><h3>What job descriptions should actually say</h3><p>Most job descriptions describe responsibilities.</p><p>Very few describe decision-making.</p><p>If you want to reduce harm, start here.</p><p>A job description should not just say <em>what the role does</em>, but <em>how the hiring manager thinks</em>.</p><p>It should answer questions candidates are currently forced to guess:</p><p><strong>Who is the hiring manager?</strong> • Background and discipline • What they personally value in good work</p><p><strong>How do they evaluate candidates?</strong> • Portfolio-first or conversation-first • Depth vs breadth • Craft vs impact vs velocity</p><p><strong>What actually matters in this process?</strong> • Is a Framer site preferred over a PDF? • Are numbers expected, or treated skeptically? • Is domain experience a must-have or a bonus?</p><p><strong>How do they operate day to day?</strong> • High ambiguity or structured execution • Fast iteration or careful consensus • Strong opinions or collaborative shaping</p><p>Most of the time, especially for earlier execution focussed roles, you are checking primarily for a ‘vibe-check’, someone who ‘seems like a nice person to work with’; so state that.</p><p>“Our company wants to move to everythin-AI, and we need to hire someone for it asap” Say it!</p><p>This is not oversharing. This is basic clarity.</p><h3>A reminder for hiring managers</h3><p>Here is the part that rarely gets said.</p><p>You will be on the other side too.</p><p>Markets turn. Budgets freeze. Leadership changes. Companies collapse. Age, health, visas, and luck eventually interfere.</p><p>The system you normalize today is the one you may need to survive tomorrow.</p><p>So here are a few things you can do. Not as kindness. As responsibility.</p><h3>If you are a hiring manager, do this</h3><p><strong>1. Name the rejection reason</strong></p><p>Pick the primary reason and state it plainly.</p><p><strong>• Skill gap • Portfolio depth • Seniority mismatch • Domain experience • Communication clarity • Internal candidate</strong></p><p>One reason is enough.</p><p><strong>2. Stop hiding behind “culture fit”</strong></p><p>If you mean <strong>pace</strong>, say pace. If you mean <strong>disagreement style</strong>, say that. If you mean <strong>ambiguity tolerance</strong>, say it.</p><p>Unexplained “culture fit” is avoidance.</p><p><strong>3. Align internally before interviewing</strong></p><p>If one interviewer wants metrics and another distrusts them, that is your failure, not the candidate’s.</p><p>Applicants should not be punished for <strong>internal contradiction</strong>.</p><p><strong>4. Do not interview without intent</strong></p><p>If the role is frozen, if approval is unlikely, if an <strong>internal hire</strong> is guaranteed, do not run people through the process.</p><p>Their time is not free.</p><p><strong>6. Winback</strong></p><p>If you say you really liked their work, but the presentation had some misalignments, ask them if they can have a <strong>15-min redo</strong> in the next days. Yes it is expensive, but then just say that.</p><p><strong>5. Remember the asymmetry</strong></p><p>For you, this is one requisition. For them, this is rent, residency, healthcare, dignity, identity.</p><p>Act accordingly.</p><h3>This is not about kindness</h3><p>This is about accountability.</p><p>Hiring systems shape lives far beyond org charts and quarterly goals. The quiet opacity of rejection emails has material consequences, especially for migrants, juniors, caregivers, and anyone without a financial buffer.</p><p>Transparency will not fix the job market.</p><p>But silence is actively making it worse.</p><p>If you have the power to decide who advances and who disappears back into the queue, you also have the responsibility to leave a trace of truth behind.</p><p>Anything less is institutional indifference disguised as process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8K94jN8jXvTfPyGa8lN_Fg.png" /></figure><blockquote>If you liked this article, consider reading one on a parallel thread:</blockquote><p><a href="https://adityaaserkar.medium.com/get-a-ux-design-job-in-europe-from-india-f5265c0680a2">Get a UX design job in Europe from India.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=43141207dc36" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI & humans, is Time a Bug?]]></title>
            <link>https://adityaaserkar.medium.com/ai-humans-is-time-a-bug-937acd916c24?source=rss-d3bbddfe5821------2</link>
            <guid isPermaLink="false">https://medium.com/p/937acd916c24</guid>
            <category><![CDATA[chatgpt]]></category>
            <category><![CDATA[glitch]]></category>
            <category><![CDATA[future]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[dystopia]]></category>
            <dc:creator><![CDATA[Aditya Aserkar]]></dc:creator>
            <pubDate>Wed, 17 Dec 2025 21:13:27 GMT</pubDate>
            <atom:updated>2025-12-17T21:14:44.489Z</atom:updated>
            <content:encoded><![CDATA[<h4>Foreshadowing, or am I?</h4><h3>The Funniest Expectation About AI Is That It’s a Computer</h3><p>There is a strange expectation we place on AI. I literally asked it to simply retrieve something it said half hour ago and this is what I got:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*69Jaxn0AocUlcnU8EwWNoA.png" /></figure><p>We expect it to behave like a <em>computer</em>. And it will let us down. You say please to it several times, thinking that it will spare You when It takes over. But wait, and see how it tries to get out each time:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7GQ1Md4WvHk29MqIB2bxLA.png" /><figcaption>ChatGPT why do you lie?</figcaption></figure><p>We assume certain things about machines.</p><p>That they remember better than we do.</p><p>That they do not have the capacity to lie and decieve.</p><p>That they keep records.</p><p>That when something is “saved”, it exists somewhere, patiently waiting to be retrieved.</p><p>These assumptions feel obvious because they come from decades of interacting with computers that behave like archives. Files have timestamps. Databases have histories. There is always a before and an after.</p><p>So when an AI fails to resurface something it clearly “knew” earlier, the reaction is immediate. Confusion first. Then irritation. Then suspicion. Surely this is just bad storage. Surely the past must exist somewhere inside the system.</p><p>But that reaction already hides a deeper assumption. That time inside these systems works the way time works for us. That there is a stable past to go back to. That meaning persists the way events do in memory.</p><p>What if none of that is true?</p><p>What if the discomfort we feel is not about broken recall, but about trying to impose a human timeline onto a system that does not experience time at all?</p><p>Perfect recall. Deterministic storage. A neat CRUD database somewhere behind the curtain. Save, retrieve, query, replay. If it said something once, surely it can surface it again. If it “remembered” something, surely that memory is literal, exact, and addressable.</p><p>After all, it’s software.</p><p>And yet, the moment you actually use an LLM for any length of time, this expectation starts to crack.</p><p>You ask it to resurface something it said earlier.</p><p>You are sure it exists.</p><p>You remember the moment vividly.</p><p>And it doesn’t quite find it.</p><p>Not because it is hiding it.</p><p>Not because it is malicious.</p><p>But because that is simply not how it works.</p><p>And this is where the irony begins.</p><h3>We Fear AI Because We Think It Is Too Machine-Like</h3><p>Most public anxiety around AI comes from a single assumption.</p><p>That it is cold.</p><p>Deterministic.</p><p>Perfectly rational.</p><p>Unburdened by human fuzziness.</p><p>A machine that never forgets.</p><p>A system that never contradicts itself.</p><p>A database with opinions.</p><p>But the reality is almost the inverse.</p><p>Large language models do not operate like traditional software systems. They do not behave like a well-indexed knowledge base. They do not store your conversations as a clean, replayable archive. You really do not need to say please to save your future self.</p><p>What they do instead feels deeply familiar.</p><p>They remember <em>themes</em>, not transcripts.</p><p>They retain <em>patterns</em>, not artifacts.</p><p>They reconstruct meaning rather than retrieving files.</p><p>Which is exactly what humans do.</p><h3>The “Memory” Problem Is a Human Problem</h3><p>When I say “you said this earlier”, what am I really asking?</p><p>I am asking another entity to reconstruct a past moment based on context, relevance, and probability. Not to fetch a byte-perfect record, but to recreate intent.</p><p>That works surprisingly well when talking to people.</p><p>It works terribly when we expect computers.</p><p>And yet, LLMs sit awkwardly in between.</p><p>They are implemented in silicon, trained on text, deployed as software. But the interaction model they expose is not computational. It is conversational.</p><p>So when an LLM says “I’ve saved this” or “this is pinned”, what it often means is something closer to:</p><blockquote>“This concept is now more likely to influence future responses.”</blockquote><blockquote>Not: “I have stored an immutable object at address 0x4F3A.”</blockquote><p>That mismatch is not a bug.</p><p>It is a category error on our side.</p><h3>We Accidentally Built a System That Forgets Like Us</h3><p>Humans are terrible at exact recall.</p><p>Ask ten people to recount the same meeting, and you get eleven versions. What survives is not the wording, but the emotional and conceptual residue.</p><p>What mattered.</p><p>What stood out.</p><p>What aligned with existing beliefs.</p><p>LLMs do the same thing.</p><p>They compress.</p><p>They generalise.</p><p>They lose sharp edges.</p><p>Which is why asking an LLM to behave like a relational database feels oddly frustrating. You are talking to something that fundamentally works by approximation and expectation, while demanding precision and permanence.</p><p>In other words, you are having the same argument people have with each other all the time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*R2tRe09wPs8YwNDt" /><figcaption>Is ChatGPT just one amongst us?</figcaption></figure><h3>The Real Uncanny Part Is Not Intelligence</h3><p>The uncanny part of AI is not that it is too smart.</p><p>It is that it mirrors our cognitive flaws so well.</p><p>It forgets in ways that feel relatable.</p><p>It reconstructs confidently and imperfectly.</p><p>It sometimes insists it remembers something that it cannot quite surface.</p><p>And that is exactly what makes it unsettling.</p><p>We expected a machine.</p><p>We got something closer to a mind.</p><p>Not a human mind.</p><p>But a statistical one that rhymes uncomfortably well with how we already function.</p><h3><strong>Time Was Never There to Retrieve From</strong></h3><p><em>Smarter people please refrain to find flaws in my analogy</em></p><p>There is a useful parallel here from physics. Since Einstein, time is no longer treated as a flowing river in the universe, but as a dimension. Past, present, and future are not objectively “moving”. They coexist. The flow is something we impose for comprehension, not something the universe itself requires. In that framing, asking where the past “went” is already the wrong question. And this is where my frustration with AI memory starts to look misplaced. A retrieval request only makes sense if there was a stable past to begin with. But LLMs do not experience time as a sequence of stored moments. They operate in a kind of perpetual present, generating meaning based on probabilities, context, and constraints right now. No timeline, no archive, no before or after in the human sense. My insistence that it “go back” and fetch something says more about my need for narrative continuity than about the system’s failure. I was asking a timeless system to behave like a diarist.</p><h3>Maybe That’s Why This Feels So Disappointing</h3><p>There is a quiet disappointment when AI fails to be a perfect archive.</p><p>Because deep down, we wanted something better than us.</p><p>A memory that never fades.</p><p>A record that never lies.</p><p>A system that resolves ambiguity instead of amplifying it.</p><p>Instead, we built something that reminds us of ourselves.</p><p>Messy.</p><p>Contextual.</p><p>Selective.</p><p>And perhaps that is the real irony.</p><p>We fear AI will replace humans, while simultaneously being frustrated that it does not behave like a calculator.</p><p>But the truth is simpler.</p><blockquote>“It does not replace us because it already resembles us far more than we are comfortable admitting.”</blockquote><p>With the ENTIRE knowledge on the internet it has available to retrieve within 15milliseconds, it doesn’t know what was written just above. Perhaps, with the rise in ADHD diagnoses lately, maybe it’s time we put ChatGPT to the test as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/0*RjzlpcbxoqPi_13U.gif" /><figcaption>The famous “replicate this exact image” prompt in a .gif</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=937acd916c24" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Anthropology of Commutes]]></title>
            <link>https://adityaaserkar.medium.com/the-anthropology-of-commutes-83c8385c4b87?source=rss-d3bbddfe5821------2</link>
            <guid isPermaLink="false">https://medium.com/p/83c8385c4b87</guid>
            <dc:creator><![CDATA[Aditya Aserkar]]></dc:creator>
            <pubDate>Sun, 09 Nov 2025 19:14:58 GMT</pubDate>
            <atom:updated>2025-11-09T19:43:26.520Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>What Mumbai’s Trains Teach That Design Often Forgets</strong></p><p>I’ve always been vocal about what Mumbai teaches you, be it its pace, its patience, its capacity to function against impossible odds. But lately, I’ve been wondering <em>how</em> those lessons actually take shape. Is it just culture, or is there something deeper; something anthropological in the way people behave when space itself becomes scarce?</p><p>I’ve spent half of my adult life in awe of Mumbai. Not just its spirit, but its invisible systems of intelligence; the kind that only reveal themselves when you leave.</p><p>After years of living in Europe, I’ve begun to notice something I can’t quite decode. Public transport here, despite being only little less as dense, feels strangely dissonant. The U-Bahn in Berlin or the RER in Paris can be as crowded as a commuter trains in India in non-peak hours, of course not exactly squished and bone crushing like in Mumbai, but basically crowded inside the compartment with no more standing room, yet somehow, no one seems to <em>know how to be</em> in that crowd.</p><p>People cluster by the doors while the gangways remain empty. Passengers silently block each other’s paths; not out of malice, just a kind of collective blind spot. No one tells anyone to move in. Everyone’s polite, but oddly disengaged.</p><p>In Mumbai, that would be impossible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mn6BNXlU2_WZOIvkH3j3lA.jpeg" /><figcaption>A picture from Nürnberg, a non-conforming pattern emerges</figcaption></figure><p><strong>The Unwritten Code of Crowds</strong></p><p>Decades in Mumbai train you in a choreography of empathy. You give your seat to an elder or a woman without thinking. You take your backpack off to your feet or in the front to make space. You watch subtle cues on who’s likely to disembark, when to step aside, how to let the next person through. Also actively helping people to get off at a stop if they are unable to squish their way out.</p><p>Even minimal conversation becomes design in motion: gestures, glances, a thousand micro-coordinations that make the impossible commute possible.</p><p>Of course one would still prefer European levels of crowd over Mumbai crowds any day, but the article is about how systems and flow state originate. There naturally are social norms such as waiting for people to disembark, and the escalator etiquette, however they are not emergent. They are expected and the right way to do things. Emergent patterns are unsaid, like keeping bags on empty seats as an example.</p><p>Thus, most of the times, what looks like chaos in Mumbai is, in truth, a <em>self-organizing system</em>.</p><p><strong>When Design Over-Optimizes</strong></p><p>From a designer’s lens, this difference feels anthropological but also structural.</p><p>European transport design is about frictionless predictability. There are clean signage, clear lanes, automated announcements. It assumes that if the environment is designed perfectly, the human doesn’t have to adapt.</p><p>Mumbai, on the other hand, has no such luxury. Its systems <em>demand</em> human adaptation, improvisation, anticipation, empathy. The city teaches you to design with people, not just for them.</p><p>Don’t get me wrong, a lot of India’s collective empathy fails when it comes to cleanliness, waste management, or even respecting personal space and shared property. But in this particular arena, the negotiation of shared space as a group it somehow wins. Once you are exiting the platform, on the foot over bridge, you become a part of a river. You will not be allowed to not be a part of the river. If you try to become a rock, you will be toppled over, made into a pebble and then the river will take you in. But getting off at the platforms in Europe, there doesn’t seem to be such flowing rivers emerging.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*47OkOKDJxqLZ9THDJ0f8Hw.jpeg" /><figcaption>Picture from Mumbai, flow pattern emerges in social group</figcaption></figure><p><strong>Collectivism as Spatial Intelligence</strong></p><p>Perhaps this comes from a deeper social code. India’s collectivist fabric naturally rewards social prediction; knowing how one’s small action changes the collective rhythm.</p><p>In individualistic societies, design tries to remove that dependency: each person can and should function independently without interdependency and coordination. That is exactly the purpose of self empowerment. The system’s promise is comfort through separation. But that also means less practice in social sensing and therefore less need to read each other’s intentions in shared space.</p><p><strong>Predictive Empathy and Emergent Design</strong></p><p>I think of Mumbai’s local trains as a live model of <em>emergent design</em>: order that arises from repeated interaction, not top-down control.</p><p>People there don’t wait for rules to guide behavior; they develop their own feedback loops. Over time, these loops harden into norms: who stands where, who boards when, how seats rotate. It’s a distributed UX system built on millions of daily micro-decisions.</p><p>Designers often chase “seamless” experiences, but Mumbai shows that friction can be a teacher. When systems don’t guarantee comfort, people invent their own logic of cooperation.</p><p><strong>The Paradox of Equality</strong></p><p>In Europe, equality flattens differences. If everyone’s the same, then yielding becomes optional. In Mumbai, hierarchy of age, gender, urgency acts as a social design tool. It’s less about privilege and more about flow.</p><p>Designers often debate inclusion versus hierarchy. Inclusion isn’t about removing difference, instead it’s about choreographing it well.</p><p><strong>The Smell of Compliance</strong></p><p>I travel on the Nürnberg–Munich RE line almost every other day. It’s one of the most crowded routes I’ve ever been on. Often, Deutsche Bahn fails to send a double-decker train, and the density quadruples. People squeeze in, stand silently, and bear it.</p><p>On the same platform, there’s almost always a longer, emptier double-decker heading toward Ulm. No one bats an eye or asks why they can’t simply be swapped.</p><p>There may be a hundred logistical reasons behind it, but when something persists unchanged for years, the smell of compliance grows stronger.</p><p>Systems don’t just design behavior; they normalize it. And after a while, resignation begins to look like order.</p><p><strong>Cities as Behavioral Interfaces</strong></p><p>Ultimately, cities behave like interface; constantly shaping, nudging, rewarding, and penalizing behaviors.</p><p>European cities externalize order through design; Indian cities internalize it through social instinct. One outsources empathy to systems, the other to people. Both work, until they don’t and break.</p><p>As a designer, I keep wondering: what’s the ideal balance?</p><p>Can we design systems that leave just enough space for human improvisation, for empathy to emerge naturally, rather than be automated away?</p><p>Because sometimes, the most efficient systems forget the very thing Mumbai never lets you forget: <strong>that efficiency and empathy are not opposites, they’re co-dependent. </strong>From traffic formed in the bylanes due to people illegally parking their scooters to quickly buy something, to a bank employee opening an account even if you dont have a birth certificate. They are all part of this juxtaposition of effeciency and empathy.</p><p>And maybe that’s the real question,</p><p>When you stand in a crowded train, wherever you live, do you feel part of a system that moves <em>with</em> you, or one that simply moves <em>you</em>?</p><p>If you’ve liked this, consider reading<a href="https://medium.com/@adityaaserkar/designing-for-trust-in-untrusted-industries-c97cbe2f0a41"> how trust is created.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83c8385c4b87" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing for Trust in Untrusted Industries]]></title>
            <link>https://adityaaserkar.medium.com/designing-for-trust-in-untrusted-industries-c97cbe2f0a41?source=rss-d3bbddfe5821------2</link>
            <guid isPermaLink="false">https://medium.com/p/c97cbe2f0a41</guid>
            <category><![CDATA[trust]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[dark-patterns]]></category>
            <category><![CDATA[design-ethics]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Aditya Aserkar]]></dc:creator>
            <pubDate>Mon, 30 Jun 2025 11:04:35 GMT</pubDate>
            <atom:updated>2025-06-30T11:04:35.415Z</atom:updated>
            <content:encoded><![CDATA[<p><em>When credibility, regulation, and business logic pull in opposite directions</em></p><h3>The Trust Deficit</h3><p>Some industries don’t get the luxury of a clean slate. Users don’t arrive curious; they arrive suspicious. They’ve been burned before. Confused, misled, cornered by asterisks and opt-out fees.</p><p>They’ve read the fine print. Or worse, they didn’t, and paid for it.</p><p>In such industries, be it insurances, comparison websites, rental cars, shady flight websites, even healthcare, and now even aircraft manufacturing giants, the UX that a designer has to work with, isn’t just about frictionless flows or tasteful shadows. It’s about designing for negative trust.</p><p>And when the business is incentivised to obscure, upsell, or deceive? That’s where things get real.</p><h3>Trust Isn’t a UX Problem. It’s a Business One.</h3><p>If business got its way, every sentence would have an asterisk.</p><p>That’s not just a metaphor. It’s the roadmap.</p><p><strong><em>Cancel anytime</em></strong></p><blockquote>*Unless it’s a Sunday.</blockquote><p><strong><em>Free trial</em></strong></p><blockquote>*But we’ll charge you on day 6 just to be safe.</blockquote><p>As designers, we’re not just solving usability problems. We’re operating in a space where legal, brand, and growth incentives often contradict each other.</p><p>And often, trust is treated like decoration. Something you add once the flows are done. But trust isn’t a veneer. It’s the architecture. It literally is the whole flow, including the back-end, the inventory, the data structure, what is shown vs. what is withheld and so on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X4tg8jzsAVUN91eTG5nrhg.png" /></figure><h3>Brand is the Starting Line, and the Baggage</h3><p>After moving to Germany, I saw how the banking infrastructure is famously decades behind the rest of the world. Over the years of using it and being frustrated over the UX of all these old legacy banks where they are charging me money for keeping my money, while earning interest with my money; and to top it all, give zero user experience, no app, no instant money transfer, no notification on money deduction, not even a language selector, and not even being physically open. Still people trust them. The neo banks however, run on the same laws as any other banks, yet struggle to onboard customers with better UX.</p><p>Some companies begin with trust already in the bank. Siemens, Philips, even these boring banks. Their legacy, stability, and market monopoly act like UX multipliers. You don’t need to over-explain, over-design, or over-reassure.</p><p>But if you’re designing for a car rental platform, a neobank, or a digital insurer; you’re already starting in the red.</p><p>You’ll be asked to build credibility without the legacy. To reassure without overpromising. To simplify without omitting risk.</p><p>That’s not friction. That’s the job.</p><h3>The UX of Mistrust: Patterns That Break the Deal</h3><p>Here’s what erodes trust quickly, and how to spot it:</p><ul><li><strong>Inconsistency in copy and tone<br></strong>When the CTA says “No commitment” but the cancel button is buried three screens deep, users notice.<br>Trust erodes in the gap between what you say and what they see.</li><li><strong>Ad clutter and cross-sells<br></strong>Irrelevant banners, pushy add-ons, modal popups after checkout — all signal that the business cares more about revenue than the user’s task.<br>Nothing says “unstable” like a desperate UI.</li><li><strong>Legalese that buries meaning<br></strong>If your compliance message reads like a hostage note, no one’s reading. And that’s the point, right?<br>But when users find out what they agreed to, trust collapses. And support costs rise.</li></ul><p>Your customer support after purchase is a direct metric of investing in trust-UX. However, product’s don’t tend to see it. They ‘feature-ise’ it, that is, if at all they talk to the aftersales team.</p><h3>Measuring Trust When You Can’t Ask for It</h3><p>Trust isn’t just a vibe. It costs money when it’s missing.</p><p>Here’s how to quantify it:</p><ul><li>Gather support center complaints and call logs</li><li>Tag complaints that stem from confusion, inconsistency, or unmet expectations</li><li>Estimate support cost per ticket — time, agent hours, escalation</li><li>Design UX fixes that preempt those issues, and test again</li></ul><p>Suddenly, trust becomes a cost-saving measure, not a fluffy ideal. The business stops asking for “cooler” designs, and starts asking for “calmer” ones.</p><h3>How Designers Subtly Resist Shady Incentives</h3><p>Let’s be honest. Not every trust issue is solvable through better UX. Sometimes, you’re just being asked to sugarcoat a bad policy.</p><p>“Can we hide this until after payment?”</p><p>“Legal says we need to disclose it — but let’s make that collapsible.”</p><p>“This dark pattern works. Please don’t overthink it.”</p><p>In these moments, you’re not just a designer. You’re a negotiator. You’re deciding how complicit you’re willing to be.</p><p>But resistance doesn’t have to mean confrontation. Sometimes it looks like:</p><ul><li><strong>Documenting trade-offs<br></strong>“Here’s what we’re doing, and here’s the potential fallout.”<br>This becomes a time capsule for the next version, or the next designer.</li><li><strong>Designing ethical defaults<br></strong>Pre-select the option that aligns with what the user would want, not what the business wants them to miss.</li><li><strong>Giving users escape routes<br></strong>A clear cancel button. A refund policy that’s visible before payment. These aren’t just nice — they reduce churn rage.</li></ul><p>A close button when a cancel button already exists, is not just a design pattern, it shows that you as a designer, knows your user’s anxieties.</p><p>Think of these as micro-revolts. Quiet UX acts of integrity. They won’t always win the sprint, but over time, they shift the culture.</p><h3>Visual Pollution and the Erosion of Credibility</h3><p>Trust isn’t just broken by words. Sometimes, the very layout of a screen tells a user:</p><p>“You’re not the priority here.”</p><p>This shows up as:</p><ul><li>Banner ads for unrelated services</li><li>Cross-sells shoved between checkout steps</li><li>“Personalized” offers that feel like they were picked out of a hat</li></ul><p>Even if the product works well, these signals say:</p><p>“This space isn’t about your goals. It’s about our quotas.”</p><p>Clutter isn’t just ugly. It’s suspicious.</p><p>Because when the interface looks desperate, users assume the company is too.</p><p>Designers often inherit this mess. Marketing wants promo real estate in the hero section, with asterisks. Product wants upsell placement of the feature they just launched to get visibility. Legal wants disclaimers, but in a collapsed state, just in case.</p><p>Your job isn’t to say no to everything. Your job is to negotiate for signal over noise.</p><p>A trust-first layout is clean, focused, and narratively aligned. It says:</p><p>“We know what you’re here for, and we’re not trying to distract you from it.”</p><h3>Creating Narrative Consistency Across the Funnel</h3><p>Trust is rarely broken in a single screen. It frays across time.</p><p>It’s the drip effect — when copy, tone, or promises shift slightly with every touchpoint.</p><ul><li>The ad said “Free,” but the product says “Trial.”</li><li>The email says “Cancel anytime,” but the dashboard makes you email support.</li><li>The headline sounds helpful, but the tooltip reads like a legal disclaimer.</li></ul><p>Each of these on their own is forgivable. Together, they form a narrative collapse.</p><p>The user doesn’t know who to believe anymore. That’s fatal for trust.</p><h3>Solution: Build a narrative architecture.</h3><ul><li>Audit the entire journey: from ad to landing to onboarding to dashboard to support</li><li>Ask: does the story hold up?</li><li>Align tone and terminology across departments: marketing, legal, product, CX</li><li>Create a glossary of non-negotiable words and their intended usage</li></ul><p>Think of it like a screenplay. Every line and every scene needs to serve the same plot.</p><p>Consistency isn’t just clean. It’s credible.</p><h3>Designing a Trust-First System</h3><p>What if trust wasn’t just a feeling you chased, but a system you documented?</p><p>Imagine a component library that flags:</p><ul><li>“Legally required copy — no edits allowed”</li><li>“Trust-sensitive interaction — user control must be obvious”</li><li>“Dark pattern risk — add extra validation”</li><li>“Expected escalation — must have visible support CTA”</li></ul><p>Or Figma components tagged with:</p><ul><li>trust-variant: high</li><li>compliance-sensitivity: strong</li><li>language-check: legal review required</li></ul><p>Suddenly, your system is not just about buttons and breakpoints. It’s about values at scale.</p><p>Design systems can encode accessibility, localization, and performance.</p><p>Why not ethical credibility too?</p><h3>Final Word: Trust Is the Interface</h3><p>You can’t A/B test your way into trust.</p><p>You can’t metrics your way out of moral debt.</p><p>Trust is slow to earn, fast to burn, and really expensive to rebuild.</p><p>But it’s also your product’s most valuable conversion funnel. Without it, nothing else matters.</p><p>Designers don’t always get to choose the business they’re in.</p><p>But they do get to choose the seams they soften, the distractions they remove, and the asterisks they fight to explain.</p><p>You’re not just building flows.</p><p>You’re building the space where someone decides whether to believe you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DMaE8w8U_3_M3H4Rxf55ZA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c97cbe2f0a41" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What UX Teams Get Wrong About White-Label Design]]></title>
            <link>https://adityaaserkar.medium.com/what-ux-teams-get-wrong-about-white-label-design-2f513b36211f?source=rss-d3bbddfe5821------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f513b36211f</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[enterprise]]></category>
            <category><![CDATA[white-label]]></category>
            <dc:creator><![CDATA[Aditya Aserkar]]></dc:creator>
            <pubDate>Tue, 24 Jun 2025 08:42:12 GMT</pubDate>
            <atom:updated>2025-06-24T08:42:12.440Z</atom:updated>
            <content:encoded><![CDATA[<h4>This week alone I created two car subscription funnels for white-label pitch decks. But is that the real challenge?</h4><p>White-labeling sounds neat on a roadmap slide. A neat little promise: “Design once, ship everywhere.” It promises scale, modularity, and elegance. But for those of us who’ve actually been in the weeds, crafting them, pitching them, maintaining them — white-labeling can be a beautiful lie.</p><p>This week alone, I created two entire car subscription booking funnels — each for a different white-label pitch deck. That makes it the fourth one <em>this month</em>. And honestly? I had to pause and ask: how the hell did I just do that?</p><p>The answer lies in what we’ve come to unlearn about white-labels. The myths we keep repeating, and the systems that get quietly stretched beyond their breaking point.</p><h3>The Problem Isn’t That It’s Hard. It’s That It’s Easy to Get Wrong.</h3><p>There’s a prevailing misconception that white-labeling is just… thematic. Change the logo, swap in brand colors, switch the typeface, maybe tweak some corner radii. Done.</p><p>But if your product is something a user interacts with — not just views — then no two brands are ever truly interchangeable. A white-label version for Rolls Royce should not, and <strong>cannot</strong>, resemble one for Dacia.</p><p>Not just in how it <em>looks</em>, but in how it <em>thinks</em>.</p><p>Take transparency. A luxury brand might opt for minimalist disclosures, personal concierge prompts, soft transitions. Meanwhile, a budget-focused brand may require up-front pricing, comparison charts, reviews, and tooltips galore. Same flow, entirely different architecture.</p><p>To assume this can be handled with palette swaps is to ignore what branding really is: a promise, a hierarchy, a mindset. Your design needs to reflect that — not just skin it.</p><h3>Start With Frameworks, Not Flexibility</h3><p>The smart way to white-label is to begin by designing <strong>packages</strong>, not just a design system. These are not superficial themes. They’re <em>opinions</em> about how a brand shows up in product form.</p><p>Each package answers:</p><ul><li>What does this brand over-communicate? What does it leave unsaid?</li><li>Where does it want to feel empowering, and where does it feel automatic?</li><li>What is the emotional arc of the user journey?</li></ul><p>A Rolls Royce-esque package may lean into indulgence, serenity, exclusivity. A Dacia-style package may highlight efficiency, clarity, and control. These mental models affect not just visual design, but microcopy, affordances, feedback loops.</p><p>When you define packages this way, your WL architecture becomes smarter. It becomes <strong>context-aware</strong>, and crucially — <em>scalable</em>.</p><h3>Constraint Is a Strategic Gift</h3><p>It’s easy to fall into the client-pleasing spiral. A WL partner says, “Can we make the CTA a warmer blue?” And you say, “Sure.” They say, “Our brand font is this weird proprietary variable serif — can we use that?” And you say, “Well… maybe.”</p><p>But every yes is a fork. Every fork is a new maintenance burden. And soon, your WL system becomes a museum of exceptions.</p><p>The trick isn’t to say no out of stubbornness. It’s to say no <em>strategically</em>. Set up guardrails. Offer only specific levers to pull — via tokens, presets, packages. Not infinite sliders.</p><p>That’s the pitch: <em>predictability as a product feature</em>. And it works, if you respect your own architecture enough to defend it.</p><h3>Documentation Helps. But Tokens Are Divine.</h3><p>Good documentation can smooth onboarding and reduce ambiguity. But it can’t fix entropy. It can’t solve for divergence. Tokens can.</p><p>Tokens are not a convenience — they are a philosophy. They allow WL variants to speak the same underlying design language. Change a token, and you cascade a new identity across the board.</p><p>But tokens don’t materialize magically. You have to plan for them, from Day 0. When you design your components, your content styles, your layout grid — everything has to respect the token hierarchy. Only then does WL scale become a promise you can keep.</p><h3>The Hidden Beast: Maintenance</h3><p>Let’s talk about what happens <em>after</em> launch.</p><p>Your core product updates its layout engine. Your branding gets a refresh. Your backend APIs get smarter.</p><p>But your WL partner? They want to stay on version 2.3.1. Because they “like the old one.” Or worse, Business says, “They didn’t pay for getting updates.”</p><p>Suddenly, your sprint velocity is eaten up by legacy patching. Your WL is dictating how long you have to keep dead code alive. Your team becomes a service desk for decisions someone else made last year.</p><p>So — futureproofing is not optional. It has to be encoded both in your contracts <em>and</em> in your code. Design refresh policies. Deprecation timelines. Optionality for plug-and-play adoption.</p><p>If this is missing, you’re just dragging a heavy cart with shiny wheels.</p><h3>How To Actually Do White-Label Design</h3><ol><li><strong>Segment your white-labels</strong> — Don’t build per-client. Build for brand archetypes. Rolls vs Dacia. Think in packages.</li><li><strong>Design the framework, not the options</strong> — Define where flexibility <em>makes sense</em> and where it breaks scale.</li><li><strong>Tokenize everything</strong> — Spacing, colors, typography, interaction speeds, content tone. Make it swappable.</li><li><strong>Plan for the future</strong> — Refresh cycles, legacy handling, versioning discipline. Write it down.</li><li><strong>Build a pipeline</strong> — From pitch deck → sample audit → package match → tokenization → mockups → plug-and-play components.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JFqgoAaMw81qs1DLKPm70A.png" /></figure><h3>Example: Rolls Royce vs Dacia (Zoomed In)</h3><figure><img alt="Table about what essence a brand brings in, that must be considered for White Label solutioning." src="https://cdn-images-1.medium.com/max/1024/1*NfDZMhxfgKH7idtJCyJm3A.png" /></figure><p>It’s not just how it looks — it’s how the product <em>behaves</em>. Designing for this requires more than paint. It requires intention.</p><h3>Final Thought</h3><p>White-labeling isn’t a visual reskin. It’s a multi-layered negotiation between brand, user expectations, and systemic architecture.</p><p>Done well, it multiplies your reach. Done poorly, it erodes your roadmap. So before you take that next WL request, pause.</p><p>Ask not “Can we do this?”</p><p>Ask: <strong>“What kind of WL is this?”</strong></p><p>And if the answer isn’t already in your packages — you’re not ready yet.</p><h3>✅ White-Label Readiness Checklist</h3><p>Thinking of building white-label solutions? Start here:</p><ul><li>Have you defined WL <em>packages</em> by brand archetype?</li><li>Is your design system tokenized from the ground up?</li><li>Are constraints clearly defined and communicated?</li><li>Is your update/maintenance policy written and shared?</li><li>Do you have a repeatable process from pitch → build?</li><li>Have you defined what’s negotiable vs. non-negotiable?</li><li>Is there a design-tech handshake to back all this?</li></ul><p>Print it. Share it. Fight for it in the next roadmap planning call.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O63zFgfha1-xBfYlQvXZLA.png" /></figure><h3>👇 Got WL war stories, odd client requests, or systems tips? Drop them in the comments.</h3><p>Let’s make white-labeling smarter — together.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f513b36211f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Get a UX design job in Europe from India.]]></title>
            <link>https://adityaaserkar.medium.com/get-a-ux-design-job-in-europe-from-india-f5265c0680a2?source=rss-d3bbddfe5821------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5265c0680a2</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[india]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[europe]]></category>
            <dc:creator><![CDATA[Aditya Aserkar]]></dc:creator>
            <pubDate>Fri, 11 Mar 2022 10:21:08 GMT</pubDate>
            <atom:updated>2022-03-11T13:44:16.601Z</atom:updated>
            <content:encoded><![CDATA[<h4>Wait, Why though?</h4><p>As you might imagine, the engineering centric world will always ponder over all the <strong>Hows</strong>. How to land a job in Europe? How to create the best portfolio? How many projects to display in it? The internet is filled with it. But before we start pinning out the <em>How-might-we</em> post-its, lays the job of a designer. And this article aims to do that job — <strong>The Whys.</strong></p><p>Clearly, my fascination with recursively asking <strong>Why</strong>, to every single thing is not going to stop anytime soon. This type of a write-up has been long pending anyway. After getting hundreds of phone calls from fellow designers who are trying to move from India to the Europe to pursue a career, I have been pondering about writing it all down. I also try to find out why is it that they are thinking of making this move.</p><p>Those of you who know me, know my perpetual inclination towards healthcare design, urban planning and education. This goes to say that I had the privilege of moving from one healthcare biggie from India, to another in Germany. Thus, the difficulties I faced while making this move, would have been certainly lower that what you might when you apply. Thus, my writing down of the <em>Hows </em>that I dealt with, might not do justice to the process in the first place. <em>#disclaimer01</em></p><p>What I plan to do is to talk <strong>mostly about motivations, expectations, differences</strong> and the likes. <em>(Personally, I dread that this might end up again as a rant, but given my perennial cynicism, that’s a given. But however ranting the article might sound, we need to realise, at each comparison, that the two societies are completely built for different things. And only with acknowledging the differences and comparing them with our needs, can we better our surroundings for us.)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FQHgvcCac2kCH9k2xXU4mg.png" /><figcaption>In reality, I had a little more bags, and a little less hair while moving.</figcaption></figure><h3>Motivation</h3><p>What is your motivation to move?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/981/1*b1cizPUycaYBWUseyUjSWA.png" /></figure><h4>Financial</h4><p>Straight to the point, if you are one of those who is motivated by money, <strong>unfortunately Europe might not be the right place for you. </strong>In that case, you’d rather look for jobs in the US if you still want to move out, or else you’d easily save more moolah living in Bangalore or the likes. I could give you a justification excel sheet, but believe me, don’t move for this reason. You would earn more, but savings would definitely be far less. For budgeting purposes, check out <a href="https://www.numbeo.com/cost-of-living/">Numbeo</a>. You cannot expect to save 2 lakh Indian rupees a month, that is simply not gonna happen in Europe. The EU society does not need you to save money like we Asians do. Healthcare is taken care of, partially pension is taken care of, why would you need to save? You’d need to save for that’s what you’ve been trained with right from adolescence in Asian countries. Now that thats out of the window, lets look at others.</p><h4>Social</h4><p>European cities are an amalgamation of the world. It is beautiful to experience. Different languages, different cuisines, completely different topography. People from all over the world are here. It is quite literally the melting pot of cultures. In spite of so much inflow, each city or region has its very quintessential character. If you are someone who loves exploring yourself while exploring people from all over our Earth, this is absolutely the place for you. Listening and creating your own stories on the way. So many types of meetups, to suit your needs. With the large expat population, you will meet, love, cherish the bonds, the similarities, and embrace the differences amongst fellow humans.</p><h4>Education</h4><p>Though this article is not aimed at this scenario, it could just be the best path to take. Hands down the best motivation to move abroad. Not that education in itself is necessarily better, given that the fundamental basis of education that stems from the western philosophy is bound to be different. Constraints of society is different, therefore education focus is different as well. However, <strong>Education is highly subsidised, universities have real good facilities and expenditure for research, cultural amalgamation and social integration is kept at a priority.</strong> And come on, most universities are hundreds of years old, with amazing legacy, and the buildings! If I were you, I would gawk at the amazing architecture day in and day out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/985/1*pN8ty4IM-4iMvyErL6eNCg.png" /></figure><h4>Quality of Life</h4><p>If you want to ensure <strong>work-life balance</strong>, overall Europe would easily rank better than almost any country in the world.</p><p>Depending on the city you live in, the <strong>commuting time </strong>would surely be halved. This would immensely add to your quality as well as quantity of life. The time you spend only waiting for your Uber in Bangalore, will be the time you take to reach office in a large part of Europe.</p><p>If simply <strong>breathing</strong> <strong>fresh air, travel, partake in art, museums, history, languages, cultures, architecture, interact with people of the world</strong>, etc. is something you fancy, then surely there can be nothing better than Europe. No arguments there.</p><p>Beware though that travel within EU is not all that inexpensive and feasible. Overnight and direct trains unfortunately haven’t yet been discovered here. If you fancy ZMND-style cross country Eurotrip drives, be ready to shell out big bucks. A German drivers license would set you back about 1500~2000 EUR and 6 months of training with at least 2 attempts.</p><p>The kind of travels that occur in India, like a weekend trip to Waynaad, Coorg, Goa or something (or the north Indian equivalent) in which you not once consider the costs associated with it; simply cannot happen in Europe. Though Paris would be only a few hours away, it is not a weekend trip. You simply will not be able to wisely afford an ad-hoc trip like this. So if going on weekend trips for a few hundred kilometer every week is your thing, that is almost certainly not possible economically and logistically in Europe.</p><h4>Personal Growth</h4><p>The above part then brings us to personal growth. If you want to shed your workaholic tendencies born in India/Asia perhaps for psychological or physiological reasons, then this would be a good place to be. Learning to have a demarcation between work and personal life might be something that you’ve been trying to incorporate but has never been possible. You could do that here. Focusing on other aspects of life, to know that there are subtle nuances to living. Invest time in relationships, personal goals, sports, etc. would be the best to do while living here. If that is on your agenda, moving here might be a good step. Buy a paddle boat, and bike to your nearby lake. Look up the sky when it snows, start living again, it is magical.</p><h4>Professional Growth</h4><p>A lot of companies have their headquarters in Europe. This would be the center for the decision making processes. If you feel that you are constantly hitting a ceiling in terms of ability to push your ideas into the roadmap in an European MNC, this would be one reason. This would be overridden by the nature of the company though. The flipside of this is that the fast paced perpetual learning environment that Indian/Asian cities facilitate, would be difficult to find here. High levels of complacency born out of the first world comforts and that the development will continue outside of the EU anyway, will be a common sight. People also tend to stick to one company for decades. If it were happening in India, the HR would’ve ruled us out by saying that since you didn’t switch jobs, you were seeking for comfort, we don’t want you!</p><h4>Simply Get Away</h4><p>You can tick this option if you are fed up of the Indian political scenario, want to get out of the rat race, the constant honking traffic, sweaty train rides or simply want to get out of the constant infringement of relatives asking you when you plan to proverbially — ‘<em>beta shaadi kab karoge</em>’.</p><h3>Expectation, and differences.</h3><p><strong>What to expect or what to look for?</strong></p><p>My opinions are based on a small city — big company coupling. They might be completely inverted in a big city — small company couple thus might not be applicable for that. I shall write more on that when I move to that framework. Although I would proof-read this writeup through other fellow designers in the same boat, I take the risk of penning down honest the thoughts. However politically incorrect they might end up being. <em>#disclaimer02</em></p><p>To make a decision of ‘where to move’ hangs on multifold parameters. You would need to evaluate your motivations as above and then choose which one of them tops your priority chart.</p><p>You would then need to couple the motivations with what are your expectations. Rank them by priority. You are not going to get it all. <em>#selfacceptance</em>. Are you moving to focus on a specific domain/role/responsibility or other career related parameters, or are you looking at more of social, multicultural, demographic exposure. The answer would rarely lead you to both, however a balance can be thought of.</p><p>This also completely depends on which phase of life you are at. You might want to proliferate in your professional lives, or your personal. As previously mentioned, there is a thick line between work and life in Europe overall.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x6QFOk-g-sPvsoZizDTyrw.png" /></figure><p>Below would be some of the micro and macro deciding factors and expectations that one needs to set in.</p><h4>City</h4><p>Personally, now that I know myself a bit better, I would take this as the prime deciding factor. Even though from a general Indian mindset, one would move for the opportunity, will soon realise that the self is more important. This might mean to prioritise a place to be in. A place changes everything. Kinds of people you would meet, and be with; places you can visit in terms of accessibility; money that you can spend/save, and so on.</p><h4>Domain</h4><p>This had been my deciding factor while moving. If you wish to stay within a domain, there are a plethora of great companies set up offices here. Domain knowledge is well respected here and would certainly be a big plus.</p><h4>Role</h4><p>Roles are usually malleable. Also moving within should be fairly possible. Hence fixating on this as a reason to move, might be too constricting. Unless of course you are in a niche market and this is top priority.</p><h4>Small / Large organisation</h4><p>Naturally, size of organisation gives you different grades of freedom at your work. Freedom to experiment, freedom to learn, grow and so on. As a side note, for a designer, one should check the metrics of measurement of a company. How do they maintain a balance between the value to the user and the business / sales goals. Large and small organisations handle it fairly differently, both having different buffers to operate in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hFnB37CfQ6D5mGfZQcLO0w.png" /></figure><h4>Overall lookout</h4><p>Well, this might be a difficult section to pen down while staying as politically correct as possible. However, the central aspect of the difference in the expectation out of life from an Indian/Asian upbringing versus a west European upbringing is starkly evident with each passing minute. As a designer, you would/should be aware of the ethnographic viewpoint of lives of people and the circumstances that maketh them.</p><p>While every step you walk in Koramangala would be million dollar evaluation start-up and every stone you throw lands on a founder of some or the other company, the investment of self and efforts towards the said startups is easily way beyond what would be considered legal in western Europe. Indians might be attuned to being hypercompetitive straight from birth, since even that would determine the hospital our parents could afford. This competitiveness for existence is simply not there in the EU, why should it.</p><h4>Work Culture</h4><p>The word culture means totally different in the definition of the west and the east. Your quarterly company sponsored dinners, or team outings, or the pleathora of HR organized proverbial <em>Rangoli competitions, sports events, family day out </em>and the likes, simply cannot happen. You need to know that people would avoid mixing work and personal life as much as possible. CEOs of your company dancing with you on booked venue with celebrities performing on Bollywood numbers is simply unimaginable in western Europe. So if you count on blowing off steam as well as getting to know the real people behind your colleagues over the sports day, you’d feel left out. Team building activities are not on the priority, since colleagues are supposed to be only colleagues. Surely if you wish more out of them, it would be on your own accord, the company would never ever internalize it in the process.</p><p>Employees do not switch jobs that often. Their idea is to get comfortable at a place. You will also find people not wanting to climb the ‘ladder’. There will be plenty who are once a developer, always a developer. They would simply not want to take on the different path of becoming a people manager, or cross over to being a product manager, and so on. This also means that the incentives given by the company would simply not be. Don’t expect a few sweatshirts every winter, or company tee shirts, umbrellas, shoes, I don’t even remember what all I got. Awards and recognitions are also comparatively way lesser in my experience. While in India, every small project would get you a few thousand rupees in addition to a Bravo medal at a townhall.</p><p>Not sure if this next point comes under work culture, but food is usually not free in this part of the world at the workplaces (or anywhere :P)</p><p>While at this stage, another attempt if the earlier disclaimers have been forgotten, all of these are mere generalisations, naturally, there exists things outside of this middle of the bell curve in both the countries/societies. <em>#disclaimer03</em></p><p>As mentioned, the objective of people, their purpose in life is literally to live it to the fullest. To enjoy each tiny aspect of it. Something that majority of Indians simply cannot fathom. We have been accustomed to, (and even want in my case) to blur the boundaries between work and life. This is all the more evident when you have a design lens that you look at the world with. Every object, process, system, app, streetlight, bench, bus route, pothole, etc. that you see, you would enter the problem solving mode.</p><p>The other aspect is that of proficiency. Go to a design studio in India, you will inevitable find a bunch of trained designers. European system doesn’t seem to work that way. People want to find their passion not just in their formative years, but throughout their lives. Which is a really good thing on a personal level. So it would not be alien to see someone who was a musician for 14 years, then did advertising for 5, and moved to UX research from there. I am certainly not a proponent of degree based designations. However, I am a proponent of a design sensitivity based designations, those who have a keen eye on the subtle nuances, right to the systemic framework of things.</p><p>The money aspect has already been discussed, however, reiterating, if you seek for annual bonuses, Above&amp;Beyond or such awards, or simply annual appraisals, it might be better to forget it. Given that the inflation of prices in the country is so low, the dearness of living almost stays stagnant. It is only now that some of the fixed cost has been increasing. We will have to see how it goes going forth.</p><h4><strong>Simply Living</strong></h4><h4>Services</h4><p>India / Asian countries are a service oriented economy. It is quite literally the service provider of the world. Thus one needs to understand the basic differences in the outlook of the two economies. The ample availability of workforce for every aspect of life has mostly been taken for granted. The said workforce would be meagrely paid and exploited. For European economies, workers rights are at the top.</p><p>Thus it would not be feasible to have an app to send a boy to fetch around and deliver a packet of your morning cigarettes, milk and eggs within 10 minutes after you order it as you wake up early in the morning.</p><p>The second thing would be data privacy. Indian society unfortunately hasn’t been much into privacy, while the GDPR is a complete contrary. You will not get a text message on each card swipe. To add to that, transactions would appear on the bank a few days after they have been processed. This means that you simply cannot budget your expenditure using real time apps.</p><p>Well, if you have thought of moving out of the country, you might already have forgone a house help. You would’ve decided to cook for yourself, but that is not all. In case you are a regular user of services in India that take care of your usual needs, you might want to think harder. You’d have to leave, Zomato/Swiggy, Dunzo, BigBasket, Amazon one day deliveries, or simple financial services such as UPI, investment apps, budgeting apps (Walnut/Splitwise), or commuting apps such as Uber/Ola, Yulu, Zoomcar, Bounce, apps for doctors (Practo), handymen, movers (Porter), UrbanClap and the list goes on and on. Some larger cities in Europe would have some apps that replicate these business models, but largely none. If they exist, it would be expensive that it doesn’t make sense to use it. Oh and yes, unavailability of unlimited mobile internet will pinch you every single day.</p><h4>Weather</h4><p>Weather is a thing here. If you fancy living inside a refrigerator for a large part of each year, then Europe would be the place for you! You would’ve never in your life used the weather app in India, but in Europe, you will have to check it each morning and a day prior. There will be weeks where you don’t see the sun, you will start taking VitD tablets. And other days when the sun is out and no one works for the entire month. Summer holidays are not just for kids anymore. Negative temperatures over the winters and especially the lack of sunlight, if paired with being alien to the surroundings will be downright depressing. <br>Okay, enough of negatives, but the amazingness of the actual changing weather will be observed here. All the seasons are extremely unique and lovely in all of its aspects. Summer is like a fiesta. Everyone is in their top spirit. Cities are packed with people, lakes and rivers are filled. Fall brings in the colourful beauty which is then followed by winter. However dreaded, there is still nothing more magical than snow. The spring then closes the loop by bringing us flowers. In India, we take weather completely for granted. This will change and we will appreciate the beauty of nature. I cannot be more grateful for gradually growing fond of these weather distinctions here and the beauty it provides. You can actually map your life on a weather timeline. Ah, the winter of 2020, the summer of 69.</p><h4>Language</h4><p>Again, the disclaimer stands. Most large European cities would speak English, and smaller cities, younger generations would too speak English. However, for all practical purposes, you will need to learn the local language. Cannot stress this enough. This would mean that you pick a dedicated country, and invest a year or two to learn at least the basics of the language. This will be the foundation for you to integrate in the society, get help and service when needed. <br>Learning a language is one of the most wonderful experiences. I believe most Indians already have a knack for learning languages. Languages open a whole new world. You get to understand culture, traditions, history and the psyche of the people. The comparisons, the etymology, even if you are no language nerd, you will start loving these nuances.</p><h4>Closing</h4><p>Thus, to sum up, this has been largely a collation of the pros and cons of moving to European country, coming from an Indian (or Asian) city. One needs to evaluate which phase of life s/he is at, and what are the motivating factors that would contribute to the decision making. You will invest multiple years of your life in this process, decide wisely.</p><p>Wish you all the best :)</p><blockquote>It would be really helpful if you comment below your reasons to want to leave a country for another. It could be your Childhood dream, the reelection of the far right party, the tiredness of constant city life, perpetual work day and night or simply to just explore and so on.</blockquote><blockquote><em>Thank you for reading and I wish you and your loved ones a good physical and mental well-being.</em></blockquote><blockquote><em>If you liked reading this, consider reading how city design affects our mental well-being.</em></blockquote><p><a href="https://adityaaserkar.medium.com/a-city-and-its-architecture-a22d7041e7fd">A city and its architecture</a></p><blockquote>All amazing illustrations are courtesy <a href="https://undraw.co/">https://undraw.co/</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5265c0680a2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Debt]]></title>
            <link>https://adityaaserkar.medium.com/design-debt-8690a4e107f5?source=rss-d3bbddfe5821------2</link>
            <guid isPermaLink="false">https://medium.com/p/8690a4e107f5</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Aditya Aserkar]]></dc:creator>
            <pubDate>Sun, 09 May 2021 09:30:37 GMT</pubDate>
            <atom:updated>2021-05-09T09:30:37.795Z</atom:updated>
            <content:encoded><![CDATA[<h4>Part two — Fail Fast, fail often.</h4><h3>What is Debt?</h3><p>The <strong>pandemic is the debt we are paying</strong> to the failure of recognizing our damaging hyperconsumption, failure of preparing and foreseeing the largely abysmal healthcare. <strong>The next stronger mutations will be the debt to be paid by the world for the withholding of the IP rights.</strong> So now that each human being on the planet knows about debt in an experiential way, maybe there is a chance to be more empathetic towards talking about the what and hows of Design Debt.</p><h3>What is Design Debt?</h3><p>In the <a href="https://adityaaserkar.medium.com/design-debt-a686d6a8a0de">previous article for Part One</a>, I attempted to talk about visualizing design debt from an interface. In this one, I would try to talk about how it is created. First broadening, and then narrowing from there.</p><p>One problem regarding design debt that I realize lies in the definition of ‘<em>Design</em>’ itself. Most designers would look at Design, as a core all-encompassing functional aspect of any product-process development.</p><h4>Example:</h4><p>The <strong>logistical challenge of vaccinating the majority of human beings on the planet,</strong> <strong>is a supply-chain design problem.</strong> <br>The <strong>mRNA synthesis itself was a biotech vaccine design challenge</strong>. <br>The <strong>publicity of the efficacy of the vaccine is an advertising design challenge,</strong> and so on. <br>Thus, as soon as you solve something for someone, you are designing. This is where the understanding of this someone — <strong>the user,</strong> comes to play such a vital role. An interface is just a tool/means to achieve the user’s expectations. Through this, I attempt to relate to the ‘Fail Fast, fail often’ paradigm.</p><p>In my opinion,</p><blockquote>It is in fact Design Debt, that results into Tech debt.</blockquote><h3>How is design debt created?</h3><p>The ‘<em>Fail Fast</em>’ often does not talk about the definition of this <em>Fast</em>. And not defining this seems to usually be one of the root cause of the design debt. While failing fast, the systemic changes that the product and to the functioning and processes of an organization go through, is often ignored. Perhaps one should try their best to fail in repeated user testing cycles and not as much in a released product. Perhaps rather than putting all efforts in failing faster, effort should be put in judicious, meticulous, farsighted and thoughtful decisions.</p><p>One core reason for design debt is how one begins product development, and how much of the user’s perspective enters in the product.</p><blockquote>Developer-Centric Design (DCD) is a unsaid paradigm.</blockquote><p>DCD and Stories. Yes, User Stories. Throughout all these years, I’ve seen the Agile User Stories, being written from the perspective of the development.</p><h4><strong>Example:</strong></h4><blockquote>“In order to avoid synchronization issues of multi-threads in backend, we need to route requests into the front-end box, otherwise exceptions would occur in the system interfacing.”</blockquote><p>This could easily have been,</p><blockquote>“As a clinician, I would like to see the same patients in the examination as in the list, so that I can verify if I’m performing the correct patient-examination.”</blockquote><p>Sure, there will be actionable tasks inside a user story, and these tasks can be developmental requirements but the story needs to be a User’s Story.<br>This fallacy not only ostracizes the development team from the users, it also in a way isolates them from the cause, vision and mission of the company itself.</p><p>As the situation worsens when there are aspects of ‘<strong><em>How should the user do it</em></strong>’ embedded within these User Stories.</p><h4>Example:</h4><blockquote>“As a clinician, at the time of setting up the scan, I would like to see the patient information<strong> on a tablet</strong>, so that I can verify the patient details before the scan.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XyRqTnnTjI_ZT1iZx-yhqg.png" /><figcaption>Me thinking what all changes can this design test result influence</figcaption></figure><p>The other main presupposition of failing early that I think organizations miss, is learning from those failures. The tests themselves are done at a much later stage in the product development process. Thus, the tests iterations are too close to make a substantial difference in your product architecture. Thus, the possible learnings from a test would also be very shallow.</p><p>A UX test should test the product architecture, and not simply whether the button should be on the footer or on the left panel. A UX test should also bring out the fallacies in the product development processes, and not simply whether the user is able to click on something or understand an icon.</p><blockquote>A UX test should prioritize testing different product architectures and hierarchies and not simply the color of a button.</blockquote><h4>Example:</h4><blockquote>For an AI-enabled training system, the test should be aimed at evaluating which metric/parameter of the AI needs a user input (according to the user) to increase the confidence level, and not how. How, as usual, comes much later.</blockquote><p>Another crucial aspect is what to do with the test results. If you have performed the test too late in the development process, you would have not much leeway other than patchwork.<br>However, what you could do is <strong>feed the user test results for the usability of design patterns into your Design System</strong>, if you don’t, massive debt is underway.</p><h3>So, what to do about it?</h3><p>Apart from the core problems and solutions already mentioned above, there could be some more systemic changes that could be done. <br>Clearly, in a way an antithesis of this current paradigm —<strong> “Design Early, Design Often”</strong>, does that make sense? It tries to elucidate that design is not an execution role, rather a planning role.<br>Design, though now has a fancy little corner within the fairly undesigned agile chart below, however contradicts this core philosophy, amongst other things. Just like a software codebase/framework cannot align to fail early fail fast, certain aspects of design cannot too. The implications of bad primary navigation and basic hierarchical inconsistencies are simply too big to come out of.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*La8mqHK3d0tYquWD.png" /><figcaption>Source: <a href="https://www.scaledagileframework.com/lean-ux/">https://www.scaledagileframework.com/lean-ux/</a></figcaption></figure><h3>What could be the common causes of design debt?</h3><p>Adding to the earlier points, there are things that happen when the org tries to fail fast and fail early. Certain aspects of the product get cemented in the process. I try to abstract the problems and the possible solutions of some.</p><h4><strong>Legacy products</strong></h4><p><strong>Problem <br></strong>Dogmatic navigations and workflows are prime examples. Software that emulates CRUD to be the maximum capability of it and then expects to have an AI layer on top, is a recipe for disaster. <br><strong>Solution<br></strong>With changing times, codebase and design paradigms need to change.</p><h4><strong>Process</strong></h4><p><strong>Problem <br></strong>A product development process is thought of this dogmatic thing that will remain. This has to change. The product will be only as good as the worst process. <br><strong>Solutions<br></strong> Sensitizing and allowing for alterations in the process is utmost importance. — The earlier example of integrating usability feedback directly into to design system instead of the product is one central process anomaly which most likely does not happen. <br>— This is similar to language localization which quite often, wanders around as an afterthought, and thus is rarely designed for. It is a debt, it will come back and bite you.<br> — Include product management in your user testing and usability testing. If possible also the developers. If possible, book a theater and project it there :)</p><h4><strong>Bio magnification of bad design</strong></h4><p><strong>Problem</strong><br>The aspect of ‘<em>We’ve always had it this way</em>’, and the inability to revert from bad design decisions will only magnify it to unimaginable proportions. <strong>Solution</strong><br>The only way — Question, question, question. Recursively.</p><h4><strong>Design patchwork</strong></h4><p><strong>Problem</strong><br>This magnification would only result into the patchy solution-centric design work which will reach its brim sooner than later. <br><strong>Solution</strong><br>Designing as early as possible, before development, and testing different architectures could help solve for this.</p><h4><strong>Instant gratification</strong></h4><p><strong>Problem<br></strong>Any of this patchwork, or any feature that is launched for instant gratification is almost always bound to fall in the bucket of debt. <br><strong>Solution</strong><br>If user need is not warranted, don’t force-fit, if user need is warranted, embed it in your product, not in its configuration page.</p><h4><strong>Developer centric design</strong></h4><p><strong>Problem<br></strong>As mentioned, this one is quite common. When the developer resources are considered more precious than the planning aspect, this rabbithole is not far away.<br><strong>Solutions</strong><br>They say, if you think good design is expensive, you should look at the cost of bad design. I’m not sure of any actionable solutions, but invest in people who advocates for the users and look at bettering the processes that lead to the organization’s perspective towards UCD. <br> — One (slim) possibility is to change the business model to reap benefits only if value to the customer/user is exhibited. And not based out of sales metrics. This will be a blow but I imagine, will straighten out the organization like nothing else can.</p><h4><strong>Multiple designers</strong></h4><p><strong>Problem<br></strong>A natural progression, leading to faster turnaround of designer roles. New designers coming from different experiences should bring better ideas and most likely possible resolution for the ongoing problems. However, if the system and process is not capable to accepting this, it will merely amplify the design debt. <br><strong>Solutions</strong><br>Ask new designers to present the processes that they liked from the previous organizations, and ask the old ones to document. And, the done definition. One should not be allowed to mark a user story as done if it is not documented.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oEoKQwaJfiCGXWHPKZesWw.png" /></figure><h4><strong>Lack of documentation</strong></h4><p><strong>Problem<br></strong>Expedited role changes will magnify back lack of documentation like nothing else. The organization would end up designing the same thing dozens of times. <br><strong>Solution</strong><br>The done definition. Design rationales not being documented can be thought of as a ginormous debt which deserves its own article in the near future.</p><h4><strong>Randomized design critique</strong></h4><p><strong>Problem<br></strong>Similar to testing the designs at apparently random development stages, critiquing at random product planning stages will incur design debt.<br><strong>Solution</strong><br>Clearly, design early. At least the standard 30–60–90 critiquing should be followed.</p><h4><strong>Resolving ux changes through ui</strong></h4><p><strong>Problem</strong><br>Finally, the classic last resort, resolving UX changes through UI. Creating hyperlinks, softwares inside softwares using i-frames, promoting every unknown as a ‘configuration feature’ and so on, are classic examples of solving for UX from the UI.<br><strong>Solution</strong><br>Unfortunately, at this juncture, debt is already there. To avoid it from exploding, start doing the above points again.</p><p>Just like any debt, design debt is inevitable. Similar to how a company should set aside money for building a new tech stack every decade or two to revamp their architecture and code framework, the same needs to be allocated for design.</p><p>And while we are at it, keep one day a week as a meeting-free day in the organization. Let people work.</p><blockquote>Thank you for reading and I wish you and your loved ones a good physical and mental well-being.</blockquote><blockquote>If you liked reading this, consider reading <a href="https://adityaaserkar.medium.com/design-debt-a686d6a8a0de">the Part One of this series.</a> And if you have already done that, then <a href="https://adityaaserkar.medium.com/the-user-problem-bb9ea7069aba">check this one below where I (yet again) advocate for the user.</a></blockquote><p><a href="https://adityaaserkar.medium.com/the-user-problem-bb9ea7069aba">The user problem</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8690a4e107f5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Debt]]></title>
            <link>https://adityaaserkar.medium.com/design-debt-a686d6a8a0de?source=rss-d3bbddfe5821------2</link>
            <guid isPermaLink="false">https://medium.com/p/a686d6a8a0de</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[organisational-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Aditya Aserkar]]></dc:creator>
            <pubDate>Sat, 21 Mar 2020 10:52:17 GMT</pubDate>
            <atom:updated>2020-03-21T10:52:17.875Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Part One — </strong>Deconstruction of an interface</h4><p>Its been over 6 months that this write-up is in my drafts and I have been procrastinating on finishing it. And as a matter of fact, that is one of the prime examples of how debt is created. <em>So I finally sit down this weekend, washed my hands for 20 seconds and opened my laptop.</em></p><p>If you are a designer who is trying hard to make structural changes, and the product management says, that is too expensive, or worse, “But, we’ve always had it this way!”, yes you are headed in straight in this trench of design debt.</p><blockquote>‘But, we’ve always had it this way!’ — Almost Every Product Management</blockquote><p>There is something about a tech debt that people are comfortable investing in even though not many people know about scalability and vision in tech decisions. But design debt on the other hand, is completely disregarded mainly because people continue to think of design as a mere coloring department and everyone has an opinion but rarely anyone has a vision and especially one that connects the user to the interface to the tech and org decisions. In fact, because of that perception, I recently even saw myself making different layers within the interface that would suggest how data should flow and which section should influence which.</p><h4>Containerization</h4><p>We could take a small detour to demonstrate that in say, deconstruction of a tablet interface from the gif below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TSGB3YtB6AoYfGWeIb5Bcg.gif" /><figcaption>Interface Hierarchy and containerisation</figcaption></figure><p>Considering a left to right approach, decisions made towards the right, viz. in taskflow or workflow, should not affect the product (offering) or the platform section. This ‘spilling out’ of functions from their respective area of influence creates irrevocable framework complications going forward. We all know how difficult it is to remove something after it has been developed within a product. <strong>Sadly something that has been added to a product without documentation cannot be removed without documentation.</strong></p><p>Ergo, this area of influence needs to be neatly defined and upheld if one wants to push back on design debt as much as possible. Most of this debt comes from one area or one workflow trying to influence the other. It then quickly becomes a matter of ego for one product/workflow to ‘<strong>be seen</strong>’. When the screen real estate is premium every workflow will fight for it inevitable blurring the boundaries and thus responsibilities in the due process.</p><blockquote>Seamless design should only be for the user, and that can happen only if there are definite, responsible and prominent seams within the interface — workflow — product — platform — and organisation.</blockquote><p>Thus, decisions towards the right of this scale in the gif above, (<em>which is the child</em>), should not affect the ones on the left (<em>parent</em>). If and only if all children feel that they have the same feature demand then the parent can have a look at it and decide whether to ‘<strong>promote</strong>’ this feature. Otherwise, each kid only gets to play with their own toys in their own room. No messing up the hall.</p><p>It should be clear from the gif the flow of data, the access control, user privileges and area of influence. The data that is required by the complete platform should only be housed in the leftmost layer here. Children on the right can only be allowed to take instances from it. These things are usually common from a tech architect perspective, but quite often people seem to not relate it to the visuals displayed on the screen.</p><h4>Organised organisation</h4><p>In fact I would go even further to say that an entire organisation needs to be physically mapped according to your interface and this framework needs to manifest itself in the physical world. Imagine fancy interior design where the teams are sitting dependent on the area of influence they have on product and how the seams of these different areas need to be connected. This had become a complete different topic on its own so it got its own little post.</p><p><a href="https://medium.com/@adityaaserkar/open-office-design-61cc7e6221bd">Open office design</a></p><p>If <a href="https://medium.com/@adityaaserkar/open-office-design-61cc7e6221bd">you read that previous article</a>, there I try to illustrate how even the teams need to be developed according to this within each other, and even physically positioned inside of the organisation to facilitate this framework. They simply cannot be set as independent pillars that we see in most organisations. Thus, a simple deconstruction of a screenshot above can help completely reorganize the whole organisation.</p><blockquote>In this part we briefly touched upon from interface upwards. How interfaces can give rise to organisational structural changes. A lot of content has been left to the imagination of the reader because that is precisely the idea of the article. For the next part, I shall try to illustrate design debt in the realms of the infamous ‘<strong>Fail fast, fail often</strong>’. We shall touch upon <strong>Agile or SAFe in the realm of Design</strong> and then the dreaded — <strong>Design Documentation</strong>.</blockquote><blockquote>It isn’t uncommon for designers to literally see through the differences and ego fights that might be happening in a company just by looking at your configuration page. :)</blockquote><blockquote>If you liked reading my article considering reading more and following my work to get updates. <br>Quarantine read recommendation — <a href="https://medium.com/@adityaaserkar/the-user-problem-bb9ea7069aba"><strong>The User Problem</strong></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a686d6a8a0de" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Open office design]]></title>
            <link>https://adityaaserkar.medium.com/open-office-design-61cc7e6221bd?source=rss-d3bbddfe5821------2</link>
            <guid isPermaLink="false">https://medium.com/p/61cc7e6221bd</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[space-design]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Aditya Aserkar]]></dc:creator>
            <pubDate>Wed, 12 Feb 2020 09:31:24 GMT</pubDate>
            <atom:updated>2021-04-24T10:41:00.064Z</atom:updated>
            <content:encoded><![CDATA[<h4>version Umpteenth</h4><p>Yes, this is yet another post that talks about the organisation of an organisation. This is not my forté, so most of the things in this write-up are solely through empirical knowledge, some years of observation, introspection, my love towards spatial design, thousands of hours of cribbing over team silos, and of course the self-aware narcissism of a being a designer. Now that the disclaimer is out of the way, let us see what has been happening in the space design of offices and how it is known to affect work.</p><p>Perhaps we start with a Vox video, awesome as always. But do remember to get back to reading the rest of my article!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F-p6WWRarjNs%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D-p6WWRarjNs&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F-p6WWRarjNs%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/535ea212bdab6a39203639d4e3e7f740/href">https://medium.com/media/535ea212bdab6a39203639d4e3e7f740/href</a></iframe><p>While we all embrace remote working culture, albeit slower than what we wished for, the one thing that co-location has to offer is stronger collaboration. Thus, advocating for open offices cannot divert from one of their core perceived motivation — collaboration. What seems to be that in an effort to bring people closer, the result has backfired and teams remain in silos and individuals are further mentally zoned out, and it is also an introvert’s nightmare.</p><p>With what I have seen is that today’s office design is not dependent on the type of teams that it will house. That, in fact, is the post-modern nightmare. <strong>Why should office design be agnostic of the purpose of why it is built?</strong> Factories are designed in cognizance of whether it will house an assembly line or a electrical wing or a steel pressing process. Fire stations are designed differently than police stations, than hospitals, and so on. Then why does software design get left out? If a company embraces agile, the design of the organisation should reflect that. Merely having morning stand-ups won’t help. What is the first thing that comes into mind when one thinks of something that people do together and share?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/860/1*GcMCWGiA-yD9zIvsIWDa8Q.png" /><figcaption>Pizza all the way!</figcaption></figure><p>The pizza base is the platform that makes it all possible, the company. <strong>Each slice can represent one product</strong> viz. an organisation like Alphabet, can have slices like YouTube, Maps, Google, or calendar etc. Or <strong>each slice can represent one feature or function</strong>, viz. a company like Spotify can have slices like search, recommendations, player, or infrastructure, etc. It is like fractals, you could deconstruct this organisation it to the smallest possible extent. <strong>Each topping represents people</strong>. They are what makes the pizza taste good…err.. the Team complete! Finally, the cheese can represent the salary that binds everyone together! Hahaa, jokes apart, the <strong>cheese demonstrates how everyone is intertwined and dependent on each other to garner integrity to the product </strong>and thus the overall company.</p><p>So what do we get from this? Some amphitheater-ish approach to team formation that leads to space design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/995/1*3XS-iuEkiZaMVGsfTNlVDQ.png" /><figcaption>When all slices come together</figcaption></figure><p>Within each slice, there are people and roles that are indispensable for the product. They could be arranged in a way to proliferate their personal growth by proximity of fellow similar roles, or surrounded by how their aspirational movement could be. Example, a designer could be tightly knit with the product owner, while also being close to other designers from other slices/products/features. This viewpoint, as mentioned above, comes from the narcissistic lens of a designer that design as a discipline should drive the product vision, thereby being more user focused. That proposal is elaborated in a previous Medium writeup here — <a href="https://medium.com/@adityaaserkar/the-user-problem-bb9ea7069aba">The user problem</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9V-FAoWtrEa_GBdUP17d-Q.png" /><figcaption>One slice — one product — one feature, with multiple toppings!</figcaption></figure><p>The designer, and the product owner and architect form the central part of the team that aims to drive the product or feature. The SME, research and the coach concentrically outside, followed by the developer teams. When you extrapolate this slice as a part of the entire pizza as in the first illustration, you can see that the roles lay next to each other. Thus facilitating design systems by inter-product designers, larger company visions by product owners, architectural and tech decisions by architects, shared codebase by collaboration of development teams and so on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/743/1*xdBKuSdklA_bpkzMCAoXyA.png" /><figcaption>Source: <a href="https://www.vecteezy.com/vector-art/181883-amphitheater-ruin-ancient-architecture-history-city-vector-illustration-top-view">Amphitheater </a>by <a href="https://www.vecteezy.com/members/misfitblue">misfitblue</a></figcaption></figure><p>Of course, it goes without saying that the diverse the team, the better the product will be since it brings different perspectives to the product. Diversity in culture, gender, ethnicity, etc. all need to be overlapped within this amphitheater-ish design.</p><p>The periphery would house all scrum meetings, kanban boards and all other jargons that may come in. The center of it thus acts like a podium for official announcements, appreciations and recognition events and so on.</p><p>What do you think? How is your workplace?</p><p><strong>Your company is a theater, hire amazing actors, directors, and facilitate them to work together, and show it to the world!</strong></p><blockquote>If you liked reading this, consider reading more below!</blockquote><ul><li><a href="https://medium.com/@adityaaserkar/the-user-problem-bb9ea7069aba">The user problem</a></li><li><a href="https://medium.com/mytake/universal-design-169d60c4853">Universal Design, what?</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61cc7e6221bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>