<?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 Uday Gajendar on Medium]]></title>
        <description><![CDATA[Stories by Uday Gajendar on Medium]]></description>
        <link>https://medium.com/@udanium?source=rss-f2a23e77b0a1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*on7VXoh-rgUbI2UC.jpeg</url>
            <title>Stories by Uday Gajendar on Medium</title>
            <link>https://medium.com/@udanium?source=rss-f2a23e77b0a1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 16:12:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@udanium/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[An AI Strategy is a Design Strategy]]></title>
            <link>https://udanium.medium.com/an-ai-strategy-is-a-design-strategy-20a788c673d3?source=rss-f2a23e77b0a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/20a788c673d3</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Uday Gajendar]]></dc:creator>
            <pubDate>Tue, 21 Apr 2026 18:44:42 GMT</pubDate>
            <atom:updated>2026-04-21T18:44:42.727Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UPL0m2jWQ_WkEss2CVik-Q.png" /></figure><p><em>// Note: This essay is drafted from a guest lecture I gave in February 2026 to a UC Berkeley master’s class on designing with generative AI. I’d love to hear which resonates most — or which you think is missing! //</em></p><p>Every week we surely hear some variant of this from a stressed, exhausted business leader or executive: “We need an AI strategy!” 🫠 Sigh.</p><p>Yet each time, what I sense is deeply emotional, and human — that fear of “falling behind”. FOMO. The quiet dread of looking lost in a board meeting while a competitor seems to have it figured out (hint: they haven’t either). The overwhelming flood of new tools, new models, new announcements — every single day. From Cursor Code to Clawbot to Moltbook to…who the hell knows is next. Wild West indeed!</p><p>But I sense this is not a strategy problem. That’s an <em>anxiety</em> problem. And you can’t solve an anxiety problem with a hasty roadmap of mandated “AI features”. 🤨</p><p>Here’s what I’ve come to believe after 20+ years designing enterprise products through the mobile revolution and cloud/SaaS shift, and more recently per developing a GenAI framework, I shared with grad students at UC Berkeley:</p><blockquote>The companies that will absorb generative AI well aren’t the ones with the most “aggressive” AI strategy. They’re the ones that treat AI adoption (and integration into human rhythms) as a design question, anchored by validated human needs &amp; goals.</blockquote><p>What’s the difference? Let me show you through five themes around designing for AI that I’ve been developing.</p><p>But first let’s acknowledge there’s a critical conversation happening, that has persisted for years across devices, apps, services, and now with GenAI or LLMs. It’s an argument captured by the following cartoon, where the user and the “system” (OS, service, tool, device, etc.) struggle to understand each other’s intent.</p><figure><img alt="Cartoon illustration of user and computer frustrated with each other: “Can’t you do anything right?”" src="https://cdn-images-1.medium.com/max/1024/0*l6360RYM9hgDuNIY" /></figure><p>This is the real “alignment problem” — connecting the user’s mental model (assumptions &amp; expectations) with the data model (system logics &amp; capabilities) via an experience model, manifested as interfaces, interactions, content/copy, and yes good ol’ information architecture. 🤓Your strategy is literally nothing without this experience model to tie the technology with the human goals and intents. Else there’s a total breakdown with frustration and loss of engagement, and failed adoption.</p><p>This alignment gap — between what humans expect and what systems actually do — is exactly what an “AI strategy” really needs to solve for. The way I see it, that breaks down into five specific design challenges or themes below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bW_pSY3J1ULRabQ-" /></figure><p><strong>❖ The “new UX contract”.</strong> Generative AI breaks the deterministic “if X, then Y” logic that every product, process, and workflow has been built on thus far pre-AI. If I click a button there’s a deterministic pre-defined action as a result. This isn’t a technical problem — it’s a relationship problem. Your employees and customers had an implicit contract with software: predictable inputs (form fields, buttons, tabs), with predictable outputs and feedback communicated. That contract is being rewritten with probabilistic results per evolving models. Design strategy asks: <em>how do we renegotiate it honestly? What does that effective experience look like?</em> 🤔</p><p><strong>❖ Constraint as creative material.</strong> Latency, model variability, token/context limits — business leaders may see these as bugs to be engineered away. Designers take a different approach, where constraints shape the craft, and emergent possibilities. The question isn’t “how do we eliminate AI’s limits?” but “how do we evolve possibilities with them to create an effective experience?” That reframe could change the entire product &amp; workflow strategy. 🙃 Indeed there’s a whole new vocabulary that implies an emergent craft of AI. Consider the following, as more than simply technical parameters but materials that shape the experience of interacting with AI:</p><ul><li><strong>Latency as anticipation: </strong>Waiting isn’t just “dead time” but a space for reflection, preparation, and building intent</li><li><strong>Non-determinism as serendipity:</strong> Variability isn’t a bug, it’s the source of discovery, surprise, and creative possibility. Lean into it.</li><li><strong>Token limits force clarity:</strong> This is a potentially impactful one when you consider “token economics” and pricing burdens. Thus such token limits demand precision, focus, and meaningful expression of intent in the prompt definition.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/992/0*Wz7OVzwAJt4TfCDx" /></figure><p><strong>❖</strong> <strong>Trust as architecture. </strong>The instinct when deploying AI is to simulate total certain confidence — to present outputs as authoritative, clean, certain. But trust isn’t built by hiding uncertainty; it’s built by revealing it honestly, progressively over time, in ways people can act on, so they’re respectfully acknowledged. This is phased experience design with a kind of temporal scaffolding, from <strong>first use</strong> towards <strong>early adoption </strong>as mental models form with feedback deciphered, then <strong>sustained usage</strong> whereby users learn to understand <em>how</em> the system arrived at its outputs, not just what it produced. It’s also what separates companies that deploy AI thoughtfully from those that create liability &amp; backlash! 😬</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*awyuQYXcF0P-_c4r" /></figure><p><strong>❖</strong> <strong>Progressive autonomy. </strong>AI (and agentic) autonomy should be earned, not assumed. The best AI integrations expand what the system can do as it proves itself — while preserving human agency at the moments that matter most. This is a design philosophy, not a procurement decision of the latest “game changing” AI tool or agent infrastructure.</p><p>Think of building that progressive autonomy as a three-layer funnel where users gradually ceded control as they build confidence. Enable reversability of choices. Keep humans in ultimate authority.</p><ul><li><strong>Supervised mode: </strong>Every action requires approval, so the system learns user prefs and boundaries.</li><li><strong>Guided autonomy:</strong> The system handles routine tasks independently, and flags edge cases for human review.</li><li><strong>Trusted partner:</strong> The end state where the system operates autonomously with defined parameters, reporting its activity transparently.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Gvk3fKH3EtDkb3Mg" /></figure><p><strong>❖</strong> <strong>Calibrated design judgment.</strong> Every AI system requires someone to decide: what level of autonomous action is acceptable here? What’s the consequence if it’s wrong? These aren’t engineering decisions. They’re ethical design choices about how much freedom to extend to a system based on demonstrated reliability. “Move fast” without this calibration is just “move recklessly.” 😬</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wVMBZkzSzIDGLgQ-" /></figure><p>Thus what emerges is a “craft of AI” based upon four intertwined practices:</p><ul><li><strong>Reading systems:</strong> Designers need to understand how models reason and where they fail to inform an improved relationship with users, per their goals/needs.</li><li><strong>Shaping constraints: </strong>As mentioned before, knowing how to leverage the parameters and constraints like response latency or token limits as design materials or tools.</li><li><strong>Preserving agency: </strong>Having a mindset of augment or amplify human capability first, not immediate replacement.</li><li><strong>Building trust: </strong>Surfacing uncertainty clearly without overwhelming users.</li></ul><p>Notice what’s absent from these five themes? A technology budget. A vendor selection matrix. A “digital transformation” initiative.</p><p>What is actually present? <em>Judgment. Relationship. Trust. Ethics. A humanistic philosophy.</em> All that fuzzy, complicated stuff. But it’s important and constructive towards shaping a practical strategy that does more than simply spark up stock prices or inflate leadership egos. 😇</p><p>These are the foundational, original concerns of <strong>DESIGN</strong> (writ-large) — now urgently relevant to how every organization navigates perhaps the most consequential shift in how work gets done in our lifetimes. So if your executive leadership team is asking “What’s our AI strategy?” then I’d gently redirect with the following questions:</p><ul><li><em>What’s our charter (principles + values) for how humans &amp; AI systems should work together?</em></li><li><em>What do we owe our customers + investors in terms of transparency and agency? What’s the governance model around that, and how is it sustained?</em></li><li><em>What level of AI autonomy matches our collective risk tolerance and lived values? How does that translate to customer values and needs?</em></li></ul><blockquote>Answer those, and the strategy reveals itself.</blockquote><p>But that’s not an AI strategy per se. That’s a design-informed strategy of how to enable people to fulfill their goals effectively, smoothly, respectfully. And it’s the only kind that ever matters. 🙏🏽</p><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/ai-strategy-design-uday-gajendar-pt5qc/"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=20a788c673d3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Victims of Velocity (updated for AI)]]></title>
            <link>https://udanium.medium.com/victims-of-velocity-updated-for-ai-acafa335a555?source=rss-f2a23e77b0a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/acafa335a555</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Uday Gajendar]]></dc:creator>
            <pubDate>Sun, 12 Apr 2026 21:15:21 GMT</pubDate>
            <atom:updated>2026-04-12T21:15:21.900Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BEJjEe9-quFNRHLOSTEhow.png" /><figcaption>Traffic lights speeding into the darkness — via Unsplash</figcaption></figure><p>AI-driven speed incurs a cost, but are you ready for it?</p><p>Build more features faster… faster… <strong>FASTER</strong>! 🙄 This vibe has become the norm in software development, as multiple pressures dominate — due to competitors, investors, customers, and now AI. However, this urgency to deliver more at a higher rate adversely impacts many elements, which I call the <strong>“victims of velocity”</strong>.</p><p>This certainly rings true for designers striving to deliver good design to customers amid rushed, hectic cycles. And with the explosive rise of AI-powered development tools — Cursor, v0, Lovable, Bolt, and their proliferating kin — the trap has grown more seductive… and more dangerous. These tools make shipping <em>feel</em> effortless. A working prototype in minutes. A full-stack skeleton before lunch. But velocity without wisdom isn’t speed — it’s just a faster way to create problems you’ll pay for later. Perhaps velocity is important, but at what cost? 🤨 And how might we pursue velocity with our eyes wide open? 👀</p><h3>Impacted: Quality of product</h3><p><strong>• Craftsmanship: </strong>This involves pixel accuracy, with clear consistency of foundational elements like colors, grids, fonts, icons, terminology, etc. Craft matters in reinforcing the perceived value that a multi-million dollar product is worthy of the price paid, not something that looks hacked or feels thrown together haphazardly, eroding trust and goodwill.</p><blockquote><em>Craft cannot be rushed; the result is nuisance “papercuts” strewn across the interface degrading the overall experience. 🫠</em></blockquote><p><strong>• Strategic forethought: </strong>With cross-functional dependencies, object/data relationships across screens and workflows, rushing often leads to broken navigation, annoying error states, confusing patterns or certain use cases are just forgotten. It takes careful deliberate time to think through the paths, journeys, taskflows …and yes, the edge cases!</p><blockquote><em>This must not be rushed just to meet an imposed deadline borne out of panic or fear — or some self-created impatience with “thinking things through”. 🙄</em></blockquote><p><strong>• Validating real user value: </strong>So, did anyone actually <em>verify</em> if this feature is one that customers will value in their daily workflow? Or are we building to ship just to make some stakeholders feel happy or finish an OKR-driven task list? Or are we building said feature to help customers achieve their goals, which they truly appreciate?</p><blockquote><em>It’s absolutely crucial to take time to confirm and clarify real customer value </em><strong><em>first</em></strong><em> before sprinting off to build. ✅</em></blockquote><p><strong>• Learning goals for the MVP: </strong>AI tools make it trivially easy to ship <em>something</em> fast. But an MVP exists to <em>learn</em>, not merely to launch. When the goal becomes hitting a deadline rather than answering a specific hypothesis — Does this resonate? Will users actually change their behavior? What breaks under real conditions? — you’ve sacrificed the entire strategic value of the exercise. <em>A feature generated in 20 minutes by Cursor is not an MVP.</em> It’s a guess in a trench coat.</p><blockquote><em>The discipline of defining what you’re trying to learn </em>before<em> you build is precisely what velocity culture erodes, and what AI-assisted speed makes even easier to skip.</em></blockquote><p><strong>• Design quality debt: </strong>Velocity culture treats debt as a “later” problem. AI-accelerated velocity makes debt invisible until it isn’t. Generated components diverge from the design system. Quickly scaffolded flows accumulate interaction inconsistencies. Patterns multiply without rationale. Before long, the product is a patchwork — functional in some places, confusing in others, impossible to maintain coherently. Ugh. Reducing debt requires the <em>discipline</em> to pause, audit, reconcile, and refactor.</p><blockquote><em>That’s anathema to a culture that worships the next release over the integrity of what’s already shipped. 😬</em></blockquote><h3>Impacted: Rituals of design</h3><p><strong>• Daydreaming: </strong>Often you need that empty whitespace of free time &amp; no activity to let the brain do its thing, marinating on concepts, just wandering the forest of reverberating notions to see what emerges. It’s not really something that can be coerced, rushed, or done “on demand”.</p><p><strong>• Serendipity: </strong>The wonderful happy accidents of colliding ideas, synchronous conversations with peers struggling with the same problem, experimental models &amp; sketches, it’s all valuable! Again, it’s not something to be forced or rushed. But contexts should be shaped to enable this to happen organically, and regularly. 🙌🏽</p><p><strong>• Empathy: </strong>This is cultivated over time through direct &amp; indirect contacts with customers, at multiple iterative levels of immersive understanding. Threads of observations and insights emerge through anecdotes, conversations, and so forth, often collectively as multiple stakeholders build a composite of who the user is — and aspires to become. Note: This can’t easily be replaced with AI-generated synthetic users!</p><p><strong><em>Truly understanding someone’s pain (and hope) builds product intuition.</em></strong></p><p><strong>• Ecosystem thinking: </strong>Your product doesn’t work in isolation! 😇 It sits inside a user’s day, alongside their existing tools, workflows, habits, mental models, and constraints. Understanding that <em>ecosystem</em> — which apps they already use, how data flows between services, what switching costs look like, who the adjacent personas are (the admin, the manager, the colleague receiving the output) — requires sustained observation &amp; cross-functional conversation.</p><blockquote><em>AI tools accelerate the </em>building<em> of a thing without illuminating </em>the world the thing enters<em>. Rushing past this produces products that are technically functional but contextually orphaned. 🤨</em></blockquote><h3>Impacted: Paths to adoption</h3><p><strong>• Change management: </strong>Even the most elegantly designed feature fails if users can’t find their footing when it arrives. 🫠 When teams sprint from build to ship without thinking through the <em>transition</em> — what workflows change, what muscle memory gets disrupted, how power users and novices experience the delta differently — adoption suffers. Confusion spikes. Support tickets multiply. Trust erodes.</p><p>Change management isn’t a post-launch afterthought; it’s a design problem that requires the same forethought as the feature itself.</p><p>Velocity culture treats it as someone else’s job. AI-assisted shipping makes it even easier to pretend it doesn’t exist at all.</p><p><strong>• Go-to-market readiness: </strong>Shipping is not launching! 😅A launch requires that customer success teams understand what changed …and why. That comms are calibrated to the right customer segments with the right framing. That sales can articulate the new value clearly with documentation which reflects reality, not a wishful spec.</p><blockquote>When product teams race to ship, GTM processes get compressed into a rushed Slack message and a changelog nobody reads.</blockquote><p>The result: features that exist but don’t land, value that’s real but invisible, and customers who feel confused rather than delighted. <strong><em>Velocity that outruns your GTM motion isn’t speed — it’s just noise.</em> 😬</strong></p><h3>The deeper trap</h3><p>Designers know deep down that imagination, empathy, and serendipity play vital, subtle roles in discovering &amp; enabling a compelling customer experience — even potentially a breakthrough product that reshapes an industry.</p><p>Now the arrival of AI coding tools adds a new psychological wrinkle: <em>the feeling of progress</em>. When Cursor generates a working component, or v0 scaffolds a complex UI in minutes, there is a genuine dopamine hit. Something exists that didn’t exist before. The temptation is to mistake that feeling for value — to confuse generation with design, output with judgment, speed with wisdom.</p><blockquote>The victims of velocity were always with us.</blockquote><p>The discipline required to protect craftsmanship, forethought, empathy, learning, ecosystem awareness, change readiness, GTM integrity, and engineering quality — these were always in tension with deadline culture. What AI tools have done is lower the activation energy for skipping all of it while <strong><em>feeling</em></strong><em> productive</em> the entire time.</p><p>How do we ensure humanistic aspects essential to what is good &amp; beautiful don’t become “victims of velocity” per competing pressures, now turbocharged by tools that make cutting corners feel like innovation? 🤔 😬</p><blockquote><em>It’s an ongoing discussion… and a battle we must all fight. 🔥</em></blockquote><p><em>What would you add to this list? What has your team felt the cost of rushing past? I’d love to hear.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=acafa335a555" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The quiet dissolution of design wisdom]]></title>
            <link>https://medium.com/design-bootcamp/the-quiet-dissolution-of-design-wisdom-f98caa7f685b?source=rss-f2a23e77b0a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/f98caa7f685b</guid>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Uday Gajendar]]></dc:creator>
            <pubDate>Wed, 28 Jan 2026 23:24:01 GMT</pubDate>
            <atom:updated>2026-02-08T23:07:53.176Z</atom:updated>
            <content:encoded><![CDATA[<p>An attempt to articulate the melancholy</p><figure><img alt="Dark mysterious liquid ripples like inky black water." src="https://cdn-images-1.medium.com/max/1024/0*qrQH8HpE0PgbBOnh.png" /></figure><p>Over the past few years it seems there’s been a particular kind of <em>quiet</em> in design spaces these days — not that productive quiet of deep work, but a melancholy ghost of questions no longer being asked. We’ve become so expert — so <em>fluent</em> — in the language of velocity, while forgetting the rhetoric &amp; argument of thoughtful restraint. A diligent designer shows PM or Engineer their latest prototype, generated in minutes, polished to perfection. “Look how fast,” they’ll say. Ship it. But speedy shipping towards…what? 🤔 As <a href="https://medium.com/p/7b6e8a8751ab">this piece allude</a>s to, optimizing for velocity without the human collaboration or decision-making in place can be damaging.</p><blockquote>No one seems to remember what’s the goal.</blockquote><p>This is how fields don’t die — they <strong>dissolve</strong>. 😶‍🌫️ Not in some final spectacular collapse, but in the gradual replacement of thinking with incessant doing, of wrestling with rendering. We’ve mistaken the ability to produce for the capacity to discern, to question, to wonder. Every tool promises to make us faster, but none ask if we’re heading in the right direction. Where are we going with all this?</p><blockquote>The human compass has been traded for quick blueprints to drive speedy execution.</blockquote><p>We see now junior designers pressured to learn AI prompting before they learn to problem-frame, to tackle indeterminate messiness — the heart of most problems! Senior designers, with their repertoire of hard-won pattern recognition + systems thinking, find themselves <a href="https://diginomica.com/tech-industry-has-ageism-problem-heres-why-matters-us-all">“optimized out” </a>— their deft ability at stakeholder management &amp; workshop facilitation reframed as resistance to delivery. The <a href="https://www.itsnicethat.com/features/welcome-to-the-entry-level-void-light-and-shade-digital-220925">middle is hollowing out</a>, leaving only those who execute, and those who approve, with no one left to question. 😬 What’s the benefit, and for whom?</p><blockquote>The real fracture or divide isn’t between human &amp; AI creativity.</blockquote><p>It’s between design as an act of <strong>care</strong> versus design as an act of <strong>production</strong>. We’ve confused Autolayout components with the deeper work of human understanding — a kind of slow archaeology of revealing what real people need, not just what they’ll click faster. That patient cultivation of taste, judgment, and ethical reasoning. The loss of courage to say “no” in a fearful culture that only rewards “ship it now.” 😔</p><p>What haunts me isn’t that AI can generate interfaces faster — that was somewhat inevitable anyway! It’s that we’ve so thoroughly relegated or regressed design that auto-generation feels sufficient. It’s “okay”. Everyone moves quicker toward nowhere in particular. The dissolution accelerates because it feels like progress. We’ve built a delivery machine that runs smoothly while forgetting what it’s supposed to produce …and for what <em>purpose</em>. We’ve reduced the designer’s role to such mechanical tasks that of course a machine can do them. As described in an essay from Dec 2023, w<a href="https://uxdesign.cc/self-sabotage-in-the-ux-design-industry-a7c092af8cc7">e likely did this to ourselves:</a> one sprint at a time, one “good enough, ship it” at a time, one unquestioned requirement at a time. One compromise at a time, while seeking that elusive “seat at the table.” 😒</p><blockquote><em>Everyone moves quicker toward nowhere in particular. It’s like a weird echo of Godot — not waiting for someone to arrive but waiting for a destination to define the goal.</em></blockquote><p>But here’s what the efficiency folks miss: the inefficient parts — those tough conversations about what we’re really trying to achieve, the debates about ethics masquerading as arguments about aesthetics, the slow gestation of ideas that need time to mature (as <a href="https://www.startuparchive.org/p/jony-ive-ideas-are-always-fragile">Jony Ive famously said</a>, “ideas are always fragile” and need time to incubate) — these aren’t bugs in the design process. <strong>That <em>is</em> the design process. ⚡️</strong></p><p>That’s where design <em>wisdom</em> lives, not in the heroic designer’s mad craft-precision skills or DS repository, but in the collective wrestling with complexity. <strong>It’s a team sport.</strong></p><p><strong>Design wisdom</strong> — borne of lived experience, judgment, taste, and intent — was never about knowing which button color converts better or how to structure an optimal menu system for a bloated platform. As Nathan Shedroff famously defined in his <a href="https://nathan.com/information-interaction-design-a-unified-field-theory-of-design/">“unified theory of information”</a>, wisdom is an accumulated knowledge over time with lived moments. Conversion, retention, upsell — <em>that was never the point</em>. It was about holding multiple probable &amp; preferable <a href="https://www.critical.design/post/speculative-design-vs-design-fiction">futures</a> in tension, about understanding the second-order effects of our collective decisions, about <a href="https://www.thisisdesign.school/hugh-dubberly/">seeing the system</a>, a <a href="https://firstmonday.org/ojs/index.php/fm/article/view/672/582">socio-information ecology</a>, beyond a clickbait screen. It was about asking not “can we?” but “should we?” — while having the vocabulary &amp; <em>authority</em> to articulate why not. 🔥</p><blockquote>That’s the seat the table. We own it by asking the questions, while driving the <a href="https://medium.com/responsible-design/what-is-responsible-design-8e587078fa9b">responsibility</a>.</blockquote><p>So here we are, watching this wisdom atrophy in real-time. Not because LLMs and AI are replacing designers, but because we’ve forgotten what we’re here for. We’ve internalized the logic of efficient rapid scale so completely that we can no longer imagine a practice organized around anything else. <a href="https://medium.com/responsible-design/what-is-responsible-design-8e587078fa9b"><em>Growth designer</em>?</a> Please. We’ve become so focused on removing friction that we’ve forgotten friction is often wisdom in disguise. 🤨</p><p>So the question isn’t whether design will survive…of course it will! Products still need interfaces, brands still need expression, problems still need solving (even if we’re solving solved problems all over again 😅).</p><blockquote>The question is whether what survives will be recognizable as design, or merely PM-driven production wearing design’s old clothes.</blockquote><p>But some folks are already choosing differently! Building practices that prize thinking over throughput. Creating space for the slow development of judgment. Insisting on the difference between making things right and making the right things. They’re not fighting the tools — they’re simply, bravely refusing the false logic that says tools are all we need. 🙌🏽</p><p>This rebuilding of design wisdom will come from remembering that design is, at its core, an <strong><em>act of </em></strong><a href="https://www.epicpeople.org/design-as-a-cultural-system/"><strong><em>cultural creation</em></strong></a>. 👣 It’s about encoding values into systems, about choosing what kind of world we want to live in, one interaction, one interface, one map or diagram at a time. We don’t need faster ways to generate solutions. <strong>We need better ways to sit with problems.</strong> We don’t need more efficiency. <strong>We need more careful forethought. </strong>And wisdom, as lived experience &amp; informed intuition, inherently resists automation. 🙃 Funny how that works!</p><p>That collective design wisdom took decades to build — from multiple schools of thought (<a href="https://homes.izmirekonomi.edu.tr/cozcan/ID204DesignSemioticsForID/Buchanan.pdf">rhetoric</a>, <a href="https://medium.com/@msbernst/teaching-hci-foundations-and-frontiers-76bb22616e0d">human factors/HCI</a>, anthropology, sociology, etc.). But it can be cultivated again, if we remember what it was for: not to make things faster, but to make things that <em>matter</em>. Not to reduce friction for more clicks, but to create <em>meaning</em>. Not to optimize metrics, but to serve <strong><em>humanity</em></strong>.</p><blockquote><em>To humanize technological culture &amp; expression.</em></blockquote><p>The choice is still ours. But every day we don’t make it, we drift further from what design could be for the UX/Tech industry. The cliff is fast approaching. 😬</p><p><em>Originally published at </em><a href="https://udanium.substack.com/p/the-quiet-dissolution-of-design-wisdom"><em>https://udanium.substack.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f98caa7f685b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-quiet-dissolution-of-design-wisdom-f98caa7f685b">The quiet dissolution of design wisdom</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Courage to Reset: A manifesto ]]></title>
            <link>https://udanium.medium.com/the-courage-to-reset-a-manifesto-be62a622b06e?source=rss-f2a23e77b0a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/be62a622b06e</guid>
            <category><![CDATA[design-leadership]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-strategy]]></category>
            <category><![CDATA[manifesto]]></category>
            <dc:creator><![CDATA[Uday Gajendar]]></dc:creator>
            <pubDate>Fri, 09 Jan 2026 17:37:20 GMT</pubDate>
            <atom:updated>2026-01-09T17:37:20.615Z</atom:updated>
            <content:encoded><![CDATA[<h4>On unlearning, relearning, and design leadership in 2026</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ga3vCs5-1j0jXQnQ.png" /><figcaption>Via Unsplash: A labyrinth wall decoration for corporate interior</figcaption></figure><p><em>“The illiterate of the 21st century will not be those who cannot read and write, but those who cannot learn, unlearn, and relearn.”</em> — Alvin Toffler, ‘Future Shock’</p><p>Design does not suffer from a lack of tools. It suffers from a failure to <em>unlearn</em>.</p><p>We learned to equate speed with progress. We learned to mistake <a href="https://medium.com/@udanium/craft-ai-wont-fix-your-design-strategy-problem-3724784d3d6e">craft for strategy.</a> We learned to optimize for delivery while quietly outsourcing judgment to processes, to frameworks, to machines that do not judge at all.</p><p>AI did not cause this fracture, this confusion. It exposed it. The way a sudden light exposes how long the room has been darkened.</p><p>And now we face a choice that is not really a choice: unlearn, or become obsolete in ways that have nothing to do with technology.</p><p>There are designers who believe the crisis is about <strong>tools</strong>. Learn the new ones fast enough, they say, and you will remain valuable. This seems like the logic of an assembly line applied to the mind. It mistakes pliability of machinery for mastery of purpose.</p><p>There are designers who believe the crisis is about <strong>craft</strong>. Polish the precise pixels, they say. Protect the hand-made from the generated. This feels like nostalgia dressed as resistance. It mistakes the artifact for the act.</p><p>Both are ways of avoiding the harder question: What is design <em>for</em> when everything that once made it slow can now be made fast?</p><p>If you can’t answer that, maybe you’re not being disrupted — you’re being revealed.😶‍🌫️</p><p>We must unlearn value as delivery convenience. And relearn value as <strong>deep responsibility.</strong></p><p>Value is not a slide. Not a story told after the fact to justify what was already decided. Not a metric selected for its willingness to move in the right direction.</p><p>Value is the discipline of naming what changes — truly changes — because design was present. In decisions. In behaviors. In the tradeoffs that were made explicit rather than buried. In the outcomes no one wanted to measure because measurement would indict choices blindly made.</p><p>If you cannot name the value before execution begins, you are not leading. You are decorating decisions made elsewhere.</p><p>We must unlearn quality as polished perfection. And relearn quality as <strong>collective trust</strong>.</p><p>Quality is not only concerned with the smoothness of a surface. It is not just defined by the precision of spacing, the consistency of components, the adherence to systems that exist because someone once decided they should exist.</p><p>Quality is really what remains reliable when circumstances become unreliable. The clarity of intent when the system fails. The confidence — hard-won, easily broken — that users and organizations place in what we build. Not just because it is beautiful. Because it is also, critically, <em>trustworthy</em>.</p><p>In an AI-driven world, quality is ethical before it is aesthetic. Operational before it is visual. Human in ways that have nothing to do with whether a human hand touched the final file.</p><p>We must unlearn discipline as mechanical process. And relearn discipline as <strong>careful restraint</strong>.</p><p>Discipline is not only the rituals we perform to feel rigorous. Not just the ceremonies of critique and review. Not found in the frameworks adopted because they came with a name and a diagram and the promise of repeatability.</p><p>Discipline is the courage to say no. To scope. To subtract. To make the tradeoff explicit and live with its consequences rather than hiding them in backlogs and “future considerations.”</p><p>Without discipline, design becomes decoration. With discipline, design becomes governance.</p><p>You are not owed a seat at the table. You earn it by knowing what you will <em>not</em> do.</p><p>We must unlearn judgment as taste. And relearn judgment as <strong>accountability</strong>.</p><p>Taste is a luxury that belongs to those who do not have to justify their choices. It is the province of the auteur, the designer-as-hero who answers to vision alone. Usually their own vision. 😅</p><p>Judgment is what remains when you must answer to others. When the choice is not between good and bad but between bad…and <em>worse</em>. When you must decide knowing you will be wrong, and decide anyway, and stand behind the decision when its consequences arrive.</p><p>AI can generate. AI can optimize. AI can even, in its parroted way, prescribe taste.</p><p>But AI cannot be accountable. That is yours. Do not abdicate it!</p><p>This, then, is what I think of as the <strong><em>reset</em></strong>.</p><p>Not returning to some imagined past when designers were respected and craft was enough. That past really did not exist. We have <em>always</em> been fighting for relevance; we have only recently begun to lose — identity, place, agency.</p><p>Not pursuing a Luddite-style rejection of AI. The tools are not the problem. The tools have never been the problem. The problem is what we were willing to forget in order to use them.</p><p>Not adopting yet another new framework, a new process, a new set of rituals to replace the ones that failed us. We do not need more new new machinery for thinking. <strong>We need to think. 🤔</strong></p><blockquote><strong>We need a reset of design’s posture. Toward organizations that would prefer we simply produce. Toward technologies that make production effortless &amp; meaning expensive. Toward ourselves, who chose convenience when we should have chosen consequence.</strong></blockquote><p>From commoditized making → to purposeful meaning.</p><p>From velocity-driven output → to judgment-laden outcomes.</p><p>From clinging to relevance → to claiming responsibility.</p><p>These are not slogans. They are directions.</p><p>You will not arrive. You will only drive.</p><p>The future does not belong to designers who master the latest tools. It does not belong to those who defend the old ones, either. 🙃</p><p>It belongs to those who can learn what is needed, unlearn what is not, and relearn what was always true but briefly forgotten: <strong>Design is not a service function; it is a leadership practice.</strong> And leadership cannot be automated, optimized, or delegated to systems that do not bear the weight of their own choices.</p><p>Design will not be saved by tools or AI. Design will not be saved by craft. Design will not be saved at all.</p><blockquote><em>It will only be </em>practiced — <em>by those willing to lead.</em></blockquote><blockquote><em>Or it will be forgotten.</em></blockquote><blockquote><em>😔🙏🏽</em></blockquote><p><em>Originally published at </em><a href="https://udanium.substack.com/p/the-courage-to-reset-a-manifesto"><em>https://udanium.substack.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be62a622b06e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Craft + AI Won’t Fix Your Design Strategy Problem]]></title>
            <link>https://udanium.medium.com/craft-ai-wont-fix-your-design-strategy-problem-3724784d3d6e?source=rss-f2a23e77b0a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/3724784d3d6e</guid>
            <category><![CDATA[craft]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Uday Gajendar]]></dc:creator>
            <pubDate>Tue, 30 Dec 2025 21:08:13 GMT</pubDate>
            <atom:updated>2025-12-30T21:08:13.707Z</atom:updated>
            <content:encoded><![CDATA[<h4>Speedy, generative craft is seductive…but insufficient</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fRNTWqNLHpCmiL9-J-go1Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@kellysikkema?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Kelly Sikkema</a> on <a href="https://unsplash.com/photos/a-person-drawing-a-diagram-on-a-piece-of-paper-lFtttcsx5Vk?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p><strong>🪧 Tl;Dr —</strong> <em>AI-infused craft makes it faster to build the wrong thing. Design leadership determines whether you’re accelerating in the right direction.</em></p><p>Periodically, I’ll get a brief message from my LinkedIn network or someone affiliated with startups, accelerators, etc. It typically goes like this:</p><p><em>“Hey, we need a designer to help us move faster. Do you know someone (maybe you?) who can jump in and start cranking out Figma to unblock Dev?”</em></p><p>🙄 I mean, yeah sure but… given my experience, more often than not such a request is potentially a signal that something more fundamental is likely broken or missing. Here’s the uncomfortable truth: if your most urgent UX need is <em>“more screens, faster,”</em> you’re tackling the wrong problem. And now, with AI able to generate those screens instantly, that problem gets amplified, faster.</p><blockquote>AI is excellent at accelerating execution <strong>when direction is clear</strong>. But many teams mistake speed for strategy — and velocity for progress — without the necessary scrutiny.</blockquote><h4>Four key “anti-patterns” to beware</h4><p>After 20+ years working across startups and scale-ups — from climate tech to fintech, mobile apps to enterprise systems — I’ve seen the same patterns emerge when teams lack strategic design leadership. These aren’t edge cases. They’re common failure modes that quietly erode momentum, burn runway, and exhaust teams. If AI is applied aggressively without diligent precautions &amp; human (or organizational) consideration, the potential to accelerate such anti-patterns increases. 😬 Not a good thing! Let’s take a closer look.</p><h4>1. A product-market fit mirage</h4><p>So the team is shipping often. Features are going live. Cool cool. But customers aren’t actively using them — or they churn after a few weeks. Often a reflexive fix is, “let’s make the UI snazzier &amp; simpler!” But crisply rendered liquid glass or flat minimalist UI on top of a weakly defined <strong>product model </strong>is inadequate. You may be solving the wrong problem or building for the wrong user altogether.</p><ul><li><strong>⚠️ Caution: AI can actively undermine product–market fit.</strong><br>AI makes it trivial to generate dozens of UI variants, often masquerading as customer-centric rigor. “We tested 12 sign-up flows” feels like progress — but accelerating iteration on the wrong idea doesn’t fix fit. It manufactures false confidence, allowing teams to A/B test their way around a broken value proposition or flawed conceptual model.</li></ul><h4>2. An alignment vacuum</h4><p>Design, product, and engineering all look busy, yet nothing moves in <em>unison</em>. Work efforts overlap or collide. Priorities shift mid-sprint. Progress stalls out — not because people aren’t working hard, but because they’re not working toward unified, aligned goals. This isn’t a tools issue. It’s a <strong>leadership gap</strong>. When teams lack shared understanding and role clarity, even the most talented employees spin their wheels in frustration.</p><ul><li><strong>⚠️ Caution: AI intensifies alignment problems.</strong><br>As design artifacts become cheap and fast to produce, everyone can show up with a solution. The result: more output, less coherence. Three stakeholders, three GenAI-created answers, one meeting. Without strong leadership to align around problem framing and direction, AI accelerates fragmentation — not progress.</li></ul><h4>3. The strategy stalemate</h4><p>We’ve all been there: quarterly planning devolves into circular, agonizing debates. <strong>Roadmaps become wishlists.</strong> Decisions lack context, rigorous criteria, or customer grounding. Without validated assumptions, agreed success criteria, or crisp decision frameworks, roadmaps do become runaway (or random) wishlists. Over time, planning turns political. Morale erodes.</p><p>What’s missing isn’t more ideas — it’s clarity around tradeoffs, informed by a responsible strategic design direction, with product intuition, borne from smart market analysis + deep customer empathy.</p><ul><li><strong>⚠️ Caution: “The AI says we should.”</strong><br>AI can quickly generate market analysis and strategic recommendations — but speed isn’t scrutiny. Teams begin citing AI outputs as evidence for feature decisions, mistaking synthesized data for strategic insight. Without experienced leadership to apply judgment, context, and nuance, AI legitimizes weak thinking instead of strengthening it.</li></ul><h4>4. The execution trap</h4><p>The team is shipping fast, but it’s mostly <em>outputs</em>, not measurable outcomes that map to a set of <strong>learning goals</strong> — or the product value prop. Features rapidly accumulate without forming a coherent end-to-end experience that feels crafted. It’s not delivering durable value, so your customers are frustrated. Teams are exhausted. Leadership is disappointed. 😔</p><ul><li><strong>⚠️ Caution: AI can put execution on overdrive without purpose.</strong><br>When teams can prototype in minutes and generate artifacts instantly, activity gets mistaken for strategy. But speed alone doesn’t create effective progress. Velocity without direction is simply expensive motion with a veneer of impact.</li></ul><h4><strong>What this looks like when it goes right</strong></h4><p>These anti-patterns aren’t inevitable. With experienced design leadership, teams can break the cycle — but it requires someone willing to challenge the brief, not just execute it faster.</p><p>Here’s what strategic design leadership looks like in practice — under real pressure, with real stakes. This is a short story, but it captures the core leadership shift AI cannot automate.</p><p>At Aurora Solar — a platform used by solar installers to design systems and close deals — the main product roadmap for Sales Mode (the solution for creating sales proposals) focused on feature parity with competitors. A reasonable instinct when you’re getting outsold on spec sheets! But stern customer feedback from “Sales Mode deniers” — reps who actively avoided the tool — told a different story: sales reps weren’t churning because we lacked features. They were churning because the proposal tool had become too difficult for real selling conditions — literally at the kitchen table with a curious homeowner.</p><p>Instead of just matching competitors checkbox-for-checkbox, the Sales Mode UX team re-envisioned the core workflow — simplifying how reps view &amp; edit proposals in the field, with fully customizable templates. The result: nearly $1M in retained ARR and major accounts pulled back from the brink of defection. AI could have helped us generate more proposal layouts — but it would not have told us to <em>rethink the selling moment itself</em>. It required listening to disgruntled customers, challenging the brief with innovative thinking, and advocating a judgment call that ran counter to the roadmap.</p><p>That’s the difference between execution &amp; direction.</p><h3>What strategic design leadership enables</h3><p>If these patterns sound familiar, the solution isn’t hiring faster tool operators or better pixel stylists. It’s investing in experienced design leadership — principals, architects, and systems thinkers — who bring clarity, judgment, and <strong>durable</strong> direction.</p><p>Here’s what that looks like in practice:</p><h4>→ Customer-validated direction</h4><p>Instead of chasing internal opinions, teams validate early with real users. Not necessarily heavy research — often sharper questions, clearer assumptions, and faster learning loops. AI can synthesize feedback at scale, but it can’t replace the human judgment required to spot contradictions, read between the lines, or uncover unmet needs users can’t articulate.</p><blockquote>Effective designers know how to leverage AI for research synthesis while maintaining the human judgment that turns data into actionable insights.</blockquote><h4>→ Systems thinking</h4><p>Strategic designers don’t just design screens — they architect multifaceted, resilient, adaptive <em>systems</em>. They examine flows, states, and dependencies across products and teams, building structures that scale instead of patches that collapse into tedious, annoying UX debt. Yes AI can generate variations <em>inside</em> a system — but it can’t design the system itself or reason well across business models, pricing/packaging schemes, and information architecture patterns.</p><h4>→ Cross-functional alignment</h4><p>Effective design leaders translate across product, engineering, business, and customers. They facilitate awkward conversations, surface invisible tradeoffs, and negotiate blurry constraints. AI can’t read the room when a CEO’s pet feature conflicts with research. It can’t navigate politics, emotion, or compromise. This work is fundamentally <em>human</em> — and essential.</p><h4>→ Strategic clarity in execution</h4><p>Design strategy doesn’t live in a fancy deck. It shows up in rituals, frameworks, prototypes, and conversations. Design leaders make strategy tangible, and help teams make better decisions throughout the “messy middle” of cross-functional engagement, from concept to approval to release. And it doesn’t happen overnight, of course. This work takes <strong><em>time</em></strong>. Patience + persistence is the path forward. 🙏🏽</p><h3>The value of strategic design</h3><p>💯 I totally get it: hiring experienced design leaders can feel expensive — especially under the intensifying pressure to ship more faster. But the cost of <em>not</em> having that leadership is far higher, and often invisible:</p><ul><li>Building the wrong feature set — now at 10× speed</li><li>Customer churn from incoherent experiences generated by disconnected tools</li><li>Months lost debating priorities without resolution</li><li>Engineering time wasted fixing misaligned assumptions post-launch</li></ul><p>AI collapses the cost of execution. Leadership determines whether that speed compounds value — or compounds <em>waste</em>. 😬</p><blockquote>The teams that succeed aren’t the ones who ship the most. They’re the ones who learn quickly and adapt deftly.</blockquote><p>In that kind of team, a design leader isn’t just the person holding the pen or wielding the tool. They’re part conductor, part strategist, part systems architect. They can help ensure the pieces harmonize together, even when new AI-infused tools or capabilities join the ensemble…</p><p>This is not something that can be randomly assigned any designer with crazy fast Figma skills, or super-amazing at prompting GenAI. It requires a kind of judgment + lived experience (<em>wisdom</em>) that only comes from <strong>navigating complexity at scale — and applying all the “learned” scars along the way. 😔</strong></p><h3>A final thought…</h3><p>Before posting that role for a <em>“craft-obsessed, scrappy designer who moves fast in Figma”</em> (or prompts GenAI supremely well), pause and ask:</p><blockquote>“Are we missing execution, or are we missing direction?”</blockquote><p>If it’s the latter — and it often is — what you need isn’t a production resource, human or artificial. You need design leadership that can harness AI while providing customer-driven vision AI alone cannot supply. The teams that succeed won’t be the ones who ship the most. They’ll be the ones who learn quickly — and adapt deliberately. The future still belongs to teams that think strategically at <em>human</em> speed and execute tactically at <em>digital</em> speed. You get there by investing in strategic design leaders who know the difference. 🙌🏽</p><p>If this resonates, reach out at udanium@gmail.com or connect with me on <a href="https://www.linkedin.com/in/udanium/">LinkedIn</a> to explore how I can help your team move forward with clarity &amp; purpose. <em>Originally published at </em><a href="https://udanium.substack.com/p/figma-ai-isnt-a-strategy"><em>https://udanium.substack.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3724784d3d6e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Seeing, sketching, and the stillness beyond the pixels]]></title>
            <link>https://udanium.medium.com/seeing-sketching-and-the-stillness-beyond-the-pixels-4a4d845de86a?source=rss-f2a23e77b0a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a4d845de86a</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[reflections]]></category>
            <category><![CDATA[sketching]]></category>
            <dc:creator><![CDATA[Uday Gajendar]]></dc:creator>
            <pubDate>Mon, 27 Oct 2025 00:26:29 GMT</pubDate>
            <atom:updated>2025-10-27T00:26:29.800Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8eSHtttOCse1gTtykYHn8A.png" /><figcaption>Uncertainty by <a href="https://unsplash.com/@lacarta">Santiago Lacarta</a> / Unsplash</figcaption></figure><p>A reflection on the true art of design, with some lamentation…</p><p>So the other day I found myself completely lost in reverie while reviewing old dusty design notes — you know, the kind you scribble in the margins during some late-night design sessions or after particularly heady, tough stakeholder meetings — and I kept returning back to this notion in my mind:</p><blockquote><strong>Design starts with seeing.</strong></blockquote><p>Not just looking. <em>Seeing</em>. 👀</p><p>It’s a practiced art of pattern recognition, of noticing problems &amp; opportunities that others miss. To <em>see</em> is to discern structure, relationships, and possibilities beyond what’s immediately visible. Over time, this seeing becomes a cultivated sensitivity — the ability to sense some faint outline of <em>potential</em> amidst all the thrashy noise and flashy novelty. (And lord knows, we’re drowning in both these days. 😅) Sigh.</p><p>But here’s the thing — seeing is just the beginning!</p><h4><strong>⟐ Sketching as inquiry</strong></h4><p>Once you’ve seen something — some pattern, some friction, some possibility — sketching becomes your fundamental way of thinking aloud. Each mark is an hypothesis. Each revision, a test or experiment. An intriguing branching of paths to explore.</p><p>I’m not talking about pushing pixels in Figma (yes, that has its place). I mean the unfiltered, messy act of externalizing thought — whether that’s with napkin sketches, whiteboard scribbles, or even comping/collaging stuff found via Google. The medium matters less than the <em>intention</em>. ⚡️</p><p>Through sketching, we probe the ambiguity until — if we’re lucky and/or persistent — this key moment of clarity reveals itself. That <em>aha!</em> feeling. <em>Epiphany</em>. The designer’s task is to capture that ephemeral, fleeting moment and render it legibly for others to understand, so as to sustain debate &amp; productive discussion. For forward progress. For shared understanding. 🙌🏽</p><h4><strong>⟐ The illusion of facades</strong></h4><p>But, and this is really crucial — clarity is not decoration!</p><p>So much of what passes as “good design” these days is what Tufte has called “facades of communication” — ornate but empty. Mostly slick style, lacking critical substance. (Looking at you, liquid glass, glowy purple sparkles, and any other trend that prioritizes trendy style over clear, useful, understanding. 🙄)</p><p>Real design work requires <em>respect</em> for the user’s tumultuous journey, beyond “the funnel”: anticipating confusion, guiding attention, and building understanding through empathy &amp; explanation. That’s the actual work of leading from zero to one. Achieving “time to value” <em>supportively</em>, not just quickly.</p><h4><strong>⟐ Emergent qualities, not goals</strong></h4><p>Here’s where I diverge from the craft-obsessed discourse on LinkedIn (you know the kind — exquisite pixels as the ultimate measure of design leadership 😬):</p><p>Refinement matters, sure. Guided by common sense — not paralyzing polish — it can result in that crisp craft we admire. But depth &amp; beauty are <strong>emergent qualities</strong>, not goals to chase. They’re outcomes of authentic honesty &amp; clarity, not objectives you can optimize for in your sprint planning. How many points do you assign to honesty &amp; clarity?? 😅</p><p>Each interaction reshapes both artifact and observer, deepening the conversation between human + system. This is that nonlinear journey Kevin Bethune writes about in his book <a href="https://mitpress.mit.edu/9780262049436/nonlinear/">Nonlinear</a> — messy, iterative, and ultimately more truthful than any perfectly polished deck can convey. 🙃</p><h4>⟐ <strong>Design as research</strong></h4><p>Borrowing again from Tufte: design is in itself a form of <em>research</em>. It’s a continuous experiment in perception, reasoning, and care. The “thinking eye” (to use Tufte’s phrase) seeks excellence not for applause or awards, but for <em>insight</em>. For that profound moment when a user thinks: <em>“Wow, thank you… of course! It all makes sense!” </em>And achieves their goal with some satisfaction, maybe even personal fulfillment.</p><p>In that quiet pursuit of knowledge, design finds serenity — a stillness from which all true creativity flows. Not the pseudo-Zen of a flat minimalist aesthetic, but the actual calm &amp; confidence that comes from deeply understanding a problem, and its potential solution. Truly inhabiting those spaces as conveyed by the “double diamond” scaffolding. 🤔</p><h4><strong>⟐ In practice…</strong></h4><p>So what does this look like in practice?</p><ul><li>Resisting that seductive lure to jump straight to “a few quick screens” (even when Lovable or V0 makes it so easy). Be cool.</li><li>Asking those pesky annoying questions about what problem we’re really solving, and why it matters — what’s driving the priority?</li><li>Making space for the messy middle — the sketching, the debates, the revisions, etc.</li><li>Trusting that clarity will emerge from the process, not precede it. And clarity is a kind of design leadership, too.</li><li>Caring enough to do the hard work of explanation, not just execution. We’re all evangelists to some degree; it’s inherent to the work we do.</li></ul><p>But I must admit — I fear these actions are rapidly becoming a lost art nowadays with the deepening dependency upon AI tools, and increasing impatience by stakeholders for anything that feels like resistance, slowing down velocity to hit artificial deadlines. But they are still important and vital. 🔥</p><p>After 20+ years in this field, whether it’s within growing startups or established enterprises, I keep coming back to this: <strong>the designer’s central job is to see clearly, think deeply, and communicate honestly.</strong> The pixels — polished and beautifully spec’d out as they may be — are simply the resulting artifact of that deeper essential practice. 😌 🙏🏽</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a4d845de86a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design as Value, Quality, Discipline]]></title>
            <link>https://udanium.medium.com/design-as-value-quality-discipline-4bfbcfe26e67?source=rss-f2a23e77b0a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/4bfbcfe26e67</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[craft]]></category>
            <dc:creator><![CDATA[Uday Gajendar]]></dc:creator>
            <pubDate>Sun, 24 Aug 2025 01:35:52 GMT</pubDate>
            <atom:updated>2025-08-24T01:35:52.920Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Wireframe pen sketches of mobile UI screens" src="https://cdn-images-1.medium.com/max/1024/1*sqnbQOnmnS6gh_XSb85t4Q.png" /></figure><p><em>Framing design to foster relationships — even in the age of AI</em></p><blockquote>“Value” might be the most overused word in the Tech Industry.</blockquote><p>In investor-led conversations, amid the endless chorus of “creating value” and “value prop,” the word has become so trite it’s practically meaningless. Yet here I am, a design leader trying to articulate what design actually brings to the table — dancing across multiple <a href="https://open.substack.com/pub/udanium/p/levels-of-design-craft?r=2kkmh&amp;utm_campaign=post&amp;utm_medium=web&amp;showWelcomeOnShare=false">levels of craft</a> from production to storytelling to principled compromise — and I keep coming back to this same damn term. Sigh. 😔</p><p>So how do we talk about the actual bonafide <em>value</em> of design without being lost in empty corporate speak?</p><p>After years of navigating this tension, I’ve found it helpful to think about design through three distinct but interconnected lenses: <strong>value, quality, and discipline</strong>. Each offers a different way to frame design’s contribution and each helps cut through the noise in its own way.</p><h3>Design as value: Impact, inspiration, influence</h3><p>When pressed to define design’s value, I often reach for the familiar frameworks: the triad of usefulness, usability, desirability. Or I’ll invoke <a href="https://udanium.substack.com/p/being-thrown-into-a-situation">Eames’ Venn diagram</a> of various overlapping concerns, or dive deep into <a href="https://www.yumpu.com/en/document/read/3669373/good-design-in-the-digital-age-aiga">Richard Buchanan’s humanistic approach</a> — is the design good, fair, just, right? The effects of choices and so forth…</p><p>But in practice, I’ve found design’s value manifests most clearly in three ways — in terms of impact, inspiration, and influence:</p><ul><li><strong>Impact</strong> of something tangible and observable — an outcome you can point to, measure, or at least describe with specific criteria. Like a physical impact, there’s something left behind, of consequence &amp; resonance.</li><li><strong>Inspiration</strong> is about provocation &amp; stimulation — sparking imagination around optimistic possibilities while also generating productive arguments that tease out what’s truly critical or essential.</li><li><strong>Influence</strong> acknowledges that design happens through relationships. Understanding your cross-functional peers’ goals, motives, and deeply held beliefs — then knowing how to shift them through the powers and artifacts of design — that’s powerful value indeed!</li></ul><h3>Design as quality: Beyond pretty pictures</h3><p>“Design” remains a frustratingly loaded word. It’s either too emotional or too pedantic, buried under over-justified rationale that’s evolved into trendy buzzwords. And still, even today in 2025, design is too often seen as simply making things look sexy, exciting, glamorous. <a href="https://medium.com/@udanium/b64e00d7807d">Pretty</a>. Ugh. 😑</p><p>But <strong>quality</strong>? Now that’s a word we all respond to favorably.</p><p>When we think of quality, we think of something well-made, crafted with durability &amp; strength. There’s an aesthetic dimension too — elegance, a poised balance of visual and tactile qualities — but it’s not <em>just</em> about looks. Quality suggests something that can stand the test of time. (Or at least until the next major release! That’s the life of software…)</p><p>So I’ve learned to lean into this. At one company, I led “Design QA” sessions to verify implementation accuracy against approved specs. Later, I helped spearhead a company-wide “quality” initiative — my subtle code for “design-driven” — without triggering pre-existing bias. The word “quality” broke the ice with engineers &amp; business leaders alike. It bypassed the messy baggage around “design” and helped us connect on shared ground. We all want to deliver something of high quality, something we can be proud of. Who doesn’t, right?</p><p>Quality becomes a pathway to design’s deeper value that’s both tangible and distinctive — cohesively applied brand qualities, UX patterns, and UI components that support &amp; respect the customer’s time, effort, and money.</p><h3>Design as discipline: Beyond creative whimsy</h3><p>“Process” can be a super touchy word in Tech. 😅 It connotes bureaucracy and time-wasting tedium, all for its own sake. Suggesting a team follow a “design process” can sound like an emphasis on project management — a mechanized, sequentialized procedure. Big burden. Huge snooze!</p><p>Yet we urgently need design to be seen as more than idiosyncratic artistic spontaneity (like those <em>Mad Men</em> drinking-and-spacing-out scenes). There must be rigor, systematic thoughtfulness, deliberation toward tangible — and yes, even measurable — outcomes.</p><p>So I talk about <strong>discipline</strong> instead: <em>As a team and company, how can we establish a sustainable discipline of design? Let’s apply design discipline to this problem. We need a disciplined approach to tackle this ambiguity.</em></p><p>Discipline suggests two things that help the designer make their case:</p><ul><li><strong>Design as rigorous activity</strong> —with intensity and reflection, a methodical cadence guided by rules, constraints, and criteria.</li><li><strong>Design as established approach</strong> — something that’s accorded recognition and space for how it enables the team’s goals.</li></ul><p>By framing design as discipline, we confer professionalism to the practice of designing and position the designer as a dedicated practitioner worthy of merit and respect, like an engineer or business manager.</p><h3>The thread that connects</h3><p>Value, quality, discipline — these aren’t just semantic tricks or corporate camouflage. They’re different facets of the same fundamental truth: design matters not because it’s mysterious or magical, but because it’s a systematic way of solving problems that puts people first.</p><blockquote>Design is a systematic way of solving problems that puts people first.</blockquote><p>When we talk about design as <strong><em>value</em></strong>, we’re acknowledging its measurable impact on human experience. When we frame it as <strong><em>quality</em></strong>, we’re connecting to everyone’s intuitive understanding of craft with care. When we position it as <strong><em>discipline</em></strong>, we’re owning our “seat at the table” as rigorous professionals.</p><p>But here’s what makes this moment different: <strong>In the AI era, that integration is our new craft. ✨</strong></p><p>We’re not just pushing pixels or plotting flows anymore — we’re shaping feedback loops, tempering automation with care, and designing dynamic systems that still make space for people to feel seen. This is difficult work with emerging patterns, practices, and principles still being developed.</p><p>The challenge isn’t choosing between value, quality, and discipline — it’s knowing how to weave them together while navigating unprecedented complexity. AI doesn’t replace human judgment; <strong>it demands more of it.</strong> More of our ethics, our empathy, our discernment. More of that careful blend of strategic foresight, creative provocation, and deep humanism.</p><p>When every tool promises to “streamline” or “optimize,” our job becomes more essential, not less. We become the <em>stewards</em> who ask not just “can we?” but “should we?” We’re the ones ensuring that in our rush toward automated efficiency, we don’t accidentally design people out of their own experiences! 🤨</p><p>Because at the end of the day, that’s what design is really about: making the complex simple, the alien familiar, the impossible inevitable — while ensuring people still feel belonging in the world we’re creating. Even when we’re just trying to explain what we do for a living. 🙏🏽</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4bfbcfe26e67" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Backstage preparing for a UX conference]]></title>
            <link>https://medium.com/rosenfeld-media/backstage-preparing-for-a-ux-conference-a62c4981d679?source=rss-f2a23e77b0a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/a62c4981d679</guid>
            <dc:creator><![CDATA[Uday Gajendar]]></dc:creator>
            <pubDate>Thu, 13 Jun 2024 00:01:25 GMT</pubDate>
            <atom:updated>2024-06-13T13:21:43.704Z</atom:updated>
            <content:encoded><![CDATA[<p>I recently wrapped up co-curating and emceeing the <a href="https://rosenfeldmedia.com/events/futures/">Designing with AI 2024 </a>virtual conference with <a href="https://www.linkedin.com/in/louisrosenfeld/">Lou Rosenfeld</a>, for Rosenfeld Media. I’ve been involved in curating conferences for Rosenfeld Media for almost 10 years, going back to 2015 with the first <a href="https://www.youtube.com/watch?app=desktop&amp;v=g1c_1LGIiOM&amp;ab_channel=RosenfeldMedia">Enterprise UX event</a> held at Rackspace HQ in San Antonio. Over the years, as the event morphed into Enterprise Experience (then back to Enterprise UX) and going fully virtual, my level of involvement and role fluctuated as others were wonderfully welcomed and amazingly involved. No two events were the same, and it’s been an incredible ride all along — truly honored! 🙏🏽 😁</p><p>This year with DWAI24 the approach was different in that I took a bit of a co-captain/leadership role in a few areas:</p><ul><li><strong>Shaping the program itself,</strong> by reviewing and selecting speakers — with valuable help and feedback from an informal group of advisors</li><li><strong>Working with the speakers &amp; panelists</strong> via feedback rounds — with iteration, collaborative reviews, speaker coach, and operational aspects thereof (“herding the cats” with constant comms and calendar logistics 😅)</li></ul><p>There’s also a third aspect this year that I leaned heavily into — serving as the <strong>program</strong> <strong>emcee</strong>! 🎤</p><p>In previous years that role was shared among the conference curation team across the themes or days, or we had someone hired specifically for the whole event. Thankfully, as fully expected with the Rosenfeld team, there was already a well-defined “run of show” document with links, titles, name pronunciations, and exact timings all set up for me — so there’s no surprises (well, that we can control anyway…more on that in a moment!) and I felt fully prepared in advance. Whew! 🙏🏽 ✅</p><blockquote><em>But there were a couple things in particular I did for my own personal preparation.</em></blockquote><p><strong>Physical setup: </strong>Where I’ve been located physically has changed during the post-Covid years as we’ve gone fully virtual. Last year I was in NYC along with Lou at Rosenfeld HQ, which was quite fun! This year due to prior travel for eldercare at my childhood home in north central Louisiana, I ended up facilitating DWAI24 from <a href="https://www.rustonlincoln.com/">Ruston, Louisiana</a> in my late father’s study! Kinda wild, huh? 😁</p><p>Below is a photo I took the day before the conference started:</p><figure><img alt="Multi-monitor setup with Macbook Air and iPad Pro with two ring lights, mouse, water bottle, headsets, and iPhone cradle" src="https://cdn-images-1.medium.com/max/1024/1*z_Q4ZUUl_PPfkNKsuwmy9Q.jpeg" /></figure><p>As you can see, there’s <strong>a lot</strong> going on!</p><ul><li>Multiple ring lights (like $20/each via Amazon) to ensure even lighting of my face, along with natural window light from the backyard. Also, using an <a href="https://opalcamera.com/opal-tadpole">Opal Tadpole 4K</a> webcam, not the internal Macbook Air camera given its low quality.</li><li>Multiple Bluetooth headphones (Beats Pro and Air Pods Pro), along with a wired headset lanyard as a backup in case those fail. Redundancies!</li><li>iPad Pro to view the live-streamed broadcast so I can check if/when that is going slow or breaking (indeed, that did happen the first day!)</li><li>iPhone cradle/charger in case things go haywire, and I need to call or someone needs to call me.</li><li>Comfortable chair and pillow. And yes, taking stretch breaks as needed!</li><li>Not pictured, but brought in later: mints, dark chocolate candy (Hershey’s Kisses), mug of green tea. Also a ceiling fan spinning with A/C blasting — it’s hot &amp; humid in Louisiana, plus those ring lights and monitors create some heat! 🔥</li></ul><p><strong>Mental prep: </strong>Of course, serving as an emcee is more than simply reading a defined script on cue. I wanted to ensure that the audience felt they were in good hands, as their steward guiding them along their journey — we like to think of the Rosenfeld Media conferences as <em>conversations</em> — feeling as natural and smooth as possible, with ample energy for everyone! ⚡️🙌🏽</p><p>So I followed the approach I often do for my own talks — I did a lot of writing days before, to get my head into the right space. I wrote and re-wrote the schedule from memory, to help me internalize the flow of speakers, breaks, sessions. I verbally rehearsed the names again and again. More writing of thoughts, quotes, transitional phrases to connect breaks to sessions. Visualizing the flow of the day, in terms of interacting with Zoom, Slack channels, Google Doc scrips, the live broadcast, etc. Also literally practicing the mechanics moving my cursor across windows, and across monitors.</p><figure><img alt="Handwritten, scribbled pen notes across two pages of unlined sketchbook, with a black ink ballpoint pen across the pages." src="https://cdn-images-1.medium.com/max/1024/1*xeeM3AzAqNdZ7aWjP8uvhg.jpeg" /></figure><p>The whole point of all this prep is to get <em>super</em> comfortable with all that, so come 9 AM there’s not some “shock of the new”, scrambling to get things settled while in a panic of sudden realizations. So, I took it kinda seriously — to ensure maximum quality for the audience and speakers, too! 😌</p><p>One final point to emphasize: I sought to be in a state of improv, or <strong><em>“flex and roll”</em></strong> as I call it. As with anything “live”, crazy stuff can happen, and it did. 😆 But you gotta roll with it, and keep the audience going with the flow as well. I’m reminded of two quotes in that regard:</p><ul><li>Maya Angelou’s famous saying that people may forget what you said, but will always remember how you made them <strong>feel</strong>.</li><li>Lou Rosenfeld’s description of the Rosenfeld Media brand voice/tone as “conversational with human warmth”. 🙏🏽</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a62c4981d679" width="1" height="1" alt=""><hr><p><a href="https://medium.com/rosenfeld-media/backstage-preparing-for-a-ux-conference-a62c4981d679">Backstage preparing for a UX conference</a> was originally published in <a href="https://medium.com/rosenfeld-media">Rosenfeld Media</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Levels of design craft]]></title>
            <link>https://medium.com/rosenfeld-media/levels-of-design-craft-5c0526c9dea8?source=rss-f2a23e77b0a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c0526c9dea8</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[enterprise-ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[craft]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Uday Gajendar]]></dc:creator>
            <pubDate>Tue, 28 Feb 2023 18:01:31 GMT</pubDate>
            <atom:updated>2023-02-28T18:15:32.206Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Philip Johnson’s Paine House." src="https://cdn-images-1.medium.com/max/1024/1*uKfxP-hlFV97hKBEgG8ECg.jpeg" /><figcaption>Philip Johnson’s Paine House</figcaption></figure><p>Say it with me: tradecraft, stagecraft, statecraft</p><p>I’ve been championing this notion of multiple levels of craft for a while now — at least 5+ years, since the early days of the <a href="https://rosenfeldmedia.com/enterprise-ux-2023/">Rosenfeld Enterprise UX Conference</a> 😅 It’s now become a bit of a “stump speech”, folded into my recent talks about sensemaking, systems thinking, and what I’ve termed as “meta-design”. 🤨 Enjoy!</p><p>One of the most essential elements of design is <strong><em>craft</em></strong> — shaping materials with masterful skill toward a benchmark of quality, driven by a dedication to refining the details so the result is worthy of personal pride and popular appreciation. Craft is what makes “Design” (writ large) truly a <em>maker’s profession</em>, delivering exemplary artifacts and products, something tangibly defined with careful attention.</p><p>Accordingly, when it comes to designing software apps or services (comprised of interaction, interface, information, and so forth) craft is vital to the execution of a well-formed digital experience — complete with colors, fonts, layouts, timing and sequence of behaviors, sensible paths and flows, and tone of messages. A well-crafted software experience conveys quality that can be seen, felt, shared, and paid for with confidence in the perceived benefits. Craft clearly matters!</p><p>Going further, I think it’s important to explore the <em>levels</em> of craft a designer (and a design leader) can bring to the field. I suggest there are three levels which interplay in the course of doing the work of a professional designer, while engaging with clients &amp; stakeholders to ultimately ship a product / service / experience to customers. Let’s take a closer look:</p><p><strong>🛠️ Tradecraft:</strong> This is the craft we typically associate with design, at the tactical, tangible level of executional details, for final production. Every element precisely and carefully shaped with an exacting attention to the abilities of the tools, potentiality of the materials, and needs of the context at hand. It really is the handiwork, and the work of the trade. Tradecraft also connects to the features and functions of a product (or service, app, etc.) in a visceral way — what is seen, felt, and experienced personally.</p><p><strong>🎭 Stagecraft:</strong> However, finessing the pixel &amp; code-based nuances of a digital artifact is only a part of a designer’s craft. Indeed, such artifacts, as beautifully executed as they may be, are useless unless there is a compelling story that evocatively connects them in a meaningful way — to the stakeholders involved and the ultimate users — so they grasp how it all fits into a theme, a brand philosophy, a set of principles/values around living or working. Stagecraft thus involves presentation skills…and a bit of performance theater, via staging workshops to facilitate complex dialogues that move teams towards new possibilities, alignment of purpose, and shared agreement. Stagecraft is about the performative, collaborative, participatory nature of designing through the power of inspiration &amp; conversation, which connects to an emotional, principled core. It really is the drama of humanism, through the impact of facilitation and presentation.</p><p><strong>☕️ Statecraft:</strong> And as we know, to get that beautifully defined, well-articulated design built and delivered requires certain nuances of compromise, negotiation, and influence. It’s the political, pragmatic stuff that’s inherent to any product development process because, well…<em>people</em>! 😅 Look, people have varying agendas with some ego and maybe trying to amplify their position, due to certain incentive models or belief structures; so, every designer who wants to be effective must grasp this critical point. Indeed, it requires elements of statecraft, artfullly shaping relationships with people towards shared aims, with thoughtful debates on risks, tradeoffs, resources, timelines. This corresponds to the organizational, political, and administrative aspects of designing, which don’t have to be icky or boring! Done well, statecraft can lead everyone toward a pursuit of purpose and value embodied in a potent design direction, that may emerge — sometimes painfully — via those tough negotiations. Knowing how to navigate the nuances of power and relationships is the vital skill to hone, especially while “leveling up” as a design leader.</p><p>Tradecraft, stagecraft, and statecraft may well be the fundamental levels of craft a designer should master as an ongoing career journey. They are not necessarily sequential — just like any creative process, mastering craft can be messy with iterative repeat attempts, with some parallel processing, too: <em>imagine applying statecraft to a business team to protect a new concept’s development, while guiding a team of designers with the storytelling and tactical execution.</em> But at least knowing about these levels can help a designer bring a more informed approach to their own evolving craft of design. ⚡️</p><p>⌘ Useful resources —</p><ul><li><a href="https://mitpress.mit.edu/9780262631891/abstracting-craft/">Abstracting Craft</a> by Malcolm McCullough</li><li><a href="https://www.pearson.com/en-us/subject-catalog/p/designing-together-the-collaboration-and-conflict-management-handbook-for-creative-professionals/P200000008944/9780321918635">Designing Together</a> by Dan Brown</li><li><a href="https://gamestorming.com/">Gamestorming</a> by Dave Gray, Sunni Brown, James Macanufo</li><li><a href="https://www.duarte.com/resources/books/resonate/">Resonate</a> by Nancy Duarte</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c0526c9dea8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/rosenfeld-media/levels-of-design-craft-5c0526c9dea8">Levels of design craft</a> was originally published in <a href="https://medium.com/rosenfeld-media">Rosenfeld Media</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2022 Reflections: Loss, Leadership, and Design]]></title>
            <link>https://udanium.medium.com/2022-reflections-loss-leadership-and-design-ee308325388a?source=rss-f2a23e77b0a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee308325388a</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[loss-of-a-parent]]></category>
            <category><![CDATA[transitions]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Uday Gajendar]]></dc:creator>
            <pubDate>Wed, 21 Dec 2022 21:23:27 GMT</pubDate>
            <atom:updated>2022-12-22T00:34:40.756Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F7ovNTzAsOXrzIiZvAckxw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@yespanioly?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Yousef Espanioly</a> on <a href="https://unsplash.com/photos/DA_tplYgTow?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Looking back upon this year, it was perhaps one of the most dramatically impactful both personally &amp; professionally, in a very long time. It was a year fraught with grief and change, per the passing of my father after a lengthy illness — that in itself is a story to write another time, dealing with the merciless gaps in our healthcare (and eldercare) systems :-( Myriad issues abound — service design, humanism, advocacy, communication, payments, insurance…it’s just exhausting to catalog them, and I’m still processing many lessons therein.</p><p>However, a few points come to mind from the overall journey of my father’s illness &amp; passing that I’d like to share for now, which I hope to develop further in a future story.</p><p><strong>It’s not impossible; often it’s just really difficult: </strong>While it may sound like some athletic shoe ad, adopting this attitude really helped me persevere through the roadblocks, obtuse people, interminable phone holds, and countless documents I had to sign and…fax?! Ugh. But they are just difficulties; they can be overcome with tenacity, help from friends/family, and a lucky break or two (knowing who to know). Being in a small town can truly help, in that regard. More on that later…</p><p><strong>Whatever happens, happens on time, when it’s supposed to:</strong> We can choose to rage against the universe, or accept that certain things happen as they’re meant to, as a way to teach you, guide you, inspire you, help you become better and make things better along the way forward. It’s not about giving in as much as giving way to possibilities that shape you. Sense and respond, with curiosity.</p><p><strong>We live in transition:</strong> As we know, our cells die and regenerate constantly. Our thoughts meander and morph continuously. We fidget and shift our weight, adjusting our posture and place. We’re not the same person moment to moment. We grow and adapt over time. We’re always changing, and transitioning along the way. Knowing this make death — which is really a transition of life — easier to acknowledge as natural and pervasive.</p><p>OK. Whew. That was kinda heavy! I hope to say more soon (likely in 2023 Spring) in a completely separate multi-part essay, to give the proper space to share that perspective.</p><p>Meanwhile, professionally 2022 was a year of delving deep into “management” writ large, leading and building a team for a complex domain within a rapidly growing green-tech startup. More employees every week, higher revenue targets each quarter, and bigger customers to close ever more impressive deals. It’s all quite demanding — yet rewarding! So, it’s against that backdrop I’d like to share the following insights gleaned over the past year, as a design leader and creator.</p><p><strong>1 — We work in psychological contexts; what matters are “essential human skills”.</strong></p><p>It’s important to remind ourselves that we are people first, and work happens among human beings — flawed, complex, nuanced, and often surprising. The workplace — whether virtual or physical — is an ever-changing scene of human engagement. There are various psychologies, mindsets, and interpretations that affect how we thrive and fulfill (or don’t) our own goals. So-called “soft skills” that I call <em>essential human skills</em>, are needed more than ever as work becomes asynchronous, distributed, and dependent on multiple teams. The tenuous connections of human professional relationships need nurturing. This includes listening respectfully, asking with curiosity, and suggesting with humility. And let’s assume good intent — unless proven otherwise!</p><p><strong>2 — We can’t make someone do something; instead, develop influence.</strong></p><p>The moment you find yourself thinking “how do I <em>make</em> that team or peer do” something you want, it’s wise to take a step back and question your own motives and how they may align (or not) with the other’s goals/needs. And then pursue ways to encourage, invite, or advocate for their participation so they feel welcomed into a new system or activity. Setting up for their co-ownership or tying to their key measures (OKRs, etc.) can go a long way for the success of the initiative. Learning how to influence (those human skills again!) is vital.</p><p>Making someone do something via top-down edict or policed standards is a quick path to low morale and negative vibes around you and your project — believe me, I’ve been there! It’s an awful feeling. Instead, explore ways to influence in such a way that creates space for collaboration with shared purpose; maybe doing it so they think it’s their idea all along, isn’t too bad at all ;-)</p><p><strong>3 — In-person presence &amp; interaction is profoundly powerful.</strong></p><p>Going on three years into the Covid pandemic, we’ve all used many tools and methods for collaborative work online (thanks Mural, Miro, Figjam, Slack, and yes…Zoom). And yet, being together in-person is a truly profound, even joyous moment! Nothing beats in-person presence and interaction, developing subliminal, collegial bonds with co-workers while taking an afternoon stroll to the corner coffee shop or touring Salesforce Park after a workshop session.</p><p>Thanks to Covid-safe protocols &amp; vaccines, I’ve been able to lead multiple workshops this year at our San Francisco-based offices with groups of engineers, designers, and product leaders. And there’s nothing quite like it — along with the pungent aroma of Sharpies and tactile feel of crumpling actual Post-It notes! Admittedly, I felt a bit rusty at first. Leading a real-live workshop requires multiple types of energy — physical, mental, emotional and vocal! Yet the positive vibes resulting from workshops persist for days, even weeks, and can reinforce asynch/distributed relations afterwards.</p><p><strong>4 — Prototyping (or “making”) is also research.</strong></p><p>Talking with users and respectfully absorbing their needs, goals, desires, pain points — that’s absolutely vital. In the discovery stage of a project, it’s through listening and learning that we develop a deep empathy for the problem/opportunity space. And also, as demonstrated by my team, via rapid clickable prototypes you can further probe the possibility space, teasing out boundaries and frontiers of what’s really valuable and feasible. As others have noted, designing involves a fun paradox — you have to do a little bit of solution generation to understand the problem, and vice versa. By making quick stimuli (mockups, clickthroughs, etc.) that serve as guided prompts for discussion, you are researching a potential future state, and thus shaping a perspective that can inform a direction for the team.</p><p><strong>5 — Big, hairy, strategic problems need naive questions.</strong></p><p>“Focus on the fundamentals” is the oft-repeated line by head coaches of sports teams which survive their biggest, toughest games of the season. It’s easy in the world of product development to get lost in the overwhelming, intimidating nature of “big hairy problems” of strategy that dominate a quarterly review. Discussions get mired in the muddy language of internal jargon, vague posturing, and indecisive meh.</p><p>Instead, I’ve found it’s more effective to focus on the fundamentals — start with simple, naive questions to steadily build up shared understanding and aligned purpose. What’s the problem? What’s our goal? Who are we serving? What are the constraints? What’s the motivation or pressure driving the decision? What does success look like? Yes they sound basic but such questions can create the rhythm of having rigorous dialogue that can lead to tackling those hairy strategic matters with confidence and clarity. And chances are, others in the room (or Zoom) are thinking the same thoughts — including other leaders! Be the first to be brave enough to ask; others will undoubtedly chime in.</p><p><strong>6 — Don’t lose sight of the abstractions while in the Autolayout 😉</strong></p><p>Sorry for the dig at Figma, but it’s a somewhat half-serious swipe. The power of Figma as a versatile, robust, diligent tool for building design systems, drawing interface layouts, and finalizing production assets is unquestionable — just ask Adobe! And yet, it’s really crucial as designers that we don’t confuse Figma with the design discipline itself. It’s a tool with collaboration wired into its DNA, and intelligently built features, like Autolayout, that amplify a designer’s efficiency.</p><p>However, designing software well requires identifying and analyzing <em>abstractions</em> — conceptual models, object relationships, organizational maps — to form a coherent experience model that guides the resulting interfaces and interactions. Users don’t think in terms of Autolayout or components; instead, they behave in terms of their goals, values, needs, per their contexts of being.</p><p>Our job is to know how to translate a deep sense for those abstractions into well engineered, beautifully crafted apps, sites, and services so people can live their lives well, into the next year and beyond…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee308325388a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>