<?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 Yoon Lee on Medium]]></title>
        <description><![CDATA[Stories by Yoon Lee on Medium]]></description>
        <link>https://medium.com/@yoondesigns?source=rss-6cc8348ddf2b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Xlvr0etFQAi4VoTFOsvsqA.jpeg</url>
            <title>Stories by Yoon Lee on Medium</title>
            <link>https://medium.com/@yoondesigns?source=rss-6cc8348ddf2b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 13:38:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yoondesigns/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[Creating Efficient Designer and Developer Collaboration]]></title>
            <link>https://medium.com/gskinner-team/creating-efficient-designer-and-developer-collaboration-886175ecfd3a?source=rss-6cc8348ddf2b------2</link>
            <guid isPermaLink="false">https://medium.com/p/886175ecfd3a</guid>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[designer]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[work-culture]]></category>
            <dc:creator><![CDATA[Yoon Lee]]></dc:creator>
            <pubDate>Tue, 24 Mar 2020 14:09:08 GMT</pubDate>
            <atom:updated>2020-03-24T14:09:08.227Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OSjwNPx2uInC_7-ISAvsPg.jpeg" /></figure><p>It’s already been 2 months since our team finished the <a href="http://flutter.gskinner.com/">Flutter Vignette project</a> and gave a <a href="https://youtu.be/1AxXF038-lY">talk at Flutter Interact </a>’19. Throughout the project, we were able to maintain a healthy designer-developer relationship, which was the key to the successful completion of the project. I want to share 5 things that helped us build an effective and efficient collaboration between designers and developers.</p><h3>#1. Be in constant communication.</h3><p>A failure to communicate can lead to a lot of misunderstandings and even different interpretations of the same general goals. To avoid that, we constantly shared thoughts and progress with the team when there was any major progress or change in an individual’s work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xGt9QqbADsJtNp7K5_59UA.jpeg" /><figcaption><em>Our team discussing ideas</em></figcaption></figure><p>For instance, when a good idea rushed upon my mind, I made quick sketches. I shared them in a dedicated project channel and got instant feedback on them. Developers advised me whether the idea would be feasible or not from their perspective. The entire team talked about how to make the experience better. Free-form, low-fidelity exchange of ideas can help get everyone aligned before over-investing in a concept, or direction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lrTuH7UXAD0h9Xp0VKKPwA.jpeg" /><figcaption><em>Daily status report on Slack</em></figcaption></figure><p>Posting a daily status at the end of a day also helped us keep track of what everyone was working on. It’s also a good place to surface when you’re blocked or waiting on feedback. Having weekly sync enabled us to see a bigger picture of the project; what happened, what’s happening now, and what’s happening next.</p><p>Being in constant communication within the team generated a significant synergy effect by reducing the possibility of misinterpretation and amplifying the possibility of great ideas.</p><h3>#2. Set a smart project folder system.</h3><p>As a designer who works closely with developers, it is my job to prepare all the assets and locate them in a place where developers can easily find them. The most basic rule is to set up a smart project folder system by organizing your assets into logical subfolders and layers with descriptive names. Icon 1 is not helpful. Label them according to what is contained therein.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rzyk1rgS2DsbKJxqu6zf_g.png" /><figcaption><em>A folder structure on the Flutter Vignette project</em></figcaption></figure><p>Each vignette has its dedicated folder with its official vignette name. In each of the folders, there are _assets and _motion subfolders. This is where you can find all the assets for each vignette and animation files you can use as a reference for motion. Keeping a consistent folder structure makes searching for files easier and faster. No matter which vignette you are working on, it is obvious where to look for files.</p><p>We also kept vignette folders that had unfinished design under _In Progress. The folders are migrated into the main Design folder when the design was finished. In that way, developers were able to know which vignette they could start working with. These principles can be applied to any type of project.</p><p>A good, organized catalog of assets and relevant resources makes it easy for any team member to understand where everything is stored and speeds-up work.</p><h3>#3. Communicate with low-fidelity sketches and wireframes.</h3><p>Do you ever spend an overwhelming amount of time and resources designing something that a client or developer turns down in a matter of seconds? It has happened several times in my life. It’s not a pleasant thing to go through, but yet preventable. How? Stay to a lower fidelity when presenting ideas to your team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QKqNktaQo4yDWpZ7Mpt6iQ.jpeg" /><figcaption><em>I like to sketch to present my ideas, but do what’s most comfortable for you!</em></figcaption></figure><p>We always started with low-fidelity sketches before further developed an idea. A benefit of communicating with sketches was the ability to quickly iterate on ideas because the effort and resources required to produce sketches were significantly low. It allowed us to detect and tackle problems in the early stages which prevented them from becoming larger issues in the future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*UEelq-kFKRBogm5hMFuaiw.gif" /><figcaption><em>Low fidelity wireframe with motion</em></figcaption></figure><p>Building a low-fidelity wireframe was also an important part of our process. Instead of making developers just wait until designers hand over the final design, developers could use the wireframe as a reference and start building basic structure and testing while designers finished the design. In this way, we were able to work at greater efficiency.</p><h3>#4. Use tools to make handoff faster.</h3><p>Back in the old days, designers had to manually prepare all the necessary assets and a style guide for developers. Not only did that take a lot of time, but also it was easy to leave something out. Luckily, the situation has changed now. There are many tools available to automate design handoff.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*bFraEbEzld9579dYtjMzXA.gif" /><figcaption><em>Inspecting designs in Abstract</em></figcaption></figure><p>For this project, we used Abstract — it’s like GitHub, but for designers. It’s designed to be a version control system for Sketch, but also useful when you need to hand over designs to development. Developers can inspect designs, copy code, and export assets directly from a link. It also allows you and your team to collect focused feedback on the design and easily compare changes between design iterations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R83lrJSeCPeiS0QjMgpjWA.png" /><figcaption><em>Abstract collections for the vignette design</em></figcaption></figure><p>We also created collections for each vignette to help developers focus attention directly on the work at hand. It allows you to block out noise within a master design file and give developers only what they need.</p><p>Automating parts of our handoff process helped us to save hours of manual work. It allowed us to complete the project quicker because the specs were better organized and more accurate than doing it manually.</p><h3>#5. Create well-crafted feedback loops.</h3><p>The products we build are full of feedback loops. It’s something inevitable in the design process to make a good product. It is important to know how to deliver your feedback as effectively as possible, but also in an efficient way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PuJOJuL8lw-C8v88Ij4jSw.jpeg" /></figure><p>This is what I sent to a developer. I admit I was a bad example of giving feedback. “look less smooth and slow down a bit” are very subjective terms. It can depend on the individual’s interpretation. “Look less smooth” only tells you it is a problem but doesn’t tell you the specifics behind the problem. “Slow down a bit” doesn’t specify how much you need to slow down. Communicating little details on motion work through writing wasted a lot of time and resources with unnecessary revisions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*w8QuTG_aEl2pbpFn6eXyZw.gif" /><figcaption><em>Working with a hot-reload feature on Flutter</em></figcaption></figure><p>The way we provide better feedback was sitting down with a developer in the same place and going through changes together. We were able to see the changes we made instantly reflected in the application with a hot-reload feature on Flutter. It was a hundred times faster than doing it through a messenger or bug tracking because I could direct things and see the result in real-time. We reached a satisfactory result in 15 minutes and regretted why we couldn’t have done this way earlier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*EAwqtVgYNoBPvsDZAX56Vg.gif" /><figcaption><em>Flutter Vignettes Showreel 2019. </em><a href="https://www.youtube.com/watch?v=MI7Rl2umeeU&amp;t=10s"><em>Click here to see a full video</em></a></figcaption></figure><p>I love the way designers and developers collaborate at gskinner. We always have trust, comprehensive understanding, and mutual respect for each other’s roles. I believe that a pleasing result of the project came from the healthy relationship of the team. The healthy relationship came from all those efforts we made to make our process better. I hope this blog post also helps you to build a stronger relationship with your team.</p><p><em>Yoon Lee is a designer at </em><a href="http://gskinner.com/"><em>gskinner</em></a><em> who’s a visual problem solver, research lover, motion designer, illustrator and the best parallel parker. You can follow her on </em><a href="https://www.instagram.com/yoondesigns_/"><em>Instagram</em></a><em> or </em><a href="https://twitter.com/yoondesigns"><em>Twitter</em></a><em> to see what she’s creating.</em></p><p><em>Want to learn more about gskinner? Check out our </em><a href="https://gskinner.com/showcase"><em>latest work</em></a><em>.</em></p><p><em>This article was first posted at:<br></em><a href="http://blog.gskinner.com/archives/2020/03/efficient-designer-developer-collaboration.html">http://blog.gskinner.com/archives/2020/03/efficient-designer-developer-collaboration.html</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=886175ecfd3a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gskinner-team/creating-efficient-designer-and-developer-collaboration-886175ecfd3a">Creating Efficient Designer and Developer Collaboration</a> was originally published in <a href="https://medium.com/gskinner-team">gskinner</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Some Thoughts About Design as A Designer]]></title>
            <link>https://medium.com/gskinner-team/lessons-learned-from-design-adventures-vol-1-3713557f61ca?source=rss-6cc8348ddf2b------2</link>
            <guid isPermaLink="false">https://medium.com/p/3713557f61ca</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[designer]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[career-advice]]></category>
            <dc:creator><![CDATA[Yoon Lee]]></dc:creator>
            <pubDate>Tue, 22 May 2018 20:09:42 GMT</pubDate>
            <atom:updated>2018-11-01T20:52:24.691Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p-ucFt6GT3bCxGMuHjYVwA.jpeg" /></figure><p>If someone asks me how I feel about the last 5 years since I dove into the world of design, I’d say “everyday I am thankful for the tough love that art school showed me”.</p><p>I used to sleep 3 hours a day because I worried too much about falling behind other students. Once, I hid alone in the toilets and secretly cried because I couldn’t come up with a good idea. The worst moment was when I left my work at home on its due date after spending all night finishing it.</p><p>These unpleasant moments taught me valuable lessons. The late nights helped me believe the famous words “effort will never betray you.” Those efforts paid off as achievements at school. Crying in the toilets helped me — in my own way — to relieve anxiety and pull myself together. I was also able to become a person who thoroughly prepares for deadlines (and never forgets anything at home).</p><p>Good or bad, we learn from experience. My experiences in school became a critical part of my career as a designer. They continue to provide valuable insights and help me to form a better sense of judgement when I make decisions. In order to not forget those lessons, I write them down in my notebook and read them when things aren’t working out. They become great inspirations to refresh my brain and make me think about the most important aspects of design.</p><p>Today, I want to share a few lessons that helped me grow as a designer.</p><h3>Designers should have a reason for every decision</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jzRcZ5V6nr0ZL8R-hRJTQQ.jpeg" /></figure><p>Surprisingly, many people still don’t know much about what designers do. When I just started dating my boyfriend, he surprised me by saying ‘do you make things look pretty?’ (no offence! It’s just because he majored in science). It is a statement that designers really don’t want to hear, but at the same time, it is one of the most common misconceptions about designers. While it is true that aesthetics are an important component of design, it is not what design is all about. But, how can we prove that?</p><p>To prove that design is not just about making things look pretty, designers should always have a reason for every design decision they make. Even when placing a single line, we need to ask ourselves why we need it, because it will just become an aesthetic component without a reason to exist. ‘It looks good in that way’ can’t be a rationale. If it looks good, designers should find a reason why it looks good. We are responsible to explain our decisions in a rational manner and tie them to project goals to show why design matters much more than just an aesthetic component.</p><p>I explained this to my boyfriend several times and now he’s achieved a better understanding of my job. We sometimes have a debate on why things that we randomly see around us are designed in that way. What a great improvement.</p><h3>If it doesn’t work for me, it won’t work for others</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fp8Hoi-a6eJWVAMEU4QBZw.jpeg" /></figure><p>When I encounter creative block and don’t feel confident with the ideas I’ve come up with, I am sometimes tempted to believe in a false hope like: “Well, everyone has different tastes, so someone might like at least one of these ideas” (even though I don’t like any of them). What a sneaky thought it is!</p><p>Think about it this way: you went to a restaurant and weren’t sure what to choose from the menu. You asked a restaurant owner to recommend some of the best dishes, however they couldn’t say anything with confidence. If even the owner doesn’t feel confident about their food, how could customers trust it? It is the same for designers. If I want to sell my design, I should be the one who knows the most and feels most confident about my design to make clients understand why this approach is a right solution for their problem. However if I can’t <strong>convince </strong>myself first, how would I be able to <strong>convince </strong>others?</p><p>A few years ago, I was watching television and a celebrity was asked how he could be so stylish all the time. I still remember how he responded because his answer was simple but powerful. He answered, “take a look at yourself in a mirror. Do you look stylish to yourself?”. How easy is that!</p><p>We should always ask this question to ourselves. For the restaurant owner, imagine yourself as a customer and think if you would want to come to your restaurant again. If you are a designer, imagine yourself as a client and question if your design would WOW yourself. Don’t wait for a miraculous thing to happen. If it doesn’t feel good to you, it will never feel good to others.</p><h3>The ‘designing’ part is only half the battle</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lie6yRdAPQjNM4SEnHSQNw.jpeg" /></figure><p>A brilliant idea pops up in your head. You put a lot of effort and time to turn the idea into reality and finally finish all the design work you need; however, it’s not the end of the process. There is still one important thing left to do — the presentation of your work.</p><p>No matter how great the work is, people won’t know how great it is until they see it, but with so many platforms like Behance, Dribbble, and Instagram etc., making the most of people’s attention span is harder than ever. To make a successful launch into this competitive world, the work needs to put its best foot forward. Does a preview image look interesting enough to draw people’s attention? Does your presentation have a nice flow and order? Does it show strengths of the work?</p><p>How you present your work is as important as the work itself. It is communication between you and your audience, so make your presentation as considerate as possible. Make it easily accessible for your audience; Help them understand your story better, make them understand your project in the way you intended to. Make it interesting so they don’t get bored. A great presentation will give your work more strength and visibility.</p><h3>It’s great to be surrounded by people who are better than you</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*96NUk1sD-XiTFfK9bH1aKg.jpeg" /></figure><p>To be honest, I sometimes don’t like to be surrounded by talented people. When I was in school, there were many people who were incredibly talented. I felt lucky to have them in my class, but at the same time I felt a sense of inferiority towards them. I was constantly comparing myself to them and doubted my abilities, asking “why couldn’t I do work like them?”.</p><p>Even though these were not positive emotions and it bothered me sometimes, I sincerely appreciated to be surrounded by them. I was able to improve a lot within those struggles. They became a great stimulus to push myself to the limit and generate higher quality outcomes.</p><p>Feeling inadequate about yourself can be a real struggle, but when you try to think about it another way, it can be an opportunity to try new things, gain a new perspective, and grow. There is always the lure of being comfortable with our surroundings, but being too comfortable can hinder growth. A little bit of pressure and discomfort become great motivation to push ourselves toward something greater.</p><h3>Understand problems before trying to solve them</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*62QgNe9ZHJGdvoz7dU8zFw.jpeg" /></figure><p>Design solves problems. Great design solves problems efficiently and uses as few elements as possible; however, we can’t really say whether it solves problems efficiently or not if we don’t understand what problems we need to solve.</p><p>When I initiate a project, I spend enough time doing research until I get a solid understanding of a problem. What causes the problem? Who is your audience? What do they need? Why do they need it? How has it done in the past? It is where I spend the most amount of energy and time on. This research builds a strong bedrock to start a project. It enables me to break the problem into its most essential and determine what actually matters.</p><p>The more the project develops, the more you will find the importance of having a solid understanding of a problem. It will be your guide that tells you where you need to go and keep you on the right track throughout the project. <br> <br>As we proceed with our lives, we will face things we haven’t experienced before and learn something new. It is all part of our life-long learning process, and I hope this article becomes an opportunity for someone to learn something new. I also hope it doesn’t take me long to learn something to share and come back with Vol. 2!</p><p><em>This article was first posted at </em><a href="http://blog.gskinner.com/archives/2018/05/design-adventures-v1.html"><em>http://blog.gskinner.com/archives/2018/05/design-adventures-v1.html</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3713557f61ca" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gskinner-team/lessons-learned-from-design-adventures-vol-1-3713557f61ca">Some Thoughts About Design as A Designer</a> was originally published in <a href="https://medium.com/gskinner-team">gskinner</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Things I Didn’t Learn In Design School]]></title>
            <link>https://medium.com/gskinner-team/things-i-didnt-learn-in-design-school-f1cabe5b34ba?source=rss-6cc8348ddf2b------2</link>
            <guid isPermaLink="false">https://medium.com/p/f1cabe5b34ba</guid>
            <category><![CDATA[design-school]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[designer]]></category>
            <category><![CDATA[young-professionals]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Yoon Lee]]></dc:creator>
            <pubDate>Tue, 26 Sep 2017 15:25:56 GMT</pubDate>
            <atom:updated>2017-09-27T16:09:48.149Z</atom:updated>
            <content:encoded><![CDATA[<p>Things I Didn’t Learn In Design School</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*onHBb8PNsiq-Qv9rvcH05A.png" /></figure><p>The best decision I’ve ever made was going to design school. Surrounded by talent, designer friends, and inspiring instructors, I was able to improve more than I could have ever imagined. After four years of amazing time in school, I received several job offers after our graduate portfolio show, and ended up working at a digital experience agency: <a href="http://gskinner.com/">gskinner</a>.</p><p>Until the moment I started work, I thought I knew pretty much everything to succeed professionally, and there was no doubt in my naïve mind I would soon become “the SUPERSTAR” designer of the company. But I found the reality to be quite different from what I imagined. Transitioning from school to a professional work environment, I felt ill-equipped as there were many things I hadn’t been exposed to at school. It was like being thrown in the middle of the ocean and having to learn how to swim all over again.</p><p>For those who haven’t plunged into the professional world yet, I came up with three important lessons learned while being at the job. They are based on my personal experiences as a graphic designer, working in the field of digital design. I hope they will give you an opportunity to reflect on your skills and attitudes as a designer, and help ease your transition into a professional role.</p><h3>Learn how to work within a time budget</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QHZOtKU-E3P4SFJ7YiwcYA.png" /></figure><p>While in school, I never had to rush myself to finish everything in class. No one really cared how much time I spent to complete my work, as long as I was able to meet the deadline. But it’s different in the professional world — I have to achieve results in an average of 8 hours a day. During the first month, I was overwhelmed with anxiety, and felt I would not be able to finish the given tasks in time allotted. There is nothing more stressful than doing creative work while your anxiety is through the roof. Here are some tips how I’ve become more comfortable with the industry’s quick turnarounds:</p><ul><li><strong>Clarify expectations on your role.</strong> To help make effective use of your time, it is important to have a clear understanding of your responsibility. Always discuss what is expected of each other with your team, and make sure you all have a shared understanding of those expectations. It helps to document them.</li><li><strong>Break complex projects down into smaller tasks</strong>. It is much easier to manage an entire project when you break it down into individual steps. Write them as smaller action steps instead of vague phrases like ‘complete everything by Friday’.</li><li><strong>Know your tools well.</strong> You can speed up your workflow by understanding your tools well. Learn how to use keyboard shortcuts and keep yourself up-to-date with all the features of your tools.</li></ul><h3>Be familiar with the development process</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nGFnbWO6yLED9jzZtYXgSg.png" /></figure><p>Often, we, as designers, are secretly afraid of code. When I was in school, I brainwashed myself into believing a designer’s job was solely being good at design. However, designers and developers work closely at many modern-day agencies like gskinner. To facilitate smooth communication with developers, I had to learn their language and understand their job as well. This is what <em>you</em> will have to learn — especially if you want to work in the field of digital design. Learning new skills outside your school training can be uncomfortable and foreign, but you will find yourself growing and benefiting from the uneasiness. Here are my tips that will make for better communication between you and the developer:</p><ul><li><strong>Have a basic understanding of HTML and CSS.</strong> By doing so, you can properly understand the needs of the developers. Communication within your team will be much easier when you have a better sense of how the development process works.</li><li><strong>Learn how to make a successful design hand-off</strong>. Your design files should be clean enough to hand over with little-to-no explanation. gskinner has their own system for the process in place to ensure flawless team alignment between designers and developers. <a href="https://medium.com/@CanvasFlip/tips-for-smooth-design-handoff-to-developer-a810dec734f1">This article</a> will help you to get a better sense of what I am talking about.</li></ul><h3>Your goal as a new designer should be to grow, not show off</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hi8obihlI7-bbz1B-Bzg5A.png" /></figure><p>When I was done with school, I felt confident as a designer. I couldn’t be more excited about giving myself over to the professional world around that time, however; my positive mood rapidly fell as I started working. I felt overwhelmingly underprepared to deal with the real world. I felt frustrated with myself for not being able to answer every question.</p><p>Naturally, this will happen to every new grad. No one would expect you to know everything from the beginning. Instead, demonstrate your ability to grow. Showing that you are ready, willing, and able to learn is much more valuable than showing off your credentials. Here are helpful tips on how you can continue to grow as a young designer after school.</p><ul><li><strong>Find a healthy environment you can learn.</strong> This is the biggest reason why I came to gskinner. Part of my job now is to spend time every week exploring things I am interested in, and apply them to new skill sets. This keeps learning interesting, and allows me to continue growing as a designer. Make sure you start in a company where they value your personal development.</li><li><strong>Don’t be afraid to ask questions.</strong> Don’t fear appearing stupid if you ask a lot of questions. Asking questions is the quickest way to learn, and most people in our industry are eager to share their skills and knowledge.</li><li><strong>Readers make leaders.</strong> Things are changing rapidly in our industry and it is important to keep up with the current trends if you don’t want to be left behind. Every morning we set aside time to read and share interesting articles and blogs before we start the day. Doing this keeps us updated and accountable with developments and changes in the industry.</li></ul><p>My first month at gskinner was a headfirst dive into the professional world. I constantly doubted my abilities, questioned if this job was a right fit for me, and struggled every day with things unfamiliar to me. Now, after my third month at gskinner, I’m starting to find my feet, and am comfortable admitting to myself that there is no such thing as a perfect designer.</p><p>The most important lesson I want to stress is to stay humble and have the willingness to learn. If you have not graduated or interned yet, this blog post can be your guide and a cheat sheet. I hope my advice is helpful for those of you who will soon be stepping into your dream career.</p><p><em>This article was first posted at </em><a href="http://blog.gskinner.com/archives/2017/09/things-that-i-didnt-learn-in-design-school.html"><em>http://blog.gskinner.com/archives/2017/09/things-that-i-didnt-learn-in-design-school.html</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f1cabe5b34ba" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gskinner-team/things-i-didnt-learn-in-design-school-f1cabe5b34ba">Things I Didn’t Learn In Design School</a> was originally published in <a href="https://medium.com/gskinner-team">gskinner</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>