<?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 Jeong-sook Lee on Medium]]></title>
        <description><![CDATA[Stories by Jeong-sook Lee on Medium]]></description>
        <link>https://medium.com/@beauttari?source=rss-6b7fad43264c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Q3ZDGilT-VgvvlgVv9RKyg@2x.jpeg</url>
            <title>Stories by Jeong-sook Lee on Medium</title>
            <link>https://medium.com/@beauttari?source=rss-6b7fad43264c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 21:23:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@beauttari/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[Design with Beginner’s Mind.]]></title>
            <link>https://medium.com/sap-design/design-with-beginners-mind-c16bc8f0ef4e?source=rss-6b7fad43264c------2</link>
            <guid isPermaLink="false">https://medium.com/p/c16bc8f0ef4e</guid>
            <category><![CDATA[design-culture]]></category>
            <category><![CDATA[designer]]></category>
            <category><![CDATA[slow-design]]></category>
            <category><![CDATA[mindful-design]]></category>
            <category><![CDATA[enterprise-design]]></category>
            <dc:creator><![CDATA[Jeong-sook Lee]]></dc:creator>
            <pubDate>Thu, 10 Jan 2019 17:07:15 GMT</pubDate>
            <atom:updated>2021-10-21T23:06:56.646Z</atom:updated>
            <content:encoded><![CDATA[<h3>Design with a Beginner’s Mind</h3><p><strong>Why design culture matters for enterprise software.</strong></p><p>A few summers back, I was riding on horseback through the deep mountains of Kyrgyzstan with a young local woman. She said, “When I was a little girl, I always wondered what would be behind these high mountains.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*-ctAqiTijDhiJrAohHRb9g.jpeg" /></figure><p>“Did you find the answer?” I asked, intrigued.</p><p>“Yes, I did. It’s another mountain,” she answered with a shrug and a smile.</p><p>How true. There’s always another mountain. That’s how things turn out every day at work. My entire career has been this way. Lao Tzu couldn’t have put it any better.</p><h3>Why design culture?</h3><p>I wasn’t always conscious about how a design culture affected product quality. While designing enterprise software, it quickly became clear to me, that technology or A+ design concepts alone cannot make a great product. Imagine the complexity and scale enterprise software has. We design large scale products with long product lifecycles with high dependencies. No single step from design to implementation can be done without a broad collaboration across different teams and organizations. Our designs undergo a long buy-in, tedious alignment processes and often painful trade-offs along the way of productization. When individual product or designer competes to outsmart other solutions and work in silos, we end up creating a bunch of inconsistent designs, which would make our users to pause and wonder. Design details out of an immature decision-making culture fail to communicate the design intention to users and thus confuse them. A vague product vision or insufficient understanding of the product leads us to change our designs back and forth, and the product ecosystem will suffer.</p><h3><strong>How we build is as important as what we build.</strong></h3><p>A healthy design culture seeks the right problems to solve and challenges today’s solutions constantly. It turns disagreements into constructive iterations, convert failures into opportunities, and grows ideas into the products.</p><blockquote><strong>Design slow.</strong></blockquote><p>A healthy design culture has a long breath. This allows us to tackle long winded design processes without being exhausted on the way, forgetting the vision, or losing the flexibility to reorientate and readjust the goal on the way. It helps us approach every step of design mindfully without being carried away or rushed. We can always step back and revisit the problem without jumping into solutions too early.</p><blockquote>“<strong>Are we solving the right problems? Will this be still a problem, when things around it change?”</strong></blockquote><p>Down the line, taking time in each step saves us a lot of time, energy, and disruptions. Slower is faster. It also allows us to solve local problems and benefit the whole at the same time.</p><blockquote><strong>Design with a beginner’s mind.</strong></blockquote><p>A healthy design culture also encourages <strong>design with accountability. </strong>It provides an environment where we can try out new things without fear, and allows us to fail and fix our own failures afterwards. It’s not about making right decisions all the time. It’s about failing better — making sure that we learn from the conclusions and decisions we made. Over time, we not only learn how to fix problems but also how to outgrow them.</p><p>That’s how we <strong>build our endurance and sovereignty, </strong>which brings harmony to our intentions and actions, <strong>harmony to vision and products. </strong>A healthy design culture will create solutions that are well thought through and add tangible values to the users, rather than fixing something in hurry and causing new problems elsewhere.</p><blockquote><strong>Allow time to mature.</strong></blockquote><p>A design culture cannot be created overnight. Nor can it be created by a selected handful of people. A healthy design culture is not a magic, but a continuous observation and iteration of every details of our daily interaction. A culture needs to be lived and practiced daily. It mandates mindfulness of everyone. It calls for beginner’s mind. It needs grit.</p><p>Throughout my design career, certain products made me particularly curious about the people behind them. First of all, they must have had a great time making them. From the outside you can see the enthusiasm, and the collective momentum the team must have had. Second, the indefatigable boldness and product quality they carried through the product evolution. They must have had strong tradition and leadership capable of reading the time and re-interpreting their product/brand vision. Be it a magazine, restaurant, bank, school, hardware or software. You can see how they dealt with the time and technology for their business. Some of them kept renovating their processes, products and services with a continuous momentum. Some of them struggled to make it. Some of them didn’t care at all. We can tell who “evolved the tradition” and executed it with untiring passion, and who played catchup. The philosophy and culture behind their product journey came across through their products. It’s not only the products they created, but also their sovereignty over their products that inspires us.</p><p><strong>Design culture </strong>is to me the philosophy that nurtures the right attitude, behavior and discipline. Design culture is also the environment that shapes the interpersonal dynamics between people and paces their work from ideation to productization. Design is, after all, all about people.</p><p><a href="https://medium.com/sap-design/design-like-a-landscaper-15878c2886ac">Design like a landscaper.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c16bc8f0ef4e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sap-design/design-with-beginners-mind-c16bc8f0ef4e">Design with Beginner’s Mind.</a> was originally published in <a href="https://medium.com/sap-design">Experience Matters</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Like a Landscaper.]]></title>
            <link>https://medium.com/sap-design/design-like-a-landscaper-15878c2886ac?source=rss-6b7fad43264c------2</link>
            <guid isPermaLink="false">https://medium.com/p/15878c2886ac</guid>
            <category><![CDATA[complexity]]></category>
            <category><![CDATA[designer]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[enterprise-design]]></category>
            <dc:creator><![CDATA[Jeong-sook Lee]]></dc:creator>
            <pubDate>Mon, 07 Jan 2019 13:15:30 GMT</pubDate>
            <atom:updated>2021-10-21T23:07:19.082Z</atom:updated>
            <content:encoded><![CDATA[<h3>Design Like a Landscaper</h3><p><strong>Why enterprise software design is a different genre.</strong></p><blockquote>During my days as a design student, and later while working at design agencies, I used to believe that good design sprung from natural-born talent, a prestigious education, and fast foot work with prominent clients. I spent days, nights, and weekends on countless quick turnarounds. Successful customer pitches made me feel competent and accomplished. After each quick delivery, I would dive into the next project as fast as possible.</blockquote><blockquote><strong>That all changed, when I started working on enterprise software.</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Hg8Udbn2Hvv5Rc_LpPmDrg.jpeg" /></figure><h3><strong>Enterprise software design is like landscaping.</strong></h3><p>In parks or gardens, every plant is unique with different life-cycles. Some grow faster than others, some grow higher, some even grow on the stem of another plant. Enterprise design is no different. Both gardens and enterprise design require long-term thinking and have short term needs. Enterprise design is crafting the experience throughout the year, catering all different business domains with various unique needs over many years.</p><p>It is a fundamentally <strong>different job than a florist </strong>who makes beautiful bouquets. Bouquets may have a high “wow” factor, but they also have a short shelf life. The same goes with a designer making a stand-alone, quick turnaround or short term project — they may serve an immediate need, but how will the solution grow and integrate with innovations in the future?</p><p>Landscaping needs careful planning based on the knowledge of each plant and its best soil. It needs dedication. It needs continuous nurture. Some plants need more sun, and some need less water. Some lose their leaves in autumn and others are evergreen. It needs a prudent observation over time how they grow together. Introducing a new plant needs an accurate assessment on its impact on the ecology and the overall experience of the garden. Of course, it does not and should not exclude any options for remodeling and metamorphizing. All that matters is when and how.</p><p><strong>Designing large scale products with long life cycles was an entirely different challenge.</strong> It is designing the time. We fix acute issues that pop up for both old and new applications. We constantly renovate existing applications with more features and additional functionality. We also introduce a brand new, modern framework. Anything new should be compatible with old solutions. Any new feature should not contradict the existing infrastructure, nor should it disrupt the entire product ecosystem. One careless design change can fundamentally damage the consumer experience due to hidden dependencies in the existing solution. After countless cycles of trial and error over many years, reoccurring patterns of problems emerge. Over time we learn what the dependencies are and understand how they evolve in growing complexity.</p><h3><strong>Enterprise software design changed me, will change you.</strong></h3><p>Once you have experienced large-scale framework design, you would never design anything without considering the changing complexity of a growing system. You will always question how it will grow in the years to come and plan for it to scale and integrate with other systems. After all, all the small pieces need to work together.</p><p><strong>My belief about great design has changed, too. </strong>The florist who makes beautiful bouquets that will be thrown away tomorrow is gone. Now, I design for<strong> </strong>today, tomorrow and the years to come. Without a strong vision and determination, a design, no matter how great it is, won’t survive the long-winded process. Brilliant ideas can often die before they are given a chance to flourish. For these great seeds to germinate and grow, they need to have tenacity to undergo a long buy-in, tedious alignment processes and often painful trade-offs along the way to productization. I believe, a strong vision of your enterprise design garden in the coming years and the passion to make the vision come true, will generate the energy and endure to the launch of the product.</p><p><strong>Great design solves the right problems. </strong>When we are too busy fixing immediate local problems, we tend to lose the sight of our big picture. When we rush to control the damage, we forget to question whether we are fixing the right problems. If we are too careful not to break the present, we overlook that we are breaking the future with today’s quick fixes. We often forget that the solutions used to solve yesterday’s problem won’t always solve the problems of tomorrow. Allowing time to seek the right problems to solve and to plan when and how to evolve the system is the essence of designing a complex ecosystem, designing the time.</p><blockquote><strong>As I reflect, I enjoyed my transformation from a florist to a gardener. </strong>My job is to design a beautiful journey throughout the year, dealing with things that are totally out of our control. My garden survives hard winds and cold winters and brings about great fruits the following year. It offers a journey that is never the same. It is different kind of design. It is not only the products and artifacts, it is also the process and people you meet on the way. The landscape of enterprise software design changes, and we need to design differently. We need to design the time.</blockquote><p><a href="https://medium.com/sap-design/design-with-beginners-mind-c16bc8f0ef4e">Design with beginner’s mind.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15878c2886ac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sap-design/design-like-a-landscaper-15878c2886ac">Design Like a Landscaper.</a> was originally published in <a href="https://medium.com/sap-design">Experience Matters</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>