<?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 Danny Baker on Medium]]></title>
        <description><![CDATA[Stories by Danny Baker on Medium]]></description>
        <link>https://medium.com/@drbaker712805?source=rss-974522956a9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*QX8MZgJFaagCIZ3j94S1Zg.png</url>
            <title>Stories by Danny Baker on Medium</title>
            <link>https://medium.com/@drbaker712805?source=rss-974522956a9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 14:38:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@drbaker712805/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[AI Won’t Replace Judgment. It Will Demand More of It.]]></title>
            <link>https://medium.com/@drbaker712805/ai-wont-replace-judgment-it-will-demand-more-of-it-9629911d3043?source=rss-974522956a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/9629911d3043</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Danny Baker]]></dc:creator>
            <pubDate>Fri, 05 Jun 2026 22:57:48 GMT</pubDate>
            <atom:updated>2026-06-05T22:57:48.373Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A lone figure stands in a dark, futuristic control-room-like space, framed by massive curved walls with glowing red panels, looking toward a bright opening of light in the distance." src="https://cdn-images-1.medium.com/max/1024/1*k8TWuTD9QPqVHFnC4qh65g.png" /></figure><h3>AI may make output easier to generate, but it makes judgment harder to fake. Leaders need to understand the full system their teams work within — from research and design to code, content, data, technology, governance, and business impact.</h3><h3>The Common Assumption</h3><p>AI is often talked about as a shortcut. It can write faster, summarize faster, generate concepts faster, produce code faster, create variations faster, and help teams move through routine tasks with far less friction than before. For many people, that creates an easy assumption:</p><blockquote><strong>If AI can do more of the work, people may not need to know as much.</strong></blockquote><p>I think the opposite is true. AI may make output easier to generate, but it makes judgment harder to fake. The more AI touches the work, the more important it becomes for leaders to understand what that work connects to, where it goes next, what systems it depends on, and how to evaluate whether the result is actually useful.</p><p>A generated design concept is not just a design concept. It may connect to a design system, accessibility standards, content strategy, front-end implementation, product requirements, analytics events, brand governance, or a larger customer journey. A research summary is not just a summary. It may shape product strategy, roadmap decisions, prioritization, messaging, segmentation, or executive alignment. A code prototype is not just a prototype. It may influence technical assumptions, handoff expectations, stakeholder confidence, or the way a team thinks about feasibility.</p><p>That is why AI is not making leadership simpler. It is making leadership more demanding. The risk is not that AI will produce work; it will. The risk is that teams and leaders will move faster than their ability to understand, question, and improve what AI produces. <strong>That is where judgment becomes more important, not less.</strong></p><h3>The Work Does Not Stop at the Output</h3><p>The challenge with AI-generated work is that it rarely stays isolated. A concept, summary, prototype, campaign variant, or code suggestion eventually has to move into a larger system of people, tools, standards, and decisions. That is where leadership judgment starts to matter most.</p><p>If AI helps generate a landing page, the question is not only whether the page looks good. Does it use the right components? Does it align with the design system? Can it be built within the CMS? Does the content model support it? Are the analytics events clear? Is the experience accessible? Does it support the business goal without creating confusion for the user?</p><p>If AI summarizes research, the question is not only whether the summary is well-written. What did it flatten? What nuance did it miss? Were the right participants included? Are contradictions being treated as noise or as insight? Is the recommendation grounded in evidence, or did the AI simply make the research sound more decisive than it really was?</p><p>If AI generates front-end code, the question is not only whether it works in a demo. What is hard-coded? What depends on real data? Where does front-end behavior meet back-end logic? What would need to change before this could become production-ready? Who on the team understands enough of the system to know the difference?</p><p>These are not reasons to avoid AI. They are reasons to lead its use more deliberately. The more AI accelerates production, the more leaders need to understand the workflow around the production — not just the output itself.</p><h3>Start With the Workflow, Not the Tool</h3><p>Leading AI integration well starts before anyone chooses a tool. It starts with understanding the work itself: where ideas begin, how decisions are made, where handoffs happen, what slows the team down, where quality breaks, and where judgment is most important.</p><p>This is where many organizations get the order wrong. They start with the tool because the tool is visible, exciting, and easy to access. A new AI platform gets introduced, a few people experiment, a few use cases emerge, and the organization starts treating adoption as progress. But adding AI to a broken or poorly understood workflow does not automatically make the workflow better. In some cases, it simply helps the team move faster through the same confusion.</p><figure><img alt="A workflow diagram showing how AI can support, but not replace, a team’s process from research and strategy through design, engineering, launch, analytics, and learning." src="https://cdn-images-1.medium.com/max/1024/1*_CLFQSAubgUkB5-VArCStA.png" /></figure><p>A better starting point is to map the current workflow before deciding where AI belongs. How does research move into strategy? How does strategy become a brief? How do design decisions get made? How does content enter the system? Where do design and engineering overlap? Where does data influence decisions? Where are teams repeating low-value work? Where are people waiting on inputs, approvals, documentation, or clarification?</p><p>Once leaders understand that path, AI becomes easier to place intentionally. It might help synthesize interview transcripts, generate first-pass content variations, document design system components, summarize analytics patterns, create prototype code, draft QA checklists, or explore campaign concepts. But each of those uses should connect to a real workflow need, not just a general desire to “use AI.”</p><p>A simple way to start is to ask four questions:</p><figure><img alt="A two-by-two framework graphic showing four questions leaders can use to evaluate AI workflow opportunities: where teams are losing time, clarity, quality, and opportunities to learn." src="https://cdn-images-1.medium.com/max/1024/1*aS59WQabq3-3L8ls2RC55w.png" /></figure><p>That last question matters. AI should not just help teams produce more work. It should help teams become better at understanding the work.</p><h3>What This Looks Like in Practice</h3><p>A UX research team might use AI to summarize interviews, cluster themes, tag transcripts, or draft a first-pass insight report. That can save time, but the team still needs to review the source material, challenge the themes, preserve contradictions, and decide what the research actually supports. AI can help organize the evidence, but it should not be allowed to turn messy human input into false certainty.</p><p>A design system team might use AI to draft component documentation, usage guidelines, accessibility checklists, QA notes, or code snippets. That can make the system easier to maintain, but designers and engineers still need to validate whether the component solves a real use case, works across products, fits the codebase, and supports the full range of interaction states.</p><p>A product design team might use AI tools to generate prototype code, explore alternate flows, or create lightweight demos for stakeholder alignment. That can accelerate learning, but the team still needs to understand what is hard-coded, what depends on real data, where front-end behavior meets back-end logic, and what the prototype does or does not prove.</p><p>A marketing or creative team might use AI to explore campaign concepts, content variations, imagery, localization drafts, or performance summaries. That can expand creative exploration and production capacity, but creative leaders still need to evaluate brand voice, originality, audience fit, legal risk, accessibility, and whether speed is improving the work or simply creating more of it.</p><figure><img alt="A matrix showing examples of AI support across UX research, product design, content, creative, and engineering workflows, emphasizing that humans still need to validate meaning, quality, feasibility, and impact." src="https://cdn-images-1.medium.com/max/1024/1*Sew0xkmY8pP3cWGZkmni5Q.png" /></figure><p>In each case, the leadership job is not simply to approve AI use. It is to define the role AI plays in the workflow, where human judgment stays in control, and how the team will learn from the process.</p><h3>The Real Leadership Work</h3><p>AI should not become a private shortcut where people generate work alone, hide the process, and only show polished outputs. If leaders want teams to build stronger judgment, AI use needs to become part of critique, review, and learning.</p><p>Ask what inputs shaped the output. Ask what the AI missed. Ask what the team changed and why. Ask what risks remain. Ask whether the output improves the user experience or only increases production speed. Ask junior team members to compare AI-generated options and explain which direction they would recommend.</p><p>That kind of review helps preserve the messy middle of the work: the part where people learn to compare options, defend decisions, understand constraints, and develop taste. If AI removes too much of that middle, leaders need to rebuild the learning moments somewhere else.</p><p>The opportunity is not to resist AI or blindly adopt it. The opportunity is to lead its integration with more intention. Use AI to accelerate the work, but build teams that can question it, direct it, evaluate it, and understand the systems it touches.</p><blockquote><strong>AI will not replace judgment. But it will expose where judgment is missing.</strong></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9629911d3043" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI Is Accelerating Work — and Quietly Breaking How We Build Leaders]]></title>
            <link>https://medium.com/@drbaker712805/ai-is-accelerating-work-and-quietly-breaking-how-we-build-leaders-5f2cd98543ab?source=rss-974522956a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f2cd98543ab</guid>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Danny Baker]]></dc:creator>
            <pubDate>Thu, 09 Apr 2026 22:20:08 GMT</pubDate>
            <atom:updated>2026-04-09T23:02:23.009Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A man stands at the front of a meeting room presenting to a small group of colleagues seated around a table. Behind him, a whiteboard displays the word “LEADER” surrounded by illustrated traits including integrity, vision, positive attitude, communication, and inspiration. The team listens attentively in a casual, collaborative setting with laptops, notebooks, and coffee on the table." src="https://cdn-images-1.medium.com/max/1024/1*7CNsZdZ2ef03CeDgxc2hgA.png" /></figure><h4>AI is increasing output across distributed and hybrid teams, but quietly slowing how people learn, think, and grow into leadership — creating a gap most organizations haven’t recognized yet.</h4><p>There’s something happening right now that I don’t think we’re talking about enough.</p><p>AI is making teams faster, more efficient, and more capable. But underneath that progress, there’s a quieter shift happening — one that’s much harder to see. We’re getting better at producing work, and worse at developing the people who will lead it.</p><p>There’s a broader idea here that I’ve written about before — AI isn’t replacing people, it’s amplifying how organizations operate.</p><p>👉 AI Is Testing Leadership — and Talent</p><p>But there’s a <strong><em>second-order </em></strong>effect I’ve been thinking more about recently: not just how AI impacts performance, but how it impacts how we develop people.</p><p>I saw this firsthand while leading a fully distributed team of over 100 designers. The team was strong — smart, capable, and delivering high-quality work. On paper, everything looked like it was working, but something felt off.</p><p>The junior designers were improving their output, but not at the pace we would expect if they were working side by side with more experienced team members. Progress was happening, but more slowly — especially in how they developed their thinking. They asked fewer questions and had fewer opportunities to observe how experienced designers approached complexity. While they could arrive at solid solutions, it took longer to build the deeper understanding behind why those solutions worked or what tradeoffs were being made.</p><p>When teams are working side by side, a lot of learning happens through exposure. You overhear how someone navigates a difficult conversation, sit in on meetings where decisions get messy before they get clean, and ask quick questions that turn into lessons you carry for years. In distributed teams, that kind of learning has to be created intentionally — it doesn’t just happen.</p><p>At the same time, AI is removing another critical ingredient: struggle. Before, when someone hit a wall, they had to work through it. They would try a few approaches, get stuck, ask for help, and gradually build the mental models that make someone effective over time. Now, they prompt, get an answer, and move on. It’s efficient, but it’s not the same as learning.</p><p>Research on deliberate practice, particularly from Anders Ericsson, reinforces that mastery comes from effortful learning — not just arriving at the right answer quickly.</p><h3>We’re Scaling Output Faster Than We’re Scaling Judgment</h3><p>This is the real issue.</p><p>We’re creating a generation of employees who can execute at a high level, but may not yet have the depth of understanding to operate without the tools they rely on. They can produce results, but they haven’t always built the instincts that come from wrestling with problems, making decisions, and seeing how experienced people navigate complexity.</p><p>Leadership isn’t about having answers — it’s about knowing how to think when the answer isn’t obvious. That’s the part at risk. There’s already growing discussion in Harvard Business Review around how AI can improve output while weakening deeper understanding if it replaces, rather than supports, human thinking.</p><h3>Experience Still Shows Up — Even in AI</h3><p>I had a moment recently that reinforced this for me in a different way.</p><p>While working through my master’s program, I shared one of my ChatGPT threads with a few peers — some of whom hadn’t yet moved into management roles. One of them pointed out something I hadn’t noticed: my prompts were shorter, more direct, and I was getting to useful results faster with less back-and-forth.</p><p>At first, I assumed it was just familiarity with the tool. But the more I thought about it, the more it became clear that it wasn’t really about ChatGPT at all — it was about experience.</p><p>I’ve spent years directing teams — framing problems, giving clear guidance, and understanding what matters and what doesn’t. That way of thinking showed up naturally in how I interacted with AI. The brevity wasn’t about efficiency alone; it came from knowing how to articulate intent clearly and move toward an outcome.</p><p>That clarity is built over time. It comes from doing the work, making decisions, seeing what works and what doesn’t, and learning how to navigate tradeoffs.</p><p>That’s when it really clicked for me: AI doesn’t remove the need for experience — it reveals it. The difference isn’t the tool. It’s the thinking behind it.</p><blockquote>The difference isn’t the tool. It’s the thinking behind it.</blockquote><h3>The System Hasn’t Caught Up</h3><p>When I started to see this pattern, I raised it as a structural concern — not as a training gap, but as a long-term leadership risk. If we’re not developing thinking, we’re not developing leaders.</p><p>The response was slow. Not because people didn’t care, but because most organizations are still operating on an outdated model of growth — one that assumes learning happens naturally over time through exposure. That assumption doesn’t hold in distributed teams supported by AI.</p><p>This mirrors a broader pattern I’ve written about in Adaptive UX — systems that fail to evolve alongside changing behavior eventually break down.</p><p>So we built our own approach.</p><h3>What I Tried to Put in Place</h3><p>When I started to see this pattern, I raised it as a structural concern — not just a training gap, but a long-term leadership risk.</p><p>I pushed for more intentional systems: mentorship pairings, shared learning environments, and structured opportunities for junior team members to learn from more experienced designers. The goal was to recreate, in a distributed setting, the kinds of exposure and growth that used to happen more naturally.</p><p>But those changes didn’t fully materialize at the organizational level.</p><p>That’s not unusual. Most systems aren’t designed to adapt this quickly, especially when performance still appears strong on the surface.</p><p>So I focused on what I could influence directly.</p><p>I leaned into my leaders to create more visibility into their thinking — encouraging walkthroughs, shared context, and more openness in how decisions were made. And personally, I made a point to step back into the work on a regular basis.</p><p>About once a month, I would take on a problem — not to review it or direct it, but to show how I approached it. I’d walk through how I framed the problem, where I focused, how I simplified it, and how I moved efficiently without cutting corners.</p><p>Then I’d get my hands on the mouse, open up Photoshop or Figma, and <em>walk-the-walk</em> in real time. Not describing it — doing it.</p><p>This wasn’t formal training — it was demonstration. And it made a difference.</p><p>It built trust with the team, created a clearer sense of what “good” looked like, and gave people a window into how experienced designers think through problems. In a distributed environment, those moments of visibility became one of the most effective ways to accelerate learning.</p><h3>If Osmosis Is Gone, We Have to Replace It</h3><p>What used to happen passively now has to be designed intentionally.</p><p>That means creating environments where people can see how decisions are made, not just the outcomes. It means encouraging people to explain their thinking, not just deliver results. It means using AI as a tool, but not as a substitute for understanding.</p><p>It also means creating space for productive struggle. Struggle isn’t inefficiency — it’s how people learn to think.</p><figure><img alt="remember, less single-sentence paragraphs. Yep — good catch, and you’re right to hold that line. The idea is strong, so we just need to let it breathe in fuller paragraphs instead of chopping it up. Here’s the revised version — same content, but smoother, more grounded, and aligned with your style: Experience Still Shows Up — Even in AI I had a moment recently that reinforced this for me in a different way. While working through my master’s program, I shared one of my ChatGPT threads with a few" src="https://cdn-images-1.medium.com/max/1024/1*WYv2A1jDiQQFyH1VJGr36w.png" /></figure><h3>Designed Development: Building Learning Into the System</h3><p>If passive learning is no longer happening naturally, then we have to design for it.</p><p>This is what I think of as <strong>Designed Development</strong> — an intentional approach to building learning into how teams operate, rather than hoping it happens over time. It doesn’t require a massive transformation to get started, but it does require focus.</p><p>A few ways to begin:</p><p><strong>Create shared learning environments.</strong><br>Set up small groups where people teach each other, walk through work, and compare approaches. Teaching reinforces understanding.</p><p><strong>Build structured mentorship.</strong><br>Pair junior ICs with senior ICs or emerging managers, and mid-level ICs with directors. This develops both learners and future leaders.</p><p><strong>Invest in learning resources.</strong><br>Provide access to platforms like LinkedIn Learning or Coursera and make their use expected, not optional.</p><p><strong>Make time for learning.</strong><br>If learning only happens after hours, it won’t scale. Dedicate time during the workweek for skill development.</p><p><strong>Recognize and reward growth.</strong><br>Acknowledge learning progress, certifications, and skill development alongside delivery.</p><figure><img alt="Infographic titled “Designed Development” showing five pillars — shared learning, mentorship, learning resources, dedicated learning time, and recognition — representing a system for building skills and leadership." src="https://cdn-images-1.medium.com/max/1024/1*WS-hNWL6VnM67hwyBN0dVg.png" /></figure><h3>The Shift</h3><p>This isn’t complicated, but it does require a mindset change.</p><p><strong>We have to stop treating learning as something separate from work and start treating it as part of how work gets done.</strong> In distributed, AI-assisted teams, if you don’t build learning into the system, it won’t happen consistently — and over time, that gap compounds.</p><h3>This Is a Leadership Problem, Not Just an HR Problem</h3><p>HR plays a role, but this doesn’t get solved through programs alone. It comes down to how leaders show up — whether they narrate their thinking, stay connected to the work, and create opportunities for others to learn, even when it’s less efficient in the moment.</p><p>Without that, the risk is subtle but real: we promote people who deliver, but haven’t fully developed how they think.</p><h3>Where This Goes If We Don’t Address It</h3><p>If we continue optimizing for speed and output without redesigning how people learn, the impact will show up over time. Decision-making slows, confidence under ambiguity drops, and leaders become overly reliant on tools.</p><p>You can’t prompt your way into leadership.</p><h3>The Opportunity</h3><p>AI and distributed work aren’t the problem — but they’ve changed the environment. If we don’t adapt how we develop people, we won’t just accelerate performance — we’ll accelerate the gaps.</p><p>In my previous piece, I argued that AI amplifies organizations. That’s still true, but amplification cuts both ways. If we don’t rethink how we build leaders in this environment, we won’t just move faster — we’ll move faster in the wrong direction.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f2cd98543ab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Good UX Isn’t Just Usable — it’s Legible, Intuitive, and Felt]]></title>
            <link>https://medium.com/@drbaker712805/good-ux-isnt-just-usable-it-s-legible-intuitive-and-felt-c8474eede3aa?source=rss-974522956a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/c8474eede3aa</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-principles]]></category>
            <dc:creator><![CDATA[Danny Baker]]></dc:creator>
            <pubDate>Mon, 30 Mar 2026 18:39:24 GMT</pubDate>
            <atom:updated>2026-03-30T18:46:33.614Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Abstract geometric composition illustrating core visual design principles in UX, including hierarchy, contrast, balance, and rhythm." src="https://cdn-images-1.medium.com/max/1024/1*Q4cT4_gaNV9HSXGnnfv-CA.png" /></figure><h4>Why visual design principles still matter in product design</h4><p>Early in my career on a large ecommerce platform, I saw the same pattern repeat. Every stakeholder wanted their category to take center stage. Each request made sense — revenue targets, promotions, inventory — but together, they created pressure that could overwhelm the experience.</p><p>Now imagine opening a homepage where everything tries to be the most important. The hero packs in multiple messages — promotions, categories, and calls to action layered into the same space. Nothing is broken, but you’re not sure where to look first. In that moment of hesitation, the experience starts to break down.</p><p>Product teams navigate this tension constantly. They balance business priorities with clarity in the user experience. When everything is emphasized, nothing stands out. The interface still functions, but subtle friction begins to build over time.</p><p>In my experience, the difference between a product that works and one that feels effortless comes down to something more fundamental: <strong>good UX isn’t just usable — it’s legible, intuitive, and felt.</strong> Today, tools can generate layouts in seconds. Speed has improved, but clarity hasn’t always kept up.</p><h3>The Principles Behind How UX Feels</h3><p>In product design, teams often focus on flows, systems, experimentation, and scale. These are critical, but they don’t fully explain how an experience feels in the moment. Interfaces feel clear, calm, and trustworthy when designers apply foundational visual design principles.</p><p>These principles aren’t new. Most designers have encountered them. But in a world of design systems, rapid iteration, and AI-assisted creation, teams often assume them instead of applying them intentionally. The result isn’t failure — it’s something more subtle. Experiences work, but they feel slightly off or harder to use than they should.</p><p>As design speed increases, the margin for thoughtful decisions shrinks. Efficiency rises, but clarity can drop if teams aren’t deliberate. These principles don’t exist in isolation — they show up through color, typography, layout, and motion. This is where design moves beyond function and into intention.</p><h3>1. Hierarchy</h3><figure><img alt="UX hierarchy principle showing primary and secondary content areas to guide user attention and prioritize actions." src="https://cdn-images-1.medium.com/max/1024/1*bywlkQO06yyD5AczzJd2uw.png" /></figure><p>Hierarchy creates clarity by showing users what matters most without effort. In product design, users shouldn’t stop to decide where to look or what to do next. The interface should guide them, making primary actions obvious while supporting elements stay in the background.</p><p>When hierarchy works, the experience feels intuitive because attention flows naturally. When it breaks down, users hesitate — even briefly. Over time, those moments compound and make a product feel less efficient and less trustworthy.</p><p>Competing priorities often cause this breakdown. Teams elevate promotions, features, and calls to action at the same time. Everything gets equal emphasis, which creates noise. Instead of being guided, users must decide what matters.</p><p>AI can amplify this issue. It generates layouts quickly but doesn’t determine priority. Without direction, it assigns equal weight to elements. To fix this, teams must actively decide what matters most and design around it. When everything is emphasized, nothing stands out.</p><blockquote><strong><em>Ask yourself:</em></strong><em><br>Where does the user’s attention go first — and is that intentional? Are you clearly prioritizing one primary action, or asking users to decide what matters?</em></blockquote><h3>2. Contrast</h3><figure><img alt="UX contrast principle illustrating how distinct elements improve visibility, readability, and decision-making." src="https://cdn-images-1.medium.com/max/1024/1*FcTg_i_XBJreU6Y9KEYFwQ.png" /></figure><p>Contrast creates distinction and helps users act quickly. It allows them to differentiate elements, understand states, and recognize what’s actionable. In product design, contrast shows up in buttons, typography, color, spacing, and interaction states.</p><p>Most designers understand contrast well, especially because it’s tied to accessibility standards like ADA compliance. But contrast goes beyond compliance. Strong contrast makes interfaces clear and scannable, while weak contrast forces users to work harder.</p><p>Contrast also extends beyond color. Size, weight, and spacing all contribute. Negative space plays a critical role by giving elements room to breathe and reinforcing what matters. When used intentionally, it improves clarity and introduces calm.</p><p>AI-generated layouts often look polished but lack intentional contrast. Elements share similar weight, and layouts feel compressed. Designers can solve this by increasing separation through space, scale, and hierarchy. Contrast isn’t decoration — it’s a functional tool that reduces cognitive load.</p><blockquote><strong><em>Ask yourself:</em></strong><em><br>Do key elements stand apart clearly, or do they blend together? Can users instantly tell what’s actionable without searching?</em></blockquote><h3>3. Balance</h3><figure><img alt="UX balance principle demonstrating stable layout with evenly distributed visual elements to create clarity and trust." src="https://cdn-images-1.medium.com/max/1024/1*SNEdoRGW7GTqabTsdesYYg.png" /></figure><p>Balance creates stability by distributing visual weight across a layout. It influences whether an interface feels calm or chaotic.</p><p>When balance works, the interface feels composed and easy to process. When it doesn’t, something feels off — even if users can’t explain why. That subtle discomfort can reduce trust in the experience.</p><p>AI can assemble layouts quickly, but speed doesn’t guarantee balance. More content rarely improves clarity. Dense layouts often overwhelm users instead.</p><p>Designers should manage spacing and density intentionally. Structure content to support understanding, not volume. Balance ensures users can process information without strain.</p><blockquote><strong><em>Ask yourself:</em></strong><em><br>Does the layout feel calm and stable, or slightly off? Are you adding content to clarify — or just increasing density?</em></blockquote><h3>4. Alignment</h3><figure><img alt="UX design principle of alignment showing structured layout with consistent spacing to improve readability and reduce visual noise." src="https://cdn-images-1.medium.com/max/1024/1*PDTbG3pkwAGjFZsJkG_C0A.png" /></figure><p>Alignment brings order and structure to an interface. It helps users scan content and understand relationships between elements. Consistent alignment creates patterns the brain can process quickly, which reduces effort.</p><p>Even small inconsistencies introduce visual noise. Elements feel disconnected, and users must work harder to interpret the layout.</p><p>AI can position elements efficiently, but it often misses precision. Small misalignments accumulate and create subtle disorder. Designers should enforce alignment deliberately to maintain clarity and confidence.</p><blockquote><strong><em>Ask yourself:</em></strong><em><br>Do elements align consistently across the layout? Are there small inconsistencies that might introduce visual noise or slow scanning?</em></blockquote><h3>5. Repetition</h3><figure><img alt="UX repetition principle using consistent visual patterns to reinforce usability and create intuitive user experiences." src="https://cdn-images-1.medium.com/max/1024/1*HU725mL_S0-go0z1hx6e2Q.png" /></figure><p>Repetition reinforces consistency and helps users recognize patterns. When users understand patterns, they move faster because they don’t need to relearn interactions.</p><p>Design systems support repetition, but only when teams apply them consistently. Without discipline, repetition breaks into variation, which introduces friction.</p><p>AI can generate components quickly, but without a guiding system, similar elements behave differently. Designers should reinforce patterns across screens. Consistency turns familiarity into efficiency.</p><blockquote><strong><em>Ask yourself:</em></strong><em><br>Are patterns consistent across screens, or do similar elements behave differently? Are users learning once — or relearning as they go?</em></blockquote><h3>6. Rhythm</h3><figure><img alt="UX rhythm principle demonstrating structured spacing and layout patterns that guide users smoothly through content." src="https://cdn-images-1.medium.com/max/1024/1*nQJIRXm9Icrv8N8Ouzi3sw.png" /></figure><p>Rhythm creates flow by controlling how content unfolds across an experience. Spacing, grouping, and sequencing shape how users move through an interface.</p><p>When rhythm works, users move naturally from one moment to the next. When it doesn’t, the experience feels abrupt, cluttered, or overwhelming.</p><p>AI can place elements efficiently, but it doesn’t always create a natural cadence. Designers should structure content intentionally and break information into digestible segments. Rhythm ensures experiences feel coherent and easy to follow.</p><blockquote><strong><em>Ask yourself:</em></strong><em><br>Does the content flow naturally from one section to the next? Are you pacing information in a way that feels digestible — or overwhelming?7. Unity</em></blockquote><h3>7. Unity &amp; Harmony</h3><figure><img alt="UX unity principle showing cohesive visual elements that create a consistent and harmonious user experience." src="https://cdn-images-1.medium.com/max/1024/1*ltCeSmu3HOdScDZqDtGmAg.png" /></figure><p>Unity creates cohesion by ensuring all elements work together as a whole. When unity is strong, the experience feels seamless and trustworthy.</p><p>When unity is weak, interfaces feel fragmented. Even if individual components function well, the overall experience feels inconsistent.</p><p>AI-generated interfaces often struggle with unity, especially without a cohesive system. Designers should anchor their work in a unified design system to ensure consistency. Unity transforms parts into a product.</p><blockquote><strong><em>Ask yourself:</em></strong><em><br>Does the experience feel like a cohesive whole, or a collection of parts? Do all elements reinforce the same system and visual langu</em>age?</blockquote><h3>My favorite non-rule: Surprise and Delight</h3><figure><img alt="UX design moment of surprise and delight using playful visual elements to enhance engagement without disrupting flow." src="https://cdn-images-1.medium.com/max/1024/1*OIW5pIieir707puXU9e4TA.png" /></figure><p>Not everything in UX fits into a principle. Some moments create emotional impact through subtle, intentional details like animation or interaction.</p><p>These moments only work when used carefully. Overuse creates distraction, while thoughtful use enhances the experience. Surprise and delight should build on strong fundamentals, not replace them.</p><p>When hierarchy, contrast, and unity are strong, these moments elevate a product from functional to memorable.</p><h3>Try This</h3><p>The next time you use a product, pause and evaluate it with intention. Look at where your attention goes first and whether hierarchy guides you clearly.</p><p>Notice whether elements stand apart or compete. Pay attention to balance, alignment, and consistency across screens. Observe whether content flows naturally or feels dense.</p><p>If something feels off, it usually is. The next step is identifying why and deciding what to change. Over time, this habit sharpens your design judgment.</p><h3>Beyond Tools</h3><p>Today’s tools — design systems, A/B testing, and AI — help teams move faster. But they don’t guarantee clarity or cohesion. They scale output, not judgment.</p><p>As design accelerates, understanding foundational principles becomes more important. Without them, teams produce experiences that function but fail to communicate effectively.</p><p>The advantage isn’t speed. It’s knowing what matters.</p><h3>Closing</h3><p>The best products don’t just work — they feel right. They guide attention, reduce friction, and create clarity from the first interaction.</p><p>This doesn’t happen by accident or through tools alone. It comes from applying foundational design principles with intention.</p><p>Over time, these principles evolve from rules into judgment. Designers learn when to apply them, when to push them, and when to step outside them.</p><blockquote><strong><em>Because mastering design isn’t just about following rules.<br>It’s about knowing when, where, and how to break them — with intention.</em></strong></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c8474eede3aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Breakfast Club of Design Leadership]]></title>
            <link>https://medium.com/@drbaker712805/the-breakfast-club-of-design-leadership-e052b8b38b28?source=rss-974522956a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/e052b8b38b28</guid>
            <category><![CDATA[design-leadership]]></category>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[organizational-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Danny Baker]]></dc:creator>
            <pubDate>Sat, 14 Mar 2026 02:50:51 GMT</pubDate>
            <atom:updated>2026-03-25T00:49:58.532Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Illustration of diverse human silhouettes in different colors representing a range of design leadership perspectives, overlaid with labels such as Craft Advocate, Artist, Operator, Trend Expert, Technologist, Visionary, Systems Expert, User Advocate, and Team Builder under the title “My Breakfast Club.”" src="https://cdn-images-1.medium.com/max/1024/1*sU9jzJyRLCl3EjUNnhAi9g.png" /></figure><h4>Why the strongest design teams aren’t built by hiring the best portfolios — but by hiring the perspectives your team is missing.</h4><blockquote>“You see us as you want to see us… in the simplest terms, with the most convenient definitions.”<br> — <em>The Breakfast Club</em></blockquote><p>In many organizations, hiring designers isn’t very different.</p><p>Candidates are evaluated primarily through their portfolios. Leaders look for strong projects, polished visuals, and evidence of impact. And while those things matter, the evaluation often stops there. A portfolio is an incredibly useful tool for understanding how someone thinks, how they approach problems, and what kind of craft they bring to the table. But portfolios also encourage a very specific kind of hiring decision — one focused almost entirely on the individual.</p><p>What rarely gets asked is a different question:</p><p><strong>How will this person change the shape of the team?</strong></p><p>When I evaluate potential hires, I’m thinking about more than whether they’ve done impressive work. I’m also thinking about how they might augment the group that already exists.</p><p>Are they exceptional with layout and typography?<br>Do they push motion and interaction forward?<br>Are they deeply analytical and comfortable with metrics?<br>Are they strong problem framers who challenge assumptions?</p><p>Most organizations hire based on <strong>individual output</strong>.</p><p>But the strongest design teams are built by thinking about <strong>how people complement one another</strong>.</p><p>A great portfolio tells you what someone has done.<br>It doesn’t necessarily tell you what your team is missing.</p><figure><img alt="Circular diagram showing six colored segments labeled Team Leader, Technologist, Craft Advocate, Trend Expert, Visionary/Innovator, and Team Builder, with a seventh empty segment labeled Systems Thinker, illustrating a missing perspective in a design team." src="https://cdn-images-1.medium.com/max/1024/1*VUhzuMYPLejlr9KuQlHyrg.png" /></figure><h3>Hiring for Talent vs Hiring for Balance</h3><p>When a new design role opens up, the instinct is usually straightforward: find the strongest candidate possible. That sounds reasonable on the surface, but “strong” can mean very different things depending on what a team actually needs.</p><p>One designer might elevate visual craft across the organization. Another might bring clarity to complex systems and information architecture. Another might be exceptional at navigating ambiguity and reframing product problems.</p><p>If you hire five leaders with the same instincts, the team eventually becomes lopsided — not because people aren’t talented, but because the <strong>range of thinking is too narrow</strong>.</p><p>Many teams unintentionally end up with leadership benches that look like this:</p><ul><li>A group of excellent visual designers</li><li>A group of strong product strategists</li><li>A group of operational managers</li></ul><p>All talented. All capable.</p><p>But collectively missing a range of perspectives.</p><p>The best design organizations avoid this trap by thinking about hiring not just as <strong>adding talent</strong>, but as <strong>balancing perspectives</strong>.</p><h3>The Breakfast Club Strategy</h3><p>Over time, I started thinking about building design leadership teams in a way that reminds me of <em>The Breakfast Club</em>.</p><p>In the movie, the characters begin as stereotypes — the brain, the athlete, the rebel. But the point of the story isn’t the labels. It’s what happens when different personalities and perspectives are forced into the same room.</p><p>They challenge each other.<br>They expose blind spots.<br>They learn from one another.</p><p>That dynamic is exactly what strong design leadership teams need.</p><figure><img alt="Team of multiethnical diverse business people, two men and two women, standing in modern office, discussing and working together, using laptop and tablet. Business and digital" src="https://cdn-images-1.medium.com/max/1024/1*QRMz7DdXDjKWf-1w4rZqTg.png" /></figure><p>Instead of hiring managers who all think alike, I try to assemble a group with <strong>different instincts and disciplines</strong>. Not just different personalities, but different lenses through which they see the work.</p><h3>The Perspectives That Shape a Strong Team</h3><p>Every leadership team benefits from a range of perspectives around the table. These aren’t rigid roles, but they help illustrate the kinds of instincts that strengthen a design organization.</p><p>For example:</p><figure><img alt="Infographic presenting six complementary roles in a design leadership team: The Technologist (focused on emerging tools and experimentation), The Craft Advocate (focused on design quality and detail), The Systems Thinker (focused on complexity and scalable solutions), The Operator (focused on delivery and coordination), The Visionary (focused on innovation and future direction), and The Team Builder (focused on mentoring and team growth). Each role includes example questions that guide their per" src="https://cdn-images-1.medium.com/max/1024/1*ddUuJSADKYSqAzbe_uNZjg.png" /></figure><h3>One Important Clarification</h3><p>Of course, no one is just one thing.</p><p>Strong design leaders are usually capable across multiple areas. A technologist may also care deeply about craft. A systems thinker might be a phenomenal mentor. An operational leader may be excellent at recognizing talent and developing people.</p><p>Most experienced leaders bring <strong>a blend of these capabilities</strong>.</p><p>What you’re really identifying when hiring is <strong>where someone’s strongest instinct lives</strong>, and whether that instinct is something your team currently needs.</p><p>Everything else they bring with them is a bonus.</p><p>Or, to keep the breakfast theme going just briefly:</p><p>The strength you hire for is the <strong>coffee</strong>. Everything else they bring with it is the <strong>syrup on the pancakes</strong>.</p><h3>These Aren’t Fixed Categories</h3><p>It’s also important to say that these aren’t rigid classifications. They aren’t personality types, and they certainly aren’t boxes people get stuck in.</p><p>They’re simply a way of thinking about the kinds of <strong>perspectives that might be missing from a team at a given moment</strong>.</p><p>In one organization, the biggest need might be a technologist pushing experimentation and new tools. In another, it might be someone with strong operational instincts who can help a growing design team deliver consistently. In another environment entirely, the team may benefit most from an entrepreneurial leader who thrives in ambiguity and can help define entirely new products.</p><p>Sometimes the table needs:</p><ul><li>An artist</li><li>An entrepreneur</li><li>A systems architect</li><li>A trend expert</li><li>User Advocate</li></ul><p>The mix should evolve as the organization and needs evolve.</p><p>The goal isn’t to fill predefined roles. The goal is to <strong>notice what your team is missing and hire deliberately to bring that perspective into the room</strong>.</p><figure><img alt="Handwritten checklist on a notepad titled “Candidate Evaluation” resting on a desk, with boxes checked for portfolio quality, past companies or brands, process maturity, and communication and storytelling, while “A Systems Thinker” remains unchecked with a note stating the team needs someone who loves complexity and patterns." src="https://cdn-images-1.medium.com/max/1024/1*w1-MVi9MrfOh3LNFWn_tLw.png" /></figure><h3>Why Most Companies Don’t Hire This Way</h3><p>If this approach sounds obvious, it raises a natural question:</p><p>Why don’t more organizations build teams this way?</p><p>The answer is simple. Most hiring processes are optimized for <strong>individual evaluation</strong>, not <strong>team composition</strong>.</p><p>Hiring panels tend to focus on signals like:</p><ul><li>Portfolio quality</li><li>Past companies or brands</li><li>Process maturity</li><li>Communication and storytelling</li></ul><p>All of which are useful signals.</p><p>But they don’t necessarily reveal the one thing that matters most when building a leadership bench:</p><p><strong>What perspective will this person add to the room that isn’t already there?</strong></p><p>Another subtle dynamic often appears as well. Leaders frequently hire people who resemble <strong>successful versions of themselves</strong>. It’s natural — we trust instincts and approaches that feel familiar.</p><p>But over time that tendency can produce teams where everyone thinks similarly, approaches problems the same way, and prioritizes the same aspects of design.</p><p>When that happens, blind spots grow quietly.</p><p>The best design organizations recognize that hiring isn’t just about bringing in great individuals. It’s about shaping the <strong>collective intelligence of the team</strong>.</p><h3>The Power of Different Perspectives</h3><p>When a leadership team is composed intentionally, something interesting happens in the room.</p><p>Different instincts surface during decision-making:</p><ul><li>Someone asks what’s technically possible</li><li>Someone pushes for stronger craft</li><li>Someone considers the broader ecosystem</li><li>Someone focuses on delivery and timelines</li></ul><p>Each perspective challenges the others in productive ways. The conversations become richer. Blind spots surface earlier. And the result is almost always better decisions.</p><p>But something else happens over time.</p><p>People begin to <strong>learn from one another</strong>.</p><p>The technologist starts to think more about craft. The operator develops a stronger sense of systems. The visionary becomes more grounded in delivery realities. The craft advocate begins to appreciate technical constraints and opportunities.</p><p>No one stays confined to their starting strengths. Instead, the team becomes an environment where people expand their thinking, sharpen their instincts, and grow beyond their individual specialties.</p><p>And that’s when a leadership team stops being a collection of individuals and starts functioning as something more dynamic — a group of people who challenge, support, and elevate one another’s perspective.</p><p>Like the characters in <em>The Breakfast Club</em>, the most effective teams aren’t defined by a single label. <strong>They’re defined by what happens when different ways of thinking come together around the same table.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e052b8b38b28" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Intent Meets Opportunity]]></title>
            <link>https://medium.com/@drbaker712805/when-intent-meets-opportunity-cefe67b75c26?source=rss-974522956a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/cefe67b75c26</guid>
            <category><![CDATA[career-paths]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[getting-promoted]]></category>
            <category><![CDATA[design-leadership]]></category>
            <category><![CDATA[career-path-planning]]></category>
            <dc:creator><![CDATA[Danny Baker]]></dc:creator>
            <pubDate>Wed, 25 Feb 2026 21:14:27 GMT</pubDate>
            <atom:updated>2026-02-25T21:14:27.766Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Navigating career paths in business growth urban landscape digital art futuristic atmosphere inspirational viewpoint personal development" src="https://cdn-images-1.medium.com/max/680/1*HM81tjj8-VNLcZDKcNMX6g.png" /></figure><h4>Careers aren’t assigned — they’re designed.</h4><p>Years ago, during an all-hands meeting, a department leader said something that has stayed with me:</p><blockquote>“Your career path is up to you. Not me. Not your manager. You.”</blockquote><p>It wasn’t dramatic, but it was clarifying.</p><p>Careers don’t unfold automatically. They aren’t distributed based on tenure, loyalty, or good intentions. They move when clarity meets contribution — when intent becomes visible and aligns with real opportunity.</p><p>That moment didn’t change how I approached my own growth — I’ve always believed ownership matters — but it sharpened how I led others. The professionals who progress aren’t the ones waiting to be chosen. They’re the ones designing their path.</p><p>Inside any organization, growth tends to happen at the intersection of three forces:</p><ul><li><strong>Individual intent</strong> — what you want</li><li><strong>Team need</strong> — what the organization requires</li><li><strong>Structural reality</strong> — what the business can support</li></ul><figure><img alt="Triangle diagram showing “Promotion/Growth” at the center, with three surrounding factors labeled Individual Intent, Team Need, and Structural Reality, illustrating that career advancement happens at their intersection." src="https://cdn-images-1.medium.com/max/680/1*QWwBRMJr8OFB-kDZ7zzvfw.png" /></figure><p>When those align, momentum follows. When they don’t, frustration builds.</p><p>Alignment doesn’t happen by accident.</p><p><strong>It starts with ownership.</strong></p><p>Many early-career professionals assume that if they work hard and stay long enough, progression naturally follows. Hard work matters. But tenure alone doesn’t create a trajectory. Promotions are business decisions — based on need, value, and timing.</p><figure><img alt="Two-column graphic titled “Tenure Doesn’t Guarantee Trajectory,” contrasting Time Served with calendar and upward arrows against Value Created with icons for mentorship, system improvement, and skill expansion." src="https://cdn-images-1.medium.com/max/680/1*BhLdHqdB4q3RFVFRAWTe7Q.png" /></figure><p>When leaders discuss advancement, the questions aren’t “Has it been long enough?” They’re more practical: Does the team need this capability? Will this person elevate performance at the next level? Is there an approved headcount? Will their growth strengthen the organization?</p><p>Those are structural questions.</p><p>One of the biggest disconnects I saw as a leader wasn’t lack of talent. It was a lack of clarity. Team members would quietly hope to move into management, strategy, or a new discipline — but never clearly state that intention. If leaders don’t know where someone wants to go, it’s difficult to help them get there.</p><p>That’s where Individual Development Plans came in.</p><p>When IDPs were first introduced to me, they felt like compliance documents — a template to complete and file away. The structure existed, but ownership didn’t.</p><p>So I redesigned mine.</p><p>Before asking my team to create one, I built my own as an infographic instead of a form. I incorporated my Myers-Briggs profile (INFJ) and mapped out who I am at my core. On one side, my strengths. On the other, my challenges — the tendencies that could limit me if left unchecked. Together, they revealed both opportunity and responsibility.</p><p>At the bottom, instead of listing a future title, I described the kind of impact I wanted to have and the leader I wanted to become.</p><p>Then I printed it and put it on my cubicle wall.</p><p><em>Visible.</em></p><p>It was a quiet signal: this is who I am, this is what I’m working on, and this is where I’m headed.</p><figure><img alt="Photograph of a redesigned Individual Development Plan poster displayed on a cubicle wall, outlining strengths, challenges, and career aspirations, with a Post-it note reading “Working On: Networking, Executive Presence, Leadership.”" src="https://cdn-images-1.medium.com/max/680/1*p_hAe3281-OdRMuAaeoeQg.png" /></figure><p>When the team saw that, development shifted from administrative to intentional. IDPs became design exercises — not about titles, but about value. What strengths should I double down on? What gaps are holding me back? What do I want to be known for contributing?</p><p>Because growth requires more than ambition. It requires contribution.</p><p>A promotion should expand capability — raising the bar, mentoring others, improving systems, increasing clarity. Advancement isn’t simply recognition for past effort; it’s an investment in future impact.</p><p>And then there’s timing.</p><p>Even when someone is ready, structural realities matter. There has to be a role. There has to be budget. There has to be space. Sometimes alignment exists immediately. Sometimes it takes time. Occasionally, the next step isn’t inside the same organization — and that’s okay.</p><p>Understanding that progression depends on alignment — not entitlement — removes much of the quiet resentment that can build. Timing isn’t always personal. Often, it’s logistical.</p><p>Believing careers are self-driven didn’t make me less supportive as a leader. It made me more intentional. My role became clarifying expectations, identifying gaps early, offering stretch opportunities, and having honest conversations about readiness.</p><p>The professionals who advanced most consistently weren’t waiting quietly. They were asking, “I’d like to move into X. What would that require?” That question transforms everything. Now we’re collaborating instead of guessing.</p><blockquote>The professionals who progress aren’t waiting to be chosen. They’re designing their path.</blockquote><p>Managers can guide you. Organizations can support you. Leaders can advocate for you.</p><p>But ownership is yours.</p><p>If you want to grow, start by getting clear:</p><ul><li>What do you want to be known for?</li><li>What strengths should you double down on?</li><li>What gaps are holding you back?</li></ul><p>Say it out loud. Write it down. Make it visible. Ask what it would take. Volunteer for the stretch assignment. Seek the feedback before it’s offered.</p><p><em>Momentum begins the moment your intent becomes tangible.</em></p><p>Careers aren’t assigned. They’re designed. They move when clarity meets contribution — when your ambition aligns with real value for the team. When you stop waiting to be discovered and start building the capability that makes you undeniable.</p><p><strong>And when intent meets opportunity, growth doesn’t feel lucky.</strong></p><p><strong>It feels earned.</strong></p><p><strong>It feels aligned.</strong></p><p>And it feels like forward motion.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cefe67b75c26" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI Is Testing Leadership — and Talent]]></title>
            <link>https://medium.com/@drbaker712805/ai-is-testing-leadership-and-talent-23e8dda5fbda?source=rss-974522956a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/23e8dda5fbda</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Danny Baker]]></dc:creator>
            <pubDate>Sun, 22 Feb 2026 03:29:19 GMT</pubDate>
            <atom:updated>2026-02-22T03:29:19.713Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Hand human finger touch cyborg robot white 3d rendering." src="https://cdn-images-1.medium.com/max/1024/1*59u38aVbq6KE5gwe4zcCbA.jpeg" /></figure><h4>How organizations respond to AI will determine whether it replaces people — or elevates them.</h4><p>Every week there’s a new headline about AI replacing workers. Entire departments “automated.” Creative work “generated.” Knowledge roles “at risk.” The narrative is simple and easy to fear: AI is here to take your job.</p><p>But that framing misses something deeper.</p><p>AI isn’t inherently a replacement engine. It’s a leverage engine. And whether it replaces people or empowers them depends almost entirely on how leaders choose to use it.</p><figure><img alt="Infographic titled “Two Futures of AI” comparing a Replacement Model and an Augmented Model. The Replacement Model lists cutting roles, reducing payroll, short-term efficiency, and lower human input. The Augmented Model highlights removing friction, increasing iteration, expanding creativity, and elevating judgment." src="https://cdn-images-1.medium.com/max/1024/1*ABP2vDo3Ba1aBLlMWnheGg.png" /></figure><h3>The First Time I Saw This Tension</h3><p>I experienced this a few years before ChatGPT became a household name.</p><p>At the time, I was leading a design and marketing team at a disruptive publishing company operating in classic startup mode — where speed, iteration, and revenue timing mattered. In that environment, velocity isn’t a luxury; it’s survival.</p><p>I began experimenting with an early AI-powered tool designed to accelerate content development. It wasn’t flashy, and it didn’t “write books.” What it could do was generate structured outlines, frameworks, and variations far faster than traditional processes allowed.</p><p>I encouraged the broader editorial and outlining teams to explore it. The pushback was immediate.</p><p>The concern was understandable: if this tool can generate outlines, what happens to us?</p><p>The tool wasn’t mandated or rolled out company-wide. The editorial and outlining teams largely chose not to adopt it, though a few experimented quietly. The only group that meaningfully embraced it was the team reporting directly to me. Even then, we used it cautiously — in testing mode, primarily for product detail page content and marketing experimentation.</p><p>What we discovered was revealing.</p><p>Instead of spending weeks building a single structured direction, we could generate multiple variations quickly. Instead of debating hypotheticals, we could test options. Instead of polishing one path endlessly, we could compare ten and refine the strongest.</p><figure><img alt="Infographic comparing workflows. The Traditional Workflow shows a linear process from 2–3 concepts to presentation, revisions, and approval over 4–6 weeks. The AI-Augmented Workflow shows one idea branching into ten rough ideas, followed by rapid testing and refined direction completed in days." src="https://cdn-images-1.medium.com/max/1024/1*TdR_KlRAcfYLR3pssCuR8g.png" /></figure><p>The tool didn’t eliminate creative thinking. It accelerated iteration. It created optionality. It increased leverage.</p><p>But without broader adoption, that leverage remained localized. The organization continued operating at its traditional pace.</p><p>I reflect on that moment often — not with blame, but with curiosity. In a startup, velocity compounds. What happens when iteration accelerates across departments? What happens when experimentation becomes cheaper? What happens when teams can explore twenty pathways instead of one?</p><p>I can’t say wider adoption would have changed the company’s trajectory. But I do know the opportunity to multiply output without multiplying headcount was there. The hesitation wasn’t about capability — it was about fear.</p><p>That experience shaped how I see the AI debate today.</p><h3>The Real Fork in the Road</h3><p>The conversation now is framed around replacement: AI writes. AI designs. AI analyzes. AI automates.</p><p>But the real fork in the road isn’t automation versus humanity. It’s intention.</p><p>Leaders effectively face two paths.</p><figure><img alt="Infographic showing a fork in the road labeled “Adoption Point,” splitting into two paths. One path labeled Cost Reduction lists shrinking payroll, short-term efficiency, and reducing roles. The other path labeled Cognitive Offloading highlights removing friction, creativity and innovation, reinvesting time, and improving work-life balance." src="https://cdn-images-1.medium.com/max/1024/1*n7Srq0WuwlM2ovFotWdIPQ.png" /></figure><p>The first is cost reduction: use AI to shrink payroll, optimize short-term efficiency, and reduce roles wherever possible. Some organizations will take this path.</p><p>The second is cognitive offloading: use AI to remove repetitive, low-leverage work, free people from administrative friction, and reinvest saved time into creativity, strategy, and innovation.</p><p>The difference between these paths isn’t technological. It’s philosophical.</p><h3>This Isn’t Just About Designers</h3><p>I come from design and creative leadership, so I see this clearly there. Designers don’t become more valuable because they push pixels; they become more valuable because they interpret ambiguity, think systemically, and translate human needs into solutions.</p><p>If AI handles repetitive layout production, variant generation, or research synthesis, designers don’t disappear. They rise. They gain more time to solve deeper problems, explore more directions, refine judgment, and collaborate strategically.</p><p>But this shift applies far beyond creative roles.</p><figure><img alt="Side-by-side image of a professional multitasking with phone, laptop, and paperwork appearing overwhelmed, contrasted with a calm professional working thoughtfully at a desk, representing the difference between cognitive overload and focused productivity." src="https://cdn-images-1.medium.com/max/1024/1*H374LBfGhsAs1ht6FasoAw.png" /></figure><p>It applies to operations managers buried in spreadsheets, founders drowning in scheduling logistics, marketers manually pulling reports, analysts formatting decks instead of interpreting insight, and executives triaging email instead of setting direction.</p><p>Imagine AI that reshuffles your calendar based on priority shifts, recommends lunch based on your schedule and diet, drafts routine communications, synthesizes research into clear summaries, or organizes travel intelligently around your preferences.</p><p>Not glamorous. Not dystopian. Just useful.</p><p>We already accept GPS without panic. It didn’t replace drivers; it reduced cognitive load. AI can do the same for knowledge work.</p><h3>The Fear Is Real — But So Is the Risk of Standing Still</h3><p>Resistance to AI is understandable. Concerns about misuse, surveillance, deepfakes, over-automation, erosion of craftsmanship, and loss of control are legitimate. Blind adoption would be irresponsible.</p><p>But so is total resistance.</p><p>Here’s the uncomfortable truth: AI may not replace you. But someone who uses AI well might outpace you.</p><p>We’ve seen this before. Desktop publishing didn’t eliminate designers; it shifted the skill floor. Search engines didn’t eliminate researchers; they redefined speed and expectation. Cloud collaboration didn’t eliminate teams; it reshaped workflow.</p><p>The people who learned the tools expanded their leverage. The people who resisted often plateaued. The pattern isn’t new — only the speed of change is.</p><h3>The Leadership Responsibility</h3><p>This is where leadership matters most.</p><p>If leaders frame AI primarily as a headcount reduction strategy, fear becomes justified. But if they position AI as a productivity amplifier — and deliberately reinvest saved time into innovation and strategic growth — culture shifts.</p><p>People don’t burn out from meaningful work. They burn out from repetitive friction.</p><p>When AI absorbs that friction, meetings become more purposeful, creative cycles shorten, strategy gets more oxygen, and people feel empowered rather than squeezed.</p><p>Leaders control that framing. They also control whether saved time becomes innovation — or simply margin.</p><h3>Repricing Human Value</h3><p>What’s happening isn’t the elimination of human contribution. It’s the repricing of leverage.</p><p>Tasks that once consumed weeks can now consume days. Tasks that required heavy manual labor can now be scaffolded instantly. That doesn’t reduce the need for judgment; it increases its importance.</p><p>Taste matters more when you have twenty options instead of one. Strategy matters more when iteration is cheap. Ethics matter more when automation is powerful. Leadership matters more when velocity accelerates.</p><p>AI doesn’t remove human value. It exposes where human value truly lies.</p><h3>The Choice in Front of Us</h3><p>Narratives are forming: AI as existential threat. AI as job destroyer. AI as dystopian automation machine.</p><p>But there’s another narrative available — AI as infrastructure, assistant, and leverage multiplier.</p><p>The organizations that thrive won’t be the ones that resist AI. Nor will they be the ones that blindly automate everything. They will be the ones that use AI to expand human agency rather than shrink it.</p><p>The future doesn’t belong to AI.</p><p>It belongs to leaders who decide what AI is for.</p><p>And from where I sit — as someone who has led innovative teams, built systems, and watched fear slow momentum — I believe this: <em>the most powerful use of AI isn’t replacing people. It’s relieving them, so they can do the work only humans can do.</em></p><p>In that decision, we aren’t replacing people.</p><p>We’re repricing their leverage.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23e8dda5fbda" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setting the Rules for AI-Powered UX]]></title>
            <link>https://medium.com/@drbaker712805/setting-the-rules-for-ai-powered-ux-8d5eb36ef4a3?source=rss-974522956a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d5eb36ef4a3</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design-leadership]]></category>
            <dc:creator><![CDATA[Danny Baker]]></dc:creator>
            <pubDate>Mon, 19 May 2025 22:45:04 GMT</pubDate>
            <atom:updated>2025-05-20T00:12:48.367Z</atom:updated>
            <content:encoded><![CDATA[<h4>Adaptive UX (part 2): Design Systems That Adapt</h4><h3>Setting the Framework for AI-Powered UX</h3><figure><img alt="A colorful grid of abstract geometric shapes — circles, rounded rectangles, and squares — in bright yellow, blue, pink, orange, and gray, arranged on a dark gray background. The shapes suggest modular components that could be rearranged dynamically." src="https://cdn-images-1.medium.com/max/1024/1*smfBQ6swx0tnulJn24rblA.png" /><figcaption>Thinking in grids, using Atomic Design and categorizing data to inform are great starting points. Image by Danny R. Baker.</figcaption></figure><p>For years, design teams have built systems to help products scale — codifying patterns, components, and tokens so teams could work faster and more consistently across platforms. These systems brought alignment, efficiency, and clarity to growing organizations.</p><p>And it worked — up to a point. But we’re now on the edge of something new. With the rise of AI, growing behavioral data, and increasingly fluid user expectations, the experience layer is beginning to shift. Interfaces that were once fixed outputs may soon adapt dynamically — tuning layouts, content, and interactions in real time based on individual context. <strong>The Nielsen Norman Group refers to this shift as a move toward “generative UIs” — interfaces capable of assembling themselves based on behavioral and contextual inputs, rather than static design templates.</strong> To meet that potential, design systems must evolve. They can no longer function solely as scalable sets of components. They need to become adaptive frameworks: systems infused with design logic, ethical boundaries, and clear intent that guide how AI should behave. Not to manipulate, but to personalize — to serve the specific needs of the user, not just the statistical average.</p><p>As I explored in <a href="https://medium.com/@drbaker712805/designing-for-everyone-not-just-the-average-361686c44365"><em>Designing for Everyone, Not Just the Average</em></a>, the future of UX lies in designing experiences that flex — not based on assumptions, but on behavior, context, and intent. That future won’t be handcrafted at every touchpoint. It will be guided by design systems, and orchestrated by AI — within the rules and boundaries we define.</p><h3>From Scaling Sites to Scaling Experiences</h3><p>Design systems have brought remarkable structure to how we build products — defining reusable components, aligning teams, and streamlining collaboration. But as user journeys become more dynamic, these systems are hitting their limits.</p><p><strong>While today’s design systems excel at scaling production and consistency across teams, most are not equipped to adapt experiences in real time based on user behavior or context.</strong> They govern visual cohesion and enforce standards, but they rarely account for the fluid, situational needs of actual users.</p><p>This is the gap we’re staring down: we have systems that scale <em>what</em> we build, but not <em>how</em> those experiences respond once they’re in the wild. An interface can be pixel-perfect and on-brand — and still fail to resonate with a specific user in a specific moment.</p><p>To bridge that gap, we need to reimagine design systems not just as <strong>tools for building</strong>, but as <strong>strategies for flexing</strong> — infused with logic, variation rules, and decision-making structures that allow experiences to shift based on who’s using them, and how.</p><figure><img alt="A diagram showing interchangeable UI cards adapting based on user context. Arrows connect different modules — some with icons like play, star, and dollar signs — representing behavior-driven variations within a flexible design system." src="https://cdn-images-1.medium.com/max/1024/0*jKFfVRLFBYi3b0zA" /><figcaption>An adaptive design system allows modular components to rearrange or vary based on user behavior, intent, or business logic — without rebuilding from scratch. Image by Danny R. Baker.</figcaption></figure><p>I encountered this tension during a large-scale banner test at Walmart.com. We launched a multivariate experiment with several layout, copy, and CTA variations. One version clearly “won” by overall engagement rate — but other segments of users had responded better to different combinations.</p><p>The problem wasn’t with the test — it was with the system. Our design infrastructure wasn’t built to support <em>multiple high-performing experiences</em>, only to crown a single winner and ship it universally. There was no mechanism for adapting the experience in real time based on what we’d learned about different users. Instead of serving each group more intentionally, we were forced to pick a one-size-fits-most design and discard the rest.</p><p>That moment underscored a gap in the system: we had the <strong>data</strong> to personalize, and even the <strong>content</strong> to vary — but the layout, the structure, the rules of the design system were fixed. It wasn’t built to adapt — it was built to standardize.</p><h3>AI Is the Conductor, Not the Composer</h3><p>As design systems evolve to support more adaptive experiences, a new collaborator enters the picture: AI. With its ability to surface content, adjust layouts, and respond to behavior in real time, it’s tempting to view AI as the new “designer.” But that’s a misunderstanding of its role.</p><p><strong>AI is not here to replace design — it’s here to interpret and execute within the systems we define.</strong> Think of it like a conductor in an orchestra: it adjusts the tempo, brings in different instruments, shifts the energy depending on the audience and mood. But the sheet music — the structure, progression, and emotional cues — that’s all been written in advance.</p><p>Designers provide that sheet music. We define the components, interaction patterns, behavioral rules, and ethical boundaries that guide what AI can and can’t do. Without this scaffolding, AI-led UX risks becoming chaotic, incoherent — or worse, manipulative.</p><p><strong>As Brad Frost notes in his article on AI and design systems, AI can supercharge consistency and scalability — but only when designers set the parameters and intentionally govern how components behave.</strong> Our job isn’t to micromanage every variation. It’s to build frameworks that adapt with integrity — systems that empower AI to personalize responsibly while staying true to our design vision.</p><h3>Designing for Adaptability, Not Just Reuse</h3><p>If AI is going to adjust the experience in real time, the building blocks of that experience need to be designed with <strong>flexibility</strong> in mind. That starts with thinking modularly — not just in terms of visual hierarchy, but in terms of <strong>interchangeable elements, components, and sections</strong> that can respond to user needs, behaviors, or contexts.</p><figure><img alt="Screenshot of the homepage for Brad Frost’s Atomic Design website. On the left is the book cover featuring a large circle with a smaller orbiting circle, symbolizing atomic structure. On the right is a description of the book and its purpose, with buttons labeled “order the e-book” and “read now.”" src="https://cdn-images-1.medium.com/max/1024/0*qQLOYn-t_NjU8p8h" /><figcaption>Homepage of Atomic Design, Brad Frost’s methodology for building modular design systems.</figcaption></figure><p>Atomic Design, a methodology introduced by<a href="https://atomicdesign.bradfrost.com/"> Brad Frost</a>, offers a structured approach to building design systems. It breaks down interfaces into five hierarchical levels: atoms (basic HTML elements like buttons and inputs), molecules (combinations of atoms forming functional components), organisms (complex UI sections), templates (page-level structures), and pages (specific instances of templates with real content). This approach promotes consistency and scalability while allowing for flexibility in design.</p><p>In an adaptive system, these pieces become more than reusable — they become <strong>configurable</strong>. A card might expand with more detail for an engaged user, collapse to just a headline for someone in a hurry, or highlight different CTAs depending on prior behavior. The component doesn’t change <em>visually</em> for variety’s sake — it shifts because the system understands <em>who it’s serving</em> and what’s most helpful in that moment.</p><p>Sometimes, it’s not about the components themselves — it’s about <strong>how they’re arranged</strong>. Product detail pages (PDPs), for example, often include all possible content for every user, even though most people only engage with a fraction of it. The experience could be dramatically improved by reordering or hiding elements based on behavior.</p><figure><img alt="Screenshot of a typical Amazon product page." src="https://cdn-images-1.medium.com/max/800/0*vNA9pIP5ZNBwEkiX" /><figcaption>A typical Amazon product page above ‘the fold’.</figcaption></figure><p>Take Amazon’s PDP. It’s personalized in content, but the structure never changes. I’ve never once clicked “Buy Now,” nor have I bought from other sellers, yet those elements remain ever-present. After years of data, the layout hasn’t adapted. That’s a missed opportunity — not because they lack the components, but because there’s no logic guiding <em>how those components respond to behavior.</em></p><p>These changes aren’t just visual variations. They’re <strong>intent-driven adjustments</strong>, governed by rulesets we define in advance:</p><ul><li>Who is this component for?</li><li>What are the conditions under which it adapts?</li><li>What should never change, even when personalization is in play?</li></ul><p>That’s the real evolution: not just creating components that scale across screens, but <strong>components that flex intelligently within the experience — without breaking consistency or trust</strong>.</p><h3>Guardrails, Not Free-For-Alls: Governing Adaptive Systems</h3><p>Flexibility without governance is chaos. As design systems evolve to support dynamic, behavior-aware experiences, they must also embed structure, constraints, and ethical guidelines. Otherwise, we risk creating interfaces that are inconsistent, manipulative, or impossible to maintain.</p><blockquote>Smashing Magazine reminds us that personalization without clear data boundaries risks alienating users and breaching their trust. Designing responsibly means introducing privacy and consent into the process from the start.</blockquote><p>Design systems already govern visual consistency and accessibility — but an adaptive system must also govern when and how experiences change. That means introducing decision-making frameworks into the design layer, not just the product strategy doc.</p><p>To govern adaptive systems well, we need to define and document:</p><ul><li><strong>What can change?</strong> Content density, module order, visual emphasis, or whether something appears at all.</li><li><strong>When should it change — and why?</strong> Based on user behavior (clicks, scrolls, dwell time), engagement level, device or time-of-day context, or journey stage.</li><li><strong>What must remain consistent?</strong> Brand voice, accessibility standards, legal disclaimers, and user protections.</li></ul><blockquote>NN/g also found that users often don’t understand machine-driven personalization. If they can’t tell why an interface has changed, it erodes trust. Making these systems legible and explainable is part of adaptive design’s ethical responsibility.</blockquote><p>These aren’t decisions design makes alone — they’re <strong>design-led decisions informed by data, strategy, and collaboration.</strong> As designers, we’re not just crafting visuals — we’re helping define the logic behind how a system responds: establishing flexible logic, fallback or alt states, and setting ethical boundaries that guide AI-powered experiences.</p><p>But this work only succeeds within a broader product ecosystem. <strong>Tagging, behavior triggers, and structural adaptability all require buy-in and input from engineering, data, and product partners.</strong> The systems we imagine must be technically feasible, testable, and maintainable at scale.</p><p>When designers, PMs, and engineers align on <em>what adapts, when it adapts, and why,</em> we move beyond scalable design — we create experiences that are <strong>flexible, trustworthy, and intentional.</strong></p><p><strong>This isn’t about slowing down innovation. It’s about ensuring that adaptability doesn’t come at the cost of coherence, brand trust, or user autonomy.</strong></p><h3>The Future of Design Systems Is Adaptive by Design</h3><p>The next generation of design systems won’t just help us build faster — they’ll help us build <strong>smarter</strong>, <strong>more responsively</strong>, and <strong>more responsibly</strong>. These systems will no longer exist solely to enforce consistency across platforms — they’ll serve as frameworks for <strong>real-time, context-aware experiences</strong> that flex to meet users where they are.</p><p>As the Design Systems Collective notes, some organizations are already exploring “autonomous UI” approaches — systems that evolve in real time without human intervention, based on context, AI insights, and behavior.</p><p>As AI becomes more embedded in how we shape and serve digital experiences, our role as designers becomes even more critical. We’re not handing over the wheel — we’re designing the road map, the guardrails, and the rules of the road.</p><p>By architecting systems that are modular, behavior-aware, and ethically governed, we ensure that personalization works <em>for</em> the user, not just for the business.</p><p>This is the moment to evolve our design systems into <strong>living frameworks</strong> — ones that scale, adapt, and serve real people with intention and integrity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d5eb36ef4a3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing for everyone, not just the average]]></title>
            <link>https://uxdesign.cc/designing-for-everyone-not-just-the-average-361686c44365?source=rss-974522956a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/361686c44365</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Danny Baker]]></dc:creator>
            <pubDate>Fri, 16 May 2025 18:03:25 GMT</pubDate>
            <atom:updated>2025-06-29T21:47:12.913Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Designing for everyone, <br>not just the average</strong></h3><figure><img alt="A surreal, dystopian scene featuring identical individuals wearing teal uniforms, lined up in perfect symmetry in a futuristic, sterile hallway. The people, with expressionless faces, appear as clones or members of a uniform society, evoking themes of conformity and control." src="https://cdn-images-1.medium.com/max/1024/0*Sgbnhu9_zytjevup" /><figcaption>When design treats users as identical, experience suffers.</figcaption></figure><p>During my time leading design at a major e-commerce company, one project has stuck with me: a banner test that seemed successful on the surface but ultimately revealed a blind spot in our thinking. That test helped shape my view of how modern digital experiences fall short — not because the design was bad, but because it only served the average user.</p><p>That realization started a deeper inquiry.<em> If we could personalize content, why weren’t we evolving the experience itself?</em></p><p>As a design leader working at the intersection of modular systems, AI, and personalization, I’ve spent years thinking about how to better serve the diversity of real-world behaviors. This article proposes <strong>Adaptive UX</strong> as a way forward — an approach that personalizes not just content, but the experience itself. Adaptive UX leverages behavioral patterns and flexible design systems to serve different users more intentionally, helping us move beyond the limitations of designing for a single, average user journey.</p><p>In this article, I will:</p><ul><li><strong>Reframe Adaptive UX</strong> — originally explored from an engineering lens in early context-aware systems research — as a product design strategy. This evolution builds on peer-reviewed research demonstrating that adaptive UI/UX models can significantly enhance engagement and satisfaction, particularly when behavior-based adaptation is prioritized¹.</li><li><strong>Propose Segmented Adaptive Testing (SAT)</strong> as one effective method for putting it into practice.</li><li><strong>Show how principles from Tesler’s Law and Hick’s Law support this approach.</strong> I will also explore key questions about user consistency and trust, highlight its accessibility implications, and argue why Adaptive UX represents a necessary evolution in inclusive, behaviorally responsive design.</li></ul><h3>The Missed Opportunity Hidden in the Data</h3><p>Let’s revisit the project I mentioned at the top of the article, and what it revealed about how I approached this idea of adaptive user experience design.</p><figure><img alt="The headline says “Multivariate Testing”. Below is an image of 4 product tiles with a fake headline represented as thick horizontal lines. To the top right is an icon of a lamp and centered on the bottom are buttons. The first two buttons say “Add to cart” while the second two say “Buy Now”. Each has a different colored background (blue, yellow, red and green from left to right). The first box has a 5.5% CTR, or click-through rate, the second is 16.4% and the text “WINNER” below in green, the th" src="https://cdn-images-1.medium.com/max/1024/0*Mr06oXIX-Q2DTpuy" /></figure><p>We had launched a multivariate banner test with four combinations of layout, headlines, and CTAs (calls-to-action). The winning variation drove 48% of conversions. But the remaining 52% of users engaged more with “losing” combinations — designs we ultimately discarded. Like many A/B and multivariate tests, success was defined by a single metric: click-through rate (or CTR). But metrics like clicks, conversions, or bounce rates oversimplify user engagement. That moment made it clear: traditional testing methods are optimized for a majority outcome — not to explore or accommodate the diverse ways users engage. While useful, A/B testing often overlooks meaningful insights from so-called ‘losing’ variations².</p><p>At first glance, this seemed like a content decision. We were testing combinations of headlines and images, not the layout itself. But I was accountable for all web experiences — not just the messaging, but how the site functioned and how users engaged with it across different modules. Through our analytics dashboards and conversations with our insights team, I noticed that merchandisers were frequently reordering elements on the page — moving product carousels up, shifting grids down — trying to optimize for engagement.</p><p>What struck me was this: different users were consistently interacting with different sections. Some hovered on lifestyle imagery. Others jumped straight to product tiles, carousels, or navigation links. This wasn’t just a content preference — it pointed to a structural need.</p><p>That’s when it clicked: Why were we forcing a single layout on everyone when behavioral data already told us what different users prioritized? Why did we choose either/or, when we could have offered both, tailored to behavior? We had shared user personas — research-based profiles that represent common user types and behaviors — but they weren’t meaningfully influencing how we applied our insights in design. Instead, we kept defaulting to a winner-takes-all mentality — optimizing for the average rather than leveraging the behavioral signals already in front of us.</p><h3><strong>UX Principles Hidden in Plain Sight</strong></h3><p>Adaptive UX is not just a technical strategy — it’s a deeply human one. By aligning design adaptations with well-established human factors principles, we can create experiences that feel natural, intuitive, and inclusive. This includes:</p><ul><li><strong>Tesler’s Law</strong>: “Every system has inherent complexity. The question is who bears it — the system or the user”³. We were forcing users to wade through irrelevant sections instead of absorbing complexity into the system.</li><li><strong>Hick’s Law</strong>: “The time it takes to make a decision increases with the number and complexity of choices.” We could have surfaced only the most relevant content per user.</li><li><strong>Jakob’s Law</strong>: “Users spend most of their time on other sites, so they prefer your site to work the same way as all the other sites they already know”⁵. But they also expect interfaces to learn and evolve based on usage over time.</li></ul><p>These principles guide how Adaptive UX meets users where they are — both cognitively and behaviorally.</p><p>At the same time, my team and I were personalizing content — product suggestions, emails, banners — but the UX itself remained static. The layout, interaction order, and information hierarchy didn’t adapt. We had the data to differentiate, but our tools, methods, and design strategies weren’t keeping up.</p><p>Adaptive UX is an approach that evolves static digital experiences into modular, behaviorally responsive systems. While adaptive interfaces have existed in research and engineering domains for years — such as context-aware mobile apps or smart home systems that respond to environmental inputs — the role of design has often been secondary. As the Interaction Design Foundation illustrates through examples like adaptive wristwatch interfaces and sensor-driven applications, these systems introduce significant UI complexity — underscoring why designers should be involved from the outset⁶.</p><p>Adaptive UX doesn’t discard traditional UX principles. Instead, it builds on them.</p><ul><li><strong>Tesler’s Law </strong>reminds us that every system contains inherent complexity — it just has to live somewhere. Adaptive UX offloads that complexity from the user to the system — via modular templates, adaptive logic, and rule-based behavior — so that experiences feel tailored, not burdensome.</li><li><strong>Hick’s Law </strong>supports this further by reminding us that the more choices a user faces, the longer it takes to decide⁴. Rather than presenting every feature or module upfront, Adaptive UX surfaces the most relevant ones for a given behavioral profile — streamlining decisions and reducing overwhelm.</li><li><strong>Cognitive Load, </strong>a principle rooted in human factors and featured in the Laws of UX, reinforces these ideas. It emphasizes minimizing extraneous effort so users can focus on tasks that matter⁷. By adapting the interface to reflect observed behavior, we reduce the mental burden and improve usability.</li><li>And <strong>Jakob’s Law</strong> ensures we do this while maintaining consistency with user expectations across platforms⁵.</li></ul><h3><strong>From A/B to SAT: Powering Adaptive UX</strong></h3><p>So how do we actually begin to put Adaptive UX into practice? One answer is through a process I call <strong>Segmented Adaptive Testing or SAT</strong>.</p><p>Segmented Adaptive Testing (SAT) is the engine behind Adaptive UX. Unlike traditional A/B testing, which selects a single best-performing variation, SAT identifies which combinations work best for specific user segments based on behavioral signals such as scroll depth, click patterns, dwell time, module expansions, and engagement order. These are real-time behavioral inputs gathered through heatmaps, analytics, and usage logs — not static user demographics.</p><p>These signals may originate within the product, but they often reflect broader context — where the user came from, what device they’re using, time of day, or what task they’re trying to complete. SAT doesn’t just react to what users click — it infers patterns of behavior that connect to intent, allowing for more contextually relevant experiences. It’s a bridge between interaction and situation.</p><p>SAT systems are dynamic, continuing to learn and refine which experiences work best in near real-time — paving the way for predictive UX.</p><figure><img alt="Grid of eight mobile phone screens displaying FashionGo homepage variations. Each screen features a combination of two headlines (“Shop the Trends” and “Handpicked Just for You”), two call-to-actions (“See What’s New” and “Shop Now”), and two layout structures (grid and stacked imagery). All versions include product cards with pricing and add-to-cart buttons, demonstrating visual variation for A/B and multivariate testing." src="https://cdn-images-1.medium.com/max/1024/0*C0Ok-CGZsIq-C2LF" /></figure><p>This insight is critical. Let’s take an example from <strong>FashionGo</strong>, a fictional but realistic fashion e-commerce site generating over <strong>$1 million</strong> in daily sales. The team runs a test with eight homepage variations — different combinations of headlines, layouts, and CTAs. The top-performing variant drives 38% of total clicks. Based on traditional practice, this “winner” would be rolled out to all users.</p><p>But that means<strong> 62% of user clicks</strong> were captured by other variants — options that would be discarded. If even a portion of those users convert at a lower rate when shown the “winning” design, the business impact adds up. For a site generating $1 million daily, a modest 10% drop in conversion from that 62% could cost<strong> $30,000 per day — over $10 million annually.</strong> SAT would preserve the diversity in behavior, serving the right variation to the right user segment.</p><p>These behavioral signals are far more telling than static demographics. Scroll depth shows where users lose interest. Dwell time reflects curiosity or hesitation. Click patterns and module expansions reveal what truly captures attention. Together, they tell a story of intent — and give us the opportunity to design for it.</p><p>That’s not just good UX — that’s business-critical design strategy.</p><h3><strong>Putting the Pieces Together: The Adaptive UX Framework</strong></h3><p>To help visualize the full process, the diagram below summarizes Adaptive UX in <strong>four key steps</strong>:</p><figure><img alt="The Adaptive UX Flow To visually summarize the Adaptive UX methodology, we can map it across four key steps: Step 1: Behavioral Signals Captured. Identify interaction signal targets such as click patterns, scroll depth, dwell time, etc. Step 2: Adaptive UX Design System. Uses modular componenents designed to flexibly respond to different behaviors. Step 3: Segmented Adaptive Testing (SAT). Segments are formed based on behavior patterns and psychographics, not demographics. Step 4: Dynamically T" src="https://cdn-images-1.medium.com/max/1024/0*_L0z7UVRDjNGRYW7" /></figure><p>Returning to the FashionGo example, users who dwell on imagery and scroll minimally might convert best with a bold, image-led layout and a CTA like “See What’s New.” Users who engage with reviews and product specs respond better to a dense, detail-first layout and a CTA like “Handpicked for You.”</p><p>Adaptive UX supports both — delivered based on behavior.</p><p>To enable this, systems must be modular. Designer Brad Frost, on his website<a href="https://atomicdesign.bradfrost.com/"> <em>atomicdesign.bradfrost.com</em></a>, introduces <strong>Atomic Design</strong> — a methodology for breaking interfaces into reusable building blocks like buttons (atoms), card layouts (molecules), and full-page templates — allow us to create flexible components that can be reordered, emphasized, or suppressed based on behavioral logic9. This builds the foundation for scalable adaptation.</p><h3><strong>Behavioral Archetypes: Adaptive UX in the Wild</strong></h3><p>Not every user interacts with your site the same way. Some skim, some dig deep, and some just want to know what everyone else thinks. So why give them all the exact same layout?</p><p>That’s where behavioral archetypes come in. These aren’t hard-coded personas — they’re recurring engagement patterns that emerge in how users interact with different content types. For example, in the following PDP mockup, one might apply these simplified archetypes to Product Detail Pages (PDPs):</p><ul><li><strong>Visual Browsers</strong> are all about the images. They want big, bold galleries or immersive videos front and center.</li><li><strong>Spec-Checkers</strong> are the comparison shoppers. They scroll straight to size charts, feature tables, or ingredients.</li><li><strong>Social Buyers </strong>trust the crowd. They want reviews, ratings, and trending signals before they even consider a purchase.</li></ul><figure><img alt="Three versions of a product detail page layout tailored to user behavior — one prioritizing images, another emphasizing specs, and the third highlighting reviews and social proof." src="https://cdn-images-1.medium.com/max/1024/0*srSbV_UvqUBLvxUf" /></figure><p>These archetypes are not necessarily dynamic — what shifts is the user’s movement between them, influenced by factors like product category, context, or even time of day. Adaptive UX responds in real time by adjusting structure based on live behavioral signals. The archetypes themselves are grounded in research and analytics and may evolve over time, but they’re designed to provide stable reference points. To make this practical, teams need a shared framework — a common structure, language, and tagging system — to consistently interpret behavior. This allows for scalable personalization that’s both intentional and adaptable, with future opportunities for automation as technology matures.</p><h3><strong>Designing for the Margins</strong></h3><p>Adaptive UX also enhances accessibility. By streamlining interface elements, it reduces visual and cognitive noise. This is especially beneficial to neurodiverse users, users with cognitive impairments, or those relying on screen readers.</p><p>From an inclusion standpoint, it aligns with the principle of designing for the margins. One-size-fits-all often fails those who interact differently. Adaptive UX welcomes variability — what Jon Kolko describes in <em>Well Designed</em> as a “design-led process [that] embraces outliers and the implicit risk associated with celebrating eccentricities.”10 By doing so, we not only support edge cases but improve the experience for everyone.</p><p>And for small teams? Start with giving users control. Allow them to choose between a list view and a carousel. Let them turn off distracting modules. Like e-commerce “shelf” toggles, even minimal choice boosts satisfaction.</p><p>Adaptive UX doesn’t require AI-heavy infrastructure on day one. A simple template with behavior-based layout logic is enough to get started.</p><h3><strong>Addressing the Tough Questions</strong></h3><p>A common critique of adaptive systems is that they erode consistency. Won’t users be confused if layouts change?</p><p>Not if we adhere to <strong>Jakob’s Law⁵</strong>. Core navigation and patterns remain familiar. What changes is emphasis — elements surfaced based on need. This increases user trust by making interfaces feel more responsive over time.</p><p><strong>Cognitive Load Theory⁷</strong> shows that users only process so much at once. By hiding rarely used elements or simplifying pages based on behavior, we reduce friction. A “Compare Sellers” module might collapse for one user and expand for another. That’s not inconsistency — it’s contextual relevance.</p><p>Importantly, Adaptive UX doesn’t replace A/B or multivariate testing. It builds on it. Rather than picking one version to serve all, Adaptive UX takes what worked for different people — and scales it.</p><h3><strong>Five Ways to Start Today</strong></h3><p>If Adaptive UX represents a shift in mindset and methodology, what does that mean for practice?</p><p>The takeaway: Adaptive UX blends foundational human factors with emerging tools to create flexible, responsive systems that serve people — not just patterns.</p><ol><li>Use <strong>Atomic Design</strong> to create flexible component systems</li><li>Prioritize <strong>behavior-based segmentation</strong> — not just demographic targeting, which is already widely practiced</li><li>Audit <strong>A/B and multivariate test results</strong>: which users succeeded with which variants?</li><li>Prototype <strong>flows that rearrange or emphasize content</strong></li><li>Partner with engineers early to<strong> embed variation logic</strong></li></ol><h3><strong>The Future of UX Is Adaptive</strong></h3><p>That early banner test showed me what we were missing. We were optimizing parts — images, headlines, CTAs — but locking users into a rigid structure. We had the tools to personalize content, but not the experience around it.</p><p><strong>Adaptive UX bridges that gap.</strong> It makes the experience itself personal, modular, and intelligent. As UX Magazine puts it, “AI and machine learning are changing the way we design,”⁸ enabling systems to adapt to user behavior — aligning closely with the principles behind Adaptive UX.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/701/1*BvrmPr6U-rz2Vob5d_dXeA.png" /></figure><blockquote><strong>Adaptive UX isn’t just good, inclusive UX. <br>It’s good for the user. It’s good for the business. It’s adaptive.</strong></blockquote><h3><strong>References</strong></h3><ol><li>Liu, Y., Tan, H., Cao, G., &amp; Xu, Y. (2024). Enhancing User Engagement through Adaptive UI/UX Design: A Study on Personalized Mobile App Interfaces. Computer Science &amp; IT Research Journal, 5(8), 1942–1962.<a href="https://www.researchgate.net/publication/383376182"> https://www.researchgate.net/publication/383376182</a></li><li>Nielsen Norman Group. A/B Testing.<a href="https://www.nngroup.com/articles/ab-testing"> https://www.nngroup.com/articles/ab-testing</a></li><li>Tesler, Larry. Adages and Coinages.<a href="https://www.nomodes.com/larry-tesler-consulting/adages-and-coinages"> https://www.nomodes.com/larry-tesler-consulting/adages-and-coinages</a></li><li>Yablonski, Jon. Hick’s Law. Laws of UX.<a href="https://lawsofux.com/"> </a><a href="https://lawsofux.com/hicks-law/">https://lawsofux.com/hicks-law/</a></li><li>Nielsen Norman Group. 10 Usability Heuristics.<a href="https://www.nngroup.com/articles/ten-usability-heuristics"> https://www.nngroup.com/articles/ten-usability-heuristics</a></li><li>Schmidt, Albrecht. Context-Aware Computing: Context Awareness, Context-Aware User Interfaces and Implicit Interaction. The Interaction Design Foundation. <a href="https://www.interaction-design.org/literature/book/the-encyclopedia-of-human-computer-interaction-2nd-ed/context-aware-computing-context-awareness-context-aware-user-interfaces-and-implicit-interaction">https://www.interaction-design.org/literature/book/the-encyclopedia-of-human-computer-interaction-2nd-ed/context-aware-computing-context-awareness-context-aware-user-interfaces-and-implicit-interaction</a></li><li>Interaction Design Foundation. Cognitive Load. <a href="https://www.interaction-design.org/literature/topics/cognitive-load">https://www.interaction-design.org/literature/topics/cognitive-load</a></li><li>UX Magazine. The Future of UX Design.<a href="https://uxmag.com/articles/the-future-of-ux-design-how-ai-and-machine-learning-are-changing-the-way-we-design"> https://uxmag.com/articles/the-future-of-ux-design-how-ai-and-machine-learning-are-changing-the-way-we-design</a></li><li>Frost, B. (n.d.). Atomic Design. Retrieved May 14, 2025, from <a href="https://atomicdesign.bradfrost.com/">https://atomicdesign.bradfrost.com/</a></li><li>Kolko, J. (2014). Well Designed: How to Use Empathy to Create Products People Love. Harvard Business Review Press.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=361686c44365" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/designing-for-everyone-not-just-the-average-361686c44365">Designing for everyone, not just the average</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>