<?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 Sunit Singh on Medium]]></title>
        <description><![CDATA[Stories by Sunit Singh on Medium]]></description>
        <link>https://medium.com/@surdattack?source=rss-b59020bc62e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*JQVGjhZQcZhfM-isSxEymA.jpeg</url>
            <title>Stories by Sunit Singh on Medium</title>
            <link>https://medium.com/@surdattack?source=rss-b59020bc62e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 11:17:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@surdattack/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[The Founding Designer]]></title>
            <link>https://medium.com/@surdattack/the-founding-designer-37e772c8f639?source=rss-b59020bc62e------2</link>
            <guid isPermaLink="false">https://medium.com/p/37e772c8f639</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[founders]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Sunit Singh]]></dc:creator>
            <pubDate>Wed, 01 Apr 2026 04:52:11 GMT</pubDate>
            <atom:updated>2026-04-01T04:52:11.088Z</atom:updated>
            <content:encoded><![CDATA[<h4>Hiring your first designer in the age of AI</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-pJwtUXXtJpxE0R2tdZjEw.png" /></figure><p>One question founders keep asking me: who should they hire as their first designer?</p><p>My fundamental answer hasn’t changed much over the years. But the context has. AI has changed how products get imagined and built. That shift is worth addressing, so I thought I’d write this down.</p><p>Design, product, and engineering are getting closer together. AI has sped things up, and now product managers can prototype, engineers can generate decent user interfaces, and designers can work much closer to code. The old model of handing things off is clearly not working anymore.</p><p>However, this does not make the founding designer less important. It makes the right founding designer even more important.</p><p>AI does not reduce the need for a founding designer; it raises the bar. Because when it becomes easier to make things, it becomes even more important to know what to make.</p><h3>What is happening</h3><p>The boundaries between roles are getting blurry. Design is no longer just about screens, product is no longer just about documents, and engineering is no longer just about code.</p><p>Now everybody can do a little bit of everybody else’s work, which is a good thing. It makes teams faster, shortens the time between an idea and a real product.</p><p>But it also creates confusion. Some founders wonder: if everyone can prototype now, do they still need a strong designer?</p><p>The answer is yes. Because making something is easier than knowing what to make, what to remove, what to keep familiar, what to test first, and what needs to feel trustworthy before it reaches a user.</p><p>That is still design, and in a startup, it is not a side skill, it is foundational.</p><h3>So what does that mean for founders?</h3><p>The biggest mistake founders make is not hiring the wrong type of designer, but underinvesting in the role. They will stretch to hire a strong founding engineer because they understand that this person is shaping the core of the company.</p><p>But with design, many founders cut the budget, lower the bar, and hire someone too junior. That is risky.</p><p>A startup is trying to create something new, and if you are not trying to create a new way for the world to do something, then why are you doing a startup at all? And when you are building something new, design is not just arranging screens; it is imagining a new experience, giving it shape, and making it clear enough for people to trust and use.</p><p>That takes some experience. This is not a criticism of young designers; there are many talented ones. But early-stage work is hard, there is no map, the product is still forming, the team is moving fast, and trade-offs appear every day. You need someone who can handle ambiguity without freezing and shape the product while it is still changing.</p><p>So the question is not just “Can this person design?” but “Can this person help invent the product with us?”</p><h3>Now what should you look for?</h3><h4>1. A tinkerer</h4><p>At this stage, you want a tinkerer, someone who naturally pulls things apart, understands how they work, experiments freely, and is not afraid to break and rebuild to make things better.</p><p>In the age of AI, this matters even more. The cost of trying things has dropped, so you can explore more directions, prototype faster, and get something real in front of users much sooner. The advantage is no longer just speed; the advantage is how well someone uses that speed.</p><p>A strong founding designer will use AI to widen exploration, compare paths quickly, and tighten the loop between idea, prototype, and feedback, not to avoid thinking, but to learn faster.</p><p>Traits: Curious. Fast. Hands-on.</p><h4>2. A person with real craft</h4><p>Speed alone is not enough. Your first designer also needs craft, not fancy-for-the-sake-of-fancy, but real craft that makes a product feel robust and trustworthy.</p><p>And AI raises the bar here too. Because when anybody can generate something decent, the value shifts to knowing what is worth keeping, what needs fixing, and what should never ship. AI can give you options, but it cannot give you taste, it cannot tell you where trust breaks, and it cannot decide what feels obvious, calm, or believable for your users.</p><p>That is where craft shows up. And today, craft is no longer just visual; it includes shipping, understanding constraints, working closely with engineers, and being comfortable getting close to code. The best designers now are not just making mockups; they are shaping real product behaviour, often in the medium itself.</p><p>Traits: Sharp eye. Good judgment. High care.</p><h4>3. A generalist with one strong anchor</h4><p>AI has compressed the gap between idea, prototype, and build, so this person needs to work across that whole loop, understand the problem, shape the flow, prototype quickly, and work closely enough with engineering to get it shipped.</p><p>That is what I mean by a generalist. But breadth alone is not enough; you should be deeply convinced about one thing — their product sense, their speed, their craft, or their ability to bring clarity to messy ideas.</p><p>Traits: Broad range. One clear edge.</p><h4>4. The last but not the least</h4><p>In the early stage, you do not have benchmarks. You do not have a reference point. And now, with AI, you will have ideas and prototypes flying around like confetti.</p><p>That is why you need a designer with conviction.</p><p>Not stubborn for the sake of it. But opinionated enough to protect the product from turning into designed-by-committee mush.</p><p>Early on, someone has to hold the line.</p><h3>Concluding…</h3><p>In the age of AI, a great founding designer is curious, serious about their craft, and comfortable moving across design, product, and build. But what really matters is conviction.</p><p>They have a point of view. And they are willing to stand by it.</p><p>If you are compromising<strong>:</strong> Conviction &gt; Speed &gt; Craft.</p><p>Speed + Conviction beats anything else</p><p>Because when ideas and prototypes keep changing, this is the person who stays steady and protects the product from losing its shape.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37e772c8f639" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Design Ruined My Life]]></title>
            <link>https://medium.com/@surdattack/how-design-ruined-my-life-c01ca56914ca?source=rss-b59020bc62e------2</link>
            <guid isPermaLink="false">https://medium.com/p/c01ca56914ca</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[life]]></category>
            <dc:creator><![CDATA[Sunit Singh]]></dc:creator>
            <pubDate>Wed, 18 Mar 2026 03:27:42 GMT</pubDate>
            <atom:updated>2026-03-18T03:27:42.680Z</atom:updated>
            <content:encoded><![CDATA[<h4>The curse of noticing what everyone else ignores.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2G4bb0c27qb0zcfGyngKuw.png" /></figure><p>I have come to the conclusion that design has, in a very practical sense, ruined my life.</p><p>Most people go through their day in a blissful state of semi-awareness. I, on the other hand, pay a constant, invisible tax on my sanity because I notice how poorly the world is put together.</p><p>Take a simple car ride in the city. For anyone else, it’s just a way to get home. For me, it’s a sensory audit. Every time the driver slams the brakes a second too late or accelerates too early, every time the suspension shudders over a poorly levelled speed bump, my brain registers a flaw. I tense up, mentally auditing the seat ergonomics and the rattling plastic trim. I mention it to the person next to me, and they just shrug. “What? It’s absolutely fine,” they say.</p><p>It isn’t fine. It’s friction. And once you’re trained to see it, you can never unsee it.</p><p>There are countless examples where something small spoils the experience for me while leaving everyone else unaffected. I get annoyed, distracted, and physically tense. But others are just fine. It makes you realise that the sensitivity you once trained as a strength has become a condition of daily life.</p><p>I’ve been called out for always complaining, for being too picky, for being a spoil-sport who can’t just let things go and enjoy the moment like everyone else. But that’s not what’s happening. The truth is, I have got a part of my brain that constantly scans for what feels off, what feels unresolved, what could have been thought through better. I didn’t mean for it to become this permanent, but somewhere along the way, what began as training became wiring.</p><p>This is the side of design training they don’t tell you about. They talk about “empathy” and “craft,” but the real result is that your tolerance for friction drops to zero. You stop experiencing life at face value. Instead, you live in the permanent, agonising gap between <em>what is and what it should have been</em>.</p><p>The most exhausting part isn’t even the objects themselves; it’s the “Chalta hai” attitude that comes with it.</p><p>I see people constantly twisting themselves to accommodate bad design. We memorise the nonsensical UI of a banking app. We blame ourselves for being “bad with technology” when the technology is actually just hostile. We call it “getting used to it.”</p><p>I call it a lack of care.</p><p>Designers are disproportionately irritated because we can see exactly where the effort stopped. We see the point where a developer, an architect, or a manufacturer looked at a problem and said, “That’s good enough.”</p><p>It’s an exhausting way to live. Your day becomes a crowded list of small disappointments and missed opportunities for elegance. But I suppose that’s the price. You have to be genuinely bothered by how things are before you feel driven to make them better.</p><p>So no, I probably can’t switch this off. This is part of how I move through life now.</p><p>But the upside is that the good stuff lands just as intensely. A well-designed product, a thoughtful detail, can make me absurdly happy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c01ca56914ca" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design decisions are not about being right]]></title>
            <link>https://medium.com/@surdattack/design-decisions-are-not-about-being-right-fc9e07af2b07?source=rss-b59020bc62e------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc9e07af2b07</guid>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Sunit Singh]]></dc:creator>
            <pubDate>Mon, 15 Dec 2025 14:39:26 GMT</pubDate>
            <atom:updated>2025-12-15T14:39:26.546Z</atom:updated>
            <content:encoded><![CDATA[<h4>It’s about making responsible trade-offs under uncertainty.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PR2H3eR4Lj5ugPYMQiTOmw.png" /></figure><p>We make hundreds of design decisions and almost never reflect on how we make them.</p><p>A designer who enjoyed my last few posts suggested I write about decision-making. I agreed. I thought it would be easy. It wasn’t. I had to keep a log, revisit meeting transcriptions, and find my own patterns.</p><p>This is the first post in a series. It’s not a framework yet. It’s just reflection.</p><p>Decision-making, especially in product design, is not about finding the right answer.</p><p>It is about making a choice in a situation that is constantly changing. It’s always a moving target.</p><p>Information arrives late. The context shifts mid-sprint. Constraints change under your feet. What looked “obvious” on Monday becomes risky by Friday.</p><p>So most design decisions are made under uncertainty.</p><p>Whether we admit it or not, every decision is a bet.</p><h4>Why design discussions go off the rails</h4><p>You have seen the meeting.</p><p>Someone says, “Make it cleaner.”<br>Someone else says, “This will hurt conversion.”<br>Another says, “It feels too premium.”<br>Someone pushes for speed. Someone worries about trust.</p><p>The room gets tense. People defend positions. The debate collapses into pixels, copy, and components.</p><p>But that is usually not the real disagreement.</p><p>What is actually happening is that people are protecting different priorities.</p><p>Trust. Revenue. Speed. Craft. Risk. Performance.</p><p>Nobody names the conflict, so it leaks out as design critique.</p><p>If you do not surface what is truly at stake, teams can argue about UI forever and still not make a decision.</p><h4>We are not choosing between right and wrong</h4><p>Many teams behave as if there is one correct answer hidden somewhere in the design.</p><p>Design is not maths. There is no single right path.</p><p>The hard calls live in the messy middle where multiple options are valid, and every option makes something else worse. That cost is not a mistake. That cost is the choice.</p><p>We are not choosing between right and wrong.</p><p>We are choosing what we are willing to trade.</p><p>And “better” depends entirely on context.</p><p>Design options don’t win on every dimension. Each one has a different profile: one buys speed, another buys reassurance. One protects momentum, another protects understanding.</p><p>Once you see that, arguing about corner radius feels like noise. The real work is choosing which strengths matter most right now, and which costs you’re willing to accept.</p><h4>Context has three realities</h4><p>A simple model I return to is this: every design decision is a bet across three realities.</p><p><strong>User reality</strong><br>Their intent, anxieties, motivations, limitations, and level of savviness. What is this user trying to do right now, and what could stop them.</p><p><strong>Business reality</strong><br>Stage, objectives, growth pressure, revenue model, competition, constraints. What the company needs to prove next.</p><p><strong>System reality</strong><br>Tech, ops, compliance, time, scale. What is actually possible without breaking something else.</p><p>Designers sit at the intersection of these realities. That is where the real trade-offs show up.</p><p>Not on the screen.</p><p>In the tension between what users need, what the business wants, and what the system can support.</p><h4>The move that improves decision-making</h4><p>Many teams get caught up in debates about the interface. The best teams are upfront about it. They write a straightforward statement of the reality of the situation.</p><ul><li>what are we optimising for right now</li><li>what are we willing to sacrifice, on purpose</li><li>what evidence would change our mind</li></ul><p>Because the real questions are rarely “is this good design?”</p><p>They sound more like this:</p><p>Do we want frictionless momentum or deep comprehension?<br>Do we want clarity or nuance?<br>Do we respect user intent or advance the business agenda?<br>Do we earn trust slowly or chase short-term growth?</p><p>None of these have universal answers.</p><p>A decision that is responsible early can be reckless at scale. A shortcut that helps activation can quietly damage trust later.</p><p>This is why context is not a detail. Context is the decision.</p><h4>What a design decision really is</h4><p>As designers, we are always placing bets.</p><p>Speed vs reassurance.<br>Clarity vs completeness.<br>Trust vs conversion.<br>Consistency vs a locally perfect screen.</p><p>But these are rarely binary switches. They are dials. You are choosing degree, not sides.</p><p>And most decisions are not “good vs bad”. They are “good vs better”, where “better” depends on the moment, the user, and the company’s state.</p><p>What separates senior designers is not taste. It is judgement you can explain. The ability to name the trade-off, turn the dial deliberately, accept the downside, and say what would change your mind.</p><p>Great designers do not pretend there is no cost. They choose which cost they are willing to live with.</p><p>That is a design decision. A conscious trade-off, made in context, with accountability.</p><h4>The designer’s actual job</h4><p>A design decision is a trade-off made in context.</p><p>And the context is this: you are designing inside a commercial endeavour. That’s the point.</p><p>So your job is not “user vs business”. It is balancing both, responsibly. Ignore the business and you build ideals that never sustain. Ignore the user and you hit numbers while quietly breaking trust.</p><p>The best outcomes make the business agenda real but invisible. The worst ones shove it in the user’s face.</p><p>Creatively solve for the business while protecting the user’s trust. That’s the job.</p><h4>To summarise</h4><p>You don’t need to be right to do good design. Make a responsible bet by considering the context. Choose trade-offs with careful consideration and balance user needs alongside business goals. That’s what design decision-making is, not a hunt for the one correct answer.</p><h4>What’s next</h4><p>There is a lot more to say about decision-making in design because these tensions show up everywhere: onboarding, copy, flows, growth experiments, trust, and monetisation.</p><p>I’m going to write more in this series, breaking down the recurring trade-offs designers face, and how to make cleaner calls when there isn’t a single “right” answer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc9e07af2b07" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Clarity & Craft — Part 2]]></title>
            <link>https://medium.com/@surdattack/clarity-craft-part-2-5d43c4204971?source=rss-b59020bc62e------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d43c4204971</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[craft]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Sunit Singh]]></dc:creator>
            <pubDate>Tue, 09 Dec 2025 05:46:38 GMT</pubDate>
            <atom:updated>2025-12-10T04:25:47.884Z</atom:updated>
            <content:encoded><![CDATA[<h3>Clarity &amp; Craft — Part 2</h3><h4>Part 2 is on Craft : Controlling the outcome</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q7oLr3XAUdG9nfN-6EaH8A.png" /></figure><p><a href="https://medium.com/@surdattack/clarity-craft-part-1-17235390b0ae">In the earlier piece</a> I spoke about clarity. About building a solid worldview before you touch a screen.</p><p>This one is about what happens after.</p><p>When I say craft, it’s about how we use our taste, judgement to shape the outcome. It’s about mastering our medium, understanding its behaviour, its limits and possibilities.</p><p>It’s not about which tool we use, but how we use it.</p><p>Throughout our careers, craft has involved being hands-on and having direct control.</p><p>You dragged shapes Sketch or Figma.<br>You pushed pixels, aligned grids, adjusted auto layouts.<br>You tuned type, spacing, icon strokes, motion.</p><p>The good thing:<br>WYSIWYG<br>Fine control</p><p>You were coordinating your eye, your hand, and your tool. Output quality depended on how fluent you were with these tools and how strong your taste was. Your taste and judgement still did a lot of the heavy lifting.</p><h3><strong>Cut to vibe-coding et al.</strong></h3><p>AI has quietly changed where craft lives. It has lowered the barrier to create. Now, tasks that used to take years of practice with design software can be done in just a few easy steps.</p><p>We write a few lines and get full screens back.<br>We generate illustrations, icons, and images on demand.<br>Prototypes can be generated in one shot —interactions, motion, the works.</p><p>You go from idea to a working prototype in minutes.</p><p><strong>Life is good, until it’s not.</strong></p><p>You soon realise:</p><ol><li>Everything looks the same.</li><li>Nothing is in your control.</li></ol><p>The truth: it’s a reflection of how vague we are.</p><p>It’s worth remembering that LLMs don’t read your mind — they match patterns. When your prompt is unclear, the model has to guess what you intended.</p><ul><li>“fun” → could be bold, playful, childish, meme‑y, or colourful</li><li>“premium” → could be dark, minimal, glossy, serif or gold</li></ul><p>They can’t see the pictures in your head or the years of taste you’ve built up. All they see is the words you type.</p><p>This is why it feels like you have very little control. Change a word here, add an adjective there, and the layout shifts in a whole new direction. You’re back at the start, trying to get things back on track. The time you saved earlier vanishes with the cleanup.</p><p>So which tool is going to come to our rescue?</p><h3><strong>Enter vocabulary</strong></h3><p>Think of the last time you got feedback on your work.</p><p>Maybe a founder or PM said, “Something is off, but I can’t put my finger on it.” Or a comment like, “Can we make it more premium?”</p><p>You are then stuck interpreting what “off”, “premium” might mean. You make a few assumptions, do another round, and hope you’ve guessed right. That sets you into an endless loop of iterations .</p><p>What is missing there is shared language. A shared vocabulary.</p><p>It is exactly the same with LLMs.</p><p>They do not see the picture in your head. They only see the words you type. When your language is vague, the model is forced to guess what you meant. You end up with generic, unpredictable output for the same reason you end up with vague human feedback.</p><p>That is why vocabulary starts to matter so much.</p><p>Earlier, craft lived in the hands — tool skill, manipulation, finesse.<br>Now a big part of craft sits in the mind — clarity, judgement, vocabulary.</p><p>Language has become the interface.</p><p>And once language is the interface:</p><ul><li>The quality of your words starts to define the quality of your work.</li><li>Vocabulary = Differentiation = Your way out of sameness.</li><li>Vocabulary = Precision = Your way out of unpredictability.</li></ul><p>Now, consider a professional photographer and someone who has only used a phone camera. They both try to generate an image.</p><p>The pro will almost always get better results.</p><p>One simple reason: Better vocabulary.</p><p>They know lighting (soft vs harsh, side-lit vs backlit), lenses, depth of field, composition. If they work with models, they are used to directing posture, expressions, where the eyes go.</p><p>All of that is language.</p><p>So they do not say:</p><blockquote>“Nice portrait with moody vibes.”</blockquote><p>They say:</p><blockquote>“Tight medium shot, soft diffused light from the left, shallow depth of field, subject slightly off-centre, eyes to camera, neutral expression with a hint of a smile.”</blockquote><p>Same tool. Same model. Different words, different output.</p><p>Design works the same way. If language is now the interface, then vocabulary is how you raise the bar of your work.</p><p>So, now what?</p><h3>How to build a design vocabulary</h3><h4>1. Describe great work</h4><p>Don’t just bookmark references. Take 2 minutes to describe why something works:</p><p>Layout: “strong left column, generous margins, clear vertical rhythm”<br>Type: “grotesque sans-serif typeface, comfortable line-height, laddered hierarchy”<br>Visuals: “isometric illustration, rounded shapes, muted palette, clay-like texture”<br>Emotion: “feels calm and trustworthy”</p><p>You are training yourself to see and describe.</p><h4>2. Steal language from good documentation</h4><p>Read up Apple HIG, Material Design, and other design systems as language training, not just rules.</p><p>Notice words like: elevation, hierarchy, density, emphasis, surface, depth, state. Also notice how they describe feel: expressive vs neutral, loud vs quiet, comfortable vs compact.</p><p>Pick the words that fit your taste and start using them.</p><h4>3. Learn just enough of the technical stuff</h4><p>You do not need to be an engineer. You just need the terms.</p><ul><li><strong>UI:</strong> components, HTML tags, key CSS properties (spacing, alignment, shadows, radius, transitions).</li><li><strong>Images:</strong> shot types (close up, medium, wide), depth of field, rule of thirds, basic lighting.</li><li><strong>Motion:</strong> simple film and animation ideas like pacing, easing, delay, stagger.</li></ul><p>This lets you ask for specifics instead of “clean”, “smooth”, or “nice”.</p><h4>4. Keep a cheat sheet</h4><p>As you pick up good phrases:</p><ul><li>Write them down</li><li>Group them: layout, type, colour, imagery, motion, emotion</li><li>Reuse them in prompts, specs, and feedback</li></ul><p>That cheat sheet becomes your portable glossary of terms. Every time you use it, you reduce vagueness and pull the output closer to your taste.</p><p>When you treat vocabulary as part of craft, a few things shift:</p><ul><li>The first draft from your tools lands much closer to your taste.</li><li>You spend less time fixing unexpected output and more time refining your work</li></ul><p>So, this brings us to the end of this series. To wrap this up:</p><ul><li>Clarity is how you understand people and decide what to build and why.</li><li>Craft is how you shape what actually comes out, using language, taste, and judgement.</li></ul><p>Your edge comes from having a solid worldview in your head and using precise words to bring it to life.</p><h4>Further reading:</h4><p>Here’s Part 1, in case you missed it</p><p><a href="https://medium.com/@surdattack/clarity-craft-part-1-17235390b0ae">Clarity &amp; Craft — Part 1</a></p><p>If you want to go deeper into the idea of how a shared design language helps in general, I’d written about it earlier here:</p><p><a href="https://medium.com/@surdattack/the-secret-to-great-design-a-shared-design-language-132804480e41">The Secret to Great Design: A Shared Design Language</a></p><p>If you are curious about the taste, what it really is, how it grows, and how to use it as a designer’s edge. I wrote a separate piece on that recently:</p><p><a href="https://medium.com/@surdattack/taste-the-human-edge-over-the-machine-e134fecabd34">Taste: The Human Edge Over the Machine</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d43c4204971" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Clarity & Craft — Part 1]]></title>
            <link>https://medium.com/@surdattack/clarity-craft-part-1-17235390b0ae?source=rss-b59020bc62e------2</link>
            <guid isPermaLink="false">https://medium.com/p/17235390b0ae</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Sunit Singh]]></dc:creator>
            <pubDate>Mon, 08 Dec 2025 12:18:07 GMT</pubDate>
            <atom:updated>2025-12-09T05:48:00.440Z</atom:updated>
            <content:encoded><![CDATA[<h3>Clarity &amp; Craft — Part 1</h3><h4>Part 1 is on clarity: building a worldview before you touch a screen.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ge7TVIM0qHAjhjZ13sb2qg.png" /><figcaption>Clarity + Craft. A Blockbuster Combo</figcaption></figure><p>One morning on a long climb, gasping up a hill, a line from three–time Tour de France winner Greg LeMond came back to me:</p><blockquote>“It never gets easier, you just get faster.”</blockquote><p>On the bike it means the pain does not go away; you just get to your finish line faster. In my first months working with AI, I saw this applied to my work too. I was moving a lot faster, but it came with its own struggles.</p><p>The work itself has not become easier. In fact, expectations are higher, stakes are bigger, the noise is louder. The biggest shift however, is the speed at which we can move.</p><p>Research that took weeks is now days. <br>Exploration that took days is now hours.<br>Prototyping that took hours is now minutes.</p><p>It feels like magic, no doubt, but speed comes at a cost. It is just as easy to drift as it is to move forward, and you can end up pretty far from where you should be.</p><p>To avoid losing the plot, you need a compass. And for me, that compass has two parts:</p><ul><li><strong>Clarity</strong>: Deciding what to build and why.</li><li><strong>Craft</strong> : Controlling what comes out.</li></ul><p>Combined, they become our internal and eternal compass.</p><p>So, this is a two part series.</p><p>In this post, I focus on <strong>clarity</strong> and why it is non–negotiable, especially in the AI era.</p><p>In the next one, I go into <strong>craft</strong>, and why the combination is deadly.</p><h3>Why our usual “clarity” is not enough</h3><p>When I say clarity, I do not mean more data or a careful read of a well-written PRD. I mean going wide and deep enough on a problem that you can see it from different angles. The picture is so clear it feels like a simple, coherent story in your head. You’ve built a solid mental model of what is really going on, so your decisions are backed by conviction.</p><p>Most teams claim they chase clarity. In reality, they chase inputs.</p><ul><li>Interview notes</li><li>Analytics and Funnels</li><li>Product requirements</li><li>Competitor screenshots</li></ul><p>None of these are wrong. I use all of them. The problem is what they <strong>do not</strong> give you.</p><ul><li>Interviews are full of survivorship bias.</li><li>Analytics tells you what happened, not why.</li><li>Requirements are shaped more by the organisation than by users.</li><li>Benchmarks are the glossy tip of someone else’s iceberg.</li></ul><p>None of these build a strong worldview.</p><p>So product decisions quietly get made from:</p><ul><li>The last strong opinion in a meeting.</li><li>The latest metric that dipped.</li><li>Whatever your favourite competitor shipped last quarter.</li></ul><p>Those ground truths are useful, but they are not enough. You still need a deeper understanding of the people and behaviour behind them before you decide what to build.</p><h3>A cheat code for human behaviour</h3><p>Once you know what real clarity looks like, the obvious question is how to get there without spending months buried in research. This is where AI, used well, becomes my cheat code to human behaviour.</p><p>Let us say we are building an app to help people with intermittent fasting.</p><p>Most people, once they have an LLM, write a prompt like:</p><blockquote>Give me the top intermittent fasting apps, their key features, pros and cons, and best practices for designing a fasting app.</blockquote><p>You get a reasonable response. It is also exactly the same answer any other designer in the world will get.</p><p>I would rather use the model to expand how I see the problem than to design the app for me. For the same fasting problem, I will ask:</p><h4><strong>1. Bring in the experts</strong></h4><p>First, I pull the real thinkers into the room:</p><blockquote>“I’m designing a fasting app. Start by giving me a high-level map of the strongest thinkers in habit formation. Include authors, behavioural scientists, psychologists, and product thinkers who study why habits form, break, or fail… Then point me to the specific books, interviews, and research papers I should study to go deeper.”</blockquote><p>This gives me a landscape of who to learn from and what lenses they use.</p><h4><strong>2. Understand the core psychology of fasting</strong></h4><p>Next, I go deeper into the <em>inner world</em> of the user:</p><blockquote>“Help me understand the intrinsic motivation behind fasting. Go beyond surface-level reasons. Break down the psychological triggers, identity-based motivations, emotional gains, self-regulation patterns, and long-term behavioural rewards.”</blockquote><p>Then I make it specific to different user types:</p><blockquote>“Give me a framework to classify different types of fasters, from beginners to disciplined long-term practitioners. For each group, explain the inner motivations that sustain the habit. Tell me where I can learn more: books, podcasts, research, long-form essays.”</blockquote><p>Now I am not looking at “a user” in abstract. I have clear segments and their inner narratives.</p><h4>3. Understand applicable mechanics</h4><p>Next, I study how great products actually build habits in the wild.</p><blockquote>“Give me a global view of apps that have successfully helped users build habits. Cover health, fitness, meditation, education, finance, and daily routines. For each category, tell me what design principles they used, especially the reinforcement loops, streaks, variable rewards, identity triggers, and social accountability. Pull from interviews of founders, design heads, and product leads where they explain their decisions, the psychology they leaned on, the mistakes they made, and what actually moved the needle.”</blockquote><p>It gives me a toolbox of proven loops I can adapt, instead of guessing.</p><h4><strong>4. Understand and apply behaviour frameworks</strong></h4><p>Next, I zone in and apply a behaviour framework</p><blockquote>“How does the Hooked Model apply to fasting: triggers, actions, rewards, and investment? Then tell me which other frameworks I should use alongside it to get a deeper view of behaviour (JTBD, motivation science, identity theory, cognitive load, habit loops, relapse psychology). For each, explain how it helps me design a clearer, more supportive fasting experience.”</blockquote><p>By this point, I am not collecting more ideas for features. I have a clear mental model of how this habit works and a short list of levers worth building around.</p><p>Why do this?</p><p>Because better inputs change the ceiling of your thinking.<br>Without this, you are drawing a caricature of your user.</p><p>AI makes this practical now. What once took a month can now fit into an afternoon. But it still needs a brain on top.</p><p>The model compresses <strong>research time</strong>, not <strong>thinking time</strong>.</p><p>When I use AI for clarity, I want the problem to click in my head. I decide what questions really matter, I cut everything that does not help answer them, and I rewrite what is left in my own words until it sits in my head as one clear story.</p><p>Why follow this loop at all? Because a few important things change:</p><ol><li><strong>You stop worshipping benchmarks.<br></strong>You can see why something works for them, and decide if it should work for you.</li><li><strong>You stop taking PRDs as gospel.</strong><br>When a requirement doesn’t fit your mental model, you have deeper reasoning to explain why it doesn’t work.</li><li><strong>You add real value in the room.</strong><br>You are not only designing the experience; you are contributing to the larger story the product is telling.</li><li><strong>Your trade-offs get sharper.</strong><br>Saying no becomes easier because you know exactly what you are protecting.</li><li><strong>And most importantly, you learn something that stays with you.</strong><br> You do not just ship a feature; you leave with a deeper understanding of people and behaviour — learning that compounds far beyond a single screen.</li></ol><p>That is the point of this whole first part for me.</p><p>Clarity, to me, is a mental model of the human on the other side. AI, used well, just helps you build that model much faster. Used lazily, it helps you generate generic work faster.</p><p>In the next part, I will talk about craft: how you use language and vocabulary so that, once you have this clarity, you can actually control what comes out of the AI tools.</p><p>Stay tuned.</p><p>Update: Part 2 is out</p><p><a href="https://medium.com/@surdattack/clarity-craft-part-2-5d43c4204971">Clarity &amp; Craft — Part 2</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17235390b0ae" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Taste: The Human Edge Over the Machine]]></title>
            <link>https://medium.com/@surdattack/taste-the-human-edge-over-the-machine-e134fecabd34?source=rss-b59020bc62e------2</link>
            <guid isPermaLink="false">https://medium.com/p/e134fecabd34</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[beauty]]></category>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Sunit Singh]]></dc:creator>
            <pubDate>Tue, 02 Dec 2025 18:06:50 GMT</pubDate>
            <atom:updated>2025-12-03T03:56:28.493Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0gtDKAaWRJmCMtMLHPDxhQ.png" /></figure><p>Lately, it seems that everyone in design and product is obsessed with taste. It’s a topic that constantly comes up in conversations about AI, and rightly so. The tools we have today can almost do everything, except make judgements.</p><p>I’ve also noticed that our discussions about taste can be overwhelming or intimidating, especially for younger designers who are still grappling with the basics. For them, it’s just another skill to add to their list — and a pretty abstract one at that.</p><p>Recently, I was invited to talk about taste on a podcast, which made me take a step back and examine it more closely. I spoke to younger designers, reflected on my own experience, and discovered something interesting: some people have a clear understanding of taste; others see it as simply a matter of aesthetics; and for others, it’s this elusive, almost inherited quality.</p><p>So I thought, why not share my notes on it?</p><h3>Understanding taste</h3><p>For me, taste is nothing more and nothing less than <em>applied judgement</em>.<br>It’s how you see the world. What feels right to you. The micro-choices you keep making every day without even realising.<br>It’s noticing the details others skip.<br>It’s the quiet confidence you have when you’re building something no one has seen before.<br>It’s the connection you instinctively draw between two unrelated ideas.<br>And it’s deeply personal — your upbringing, your memories, your cultural context, your mentors, your aspirations, your biases, your worldview.</p><p>To understand why taste is not fixed, I often think of a hotel. Walk into any well-designed one and you’re walking into someone’s choices — tiles, lighting, furniture, scents. Some people will find it stunning. Others may find it tacky. But none of that changes the fact that someone exercised their judgement. Taste is like beauty. It sits in the beholder but originates from the creator.</p><blockquote>And it is closer to a feeling — perceived notion of a subject by an observer or group of observers.</blockquote><blockquote><strong>~ Ani Dalal, Product Designer</strong></blockquote><p>Or take pixel art.<br>When video games first came out, pixelation wasn’t a style. It was a painful limitation. Memory was scarce. Graphics were clunky. It simply <em>was</em>.<br>Yet today, pixel art is used intentionally, almost romantically — on T-shirts, indie games, crypto apps. Something once born out of constraint is now a design statement, even a tastemaker’s aesthetic. That’s taste evolving with time, not existing in some fixed, eternal state.</p><p>It’s the same with architecture.<br>The Art Deco buildings along Marine Drive in Mumbai are considered iconic treasures today, but back then they were just… common.<br>Our own cities feel chaotic to us, but foreigners find beauty in the disorder because they’re coming in with fresh eyes.</p><p>Taste is relative. Contextual. Shifting.</p><p>It grows with exposure, environment, and time.</p><p>And if we really zoom out, most of us are simply operating inside the aesthetic expectations of our era — the UI patterns, trends, safe palettes, familiar visual styles. We think we’re being original, but we’re mostly repeating fragments of the same pattern language.</p><p>Breaking out of that requires borrowing from outside our field. Looking at nature if you’re an architect. Studying films or games if you’re a designer. Seeking discomfort. And above all, building conviction — enough of it to swim against what’s currently “acceptable.”</p><p>Taste is not fixed. It is trained. And it is always in motion.</p><blockquote>Taste is personal – my taste, your taste – shaped by our own preferences. But it also leans toward the popular. We often anchor our sense of taste to well-known artists, directors, or people we admire.</blockquote><blockquote>It can’t be measured. The difference between two “tasteful” designs is hard to quantify based on taste alone – in the same way that calling something good or bad is hard to define without context.</blockquote><blockquote><strong>~ Ani Dalal, Product Designer</strong></blockquote><h3>Why it matters now</h3><p>If taste is so fluid, why does it matter at all. Especially now?</p><p>AI has changed the nature of creative work in a profound way. It has completely collapsed the barrier to creation. Anyone can produce a reasonable draft. Anyone can generate UI, an illustration, a pitch deck, a short film, a logo. The playing field is flatter than ever.</p><p>But that’s precisely the problem.<br><strong>Everything is starting to look the same.</strong></p><p>AI compresses the world into predictable patterns.<br>Creators follow those patterns because they’re fast and convenient.<br>Outputs converge.<br>The soul goes missing.</p><p>The ceiling, meanwhile, has risen dramatically. You can iterate 100 versions in an afternoon. You can simulate risky ideas with almost no cost. You can explore wildly before committing. But without taste, you’re just generating volume, not value.</p><p>Taste becomes the differentiator because it’s the part of creative judgement AI can’t replicate in context.<br>Your worldview.<br>Your intuition.<br>Your ability to decide what matters and what doesn’t.<br>Your willingness to refine or discard.<br>Your courage to stand behind a creative choice even if it’s not universally appreciated.</p><p>AI can give you ten possibilities.<br>Taste picks one.</p><p>AI can summarise everything.<br>Taste decides the story.</p><p>AI can speed up the craft.<br>Taste strengthens the conviction behind the craft.</p><p>In other words, taste is not about privilege or refinement.<br>It’s simply the lens through which your judgement comes alive.</p><p>And in a world where output is infinite, your judgement becomes your identity.</p><h3>So what’s next?</h3><p>How do you actually grow it? And what changes tomorrow morning?</p><p>The answer is less glamorous than most people expect — it’s discipline, not magic.</p><p>You develop taste the same way you build strength:</p><p><strong>Weights:</strong> what you consume, the ideas and references you expose yourself to.<br> <strong>Reps:</strong> what you make, refine, discard, revisit, and improve.</p><p>Consume better. Curate harder. Study nuance. Build vocabulary. Borrow from unfamiliar disciplines. Surround yourself with people whose standards exceed yours. Use great products. Exercise your taste on side projects. Experiment until something clicks.</p><blockquote>To me, it is:</blockquote><blockquote>•⁠ ⁠developing/having a judgment on what’s good vs great.<br>•⁠ ⁠⁠ability to curate, recognise patterns that moves your heart or feel like great work to you — and apply to the new problems.</blockquote><blockquote>You develop it by exposing yourself to great work, reflecting on what moves you, and finally practicing it.</blockquote><blockquote><strong>~ Nikhil Tirumalasetty. Product Manager</strong></blockquote><p>And finally, bring this into your AI-driven workflow:</p><p><strong>Let AI build. Let taste elevate.</strong><br>Use AI as a starting point, not a finishing line.</p><p><strong>Let AI widen your worldview. Let taste filter it.</strong><br>AI can show you endless possibilities. Your taste will decide which ones to pursue.</p><p><strong>Let AI expand your horizon. Let taste give you coherence.</strong><br>Go beyond design — produce copy, illustrations, motion and fully functional prototypes.<br>Your taste ensures it all feels like one story.</p><p><strong>Let AI explore wildly. Let taste ensure you don’t lose the plot.</strong><br>Remix endlessly. But pick sparingly. Conviction matters more than variety.</p><p><strong>Let AI accelerate your craft. Let taste define your identity.</strong></p><p>Because at the end of the day, AI can generate.<br>Only you can judge.<br>AI can produce.<br>Only you can choose.<br>AI can build.<br>Only you can raise the bar.</p><p>Taste is just the sum of your decisions.<br>And your decisions are shaped by your curiosity, your exposure, your discipline, and your willingness to pay attention.</p><p>That is the real work.<br>That is the real edge.<br>And that is what will separate creative people in the age of AI — not only how fast they build, but the choices they make.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e134fecabd34" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When two worlds collide]]></title>
            <link>https://medium.com/@surdattack/when-two-worlds-collide-fdd036034277?source=rss-b59020bc62e------2</link>
            <guid isPermaLink="false">https://medium.com/p/fdd036034277</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ideation]]></category>
            <category><![CDATA[humour]]></category>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Sunit Singh]]></dc:creator>
            <pubDate>Thu, 27 Nov 2025 06:58:05 GMT</pubDate>
            <atom:updated>2025-11-27T07:05:11.079Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>The hidden link between laughter and insight</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lpnbeoJ_wbXDb7e2AnJUJA.png" /></figure><p>Most people who know me well, know one thing: give me three topics, and I’ll probably have a joke for at least one. It’s a strange skill to claim, but it has been with me for as long as I can remember.</p><p>I grew up in a family where humour was always in the air. At weddings, festivals, Sunday lunches, or random evenings, someone always told a joke. My cousins, uncles, aunts, even the quiet ones. I waited for new jokes like kids wait for dessert. Once I heard a good one, I’d take it to school or college. I’d add my own masala, refine my delivery and share it with friends. Soon it became my party trick.</p><p>Another habit developed: puns. Sometimes I’d play with someone’s name, explore the history of a word, or find a phonetic twist. There’s a thrill in uncovering double meanings hiding in plain sight and turning them into something fun.</p><p>I’m no stand-up comedian. I don’t have the guts to hit the stage. At best, I’m a hobbyist, experimenting in safer settings with friends and family.</p><p>Recently, while preparing for two talks — one on taste, another on creativity . Like the usual geek that I am, I went straight into the physiological side of how ideas form. What’s happening in the brain when something original emerges.</p><p>That curiosity led me to a book I wasn’t expecting to love: <em>The Act of Creation</em> by Arthur Koestler, 1964. Yes 1964.</p><p>And this is where the story takes a turn.</p><p>Koestler makes a bold claim about creativity. He says that all genuine insight whether it’s a joke, a scientific breakthrough, or a moment of artistic clarity, it all comes from the same mental mechanism. He calls it <strong>“bisociation.”</strong></p><p>He writes that creativity occurs when “two habitually incompatible matrices” collide. In simple words, a breakthrough happens when two different ways of seeing the world suddenly intersect in your mind and create a new meaning. He describes this moment as an “unstable equilibrium,” a split-second where the mind is in two worlds at once.</p><p>When I read that, something clicked.</p><p>Koestler doesn’t stop there. He points out that this same mechanism powers three types of creative emotion:</p><ul><li><strong>A-ha</strong> in science sparks discovery.</li><li><strong>Ha-ha</strong> in humour triggers laughter.</li><li><strong>Ah</strong> in art stirs emotion.</li></ul><p>His summary is beautifully sharp:</p><blockquote>“The Ha-ha reaction signals the collision of bisociated contexts; the A-ha reaction signals their fusion; and the Ah reaction their juxtaposition.”</blockquote><p>A joke works because you guide the listener along one line of meaning, then flip them into another. Koestler calls humour “the sudden bisociation of a mental event with two habitually incompatible matrices.” The built-up tension from the first frame cannot follow into the second, so it spills out as laughter.</p><p>That’s exactly why timing matters. Why a punchline needs economy. Why even one extra word can kill a joke. Why you don’t get a second chance.</p><p>But the revelation for me was this:</p><p><strong>Jokes aren’t just a party trick. They are a pure form of creativity.</strong></p><p>A joke forces you to connect distant ideas. To notice relationships others might miss. To build a bridge no one else was expecting. Koestler himself says, “Comic discovery is paradox stated; scientific discovery is paradox resolved.” The structure is the same. Only the outcome differs.</p><p>Once I saw jokes this way, something shifted.</p><p>If humour is built on bisociation, and creativity is also built on bisociation, then being able to make jokes is not unrelated to being creative. It’s training. It’s practice. It keeps the mind flexible. It teaches you to jump between meanings, to embrace mismatches, to play with unexpected overlaps.</p><p>As I read Koestler, it felt strangely like looking into a mirror.</p><p>My lifelong habit of telling jokes wasn’t a side hobby. It was a quiet apprenticeship in creativity.</p><p>It trained me to notice the hidden second frame in any situation.</p><p>It taught me to switch perspectives instantly.</p><p>It kept my mind interested in connections that others might skip over.</p><p>Humour sharpened the same muscles I rely on for design, problem-solving, sense-making, and even taste.</p><p>Discovering Koestler’s work felt clarifying, almost as if the answer to how I think had become a little clearer. It connected a personal thread I’d never examined with a deeper mechanism of how ideas form. It also left me with a practical question: what can we do outside of work to sharpen this creative instinct, not through effort or hacks, but by noticing how our minds collide ideas and make unexpected leaps?</p><p>It also gave me a renewed respect for stand-up comedians and writers. They operate at creativity’s highest setting; instant idea collisions, unforgiving timing, and feedback that is brutally honest. Few crafts demand that level of precision.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fdd036034277" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[True Detective — The UX Edition]]></title>
            <link>https://medium.com/@surdattack/true-detective-the-ux-edition-be410ffdd083?source=rss-b59020bc62e------2</link>
            <guid isPermaLink="false">https://medium.com/p/be410ffdd083</guid>
            <category><![CDATA[crime]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[mystery]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Sunit Singh]]></dc:creator>
            <pubDate>Tue, 05 Aug 2025 11:37:48 GMT</pubDate>
            <atom:updated>2025-08-05T11:37:48.791Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>True Detective — The UX Edition</strong></h3><h4><strong>What Product Builders Can Learn from Detectives</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6SEXtkua9n90-bqyJ-RUcg.png" /></figure><p>On most nights, you’ll find me deeply lost in autopsy reports, CCTV timelines, and interrogations. That is, on screen. From <em>Unforgotten </em>to <em>Mare of Easttown</em>, crime series never tire me out. Crime drama is my comfort food.</p><p>One night, while watching a detective break down a person of interest, I received a Slack message asking for some guidance on a user-research study. I was in the middle of a nail-biting scene, moments before the truth spilled out. I hit pause and rattled off a checklist of what we still needed to investigate (Oh wait, did I just say investigate?)</p><p>As I start jotting my list of requirements, it felt like I was impersonating the lead detective on the case. Then I saw the link. That tiny interruption sent me down a rabbit hole: what if we approached user research the way a detective runs a case?</p><p>It’s a thought that lingered. Because as product builders, we are constantly wondering why users aren’t using a feature or in some cases, what makes a seemingly useless one suddenly click. We pivot away at spreadsheets, analyse funnels to death, chat with a handful of users, and stitch together a story. But the blunt truth is, we know only half the truth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YfpyVCwNIExBisgx.jpg" /></figure><p>While a criminal investigation is higher stakes than churn, what if we treated truth-seeking with same level of seriousness?</p><h3>Beyond the screen: how real agencies crack cases</h3><p>My curiosity about how investigative agencies operate led me to a series of questions:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pvExaKHw0WzRsSTrewAkkA.png" /><figcaption>Prompts for my research</figcaption></figure><p>I started digging. Which agencies have the best track records? What frameworks do they follow when interviewing suspects, witnesses, or victims? Are there handbooks? Step-by-step guides? Turns out, there are — and they’re surprisingly detailed. Built to separate truth from fiction, these playbooks offer more than just procedure; they reflect a mindset. One that values patience, pattern recognition, and disciplined listening.</p><p>The comparison started as a passing thought, but the more I reflected on it, the more it held up. Detectives don’t just rely on instinct — they follow structured protocols, ask precise questions, and gather evidence methodically. There’s a lot in their approach that maps surprisingly well to user research.</p><h3>Investigative playbooks worth stealing</h3><p>Here are a few that stood out. And yes, I do have a personal favourite — you’ll spot it as you read on.</p><h4><strong>PEACE </strong>(Plan, Engage, Account, Closure, Evaluate)</h4><p>The PEACE framework — first set down in the UK’s Home Office Circular and now baked into College of Policing guidance — turns an interview into five plain-spoken steps: <strong>Prepare &amp; Plan, Engage &amp; Explain, Account, Closure, and Evaluation</strong>. It was born in the early ’90s to stop the brow-beating interrogations that had produced false confessions. The method is straightforward: (Plan) do your homework, (Engage) build rapport, open the conversation with clear ground rules, (Account) let the interviewee tell their story in their own words, (Closure) test gaps or contradictions with respectful follow-ups, (Evaluate) then review how you did so you keep getting better. That calm, documented approach has since travelled well — showing up in police training from Australia to Canada.</p><h4><strong>SUE</strong>(Strategic Use of Evidence)</h4><p>The SUE approach, short for Strategic Use of Evidence, grew out of Scandinavian research in the early 2000s and is now standard issue for Swedish detectives. You walk in already knowing your key facts, but you keep them tucked away. Start with open-ended questions so the interviewee lays out their version first. Then you introduce each piece of evidence — phone logs, CCTV timestamps, eyewitness notes — only when it helps probe a gap or contradiction. That slow-drip reveal nudges false stories to collapse on their own, without brow-beating, and leaves a clear audit trail for court. Studies show it sharpens deception detection, which is why everyone from Norwegian police to FBI trainers has added SUE to their playbook.</p><h4>TED (Tell, Explain, Describe)</h4><p><strong>This is my favourite</strong></p><p>Tell, Explain, Describe was lifted straight from British investigative interviewing and is loved for its simplicity. Detectives use it to turn a silent suspect into a storyteller:</p><ul><li>“<strong>Tell</strong> me what happened when you walked in,”</li><li>“<strong>Explain</strong> why you chose that route,”</li><li>“<strong>Describe</strong> the room in detail.”</li></ul><p>The open verbs keep the narrative flowing and surface details that yes-or-no prompts miss. Swap the crime scene for a product and the magic holds. In a usability test you might ask,</p><ul><li>“<strong>Tell me</strong> what you hoped to achieve on our app”</li><li>“<strong>Explain</strong> what slowed you down,”</li><li>“<strong>Describe</strong> what caught your attention”</li></ul><p>Each nudge pushes the participant to expand, reveal context, and hand you language you can reuse in copy. Stick TED on a Post-it next to your webcam; pull it out in every interview and chase each answer as if the product’s life hinges on the truth you uncover.</p><h4>Free Narrative</h4><p>Start with one broad question, then let silence do the heavy-lifting. Detectives call this a “free narrative”: it surfaces timelines, motives, and gaps no rapid-fire quiz can. In user research, try “Tell me about the last time you ordered groceries on our app” and stay quiet. People will reveal what mattered and what hurt, giving raw context without your bias. One open question, a pause, and a notebook often beat a ten-page script. The silence may feel awkward, but resist the urge to fill it.</p><h4><strong>Golden hours: why the clock matters</strong></h4><p>Detectives call the first 48 hours after a crime the <em>golden hours</em> for a reason. Evidence is untouched and memories are clear. Wait, and fingerprints fade, stories firm up. Products have the same window. Collect feedback right after launch, or at most within 48 hours of use, because anything later is already diluted. Users remember exactly where they tripped and how they felt.</p><p>In closing, the parallels between investigative frameworks and our own design and research methods are striking. Framing your next user interview through that lens immediately raises the stakes. By embracing these playbooks, we could potentially uncover the truths about our products and users with the same diligence and curiosity. So, the next time you step into a user interview then chase each answer as if your product’s very life depends on it.</p><p>Just remember, you are not interrogating a suspect, you are partnering with a human who holds a clue to a better product.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be410ffdd083" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Next-Gen UX in AI: Redefining SaaS Products in the Age of AI]]></title>
            <link>https://medium.com/@surdattack/next-gen-ux-in-ai-redefining-saas-products-in-the-age-of-ai-296c0e427b45?source=rss-b59020bc62e------2</link>
            <guid isPermaLink="false">https://medium.com/p/296c0e427b45</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Sunit Singh]]></dc:creator>
            <pubDate>Wed, 26 Mar 2025 22:45:51 GMT</pubDate>
            <atom:updated>2025-03-27T02:22:05.463Z</atom:updated>
            <content:encoded><![CDATA[<h4>My talk at SaaSBoomi — Annual 2025</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VDekQxpohn4poUn4AhT-Cw.jpeg" /></figure><p>I was invited to SaasBoomi in Chennai this Tuesday to talk about the next generation of UX in AI. It was an incredible opportunity to share insights and unveil some of our ongoing work at Krutrim — work that, until that moment, had never been shown publicly.</p><p>I began by reminding the audience, “The SaaS interfaces you’re building today will soon be obsolete.” And I meant it. AI is dramatically reshaping user expectations, and we can’t keep holding on to the old ways of designing.</p><h3>Why Traditional SaaS Design Falls Short</h3><p>Let’s be honest: most SaaS products are basically souped-up spreadsheets. Sure, we add fancy UI components and tabular interfaces, but in the end, it’s CRUD (Create, Read, Update, Delete) under the hood. I joked on stage about how we “do our best to make it sexy,” yet we’re still bound by rigid, templated designs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*PGdwnnAkU2bkj8RpyM88DQ.jpeg" /></figure><ul><li><strong>Overwhelming Choices:</strong> As I said in Chennai, “Users come with one job in mind, yet we bombard them with countless options.”</li><li><strong>Complex Navigation:</strong> I shared my frustration with hierarchical design — digging through layer upon layer just to find one piece of information.</li><li><strong>Manual Data Filtering:</strong> Many SaaS tools dump massive tables of data in front of us, expecting us to figure it all out ourselves.</li><li><strong>Rigid Templates:</strong> It’s not just about convenience for developers. “Most SaaS products are template-driven, constraining true innovation and user-centric design.”</li></ul><p>These challenges led me to emphasise the need for a new approach — one that starts, first and foremost, with the user.</p><h3>Thinking User-Backwards</h3><p>I firmly believe that “thinking backwards from the user never goes out of fashion — AI or no AI.” No matter how advanced technology gets, understanding the user’s life goals, KRAs, and day-to-day challenges remains critical. If we skip this step, we risk building overcomplicated features that people don’t actually need.</p><p>So before we jump to how AI can revolutionise things, we must ask:</p><ul><li>What are users really trying to do?</li><li>What’s their environment or context?</li><li>Which steps can we streamline or eliminate?</li><li>What information do they need at their fingertips?</li></ul><h3>AI: The Great Simplifier</h3><p>On stage, I played a quick audio snippet of our upcoming AI-driven news aggregator, which seamlessly stitches together trending news from multiple sources and then uses text-to-speech. The idea was to prove, in a fun way, that AI “isn’t just a chatbot or a checklist feature” — it’s a force multiplier for user experiences.</p><p>What does it simplify?</p><ul><li><strong>Searching → Asking:</strong> Users can simply converse with AI instead of clicking through endless drop-downs.</li><li><strong>Static Dashboards → Contextual Insights:</strong> Instead of a page full of charts, we can serve up the right insight at the right time.</li><li><strong>Predefined Paths → Adaptive Flows:</strong> We can guide users differently depending on context, time of day, or even the user’s mood.</li><li><strong>Basic Personalisation → Deep Contextual Awareness:</strong> The AI can adapt its responses (and even tone) based on what it learns from the user.</li></ul><h3>Demystifying AI — The Ghost in the Machine</h3><p>I often get questions about these AI “agents,” “copilots,” and “background workers.” Breaking it down:</p><ul><li><strong>AI Assistants:</strong> “Ask and you shall receive.”</li><li><strong>AI Add-ons:</strong> The AI is there, but only steps in when needed.</li><li><strong>AI Copilots:</strong> The AI actively helps you get work done — you can jump in or override it when you want.</li><li><strong>AI Background Agents:</strong> They operate behind the scenes, synthesising data and serving insights.</li><li><strong>AI Workers:</strong> Full-on autonomous digital workers that can replace manual tasks.</li></ul><p>Examples shared</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*gJ2Y95RBLJiJWypCjU4xYQ.jpeg" /><figcaption>AI Assistant</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*w3b7zVTsysVHPbCzhc3tYA.jpeg" /><figcaption>AI Add-on</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*uB-HpPbmx2uUMFxbcYhRkA.jpeg" /><figcaption>AI Copilot</figcaption></figure><h3>Evolving Interaction Models: Conversational &amp; Adaptive UI</h3><p>One of my favourite demos involved a conversational interface that not only responded in real time but also showed its “thinking” or reasoning steps. I used to say, “I often find myself speaking to an AI as though it’s human — and getting upset when it doesn’t behave!” That’s actually a good sign: it means we’re crossing the threshold into more natural, human-like interactions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*2fjxALv85S-6U40SQURnbg.jpeg" /></figure><p>We also showcased voice-based tasks: brainstorming, dictation, and command-and-control. Yet I reminded everyone, “Voice interactions are intuitive but must balance immediacy, accuracy, and environmental constraints,” especially if your user is on the move or in a noisy office.</p><h3>Adaptive UI (GenUI)</h3><p>Personalisation has long been a buzzword, but too often we’ve lacked the tools to really deliver it. Now, we can feed location, time-of-day, and user history into AI systems that can dynamically shape the UI.</p><p>For instance, we took a static event-scheduling app (Sched) and let AI adapt it on the fly — knowing it was midday, the user was in Chennai, and that they might be interested in SaaSBhoomi. Instead of just showing a long schedule from 9:45 AM onward, the app automatically pinned the user’s current session to the top. “This is the time right now — here’s what’s happening,” it would say, saving them from unnecessary scrolling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*mmyktgZF9uR-bZ1bQQsLrw.jpeg" /><figcaption>Sched App</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*2S1jB_OkauChcV1PUx99fA.jpeg" /><figcaption>Adaptive UI — Generated by AI</figcaption></figure><h3>Designing for Human-AI Collaboration</h3><p>“Balancing prompt-based interactions with direct manipulation is critical.” Many of us learned to trust direct control (clicking, dragging, selecting). But in an AI-driven world, we also rely on the AI to do part of the heavy lifting — and we still want the freedom to jump in and manually fine-tune something.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*kcRUG2FfI2JaQsIfUzKjnw.jpeg" /></figure><p>On stage, I demonstrated an interface with a chat-like prompt on one side and a direct manipulation canvas on the other. Sometimes you just want to click and edit something yourself; other times it’s easier to ask the AI to do it. Both approaches can (and should) live side by side.</p><p>Examples shared:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*Sx5e7by3XHxOCM0ZMlzbqA.jpeg" /><figcaption>V0 — Where User &amp; AI collaborate to build UIs with Prompts</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*e5m9WaEBjo9-tWWUbsW_Qg.jpeg" /><figcaption>V0 — Where User has the opportunity to co-manipulate</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*J2x29y49XZWCeXRpcRNTvg.jpeg" /><figcaption>V0 — Where User is in full control for manipulation</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*lkqXPKSDIRl8g2Co4rfOhQ.jpeg" /><figcaption>ChatGPT’s Inline edit widget in the Canvas.</figcaption></figure><h3>Final Thoughts</h3><p>As I wrapped up my talk, I mentioned a small but telling story from my hotel in Chennai. I couldn’t figure out how to switch on the lights — because everything was controlled by an iPad’s digital interface. It was flashy, sure, but also confusing. “Technology without user-centric design can create more confusion than convenience.” That line drew a lot of nods from the crowd.</p><p>Ultimately, AI won’t solve every design shortcoming on its own. We must keep the user’s context, challenges, and goals at the forefront of everything we create. That’s how we future-proof our products against obsolescence. Stay curious, stay adaptive, and never forget that, at its core, UX is about helping people accomplish their goals with ease and delight.</p><h3>Resources shared:</h3><ul><li><a href="https://medium.com/@surdattack/breaking-into-ai-ux-essential-reading-list-and-reflections-for-designers-8866411490cc">Breaking into AI/UX: Essential Reading List and Reflections for Designers</a></li><li><a href="https://emilycampbell.co/my-emerging-heuristics-for-assessing-ai-design/">My emerging heuristics for assessing AI Design - Emily Campbell</a></li><li><a href="https://www.shapeof.ai/">The Shape of AI | UX Patterns for Artificial Intelligence Design</a></li></ul><p>A big thanks to <a href="https://www.linkedin.com/in/rakeshmondal/">Rakesh Mondal</a> for helping me with the presentation, <a href="https://www.linkedin.com/in/varunshoor/">Varun Shoor</a> for inviting me and <a href="https://www.linkedin.com/in/anjeli/">Anjeli Singh</a>, my co-speaker.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=296c0e427b45" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How AI is influencing today’s design workflows?]]></title>
            <link>https://medium.com/@surdattack/how-ai-is-influencing-todays-design-workflows-in-conversation-with-a-young-designer-ac6810b9cfd5?source=rss-b59020bc62e------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac6810b9cfd5</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[process]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Sunit Singh]]></dc:creator>
            <pubDate>Thu, 20 Feb 2025 11:08:02 GMT</pubDate>
            <atom:updated>2025-02-20T11:08:34.291Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>In conversation with a young designer</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*89BojiEB-U9YTL8Ys1lLoA.png" /></figure><blockquote>This article is based on a real conversation between myself and <a href="https://x.com/pbshgthm"><strong>Poobesh</strong></a><strong>, </strong>a young, enthusiastic designer eager to discover how artificial intelligence can (or should) reshape design workflows. Although a student of design, Poobesh is pushing boundaries by venturing into mechanical engineering to experimenting with hardware.</blockquote><p>Over the past few years, design tooling has undergone dramatic changes — yet many practitioners have made little shift in their everyday workflows. This question that Poobesh was investigating whether modern AI tools are genuinely reshaping how designers work — or if teams still rely on long-standing processes.</p><p>Having experimented extensively myself, I was eager to discuss the evolving role of AI in design.</p><h3>The questions</h3><p>Poobesh, has been on a mission to find out whether modern AI tools truly reshape how designers work or if teams still rely on the same tried-and-tested methods. Poobesh had noticed that most designers still relied almost exclusively on Figma — despite the wave of AI tools claiming to revolutionize the field. Intrigued, he began interviewing seasoned designers, including me. Poobesh reached out to me with three key questions:</p><ol><li><strong>How is AI influencing today’s design workflows?</strong></li><li><strong>Why are many teams hesitant to adopt new tools?</strong></li><li><strong>Where can AI and data-driven insights deliver the greatest value?</strong></li></ol><p>I was thrilled to dive into this conversation — particularly because I’m often asked about my own workflows and recently shared my personal playbook on Twitter:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zp9Hzt7rsXcECzKJpsGF7A.png" /><figcaption><a href="https://x.com/surdattack/status/1891287341639094637">https://x.com/surdattack/status/1891287341639094637</a></figcaption></figure><p>This discussion felt like the perfect follow-up to that tweet, offering a closer look at how I structure my process. Below is a synthesis of our exchange, featuring core insights and practical takeaways for anyone curious about integrating AI into their design approach.</p><h3>The Figma-first reality</h3><p>From his initial interviews, Poobesh found that around <strong>95% of designers</strong> continue to live and breathe in Figma, with only minor forays into AI for asset creation.</p><p><strong>Poobesh</strong>:</p><blockquote>“Ninety-five percent of the folks I’ve talked to haven’t really changed anything in their workflow. They live and exit in Figma.”</blockquote><p>He also realized that most AI-driven design tools on the market promise to <em>eliminate</em> the need for a designer, rather than <em>empower</em> existing designers with improved productivity. This misalignment raised key questions about the direction of AI in the design space.</p><h3>3. Where overpromising AI tools fall short</h3><p>Throughout our conversation, I stressed that many AI tools oversell their capabilities by advertising a simple, high-level prompt — like “<em>design a food delivery app</em>” — and expecting a polished final product.</p><p><strong>Me</strong> :</p><blockquote><em>“If you give that intern a very high-level brief, saying, ‘Hey, design an app for food delivery,’ that person is going to think on its own and design a food delivery app. That can be great in itself, but it won’t be in line with what you want or what the business wants.”</em></blockquote><p>The same principle applies to AI: if you feed it shallow inputs, you’ll get superficial outputs. Real design requires understanding business context, user motivations, and technical constraints — areas where a simple prompt just isn’t enough.</p><h3>Redefining the designer’s role</h3><p>One major reason these AI tools <em>appear</em> to replace designers is because <strong>design</strong> is often seen in a narrow sense — primarily UI screens and mockups. In reality, design encompasses:</p><ul><li><strong>Business Strategy:</strong> Mapping user needs to company objectives.</li><li><strong>Data &amp; Research:</strong> Analyzing social media, app store reviews, support tickets.</li><li><strong>Technical Understanding:</strong> Knowing how APIs, frontend frameworks, and databases work.</li><li><strong>Behavioral Psychology:</strong> Applying principles of persuasion and motivation to craft experiences.</li></ul><p><strong>Me</strong>:</p><blockquote><em>“If you’re doing digital design, you need to know how code works in the background, what happens under the hood, and so on. You can’t be an automobile designer without knowing the mechanics of how automobiles work.”</em></blockquote><h3>AI as an intelligent, direction-hungry intern</h3><p>I explained to Poobesh that I view AI as a <em>highly capable but direction-hungry intern</em>. With the right prompts and iterative guidance, AI can handle repetitive tasks, data parsing, and quick prototyping.</p><p><strong>Me</strong> :</p><blockquote>“I find it to be like a design intern who’s really smart, who can do anything, but if you don’t channel that energy properly, you won’t get the results you want.</blockquote><p>This doesn’t trivialize the designer’s role; instead, it highlights the need for <strong>strategic oversight</strong>. Designers must break down tasks, provide context, and iterate continually — just as they would with a junior teammate.</p><h3>The Three Pillars: Clarity, Conviction, and Craft</h3><p>I walked Poobesh through the framework I use to structure my AI-enhanced workflow:</p><h4><strong>Clarity</strong></h4><ul><li><strong>Gather Data</strong>: “<em>I scrape social media, app store reviews, support tickets — everything.</em>” to get a 360 degree view.</li><li><strong>Summarise with AI</strong>: Using ChatGPT or NotebookLM I parse large data sets quickly, spotting recurring user pain points or sentiment trends.</li></ul><h4><strong>Conviction</strong></h4><ul><li><strong>Deep Research</strong>: “<em>Sometimes I speed-read relevant books on gamification or psychology using AI prompts, summarizing entire chapters in minutes. And start applying those principles to the problem at hand.</em></li><li><strong>Strategic Alignment</strong>: Combine these learnings with the business’s core objectives so you know <em>why</em> you’re designing each feature.</li></ul><h4><strong>Craft</strong></h4><ul><li><strong>Iterative Prototyping</strong>: “<em>I rely on platforms like V0 or code assistants to generate interactive prototypes. Then, I refine the visuals or flows in small steps.</em>”</li><li><strong>Figma for Finishing Touches</strong>: “<em>When I need pixel-perfect elements, I jump briefly into Figma, then integrate those assets back into the AI-driven prototype.</em>”</li></ul><h3>7. Real-world example: Why step-by-step matters</h3><p>During our talk, we joked about the anti-pattern of giving AI a vague prompt (e.g., “Design a social networking app”) and leaving it at that. AI is powerful, but it still requires an iterative, step-by-step approach:</p><p><strong>Me</strong>:</p><blockquote>“The difference between success and failure in AI-driven design is how you break down tasks. If you dump a lot of information at once, you’ll confuse the AI — and get nonsense. But if you work like it’s an actual person, step by step, you can guide it toward the right output.”</blockquote><h3>Why the current generation of AI tools miss the mark</h3><p>Despite their marketing, many AI design tools are geared toward skipping an entire design function:</p><p><strong>Poobesh</strong>:</p><blockquote>“It almost seems like they’re promising that you can skip having a designer at all. But real design work requires so much context — from user research to brand identity — that a single prompt can’t capture.”</blockquote><p>Most importantly, these “instant app” tools ignore the deeper layers of business alignment and technical feasibility, which are crucial to any product’s success. They might generate generic UI screens, but they rarely account for the entire product ecosystem.</p><h3>Embracing experimentation</h3><p>We concluded that <strong>designers shouldn’t fear AI</strong> — they should <em>experiment</em> and adapt. Even in its current form, AI drastically cuts down on busywork, giving designers more time for high-level thinking.</p><p><strong>Me</strong> (Design Advisor):</p><blockquote>“Everything is an experiment now. You do it, you learn, and you move on. The beauty is, it frees you from a lot of overwhelming thoughts about tomorrow. Just focus on building something amazing today — AI can help with that.”</blockquote><h3>A public interest message to the design community</h3><p><strong>To fellow designers</strong>: If you’re still locked in a single tool like Figma for everything, consider broadening your approach. AI can:</p><ul><li><strong>Handle large-scale data</strong> so you can diagnose user needs faster.</li><li><strong>Speed up prototyping</strong> so you can test multiple directions in days instead of weeks.</li><li><strong>Inspire new ideas</strong> by providing an “outside perspective” on potential solutions.</li></ul><p>Yet, AI won’t replace the strategic and empathetic core of what you do. That’s where your expertise and human insight will always remain indispensable.</p><h3>Final Takeaways</h3><ol><li><strong>Redefine your role:</strong> Embrace the full breadth of design — business, data, technology, and psychology.</li><li><strong>Adopt AI thoughtfully:</strong> View it as an intern who needs guidance, not a black-box solution that magically generates perfect designs.</li><li><strong>Iterate and experiment:</strong> The best results come from step-by-step collaboration with AI, paired with your domain expertise.</li><li><strong>Stay curious and adaptive:</strong> Tools evolve quickly; investing time in experimentation now can future-proof your skill set.</li></ol><p><strong>In Summary:</strong> This conversation between me and a driven, young IIT grad named <strong>Poobesh</strong> highlights how designers can evolve their craft by using AI as a force multiplier. Rather than clinging to one-tool-fits-all or fearing “designer replacement,” the key is to <strong>expand your creative bandwidth </strong>while letting AI handle tedious or large-scale tasks.</p><blockquote>“If you focus on what AI does best — rapid iteration, pattern recognition, large-scale data analysis — you’ll free yourself to focus on the high-level strategy and empathy-driven aspects of design.”</blockquote><p>Our hope is that more designers will take the plunge, explore new workflows, and ultimately shape AI to serve their vision — rather than letting AI dictate the boundaries of design.</p><p><em>Thanks </em><a href="https://x.com/pbshgthm"><em>Poobesh</em></a><em>, for the lovely questions. It was a great start of the day.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac6810b9cfd5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>