<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Elmer  Enicky on Medium]]></title>
        <description><![CDATA[Stories by Elmer  Enicky on Medium]]></description>
        <link>https://medium.com/@elmerenicky?source=rss-9ddef40ad1ba------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*j8_U-yoBhCVMrlg126WoDw.jpeg</url>
            <title>Stories by Elmer  Enicky on Medium</title>
            <link>https://medium.com/@elmerenicky?source=rss-9ddef40ad1ba------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 03:45:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@elmerenicky/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[You Cannot Agent What You Have Not Mapped]]></title>
            <link>https://elmerenicky.medium.com/you-cannot-agent-what-you-have-not-mapped-7097a0fea84e?source=rss-9ddef40ad1ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/7097a0fea84e</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[agentic-ai]]></category>
            <dc:creator><![CDATA[Elmer  Enicky]]></dc:creator>
            <pubDate>Sun, 16 Aug 2026 17:32:57 GMT</pubDate>
            <atom:updated>2026-08-16T17:32:57.823Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BjPXBe7EPrj788puWPZ0DA.png" /></figure><h4>Why most AI transformations start with technology, when they should start with understanding work.</h4><p>For years, I believed AI transformation was primarily a technology challenge. Like many people working in this space, I assumed success depended on selecting the right large language model, building the right agents, integrating the right platforms and establishing the right governance. If we solved those problems, transformation would naturally follow. It seemed logical. After all, most conversations about enterprise AI begin with technology, so it was easy to believe that technology would also determine its success.</p><p>That assumption changed over the course of an enterprise AI transformation programme. I expected the biggest lessons to come from experimenting with models, designing agents or exploring new orchestration frameworks. Instead, the most important insight emerged from something far less technical. The breakthrough didn’t come from building a better AI capability. It came from asking a better question.</p><p>Every workshop followed a familiar pattern. Conversations quickly turned towards copilots, autonomous agents, orchestration platforms and the latest advances in large language models. The discussions were thoughtful, technically sophisticated and exactly what you would expect from an organisation making a serious investment in AI. Yet despite the quality of those conversations, I left each session with the same feeling that something important was missing.</p><p>While everyone had an opinion about artificial intelligence, almost nobody could confidently answer a much simpler question.</p><h4><strong>What work are we actually trying to transform?</strong></h4><p>At first, the question felt almost too obvious. Surely every organisation understands its own work. Yet the more we explored it, the more uncomfortable the answer became. Most organisations understand reporting lines, governance and documented processes remarkably well. What they often struggle to understand is how work actually happens how decisions are made, where knowledge moves, where effort is duplicated and where value is really created.</p><p>Ask ten experienced practitioners how they spend a typical Tuesday and you&#39;ll hear ten different stories. Not because anyone is wrong, but because work evolves much faster than documentation ever can. Process maps describe how organisations believe work happens. People describe how it actually happens. Between those two realities sits an enormous amount of hidden complexity.</p><p>The organisation certainly wasn&#39;t lacking ambition. There were copilots, proof-of-concepts, specialist AI tools and executive sponsorship. From the outside, everything looked exactly as you would expect from an enterprise embracing AI. Yet beneath that momentum sat a surprisingly uncomfortable truth.</p><p>Nobody could confidently explain how work actually flowed across the organisation.</p><p>Not the process.<br>The work.</p><p>Where did knowledge move? Which activities quietly repeated across different teams? Which decisions depended on human judgement? Which capabilities already existed but had never been recognised as reusable?</p><p>That was the moment our perspective changed not because the technology changed, but because the question changed.</p><h4><strong>Technology-first vs Work-first comparison</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PXQnLxpiHyQlYXwwg-CsGw.png" /></figure><p>Looking back, I believe that was the real beginning of the transformation. Instead of asking, <em>”What AI should we build?”</em>, we started asking, <em>“How does work actually create value?”</em></p><p>Everything that followed grew from that single shift in perspective. The obvious next step would have been to start designing AI agents. Instead, we found ourselves doing something quite different. We started trying to understand work not work as it appeared in process documentation, but work as it actually happened. The conversations, decisions, handovers and moments of judgement that quietly determine whether an organisation succeeds or struggles every single day.</p><p>Most organisations don’t suffer from a lack of AI ideas. They suffer from a lack of organisational visibility. Everyone understands their own role, but very few people understand how their work connects to the wider system. As organisations grow, teams become more specialised, responsibilities become fragmented and knowledge naturally disperses across functions.</p><p>Humans compensate remarkably well for that complexity. We ask colleagues for advice, build informal networks and rely on experience to bridge the gaps between formal process and reality.</p><p>AI doesn’t.</p><p>An AI system can only operate within the understanding we give it. If we cannot describe work consistently, we should not expect AI to perform it consistently. That realisation fundamentally changed how I think about enterprise transformation.</p><p>I had always believed AI would make organisations more intelligent. Increasingly, I began to realise that AI first forces organisations to understand themselves.</p><h4><strong>AI Amplifies What You Already Understand</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JfEvWUnrnvc2vPPOUr1jow.png" /></figure><p>As we continued mapping work, something unexpected emerged. Activities that initially appeared unique turned out to be remarkably similar across different teams. Capabilities thought to belong to one function quietly existed throughout the organisation. Knowledge that seemed highly specialised became reusable once viewed through the lens of capability rather than job title.</p><p>The conversations changed.<br>People stopped asking which AI agent they should build.</p><p>They started asking why three different teams were solving essentially the same problem in three different ways. That was a much better conversation. Not because it was about AI.<br>Because it was about the organisation.</p><p>Once work became visible, duplication became visible. Once duplication became visible, opportunities for reuse became obvious. Only then did conversations about automation begin to make sense.</p><p>One afternoon I stood in front of a wall covered with hundreds of mapped activities. Individually they looked insignificant reviewing requirements, facilitating workshops, documenting decisions, validating assumptions. Collectively, however, they revealed something much more powerful.</p><p>For the first time, we weren’t looking at projects. We were looking at how the organisation actually created value.</p><p>It was one of those rare moments when months of complexity suddenly collapsed into a single, simple insight.</p><blockquote><strong>We thought we were designing AI.<br>In reality, we were discovering the organisation itself.</strong></blockquote><p>That idea has stayed with me ever since.<br>Today, whenever someone asks me where an AI transformation should begin, I rarely start by talking about models, platforms or agents.</p><p>Instead, I ask a different question.<br><strong>How well do you understand the work you’re trying to transform?</strong></p><p>If the answer is uncertain, every conversation about AI that follows is built on assumptions rather than understanding. And assumptions rarely scale.</p><p>Technology has become remarkably good at generating answers. The organisations that will lead the next decade won’t necessarily have better AI.</p><p>They’ll ask better questions. Not, <em>”Which AI platform should we buy?”<br></em>But, <em>*”How does work actually create value here?”*</em></p><p>Because once you understand the work, everything else becomes easier.<br>Governance becomes clearer.<br>Capabilities become visible.<br>Value becomes measurable.</p><p>Only then does AI have something meaningful to amplify.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7097a0fea84e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beyond the Prompt: Why the Future of AI is Agentic, Not Generative]]></title>
            <link>https://elmerenicky.medium.com/beyond-the-prompt-why-the-future-of-ai-is-agentic-not-generative-78d2f80962bc?source=rss-9ddef40ad1ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/78d2f80962bc</guid>
            <category><![CDATA[agentic-ai]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Elmer  Enicky]]></dc:creator>
            <pubDate>Wed, 08 Apr 2026 10:30:54 GMT</pubDate>
            <atom:updated>2026-04-08T10:30:54.433Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/538/1*KqgCs33z9j22OAi0wJ7VLw@2x.jpeg" /></figure><p>I used to measure the success of a digital service by its “stability.” If the data moved from point A to point B without the system crashing, we called it a win. We built the forms, set up the validation rules, and patted ourselves on the back when the “Submit” button did exactly what it was told.</p><p>But as we move into the era of <strong>Generative AI</strong>, I’ve realized that our traditional systems are fundamentally flawed. They are technically perfect, but humanly exhausting.</p><h3><strong>The “Mop and Bucket” Strategy</strong></h3><p>Think about the last time you used a complex digital service. You fill out ten fields, hit submit, and – boom – a red error message tells you that “Field 4 is invalid.”</p><p>This is the “Passive Processor” model. The system watches you make a mistake and waits until you are finished to tell you about it. It’s the digital equivalent of a teacher watching you take an entire exam, only to tell you once you’ve handed it in that you used the wrong color ink.</p><p>In many high-volume services, we see “green” technical metrics masking a sea of human friction. We end up using a mop and bucket – support teams and manual rework to clean up a floor while the tap is still running wide open at the point of input.</p><h3>The Shift to Agentic Workflows</h3><p>The revelation isn’t just that AI can “generate” text; it’s that it can <strong>reason</strong> through a process. We are moving away from passive interfaces toward <strong>Agentic Workflows.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*r-BTOiXh9Jn3Ifm3m7zZTQ@2x.jpeg" /></figure><p>In an agentic system, the AI isn’t just a chatbot sitting in a sidebar; it is an active participant in the journey. It uses<strong> Generative UI</strong> to adapt the interface to the user’s specific context. It employs <strong>reasoning loops</strong> to sense when a user is hesitating and provides the exact nuance needed to move forward.</p><p>By moving this “intelligence” upstream, we change the nature of the interaction. The system isn’t just a gatekeeper anymore; it’s an <strong>Autonomous Agent</strong> that:</p><ul><li><strong>Anticipates Intent:</strong> Sensing the “why” behind the data before it’s even typed.</li><li><strong>Self-Corrects: </strong>Catching misalignments in real-time through background reasoning.</li><li><strong>Orchestrates Outcomes:</strong> Navigating the complex back-office logic so the user doesn’t have to.</li></ul><h3>Total Enterprise Reinvention</h3><p>The goal of modern digital transformation isn’t just “efficiency.” Efficiency is just doing the wrong thing faster.</p><p>The real value of Gen AI isn’t in its ability to write poems; it’s in its ability to <strong>influence decisions where they are still flexible.</strong> When we build agentic architectures, we aren’t just automating a task; we are redesigning the relationship between humans and machines.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/557/1*gkUWdr1hQWYQhOWNHef7ug@2x.jpeg" /></figure><p>The system stops being a hurdle the user has to jump over and starts being a partner that walks beside them. It becomes <strong>coherent</strong>.</p><h3>Final Thought</h3><p>The next time we sit down to design a service, we shouldn’t ask, “How do we automate the back office?”</p><p>We should ask: <strong>“How do we use Agentic AI to ensure the back office never needs to see this in the first place?”</strong></p><p>That is where the real transformation happens. Not in the output, but in the architecture of the influence.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78d2f80962bc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My UX design journey with GDS and the GOV.UK prototyping kit]]></title>
            <link>https://medium.com/kainosxd/my-ux-design-journey-with-gds-and-the-gov-uk-prototyping-kit-c4827d2a033c?source=rss-9ddef40ad1ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4827d2a033c</guid>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[gds-system]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[accessible-design]]></category>
            <dc:creator><![CDATA[Elmer  Enicky]]></dc:creator>
            <pubDate>Tue, 26 Mar 2024 09:57:42 GMT</pubDate>
            <atom:updated>2024-03-26T16:23:09.990Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*peOWEAM6YOhJ1XuPXWF8HA.jpeg" /></figure><p>Hey there! I’m Elmer, and for the past 18 months, I’ve been immersed in <a href="https://design-system.service.gov.uk/">UK Government Digital Service (GDS)</a> projects through Kainos. Let me take you through how my encounter with GDS and the GOV.UK prototyping kit has been nothing short of transformative to my perspective on design.</p><h3>Learning to love the GDS approach to design</h3><p>When I first stepped into a project which followed the <a href="https://www.gov.uk/service-manual">GDS standard</a> I’ll be honest, I had my doubts. I wondered if there was any room for creativity in what seemed like a pretty rigid framework. And, following established standards felt a bit daunting. But as I got deeper into my role, I had this “aha” moment. I realised that being a UX designer in this context was actually a golden opportunity, not a limitation.</p><p>Sure, those GDS standards seemed a bit strict at first, but I quickly understood their benefit. In a world where flashy trends often overshadow practicality, sticking to GDS standards means focusing on what really matters: making things work seamlessly for users.</p><p>Along my GDS journey, I’ve picked up 6 key lessons.</p><h4>1. Put users first</h4><p>GDS standards constantly remind us to centre our design decisions around what users actually need. By keeping things accessible and easy to use, we ensure that our digital services truly serve the people.</p><h4>2. Find the balance between looks and functionality</h4><p>Coming from a graphic design background, I’ve always had an eye for aesthetics. But my time with GDS standards has highlighted the importance of finding that sweet spot between looks and functionality. While a snazzy colour scheme is nice, it’s worthless if it gets in the way of users getting stuff done. So instead of chasing after every passing trend, I’ve learned to focus on crafting interfaces that are intuitive and work well.</p><h4>3. Less is more</h4><p>Simplifying things doesn’t mean sacrificing creativity. It’s about cutting out the clutter to make interfaces clear, intuitive, and a breeze to navigate. We should never forget that users do not visit our products to admire our designs but to complete a task.</p><h4>4. Consistency is king</h4><p>Following GDS standards means government digital services are consistent across the board. This builds trust with users and makes their lives easier by giving them a familiar experience every time they interact with GOV.UK.</p><h4>5. Teamwork makes the dream work</h4><p>Designing isn’t a solo act. It’s all about collaborating with stakeholders, developers, and end-users to create solutions that meet user needs, and which can be implemented easily.</p><h4>6. The GOV.UK prototype kit impacted my work</h4><p>Let me tell you about my experience with the <a href="https://prototype-kit.service.gov.uk/docs/">GOV.UK Prototyping Kit</a>. It completely changed my approach to design. Initially, its promise of minimal coding requirements intrigued me, but its impact surpassed my expectations.</p><p>As I delved into prototyping with the kit, I realised the importance of UX designers learning technical knowledge.</p><p>For example, understanding accessibility requirements and technical constraints for different elements, including:</p><ul><li>labels</li><li>legends</li><li>hidden text</li></ul><h4>Benefits of the GOV.UK prototype kit for my work</h4><p>Learning to create coded prototypes showed me how to:</p><ul><li>design for users of assistive technology</li><li>improve my communication with the development team</li><li>understand and appreciate project constraints</li></ul><p>Embracing the GOV.UK Prototype Kit has elevated my technical proficiency as a UX designer. It has also inspired my desire to delve deeper into coding and website mechanics.</p><h3>Concluding my GDS journey</h3><p>In essence, my journey with GDS and the GOV.UK prototyping kit has been eye-opening. This is because I have embraced design and development standards that prioritise practicality, accessibility, collaboration and meeting user needs.</p><p>I firmly believe that GDS serves as a valuable reference point for designing any product, offering invaluable insights and guidance.</p><p>Here are a few things to help you on your design journey:</p><ul><li><a href="https://www.craigabbott.co.uk/">The website of accessibility specialist Craig Abbott</a></li><li><a href="https://adamsilver.io/newsletter/">Newsletter of Adam Silver, UX designer</a></li><li><a href="https://x-govuk.github.io/">X- GOV.UK’s community design resources</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4827d2a033c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kainosxd/my-ux-design-journey-with-gds-and-the-gov-uk-prototyping-kit-c4827d2a033c">My UX design journey with GDS and the GOV.UK prototyping kit</a> was originally published in <a href="https://medium.com/kainosxd">Kainos Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Embracing green software development: How UX designers can contribute to a sustainable future]]></title>
            <link>https://medium.com/kainosxd/embracing-green-software-development-how-ux-designers-can-contribute-to-a-sustainable-future-62a54a05310f?source=rss-9ddef40ad1ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/62a54a05310f</guid>
            <category><![CDATA[green-ux]]></category>
            <category><![CDATA[kainos]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[green-software]]></category>
            <dc:creator><![CDATA[Elmer  Enicky]]></dc:creator>
            <pubDate>Mon, 31 Jul 2023 15:10:54 GMT</pubDate>
            <atom:updated>2023-07-31T15:10:54.618Z</atom:updated>
            <content:encoded><![CDATA[<h4>Plus actionable tips for your contribution</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v9tQRlWSX4kaNnlVYAdYWA.png" /></figure><h4>Introduction</h4><p>In today’s digital world, technology has become a powerful tool that influences our daily lives and shapes our future. As the focus on sustainable practices increases, green software development emerges as a vital factor in reducing our environmental impact. At <a href="https://www.kainos.com/about-us/sustainability/green-software">Kainos</a> we are committed to reducing the environmental impact of our software and its UX designers play a significant role in fostering software development. Let’s dive into the ways UX designers can craft energy-efficient and environment-friendly software solutions.</p><h4>Building on green foundations: Sustainable design principles</h4><p>Using sustainable design principles as a blueprint, Kainos’ UX designers can significantly minimise the environmental footprint of the software they develop. By focusing on usability, efficiency, and modularity, they ensure that the software embodies sustainability from the get-go. Here’s how it works:</p><ul><li>Use easy-to-grasp design patterns and straightforward language to enhance user experience and lessen the need for extensive support resources.</li><li>Create designs that demand less from computing resources. This might involve using optimised images and leveraging lazy loading techniques to reduce energy use. It’s a win-win approach, elevating user experience while also helping mother nature.</li></ul><h4>User-centred design: Making users the priority</h4><p>The user-centred design (UCD) approach puts users and their needs in the limelight. This strategy enables UX designers to create streamlined and user-friendly applications that also consume less energy and resources.</p><p>For instance, if users are having a tough time finding a certain feature, the designer can make it more prominent, reducing the energy and time spent hunting it down</p><h4>Efficient and Accessible: Crafting User-Friendly UI Design</h4><p>Creating a robust user interface is key to accessibility and responsible use of computer resources. By removing superfluous graphical elements, animations, and transitions, designers can optimise software performance, reduce energy use, and make applications friendlier for a variety of devices.</p><p>For example, Responsive Design. By making sure the user interface adjusts to different screen sizes and orientations, software becomes accessible across all devices, from smartphones to desktops, while also optimising resource use. It’s an approach that boosts user experience, software performance, and energy efficiency.</p><h4>Collaboration with development teams: Bridging the gap</h4><p>Through close collaboration with development teams, UX designers can ensure that green design decisions become real-world software solutions. Together, they can foster energy-saving coding practices, giving rise to software that cares for our planet.</p><p>This mutual understanding is crucial. UX designers can explain their green design choices, and developers can share the technical constraints or opportunities that could influence these decisions. This synergy paves the way for more energy-efficient solutions and embeds sustainability in every corner of the software development process.</p><h4>Continuous improvement &amp; education: Keeping up with best practices</h4><p>Being a UX designer at Kainos, it’s crucial to stay abreast of sustainable practices and disseminate this knowledge among the team. This role involves fostering an environment of continuous learning and knowledge exchange, which contributes to the establishment of a culture of sustainability and responsibility within the organisation. This commitment to sustainability is further exemplified in <a href="https://www.kainos.com/about-us/sustainability/green-software">Kainos</a>’ green software articles, which I would suggest to all practitioners.</p><h4>Inclusive design &amp; accessibility: Fostering a green mindset</h4><p>Inclusive design and accessibility sit at the heart of green software development. By integrating these principles and fostering collective efforts, Kainos is making significant strides in adopting sustainable development practices.</p><p>But remember, green software development isn’t just about shrinking environmental impact. It’s about building software that everyone can use. By making software accessible, we’re opening digital doors for people with diverse abilities, making digital inclusivity a reality.</p><h4>Conclusion</h4><p>UX designers can make a real difference in green software development by bringing sustainability, accessibility, and inclusive design to the forefront of their work. By joining forces, we can magnify our efforts and accelerate the drive towards a greener future.</p><p>Together, we will harness the power of innovative strategies and foster seamless collaboration with development teams, aiming to create a digital landscape that prioritises environmental responsibility.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=62a54a05310f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kainosxd/embracing-green-software-development-how-ux-designers-can-contribute-to-a-sustainable-future-62a54a05310f">Embracing green software development: How UX designers can contribute to a sustainable future</a> was originally published in <a href="https://medium.com/kainosxd">Kainos Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Once Upon a Time in Kainos: How Parenthood Transformed My UX Design Journey]]></title>
            <link>https://medium.com/kainosxd/once-upon-a-time-in-kainos-how-parenthood-transformed-my-ux-design-journey-f66fa25265d2?source=rss-9ddef40ad1ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/f66fa25265d2</guid>
            <category><![CDATA[parenthood]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[professional-growth]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Elmer  Enicky]]></dc:creator>
            <pubDate>Tue, 11 Jul 2023 08:43:19 GMT</pubDate>
            <atom:updated>2023-07-11T08:43:19.325Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f1c7kOf6kYxoFR1kodivng.png" /><figcaption>Image: My first day as UX Designer at Kainos</figcaption></figure><p>Once upon a time, on a special day in September 2022, something remarkable happened. My second child was born, coinciding with the beginning of my thrilling adventure into the world of user experience (UX) design. Little did I know that this life-altering moment would not only transform my personal life but also profoundly enrich my skills as a graduate UX designer.</p><p>As I started my career in UX design at Kainos, I discovered a work culture that nurtured and supported me, laying the foundation for my growth. Kainos, with its flexible approach, provided the space and understanding I needed to thrive as both a parent and a designer. It was the perfect environment where I could develop my skills while being there for my growing family.</p><h4>Awakening empathy</h4><p>Parenthood, with its sleepless nights, tender cries, and joyful laughter, has awakened a newfound sense of empathy within me. These experiences as a parent have opened my heart to a deeper understanding of human needs, extending beyond the realm of parenthood and enriching my professional life as a UX designer. I have come to realize that in order to create truly meaningful user experiences, I need to step into the shoes of my users and empathize with their desires, frustrations, and dreams. Parenthood has given me a gift: an enhanced ability to empathize. This newfound perspective has empowered me to incorporate a diverse array of viewpoints into my design approach.</p><h4>Parenthood and problem-solving</h4><p>The challenges of parenthood, from deciphering a baby’s cries to navigating the complexities of a newborn’s and a toddler’s emotions, sharpened my problem-solving skills. The iterative problem-solving mindset instilled in me through parenthood seamlessly transferred into my design process. I learned to approach design challenges with curiosity, embracing trial and error as stepping stones toward innovation. Parenthood taught me that every problem has a solution, waiting to be discovered through persistence and resilience.</p><h4>The Power of Simplification</h4><p>In the whirlwind of parenthood, I discovered the power of simplification. Managing a household and caring for a child demanded a streamlined approach to tackling complex tasks. Through the lens of parenthood, I learned to identify what truly matters. As designers, we often find ourselves caught between business requirements and technical capacity, though the most important aspect is meeting our users’ needs and addressing the right problem. Stripping away unnecessary complexities and focusing on the core elements became crucial. This newfound skill has become an integral part of my UX design philosophy. I realized that by simplifying user experiences, removing barriers, and reducing cognitive load, I can create designs that effortlessly guide users towards their goals.</p><h4>Time Management Superpowers</h4><p>The demands of parenthood also taught me the art of time management. Balancing parental responsibilities with project deadlines required careful planning, prioritization, and adaptability. I became a master of multitasking, a skill that seamlessly transitioned into my professional life as a UX designer. The ability to efficiently manage my time allowed me to meet project milestones without compromising the quality of my work. Parenthood had equipped me with a superpower — a time-turner that allowed me to gracefully navigate the intricate dance between parenthood and design.</p><h4>Patience as a design virtue</h4><p>Patience, the unsung hero of parenthood, revealed its profound significance in the realm of UX design. From the countless nights spent soothing a crying baby to the toddler tantrums that tested my resolve, I learned the art of patience. This quality became my guiding light as a UX designer. I understood that creating exceptional user experiences required meticulous attention to detail, countless iterations, and unwavering dedication. Parenthood had bestowed upon me a wellspring of patience, nurturing my ability to iterate and refine my designs until they reached latest best version.</p><h4>Embracing the intersection of parenthood and professional growth in UX design</h4><p>In conclusion, my journey into parenthood, intertwined with my career at Kainos, has shaped me into a more empathetic, intuitive, and skilled UX designer. The supportive work culture at Kainos allowed me to embrace both my role as a parent and a designer. Parenthood enhanced my UX design skills by instilling empathy, fostering iterative problem-solving, emphasizing simplification, teaching effective time management, and nurturing patience. It is a testament to the remarkable growth and success that can arise at the intersection of personal and professional development.</p><h4>Unleashing the Magic of Parenthood in UX Design</h4><p>Let the magic of parenthood unlock hidden depths within you, shaping you into a more empathetic, intuitive, and skilful UX designer.</p><p>May your journey be filled with wonder, inspiration, and the ever-present reminder that the most extraordinary stories are often found at the crossroads of personal and professional growth.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f66fa25265d2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kainosxd/once-upon-a-time-in-kainos-how-parenthood-transformed-my-ux-design-journey-f66fa25265d2">Once Upon a Time in Kainos: How Parenthood Transformed My UX Design Journey</a> was originally published in <a href="https://medium.com/kainosxd">Kainos Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ancient Greece: The inspiration behind modern UX design.]]></title>
            <link>https://medium.com/kainosxd/ancient-greece-the-inspiration-behind-modern-ux-design-aab7f838025a?source=rss-9ddef40ad1ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/aab7f838025a</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[iterative-design]]></category>
            <category><![CDATA[user-centered-design]]></category>
            <dc:creator><![CDATA[Elmer  Enicky]]></dc:creator>
            <pubDate>Thu, 01 Jun 2023 16:14:38 GMT</pubDate>
            <atom:updated>2023-06-01T16:14:38.650Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E-VYJiYujFrM-8x-SQzZ4Q.png" /></figure><p>When we think of ancient Greece, we often imagine its contributions to science, art, philosophy, and architecture. But did you know that the ancient Greeks were also way ahead of their time when it came to ergonomics and design?</p><h3><strong>User-centred design and Hippocrates</strong></h3><p>In the 5th century BC, a Greek physician named Hippocrates recognized the importance of designing tools that were not only comfortable but also safe for human use. He believed that well-designed tools could enhance efficiency and prevent injuries. For instance, in his blueprint for hospitals, Hippocrates outlines methods for creating the most optimal and comfortable working conditions for medical professionals. Additionally, ergonomic considerations can be seen in the design of bench seating in ancient Greek theatres. This design choice enhanced blood flow in the legs of audience members, preventing numbness that could have resulted from extended periods of sitting during theatre performances. This user-centric approach to design is still at the core of modern UX design. Today, UX designers aim to create products and services that are easy to use and meet users’ needs.</p><h3><strong>Aesthetics and the Golden Ratio</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Iuvikzq2JZBgPPbcrdftuQ.png" /></figure><p>The ancient Greeks had a remarkable eye for aesthetics. They believed that the most pleasing designs followed the Golden Ratio, a mathematical principle found in nature and art. Even today, UX designers use the Golden Ratio to craft visually appealing and <a href="https://www.nngroup.com/articles/golden-ratio-ui-design/">user-friendly layouts and interfaces</a>.</p><h3>Simplicity and clarity</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pp6Ie9FRj1fGz-7Srkj1PA.png" /></figure><p>Simplicity and clarity were highly valued in ancient Greek design. They believed that the best designs were those that were easy to comprehend and navigate. This principle remains evident in modern UX design, where simplicity and clarity are essential. When a design is clean and straightforward, users can quickly understand and enjoy using it. An example of Greek simplicity is the lever, which was first described by Archimedes in 206 B.C. This invention revolutionized construction and even aided in setting ships to sail.</p><h3>Iterative design processes</h3><p>The ancient Greeks were masters of iterative design. They would create prototypes and models of their designs, testing them to gauge their functionality. This iterative approach is still employed by UX designers today. Through wireframes, mock-ups, and prototypes, they ensure usability and meet users’ needs before launching a product or service.</p><h3>Applying Ancient Greek principles to your UX design</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SkFAprJTzXlHNrD9lw8daw.png" /></figure><p>To apply these ancient Greek principles to your own UX design, consider the following tips:</p><p>1. Prioritise the user: Always keep the user at the forefront of your design process. Understand their needs and pain points and strive to make their experience as effortless and enjoyable as possible.</p><p>2. Harness the Golden Ratio: Use this powerful tool to create aesthetically pleasing and functional designs. Seek balance and visual harmony in your layouts and interfaces.</p><p>3. Embrace simplicity: The best designs are often the simplest ones. Avoid clutter and complexity, ensuring that your designs are easy to comprehend and navigate.</p><p>4. Test and iterate: Don’t assume your designs are user-friendly. Test them with real users to gather feedback and identify any usability issues. Continuously improve and refine your designs.</p><p>By following these tips, you can infuse your UX designs with the spirit of ancient Greek wisdom. Your designs will become user-centric, visually appealing, and easy to use.</p><h3>In Conclusion</h3><p>The ancient Greeks left an enduring legacy in ergonomics, which continues to shape modern UX design. Through their emphasis on user-centred design, simplicity, clarity, and the application of the Golden Ratio for visual harmony, we can learn valuable lessons in creating seamless digital experiences. By using the foundational principles of Greek ergonomics, modern UX designers can elevate their designs and increase the success of their products and services. As we continue to innovate in UX design, we can look to the ancient Greeks as pioneers of human-centred design and draw inspiration from their timeless principles.</p><p>Let’s learn from the ancient Greeks and create UX designs that truly resonate with users.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aab7f838025a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kainosxd/ancient-greece-the-inspiration-behind-modern-ux-design-aab7f838025a">Ancient Greece: The inspiration behind modern UX design.</a> was originally published in <a href="https://medium.com/kainosxd">Kainos Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>