<?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[Emplifi Design - Medium]]></title>
        <description><![CDATA[Case studies &amp; ideas about UI design, UX research, everyday office life, and more from Emplifi’s Product Design team. - Medium]]></description>
        <link>https://medium.com/emplifi-design?source=rss----f146767dd08---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Emplifi Design - Medium</title>
            <link>https://medium.com/emplifi-design?source=rss----f146767dd08---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 21:33:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/emplifi-design" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to waste fewer tokens in Cursor]]></title>
            <link>https://medium.com/emplifi-design/how-to-waste-fewer-tokens-in-cursor-f481685c8a05?source=rss----f146767dd08---4</link>
            <guid isPermaLink="false">https://medium.com/p/f481685c8a05</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[design-leadership]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[cursor]]></category>
            <category><![CDATA[ai-tools]]></category>
            <dc:creator><![CDATA[Luděk Černocký]]></dc:creator>
            <pubDate>Mon, 21 Sep 2026 09:36:58 GMT</pubDate>
            <atom:updated>2026-09-21T09:36:58.156Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BidhHLL7Tznh3ZiCyHoXLQ.png" /></figure><p><strong>What I learned managing Cursor usage across my design team.</strong></p><p>AI used to feel unlimited. Open ChatGPT. Ask something. Generate another version. Start over. Who cares.</p><p>Then AI moved from being something we occasionally <em>asked things</em> to something we actually <strong>work with</strong>. That’s a very different scale.</p><p><strong>Most of my design team works in code now.</strong> PRs, MRs, frontend changes, and increasingly contribute directly to production. And we prototype more than ever — although “prototype” is becoming a slightly misleading word. With our own <a href="https://soul.emplifi.io/">Soul Design System</a> MCP, we build 1:1 versions of the actual product in code, using real components.</p><p>We use Cursor a lot. I probably use it more than I should — enough that I even built <a href="https://calando.app/">Calando</a>, a macOS app that reminds me to stop working and take a break. There’s some irony in that.</p><p>And once an entire team starts working this way every day, something else changes too: <strong>AI usage stops feeling unlimited.</strong></p><p>Agents read files, search codebases, call tools, run commands, inspect results, and try again. That’s what makes them so useful — and also why they can consume a surprising number of tokens doing perfectly normal work. Multiply that across a team and suddenly those tokens are a real budget.</p><p>So I started paying attention. I watched our usage, asked people on the team how they actually use Cursor, compared models, looked at what was eating context, and which of our habits were quietly making every request more expensive.</p><p>Basically, I went down the token rabbit hole.</p><p>Not because I wanted everyone counting tokens before pressing Enter. That sounds miserable. I wanted to know whether we could use Cursor just as much while wasting less.</p><p>And somewhere along the way, I realized I’d been looking in the wrong place. The biggest opportunity wasn’t in writing shorter prompts.</p><p><strong>It was in controlling what Cursor reads.</strong></p><h3>You’re probably optimizing the wrong thing</h3><p>We talk <strong><em>a lot</em> </strong>about prompts.</p><p>How to structure them. How long they should be. Which magic words make the model perform better.</p><p>Be concise.</p><p>Use XML.</p><p>Don’t say please. Say please.</p><p>Threaten the model. Promise it $200.</p><p>Whatever this week’s prompting wisdom happens to be.</p><p>But from a token perspective, the prompt you type is often not the interesting part.</p><p>Every Cursor request can also include files, conversation history, Rules, Skills, MCP tool definitions, terminal output, and other context the model needs to process.</p><p>A <a href="https://blog.pragmaticengineer.com/the-pulse-interesting-ai-coding-stats-from-cursor/">Pragmatic Engineer analysis</a> of Cursor’s own aggregated usage data suggests it consumes roughly <strong>10× more input tokens than output tokens</strong> — and that those input tokens account for most of the actual cost.</p><p>That was my little <em>oh</em> moment.</p><p>You can save 20 tokens by removing a sentence while Cursor quietly reads tens of thousands of tokens of context.</p><p>Cool.</p><p>So the question I ask now is much simpler:</p><p><strong>What does the model actually need to see to do this job?</strong></p><p>Once you start looking at Cursor that way, you notice waste everywhere.</p><h3>Start with the invisible stuff: MCP</h3><p>This was probably my easiest win.</p><p>I love MCP.</p><p>Connecting Cursor to Figma still feels slightly magical. And once you discover MCP, there’s a natural tendency to start collecting servers.</p><p>Figma? Obviously.</p><p>Browser? Sure.</p><p>Analytics? Why not.</p><p>Something you tried once three months ago and completely forgot about?</p><p>Apparently also yes.</p><p>Enabled MCP servers expose their tool definitions to the model. Those definitions take up context even when that particular tool isn’t what you’re working with.</p><p>I haven’t run a controlled experiment to measure exactly how much disabling them saves me. But once I understood they were quietly riding along in the context, keeping every server enabled all the time stopped making much sense.</p><p>I had been treating MCP servers like Chrome extensions. Install them and forget about them.</p><p>I don’t anymore.</p><p><strong>If I’m working with Figma, Figma MCP is on.</strong></p><p>If I’m not, why am I paying to explain Figma tools to a model that’s fixing something completely unrelated?</p><p>These days, I keep only two MCPs permanently enabled: Soul MCP, our design system, and Maratonec MCP, our build environment. Everything else gets turned on when I actually need it.</p><blockquote><strong>Go look at your MCPs. I’ll wait.</strong></blockquote><h3>One task, one chat</h3><p>My second bad habit was much harder to kill.</p><p>I liked long Cursor conversations. There was something comforting about them. Cursor knew what we’d built. It knew what went wrong. It knew why we’d changed something 40 minutes ago.</p><p>It knew <em>everything</em>.</p><p>Which, as it turns out, isn’t necessarily a good thing.</p><p>My sessions often looked like this:</p><ul><li>Build feature A</li><li>Fix feature A</li><li>Actually change feature A</li><li>Start feature B</li><li>Notice something broken in feature A</li><li><em>“No, that’s not what I meant”</em></li><li>Fix the fix</li><li><em>“No, actually…”</em></li></ul><p>Three hours later, <strong>Cursor and I are basically an old married couple arguing about things neither of us remembers correctly.</strong></p><p>And all of that history is context.</p><p>The conversation now contains old implementations, abandoned decisions, errors, corrections, and explanations of things that no longer exist.</p><p>Follow-ups carry conversation history forward, so longer sessions mean more history for the model to process.</p><p>There’s no magic number at which a chat becomes too long. For me, the better signal is when the task has changed or the conversation has accumulated enough wrong turns that I no longer trust it.</p><p>So my rule is deliberately simple:</p><p><strong>One task = one chat.</strong></p><p>New feature? New chat. Different problem? New chat.</p><p>And if things start going wrong, I don’t keep stacking corrections on top.</p><p>Cursor can fork a conversation from an earlier message. If things were good five messages ago, fork from there and try again.</p><p>Think of it this way: the fresh chat is the strategy. The fork is the tactic for when you didn’t start one soon enough.</p><p>My warning sign is two consecutive prompts beginning with some variation of:</p><p><strong>“No, actually…”</strong></p><p>At that point, we’re done here. <strong>Fork.</strong></p><h3>Be specific about what it should read</h3><p>If I’m changing one function in a 2,000-line file, Cursor probably doesn’t need 2,000 lines.</p><p>If I know exactly which component is involved, I don’t need to explain its architecture from memory.</p><p>I can just give Cursor:</p><p>@Button.tsx</p><p>@Button.stories.tsx</p><p>Now it gets the real implementation, not my probably-wrong description of it.</p><p>And if I only need to change one specific section, I select that section and use Cmd+K.</p><p>Same thing with errors.</p><p>Cursor doesn’t need the entire history of human suffering printed in your terminal.</p><p>If you know what matters, point Cursor directly at it. If you don’t, let Agent search.</p><blockquote>What I stopped doing is attaching things <strong><em>just in case</em></strong>.</blockquote><h3>And yes, I stopped speaking Czech to Cursor</h3><p>This one surprised me.</p><p>English tends to tokenize more efficiently than Czech and many other languages. A <a href="https://arxiv.org/abs/2605.24718">2026 study measuring tokenizer “fertility” across European languages</a> measured English at <strong>1.23 tokens per word</strong> and Czech at <strong>2.28</strong>, with Slavic languages as a group landing between roughly 2.2 and 2.5.</p><p>Same meaning. Nearly twice the tokens.</p><p>Does that mean I translate <em>“make this button smaller”</em> into English every single time?</p><p>No. My sanity also has value.</p><p>Where I think language really matters is <strong>in persistent context</strong>.</p><ul><li>Rules</li><li>Skills</li><li>Long specifications</li><li>Anything that might be loaded repeatedly</li></ul><p>So this is what I do:</p><p><strong>Prompts: <em>preferably English.</em></strong></p><p><strong>Responses: <em>English.</em></strong></p><p><strong>Rules and Skills: <em>always English.</em></strong></p><p>If a Skill gets pulled into context again and again, I want that persistent knowledge expressed efficiently.</p><p>If I ask one quick thing in Czech because my brain refuses to translate it at 11 PM, I think the global economy will survive.</p><blockquote><strong>Optimize the repeated stuff. Not your sanity.</strong></blockquote><h3>Skills are great. Your 8,000-word SKILL.md isn’t.</h3><p>The next logical mistake is discovering Rules and Skills and deciding to teach Cursor your entire company.</p><p>I did something like this too.</p><p>Here is our design system. Here are our conventions. Here is how I like components structured. Here is how we write copy. Here is how we name things. Here are seventeen edge cases. Here is the history of modern typography.</p><p>Now please move this div 8 pixels.</p><p>But there’s another trap here, especially if you work in a shared codebase.</p><p><strong>You might not even be the person who created the expensive context.</strong></p><p>I recently opened Cursor’s context breakdown on one of our projects and found <strong>35.8K tokens sitting in Rules</strong>.</p><p>At first I assumed we had created a monster of a rules file. We hadn’t.</p><p>Most of it came from two large AGENTS.md files that had arrived with Vercel skills in the repo. In this particular setup, they were being pulled into the Rules context on every turn — even when they had nothing to do with what I was working on.</p><p>Together, those two files accounted for roughly <strong>30K of the 36K tokens</strong> sitting in Rules.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XfDzqBEqKNh7FzsIbhsxkA.png" /></figure><p>That was another little <em>oh</em> moment.</p><p>And it exposed something I hadn’t really considered before.</p><p>In a collaborative project, your context isn’t necessarily just <strong>your</strong> context.</p><p>People add Rules. Skills. Agent instructions. Tooling. Helpful documentation. Someone installs something useful on Tuesday, somebody else adds another thing three months later, and eventually nobody really knows what the model is carrying around on every request.</p><p>In our case, moving those deep guides out of AGENTS.md and loading them only when needed dropped the Rules footprint from roughly <strong>36K to around 5K tokens</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WjZeelpr837o_PnZi0P7fA.png" /></figure><p>Without changing the actual product code at all.</p><p>So now I occasionally check Cursor’s context breakdown on shared projects too.</p><p>Not just what I added. <strong>What everyone added.</strong></p><p>My preference now is <strong>progressive disclosure</strong>.</p><p>Keep the always-on stuff tiny. Put specialized knowledge into scoped <strong><em>Rules</em></strong>. Put deeper reusable workflows into <strong><em>Skills</em></strong>.</p><p>And keep SKILL.md itself relatively short, pushing detailed reference material into files that can be loaded when needed.</p><p>This is especially useful for design systems.</p><p>I absolutely want Cursor to know that we already have a component for something before it invents another one. I just want it to learn about buttons when we’re actually working on buttons.</p><blockquote>Treat always-on context like a production dependency. Every kilobyte has a recurring cost.</blockquote><h3>Composer grew up</h3><p>So far this has all been about what the model reads. But the same budget question has a second lever that has nothing to do with context: which model does the reading in the first place.</p><p>This was probably the biggest change to my actual daily usage.</p><p><strong>This is my experience. Not a benchmark.</strong></p><p>We’ve been using Cursor since pretty much the beginning, so we’ve watched Composer go through most of its evolution.</p><p>And <strong>Composer 1</strong> shaped my opinion of it for quite a while.</p><p>I thought of it as the cheap model. The grunt. Good for simple tasks. Give Composer the boring stuff. Give Claude the important stuff.</p><p><strong>Composer 2.5 is a very different animal.</strong></p><p>I use it for UI implementation. React components. Refactoring. Prototypes. Debugging. Changes across multiple files.</p><p>A surprising amount of actual product development.</p><p>Not <em>“good considering it’s cheap.”</em></p><p><strong>Good.</strong></p><p>These days, I don’t really think about model choice anymore.</p><p><strong>I just use Composer 2.5.</strong></p><p>And that might be the biggest change of all. The model I once considered a cheap grunt has become the one I trust with pretty much everything I do in Cursor.</p><p>AI models move absurdly fast, but our opinions about them don’t.</p><p>We try a model once, decide <em>“this one is dumb”</em>, and keep that opinion for six months.</p><p><strong>Six months in AI is approximately 47 years.</strong></p><blockquote>If your opinion of Composer comes from Composer 1, it might be time for another date.</blockquote><h3>Sometimes spending tokens saves tokens</h3><p>There’s one optimization that sounds contradictory.</p><p><strong>Plan more.</strong></p><p>For anything non-trivial, I’ve become a big fan of planning before Agent starts enthusiastically touching everything.</p><p>Tell me what you’re going to change. Which files? What’s the approach. What could break?</p><p>Then I review that.</p><p>Only then: go.</p><p>Yes, planning consumes tokens.</p><p>But in my experience, a little more thinking upfront is often cheaper than a long correction loop after the Agent confidently misunderstood what I wanted.</p><p>The same goes for breaking implementation into layers:</p><ul><li>Structure</li><li>Behavior</li><li>Styling</li><li>Polish</li></ul><p>Instead of:</p><ul><li>Build the whole thing</li></ul><p>It’s less magical. It’s also much more likely to work. And I increasingly think that’s one of the big differences between <strong><em>playing</em> </strong>with AI coding and actually <strong><em>working</em></strong> with it.</p><p>The goal isn’t to write the most impressive prompt and watch 4,000 lines of code appear.</p><blockquote><strong>The goal is to get to a good result with as little rework as possible.</strong></blockquote><h3>This gets expensive at team scale</h3><p>None of this mattered much when AI was something one person on the team occasionally played with.</p><p>It matters when an entire team uses it every day.</p><ul><li>An unnecessary MCP here</li><li>An expensive model doing simple work there</li><li>A giant Rule loaded hundreds of times</li><li>A conversation that should have ended 40 messages ago</li></ul><p>Individually? Who cares.</p><p>Multiply it across a team, every working day, for a year? Now you have a different problem.</p><p>We already think about API calls, storage, cloud compute, and performance. I think AI usage is slowly joining that list.</p><blockquote>Not as something everyone needs to obsess over. <strong>Just something we should stop pretending is free.</strong></blockquote><h3>Before you open another Agent</h3><p>I don’t want to end this with thirteen commandments for responsible token consumption.</p><p>So here’s the version I actually find useful.</p><p>Before starting a bigger task in Cursor, I now mentally check:</p><ul><li><strong>Am I on the cheapest model that can realistically do this?</strong> Start with Composer 2.5. Escalate when it gives you a reason to.</li><li><strong>Which MCPs are enabled?</strong> If you’re not using Figma, browser, analytics, or whatever else you’ve collected, turn them off.</li><li><strong>Is this still the same task?</strong> If not, new chat.</li><li><strong>Has this chat already gone wrong twice?</strong> Stop correcting the corrections. Fork from the last good point.</li><li><strong>Do I know which files matter?</strong> @ them. If you only need part of a file, select it. If you genuinely don’t know, let Agent search.</li><li><strong>Am I giving it context “just in case”?</strong> Don’t.</li><li><strong>Is this complex enough to plan first?</strong> A minute in Plan Mode can be cheaper than fifteen minutes of undoing enthusiastic AI.</li><li><strong>Is this going into a Rule or Skill?</strong> Keep the always-on part short, scope it where possible, and write it in English.</li><li><strong>Am I about to paste 500 lines of terminal output?</strong> Please don’t.</li><li><strong>Could a fresh chat with three good references know everything it actually needs?</strong> Very often, yes.</li></ul><p>A year ago, getting better at AI meant figuring out how to give it <strong>more</strong>.</p><p>More instructions. More documentation. More tools. More context.</p><p>Now I’m increasingly convinced the next skill is knowing what to leave out.</p><blockquote><strong>The best context isn’t the biggest one.</strong></blockquote><blockquote><strong>It’s the smallest one that gets the job done.</strong></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f481685c8a05" width="1" height="1" alt=""><hr><p><a href="https://medium.com/emplifi-design/how-to-waste-fewer-tokens-in-cursor-f481685c8a05">How to waste fewer tokens in Cursor</a> was originally published in <a href="https://medium.com/emplifi-design">Emplifi Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design systems in the AI age: How Soul is turning designers into builders]]></title>
            <link>https://medium.com/emplifi-design/design-systems-in-the-ai-age-how-soul-is-turning-designers-into-builders-8e1c9f2c6463?source=rss----f146767dd08---4</link>
            <guid isPermaLink="false">https://medium.com/p/8e1c9f2c6463</guid>
            <category><![CDATA[ai-system-design]]></category>
            <category><![CDATA[agentic-systems-design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[cursor]]></category>
            <category><![CDATA[agentic-ai]]></category>
            <dc:creator><![CDATA[Petr Novak]]></dc:creator>
            <pubDate>Tue, 10 Feb 2026 09:18:37 GMT</pubDate>
            <atom:updated>2026-02-10T09:18:36.644Z</atom:updated>
            <content:encoded><![CDATA[<p>For most of my career, the boundary between design and development has been a hard line. Designers shaped the interface, developers implemented it, and design systems sat squarely in the middle translating visual intent into reusable code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ytAe3xEEcnhA8BvLFGqYvQ.png" /></figure><p>That model served us well. Design system teams became stewards of consistency, accessibility, and shared standards. We built component libraries, documented best practices, and helped product teams move faster without sacrificing quality.</p><p>But recently, something began to shift within our design system.</p><p>It wasn’t triggered by a sudden reorg or a leap into full automation. The change has been gradual, and more fundamental: AI is reshaping how we build, and in the process, it’s redefining the identity of the people building the system.</p><blockquote>The most important transformation isn’t just happening in the Soul codebase. <strong>It’s happening in our team.</strong></blockquote><h3>From UI Designers to Design Engineers</h3><p>In the current landscape, we’re moving far beyond the traditional role of “UI designers working on a design system.” We’re becoming builders.</p><p>To be clear, this isn’t just a title change. It’s a change in ownership.</p><blockquote>Being a builder means you don’t stop at the Figma file or the spec sheet. You stay with the feature until it exists in code — polished, functional, and ready to scale.</blockquote><p>By becoming more comfortable inside the codebase, my team and I can now build and iterate on smaller components independently, refine UI details directly in implementation, and contribute improvements without always waiting for a full development cycle.</p><p>That shift alone has changed the speed and the quality of how Soul evolves.</p><h3>Eliminating the friction tax</h3><p>Design systems thrive on collaboration, but traditional processes often introduce what I think of as a “friction tax.”</p><p>The usual workflow is familiar: designers create specs, stories are written for developers, implementation lands in a later sprint, and polish arrives only after several feedback loops.</p><p>Today, that process is starting to compress. Instead of treating UI refinement as something that happens at the end, we can handle many of the “last mile” improvements directly. In practice, design intent is captured closer to the code, and quality is baked in earlier.</p><p>This isn’t about bypassing engineering, but about liberating engineering to focus on what matters most: architecture, performance, and scalability.</p><h3>Cursor: A catalyst for building</h3><p>A major driver of this shift has been our adoption of <strong>Cursor</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*doVSgK2KEERLz8n2H3N2sQ.png" /></figure><p>Cursor has become a daily bridge between design and code. For many designers, code can still feel intimidating — but <strong>Cursor makes it feel more approachable</strong>, almost like another design material.</p><p>We use it to explore component patterns, prototype ideas quickly, and iterate with a speed that would have been difficult in a traditional workflow.</p><blockquote>AI-powered IDEs don’t replace the need to understand code, but they dramatically lower the barrier to entry. They turn “I wish I could fix that detail” into “I just fixed it.”</blockquote><h3><strong><em>Preparing the Soul Design System for the AI age</em></strong></h3><p>We aren’t at the “push a button, get a design system” stage… and honestly, I’m not sure we ever will be, or we even want to be.</p><blockquote>Soul isn’t being generated by AI. It’s being <strong>prepared</strong> for it.</blockquote><p>For us, AI adoption is not about full automation. It’s about creating a system where AI can operate safely and predictably, without eroding ownership or quality.</p><p>That preparation rests on three layers: <strong>rules, skills, and commands</strong>.</p><h4>Rules are protecting quality and boundaries</h4><p>Rules define the nonnegotiables of Soul: architecture decisions, styling conventions, component structure, testing expectations, and system constraints.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xxp2suA592pv5506Wi4UeA.png" /></figure><p>Their role is simple: <strong>protect quality and set boundaries</strong>.</p><p>Rules ensure that no matter who is building, designer, developer, or AI-assisted workflow, the output stays aligned with how Soul is meant to work.</p><h4>Skills are strengthening roles</h4><p>On top of rules, we use <strong>skills</strong>.</p><p>They encode expert judgment and system knowledge rather than simple actions. They supplement roles instead of replacing them, bringing senior-level perspectives directly into the workflow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6s-aTLnhDeEf92yzCNjt-g.png" /></figure><p>For designers, skills provide access to architectural and engineering thinking that would normally require years of experience. For developers, they reinforce design intent, like token usage, spacing, visual hierarchy, and consistency, at the moment decisions are made.</p><p>Skills don’t remove responsibility: they <strong>strengthen</strong> it.</p><h4>Commands are where execution happens</h4><p>Commands handle focused actions such as creating or updating components, adding icons, adjusting tokens, or generating Storybook documentation. Many of these tasks could be fully automated, but we intentionally chose not to do that, at least for now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q_A5cdZMTntIg5gDE0SaGQ.png" /></figure><p>We also <strong>use commands to represent personas</strong>, allowing us to supplement specific roles directly within the workflow.</p><p>Instead of treating personas as abstract prompts, we define them as <strong>executable commands with a clear purpose. </strong>For example, applying a senior architect or senior developer perspective to a concrete task.</p><p>For designers, persona-commands bring architectural and engineering depth into the workflow. For developers, it’s about surface design or design-engineering viewpoints, tokenization, spacing, and visual hierarchy, where design intent matters most.</p><blockquote>The goal isn’t maximum efficiency. It’s <strong>confidence</strong>.</blockquote><p>Commands act as guardrails that allow designers to make real code changes while preserving structure and preventing accidental breakage. Over time, these small, controlled interactions build fluency and trust.</p><h3>The role of trust</h3><p>Every AI journey involves uncertainty. Teams worry about breaking things, hallucinations, or whether designers truly “belong” in the codebase.</p><p>We’ve overcome this by fostering a culture of trust in our team. We’ve accepted that <strong>code is not sacred and it’s iterative</strong>. Mistakes are part of the process, as long as you have the systems and confidence to recover.</p><p>That mindset is essential for any team looking to evolve with curiosity rather than fear.</p><h3>Human oversight and dual audiences</h3><p>None of the rules, skills, or commands in Soul exist without human ownership.</p><p>Every rule, every skill, and every command, including persona-commands, is reviewed and refined by senior architect developers. AI assists, but <strong>humans remain accountable</strong>. That balance allows us to move faster without losing control to experiment and without compromising quality.</p><p>This approach has changed how we think about design system work itself.</p><blockquote>We are no longer designing Soul only for humans. We are designing it for <strong>humans and machines at the same time</strong>.</blockquote><p>Decisions that once felt minor, like naming, structure, or documentation depth, are now directly influence how understandable, scalable, and AI-compatible the system becomes. Preparing a design system for the AI age isn’t about chasing automation.</p><p>It’s about building a system that can be understood, trusted, and evolved by people first, and by AI alongside them.</p><h3>A new identity for design system teams</h3><p>For me, the biggest win isn’t just speed. It’s independence.</p><p>The barrier between the person who designs and the person who builds is collapsing. Prototyping is richer, delivery is faster, and the final product is stronger.</p><blockquote>AI will not replace design systems. But it will reshape the teams behind them.</blockquote><p>In our case, it’s turning designers into builders. And I believe this is only the beginning.</p><p><em>How is AI changing your design system team? </em>Are your designers still working mostly in design tools, or are they starting to build directly in code as well?</p><p>I’d love to hear what you’re seeing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e1c9f2c6463" width="1" height="1" alt=""><hr><p><a href="https://medium.com/emplifi-design/design-systems-in-the-ai-age-how-soul-is-turning-designers-into-builders-8e1c9f2c6463">Design systems in the AI age: How Soul is turning designers into builders</a> was originally published in <a href="https://medium.com/emplifi-design">Emplifi Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Silos to Collaboration: My First 30 Days as a Writer on a Design Team]]></title>
            <link>https://medium.com/emplifi-design/from-silos-to-collaboration-my-first-30-days-as-a-writer-on-a-design-team-4699b98417d5?source=rss----f146767dd08---4</link>
            <guid isPermaLink="false">https://medium.com/p/4699b98417d5</guid>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[technical-writing]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Silvia Hourigan]]></dc:creator>
            <pubDate>Tue, 06 Jan 2026 15:12:30 GMT</pubDate>
            <atom:updated>2026-01-06T15:12:29.178Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HbCjt40mrf8O5Z0s" /><figcaption>Photo by <a href="https://unsplash.com/@nickmorrison?utm_source=medium&amp;utm_medium=referral">Nick Morrison</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Leaving Legacy Tech Writing Behind</h3><p>In my experience, the position of a tech writer is one that sits as an afterthought of the product release workflow. The writer is informed of changes coming to the product and updates the documentation accordingly. Whether you realize it or not, that workflow limits not only the documentation, but the product itself.</p><p>Technical writers have a lot to offer, yet we are too often an untapped resource for UI optimization. We share a comprehensive perspective on the product with teams that are often siloed and provide the customer’s point of view in complicated (and sometimes chaotic) product experiences.</p><p>Yet that hasn’t always been the reality of my career journey. So, it was a truly pleasant surprise to realize just how integrated the writers are when I started as a tech and UI writer on Emplifi’s design team. Around here, there is a different way of doing things. Being part of a forward-thinking, design-led team has pushed me to dive deeper into UI principles and fundamentally change my perspective on what a writer’s process can be.</p><h3>Breaking the Last-Minute Cycle</h3><p>The traditional tech writing workflow I’ve experienced goes something like this:</p><ol><li>Product design changes are created and implemented.</li><li>A release is announced a few days or weeks out.</li><li>Tech writers are informed during the “last wave” of information.</li><li>The scramble begins: writers rush to figure out the documentation impact and implement changes within a tight deadline.</li></ol><p>While documentation still gets updated, an accelerated timeframe doesn’t allow for content quality assurance or optimization. Synchronization with the product becomes impossible; as a result, the doc center functions as a standalone afterthought.</p><p>In contrast, an integrated system brings writers into the conversation at step one, shifting our purpose from simple writing to content strategy. Instead of scrambling, there’s time to optimize. We are given the space to take a bird’s-eye view and ensure information is presented in the best possible way.</p><p>Incorrect information, gaps, and structural inaccuracies are weeded out when writers are involved from the get-go. While some might ask, “Why should I care about documentation?” the answer is simple: <strong>this is about customer experience</strong>.</p><p>By the time a user reaches the documentation center, their experience is already “tainted.” They aren’t there for a fun read; they’re there because they’re stuck. If they are then met with inaccurate or confusing content, it could be the final straw. A broken link or a vague instruction in the docs isn’t just a typo — i<strong>t’s a failure of the safety net we promised the user when they signed up.</strong></p><h3>The Feedback Loop: Where Writing Meets Strategy</h3><p>When a writer is embedded within a design team, the benefits flow both ways. It isn’t just about the writer getting a “head start” on documentation updates; it’s about the writer being an indicator for UI complexity. It’s about creating a feedback loop that strengthens the product before it ever reaches the user.</p><h4>If it’s hard to document, it’s hard to use</h4><p>In the legacy siloed model, the writer is often the first person to realize a workflow is unnecessarily complex. However, by the time they realize it, the feature is already built. By sitting with the design team, I‘m enabled to speak up during the prototyping phase. If I’m struggling to find a logical way to explain a feature in the documentation, it’s usually a signal that the UI itself needs more clarity. This opens doors to having discussions about simplifying the design, rather than trying to explain a “clunky” experience later.</p><h4>Aligning the mental model</h4><p>Designers and developers often use internal jargon to describe new features. If those terms make it into the UI and then into the docs, the user is forced to learn a new language just to use the product. Being involved from day one allows me to help align the mental model of the user with the vision of the designer. We can ensure that the labels in the interface match the titles in the documentation center, creating a seamless narrative across the entire platform.</p><h4>Reducing the cost of knowledge</h4><p>Every time a user has to leave the product to search the documentation center, they are taken out of their workflow and forced to enter another. By collaborating with designers, we can identify which information is critical enough to live inside the UI (via tooltips or microcopy) and what belongs in a long-form article. This partnership ensures the documentation center isn’t a graveyard for things the UI failed to explain, but a library for deeper learning.</p><h3>Looking Ahead</h3><p>My first 30 days at Emplifi have been a masterclass in integration. It has been a shift in understanding what it means to be part of the product, rather than the afterthought.</p><p>I’ve come to realize that when we stop treating documentation as the last step and start treating it as a foundational design layer, the benefits are limitless. From UI optimization to reduced ad hoc code fixes and better information architecture — everyone wins. But <strong>most importantly, the customer wins.</strong></p><p>As I move into my next 30 days, I’m excited to leave the scramble behind. I’m not just writing about the product anymore; I’m helping design a better way to experience it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4699b98417d5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/emplifi-design/from-silos-to-collaboration-my-first-30-days-as-a-writer-on-a-design-team-4699b98417d5">From Silos to Collaboration: My First 30 Days as a Writer on a Design Team</a> was originally published in <a href="https://medium.com/emplifi-design">Emplifi Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design System as a Service: Why Components Aren’t Enough]]></title>
            <link>https://medium.com/emplifi-design/design-system-as-a-service-why-components-arent-enough-6f8899fe27c6?source=rss----f146767dd08---4</link>
            <guid isPermaLink="false">https://medium.com/p/6f8899fe27c6</guid>
            <category><![CDATA[ui-engineering]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[designops]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Petr Novak]]></dc:creator>
            <pubDate>Wed, 20 Aug 2025 14:00:39 GMT</pubDate>
            <atom:updated>2025-08-20T14:00:39.197Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FvVIskZ84jYxBn7hxO4nig.png" /></figure><p>Most design systems are built under the assumption that everyone will read the documentation. But in reality, what teams need most is someone who will actually help them apply it. Here’s what we learned when our DS team became a service team… without planning to.</p><h4>Key takeaways</h4><ul><li><strong>A design system isn’t just a set of components — it’s a service.<br></strong>What matters just as much as the system itself is the team that helps others use it well.</li><li><strong>Support builds trust, and trust drives adoption.<br></strong>Informal Slack help, quick consultations, and context-aware advice make teams more likely to use (and respect) the system.</li><li><strong>Everyday decisions shape the system more than the roadmap.<br></strong>Real impact happens in the moment: should we tweak the component, adjust the design, or solve it locally?</li><li><strong>Being helpful has a hidden cost.<br></strong>When quick help becomes the norm, it’s hard to shift into strategic mode or say “no” when it’s needed.</li><li><strong>You don’t need a grand plan to act like a service team.<br></strong>Sometimes it just grows out of company culture, team mindset, and a desire to be useful.</li></ul><h3>When components aren’t enough</h3><blockquote>I thought that the most important thing about a design system is components. Now I know that the most important thing is the service around them.</blockquote><p>Most designers know what a design system is made up of: components, documentation, design assets, dev assets, or even tools for audits and measurement.</p><p>However, once your design system enters a real product, you run into something most documentation does not prepare you for:</p><p>👉 <strong>Every team, every edge-case, every use-case has its own reality.</strong></p><p>And that’s where the real work begins: not with the documentation, but with the service layer around it.</p><h3>Design system as a service</h3><p>Our design system team are not only component creators or curators. We work as a unified unit, combining design, development, and support. Our team is specifically made up of three full-time developers, a design lead and manager, and two UI designers, who give us about 50% of their time.</p><p>Together with developing the component, writing documentation, and planning a roadmap, we also take care of the design system implementation, <strong>ensuring each component is used and implemented correctly, effectively, and with the right context</strong> of the specific need. That means we are embedded in day-to-day operations. We help product teams, developers, and designers whenever they find issues, blockers, or edge cases.</p><p>Our <strong>support structure is informal, but consistent and easy to access</strong>. To achieve that, we have several Slack channels and syncs. The main design system channel serves as a safe space for support: everyone can ask for help or consultation, report a bug, or suggest an improvement. Despite that, we also have space dedicated to designers on Slack or during daily open hours. These channels are here to solve any design challenge and prevent issues that can come later.</p><p>In practice, this means that <strong>our team acts as a design system rescuer</strong>. If developers need advice or help with component implementation, we are here. If designers solve a specific problem and existing components are not a fit, we are here to find the solution, whether it’s editing the design, creating an exception, or improving or creating a component.</p><p>From the perspective of the teams we support, <strong>the design system becomes less of a gatekeeper and more of a problem-solving partner</strong>…<strong> </strong>and to me, that’s worth more than any perfectly written guideline.</p><h3>Where the service is visible most</h3><p>Not every impact is measured in adoption graphs or bug reports. Sometimes, it’s the tiny, daily decisions that shape your system, as well as your relationship with the people using it.</p><p>Let me take two practical examples from our day-to-day life with a design system to illustrate how we work.</p><h4>1. A local need, solved without system changes</h4><p>A designer came to us with a design that partially used an existing component but added extra functionality specific to that one screen.</p><p>In these cases, we usually weigh three options:</p><ol><li>Extend the existing component.</li><li>Create a local solution outside the system.</li><li>Adjust the design to work with what we already have.</li></ol><p>After a quick review and conversation, we chose option 3. We adjusted the design so it could combine the original component with a small local layout addition. No changes to the DS were needed.</p><p>✅ Fast implementation, consistent UI, no dev overhead.</p><h4>2. A small feature with broad impact</h4><p>In another case, a proposed design required adding a small new feature to an existing component. But this time, we noticed:</p><ul><li>The feature would be useful in other places too.</li><li>It was technically low-effort to implement.</li><li>It would improve the flexibility of the component overall.</li></ul><p>We decided to go ahead and implement the change immediately, even outside of our sprint planning. The decision paid off.</p><p>✅ The component became more robust, more reusable, and other teams adopted it with zero friction.</p><h3>The hidden cost of being supportive</h3><p>Approaching a design system as a service has clear benefits. First and foremost, <strong>it builds trust</strong>. When teams know they can reach out and get help, they’re more likely to adopt the system, ask questions, and avoid workarounds.</p><p>It also makes the whole product more consistent. Not because we’re forcing people to follow rules, but because we’re helping them make decisions within a shared structure.</p><p><strong>But there are trade-offs.</strong></p><p>One of the biggest challenges is that <strong>speed becomes the expectation</strong>. What started as “amazing support” quickly turns into “baseline support,” and over time, it becomes hard to carve out space for long-term planning or strategic DS improvements.</p><p>Another issue is visibility. Our informal support model works well for human interaction, but not so well for planning, reporting, or leadership alignment. A lot of the work we do is valuable but invisible, unless you’re part of it.</p><h3>More than a system, less than a product?</h3><blockquote>A design system isn’t a product. It’s a living service. And like every great service it runs on trust, not just tools.</blockquote><p>We never explicitly decided to turn our design system into a service. There was no offsite, no deck, no strategy. It just happened organically. And honestly, that might be the best way for it to happen.</p><p>It was the natural result of our company culture, our team mindset, and our desire to help. And now, looking back, I wouldn’t build a design system any other way.</p><h3>How do you balance system and service?</h3><p>Are you focused solely on maintaining the system, or do you actively support the people using it day to day?</p><p>👉 <strong>I’d love to hear how other teams handle this balance.</strong> If your DS team works like a service team too, how do you manage expectations, capacity, and impact?</p><p><strong><em>Drop me a comment or message</em></strong><em> — I’m genuinely curious how others are navigating this space.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f8899fe27c6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/emplifi-design/design-system-as-a-service-why-components-arent-enough-6f8899fe27c6">Design System as a Service: Why Components Aren’t Enough</a> was originally published in <a href="https://medium.com/emplifi-design">Emplifi Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We Designed In Phases and Quickly Won Back User Trust]]></title>
            <link>https://medium.com/emplifi-design/we-designed-in-phases-and-quickly-won-back-user-trust-a0f03f28206d?source=rss----f146767dd08---4</link>
            <guid isPermaLink="false">https://medium.com/p/a0f03f28206d</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Barak Landesman]]></dc:creator>
            <pubDate>Mon, 11 Aug 2025 11:55:10 GMT</pubDate>
            <atom:updated>2025-08-11T11:55:10.555Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A minimalist clock icon with a green checkmark symbolizing Business Hours that finally tick in sync with real-world teams." src="https://cdn-images-1.medium.com/max/1024/1*aFgxvC81tQK5wrPVF7khUA.png" /><figcaption>We redesigned Business Hours in Emplifi Care, one phase at a time. (Image by <a href="https://medium.com/@vilkus">Lukáš Vilkus</a>)</figcaption></figure><p>Have you ever had a feature that many of your users depend on but only notice when something goes wrong? That was “Business Hours” for us.</p><p>It may sound like a boring feature, but for our users in <a href="https://emplifi.io/product/social-customer-care/"><strong>Emplifi Care</strong></a> who operate 24/7 in different time zones, Business Hours are super critical. They’re what informs the system when an agent is <em>actually</em> available. If they’re incorrect, everything breaks: timers run while no agent is online, tickets get misrouted and performance metrics become inaccurate.</p><p>So yes… they are a pretty big deal.</p><p>In this post, I’ll show how adopting a <strong>Work Breakdown Structure </strong>method (an idea suggested by our product manager) allowed us to <strong>slice our solution into clear phases</strong>, <strong>design without overwhelming our users or ourselves, and achieve quick wins.</strong></p><figure><img alt="A ticket pings in at 4:05 PM, but only the agent whose schedule actually covers that time turns green,  showing why accurate Business Hours matter." src="https://cdn-images-1.medium.com/max/1024/1*p8c4BMdHLgD11NKrEMl5Xg.png" /><figcaption>In Emplifi Care, Business Hours<strong> </strong>show when agents are available across timezones. (<em>Image by </em><a href="https://medium.com/@vilkus"><em>Lukáš Vilkus</em></a><em>)</em></figcaption></figure><h3>The Snowball of Pain</h3><p>The gaps in our Business Hours configuration seemed minor at first. However, the pain added up fast, especially for global teams operating across various time zones, regions, and roles.</p><p>Here are some quotes from our clients:</p><ul><li>“Our timer tells us we are late before we even wake up.”</li><li>“Reports don’t match what my agents actually did this month.”</li><li>“Supervisors are guessing who is online. Excel tables are our only resource to manage it.”</li><li>“Every team member has to configure their own schedule. It’s time-consuming and exhausting.”</li></ul><p>Obviously, this isn’t what we wanted for our users. It became clear to us that <strong>time shouldn’t be something users need to think about… but when it’s broken, they feel it!</strong></p><h3>Our strategy: Thinking in phases</h3><p>Instead of launching one massive redesign, we broke the project into <strong>two vertical phases.</strong> Each phase focused on solving a real user problem and delivering visible value. This approach gave us <strong>space to design thoughtfully and release confidently</strong>.</p><figure><img alt="Phase 1: centralize Business Hours in Settings, then link reusable schedules to entire teams." src="https://cdn-images-1.medium.com/max/1024/1*dOb8HnLMTcv7o9Q3ue_iyA.png" /><figcaption>We started with the basics, creating a clear structure for managing Business Hours. (Image by <a href="https://medium.com/@vilkus">Lukáš Vilkus</a>)</figcaption></figure><h3>Phase 1 — Build the foundation</h3><p><em>Goal: One central hub · Reusable schedules · Assign to teams</em></p><p>We started by creating a central place in Settings to define Business Hours as reusable schedules. These could be assigned to teams rather than individual users.</p><p><strong>This phase focused on</strong> <strong>structure, not behavior</strong>. By isolating the foundational design first, we were able to:</p><ul><li>Reduce setup time and duplication</li><li>Help users visualize and manage availability at scale</li><li>Deliver a clear win without disrupting any logic behind ticket routing or performance metrics.</li></ul><p>Thanks to the phased approach, <strong>we could already test and ship a self-contained improvement without getting tangled in downstream dependencies.</strong> As a bonus, we could also get user feedback early and build momentum.</p><figure><img alt="New central Business Hours table in Settings" src="https://cdn-images-1.medium.com/max/1024/1*ZmOX5gkogrmDTk7QHC2Mqw.png" /><figcaption>A central Business Hours table in Settings lets teams set reusable schedules</figcaption></figure><h3>Phase 2 — Make it smarter</h3><p><em>Goal: Respect availability · Accurate metrics</em></p><p>Once the basic structure was in place, we moved on to integrating Business Hours into the workflows that depended on them:</p><ul><li><strong>Routing logic</strong> now takes agent availability into account (so tickets are not assigned when no one is online)</li><li><strong>Response-time metrics</strong> are now calculate based on the most relevant time model (24/7, profile-level hours, or user-level hours) depending on the use case.</li></ul><p>Unlike Phase 1, this phase tackled <strong>behavior and trust</strong>. Teams could now be sure that when someone was offline, the timer paused… and when someone was working, it didn’t.</p><p>It wasn’t just about accuracy, since <strong>we also had to make sure the logic behind it all felt understandable and manageable</strong>. No one wants to spend time figuring out how a metric was calculated or why a case got routed at 2 a.m.</p><p>By saving this for Phase 2, we gave ourselves space to separate logic from setup, so <strong>we could simplify the design of each layer.</strong> Once it was live, teams could benefit without needing to re-learn the system.</p><p>Since the scheduling structure was already familiar, they could intuitively adopt the smarter behavior and roll with it.</p><figure><img alt="Unified Analytics now lets teams pick the exact time model — profile, agent, or 24/7 — so every metric tells the right story." src="https://cdn-images-1.medium.com/max/1024/1*hWAeyXF-JwFa-MqA8IZiYg.png" /><figcaption>Now, users can accurately break down the exact time model by profile, agent, or 24/7</figcaption></figure><h3>The outcome: What time taught us</h3><p>So that’s how we redesigned time.</p><p>Of course, we’re never done with improvements, and in future phases we will focus on simplifying even more the set-up process by integrating public APIs to save time.</p><p>But I can confidently say that so far, <strong>we were able to tackle a complex problem without overwhelming our users or ourselves.</strong></p><p>Since we delivered improvements in slices that could be testable and valuable on their own, adoption was also easy. We were able to:</p><ul><li>Deliver quick value without a big-bang launch</li><li>Align reporting metrics to real working hours, restoring user trust</li><li>Keep the interface simple enough that users can <em>set and forget</em></li></ul><p>Most importantly: users noticed.</p><p>Impact was almost immediate when teams stopped reporting weird timer behavior. No more Excel spreadsheets or external tools. Auto-assignments worked like they should.</p><p>And at last, Business Hours quietly started doing what they were always meant to do: reflect how our users really work.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0f03f28206d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/emplifi-design/we-designed-in-phases-and-quickly-won-back-user-trust-a0f03f28206d">We Designed In Phases and Quickly Won Back User Trust</a> was originally published in <a href="https://medium.com/emplifi-design">Emplifi Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Designer’s Journey Into the Codebase]]></title>
            <link>https://medium.com/emplifi-design/a-designers-journey-into-the-codebase-4a2bb6fa8d8d?source=rss----f146767dd08---4</link>
            <guid isPermaLink="false">https://medium.com/p/4a2bb6fa8d8d</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[codi̇ng]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Martin Šalena]]></dc:creator>
            <pubDate>Thu, 10 Jul 2025 13:52:42 GMT</pubDate>
            <atom:updated>2025-07-10T18:12:48.628Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mA9ohXX-RlGJOd1nZmbarw.png" /><figcaption>You don’t have to be a developer to benefit from touching the codebase</figcaption></figure><p>Imagine a world where designers can safely tweak copy, adjust padding, or fix that one misaligned icon… without needing a Jira ticket, a sprint slot, or a dev to pick it up. Not because we want to bypass developers, but because we want to work with them better.</p><p>That’s the vision this little experiment gave me. It started with a simple challenge from our VP of Design: <strong>“Push something (anything!) to production.”</strong></p><p>The goal wasn’t to turn designers into developers. It was rather part of an ongoing team effort to explore no-code and low-code tools as a way to reduce handoff overhead and increase agility, especially for small design improvements.</p><p>By then, we already had a small group of designers sharing no-code tips and use cases. As my colleague Filip wrote in <a href="https://medium.com/emplifi-design/from-figma-to-lovable-how-no-code-changed-the-way-i-validate-design-concepts-7f17334b3a5b">his recent blogpost about no-code</a>, “designers have two key advantages to handle this challenge: our eagerness to learn and our curious nature”.</p><p>That mindset resonated with me. So when the opportunity came to push a real change to production, I decided to give it a shot.</p><p>Here’s how I pulled it off, and why it changed the way I think about the production process.</p><h3>What I learned by touching production</h3><p>The task I chose seemed simple on the surface: <strong>update the icons and copy in a dropdown menu </strong>in our Unified Analytics module. Functionally, the menu worked, but the icons and copy were inconsistent with the final design I had prepared.</p><p>It was a small thing, but this was the heart of the challenge:<strong> take one small but real improvement that’s too minor to justify a Jira ticket, and push it all the way to production</strong>. The goal wasn’t to just point out inconsistencies, but actually fix and ship them from start to finish.</p><p>The fix itself was straightforward enough, but the process around it was a challenge. I’ll walk you through it step-by-step.</p><h4>1. Cloning the repo (aka: the scary part)</h4><p>Before this experiment, I had played with HTML, CSS, and a bit of JS while building portfolios, fake sites or just for fun. But this was the first time I’d be working in our production codebase at Emplifi.</p><p>Cloning the repo from GitLab wasn’t exactly plug-and-play. I needed the right permissions, environment variables and tooling. One of our system architects hopped on a call and patiently walked me through the setup.</p><p>And just like that, I had the app running locally. It felt like unlocking a new level in a game I thought I’d only ever watch others play.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4hSoZV_74D1OasPWEP8yoA.png" /><figcaption><em>That moment when the local build actually launches = pure joy</em></figcaption></figure><h4>2. Finding the menu in the code</h4><p>The next challenge? Finding where that dropdown menu was hiding in the code.</p><p>Unlike Figma, codebases aren’t exactly visual or intuitive. But VS Code’s search function turned out to be my best friend. I started by searching for the exact copy I wanted to update (e.g. the phrase “Chart from scratch”). That led me straight to the component handling the menu logic and labels.</p><p>It took a bit of trial and effort to understand the structure, but once I landed in the right spot, everything clicked. I could see the copy strings, the icon components, and how they were rendered inside the dropdown.</p><p>Honestly, this part went more smoothly than I expected.</p><h4>3. Making the change (without breaking stuff)</h4><p>Once I found the right component, I ran the app locally so I could preview how my edits appeared in the interface in real-time.</p><p>Again, I wasn’t interested in touching the logic or functionality of the code, just swapping in copy and icons so they would be consistent with my final design file. Technically, this was simple, but even that came with a sense of responsibility.</p><p>It felt a bit like I was entering someone else’s house. I felt pressure to do it right and leave it as tidy as I found it. So I took care to follow existing conventions: same formatting, same component style, same import patterns.</p><p>Then I ran the app locally and refreshed the interface. And there it was: <strong>my updated dropdown menu, live in the product.</strong> The copy was clearer, the icons aligned. Seeing it rendered in the product, even if only locally, was strangely exciting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y0z6ZTlHecEDMi79B1JapQ.png" /><figcaption><em>Live preview of the updated dropdown, with cleaner copy and consistent icons</em></figcaption></figure><h4>4. Submitting my change for review</h4><p>Then came the moment of truth: submitting my changes for review.</p><p>This was the part where my changes would no longer live just on my machine. Even though I wasn’t changing anything critical, I hesitated. What if I missed something? What if I broke the layout somewhere and didn’t notice?</p><p>At this point, I decided not to go at it alone. I contacted a developer from my team to walk me through the steps. He helped me understand <strong>what a pull request is, how to write a clear description, and what to expect.</strong></p><p>I added a short note, submitted the pull request, and waited.</p><p>Not long after, it was approved and merged into the main branch. Not live yet, but ready to go! It felt like I crossed an invisible finish line in the process.</p><h4>5. Seeing my updates go live</h4><p>About a week later, I opened the app and… <em>ta da</em>! I could see my updated dropdown menu, live for all our users. Just some lines of copy changed and a few icons swapped, a small moment for any coder… but for me, it felt like a big win.</p><p>It wasn’t just the excitement of seeing my contribution in production (though that was real), but it was also a learning moment for me as a designer. Thanks to that one tiny edit, <strong>I walked away with more confidence, but also more empathy in how I collaborate with engineers</strong>.</p><h3>Why this matters for designers (even if you never want to code)</h3><p>Let me repeat: I didn’t take on this challenge because I want to be a developer.</p><p>I did it because I believe <strong>designers should have more ownership,</strong> especially when it comes to the small stuff. It could be a label that’s off, unclear microcopy, or awkward spacing. These are often too small to become tickets, but too visible to ignore</p><p>Usually we file the issue into Jira, cross our fingers, and hope it gets prioritized. And then we wait. But what if, just sometimes, we didn’t have to wait and could just fix it ourselves?</p><p>We talk a lot about being “product-minded” designers. For me, this was a way to prove it, not just by thinking about impact, but by participating in the lifecycle of the product. It’s like what Luděk, who came up with this challenge, wrote in <a href="https://medium.com/design-bootcamp/the-shape-of-design-to-come-3947a6a85309">his post about the future of design</a><strong>:</strong> <strong>it’s time to “stop treating the space between Figma and production as a black box”.</strong></p><p>I can now say that understanding even the basics of how code works helped me:</p><ul><li><strong>Give better handoffs</strong></li><li><strong>Communicate more clearly with devs</strong></li><li><strong>Spot edge cases earlier</strong></li><li><strong>Advocate for small improvements more effectively</strong></li><li><strong>Reduce friction with engineers, or even remove it completely</strong></li></ul><p>Best of all, I got a behind-the-scenes look at what engineers do every day, which gave me new respect for the craft… and a new sense of possibility for mine.</p><p>If you’re a product designer, I encourage you to take up the same challenge. You don’t need to build a feature or refactor a component. Just try changing one label. Push it to production, and see what happens!</p><p><em>Thanks to the Emplifi dev team for supporting this experiment — and to Luděk for nudging us all out of our comfort zones.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a2bb6fa8d8d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/emplifi-design/a-designers-journey-into-the-codebase-4a2bb6fa8d8d">A Designer’s Journey Into the Codebase</a> was originally published in <a href="https://medium.com/emplifi-design">Emplifi Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Figma to Lovable: How No-Code Changed the Way I Validate Design Concepts]]></title>
            <link>https://medium.com/emplifi-design/from-figma-to-lovable-how-no-code-changed-the-way-i-validate-design-concepts-7f17334b3a5b?source=rss----f146767dd08---4</link>
            <guid isPermaLink="false">https://medium.com/p/7f17334b3a5b</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[lovable]]></category>
            <category><![CDATA[concept-validation]]></category>
            <category><![CDATA[no-code]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Filip Hámek]]></dc:creator>
            <pubDate>Thu, 19 Jun 2025 13:42:51 GMT</pubDate>
            <atom:updated>2025-06-19T14:51:36.691Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l8vKppAP2iczSKiw6td5zQ.jpeg" /></figure><p>You heard the news, right?</p><p><strong>Being a product designer today is about being a generalist unicorn.</strong></p><p>AI is reshaping how we work, tech layoffs hit the industry like a tsunami, and expectations have shifted dramatically amid unstable market conditions. And for us designers, those expectations are higher than ever.</p><p>We now have to do more with less. Research, concept validation, and final delivery — we’re supposed to cover it all, often solo, <em>and</em> still deliver the same quality as before.</p><p>Well, that’s a tough pill to swallow.</p><p>The good news is that designers have two key advantages to handle this challenge: our eagerness to learn and our curious nature.</p><p>That’s exactly what led me to start exploring <strong>no-code tools</strong> last autumn. I saw these tools less as a trend and more as a possible solution to these growing pressures in our profession. So I challenged myself to learn more about them, use them in real projects, and see what happens.</p><p>Fast-forward to June 2025, with five prototypes under my belt, and I can confidently say: <strong>AI no-code tools like </strong><a href="https://lovable.dev/"><strong>Lovable</strong></a><strong> deserve their own place in the modern product design process</strong>, especially for concept validation.</p><p>In this post, I’ll share why — and then I’ll walk you through my process step-by-step.</p><h3>What is Lovable?</h3><p>Lovable is an AI-powered no-code platform that transforms plain language prompts into fully functional web applications. You describe what you want, and it builds it for you. Perfect for super rapid prototyping, without having to write a single line of code.</p><h3>Who is this post for?</h3><ul><li>Curious designers and PMs wondering if no-code tools are worth it</li><li>Beginners looking for a practical, non-hyped intro to Lovable</li><li>Anyone exploring better ways to validate design concepts faster</li></ul><h3>What Lovable is not</h3><p>Before we get into it, let me say, <strong>Lovable isn’t a magic solution</strong>. It’s not a replacement for Figma, and it’s not necessarily a shortcut to better design. But I’ll show you how it can enhance parts of your design process, particularly when validating concepts under tight deadlines.</p><h3>Let me show you why it’s worth giving Lovable a try!</h3><h4>1. Validate concepts in a matter of hours, not days</h4><p>Every designer who uses Figma for interaction design will recognize this familiar scenario from their work projects.</p><p>Here’s mine: back in February, I was working on a small interaction pattern for adding users to the Emplifi platform. I needed to test all the interaction details, including clipboard interactions, email validation, error states… but I was running out of time.</p><p><strong>How could I achieve all of this in Figma and still meet my deadline?</strong></p><p>I decided it was time to explore no-code tools. I chose Lovable because it seemed user-friendly and had made a good impression while I was doing my research on no-code tools.</p><p>As you can probably guess, I was impressed. With just <strong>15 prompts in 40 minutes</strong>, I had a working prototype to present to other stakeholders. No placeholder screens, just results.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F3LVRGeb3aEA%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D3LVRGeb3aEA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F3LVRGeb3aEA%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/29ecde30bdd94f6ad76fa76fd70e508e/href">https://medium.com/media/29ecde30bdd94f6ad76fa76fd70e508e/href</a></iframe><h4>2. Align with developers from day one</h4><p>When I showed the prototype to my dev team, I discovered other benefits of this approach that I hadn’t expected: faster alignment.</p><p>After my team reviewed my concept, our project engineer recreated it using <a href="https://www.cursor.com/">Cursor</a> (an AI code editor) the next day. His version was interactive and similar to mine, but further enhanced with components from our <a href="https://soul.emplifi.io/latest/home/soul-design-system-LbXdwFUj">Soul Design System</a>.</p><p>From there, we compared our two versions and aligned on details as closely as possible.</p><p>Honestly, the outcome was nothing groundbreaking. So why am I telling you this?</p><p>Because it’s still one of my favorite design moments from the past 6–9 months. It was fun, collaborative, and most importantly, <strong>there were no misunderstandings or mismatched expectations.</strong> None of those “Wait, didn’t we agree on something else in the meeting?” moments.</p><p>The handoff was effortless, and acceptance was very smooth.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fo8ylLG76ogw%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Do8ylLG76ogw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fo8ylLG76ogw%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/36098438ea4541c21b14452a696b2104/href">https://medium.com/media/36098438ea4541c21b14452a696b2104/href</a></iframe><h4>3. Becoming an equal partner to other stakeholders</h4><p>For context, this benefit is about kick-off meetings, and how I usually feel about them.</p><p>You know how it goes. You want to be seen as an equal partner right from the beginning, but instead, you sit silently among the other stakeholders for over an hour. This early in the process, you have nothing to contribute, no vision to share, and no prototype to present.</p><p>In these meetings, <strong>I usually feel awkward, like I have a seat at the table but no real way to participate.</strong></p><p>(And before anyone rushes to the comment section: yes, I’m fully aware — as <a href="https://www.linkedin.com/in/jmspool/">Jared Spool reminds</a> us — with continuous research and strong design leadership, we <em>should</em> come in with insights, a vision, and strategy. But let’s be honest: not every team or project gets that kind of treatment.)</p><p>Here’s why no-code tools help shift this dynamic.</p><p>Figma makes it nearly impossible to deliver concepts this early in the process, but<strong> tools like Lovable remove time as a limiting factor.</strong> You can start shaping your vision very early, <em>before</em> the first sprint even begins.</p><p>For example, below are two early concepts I built for an Emplifi product called Chatbot. One explored how we might test chatbot flows, and the other presented a new overview page for listing active chatbots.</p><p>Nothing too flashy, but that wasn’t the point. What mattered is that these concepts helped communicate my intentions very early, and sparked unexpected discussions with our PM and engineers right from the kick-off.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FphRVYSjNEdg%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DphRVYSjNEdg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FphRVYSjNEdg%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e02f82d170f3379a0e912e001592078e/href">https://medium.com/media/e02f82d170f3379a0e912e001592078e/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FLBP99_2wWJU%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DLBP99_2wWJU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FLBP99_2wWJU%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/2ceb541c524a043f089f1f25fa6f5dc2/href">https://medium.com/media/2ceb541c524a043f089f1f25fa6f5dc2/href</a></iframe><h4>4. AI as a designer partner with a fresh perspective</h4><p>So far, I’ve discussed mostly the time-saving and alignment benefits of AI no-code tools. But while working on my biggest Lovable project yet — something I call the <strong>Team Roles Wizard </strong>built for the Emplifi Teams section in Settings — I discovered a completely different kind of benefit.</p><p>This one is about creativity.</p><p>I want to highlight one moment that opened my eyes when prompting Lovable. During the overall concept development, Lovable offered me a question: <em>“Would it make sense to include a team role preview panel that updates based on the permissions selected by the user?”</em></p><p>This simple suggestion made me stop and think.</p><p>At that moment, I realized I had completely missed that angle, even after conducting calls with clients, extensive competitor analysis, and gathering dozens of insights in Productboard. <strong>Lovable saw the gap I didn’t and helped me push my solution to the next level.</strong></p><p>You can imagine my reaction. If you can’t, it was something like this: “Oh my lord. I’m an idiot. Of course that it makes sense. How did I not see it until now?”</p><p>That’s when it clicked for me: <strong>AI no-code tools can be creative collaborators.</strong> They can broaden your horizons, keep you in check, help you connect the dots, and ultimately improve your design.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FN324XnxXXQw%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DN324XnxXXQw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FN324XnxXXQw%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d148f41ea33f5e6af848f58961c32192/href">https://medium.com/media/d148f41ea33f5e6af848f58961c32192/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i7rs1rNMceLG9gsfhozndA.jpeg" /><figcaption>Lovable suggested to include live Role preview</figcaption></figure><h4>5. More natural user testing</h4><p>It was a happy coincidence that I had a call with a customer the day after I finished creating the Lovable concept for team roles. I hadn’t planned to talk about roles and permissions, but the customer mentioned her struggles with them.</p><p>So I seized the opportunity to test the new concept.</p><p>I was pleasantly surprised at how smoothly the whole experience went. There were no awkward pauses, no need to explain how Figma works, and no need to adjust the scaling to make the prototype fit on the customer’s screen.</p><p>Instead, <strong>we spent 95% of our time focusing on what truly matters</strong>: the overall experience and her pain points. Those are the kind of insights you really want, especially if you only have 30-minute testing slots like I do.</p><h4>6. Become aware of technical challenges sooner</h4><p>Do I understand the basics of HTML and CSS? Yes. Does that stop me from designing ‘technical nonsense’ in Figma? Absolutely not!</p><p>The problem is that you often don’t find out that your “wonderful ideas” don’t work until the specification is finished and you’ve already moved on to another project. Then, you have to find time to go back and fix them, increasing the scope and adding strain on your relationship with developers.</p><p>Luckily, working on the concept for the Team Roles Wizard in Lovable helped me spot red flags much earlier than I normally would have. I knew that my team would question me later in the process about some decisions, and I was able to find answers sooner that I could implement into the spec.</p><p>In the case of Team Roles Wizard, I was able to catch:</p><ol><li>The missing option to rename a role</li><li>Visibility issues with the primary button on devices with a smaller screen height</li><li>How the preview panel behaved on different screen size</li></ol><p>Catching these early meant I could adjust the concept before handing it off, saving time for everyone and reducing future headaches. In this way, <strong>using no-code tools helps you to understand your solution better, which ultimately makes you a better partner for your engineering team.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wQVGa2Ty6VbP9Bu2I_yWRQ.jpeg" /><figcaption>Lovable can help you to spot technical issues sooner</figcaption></figure><h4>Bonus benefit: Real user data from unmoderated testing tools</h4><p>I’ll be honest: so far, I’ve only used the combination of Lovable and <a href="https://www.lyssna.com/">Lyssna</a> (a platform for usability testing and surveys) for the last concept mentioned above. So I’m not ready to confidently claim that testing with a live website leads to <strong>dramatically</strong> better unmoderated insights.</p><p>But… I liked what I saw. The experience felt smoother, and being able to test something that behaves like a real site adds real value.</p><p>Just take this as a handy reminder: <strong>tools like Maze or Lyssna allow you to test live websites, which complements Lovable’s ability to publish sites and prototypes quickly.</strong></p><h3>My current process</h3><h4>Step 1: Nail down your vision</h4><p>I found one limitation with Lovable and other no-code tools: the process of working with them is extremely linear. It doesn’t allow you to branch out and experiment or explore multiple directions at once.</p><p>That’s why I believe that <strong>for product designers, Lovable shines most when you already have a clear concept to validate, rather than during the exploration phase.</strong></p><p>How do I overcome these limitations? I see Lovable as just another tool in my toolkit. For exploration, I still rely on paper sketches or a Figma canvas. That’s where I figure out the core structure, flow, and potential directions.</p><p><strong>Lovable comes in only once I have a clear idea of what I want to build.</strong></p><p>That was exactly the case with my Team Roles Wizard. I first explored the concept through rough sketches and low-fidelity mockups, gradually refining them into a more detailed direction, before finally bringing it to life in Lovable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dNVzYd-qRoa-8B4Jr9LsYQ.jpeg" /><figcaption>Nail down your vision first before jumping to Lovable</figcaption></figure><h4>Step 2: Perfect your first prompt</h4><p>Once you have a solid idea, the next step is translating it into a format that no-code tools like Lovable can actually understand. This might be the hardest step, so I recommend using as many existing resources or tools as possible.</p><p><strong>Lovable needs clarity. The better your prompt, the better your result.</strong></p><p>Ask yourself if you can provide supporting materials for your prompt.</p><ul><li>Do you have a sketch or image from the first step? Attach it in the Lovable chat.</li><li>Do you have a business strategy or vision laid out? Include it.</li></ul><p>Keep in mind that Lovable will only process up to three requests per prompt and will significantly condense your initial prompt. So clarity and focus are everything!</p><p>To get the best results, I usually compose my first prompt not in Lovable but in ChatGPT, using GPTs specifically built for polishing prompts. Here’s one I use: <a href="https://chatgpt.com/g/g-6763490b201c8191b5dfea11b72fffb2-lovable-assistant">Lovable Assistant</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QgCCtDPvnKwT3rMeGaIHJg.jpeg" /><figcaption>Ask AI for help to perfect your first prompt</figcaption></figure><h4>Step 3: Make your work effective and predictable</h4><p>Once I’ve set up the initial concept, I follow this circular workflow that helps me stay fast, focused and consistent:</p><ol><li><strong>Use voice instead of typing.</strong> Writing prompts can be slow and frustrating, especially when iterating. A couple of months ago, I noticed a popular tool in the design community called <a href="https://superwhisper.com/">Superwhisper</a>. This handy tool converts speech to text, which makes the whole process much quicker and less tiring.</li><li><strong>Polish prompts with DeepL.</strong> DeepL is best known as a translation tool, but it also has a writing assistant available as a <a href="https://www.deepl.com/en/chrome-extension">browser plugin</a>. It’s super useful for refining copy. I use it to clean up my Superwhisper transcripts, which is especially helpful as a non-native English speaker.</li><li><strong>Use chat mode in Lovable.</strong> Before jumping into full implementation, I use chat mode to preview Lovable’s plan. This helps ensure it understands my request <em>before</em> it writes any code. It prevents you from having to brute-force code fixes line-by-line after a misunderstood prompt. This not only saves you time, but also helps reduce build costs as an added bonus.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dWq1p0uQROZuNLDND-WYHw.jpeg" /></figure><h4>Step 4: Build the concept like Lego</h4><p>Since I use Lovable primarily to validate my ideas with simple concepts, and not for polishing final designs, I don’t need to follow our design system or obsess over perfect components.</p><p>Instead, I approach this step like <strong>building with Lego: work fast, use what’s available, and focus on structure over aesthetics.</strong></p><p>There are tons of great UI component libraries on the internet you can borrow from, so it makes sense to take advantage of them. These external libraries offer extensive collections of pre-built interactive components that are ready for you to drop into your concept.</p><p>Here are some of my favorite libraries that I’ve used with Lovable and other tools:</p><ul><li><a href="http://21st.dev/">21st.dev</a></li><li><a href="https://originui.com/">Origin.ui</a></li><li><a href="https://ui.shadcn.com/">Shadcn</a></li><li><a href="https://headlessui.com/">HeadlessUI</a></li><li><a href="https://daisyui.com/">DaisyUI</a></li><li><a href="https://semi.design/en-US/input/autocomplete">Semidesign</a></li><li><a href="https://www.syncui.design/">Sync UI</a></li><li><a href="https://www.heroui.com/">Hero UI</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YU_6Kquj1Hzfov5MqugO2w.jpeg" /><figcaption>Be efficient by using existing component libraries</figcaption></figure><h4>Step 5: Tackle issues with different methods.</h4><p>So, you’ve transferred your vision from Figma to Lovable and assembled it using components from external libraries. If your first prompt was solid, you might be tempted to stop here — Lovable usually does a pretty good job of recreating your idea “out of the box”.</p><p>But I recommend going one step further: <strong>refine the details.</strong></p><p>In my experience, a Lovable concept needs some extra polish at this stage. It might need additional logic, UI or layout refinements, or microcopy tweaks. Here’s how I approach that refinement process:</p><ul><li><strong>Dev mode:</strong> If you’re comfortable with code, you can jump straight to dev mode. Just be aware that many components are built with the Tailwind CSS framework, which isn’t very beginner-friendly. I personally struggle with it for visual tweaks.</li><li><strong>Edit mode:</strong> For smaller changes like editing headlines, button labels, or static text, you can launch edit mode directly from the Lovable chat bubble. It’s quick and intuitive.</li><li><strong>Annotated screenshots:</strong> This is my favorite method. Don’t hesitate to just take a screenshot of your current concept, annotate it in your preferred tool (for me, it’s Figma or <a href="https://monosnap.com/">Monosnap</a>), and send it back to Lovable. It works like magic. Since Lovable gets more context, it will respond better to your intended changes.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YVu5T5BznqAsa8dxlK2b8g.jpeg" /></figure><p>Finally, <strong>repeat Steps 3 to 5</strong> <strong>until you’re satisfied with the result.</strong> <strong>But don’t overdo it.</strong></p><p>Remember, Lovable is most powerful for concept validation and communicating your vision, <em>not</em> for pixel-perfect designs.</p><h3>Wrap-up</h3><p>If you’ve made it this far, I hope I’ve been clear by now: no-code tools are not intimidating. They’re not here to replace us product designers or eliminate the need for craft — they’re here to <em>support</em> us.</p><p>In my experience, tools like <strong>Lovable can give you back time, clarity and creative energy.</strong></p><p>For me, Lovable has become more than just a prototyping shortcut. It’s my creative partner, helping me validate ideas quickly, align with engineers faster, join strategic conversations earlier, catch usability issues sooner… and even see design opportunities I hadn’t thought of myself.</p><p>Figma is still my go-to for exploration and detail work. But when it comes to communicating and showing how something <em>could</em> work — and doing it fast — Lovable fills that gap in my process.</p><p>So, if you’re an overwhelmed designer or a PM who needs to pitch an idea, I encourage you to give it a shot. You might be surprised at what you can build in one afternoon.</p><p>Do you have questions for me, or have you tried a similar tool? Don’t hesitate to drop a comment below, I’d love to continue the conversation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f17334b3a5b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/emplifi-design/from-figma-to-lovable-how-no-code-changed-the-way-i-validate-design-concepts-7f17334b3a5b">From Figma to Lovable: How No-Code Changed the Way I Validate Design Concepts</a> was originally published in <a href="https://medium.com/emplifi-design">Emplifi Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Dialogues with Alžběta Hejnová]]></title>
            <link>https://medium.com/emplifi-design/design-dialogues-with-al%C5%BEb%C4%9Bta-hejnov%C3%A1-e2d31eec9def?source=rss----f146767dd08---4</link>
            <guid isPermaLink="false">https://medium.com/p/e2d31eec9def</guid>
            <category><![CDATA[product-designer]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[design-interview]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Salwa Benaissa]]></dc:creator>
            <pubDate>Wed, 09 Apr 2025 11:01:40 GMT</pubDate>
            <atom:updated>2025-04-09T11:01:39.837Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cV6AEqeXYpI9nNB7HbB2pQ.jpeg" /><figcaption>Meet<strong> Alžběta Hejnová, Product Designer </strong>at Emplifi</figcaption></figure><p><a href="https://cz.linkedin.com/in/al%C5%BEb%C4%9Bta-hejnov%C3%A1-8b068613a"><strong>Alžběta Hejnová</strong></a><strong> (</strong>or Bětka, as we call her) is a talented Product Designer on our team, contributing to key <a href="https://emplifi.io/platform/social-media-management">Emplifi</a> modules like Unified Analytics, Listening and Knowledge. In the second interview of our <strong>Design Dialogues</strong> series, Bětka shares how her journey as a licensed architect and a recent graduate of an intensive year-long UX course shapes her work today.</p><p><strong>Tell us about your career journey into product design.</strong></p><p>I studied architecture, but during my Master’s and several internships in the field, I started to question whether it was the right career path for me. I did some research and discovered UX design. One of my architecture classmates had already transitioned into this field, so I was inspired to explore it further.</p><p>I ended up taking a great UX course at <a href="https://www.czechitas.cz/">Czechitas</a>, a Czech organization that helps women and young people get into IT and tech. Then I got my first job in the industry, and I’ve been here ever since.</p><p><strong>What was it about UX design that made you want to transition from architecture?</strong></p><p>I transitioned from architecture to product design for three reasons: better work-life balance, a desire to work closer to current innovations, and greater satisfaction from faster feedback and tangible results.</p><p>Plus, designing for the digital environment allows me to connect with end users and validate and shape my design decisions more easily, and that makes me very happy.</p><blockquote>There are well-established patterns in both UX design and architecture that you can build on. You learn to understand the design’s goals, purpose, and importance, work within the context, and collaborate with the people involved.</blockquote><p><strong>Does your architecture background still influence your UX work today?</strong></p><p>Yes, I would say it gave me the basics. Studying architecture teaches you to, among other things, observe and analyze everything around you. You have to learn to develop an ability to simplify complex problems to design elegant solutions.</p><p>The design process itself is very similar in many ways. In both fields, you need to emphasize understanding the problem or brief, look for inspiration, do research, define the main challenges, iterate on your ideas, and consult them with stakeholders. What I prefer about product design is the ability to involve users in the process at multiple stages, but the rest of the process is the same at its core.</p><p>There are also well-established patterns in both fields that you can build on, and it’s helpful to know about them. You learn to understand the design’s goals, purpose, and importance, work within the context, and collaborate with the people involved.</p><p><strong>Last year, you completed the </strong><a href="https://www.uxwell.cz/"><strong>UXWell course in Prague</strong></a><strong>. What was it all about?</strong></p><p>UXWell is a year-long course consisting of nine weekend sessions and weekly mentoring meetings. The class is small, with only 12 participants. During weekends, we dove deeply into the entire design process, starting with defining the brief, conducting proper research, recruiting users, gaining insights, and so on. We also had a consultation on the weekend’s topics on the following Tuesday. The lessons were enriched by their practical experience, and my mentors played an important role in guiding me.</p><p>The whole course is focused on self-directed learning, so you work with a mentor to create a plan and achieve it step by step. Plus, every weekend, there were some featured guest speakers who shared real-life examples related to the weekend’s topic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EaeAbCzx6kkntdSPCqxkxA.png" /><figcaption>Bětka taking part in a UXWell session on gathering feedback</figcaption></figure><p><strong>How did the course contribute to your everyday work?</strong></p><p>I gained a more profound knowledge of research, particularly how to write hypotheses, create scenarios, and ask the right open-ended questions. I also picked up practical tips for conducting interviews properly. For example, I learned the importance of setting aside time after an interview to debrief with colleagues and prevent biases, simplify follow-up work by, for example, taking notes directly in FigJam, and inviting key stakeholders into the process when possible.</p><p>Also regarding research, I learned how to design effective questionnaires and became familiar with concepts like, for example, the “<a href="https://spin.atomicobject.com/context-scenarios-inform-design/">Context Scenario</a>”. I also learned how to maximize the value of methods like <a href="http://write hypotheses, create scenarios, and ask the right open-ended questions.">Design Studio</a> and <a href="https://hbr.org/2007/09/performing-a-project-premortem">Pre-mortem</a>, or how to collect the right inspiration effectively.</p><p>The course also helped me become more organized and aware of the design process. Now I’m conscious of following or skipping steps and I’m more aware of what’s necessary and what’s nice to have, so I can prioritize accordingly. This has boosted my confidence and made me more proactive in my work.</p><blockquote><em>Staying in touch with yours users is not as easy as it may seem. It requires a lot of time, energy, and skill to properly moderate interviews and gain meaningful insights.</em></blockquote><h4><strong>Are there any real-world aspects of working as a UX designer that are totally different from what is taught in theory?</strong></h4><p>Staying in touch with your users is not as easy as it may seem in a UX course. It’s a challenge and it requires a lot of time, energy, and skill to moderate interviews and support from the leadership to get quality insights. This has been a recurring theme in all the UX roles I’ve had so far. In my current team, there’s already an initiative underway to make tangible improvements in this area, such as keeping a list of suitable candidates, running internal research workshops, and getting more intensive support from the research team, which is promising.</p><p>Another major difference is the presence, absence, or maturity of design systems. In the real world, design systems can greatly influence the speed and effectiveness of your work. If there’s no system in place, you need to create components from scratch, figure out where to store them, and manage collaboration with your colleagues, all of which takes a lot of time. When you have a design system with company-wide support as we do with <a href="https://soul.emplifi.io/latest/home/soul-design-system-LbXdwFUj">Soul Design System</a>, you can save enormous amounts of time and effort.</p><p>In the end, no theory can really teach you how to deal with people. Relationships with stakeholders go beyond theoretical methods or rules. As a designer, you need strong communication skills to get along with people, manage conflict, and advocate for key parts of the design. You’ve got to be able to recognize what’s doable, where to push, and where to prioritize working relationships. It’s about knowing how your people work and targeting the sweet spots to be effective as a team. It’s important to be sensitive to others and use those skills to create the best product possible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1fbf9gBqWuHXuIbuqjNV9A.png" /><figcaption>Bětka’s design specifications for the homepage of <a href="http://emplifi.io/">Emplifi Unified Analytics</a></figcaption></figure><h4><strong>Since joining Emplifi, what has been the most challenging design problem you’ve tackled, and how did you approach it?</strong></h4><p>I’ve faced personal challenges, like improving my English and deepening my knowledge of analytics tools. But prioritization has probably been the greatest challenge. As a product designer, I collaborate with several developer teams. This means staying in touch with several product managers, attending multiple daily meetings, grooming sessions, retrospectives, planning meetings, and design critiques.</p><p>On top of that, I’m involved in other design team initiatives, such as user research projects and showcasing works-in-progress to the company in our monthly Design Forum presentations.</p><p>Balancing all of this while still carving out time for uninterrupted work is crucial, so prioritization is definitely key. Lately, one of my personal goals is to focus on recognizing what’s truly effective and finding the sweet spot between value and effort.</p><h4><strong>What advice would you give to someone interested in pursuing a career in product design?</strong></h4><p>I can’t speak for everywhere, but in the Czech Republic, I’d recommend starting by connecting with someone who’s already in the industry and learning as much as you can about the field. Listen carefully and think about whether it’s a good fit for you. Be honest with yourself about whether this is something you truly want to pursue and why.</p><p>In the Czech UX scene, <a href="https://almadesign.jobs.cz/">there’s a Slack channel you can join</a>, and you can also attend events hosted by the <a href="https://www.asociaceux.cz/">Czech UX Association</a>, like their <a href="https://www.meetup.com/asociace-ux/">UX Mondays</a> meetups among others.</p><p>After that, it depends on your situation. If possible, you can try to find a course or school to build your skills. In the Czech Republic, I’ve heard that Alma Career runs a good <a href="https://almadesign.jobs.cz/">UX summer camp</a> for free. Also, the <a href="https://adplist.org/">ADP List</a>, which offers free mentoring opportunities, could be great for initial feedback or to discuss your situation. I would then recommend looking for work experience opportunities. From what I’ve heard, getting a job as a junior designer is not currently very easy, so stay strong, and don’t get discouraged if it doesn’t happen right away.</p><blockquote>I pay close attention when friends or colleages are tackling design-related challenges — it’s a great way to see how they approach problems and I store that knowledge for my future use.</blockquote><h4><strong>How do you stay updated with the latest trends and developments in the UX/product design world?</strong></h4><p>Product design is not subject to as many trends as, for example, UI. But I’m surrounded by many designers, so I come across new ideas and discussions daily, whether in our work channels or on social media. I pay close attention when friends or colleagues are tackling design-related challenges — it’s a great way to see how they approach problems and I store that knowledge for my future use.</p><p>I also enjoy attending designer meetups like <a href="https://www.meetup.com/asociace-ux/events/">UX Mondays</a> or similar events in Prague, like the <a href="https://medium.com/emplifi-design/act-ion-for-accessibility-our-strategy-for-designing-for-everyone-86c9441799cd">Act-ion for Accessibility</a> event that we hosted at Emplifi. And recently, I’ve started reading more books to deepen my knowledge. Some of the latest ones I’ve read include <a href="https://www.amazon.com/Sprint-Solve-Problems-Test-Ideas/dp/1442397683"><em>Sprint </em>by Jake Knapp</a>, <em>I</em><a href="https://www.amazon.com/INSPIRED-Create-Tech-Products-Customers/dp/1119387507"><em>nspired</em> by Marty Cagan</a>, and now I’m in the middle of <a href="https://www.amazon.com/Articulating-Design-Decisions-Communicate-Stakeholders/dp/1491921560"><em>Articulating Design Decisions </em>by Tom Greever.</a></p><h4><strong>What’s one design tool or software you can’t live without?</strong></h4><p>Of course, Figma! It’s an essential part of my workflow. Another tool I rely on is Notion, where I organize all my notes—about new features, 1:1 meetings, random thoughts, or things I don’t want to forget. I’m also currently testing various AI tools and still figuring out which ones work best.</p><p>Grammarly and Deepl are also indispensable. They help me write more efficiently and confidently in English. And then there’s Slack, which I use because I have to! But really, I do like it as a tool too, especially the “Later” bookmark feature, which helps me keep a tab on tasks or react to things.</p><h4><strong>Where do you look to find inspiration for your work?</strong></h4><p>Often, someone will say something that sparks an idea or helps me find a solution. I also take a lot of screenshots of things I find inspiring online. Beyond that, I really appreciate good design in the “physical” world too—whether it’s innovative architecture or timeless product designs.</p><blockquote>I love experiencing unique atmospheres, especially when the weather feels special in some way. I’m captivated by magical light.</blockquote><h4>Do you listen to music or podcasts while designing? If so, what’s on your playlist?</h4><p>I like jazz very much, but when designing, I usually need silence — or the ambient noise of a coffee shop or the hum of a train, which are some of my favorite places to work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-hohAganQ9_hMsfJmU3yPw.png" /><figcaption>“I like the elegant design of objects like candle boxes that allow you to smell the candle before buying.”</figcaption></figure><h4><strong>What are some products, digital or otherwise, that you consider to have exceptional design?</strong></h4><p>I like the thoughtful design of common objects like candy or medicine boxes, applicators, dishes, or packaging with a clever idea—like candle boxes that allow you to smell the candle before buying it. I’m also drawn to ergonomic designs, things like computer mice, chairs, or boots. And I very much value well-designed spaces—those with a logical arrangement, playful lighting, strong impressions, or a special feeling that makes them memorable.</p><h4><strong>Apart from design, what are you passionate about?</strong></h4><p>I like psychology, cinema, and taking photos — mostly of atmospheres and people I like to be with. I love experiencing unique atmospheres, especially when the weather feels special in some way — like early mornings, sunsets, or just the way sunlight shines throughout the day. I’m captivated by magical light, and I also love it when it rains or when it snows.</p><p>It’s not just the weather that inspires me, though. I find joy in sensory experiences like the smell of the sea, fresh bread from the bakery, freshly washed clothes, or the scent of a blown-out candle, flowers, or fallen leaves in autumn. All these magical phenomena give me energy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LNW_E6MRKwuN8IClzQ4OnA.png" /><figcaption>“A try at capturing a magical night skiing moment in Deštné — though never as good in photos as in reality.”</figcaption></figure><h4>Thank you for taking the time to enlighten us, Bětka!</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2d31eec9def" width="1" height="1" alt=""><hr><p><a href="https://medium.com/emplifi-design/design-dialogues-with-al%C5%BEb%C4%9Bta-hejnov%C3%A1-e2d31eec9def">Design Dialogues with Alžběta Hejnová</a> was originally published in <a href="https://medium.com/emplifi-design">Emplifi Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The shape of design to come]]></title>
            <link>https://medium.com/@ludek-cernocky/the-shape-of-design-to-come-3947a6a85309?source=rss----f146767dd08---4</link>
            <guid isPermaLink="false">https://medium.com/p/3947a6a85309</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[no-code-development]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Luděk Černocký]]></dc:creator>
            <pubDate>Sat, 05 Apr 2025 14:00:53 GMT</pubDate>
            <atom:updated>2025-04-05T14:00:52.999Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eG5HEHF9VN4jQuqmu3VlVA@2x.png" /><figcaption>Generated by ChatGPT, inspired by Mr. Milchick’s office in Severance</figcaption></figure><p>If you’re reading this in 2026 — hello, future me.</p><p>I’m writing this in spring 2025, at a moment when design is changing fast. Again.</p><p>This isn’t a prediction carved in stone — it’s a journal entry. A reflection.</p><p>A snapshot of the patterns I’m seeing in my team’s work, in conversations with product managers, engineers, fellow design leaders — and across the broader tech ecosystem.</p><p>Some of these thoughts have been forming for weeks. Others surfaced mid-conversation or while watching someone launch a scrappy no-code experiment (we’ve been doing that a lot recently).</p><p>They may age well. They may not. That’s not the point.</p><p>The point is this: change is happening. And the better we understand it, the better we can shape what comes next.</p><h3>1. Smaller Teams, Sharper Focus</h3><p>We’re entering an era of smaller, more focused teams — and this applies to every discipline, not just design.</p><p>As Marty Cagan pointed out in <a href="https://www.svpg.com/a-vision-for-product-teams/">his recent article for the Silicon Valley Product Group</a>, <strong>product teams are becoming leaner but more effective</strong>. It’s not about doing more with less — it’s about removing noise, overhead, and unnecessary handoffs.</p><p>Tooling is progressing exponentially. Ten years ago, building a prototype in one day might have required skipping crucial steps or working late hours. But now, with Figma, some no-code tools <em>(more about that a</em> <em>few sections below)</em>, and a pinch of ChatGPT/Claude, one designer can explore five directions in the morning and test three of them before lunch.</p><p>It’s not that AI is replacing us. Rather, it gives us the opportunity to design more thoughtfully. A well-equipped product designer — or product manager — can now move from problem to prototype to validated solution faster, not because they work harder — but because the environment finally allows them to work smarter.</p><p>In design (and beyond), this means fewer people but clearer ownership. Less specialization, more responsibility.</p><p><strong>I’m not going to lie: I can’t wait for this.</strong> I’ve always been a fan of smaller, faster teams. They move with clarity, build trust quickly, and waste less energy on<em> alignment theater.</em></p><p>And honestly — if you’re a leader who thinks doubling headcount automatically makes things better, you might find yourself in a hard place when the economy shifts or your company misses its targets. We’ve all seen it: hiring sprints, followed by panicked layoffs, followed by the same conversations about focus and accountability.</p><blockquote>The one-person team isn’t just a startup myth anymore. It’s becoming a viable structure — especially in smaller companies and early-stage teams. And maybe even in larger ones, as AI and no-code tools continue to evolve.</blockquote><p>And yes — that means the definition of “designer” is also shifting.</p><h4>2. The Rise (Again) of the Full-Stack Designer</h4><p>The age of hyper-specialized roles is fading. That doesn’t mean experts are obsolete — far from it. But the modern product designer’s toolkit is expanding, and they’re expected to do more with it.</p><p>Research, copywriting, visual design, systems thinking, even hands-on work with component libraries — it’s all blending. There’s a growing expectation that designers can navigate more of the product cycle independently. Not to replace other roles, but to reduce friction and keep momentum.</p><p>This shift is reflected in job descriptions. Product Designers <em>(UX/UI Designers, …) </em>are now expected to write microcopy, run usability tests, contribute to design systems, build prototypes, run through data, recruit users, and talk to customers — regularly.</p><p>And honestly, why not? With the right tools, many of these tasks are easier than ever — and can unlock better, faster decisions.</p><p>In many ways, we’re circling back to the earlier days of digital design, when the same person would ideate, design, and build.</p><p>But this time, we’re doing it with better tools, smarter systems, and (hopefully) stronger judgment.</p><h4>3. Design Systems Democratization</h4><p>As design tools evolve and no-code adoption rises, design systems are becoming more open, usable, and essential.</p><p>We’re seeing a shift from tightly controlled libraries to modular, plug-and-play ecosystems that empower not just designers but also product managers, marketers, and even customer success roles to build experiments without waiting for dev resources.</p><p>I want our product managers to be able to spin up a quick prototype using our design system—in minutes, not days—so they can test ideas quickly. That’s why I’m pushing to open up our <a href="https://soul.emplifi.io/latest/home/soul-design-system-LbXdwFUj">Soul Design System</a> almost completely.</p><p>This is exciting — but it also raises the bar. Open design systems require clear documentation, robust components, and smart governance. They force us to think like product builders, not just designers.</p><p>At the same time, <strong>the more accessible our systems become, the more we risk generic outcomes</strong>. When everyone uses the same components and patterns, sameness spreads fast. This isn’t something new; it’s been around forever. Consider how many websites resemble Linear’s design or how many new apps mimic Notion’s navigation. That’s why creativity, visual identity, and <strong>craft will become even more important — not less.</strong> Companies that need<em> </em>(or want) to stand out will need to invest in <strong>distinctive visual/UI design</strong>, compelling storytelling, and the kind of polish that AI or templates can’t replicate.</p><h4>4. Tools Are Changing Everything (If You Let Them)</h4><p><strong>Designers have never had this much power.</strong> We can test, build, and learn at a pace we couldn’t even imagine a year ago.</p><p>In my team, we’re now exploring a whole new wave of tools: <a href="https://lovable.dev/">Loveable</a>, <a href="https://v0.dev/">V0</a> <a href="https://replit.com/">Replit</a>, and <a href="https://bolt.new/">Bolt.new</a>.</p><p>We’re still deciding which one to fully integrate (security, legal, etc.) into our design stack, with Loveable and V0 currently in the lead.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dlNWpy23JOPc7zQrybAF-w.gif" /><figcaption>A short example of a Create Widget screen that was made in 1 hour. Full prototype here <a href="https://v0-public-link-sharing.vercel.app/">https://v0-public-link-sharing.vercel.app/</a></figcaption></figure><p>Some of us have also been poking around with <a href="https://www.cursor.com/">Cursor</a>. It’s powerful, no doubt, but it still feels a bit “next-level” for day-to-day design workflows <em>(Spring 2025 — you can bet that in a few months, this will not be true anymore).</em></p><blockquote><strong><em>Quick side note:</em></strong><em> as tools become more open and team boundaries blur, </em><strong><em>security starts to matter more </em></strong><em>— even for designers. After a conversation about the risks, I asked our AI/Innovation team to help us spin up our own MCP server. They’re now working on it — and even in this early phase, we’re being cautious.</em></blockquote><blockquote><em>Vibe coding is fun… until it opens your system to something it shouldn’t.</em></blockquote><p>These tools aren’t just time-savers. They’re <strong>culture and mindset shifters</strong>.</p><p>And they’re sprinting like crazy. I’m absolutely sure that if I revisit this a year from now, there will be three new tools with insane capabilities. Just look at the leap in generative image models — from eight-fingered nightmares to visuals with a crisp copy in under 12 months.</p><p>To keep up, we’ve started running internal sessions where engineers teach designers how to run projects in a local environment, think in variants, and understand system logic. It’s not about turning designers into developers (well… maybe a little). It’s about reducing fear, adding context, and making better decisions earlier in the process.</p><p><strong>The takeaway?</strong> The best tools won’t just help you move faster. They’ll help your entire team speak the same language — and build better things, together.</p><p>💡<strong>Tip</strong><em>:</em> I always recommend designers to try building a Figma plugin (you can use ChatGPT to guide you), a personal website, or — even better — a tiny tool that solves a real problem you’re facing. One of our designers built a <a href="https://buzzola.lovable.app/">hiking planner</a>. Another created a cooking companion for his side project. Other an <a href="https://shiftpic.com/">online image compression site</a>. You’ll learn more than you expect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LESyNrwBBr1QpqFaMKFqyQ.jpeg" /><figcaption>Hiking Planner app made during Loveable Hackathon <a href="https://buzzola.lovable.app/">https://buzzola.lovable.app/</a> by our Senior UI Designer <strong><em>Lukas Vilkus</em></strong></figcaption></figure><h4>5. The Return of the Design Engineer</h4><p>As tools evolve and boundaries blur, a <em>new-old</em> role is making a quiet comeback: the <strong>Design Engineer</strong>.</p><p>This isn’t a new invention — UX Engineers have existed at Google and other tech giants for over a decade. But what was once a Big Tech unicorn role is now showing up in SaaS teams, startups, and design system squads — thanks to AI, no-code, and better tooling.</p><p>We’ve been exploring this path in our own team. I set a personal goal: by the end of this year, someone from our product design team will ship a small update to the product — without needing a developer. Even something as simple as updating the copy inside a tooltip. In our UI team, the challenge is even more ambitious: update a component without dev involvement.</p><p>Why? Because the front-end should be faster now. <strong>It <em>can</em> be faster</strong>. Waiting two weeks for a text change feels wrong in a world where designers can talk to code — or at least coax it gently.</p><p>This doesn’t mean everyone on the team needs to become a coder. But it does mean that we need to get more comfortable with the systems we help shape — and stop treating the space between Figma and production as a black box.</p><p>Design Engineers (or whatever title the industry comes up with) might not be for every team. But I’m convinced they’ll become a natural part of more of them.</p><p><strong>Will it be smooth? Not at all</strong>. Developers will notice the messy parts — the syntax, the structure, the risks. And fair enough. The same thing happens with prototypes, and with any first steps into unfamiliar territory.</p><p>But if the approach is grounded in curiosity and collaboration — not control — it starts to work. The early friction is worth it.</p><blockquote>What comes next is faster iteration, better alignment, and shared respect.</blockquote><h4>6. Experts Will Matter More Than Ever</h4><p>There’s a paradox here: as roles blend and tools become easier to use, <strong>the need for true expertise is actually growing.</strong></p><p>AI is a powerful amplifier — but it can also mask inexperience. I’ve seen junior designers rely heavily on AI-generated outputs, only to produce work that lacks depth, coherence, or intent. The same is happening in engineering: AI can autocomplete code, but it can’t debug business logic. Not yet, anyway.</p><p>In this new environment, <strong>the gap between the average and the exceptional will widen</strong>. And that’s uncomfortable. Especially for those early in their careers.</p><p>But it’s also a call to action — for seniors to mentor, for teams to invest in soft skills and systems thinking, and for everyone to move beyond just pushing pixels or generating prompts.</p><blockquote>Be the expert. And if you’re not one yet, that’s fine — just don’t stay still. Keep stretching. Keep sharpening. That’s what sets people apart.</blockquote><h4>7. Taste, Creativity, and Business Thinking as Differentiators</h4><p>So, in the age of AI-enhanced workflows and pixel-perfect templates, what will truly set designers apart? Well, the same thing that’s always made great design great. <strong>Taste. Creativity. Business acumen. Communication</strong>.</p><p>As tooling improves, we’re already seeing the risk of sameness. Just look around: almost every new app looks like Notion, and every new website channels the slick minimalism of Linear. These aren’t bad patterns — they’re great ones. But when everyone follows the same formula, the edges between products blur. Experiences start to feel interchangeable.</p><p>That’s where visual taste and creativity matter more than ever.</p><p>As AI and no-code tools continue to evolve, execution is no longer the bottleneck—<strong>decision-making</strong> is. Our responsibility is to think like strategists and speak the language of impact.</p><p>It’s designers who bring clarity of intent, creativity, and strategic thinking who will ultimately rise to the top. The ones who can answer not just <em>how </em>to build something and make it look good, but also <em>why </em>and <em>for</em> <em>whom. </em>In my last article for this blog, I talked bout <a href="https://medium.com/emplifi-design/make-design-count-fb88802b5c97"><strong>how designer leaders need to wear many hats to make an impact</strong></a>. This is truer than ever in the age of generative AI, which will only leave room for designers who can connect user needs with business goals, pitch ideas clearly, and guide teams toward meaningful outcomes.</p><p>Everyone else will be stuck chasing prompt engineering tricks.</p><h4>8. What You Can Do Now</h4><p>So what do we do with all this? How to prepare for this fast-approaching future?</p><p>We’ve seen it firsthand on our team.</p><p>One of our content designers reached out to the UI team a few months ago for mentorship. She proactively started building up her technical skills, not as a formal growth plan—it just made sense for her. She has since created her first component—a color picker—and now, we genuinely believe she could become an excellent product designer.</p><p>We’ve seen similar shifts in UX Research. Today, we have three highly skilled researchers—and to be honest, I don’t see a future where we’ll need six or twelve. Not because research is less important, but because product designers are becoming better at owning parts of discovery themselves—validating ideas, running interviews, and making smarter decisions earlier.</p><p>This leaves room for our experienced researchers to act as strategic partners, not just usability testers. <strong>They support our product designers as deep-thinking, high-leverage partners, </strong>and one of our researchers has also started exploring UI design.</p><p>Just like content design, research is still a vital craft, and often, it will remain a specialized role. But moments like this remind me that staying ahead of the times isn’t just about learning new tools or chasing trends. It’s about cultivating range. The people who thrive will be the ones who are curious, driven, and unafraid to stretch beyond the job description — not because they’re told to, but because they want to meet the future on their own terms.</p><p>Now, what can you do to be ready for this new reality? Here’s what I recommend to designers — and not just them:</p><ul><li><strong>Invest in soft skills.</strong> Empathy, storytelling, facilitation, leadership — they’ll never go out of style. In fact, they’ll matter more than ever.</li><li><strong>Get your hands dirty with no-code.</strong> Build something. Break it. Learn what it can and can’t do.</li><li><strong>Be curious about AI.</strong> Use it as a sparring partner, not a crutch.</li><li><strong>Think like a product person.</strong> Design is no longer just about form. It’s about outcomes—it always should have been. AI and no-code tools are accelerating that shift giving designers more space to focus on strategy and business.</li><li><strong>Share your knowledge.</strong> Mentor, write, teach — you’ll learn more in the process.</li><li><strong>Encourage others on your team to experiment.</strong> That includes product managers, marketers, and even customer success. A simple prototype built using your design system and a no-code tool can sometimes unlock better feedback than a long PRD.</li></ul><p>The future isn’t about doing more. It’s about doing better — with clarity, intent, and speed.</p><h4>A Note to Future Me</h4><p>If you’re reading this next year, I hope some of these ideas held up.</p><p>Maybe some proved wrong — maybe something even bigger came along and changed everything again. That’s okay.</p><p>What I hope hasn’t changed is this: <strong>That we keep adapting. That we keep learning. That we lead with curiosity, not fear.</strong></p><blockquote>Because <strong>adaptation is our superpower.</strong> And design — at its best — has always been about imagining what’s next.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3947a6a85309" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Make Design Count]]></title>
            <link>https://medium.com/emplifi-design/make-design-count-fb88802b5c97?source=rss----f146767dd08---4</link>
            <guid isPermaLink="false">https://medium.com/p/fb88802b5c97</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[growth-metrics]]></category>
            <category><![CDATA[design-leadership]]></category>
            <category><![CDATA[business-strategy]]></category>
            <dc:creator><![CDATA[Luděk Černocký]]></dc:creator>
            <pubDate>Tue, 04 Feb 2025 12:18:08 GMT</pubDate>
            <atom:updated>2025-02-04T12:18:08.100Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1U8muqINQNAkWLE0oG7LUg@2x.png" /></figure><p>I recently joined the <a href="https://open.spotify.com/episode/5f3OVwkpXdGokt6Gq1bWop?si=28d3be7ac2c14609">2FRESH Design Podcast</a> (<em>thank you for having me!</em>) to discuss my experiences as a design leader. The conversation, held in Czech, was heavily focused on “the value of design” and it gave me a lot to think about. It inspired me to share these thoughts more widely — so here I am, putting pen to paper (or fingers to keyboard, let’s say).</p><p>After 13 years at <a href="https://www.emplifi.io/">Emplifi</a> <em>(formerly Socialbakers)</em>, I understand that great products aren’t built on intuition alone. In SaaS — whether B2B or B2C — success depends on how well we serve the user. But great UX doesn’t happen in isolation. Understanding users is crucial, but so is understanding the business.</p><p>The strongest design solutions don’t just look good or feel intuitive — they drive meaningful outcomes. Whether it’s reducing churn or optimizing checkout flows, <strong>design must align with business goals</strong>. That means engaging with data, tracking key metrics, and demonstrating our impact. Yet too often, I see designers and design leaders missing these opportunities. It’s not that the tools or data aren’t available — most companies are swimming in analytics. The question is, are we willing to engage with them?</p><p>In this post, I’ll share <strong>five lessons about embracing this mindset shift</strong> and aligning design with measurable outcomes. Looking back, I wish I had learned these earlier. Because when we get comfortable with numbers, we don’t just elevate design — we prove our own value.</p><h3>1. Design saves development costs</h3><p>One of the clearest ways design proves its value is by reducing development costs. Every feature built incorrectly — or<strong> iterated endlessly</strong> — drains resources. Take, for example, a feature that wasn’t properly researched or tested. Once launched, it might require multiple iterations to meet user needs. Don’t get me wrong — iterations are part of the agile process, but they should be planned and thought through in advance.</p><p>Rushed or poorly researched designs don’t just slow down progress — they also impact the team’s morale and eat into the budget for future innovations. By focusing on detailed research, prototyping, and rigorous testing, our design team ensures that features are developed right the first time <em>(almost!)</em>.</p><p>Last time I checked, our Figma workspace contained over 4,000 files filled with experiments, prototypes, iterations, MVPs (and MVPs of MVPs), usability tests, and more. A perfect example of why this approach works is Emplifi Care, our customer service module that helps brands manage inquiries, provide personalized support, and resolve issues across digital channels. Care was <em>care</em>fully designed and tested with clients long before development began, ensuring it met real-world needs. Today, a year and a half after its launch, it’s performing exceptionally well, both in adoption and as a growing cornerstone of our platform. I can’t share revenue details, but for a product this young, it’s doing <em>very</em> well. <em>I’ll definitely be coming back to our Care product and how we built it in a future piece — there’s so much more to unpack.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tYJzrFvrU2DSd3hjR7gSDQ@2x.png" /><figcaption>A glimpse at one of our early prototypes, shaped together with our great customer.</figcaption></figure><p>This echoes a key point I raised in a LinkedIn discussion<em> (in Czech)</em>: quality design isn’t just about making things look good — it’s about mitigating risks. Poor design can snowball into expensive problems when features fail to meet user needs. As design leaders, it’s our responsibility to communicate this clearly to stakeholders, which brings me to my next point…</p><p><strong>💡 Tip: </strong>Share specific examples of cost savings during leadership meetings. Knowing how developer teams are structured and resourced can help you show how early design investments prevent expensive reworks and streamline workflows. Over time, you’ll be able to quantify costs — like estimating how much two sprints of Team XYZ translate to in dollars.</p><blockquote>Rushed or poorly researched designs don’t just slow down progress — they also impact the team’s morale and eat into the budget for future innovations.</blockquote><h3>2. The design leader as a business partner</h3><p>Design leaders should be business advocates. We need to think like salespeople and position design as a strategic enabler. At Emplifi, we’ve built internal tools to streamline the creation of personalized, interactive prototypes for prospective clients. With a simple <strong>Figma plugin, an intuitive template, and a structured briefing system</strong>, our team can generate a prototype that feels native to a client’s web environment — improving engagement and trust during sales pitches. These prototypes have directly contributed to closing deals and driving revenue.</p><p>And this is just one example of how design can go beyond product development to influence the bottom line.</p><p>In my <a href="https://emplifi.design/">Design team</a>, I always try to emphasize that a design leader must “sell” the value of design to clients and within the company. That involves building strong relationships with stakeholders from other departments like sales, customer success teams, marketing, and even HR (yes, with everyone!).</p><p>Over the years, I’ve hosted (or mostly invited myself to! 😆) numerous sessions with our sales or CMS departments, where I open my design booth (aka presentation: it’s the 21st century) and present all the ways my team can help them succeed. We also walk through new features, share prototypes, and discuss their direct impact on client satisfaction. This ensures they understand how design contributes to closing deals and retaining customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bifLo0gIIZOxmlBwOt1rDA.gif" /><figcaption>Intro screen from a Figma presentation/prototype that I use to highlight how we can help</figcaption></figure><p><strong>💡 Tip:</strong> Build cross-functional relationships. Collaborating with sales and customer success teams embeds design as a critical partner in driving company growth.</p><p><strong>💪 Challenge for readers:</strong> How often do you actively engage with sales or customer teams to showcase the strategic impact of design? What’s one change you could make this quarter?</p><blockquote>Design leaders should be business advocates. We need to think like salespeople and position design as a strategic enabler.</blockquote><h3>3. Metrics that matter</h3><p>Numbers drive decisions. While qualitative insights shape great design, pairing them with data gives us the influence to push for change. In our team, we focus on:</p><ul><li><strong>Retention:</strong> Understanding how design impacts users staying with the platform and designing experiences to encourage users to stay. <em>Is our new product/feature/quick-win moving the needle in the right direction? Is our onboarding working well?</em></li><li><strong>Churn: </strong>Identifying UX pain points that lead to customers not renewing. <em>Can we help? How?</em></li><li><strong>Revenue impact:</strong> Connecting design efforts to deals closed, such as a well-designed prototype influencing a $1M ARR deal.</li><li><strong>Inbound: </strong>Supporting new customer acquisition through optimized web and product experiences. <em>Did this new shorter “Book a demo” form improve our lead gen?</em></li><li><strong>User friction signals: </strong>Every support ticket tells a story. We monitor categorized tickets in Zendesk to uncover UX friction early. If a newly launched feature triggers a flood of <em>“How do I…?”</em> questions, it’s a sign that we need to simplify the experience. Reducing these friction points improves usability and lowers customer support costs.</li><li><strong>NPS &amp; CSAT:</strong> While they’re far from perfect metrics, tracking NPS &amp; CSAT scores can offer valuable insight into customer satisfaction. <em>For example, at this precise moment, we are scheduling follow-up calls with customers who rated us negatively.</em></li></ul><p>Of course, plenty of other metrics depend on your company’s industry and goals. These could include conversion rates, time to value, feature adoption, activation rates, ads revenue, outbound, average order value<strong>,</strong> items sold, time saved, or even lives saved in healthcare.</p><p>The key is to align your design efforts with the metrics that matter most to your business. I spend quite a lot of time in Salesforce/Tableau. It’s not about fully integrating design into every analytics but more about staying informed about trends and performance, which helps us align our efforts with broader business goals.</p><p><strong>💡 Tip:</strong> Track key metrics and share them with the rest of the company regularly via dashboards or team updates to reinforce the design’s impact on the business.</p><p><strong>💪 Challenge for readers: </strong>What business metrics are you currently tracking? How can they inform your design decisions?</p><blockquote>Stay informed about business goals and align your design efforts with the metrics that matter most to your business.</blockquote><h3>4. Building internal advocacy for design</h3><p>Yes, metrics matter, but building <strong>a culture of design advocacy is what truly</strong> amplifies their impact. Here are a few tactics that we established over time — and continue to nurture every day — in my team.</p><ul><li><strong>Monthly Design Forums: </strong>We host open sessions where designers present their latest work to the rest of the company. These forums, often including 150+ attendees, are an opportunity to celebrate wins, share insights, and build internal visibility for design’s contributions. Everyone from our team has a space to present. It’s a win-win situation: designers improve their presentation skills, and everyone else gets a chance to connect the work to real people, increasing relevance and making it easier to build relationships.</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FAC5zT9KUNWg%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DAC5zT9KUNWg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FAC5zT9KUNWg%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d354cac432f862a4c2c8bb19a74613ff/href">https://medium.com/media/d354cac432f862a4c2c8bb19a74613ff/href</a></iframe><ul><li><strong>Slack channels for collaboration:</strong> Our dedicated <em>#design</em> Slack channel encourages real-time cross-functional discussions, from salespeople requesting customized assets to product managers seeking quick feedback. We also created private channels like <em>#design-feedback-champions</em>, which build deeper connections with employees who love getting a sneak peek into work-in-progress, testing prototypes, or sharing UX/UI bugs and ideas — and sending special merch (t-shirts, stickers, a personalized thank-you card,…) to our “top feedbackers” is also lovely:)</li><li><strong>Internal newsletters</strong>: We recently launched “Design Digest” — bite-sized updates showcasing recent design wins, upcoming features, and team highlights. These updates are easy to consume and keep design top of mind. Slack is great for instant communication, but email ensures broader reach, especially for those who don’t live on Slack daily (there are more of them than you might think, I have data as proof!)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZStDLsBMLDwHGJYozdegDQ.gif" /><figcaption>Our internal “Layers &amp; Legends” monthly design digest sent via email across the company</figcaption></figure><ul><li><strong>Internal research:</strong> Our research efforts don’t stop at customers. We also dedicate time to understanding our internal stakeholders’ needs and pain points. By interviewing colleagues across departments and gathering feedback, we can align our designs with internal workflows and business goals.</li><li><strong>Design strategist &amp; advocate role</strong>: One of our <a href="https://medium.com/@adela.kandr">fantastic senior designers </a>transitioned into a strategic role, acting as a bridge between design and the rest of the company. And it certainly helps that she’s good with people.</li></ul><p>Remember that advocating for design means <strong>being proactive</strong>. Don’t wait for colleagues to come to you with problems — reach out, ask questions, and look for ways to make their lives easier. This is especially important in roles with higher turnover, like sales or customer success, where new faces might not immediately know how design can help.</p><p>Early in my journey at Socialbakers, I made this very mistake — I believed that great design alone would speak for itself. However, after a few years, I realized that <strong>even the best work can go unnoticed without active advocacy and collaboration</strong>.</p><p><strong>💡 Tip:</strong> Treat internal advocacy like a product. Communicate your work widely and tailor your messaging to resonate with different audiences, from engineers to executives. One of the best advice I ever received was: <em>“Everyone needs to know that Luděk = Design.” </em>And this isn’t just about me — I actively encourage every designer on my team to embrace this mindset.</p><p><strong>💪 Challenge for readers</strong>: How might you advocate for design in your organization? Could you organize a design forum/all-hands or similar initiative? What other tactics work for you?</p><blockquote>Remember that advocating for design means <strong>being proactive</strong>. Don’t wait for colleagues to come to you with problems — look for ways to make their lives easier.</blockquote><h3>5. The mindset shift: form habits, be consistent</h3><p>If there’s one common thread I’ve shared so far, it’s this: effective design leaders aren’t passive. You need to be proactive and take initiative — but most importantly, do it <strong><em>consistently</em></strong>. It’s not enough to collaborate with other teams once, join a meeting here and there, or share a prototype and hope for lasting impact. Influence just isn’t built in a single conversation; it’s built through repetition.</p><p>Leadership requires building habits that drive the mindset shift I started this post with. And that means being <strong>persistent</strong>. At first, pushing yourself into new spaces — whether it’s leadership meetings, sales syncs, or cross-functional discussions — might feel uncomfortable or unnecessary. But the more you do it, the more natural it becomes, and what starts as a conscious effort turns into instinct. That’s when the magic happens.</p><p>I’ve seen firsthand how designers who stay visible and engaged over time become trusted partners in the business. It’s never because they had one brilliant pitch, and always because they kept showing up and proving their value again and again. The first time you explain how design saves development costs, people might nod. The fifth time, they might start bringing you in <em>before</em> decisions are made.</p><p>Keep in mind that the best opportunities to advocate for design often don’t come when you expect them. If you’re not consistently<em> </em>showing up and staying engaged, you’ll risk being overlooked. So make it a habit. Be there whenever the conversation happens, and bring design to the table.</p><p><strong>💡 Tip</strong>: Consistency drives mindset shifts — not just in yourself but also in how others perceive design and trust your expertise. Form habits to keep design visible in ongoing conversations.</p><p><strong>💪 Challenge for readers</strong>: What’s one conversation, meeting, or initiative you can commit to <em>consistently</em> this quarter? How can you turn engagement into a habit rather than a one-time effort?</p><blockquote>Influence isn’t built in a single conversation; it’s built through repetition. Be there every time the conversation happens, and bring design to the table.</blockquote><h3>The bottom line: wear multiple hats</h3><p>I think I’ve made my point: design isn’t just about making things look good — it’s about solving problems, saving resources, and driving meaningful results. The lessons I’ve shared here aren’t just strategies but a mindset shift. I hope they inspire you to think differently about how design fits into your organization’s bigger picture.</p><p>For design leaders, the key takeaway is this: to succeed, we must wear multiple hats — that of a creator, manager, mentor, but also <strong>a business advocate</strong>. This is our real challenge, and we must own it with confidence. In doing so, every effort we make to align design with business outcomes will pay off — for our users, our company, and ourselves as valued drivers of success.</p><p>What’s the one step you’ll take today to elevate design’s impact in your company? Will you track a new metric, start a design forum, or embed design deeper into business conversations?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb88802b5c97" width="1" height="1" alt=""><hr><p><a href="https://medium.com/emplifi-design/make-design-count-fb88802b5c97">Make Design Count</a> was originally published in <a href="https://medium.com/emplifi-design">Emplifi Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>