<?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 Natalka Smoczyńska on Medium]]></title>
        <description><![CDATA[Stories by Natalka Smoczyńska on Medium]]></description>
        <link>https://medium.com/@Natalka_?source=rss-25fe8262a9b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*TmYtTEBV3QUU_akDfMys_g.png</url>
            <title>Stories by Natalka Smoczyńska on Medium</title>
            <link>https://medium.com/@Natalka_?source=rss-25fe8262a9b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 09:29:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Natalka_/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[The Design System — how can you benefit from it?]]></title>
            <link>https://medium.com/appnroll-publication/the-design-system-how-can-you-benefit-from-it-800da50cb4ca?source=rss-25fe8262a9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/800da50cb4ca</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[style-guides]]></category>
            <category><![CDATA[atomic-design]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Natalka Smoczyńska]]></dc:creator>
            <pubDate>Mon, 20 Jan 2020 13:42:52 GMT</pubDate>
            <atom:updated>2020-01-20T13:42:52.916Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong><em>The Design System — how can you benefit from it?</em></strong></h3><h4><em>A comprehensive guide with real examples.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l11lrYtCJy6bQpSsgbV22w.jpeg" /><figcaption>Illustration by amazing <a href="https://dribbble.com/shots/9532636-UI-Ninja">Dominik Korolczuk</a></figcaption></figure><p><em>Design System</em> is definitely a buzzword that has been used in the digital design world for quite some time and not without reason. The key to building an easy to use digital product is maintaining design consistency, and the easiest way to do this is through a good set of rules and documentation.<strong> <br>A Design System is here to help.</strong></p><h3>How is Atomic Design connected to Design Systems?</h3><p>Brad Frost’s influential <strong>Atomic Design methodology is a good starting point</strong> to understand what a Design System is. The methodology consists of atoms, molecules, organisms, templates, and pages. The idea is that smaller elements are the part of the bigger ones and everything is tightly linked. It means that atoms (buttons, inputs) make molecules (search box that is made with button and input) and molecules make organisms (top navigation that includes the search box).</p><p>During a conference I attended 4 years ago, Vitaly Friedman from Smashing Magazine gave a talk where he said that it’s very hard to start designing with atoms because you don’t know the context of the elements yet. That’s why you have to first focus on experiences — with e-commerce you have to rock the checkout experience or product detail page and think of the flow between those pages (and you will probably start with some lo-fi wireframes at this point). Once you know what the key elements for these pages are you can focus on them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DEtmjku_FqpLtdvsQjQF4A.png" /><figcaption>Example of how Atomic Design might look like in action 😎</figcaption></figure><p>Here comes the phase of key UI elements explorations — you don’t really need to start your design with the final artboard size, specific grid, or getting all breaking points, your first task will be <strong>to explore the typography, colors and core UI elements</strong> — for each project it will be something different, for e-commerce the checkout page will be crucial, so it’s good to focus — for example on inputs that will build these pages, for a lifestyle magazine it could be the typography and an article page.</p><blockquote>Here’s an example of elements exploration shown by Vitaly: <a href="http://rif.superfriend.ly/designs/round2/">http://rif.superfriend.ly/designs/round2/</a></blockquote><p>As I mentioned — it is a good starting point because it shows us how to think component-wise, but it’s definitely not something that I would call a Design System on its own. This concept focuses on grouping common UI elements together which would rather cover the idea of creating subsidiary components, but it kind of skips the bigger vision and there might be a risk of losing the context of the product. <strong>People very often confuse the Design System with the collection of visual rules, despite the fact that it’s way more than that.</strong></p><h3>So what is a Design System?</h3><p>I’d say that a Design System is a framework for making design decisions, but more significant is what it actually does:</p><blockquote><strong><em>Design systems bring order and consistency to digital products. They help to protect the brand, elevate the user experience, and increase the speed and efficiency of how we design and build products.</em></strong></blockquote><blockquote>– Laying the Foundations by Andrew Couldwell</blockquote><p>The elements in the Design System can differ or interfere and in my opinion, there’s no one “golden recipe”. It’s because every product and brand is different and may need some tweaks to convey the vision and serve teams in the organization well. Elements a Design System might consist of:</p><h4><strong>Design Principles</strong></h4><p>This is where all of the foundations can be found like brand personality, philosophy — values, mission; language — writing style, tone of voice. <br>Its role is to guide the team towards keeping cohesion and help them understand the approach and solve problems when building a product, but in a very abstract way, because there are no specific visual solutions yet, just general guides.</p><p><em>At Mudita our design principle emphasises minimalism not only in our philosophy but both in all our tangible products and the digital design. In this case we focus on main USPs for the product, not overwhelming with tons of features. This guides us to many design decisions like sticking to a very limited color palette — we use mostly black and white with some addition of pastel blue and grey. And thanks to this we can convey the spirit of minimalism in our products.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_V5OcQpSR1hYw5GzsBsNzA.png" /><figcaption>Design Principles — Mudita’s values</figcaption></figure><h4><strong>Product Styleguide</strong></h4><p>Styleguide is a set of visual rules for the product that doesn’t show the relationships between elements nor any context. The styleguide usually includes:</p><ul><li>Colors</li><li>Typography</li><li>Imagery (photos, illustrations, icons)</li><li>Grids and Spacing System</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fARgliXzDi4ZRcper8d7Ew.png" /><figcaption><em>The styleguide for </em><a href="https://www.behance.net/gallery/77440695/Dongiving-Case-Study"><em>donation platform</em></a><em> we’ve been working on lately</em></figcaption></figure><h4><strong>Components (design and code) and Patterns Library</strong></h4><p><em>I merged these two into one point because usually these two sections interfere with each other. Quite often the description of how the component works and how it should be used (design pattern) is an introduction on the component page (component library), you can also find some Dos and Don’ts there.</em></p><p>Components are the set of reusable elements designed based on the style guide that can be used within the app. Each element also has an equivalent in the code. These might be buttons, inputs, modals, cards and other elements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PEs7xzxVRZR90tlgEzwfyg.png" /><figcaption><em>In Atlassian Design System you can find </em><a href="https://atlassian.design/guidelines/product/components/avatars"><em>Design Components</em></a><em> with a pattern-like description and each one has a linked </em><a href="https://atlaskit.atlassian.com/packages/core/avatar"><em>API doc</em></a><em> to the component’s code</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cfx8xqICBhpNnMlrQ6MiiQ.png" /><figcaption><em>Here’s a great example of a pure </em><a href="https://canvas.hubspot.com/patterns"><em>Pattern Library from Hubspot’s Canvas Design System</em></a></figcaption></figure><h3>Good practices:</h3><h4><strong>Material design</strong></h4><p>It’s the easiest one to relate to because almost every UI designer has learned how elements work and look to make a decent material design app. This one is a masterpiece that is very easy to work with. Imagine how hard it would be without these guides!</p><p><a href="https://material.io/">Material Design</a></p><h4><strong>Shopify Polaris</strong></h4><p><a href="https://polaris.shopify.com/">Shopify Polaris React</a></p><h4><strong>Atlassian Design System</strong></h4><p><a href="https://atlassian.design/">Atlassian Design</a></p><h4><strong>Hubspot’s Canvas</strong></h4><p><a href="https://canvas.hubspot.com/">Canvas Design System</a></p><h4><strong>For more check out this DS repo</strong></h4><p><a href="https://designsystemsrepo.com/design-systems/">Design Systems Repo</a></p><h3>Why would I ever make one?</h3><p>Design Systems are crucial when it comes to some of our everyday touchpoints:</p><h4><strong>1. Being on the same page with the marketing team</strong></h4><p>While building a product it’s very easy for the design and marketing team to accidentally go their own way. Having rules that are set in stone can make this journey way easier. Not only is it about the common vision and the idea of reaching goals, but also making sure the marketing team is very up to date when it comes to the stylistic, design rules, available assets like illustrations, renders, icons etc.</p><h4><strong>2. Collaborating with other designers and speeding things up</strong></h4><p>In our team of six designers it’s very common for us to work on large-scale projects together. Sometimes, the division of work is very easy — the UX designer gets the UX part, UI gets the UI, Visual does some illustrations etc. But when the project is bigger and more complex we have to work together on one thing to speed things up, so for example, three people work on the UI part. Here come all the problems… Because once you’re a designer responsible for one particular thing it’s pretty easy to be consistent, but when you’re working simultaneously with some other people you really need a guide.</p><p><strong>The Design System helps us:</strong></p><ul><li>handover projects to other designers with no extra explanation</li><li>work simultaneously and keep the consistency</li><li>create new screens and functionalities faster, once you have ‘lego blocks’ that you can be easily put together</li></ul><h4><strong>3. No need to build tons of individual RWD pages anymore!</strong></h4><p>This is definitely a thing that saves a lot of time (and frustration *wink wink*). We take advantage of thinking in blocks and create responsive versions of components, not subpages — each element should be shown in typical RWD breakpoints. The number of components are finite, and very often the number of subpages are not. 😜</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ctkUHEo4vRTh0IO6wVjhoA.png" /><figcaption><em>Some responsive components we did in our project mudita.com</em></figcaption></figure><h4><strong>4. Handling the designs to the development team, keeping the consistency and elevate user experience</strong></h4><p>The main goal here is to provide the development team with the finished list of elements that are used within the application and the description of how they work, what they do, their states (active, filled, hover) etc. It helps them (and also designers) to stick to the elements that are already designed (and developed) and prevent them from creating new ones. It is not only about our time, but also about the user’s time, who is used to some UX patterns — every datepicker or modal should look and work the same so it will be flawless to use it anywhere in the app. So it’s a win-win(-win) situation for designers, developers and users.</p><p>If you’re not convinced yet, here are a few very inspiring articles about the larger players experiences with Design Systems:</p><p><strong>From Hubspot</strong></p><p><a href="https://medium.com/hubspot-product/people-over-pixels-b962c359a14d">How building a design system empowers your team to focus on people — not pixels.</a></p><p><strong>From Uber</strong></p><p><a href="https://medium.com/uber-design/uber-design-platform-1ebff86c89e7">Uber Design Platform</a></p><h3>Threats, are they real?</h3><p>There are always great excuses to avoid creating documentation, but every excuse can get a counterargument 😇</p><h4><strong>Creating a design system for a small project is too time-consuming and won’t be availed</strong></h4><p>When working in a software house/agency it can get really hard to get a chance to design or use the design system. Very often, the given time and little scope of the work doesn’t give any chance to create anything more than a style guide. Sometimes the client is not ready yet to take the time and money to create the Design System. The reason might be that at the very beginning, during the initial stage of the product, they’re not even sure if they will get any users, funds and if they will be developing the project in the future.</p><p>In this case, a well-prepared Sketch/Figma/Adobe xd file can be a great foundation for a Design System subsequently. In my opinion, having everything organized, named and symbolized can be a great guide in the future and within small projects is substantial. <br>Thankfully here in App’n’roll, we are also working on our ventures — Mudita and Vooom, where we can truly focus on doing it the right way.</p><h4>Designers can feel limited and not creative</h4><p>Actually, designing based on a Design System can be even more challenging and creative than designing from scratch! It’s not that the elements are done and set in stone forever. If you have a good reason to change and improve something (having in mind that particular element location is multiple in the whole app), that’s great!</p><p>Making a small change might affect and improve the system easily because it’s interdependent. You can make a big difference with little effort. 😄 You will be sure that it has changed *everywhere* in the app, and you don’t need to manually check all the screens. The main focus can finally be on solving problems, not pushing pixels.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c8SHmSIXG3P44SdFTChy6Q.png" /><figcaption>Small changes can make a huge difference! • Illustration by <a href="https://dribbble.com/shots/9532636-UI-Ninja">Dominik Korolczuk</a></figcaption></figure><h4>Once the Design System is done the designer is no longer needed</h4><p>Design is never done! (If you don’t believe see this post with the evolution of google home screen and navigation 🔥 ) Once it’s done the right way, using the system, it’s way easier to maintain and improve it in the future.</p><p><a href="https://medium.com/google-design/evolution-of-android-homescreen-and-navigation-bad189d536f2">Evolution of Android Homescreen and Navigation</a></p><p>What are your thoughts on this? Are you creating and using a Design System in your organisation? How are you benefiting from this? Let me know in the comments below!</p><p><strong>Thanks for reading! ❤️</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=800da50cb4ca" width="1" height="1" alt=""><hr><p><a href="https://medium.com/appnroll-publication/the-design-system-how-can-you-benefit-from-it-800da50cb4ca">The Design System — how can you benefit from it?</a> was originally published in <a href="https://medium.com/appnroll-publication">Appnroll Publication</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From UX to UI Design]]></title>
            <link>https://medium.com/daftcode-blog/from-ux-to-ui-design-56b5f44b7bd1?source=rss-25fe8262a9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/56b5f44b7bd1</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Natalka Smoczyńska]]></dc:creator>
            <pubDate>Tue, 21 Feb 2017 13:49:43 GMT</pubDate>
            <atom:updated>2017-02-21T13:49:43.019Z</atom:updated>
            <content:encoded><![CDATA[<h4>Managing the Chaos #2</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9g7ge9aEY6ZYSGKnpLAhEw.jpeg" /></figure><blockquote>In my previous post I showed you some of the ways to gather knowledge and start learning UX. If you’ve missed it, check it out here: <a href="https://blog.daftcode.pl/how-to-start-learning-ux-299acb604347#.7dxl2fm5r"><strong>part 1.</strong></a></blockquote><p>Today I want to tell you how to put this knowledge into action! I am a UI/UX designer, so I use my UX knowledge for designing interfaces on a daily basis. You have to know that UI isn’t the only way you can use UX, but when you’re into designing web and mobile applications it’s a great way to start. I really hope you have read some of the resources I’ve recommended and you already have a lot of UX knowledge that you desperately want to use! Check out this blogpost to find out what are the next steps to try out what you know :)</p><h4>OK, I read it all, but what now?</h4><p>Once you start actively observing and reading about UX you will have an urge to use it. And the most basic question is<strong> <em>how?</em></strong> I remember I felt like I had read a lot and already knew pretty much, but it was all super messy. Like the whole effort wasn’t worth it, because I still felt like I knew ‘nothing’. I want to share with you a few issues that were the biggest blockers for me at the beginning:</p><ul><li>How exactly is it all connected? How can I use theory in practice?</li><li>What to design? What kind of project can I do?</li><li>How and when to start? What is an exact process of designing?</li><li>How to measure what is good and what is bad? How to evaluate it?</li></ul><h4><strong>Problem #1: Theory vs Practice</strong></h4><p>The biggest problem was that <strong>I really wanted to implement this knowledge ‘by force’</strong>. The most important thing I’ve learnt is that the knowledge is something that should develop in the background and it would come out only when necessary. You cannot use it when you don’t have a situation for that. And that’s why it’s so hard, because you feel like this knowledge is useless. Trust me, there will be time when it will be all extremely useful :)</p><h4><strong>Problem #2: What to design?!</strong></h4><p>OK, that one was really hard for me. For a long time I haven’t got a clue what project to do, what really is “the UX thing”. And you know what? <strong>UX is very often invisible</strong>. And I was so disappointed that I couldn’t come up with an idea for a school project that is connected with UX to the point that when I actually did, I somehow missed it :D I remember I was bending all the projects that were given from our tutors in school to be connected with <em>interaction design</em> — so I was creating web designs and applications. And hell yeah, I was doing this and I was thinking about information, layout, buttons, flows and everything but I didn’t feel like it’s UX. Goddamn, it was UX :D</p><p>When you want to start designing interfaces my tip is to <strong>start with something super tiny — for example it could be a redesign of something that already exists.</strong> You don’t like your alarm clock or weather application? Is there something you’re missing in Snapchat app? Redesign it! Focus on things that doesn’t work well for you and try to make it better.</p><p>Another great source of ideas is <a href="http://www.dailyui.co/"><strong>Daily UI Challenge</strong></a>. You can find there 100 days challenge with a new thing to design everyday. Here are the first 5 challenges, to show you what kind of tasks you can find there:</p><ul><li>Daily UI #001 — Sign Up Screen</li><li>Daily UI #002 — Credit Card Checkout</li><li>Daily UI #003 — Landing Page</li><li>Daily UI #004 — Calculator</li><li>Daily UI #005 — App Icon</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XndyAH3OL-raGaEy6cindQ.gif" /><figcaption>Daily UI #001 — Sign Up Screen for Antivirus Windows Application that I have designed</figcaption></figure><p>At first it seems to be simple, but when you start doing it by yourself, you will notice obstacles and difficulties. Try posting your designs on <a href="https://dribbble.com/Natalka">dribbble</a>, which is a great place to get feedback (make sure you get an invitation first)! You can join this challenge and see <a href="https://dribbble.com/search?q=daily+UI+%23001">how other people solved different design problems.</a> The thing you have to watch out when it comes to dribbble — very often people don’t really care about how it works (UX), but mostly on how it looks like, and very often designs aren’t thought through. I encourage you to design those elements having your users in mind. Remember that what you are creating is a part of something bigger. For example when designing a sign up screen, there is always something before and after it — a flow of the application.</p><h4><strong>Problem #3: Tools</strong></h4><p>The most important thing that I can tell about designing: <strong>it really doesn’t matter what tool you use!</strong> In fact it’s not even slightly important what software you use.</p><blockquote>The most important thing is to focus on the idea, the problem that you are going to solve.</blockquote><p>I love using paper and pencil or sharpie to draw a solution. It’s the fastest tool and it doesn’t matter if you are a beginner or not. For me sketching helps to open my mind and start visualising ideas.<strong> It’s very important not to make one sketch, but 10 different sketches</strong>. Frequently, the first thought is not the best one and you have to try different ideas. But remember not to throw away any of them! When you got an appropriate number — compare them and find their strong and weak points to come up with the right solution. <strong>These sketches are the most important UX assets.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*13hb7lTkqFLSNNhNX59RJg.jpeg" /><figcaption><em>When I design mobile applications I love to use that kind of mobile phone wireframes. It helps to put my design into context. Yet, when I need something more casual I don’t stick to them.</em></figcaption></figure><p>After you are happy with a sketch of solution, you can recreate it on a computer. What for? To deal with your real canvas &amp; pixels ;) Now it is the time to measure what font size to choose, or how big the containers should be on the screen. But remember — all in black and white or other monochrome palette. These are still wireframes.</p><p>Afterwards, there’s the last step — dealing with a UI. Now you can work on graphic appearance, pick some colors, fonts and create a GUI (Graphical User Interface). In general it is about coloring your wireframe in Sketch, Adobe XD, Illustrator, Photoshop or whatever tool you like best. In my opinion, Sketch is a great software to start with, because of functionality, easiness of learning, price and overall experience ;) And it has a 30-day free trial, so when you will be doing Daily Ui Challenge you could create even 30 designs during this time! :)</p><h4><strong>Problem #4: Is my design good or bad?</strong></h4><p>It is an extremely hard question to answer, even when you are an experienced designer ;) You might get a feeling, but it’s not everything, you need to measure your design. You can check the website: <a href="http://www.goodui.org/"><em>www.goodui.org</em></a> where you can find very good practical examples, but these are only tips, not a way you can evaluate your design.</p><p><strong>That’s why I think a great option at the beginning is to find a mentor.</strong> I know it’s easier said than done, because I really struggled with this. First of all I had no clue that I might have a mentor and I wasn’t actually looking for one. I’ve just wanted somebody who knows and understands the UX stuff and could help me learn it. And it was hard, because I hardly knew any specialists in this field. If you are looking for one, a good solution is to attend UX meetups in your city, or write an email to a designer that you admire for feedback :) Another cool option, when you already have learnt something more than just basics (so it’s not perfect for the beginning), is to apply for an internship in a company that cares about UX and has a UX team. You will definitely find a mentor there, just as I did :)</p><p>Difficulty in finding a mentor might be a big blocker, but the worst that can happen is getting stuck and doing nothing.<strong> That’s why I recommend to ask other people for feedback.</strong> Even without a mentor practicing and doing stuff is cool, right? It’s amazing to ask your friend, mum, brother or a stranger about your design! Show them your approach and ask how they find it, do they understand how does it work. Results may be incredible! And believe me or not — having a mentor is not the only good solution, sometimes<strong> asking your potential users what do they think can be even more valuable :)</strong> These are the people that would use your solution — and it will be exactly the same when you will be mature designer. Users’ opinions of your product will be the most precious and awesome.</p><blockquote><strong><em>Finding a mentor is an incredible experience and it really makes learning easier but you can somehow manage it on your own — by finding your end-users.</em></strong></blockquote><p>And don’t worry that your designs are not going to be implemented. Imagine that these are real products and think also where to put settings, what are the interactions between screens and so on. This is more intermediate thing but it’s good to have it in mind when you are designing.</p><p>These were my biggest problems during the learning process and I hope they would help you in your first steps. <strong>I would love to encourage you to start doing something!</strong> For example: find something that really makes you angry (could be an application, coffee maker or whatever) and try to fix it, step by step :)</p><p>Don’t forget to tell me what have you designed and what solutions you implemented. Did you manage to do the daily design challenge? I wish you luck with all of these! :) If you have any questions — don’t hesitate to ask them in comments. And don’t forget to follow me to read more UX and UI tips!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*KtnDoZhaAkXhmLy0-y_JoA.png" /></figure><p>If you enjoyed this post, please don’t forget to tap ❤! You can also follow us on <a href="https://www.facebook.com/Daftcode/">Facebook</a>, <a href="https://www.linkedin.com/company/daftcode-sp-z-o-o-">LinkedIn</a> and <a href="https://twitter.com/Daftcode_pl">Twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=56b5f44b7bd1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/daftcode-blog/from-ux-to-ui-design-56b5f44b7bd1">From UX to UI Design</a> was originally published in <a href="https://medium.com/daftcode-blog">Daftcode Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Start Learning UX?]]></title>
            <link>https://medium.com/daftcode-blog/how-to-start-learning-ux-299acb604347?source=rss-25fe8262a9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/299acb604347</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Natalka Smoczyńska]]></dc:creator>
            <pubDate>Thu, 09 Feb 2017 12:51:14 GMT</pubDate>
            <atom:updated>2017-02-21T14:46:41.814Z</atom:updated>
            <content:encoded><![CDATA[<h4>Managing the Chaos #1</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ltw9h3ctVAW2umK1zWkSNw.jpeg" /></figure><p>Let’s be honest: it’s a fact that a good handling of User Experience is obligatory for a designer these days. And not only designers, but also developers, copywriters, marketers… almost everybody! <strong>Why? Because when you are designing something that people will use, it’s extremely important to think about them, their feelings and experiences.</strong> It doesn’t really matter what you’re designing. It applies to web designs, applications or anything interactive, as well as things like services or physical products (e.g. a chair!).</p><blockquote>It’s good to have in mind that User Experience is a powerful tool which can be helpful every day.</blockquote><p>There’re lots of people who would love to start learning UX, but in most cases, they have no idea how to begin with. The most common question that comes up at any UX meetup is “<em>How to start doing this whole mysterious UX thing?</em>”. We’ve all been there, we’ve all done that. The problem is that access to such knowledge seems to be very limited. I have graduated from a graphic school, yet never really heard about UX during my 5 years of studies. Even when I actually asked about it, hardly ever got any serious feedback on this matter. That’s why I have started to look for this knowledge by myself. In this blogpost I want to share my personal experience and tell you what problems did I meet and how I solved them.</p><h4><strong>The problematic start</strong></h4><p>Good, we already know that UX is an important issue. But here comes the first problem — once you find out that UX exists and you want to learn it, you simply have no idea where to start. At the moment, there are many meetups and communities that gather people from this industry, but when I was starting, there were hardly any groups of interest and nobody even heard about it (well, maybe because I didn’t know the right people). Thankfully I had a great opportunity to find someone who recommended me books I could read, told me what UX is all about, and showed some real life implementations. That was amazing! I was so charmed that I couldn’t resist diving into it and learning more and more! And this is the reason why I am here — to help you to begin, just as I’ve once been helped :)</p><blockquote>The key is to have a <strong>“UX mindset” </strong>and challenge everything that you use every day.</blockquote><h4><strong>Read and… Observe!</strong></h4><p>At the beginning I remember that I didn’t even understand what it all is about, what exactly does it mean, how does it work. So from my own experience I can say, that the best way is to:</p><ul><li><strong>Find any source that contains articles or literally anything about the UX design</strong>. It’s great to start with some theory to soak up with all of these like a sponge. With every article and book read my overall knowledge of UX design improved and let me see the bigger picture.</li><li><strong>Immerse yourself in it every single day. </strong>Whether you are commuting or doing anything else — it doesn’t matter! You can read a book or an article in every gap in your schedule — during your commute or whatever. Moreover, you can evaluate the interface of a ticket vending machine in the bus and think whether it is user-friendly and intuitive.</li><li><strong>Observe things from your everyday life</strong>, starting with ordinary items like the layout of your kitchen, through the interface of your stove, up to web or mobile applications.</li></ul><p>The key is to have a <strong>“UX mindset” </strong>and challenge everything that you use every day<strong>. </strong>There are clearly 2 steps, that you can actually do simultaneously — <strong>reading and observing</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*1dXpOs9umO9YV2VqgL5cKA.gif" /></figure><p>Here’s an example from our office. We have a soap feeder that activates when you put your hands under it. However, it’s placed under the mirror, so you can’t see where it is exactly. So we came up with an idea to show this spot with an illustration. After we implemented this solution it stopped to be a problem for anyone. So a tip is to observe simple things like this and think how can you fix it :)</p><h4><strong>My favourite UX books</strong></h4><p>I have collected a lot of great UX books, and it was pretty hard to tell which ones are the best, especially for beginners. I finally decided to present you the ones that helped me the most on the very first stage of learning.</p><ul><li><strong><em>Don’t Make Me Think</em> by Steve Krug<br></strong>This is my favourite book that I could recommend literally to everyone, designers or not. It is something you are looking for when you have an urge to find a proper information with a real examples and cases. It really helps to understand and imagine how everything works and how you can implement UX in web designs. What is interesting, the examples from the book may look a bit outdated at first: they come from 90s, but amazingly enough, the knowledge and mechanism that stand behind them are absolutely up-to-date. This proves that it is quite hard to make good UX obsolete ;)</li><li><strong><em>The Design of Everyday Things</em> by Donald A. Norman<br></strong>Don Norman presents different, more classical approach. It was written about 30 years ago but it’s still accurate — real must read for every designer. This book reveals the different way of thinking and will help you to start questioning everything you see and use :) It sticks more to physical items and usability, what helps you to understand UX at the most basic level.</li><li><strong><em>100 Things every Designer Needs to Know about People</em> by Susan M. Weinschenk </strong><br>A cool book to read for understanding more on how people think and act — it shows rather a psychological approach, but with casual and easy language. A great title for beginners.</li><li><a href="https://www.uxpin.com/studio/ebooks/"><strong>UXPin books</strong></a> <br>Really valuable materials. They cover many interesting topics and are an essential source of inspiration and knowledge not only for beginners. It’s a huge collection, but don’t be confused :) If you don’t know with which one will be good to start with, just pick one or two that sound interesting for you, riffle through their pages and decide whether you want to read them or not. There are many great examples with descriptions there and some books consist only of graphics and screenshots. Really cool stuff :)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*Ba4KX85CFoYMSPi5vvviVQ.jpeg" /></figure><p>There’s a lot of other books that are amazing and contain valuable content, but I would rather stick to the ones above as a good beginning. I always felt overwhelmed by blogposts like “20 UX Books You Must Read”. Some of the classical manuals that I can highly recommend are Alan Cooper’s <em>About Face</em>, or Jesse James Garrett’s <em>The Elements of User Experience: User-Centered Design for the Web</em>, but in my opinion these books are dedicated rather for the next steps of learning.</p><p>It’s also a good idea to create a stream of UX articles — I do have it on my <a href="https://twitter.com/nasmoczynska">Twitter</a> and Medium :) That’s an amazing solution for finding something new to broaden your horizons every day. So don’t forget to follow me to get more content about UX! :) In the next post I will tell you more about how to put your knowledge into action. So stay tuned!</p><h3><strong>Read next:</strong></h3><p><a href="https://blog.daftcode.pl/from-ux-to-ui-design-56b5f44b7bd1">From UX to UI Design</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*KtnDoZhaAkXhmLy0-y_JoA.png" /></figure><p>If you enjoyed this post, please don’t forget to tap ❤! You can also follow us on <a href="https://www.facebook.com/Daftcode/">Facebook</a>, <a href="https://www.linkedin.com/company/daftcode-sp-z-o-o-">LinkedIn</a> and <a href="https://twitter.com/Daftcode_pl">Twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=299acb604347" width="1" height="1" alt=""><hr><p><a href="https://medium.com/daftcode-blog/how-to-start-learning-ux-299acb604347">How to Start Learning UX?</a> was originally published in <a href="https://medium.com/daftcode-blog">Daftcode Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>