<?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 Jimmy jim Chiu on Medium]]></title>
        <description><![CDATA[Stories by Jimmy jim Chiu on Medium]]></description>
        <link>https://medium.com/@jimmyjimchiu?source=rss-62b3b502386a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*oI1xoywTrAJitFbZwOdLNQ.png</url>
            <title>Stories by Jimmy jim Chiu on Medium</title>
            <link>https://medium.com/@jimmyjimchiu?source=rss-62b3b502386a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 03:59:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jimmyjimchiu/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[I designed and built my own App. It changed how I think about Product Design.]]></title>
            <link>https://medium.com/@jimmyjimchiu/i-designed-and-built-my-own-app-it-changed-how-i-think-about-product-design-4fa433b27442?source=rss-62b3b502386a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4fa433b27442</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[indie-app-development]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Jimmy jim Chiu]]></dc:creator>
            <pubDate>Thu, 03 Sep 2026 21:44:16 GMT</pubDate>
            <atom:updated>2026-09-03T21:44:16.948Z</atom:updated>
            <content:encoded><![CDATA[<h4>What building Colourary taught me about craft, constraints, and actually owning the product</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zGwAQFZtmvapvgAahphCDw.png" /></figure><p>For most of my career, I’ve worked as a designer inside a product team or design team. That usually means there are other people around the work. Product managers, engineers, stakeholders, researchers, delivery people. Even when design owns a problem, you’re still working within a wider system.</p><blockquote><em>Colourary was different!</em></blockquote><p>It was a small app I decided to design and build myself. And that changed the way I thought about product design more than I expected. Not because I suddenly became an engineer, or because building an app alone is somehow more “real” than working in a team.</p><p>It was simply the first time I had nowhere to pass a decision. If something didn’t make sense, I had to decide what to do with it.</p><p>If something was too complicated, I had to simplify it. If an idea was nice but didn’t really belong in the product, I had to let it go. That sounds obvious. But it feels very different when the whole product is sitting in front of you.</p><h3>Figma makes it very easy to be ambitious</h3><p>As designers, we’re quite good at imagining the ideal version of something.</p><p>In Figma, an extra feature is cheap. A new interaction takes a few frames. A different state takes another component. A clever transition might take an afternoon.</p><p>When you’re building the thing yourself, every one of those decisions suddenly has weight.</p><ul><li>That small interaction needs logic.</li><li>That extra option needs states.</li><li>Those states need testing.</li></ul><p>Then you start thinking about what happens when the user does something you didn’t expect. I found myself asking a much simpler question much more often:</p><p><strong>Does Colourary actually need this?</strong></p><p>That became one of the most useful parts of the project. I had to stop treating simplicity as an aesthetic and start treating it as a product decision.</p><h3>AI made me faster, but it didn’t make the decisions easier</h3><p>Obviously, AI played a part in making a solo project like this much more realistic.</p><p>There are things I would previously have needed much more technical help with that I can now explore, troubleshoot and build with AI alongside me.</p><blockquote><strong>That is genuinely exciting.</strong></blockquote><p>But the interesting bit wasn’t how much AI could produce. It was how often I still had to decide whether its answer was any good.</p><p>Sometimes an approach technically worked, but felt unnecessarily complicated. Sometimes the output looked perfectly acceptable, but didn’t feel like Colourary. Sometimes the quickest solution wasn’t the one I wanted the product to live with. And sometimes AI confidently helped me move in completely the wrong direction.</p><p>It reminded me of something I’ve been thinking about recently:</p><blockquote><strong>generation is becoming cheap, but judgement isn’t.</strong></blockquote><p>Being able to ask AI for something is useful. Being able to recognise whether you should use the result is much more important.</p><h3>AI didn’t just speed up production, it changed how I could explore</h3><p>One of the most useful things about building Colourary with AI wasn’t simply doing the same work faster.</p><blockquote>It was being able to explore ideas that I might previously have dismissed because they felt too expensive, too technical or too time-consuming to test.</blockquote><p>I could move from an idea to something working much more quickly. I could ask questions about implementation while I was still designing, try different approaches, test edge cases, rewrite copy, prototype interactions and then change direction without losing days of work.</p><p><strong>That shortened the distance between thinking and making. And for a designer, I think that is where AI gets genuinely interesting.</strong></p><p>Traditionally, there can be quite a large gap between imagining an experience and seeing how it behaves as a real product. AI can compress that gap. You can stay closer to the idea for longer, rather than constantly stopping to translate it into another discipline or waiting for the next stage of delivery.</p><p>It also gave me more freedom to experiment. If trying three approaches takes twenty minutes rather than two days, you’re more willing to try the slightly strange idea instead of immediately choosing the safest one.</p><p>That doesn’t mean AI is doing the creative thinking for me. If anything, it gives me <strong>more room to be creative</strong>, because less of my energy is spent on the mechanics of getting there.</p><p>For designers, I think that is one of AI’s biggest opportunities.</p><blockquote><em>Not replacing the craft.</em></blockquote><blockquote><strong>Accelerating the loop between imagination, judgement and reality.</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8uJ_ESLStyIc9QwyoQ2l6A.png" /><figcaption>Snapshot of the APP’s function</figcaption></figure><h3>Building it made UI craft feel more important, not less</h3><p>There’s a strange assumption around AI that as products become easier to generate, visual and interaction craft somehow matters less.</p><p>My experience with Colourary has been almost the opposite.</p><p>When a machine can give you a reasonable interface very quickly, “reasonable” becomes incredibly easy to achieve. And you start noticing how little separates reasonable from something that actually feels considered.</p><ul><li>A bit of spacing.</li><li>A decision about hierarchy.</li><li>How an element behaves when you touch it.</li><li>Where information appears.</li><li>What you remove.</li></ul><p>None of these things sound dramatic on their own. But together they form the character of a product. That part still required the same design eye I would use in my day job.</p><p>Perhaps more so, because there was no larger design organisation around me to catch the things I missed.</p><h3>But craft wasn’t enough either</h3><p>This was probably the more useful lesson.</p><p>As a designer, it’s very easy to care deeply about the interface. I certainly do. But when you own the whole product, the interface is only one layer of the problem.</p><p>A beautifully designed feature can still be the wrong feature. A better-looking flow can still be too complicated for what the product is trying to do. And something I might happily spend another week refining may make almost no difference to whether somebody finds Colourary useful.</p><p>You start balancing several things at once: what the user needs, what makes the product understandable, what you can realistically build, what you can maintain, and what is actually worth your time.</p><blockquote>There isn’t usually a perfect answer. There is just a decision.</blockquote><p>I think that is one of the biggest differences between <strong>doing design work</strong> and <strong>owning a product decision</strong>.</p><h3>You also become much closer to the consequences</h3><p>Inside a large organisation, there are good reasons for process.</p><p>Design reviews, tickets, acceptance criteria, governance, analytics, roadmaps and they all help teams work together. But they can also put distance between a designer and the final consequence of a decision.</p><p>On a small solo product, that distance disappears.</p><p>If onboarding is confusing, that’s my problem.</p><blockquote>If I make the scope too large, I’m the person who has to build it.</blockquote><blockquote>If the proposition isn’t clear, I can’t ask marketing to solve it later.</blockquote><blockquote>And if something feels wrong, there is no meeting required before I can change it.</blockquote><p>I found that strangely refreshing. It made the relationship between <strong>decision and consequence</strong> much clearer.</p><h3>I understand product teams a little differently now</h3><p>I’m not suggesting every product designer needs to become a developer.</p><p>And building a small independent app is obviously very different from designing a complex service with millions of users, legacy technology and large organisations behind it.</p><p>But I do think there is value in occasionally owning something from one end to the other.</p><p>It changes the questions you ask.</p><p><em>Instead of: Can we design this?</em></p><p><strong><em>you start asking: Should this exist at all?</em></strong></p><p><em>Instead of: What would the ideal experience be?</em></p><p><strong><em>you also ask: What is the smallest version that still feels good?</em></strong></p><p>And instead of thinking about hand-off as the end of the design process, you realise that the product keeps arguing back after the design is supposedly finished.</p><h3>Colourary is still a small project</h3><p>That’s part of what I like about it.</p><p>I didn’t set out to build the next giant design platform. I wanted something small enough that I could design, build, maintain and eventually put in front of real people myself.</p><p>And perhaps that constraint is exactly what made the project useful.</p><p>It forced me to make decisions. AI helped me execute many of them faster.</p><p>My design experience helped me judge the output. But neither removed the responsibility of deciding what Colourary should become.</p><p>That, more than anything technical, is what I’m taking away from the project.</p><blockquote><strong>The closer designers get to actually owning the outcome, the less design feels like producing screens and the more it becomes the continuous act of deciding what is worth making.</strong></blockquote><p><em>If you want to try the result of this experiment for yourself, </em><strong><em>Colourary is now available on the App Store</em></strong><em> a small product shaped by exactly these ideas around craft, judgement and AI-assisted making:</em></p><p><a href="https://apps.apple.com/app/colourary/id6805523236">Colourary App - App Store</a></p><p><em>Written by Jimmy Chiu, Product Designer — Design system &amp; Brand design</em></p><p><em>This article was self-authored and refined with the help of AI tools for clarity and structure.</em></p><p>📍 <em>United Kingdom &amp; Hong Kong | </em><a href="https://jimmyjimchiu.com/"><em>jimmyjimchiu.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4fa433b27442" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product design has a brand problem.]]></title>
            <link>https://medium.com/design-bootcamp/product-design-has-a-brand-problem-98676d762440?source=rss-62b3b502386a------2</link>
            <guid isPermaLink="false">https://medium.com/p/98676d762440</guid>
            <category><![CDATA[branding]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Jimmy jim Chiu]]></dc:creator>
            <pubDate>Tue, 07 Apr 2026 22:27:24 GMT</pubDate>
            <atom:updated>2026-04-18T18:54:30.893Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Why speed, standardisation, and hiring mindsets are quietly disconnecting products from what they stand for</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s9DABQAhUtX3XyhpQtWdxw.png" /></figure><h3>When I moved from brand to product design, something felt off</h3><p>Not immediately. At first, everything made sense.</p><p>User-centred thinking. Data-driven decisions. Industry standards. Accessibility. Scalable systems.</p><p>It was structured. Measurable. Rational.</p><p>But over time, I started to notice something missing.</p><p>Not in the process but in the outcome.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PCDJbtPTgedz96FBqFd4kQ.png" /></figure><h3>Product design is becoming technically correct, but emotionally empty</h3><p>Today, most product teams are highly capable.</p><blockquote>They know how to optimise flows.<br>They run experiments.<br>They follow best practices.<br>They build scalable design systems.</blockquote><p>And all of that matters.</p><p><em>As Steve Jobs once said,</em></p><blockquote><em>“Design is not just what it looks like and feels like. Design is how it works.”</em></blockquote><p>But somewhere along the way, we started to treat “how it works” as the whole definition of design.</p><p>User-centred. Data-driven. Technology-aware. If these are just the basics, then what makes it <em>product</em> design?</p><p>Because designing a product is not just about making things usable. It is about shaping something that reflects what a company stands for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pUJvi36QBPwK0pfQmQaISg.png" /></figure><h3>The missing layer: brand thinking inside product</h3><p>Coming from a brand background, this gap is hard to ignore.</p><p>Brand design is not just about logos or colours. It is about <strong>meaning</strong>, <strong>consistency</strong>, and <strong>feeling</strong>.</p><p><em>As Jeff Bezos put it,</em></p><blockquote><em>“Your brand is what other people say about you when you’re not in the room.”</em></blockquote><p>Brand is what people remember. What they feel. What they trust.</p><p>But in product design, those questions are often secondary or missing entirely.</p><p>We optimise for clarity, efficiency, and conversion. But we rarely design for identity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cTMDpPf6mUfH0jvhJm6LZQ.png" /></figure><h3>Design systems made things consistent but not expressive</h3><p>Modern design systems are powerful.</p><p>They give us tokens, components, and patterns and help teams move faster and stay aligned.</p><p>But most systems focus on structure, not expression.</p><p>They define how things work. But not how things should <em>feel</em>.</p><p><em>As Paul Rand famously said,</em></p><blockquote><em>“Design is the silent ambassador of your brand.”</em></blockquote><p>You can build an entire product using a well-crafted design system and still end up with something that feels <em>generic</em>.</p><p><strong>Consistent, but characterless.</strong></p><h3>We’re hiring for process, not perspective</h3><p>This issue does not start in design files. It might starts much earlier <em>in how we hire.</em></p><p>User-centred, data-driven, industry standard, technology-aware. These have become the default expectations of a product designer.</p><p>And they should be. But they are not what make a product meaningful.</p><p>If you are building an automotive product, you should want designers who genuinely <em>care about cars</em> and <em>how they feel</em>, <em>how they perform</em>, and what makes them <em>exciting</em>.</p><p>If you are designing for healthcare, you should want people who <em>care about people</em>. <em>Empathy</em> should not be something introduced later through a framework. It should already exist in <em>how they see the world</em>.</p><p>Before the methods, before the tools, before the process, there is perspective.</p><p>Without that, product design risks becoming technically correct, but emotionally empty.</p><h3>Speed is replacing meaning</h3><p>There is also a growing obsession with speed. Shipping fast. Getting things live. Proving value quickly.</p><p>And in that process, something often gets left behind is the brand.</p><blockquote>We borrow patterns.<br>We replicate interfaces.<br>We follow what “works” across the industry.</blockquote><p>But not everything that works belongs everywhere.</p><p>Imagine a council website designed like an Ecommence website. Or a healthcare journey that feels like a gambling platform.</p><p>They may perform well on metrics. They may follow best practices and industry standards. But do they feel right?</p><p>Do they feel like <em>that</em> organisation?</p><h3>When everything looks right, nothing feels right</h3><p>This is where product design starts to lose its meaning.</p><p>When everything becomes standardised, interchangeable, and optimised, we stop designing products and start assembling interfaces.</p><p>The result is a growing sameness across digital experiences.</p><blockquote>Everything is usable.<br>Everything is clear.<br>Everything works.</blockquote><p>But very little feels distinct.</p><h3>What needs to change</h3><p>This is not about rejecting best practices, data, or systems. It is about reintroducing what has been left out.</p><ol><li><strong>Bring brand thinking into product design</strong><br>Not as a layer at the end, but as part of how decisions are made.</li><li><strong>Define not just components, but behaviour and tone</strong><br>Design systems should guide how a product expresses itself, not just how it is built.</li><li><strong>Hire for perspective, not just capability</strong><br>Great products are shaped by people who care deeply about what they are designing.</li><li><strong>Reclaim craft as product communication</strong></li></ol><p><em>As Steve Jobs also said,</em></p><blockquote><em>“Deciding what not to do is as important as deciding what to do.”</em></blockquote><p>Details, rhythm, typography, and restraint are not decoration. They are how a product communicates; <em>clearly</em>, <em>intentionally</em>, and <em>consistently</em>.</p><h3>Product design should feel like something</h3><p>Good product design makes things usable.</p><p>Great product design makes things feel like they belong to a <strong>brand</strong>, to a <strong>purpose</strong>, to the people using it.</p><p>We don’t just design flows, screens, or systems. We design what a product feels like.</p><p>And right now, that is the part we are losing.</p><p><em>Written by Jimmy Chiu, Product Designer — Design system &amp; Brand design</em></p><p><em>This article was self-authored and refined with the help of AI tools for clarity and structure.</em></p><p>📍 <em>United Kingdom &amp; Hong Kong | </em><a href="https://jimmyjimchiu.com/"><em>jimmyjimchiu.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98676d762440" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/product-design-has-a-brand-problem-98676d762440">Product design has a brand problem.</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The future designer is not the one who knows AI]]></title>
            <link>https://medium.com/design-bootcamp/the-future-designer-is-not-the-one-who-knows-ai-ae72288cfcf9?source=rss-62b3b502386a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae72288cfcf9</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[generative-ai-tools]]></category>
            <dc:creator><![CDATA[Jimmy jim Chiu]]></dc:creator>
            <pubDate>Sun, 08 Mar 2026 12:59:39 GMT</pubDate>
            <atom:updated>2026-03-08T13:08:21.102Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Future Designer Is Not the One Who Knows AI</h3><h4>It’s the one who knows what good looks like, not just how to generate it</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y5gfjgX1mj_be4xgpZXtZg.png" /></figure><p>AI is rapidly changing how design work gets produced.</p><p>Layouts, visuals, copy, and even entire product flows can now be generated in seconds. What once took hours of manual work can appear almost instantly. For designers working in product teams, this shift raises an obvious question:</p><p><strong>If AI can generate the work, what is the designer’s role?</strong></p><p>The answer may not be what many expect. The future designer may not be defined by how well they use AI tools.</p><p>It will be defined by <strong>how well they decide what deserves to exist</strong>.</p><h3>AI Is Becoming the New “Artworker”</h3><p>In traditional advertising agencies, creative teams often had a clear separation between <strong>creative direction</strong> and <strong>production</strong>.</p><p>Art directors and designers shaped the concept, visual language, and aesthetic direction. Alongside them were artworkers — specialists responsible for preparing final layouts, resizing assets, adjusting typography, and producing deliverables.</p><ul><li>Execution scaled through artworkers.</li><li>Creative judgement stayed with designers.</li></ul><p>AI is beginning to behave in a similar way.</p><p>Today, AI can generate:</p><ul><li>UI layouts</li><li>icons and illustrations</li><li>copy variations</li><li>design explorations</li><li>even early product prototypes</li></ul><p>In other words, <strong>production is no longer the bottleneck</strong>. But generation is not the same as <strong>judgement</strong>.</p><p>Just because something can be generated does not mean it should be shipped.</p><h3>Prompting Is Not the Real Skill</h3><p>Much of the current conversation around AI in design focuses on <strong>prompt engineering</strong>.</p><p>But prompting alone is unlikely to become the defining skill for designers. Two designers can write similar prompts and receive similar outputs. The real difference appears afterwards.</p><p>One designer looks at an AI-generated interface and immediately notices:</p><ul><li>The visual rhythm feels slightly off</li><li>The hierarchy does not guide the eye naturally</li><li>The interaction technically works but feels awkward</li></ul><p>Another designer might accept it as <em>“good enough”</em>.</p><blockquote>AI generates possibilities. Designers decide <strong>which one is actually good</strong>.</blockquote><p>That decision is where <strong>design craft</strong> lives.</p><h3>Dan Koe’s Idea: Agency</h3><p>Writer and entrepreneur <strong>Dan Koe</strong> argues that the most important skill for the future is <strong>agency</strong> — the ability to initiate action, interpret complexity, and make decisions independently.</p><p>In his essay <em>“The Most Important Skill to Learn in the Next 10 Years”</em>, Koe describes agency as the ability to move from simply executing tasks to <strong>directing outcomes</strong>.</p><p>This idea resonates strongly with modern product design. In an AI-assisted workflow, the real value is no longer in producing assets.</p><p>Instead, it lies in:</p><ul><li>framing the problem</li><li>directing the tools</li><li>interpreting signals from users and data</li><li>deciding what direction the product should take</li></ul><blockquote>AI expands what we can produce.</blockquote><blockquote>Agency determines <strong>what we choose to build</strong>.</blockquote><h3>Designers Are Becoming Directors</h3><p>As AI handles more production work, the role of designers increasingly resembles <strong>creative directors or editors</strong> rather than pure makers.</p><p>Instead of crafting every screen manually, designers may spend more time:</p><ul><li>guiding AI generation</li><li>reviewing variations</li><li>refining product interactions</li><li>aligning outputs with the product vision</li></ul><p>Designers become <strong>orchestrators of possibilities</strong>.</p><p>The challenge is no longer making one interface. The challenge is choosing the right one among hundreds. And that requires something machines cannot easily replicate:</p><p><strong>taste</strong>.</p><h3>The Human Skills That Matter in the AI Era</h3><p>Many discussions about the future of work highlight abilities that are not technical skills at all.</p><p>Five capabilities are likely to become more important for designers working alongside AI.</p><h3><strong>Analytical thinking</strong></h3><p>Product designers constantly interpret signals from analytics, user behaviour, and research insights.</p><ul><li>Data tells us <strong>what happened</strong>.</li><li>Designers interpret <strong>why it happened</strong>.</li></ul><p>Understanding user motivations and translating insights into meaningful product improvements remains a human responsibility.</p><h3><strong>Resilience and adaptability</strong></h3><p>Design tools evolve constantly.</p><ul><li>From Sketch to Figma.</li><li>From static screens to design systems.</li><li>From manual workflows to AI-assisted generation.</li></ul><p>The designers who thrive will not be those attached to a specific tool. They will be those who <strong>adapt their thinking quickly</strong>.</p><h3><strong>Leadership or Self PR</strong></h3><p>As AI accelerates execution, designers increasingly influence direction. Leadership in product design does not always mean managing people.</p><p>It means:</p><ul><li>guiding product decisions</li><li>advocating for user experience</li><li>aligning teams around a coherent vision</li></ul><p>Designers who can influence outcomes become far more valuable than those who simply produce assets.</p><h3><strong>Creativity</strong></h3><blockquote>AI recombines patterns from the past. Humans introduce <strong>new perspectives</strong>.</blockquote><p>Creativity in product design is not only about visuals.</p><p>It is the ability to reframe problems and imagine solutions that data alone cannot suggest.</p><h3><strong>Self-awareness</strong></h3><p>Perhaps the most underrated skill.</p><p>Self-awareness allows designers to question their own assumptions and recognise when instinct, system rules, or AI suggestions may be wrong.</p><p>Without it, designers risk blindly trusting either <strong>data or machines</strong>.</p><h3><strong>Taste: The Skill That Cannot Be Automated</strong></h3><p>In an AI-driven design environment, one quality becomes increasingly important:</p><p><strong>taste.</strong></p><p>Taste is the ability to recognise:</p><ul><li>When an interface feels balanced</li><li>When hierarchy flows naturally</li><li>When a product experience feels coherent</li></ul><p>Legendary industrial designer Dieter Rams famously said:</p><blockquote><em>“Good design is as little design as possible.”</em></blockquote><p>Rams’ philosophy emphasised clarity, restraint, and purpose, principles that remain highly relevant in today’s digital products.</p><p>Similarly, Jony Ive often spoke about the importance of <strong>care and intention</strong> in design.</p><p>In a 2013 interview, Ive described great design as the result of people who <em>“care deeply about what they’re making”.</em></p><p>That mindset cannot be automated. AI can generate thousands of design variations.</p><p>But it cannot fully understand <strong>why one feels right</strong>.</p><h3>The Designer as the Final Gate</h3><p>AI can generate ideas and data can reveal patterns; Design systems can enforce consistency.</p><p>But before anything reaches users, someone still needs to ask: <strong>Is this actually good?</strong></p><p>That moment where judgement, taste, context, and responsibility meet — remains the designer’s role.</p><p>AI will transform how design is produced.</p><p>But the future designer will not simply be the one who knows AI. It will be the one who <strong><em>has the agency to decide what deserves to exist</em></strong><em>.</em></p><p><em>Written by Jimmy Chiu, Product &amp; Design System Designer @ Bupa</em></p><p><em>This article was self-authored and refined with the help of AI tools for clarity and structure.</em></p><p>📍 <em>United Kingdom &amp; Hong Kong | </em><a href="https://jimmyjimchiu.com/"><em>jimmyjimchiu.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae72288cfcf9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-future-designer-is-not-the-one-who-knows-ai-ae72288cfcf9">The future designer is not the one who knows AI</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Design Stops Ageing Like Wine]]></title>
            <link>https://medium.com/design-bootcamp/when-design-stops-ageing-like-wine-a4139f3c27de?source=rss-62b3b502386a------2</link>
            <guid isPermaLink="false">https://medium.com/p/a4139f3c27de</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[creative]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Jimmy jim Chiu]]></dc:creator>
            <pubDate>Fri, 06 Mar 2026 21:39:35 GMT</pubDate>
            <atom:updated>2026-04-07T21:47:10.077Z</atom:updated>
            <content:encoded><![CDATA[<h4>What old movies can teach us about modern interfaces, the AI-pattern trap, and the cost of replacing human judgment with systems.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UzYj-ugFlndrsr4hrNm-Zw.jpeg" /></figure><p>Old movies mixed practical effects with CGI. New ones often lean on CGI alone.</p><p><em>One ages like wine; the other ages like milk.</em></p><p>This isn’t happening because technology has regressed; it’s because the <em>role</em> of technology has shifted. CGI once existed to enhance reality; today, it is increasingly used to replace it. This same shift is occurring in web and app design; quietly, efficiently, and at scale.</p><h3>When Tools Supported Intent, Not Replaced It</h3><p>In the era of “wine-like” filmmaking, practical effects were the foundation. Sets had physical weight, props caught real light, and environments obeyed the laws of physics. CGI stepped in only where reality reached its limit. It supported the vision; it didn’t define it.</p><p>Early digital design followed a similar path. Because tools were limited, intent had to be strong. Designers spent more time tailoring components because decisions couldn’t be auto-resolved by a design system or a generative prompt.</p><p>What took longer wasn’t the technology; it was the <strong>design process itself.</strong> That time wasn’t a sign of inefficiency; it was the source of meaning.</p><p><strong><em>Early web and app design followed a similar path.</em></strong></p><p>The technology was limited, yes, but that didn’t make the work “slow” in a technological sense. Networks, devices, and tools were advancing just as aggressively as they are now. What was slower was the <strong>design process itself</strong>. Not because designers lacked efficiency, but because each decision had to be considered, negotiated, and tailored.</p><p><em>There were fewer shortcuts. Fewer presets. Fewer invisible defaults are being decided on your behalf.</em></p><h3>Slower Design Time, Not Slower Technology</h3><p>Technology should advance. Faster frameworks, robust design tokens, and AI assistance are markers of progress. The problem isn’t the speed of the tool; it’s the compression of the thought process.</p><p>Today, defaults and systems often decide before a human even engages. Spacing, hierarchy, and motion patterns are pre-approved by “safe” frameworks. The output is clean, accessible, and perfectly scalable but it is also increasingly anonymous.</p><p><strong><em>Being human doesn’t mean being slow. It means being considered.</em></strong></p><h3>The AI Pattern Problem (and the System Trap)</h3><p>AI is not the sole cause of today’s “homogenised” web; it simply accelerates an existing over-reliance on tech-first thinking.</p><ul><li><strong>AI</strong> generates from precedent (the average).</li><li><strong>Design systems</strong> reward consistency (the rule).</li><li><strong>Technical priorities</strong> optimise for scale (the machine).</li></ul><p>Individually, these are virtues. Together, they flatten design into a narrow corridor of “acceptable” solutions. When rigid systems and AI-driven optimisation dominate, design shifts from <strong>expression to compliance.</strong> Just like a movie overloaded with “floaty” CGI, the problem isn’t the tool, it’s letting the tool become the author. AI simply fills the remaining gaps with the most statistically average answer.</p><h3>When Everything Works, Nothing Is Remembered</h3><p>Modern websites and apps work remarkably well. They are fast, responsive, and reliable. Yet, they rarely surprise us. They rarely linger in the memory.</p><p>That is because <strong>emotional resonance does not scale.</strong> Older digital products felt “alive” because they were specific. They reflected the constraints and quirks of human judgment. You could sense where a designer chose to bend a rule to create a moment of delight. Today, an obsession with “system-first” design removes those moments of choice and with them, the product’s character.</p><h3>Aging Well Is About Judgment, Not Perfection</h3><p>The best films don’t age well because they avoided technology; they age well because the director knew when to stop. Great design works the same way. It requires the wisdom to:</p><ul><li><strong>Break a system rule</strong> when the context demands it.</li><li><strong>Override a default</strong> to create a unique brand voice.</li><li><strong>Add “intentional friction”</strong> where meaning is more important than speed.</li><li><strong>Trade pure efficiency</strong> for emotional clarity.</li></ul><p>AI and modern tooling should enhance our reality, not replace our judgment. They should give designers more space to care, not less.</p><h3>Designing for a Future That Lasts</h3><p>If we want the next generation of digital products to age like wine, we must rebalance authorship.</p><p>The future isn’t about rejecting AI or abandoning systems. It’s about remembering that design is not just a technical output, it is a human act of decision-making.</p><p>Back when CGI-enhanced reality, stories felt grounded. Back when systems supported designers, interfaces felt alive.</p><p><strong>Enhance reality. Not replace it.</strong></p><p><em>Written by Jimmy Chiu, Product Designer — Design system &amp; Brand design</em></p><p><em>This article was self-authored and refined with the help of AI tools for clarity and structure.</em></p><p>📍 <em>United Kingdom &amp; Hong Kong | </em><a href="https://jimmyjimchiu.com/"><em>jimmyjimchiu.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a4139f3c27de" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/when-design-stops-ageing-like-wine-a4139f3c27de">When Design Stops Ageing Like Wine</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing for everyone: Why inclusion is the ultimate measure of good design]]></title>
            <link>https://medium.com/design-bootcamp/designing-for-everyone-why-inclusion-is-the-ultimate-measure-of-good-design-28749ccb73f1?source=rss-62b3b502386a------2</link>
            <guid isPermaLink="false">https://medium.com/p/28749ccb73f1</guid>
            <category><![CDATA[design-philosophy]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[diversity-and-inclusion]]></category>
            <category><![CDATA[inclusive-design]]></category>
            <dc:creator><![CDATA[Jimmy jim Chiu]]></dc:creator>
            <pubDate>Tue, 30 Dec 2025 13:09:32 GMT</pubDate>
            <atom:updated>2025-12-30T15:53:13.065Z</atom:updated>
            <content:encoded><![CDATA[<h4>Moving beyond technical compliance to create a genuine sense of belonging.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9mmsuWEJK2T2QbRIP4EwgQ.png" /></figure><p>We talk a lot about accessibility in digital design: contrast ratios, keyboard navigation, and alt tags. But accessibility alone doesn’t guarantee inclusion.</p><p>You can build a product that is technically accessible and yet still manage to make people feel <em>invisible</em>.</p><p>Inclusive design goes beyond the “checklist” of compliance. It is the practice of designing with human diversity in mind, not just for permanent disabilities, but for the messy, complex reality of people navigating different cultures, contexts, and constraints.</p><h3>What we talk about when we talk about inclusion</h3><p>To design for everyone, we first have to define what that actually means. It is more than just a buzzword; it is a structured methodology.</p><p>The <strong>British Standards Institute</strong> defines inclusive design as:</p><blockquote>“The design of mainstream products and services that are accessible to, and usable by, as many people as reasonably possible without the need for special adaptation or specialised design.”</blockquote><p>This captures the core essence of the craft: designing for difference <strong>from the start</strong>, rather than treating it as an afterthought or a “special version” of the product.</p><p>Similarly, the <strong>University of Cambridge’s Inclusive Design Toolkit</strong> describes it as a process that considers the vast variation in people’s capabilities, needs, and aspirations. It’s about making informed decisions that proactively include as many people as possible, rather than accidentally excluding them through assumptions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sT9YAQgFfXq0qE7RngQ3BA.png" /><figcaption>AI-Generated image</figcaption></figure><h3>Accessibility is a standard; Inclusion is a mindset</h3><p>Accessible design ensures that people <strong>can</strong> use your product. Inclusive design ensures that people <strong>feel represented</strong> by it.</p><ul><li><strong>Accessibility asks:</strong> “Can everyone read this text?”</li><li><strong>Inclusion asks:</strong> “Does everyone feel like this text was written for them?”</li></ul><p>Accessibility is rule-based and measurable by compliance. Inclusion is human-based and measurable by <em>care</em>. One provides the floor; the other reaches for the ceiling. We need both.</p><h3>Inclusion is a branding decision</h3><p>My journey from branding to product design has changed how I see this entirely. I’ve learned that inclusion isn’t actually that different from how we think about a brand’s “positioning.”</p><p>When we build a brand, we ask: <em>Who is this for?</em> Some brands are intentionally “<strong>exclusive</strong>” like luxury goods or specialised tools. Others, like Google or Apple, strive for “<strong>universality</strong>,” aiming to feel intuitive to millions.</p><p>Inclusive design asks a strategic question: <strong>How many people do we want to invite to the table?</strong> When we design only for a narrow “ideal user,” we build barriers by default. When we design with inclusion in mind, we are prioritising reach, adaptability, and long-term trust over short-term convenience.</p><p><em>It isn’t a constraint; it’s a positioning choice.</em></p><h3>Beyond “Purple People”</h3><p>Inclusion isn’t achieved by simply clicking a “diversify” button. As Meg Robichaud from Shopify’s design team famously wrote, <em>“You can’t just draw purple people and call it diversity.”</em> True inclusion isn’t about changing skin tones in an illustration; it’s about representing lived diversity, body shapes, cultural symbols, varied environments, and a range of emotions. It’s the difference between a “token” gesture and an authentic representation.</p><p>People don’t fit neatly into marketing segments; they live complex, changing lives. Designing for that complexity isn’t “scope creep” it’s just good design.</p><h3>Why it matters: the ROI of empathy</h3><p>Inclusive design is not just ethical; it’s practical.</p><ol><li><strong>Empathy Scales:</strong> When you solve for “edge cases,” you often solve for the majority. High contrast helps the low-vision user, but it also helps the person using their phone in bright sunlight.</li><li><strong>Diversity Drives Innovation:</strong> Designing for non-typical scenarios forces us to find better patterns. Voice control, captions, and dark mode all began as accessibility features; now they are everyday essentials.</li><li><strong>Trust is a Design Outcome:</strong> When users feel seen, they stay. Inclusion makes products feel human.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OswHqcP32RigyHYDay7cAw.jpeg" /></figure><h3>How to measure the intangible</h3><p>Inclusion can feel “fluffy” until you make it visible through data. We can evaluate inclusive maturity through these lenses:</p><ul><li><strong>Research Diversity:</strong> Track demographics in usability studies. Are we learning from a broad enough spectrum of users?</li><li><strong>Usability Parity:</strong> Compare success rates between “mainstream” and “edge” users. Is the experience equitable?</li><li><strong>System Coverage:</strong> Measure the percentage of components with accessibility variants, content guidance, and motion alternatives.</li><li><strong>Perceived Inclusion:</strong> Use surveys to ask: <em>“I feel this product considers people like me.”</em> It’s qualitative, but powerful for storytelling.</li></ul><h3>Embedding belonging into the system</h3><p>Inclusive design becomes sustainable only when it is part of your design system’s DNA:</p><ul><li><strong>Foundations:</strong> Colour tokens with multiple contrast variants and accessible typography.</li><li><strong>Components:</strong> Keyboard-friendly and adaptable layouts that handle different languages gracefully.</li><li><strong>Content:</strong> Voice and tone guidelines that reflect empathy and cultural awareness.</li><li><strong>Documentation:</strong> Inclusive principles are written directly into component pages so they are never an afterthought.</li></ul><h3>From accessibility to belonging</h3><p>Inclusive design is not a finish line. It is a persistent habit of questioning. It’s asking <em>“Who might be left out?”</em> in every brief, every review, and every iteration.</p><p>When we design for inclusion, we aren’t just removing barriers. We are expanding the boundaries of where people feel they belong.</p><blockquote><strong>And that is what makes design meaningful.</strong></blockquote><p><em>Written by Jimmy Chiu, Product Designer @ Bupa</em></p><p><em>This article was self-authored and refined with the help of AI tools for clarity and structure.</em></p><p>📍 <em>United Kingdom &amp; Hong Kong | </em><a href="https://jimmyjimchiu.com/"><em>jimmyjimchiu.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=28749ccb73f1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/designing-for-everyone-why-inclusion-is-the-ultimate-measure-of-good-design-28749ccb73f1">Designing for everyone: Why inclusion is the ultimate measure of good design</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why visual design still matters in a product-driven world]]></title>
            <link>https://medium.com/design-bootcamp/why-visual-design-still-matters-in-a-product-driven-world-e15fe19cf808?source=rss-62b3b502386a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e15fe19cf808</guid>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[visual-design]]></category>
            <category><![CDATA[human-centered-design]]></category>
            <dc:creator><![CDATA[Jimmy jim Chiu]]></dc:creator>
            <pubDate>Mon, 15 Dec 2025 12:26:40 GMT</pubDate>
            <atom:updated>2025-12-15T15:52:41.053Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>How product frameworks made us efficient but less imaginative</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FkSE2WaIHjTTmAB9eB8I7A.png" /><figcaption>When Design Starts Thinking Like Code: How modern product frameworks made us efficient but less imaginative</figcaption></figure><p>In today’s product world, much of how we work as designers is built on systems that weren’t originally ours. We sprint, we refine, we deliver in cycles. We align our working style with developers, not creatives.</p><p>Our process diagrams, <em>Agile, Scrum, and Double Diamond</em>, sit in every deck as the universal truth of how design <em>should</em> work. But they’re not sacred texts. They’re <strong>tools</strong>, created to help us structure chaos, not to replace creativity.</p><p>Somewhere along the way, we became <em>users</em> of these frameworks instead of <em>authors</em> of our own process.</p><h3>When design borrows too much from dev</h3><p>Agile and sprint rituals were designed to help developers build software efficiently. But when design adopted them wholesale, we also absorbed their constraints.</p><p>A two-week sprint works beautifully when shipping code but creativity doesn’t move in sprints. It meanders, <strong>explores</strong>, <strong>contradicts</strong>, and sometimes gets lost before finding form.</p><p>Now, design work is often treated like a feature ticket: <strong>define &gt; deliver &gt; validate. </strong>We’ve become used to <strong>ADO boards and Asana tasks</strong> instead of sketchbooks, user journeys instead of emotions, Figma flows instead of raw ideas.</p><p>And while this made us better collaborators, it also made us <strong><em>safer thinkers</em></strong>.</p><h3>I still remember the smell of glue and print</h3><p>Before I moved into product design, my days were filled with brand moodboards, paper cuttings, and typography grids. I remember printing colour swatches late at night, testing paper grain under warm light, or arranging photographs until a story began to emerge.</p><p>Those moments were messy and emotional; every hue, texture, and word told a story. That kind of creative chaos doesn’t exist in a sprint.</p><p>There’s no ticket for <em>intuition.</em></p><p>We’ve replaced <strong>creative</strong> judgment with validation frameworks; <strong>imagination</strong> with iteration.</p><p>The process made us faster but less <em>felt.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q_4qR9kQc3bIuu37Jw4S5g.png" /><figcaption>Photo by <a href="https://unsplash.com/@marvelous?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Marvin Meyer</a> on <a href="https://unsplash.com/photos/printing-papers-on-brown-surface-HN1roKF-DS4?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>The Double Diamond was never meant to be a cage</h3><p>Even our most beloved design framework wasn’t meant to be a checklist.<br>It’s a philosophy of divergence and convergence like <em>a rhythm.</em></p><p>Yet many teams treat it like a project plan, forcing every idea into its four phases like clockwork.</p><blockquote>We forgot that diamonds were supposed to shine differently every time.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qAH2g6CAZ1UDnSIIwwVyrQ.png" /></figure><h3>What we can learn from a chair in Copenhagen</h3><p>Walk into any design store in Copenhagen and you’ll likely find <strong>Hans J. Wegner’s Wishbone Chair (CH24),</strong> a masterpiece of balance and empathy. Designed in 1949, it’s built from fourteen pieces of wood and a hand-woven seat made of 120 meters of paper cord.</p><figure><img alt="Hans J Wegner designed the CH24 Wishbone Chair in 1949" src="https://cdn-images-1.medium.com/max/1024/1*A_qBQM8EeEHJ6pmcf2SQdA.jpeg" /><figcaption><em>Hans J Wegner designed the CH24 Wishbone Chair in 1949</em></figcaption></figure><p>Every curve feels intentional yet natural, shaped not by data but by the designer’s deep understanding of how people <em>sit, rest, and live.</em></p><p>The Wishbone Chair wasn’t born from a sprint or a metrics dashboard. It came from decades of refinement, from the quiet dialogue between hands, tools, and human posture.</p><p>It’s rational in structure but emotional in presence, a living proof that precision and poetry can coexist. That’s what true product design should feel like:</p><blockquote><strong>crafted with reason, elevated by soul.</strong></blockquote><h3>Reclaiming creative ground in a product world</h3><p>This isn’t a call to abandon product thinking, it’s a call to <em>rebalance</em> it.<br>Structure is good; it helps us collaborate, measure, and evolve. But creativity doesn’t thrive under constant deadlines and validation loops. It needs oxygen.</p><p><strong>And especially in the age of AI, when efficiency, automation, and replication are easier than ever, it becomes even more important to design with human emotion.</strong></p><p>It’s what differentiates us, what reminds people that behind every interface there’s intent, empathy, and care.</p><p><em>To design beyond delivery, we can:</em></p><ul><li>Use frameworks as scaffolding, not walls.</li><li>Prototype beyond the backlog, just because an idea doesn’t have an ADO ticket, doesn’t mean it’s not worth exploring.</li><li>Re-introduce play into the process. Sketch, experiment, and build things that might fail.</li><li>Redefine <em>impact</em> to include <strong>emotional</strong> <strong>resonance</strong>, not just metrics.</li></ul><p>Because sometimes, the most meaningful design work doesn’t fit neatly into a sprint.</p><h3>Designers as authors, not followers</h3><p>Working across agencies and now within a product system, I’ve learned that modern design culture has become fluent in tech but less fluent in imagination.</p><p>We know how to align, estimate, and collaborate, but fewer of us talk about wonder, serendipity, or beauty.</p><p>And yet, <em>those are the things that made many of us become designers in the first place</em>. Maybe the next evolution of design isn’t about adopting more frameworks, but about reclaiming our authorship within them.</p><blockquote>To design systems that don’t just <em>deliver </em>but <em>inspire.</em></blockquote><p><em>Written by Jimmy Chiu, Product Designer @ Bupa</em></p><p><em>This article was self-authored and refined with the help of AI tools for clarity and structure.</em></p><p>📍 <em>United Kingdom &amp; Hong Kong | </em><a href="https://jimmyjimchiu.com/"><em>jimmyjimchiu.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e15fe19cf808" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/why-visual-design-still-matters-in-a-product-driven-world-e15fe19cf808">Why visual design still matters in a product-driven world</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When brand style meets design system]]></title>
            <link>https://www.designsystemscollective.com/when-brand-style-meets-design-system-ee8abc638f67?source=rss-62b3b502386a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee8abc638f67</guid>
            <category><![CDATA[designops]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[brand-identity]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Jimmy jim Chiu]]></dc:creator>
            <pubDate>Tue, 28 Oct 2025 20:54:28 GMT</pubDate>
            <atom:updated>2025-10-29T06:24:48.996Z</atom:updated>
            <content:encoded><![CDATA[<h4>Why defining “style” in systems is harder and more important than we think</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Aa9pbWmAFcpxG12ViXZZrw.png" /></figure><p>We often find ourselves asking the same question: <em>Where does the “style” in a </em><strong><em>design system end</em></strong><em>, and where do </em><strong><em>brand guidelines begin</em></strong><em>? </em>It’s a question that quietly sits in every team’s shared design file. And if you’ve ever tried to build or maintain a design system, you probably know the feeling; <em>we all struggle with it.</em></p><h3>The Overlap That Causes Confusion</h3><p>Both brand guidelines and design systems talk about colour, typography, and imagery but they were born for different reasons.</p><ul><li><strong>Brand guidelines</strong> came first. They’re <em>emotional</em>, <em>expressive</em>, and <em>timeless</em>, helping people recognise who we are through campaigns, packaging, photography, and storytelling.</li><li><strong>Design systems</strong> came later. They’re <em>practical</em>, <em>structured</em>, and <em>functional</em>, helping teams deliver consistent, accessible, and scalable digital products.</li></ul><p>As <a href="https://www.smashingmagazine.com/design-systems-book/">Alla Kholmatova</a> explains in <em>Design Systems</em>, a well-built system doesn’t limit creativity, it enables it by providing clarity, shared patterns, and purpose.</p><p>It’s no wonder we often mix the two: <em>they share the same visual DNA, just living in different environments.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JuLJfG3PRBcjRggi_G1Q6Q.png" /></figure><h3>When Style Means Different Things</h3><p>In brand guidelines, <em>style</em> is about <strong>expression</strong>:</p><ul><li>The warmth of a colour palette that tells a story.</li><li>Typography that speaks with a distinct tone.</li><li>Art direction that sets an emotion before a single word is read.</li></ul><p>In a design system, <em>style</em> becomes <strong>execution</strong>:</p><ul><li>Colour tokens, spacing, border radius, and shadows that define structure.</li><li>Typography scales that ensure accessibility and responsiveness.</li><li>Motion and interaction states (hover, focus, disabled) that respond to users, not just aesthetics.</li></ul><p>The same word “<em>style” </em>now means two different things.</p><blockquote>One speaks to the <strong>heart</strong>, the other to the <strong>hands</strong>.</blockquote><p>As Brad Frost describes in <a href="https://atomicdesign.bradfrost.com/chapter-2/"><em>Atomic Design</em></a>, design systems help us turn brand principles and ideas into <strong>tangible, reusable interface patterns</strong>, allowing consistency and scalability without losing identity.</p><h3>The Tension Between Consistency and Expression</h3><p>When done right, the brand sets the emotional foundation, and the system carries it through digital life. That “brand blue” becomes a token like color.primary.600, tested, accessible, and scalable. Typography becomes variable styles that adjust gracefully across devices. Motion shifts from cinematic storytelling to meaningful feedback in micro-interactions.</p><p>As <a href="https://medium.com/eightshapes-llc/a-design-system-isn-t-a-project-it-s-a-product-serving-products-74dcfffef935">Nathan Curtis wrote</a>,</p><blockquote><em>A design system isn’t a project. It’s a product, serving products.</em></blockquote><p>It’s that translation from brand intent to systematic expression that keeps a design system alive and human. That balance of <strong>emotion and logic</strong> is what keeps style meaningful in systems.</p><p>Maybe style isn’t about choosing sides. Maybe it’s about learning to let brand and system coexist in conversation.When the Brand Guideline Is All You Have</p><h3>When the Brand Guideline Is All You Have</h3><p>In traditional brand or advertising agencies, designers rarely have access to a design system because it often doesn’t exist. Their work focuses on storytelling and expression, not on interface scalability or digital behaviour.</p><p>When all you have is the <strong>brand guideline</strong>, it becomes both the brief and the boundary. It defines tone, colour, and emotion, but not the system logic that digital products need.</p><p>As <em>Alina Wheeler</em> explains in <a href="https://amzn.to/4o8bVul"><em>Designing Brand Identity</em></a>,</p><blockquote>Brand identity is tangible and appeals to the senses. You can see it, touch it, hold it, hear it, watch it move. Brand identity fuels recognition, amplifies differentiation, and makes big ideas and meaning accessible.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3XwsJTFrD783OLVJhqUClg.png" /></figure><p>Her definition captures what brand guidelines are built for; to unify visual and verbal elements into a cohesive whole that expresses how an organization wants to be perceived. But they stop short of defining interaction or scalability.</p><p>So when designers apply brand guidelines to digital products, they often translate emotion through instinct rather than structure. That’s where the <strong>design system</strong> steps in; it doesn’t replace the brand, it <strong>extends it</strong>, turning expression into something usable, accessible, and scalable.</p><h3>What I’ve Found: <em>Style in Design Systems vs. Brand Guidelines</em></h3><p>After my recent work auditing our foundation in design system documentation and reflecting on my earlier years in brand and digital agencies, I began to see how differently <em>“style”</em> is treated between the two worlds.</p><p>In branding, <em>style</em> is about emotion and storytelling. It stays holistic, defining how a brand should feel, sound, and behave across touchpoints.</p><blockquote>In my view, brand guidelines should remain focused on emotion and expression and <strong>should not dive too deep</strong> into the practical, digital, or interactive layers that belong to product design.</blockquote><blockquote>In design systems, <em>style</em> becomes <strong>systematic</strong>. It borrows the brand’s essence and intention, but translates them into structured, reusable logic, tokens, roles, rules, and documentation that can scale across products.</blockquote><p>It doesn’t create new styles; instead, it <strong>refers back to the brand</strong>, reinterpreting its personality through accessibility, interaction, and technical precision.</p><p>Here are some of the elements that often appear in <strong>design system style foundations</strong>, but are usually missing or only loosely defined in <strong>traditional brand guidelines</strong>:</p><ul><li><strong>Design Tokens</strong> (colour, typography, spacing, radius, motion, etc.)</li><li><strong>Accessibility Guidelines</strong></li><li><strong>Roles and Contexts</strong></li><li><strong>Interactive States</strong></li><li><strong>Motion Tokens and/or Principles</strong></li><li><strong>Elevation, Spacing &amp; Hierarchy</strong></li><li><strong>Rationale &amp; Decision History</strong></li></ul><p>Through this audit, I learned that <em>style</em> in a design system isn’t a decorative chapter; it’s a <strong>bridge between identity and implementation</strong>. It’s what allows design to stay human and brand-led, while remaining accessible, scalable, and technically robust.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r1x05WcijBOd6jJ3Z0IgMg.png" /></figure><h3>We’re Still Figuring It Out</h3><p>Every company wrestles with this balance, even the big ones.</p><p>Some design systems lean too technical and lose the brand’s warmth. Some brand guidelines stay static, unable to evolve into interactive, living documentation. But that’s the beauty of it, we’re learning to bridge the two worlds. Style isn’t a fixed chapter anymore; it’s a <strong>dialogue</strong> between <em>teams</em>, <em>disciplines</em>, and <em>time</em>.</p><p>As <a href="https://alistapart.com/article/responsive-web-design/">Ethan Marcotte</a>, the pioneer of Responsive Web Design, wrote:</p><blockquote>Rather than tailoring disconnected designs to each of an ever-increasing number of web devices, we can treat them as facets of the same experience.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FGc8o3rvBfDnm3f-R5qB0A.png" /><figcaption>Compare <a href="https://atlassian.design/foundations/typography">Atlassian’s</a> and <a href="https://fluent2.microsoft.design/typography">Microsoft’s Fluent 2</a> design system</figcaption></figure><p>For example, <a href="https://atlassian.design/foundations/typography"><strong>Atlassian’s typography foundation</strong></a> focuses deeply on structure, hierarchy, and implementation. It is clear, consistent, and highly functional, yet a little detached from the brand’s emotional voice.</p><p>In contrast, <a href="https://fluent2.microsoft.design/typography"><strong>Microsoft’s Fluent 2 typography system</strong></a> blends logic with warmth. It explains tokens and accessibility with the same precision, but also speaks about tone, personality, and how colour carries the Microsoft brand across experiences.</p><p>Both approaches are right in their own context; one prioritises clarity, the other connection and together they show how every design system negotiates its own balance between <strong>system thinking and brand feeling</strong>. <strong>Because at the end of the day, style isn’t just about how it looks, it’s about how it lives.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*Ub4mMR41dsu5gCKHsOxEVg.png" /></figure><h4>What About You?</h4><p><em>I’m curious how does your team approach style within your design system?Do you treat it as a static reference, or as something that continuously evolves with your product and brand?</em></p><p><em>Written by Jimmy Chiu, Product Designer @ Bupa</em></p><p><em>This article was self-authored and refined with the help of AI tools for clarity and structure.</em></p><p>📍 <em>United Kingdom &amp; Hong Kong | </em><a href="https://jimmyjimchiu.com/"><em>jimmyjimchiu.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee8abc638f67" width="1" height="1" alt=""><hr><p><a href="https://www.designsystemscollective.com/when-brand-style-meets-design-system-ee8abc638f67">When brand style meets design system</a> was originally published in <a href="https://www.designsystemscollective.com/">Design Systems Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From graphic designer to design system designer]]></title>
            <link>https://medium.com/design-bootcamp/from-graphic-designer-to-system-thinker-300ee063c0f6?source=rss-62b3b502386a------2</link>
            <guid isPermaLink="false">https://medium.com/p/300ee063c0f6</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[career-journey]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Jimmy jim Chiu]]></dc:creator>
            <pubDate>Sat, 25 Oct 2025 10:41:12 GMT</pubDate>
            <atom:updated>2025-10-29T08:43:52.163Z</atom:updated>
            <content:encoded><![CDATA[<h4>My journey behind the interface</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tqmFRIqCXgoupXyETfhWJw.png" /></figure><h3>When Design Was Just About Craft</h3><p>I still remember the satisfaction of perfecting a layout in Photoshop and Illustrator late at night, kerning text, aligning grids, and colour-matching pixels. Back then, design was all about <strong>craft</strong>.</p><p>I started my journey as a <strong>graphic, digital, and brand designer</strong> in Hong Kong, moving through agencies and studios where every project demanded a balance of storytelling and precision.</p><p>Each place had its own rhythm, some fast and chaotic, others more conceptual and detail-driven, but every environment sharpened a different side of me.</p><p>During my time at <strong>McCann (UM)</strong>, I learned how brands adapt their visual language across digital advertising and campaign touchpoints, where consistency meets speed, and design becomes communication. It was a crash course in how brands live and breathe in the real world, and it shaped how I think about translating identity into experience.</p><p>At studios like <strong>TOTAL</strong>, <strong>ipulse</strong>, and <strong>DSIGN Branding</strong>, I learned how to bring visual order to ideas, how craft can transform concepts into emotion. It was there that I worked on projects like <strong>HK YAU</strong>, a brand identity that reminded me why design is as much about <strong>feeling</strong> as it is about <strong>form</strong>.</p><figure><img alt="HK YAU, branding design project" src="https://cdn-images-1.medium.com/max/1024/1*Xm43Njn2hMwDhTsT0S_r4g.png" /><figcaption><a href="https://jimmyjimchiu.com/portfolios/hk-yau/">ipluse design — HK YAU Project</a></figcaption></figure><blockquote>“We don’t stand a chance of advertising with features and benefits and with RAMs and with charts and comparisons.<br>The only chance we have of communicating is with a feeling.” — <em>Steve Jobs</em></blockquote><p><em>Source: </em><a href="https://medium.com/illumination/this-steve-jobs-quote-changed-my-view-on-marketing-e4c961e36d67"><em>This Steve Jobs Quote Changed My View on Marketing</em></a></p><p>The process was almost meditative: refining logo curves, balancing type hierarchy, finding that one perfect proportion that makes a mark feel alive. Through that, I realised <strong>craftsmanship and emotion are inseparable:</strong></p><blockquote>The small details no one notices are often the ones that make people trust a brand instinctively.</blockquote><p>That stage of my career grounded me in <strong>observation and precision, </strong>disciplines I’ve carried into every role since.</p><figure><img alt="Cover image for Craft" src="https://cdn-images-1.medium.com/max/1024/1*_xf0s5M9NoCudFkyvXaNIA.png" /></figure><h3>From Branding to Systems: Seeing Structure Behind the Story</h3><p>As I transitioned into larger-scale projects, my focus shifted from surface beauty to <strong>underlying structure</strong>. When I worked on projects like <strong>Justlink</strong>, one of China’s largest flexible-hose manufacturers, the challenge wasn’t just aesthetics; it was <em>clarity</em>.</p><p>Their existing digital presence was fragmented: outdated visuals, inconsistent information, and a confusing product catalogue. My task was to bring structure to that complexity, to reorganise their <strong>information architecture (IA)</strong>, unify their <strong>brand identity</strong>, and redefine their <strong>digital tone</strong>.</p><figure><img alt="Justlink brand and web IA project" src="https://cdn-images-1.medium.com/max/1024/1*Op-vnStWBDITCRk3l1NoOg.png" /><figcaption><a href="https://jimmyjimchiu.com/portfolios/justlink-largest-flexible-hose-manufacturer-china/">DSIGN — Justlink Project</a></figcaption></figure><p>That project taught me that brand design can be a form of <strong>governance</strong>. By documenting guidelines, setting consistent layout rules, and defining how content and visuals interact, I was essentially building an early version of what we now call a<em> design system</em>.</p><p>It wasn’t about enforcing consistency for its own sake; it was about making communication easier for everyone, from marketing to engineering.</p><figure><img alt="Justlink brand and web IA project" src="https://cdn-images-1.medium.com/max/1024/1*VO6m0ylRIhqj4WPT-VRQYQ.png" /><figcaption><a href="https://jimmyjimchiu.com/portfolios/justlink-largest-flexible-hose-manufacturer-china/">DSIGN — Justlink Project</a></figcaption></figure><p>In hindsight, Justlink was where I first began to think like a <strong>system designer</strong>, even though I was still wearing a brand designer’s hat.</p><blockquote>What I didn’t realise then was that every campaign, website, and identity project was quietly training me to think beyond aesthetics, to design for clarity, not just beauty.</blockquote><p>That project taught me that brand design can be a form of governance, something echoed in <a href="https://bradfrost.com/blog/post/atomic-web-design/"><em>Brad Frost’s Atomic Design</em></a> principles, long before I knew the term “design system.</p><figure><img alt="Cover image for Brand" src="https://cdn-images-1.medium.com/max/1024/1*jM1dBfQfvFP7bjFiYv4fGQ.png" /></figure><h3>Scaling Design: The APAC Experience</h3><p>A few years later, I joined <strong>Samsonite’s APAC eCommerce design team</strong>. This was where my thinking about systems and scalability truly accelerated.</p><p>I worked across 13 countries and multiple brands: <strong>American Tourister</strong>, <strong>TUMI</strong>, <strong>Gregory</strong>, and <strong>Lipault Paris, </strong>designing digital experiences that had to look consistent yet remain flexible for local needs.</p><p>The <strong>American Tourister</strong> website redesign became my defining project there. It wasn’t just about pixels; it was about building a <strong>design framework</strong> that could travel across borders.</p><figure><img alt="Samsonite project for American Tourister" src="https://cdn-images-1.medium.com/max/1024/1*6-rK5fLLim8RfWpGSTiRmg.png" /><figcaption><a href="https://jimmyjimchiu.com/portfolios/american-tourister-website-design/">Samsonite — American Tourister Project</a></figcaption></figure><p>We created reusable UI components, a shared digital design library, and a unified visual language that allowed local designers and developers to adapt layouts without breaking brand cohesion.</p><figure><img alt="Samsonite project for American Tourister" src="https://cdn-images-1.medium.com/max/1024/1*YXaKIRxLDaqUL2Bqjy_t9g.png" /><figcaption><a href="https://jimmyjimchiu.com/portfolios/american-tourister-website-design/">Samsonite — American Tourister Project</a></figcaption></figure><p>That experience showed me how <strong>systematic design thinking can bridge teams, time zones, and cultures</strong>. For the first time, I saw how <em>structure</em> enables <em>creativity</em>.</p><blockquote>When you build a system, you empower others to create confidently within it.</blockquote><p>Working across 13 countries reminded me how powerful a shared system can be. It felt similar to what teams like <a href="https://polaris.shopify.com/"><em>Shopify with Polaris</em></a> or<a href="https://carbondesignsystem.com/"> <em>IBM with Carbon</em></a>, design languages that stay consistent globally while leaving room for local expression.</p><figure><img alt="Cover image for Digital" src="https://cdn-images-1.medium.com/max/1024/1*j21KiEanU18-mp4ISUghmQ.png" /></figure><h3>Designing the System Behind the Experience</h3><p>When I moved to the UK and joined <strong>Bupa</strong>, everything I’d learned, like craft, structure, scalability &amp; converged. As a <strong>Product Designer (UI)</strong>, I now focus on both <strong>user experience</strong> and <strong>design systems</strong>.</p><p>We collaborate with UX researchers, content designers, and engineers to deliver products that meet accessibility standards and feel consistent across every touchpoint.</p><p>Being part of the <strong>Design System squad</strong> changed how I see design entirely.<br>It’s no longer about a single interface; it’s about the <strong>ecosystem</strong> that supports hundreds of them.</p><p>We build more than components; we think about the <strong>connections </strong>between designers, developers, and content teams. Our work spans everything from design tokens and accessibility to workflow governance and documentation.</p><p>And yet, the lessons from my earliest days still guide me:</p><blockquote>The same attention to detail I once gave to logo curves at <strong>HK YAU</strong>, I now give to pixel grids and component spacing. The same structural clarity I sought in <strong>Justlink’s</strong> brand system now applies to how we build and evolve our design language at scale. The system thinking I practised at Samsonite now guides how I scale design across teams and regions.</blockquote><figure><img alt="Cover image for System" src="https://cdn-images-1.medium.com/max/1024/1*7bncX9HBs8Aar1x0P6-VrA.png" /></figure><h3>Looking Back: From Pixels to Ecosystems</h3><p>Every company I worked for added a new layer to how I understand design:</p><ul><li>Craft taught me <strong>emotion</strong> and <strong>discipline</strong>.</li><li>Branding taught me <strong>structure</strong> and <strong>storytelling</strong>.</li><li>Digital product work taught me <strong>scalability</strong> and <strong>governance</strong>.</li></ul><p>Together, they shaped how I design today: <em>Not just with hands, but with systems in mind.</em></p><p>Because at the end of the day, design is not just what we make.</p><blockquote>It’s how we think, connect, and evolve.</blockquote><p><em>Written by Jimmy Chiu, Product Designer @ Bupa “Exploring the intersection between craft, system, and design culture.</em></p><p><em>This article was self-authored and refined with the help of AI tools for clarity and structure.</em></p><p>📍 <em>United Kingdom &amp; Hong Kong | </em><a href="https://jimmyjimchiu.com/"><em>jimmyjimchiu.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=300ee063c0f6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/from-graphic-designer-to-system-thinker-300ee063c0f6">From graphic designer to design system designer</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UI as a Product Operation Ecosystem]]></title>
            <link>https://www.designsystemscollective.com/ui-as-a-product-operation-ecosystem-472ec522411f?source=rss-62b3b502386a------2</link>
            <guid isPermaLink="false">https://medium.com/p/472ec522411f</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[user-interface]]></category>
            <category><![CDATA[designops]]></category>
            <dc:creator><![CDATA[Jimmy jim Chiu]]></dc:creator>
            <pubDate>Fri, 24 Oct 2025 13:49:13 GMT</pubDate>
            <atom:updated>2025-10-26T11:06:14.960Z</atom:updated>
            <content:encoded><![CDATA[<h4>Designing the rhythm that keeps design alive.</h4><figure><img alt="UI as a Product Operation Ecosystem. By Jimmy Chiu" src="https://cdn-images-1.medium.com/max/1020/1*mHW36agiEUkAKW7SsNhqZg.png" /><figcaption>UI as a Product Operation Ecosystem</figcaption></figure><h3>1. Why UI feels stuck?</h3><p>Most of the time, UI is treated as a deliverable, aka the “last mile” of a design process.</p><blockquote><strong>Pixels, spacing, colour, accessibility… done.</strong></blockquote><p>But when the work ends there, we lose something fundamental: <br>UI becomes static. Designers repeat instead of evolving. The system ages quietly. What if we treat UI not as a <em>role</em>, but as a <em>living ecosystem, </em>something that grows, learns, and improves through time?</p><h3>2. Rethinking the role of UI</h3><p>Recently, while learning about the <strong>Product Operation Model (POM)</strong>, something clicked for me. I realised that the same operational mindset that drives great product teams could also transform how we approach UI.</p><p><em>What if UI itself could be treated as a product operation… and it is measurable, self-improving, and alive?</em></p><p>UI isn’t just about the visuals we see. It’s the system that connects discovery, creation, delivery, and learning like a continuous cycle that feeds back into itself. When we start thinking like that, UI stops being a <strong>craft</strong>, and becomes an <strong>operation</strong>.</p><blockquote><strong>UI = a self-sustaining ecosystem that operates through insight, governance, and evolution.</strong></blockquote><p>In other words, UI can (and should) run like a <strong>product operation model. <br></strong>It is measurable, maintainable, and alive.</p><h3>3. The Problem with “UI as a Role”</h3><p>When UI is defined narrowly:</p><ul><li>We focus on <em>outputs</em>, not <strong>outcomes</strong>.</li><li>We repeat similar <em>screens</em>, not solve recurring <strong>problems</strong>.</li><li>We react to <em>tickets</em>, instead of shaping <strong>systems</strong>.</li></ul><p>That’s why so many teams still suffer from inconsistency, handoff friction, duplicated work, and slow improvement cycles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*0TbAhU9bPPXI2INID1D33g.png" /></figure><h3>4. The Shift from Role to Ecosystem</h3><p>Let’s imagine a different picture. <em>A UI ecosystem that behaves like a product:</em></p><ul><li>It has a <strong>foundation</strong> (tokens, components, principles).</li><li>It has an <strong>operation</strong> (governance, workflow, version control).</li><li>It has <strong>insight</strong> (adoption metrics, design quality indicators).</li><li>It has <strong>evolution</strong> (new explorations, experiments, problem-solving loops).</li></ul><p>We don’t “finish” UI anymore. We <em>operate</em> it.</p><h3>5. The UI Operational Ecosystem Model</h3><p>Here’s how I visualise it:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/981/1*tFfgJ7QNK3Sf1vAsQ7YbdA.png" /><figcaption>The UI Operational Ecosystem Model</figcaption></figure><blockquote>The model is built around four layers: Foundation, Operation, Insight, and Evolution. Each layer supports the next and loops back through the Double Diamond process: <strong>Discover → Define → Develop → Deliver → Learn → Discover again.</strong></blockquote><p>The result is a design ecosystem that never stops learning from itself. To understand why this mindset matters, it helps to look at how my own practice evolved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*ELGmV7BEsqj2qrGtej4Lwg.png" /></figure><h3>6. My Journey from Design Craft to System Designer</h3><p>I began as a <strong>graphic designer</strong>, shaping visual identities and telling stories through form and colour. Those early years in <strong>branding</strong> taught me how design influences perception, how composition communicates voice and values.</p><p>As I moved into <strong>digital and web design</strong>, storytelling met new constraints: grids, responsiveness, and accessibility. Design became less about aesthetics, more about <strong>experience</strong>.</p><p>In <strong>product design</strong>, I realised something deeper: UI isn’t just the final layer of design; it’s the <strong>system</strong> that connects identity, usability, and technology.</p><blockquote><em>Every pixel was connected to a </em><strong>decision</strong><em>.<br>Every visual rule was a reflection of </em><strong>brand logic</strong><em>.<br>Every component was part of a </em><strong>living ecosystem</strong><em>.</em></blockquote><p>That shift from craft to systems changed how I see design. I stopped creating artefacts and started <strong>operating in design, </strong>keeping a rhythm between <em>creativity</em> and <em>structure</em>.</p><h4>My Experience Operating a UI Ecosystem</h4><p>Across multiple squads and design systems, I noticed that UI work wasn’t just about delivering pages; it was about <strong>running an operation</strong> that aligns teams and reduces duplication.</p><p>At <strong>Bupa</strong>, I helped evolve our <strong>Design System (Anatomy), </strong>maintaining components while rethinking how UI decisions flow across squads through governance, releases, and feedback loops. That’s when it clicked:</p><blockquote>The true value of UI isn’t in the pixels we create, but in how we <strong>operate</strong> those pixels as a system.</blockquote><p>By treating UI as an operation, we’ve started seeing progress:</p><ul><li>Faster delivery</li><li>More collaboration between design, engineering, and CMS</li><li>More confidence in shared design decisions</li></ul><p>We’re not fully there yet, but it’s evolving as a reflection of how UI can become a <strong>living, learning ecosystem</strong>.</p><p>Recently, I’ve been exploring how <strong>AI</strong> can support this by building <strong>Figma tools</strong> that automate templates or image editing. They remove repetitive work and let designers focus on creativity.</p><blockquote><em>When AI becomes part of the design ecosystem, it doesn’t replace designers it </em>amplifies<em> them.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*t4jU5-Kj98qHWFEAxUJQcw.png" /></figure><h3>7. The Double Diamond as a Living Engine</h3><p>The Double Diamond isn’t just a process. In this model, it’s the <em>engine</em> that keeps the UI ecosystem evolving.</p><ul><li><strong>Discover</strong> → Observe how people use the design system or product</li><li><strong>Define</strong> → Identify friction, duplication, or new design opportunities</li><li><strong>Develop</strong> → Create improvements, patterns, or visual refinements</li><li><strong>Deliver</strong> → Release updates, track metrics, and collect insights</li><li><strong>Repeat</strong> → Feed the data back into discovery again</li></ul><p>It’s a constant dialogue between design, data, and delivery.</p><h3>8. Why This Matters?</h3><p>When UI operates like a product ecosystem:</p><ul><li>Teams design <strong>faster <em>and</em> smarter</strong>.</li><li>Decisions become <strong>evidence-based</strong>, not opinion-based.</li><li>Designers move from reactive to <strong>strategic</strong>.</li><li>UI evolves <strong>with the product</strong>, not behind it.</li></ul><p>It’s not just DesignOps. It’s <strong>UI-as-ProductOps</strong>, a new layer where design becomes operational, measurable, and self-improving.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*WcnWqiC4__BuOuHdFogqOQ.png" /></figure><h3>9. How It Differs from a Design System Designer!?</h3><p>At first glance, this might sound like what a <em>Design System Designer</em> already does: maintaining components, setting up tokens, running governance, and scaling design consistency. But a <strong>UI Operational Ecosystem</strong> goes one step further. <em>In short:</em></p><blockquote>The<strong> Design System Designer</strong> builds the <strong>foundation</strong>.<br>The <strong>UI Ecosystem Designer</strong> keeps it <strong>alive</strong>.</blockquote><p>A design system without an operation model becomes static, like a library that eventually goes out of sync. But when UI is operated as an ecosystem, it continues to evolve with new insights, product needs, and user contexts. It’s the difference between <em>maintaining a library</em> and <em>orchestrating a living system.</em></p><blockquote>In many organisations, the line between a UI Designer and a Design System Designer is starting to blur. While UI Designers focus on product interfaces and DS Designers focus on scalable foundations, the future demands a hybrid mindset, one that can <em>operate</em> between both worlds. That’s where the idea of a <strong>UI Ecosystem Designer</strong> lives.</blockquote><h3>10. Final Thought</h3><p>UI was once about what we <em>see</em>. Now, it’s about how we <em>operate</em>.</p><p>Through my journey from graphic design to product design, from craft to system, I’ve learned that design isn’t just about creating interfaces<br>but about <strong>building ecosystems that move in rhythm</strong> between people, processes, and technology. The future of UI will be powered by this rhythm:</p><blockquote>A seamless collaboration between human intuition, design systems, and intelligent tools. When AI supports that flow automating what slows us down and amplifying what inspires us. UI evolves beyond static visuals into a living, learning operation.</blockquote><blockquote>Together, UX, Product, and System design shape the what and why of a product.<br>The UI Ecosystem adds the how, the rhythm that keeps them all working in harmony.</blockquote><p>That’s the next chapter of design to me, where we no longer just design screens, but <strong>design the rhythm that keeps design alive.</strong></p><p><em>If you’ve been building design systems, running UI governance, or thinking about DesignOps. I’d love to hear your thoughts. How does your team operate UI today as a deliverable or as an ecosystem?</em></p><p><em>Written by Jimmy Chiu, Product Designer @ Bupa</em></p><p><em>This article was self-authored and refined with the help of AI tools for clarity and structure.</em></p><p>📍 <em>United Kingdom &amp; Hong Kong | </em><a href="https://jimmyjimchiu.com/"><em>jimmyjimchiu.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=472ec522411f" width="1" height="1" alt=""><hr><p><a href="https://www.designsystemscollective.com/ui-as-a-product-operation-ecosystem-472ec522411f">UI as a Product Operation Ecosystem</a> was originally published in <a href="https://www.designsystemscollective.com/">Design Systems Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>