<?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 Alisher Satybaldin on Medium]]></title>
        <description><![CDATA[Stories by Alisher Satybaldin on Medium]]></description>
        <link>https://medium.com/@kespeee?source=rss-a7e21870e796------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*tlaFSpiYjMty12b6amfY1A@2x.jpeg</url>
            <title>Stories by Alisher Satybaldin on Medium</title>
            <link>https://medium.com/@kespeee?source=rss-a7e21870e796------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 14:50:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kespeee/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[8 Mistakes Junior UX Designers make.]]></title>
            <link>https://uxplanet.org/8-mistakes-every-junior-ux-designers-make-ab0bdd7c1ed6?source=rss-a7e21870e796------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab0bdd7c1ed6</guid>
            <category><![CDATA[visual-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Alisher Satybaldin]]></dc:creator>
            <pubDate>Fri, 08 Nov 2019 08:41:01 GMT</pubDate>
            <atom:updated>2019-11-08T12:32:12.485Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>And my mistakes as well, of course.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Czf0NJTOWjXz4VdWEgSHUA.jpeg" /></figure><p>Hey there, dear Design fellows. I’m about to introduce popular mistakes Junior or Entry-level Designers make. Those mistakes are partially based on my personal experience as well as on gathering details from other Designers and resources.</p><p>To be honest, I was working on <em>“Habits of a Great Designer”</em>, however, learning from mistakes is a better option than developing some habits.</p><p>But before that, I would like to thank all of you for reading my last article about <a href="https://uxplanet.org/7-common-ux-design-myth-ce254486ae6">Myths in UX Design</a>. Hopefully, it helped some of you to arrange your career path and prevent some misconceptions around your problems and solutions.</p><p>So let’s get started.</p><h3>1. Prioritizing UI over UX</h3><p>Huge mistake from almost everyone who started their career path in UX. To be honest, I made that too.</p><p><strong>The problem is</strong> that every Designer tries to think in terms of clearance and aesthetics. Why? ‘Cuz it looks great. However, the ‘beautiful and trendy’ interface won’t resolve all users’ issues. Yes, it is a great bonus, but on the other side, people use the product for a specific purpose. It might be purchasing tickets or chatting with friends, but they just want get things done.</p><p>Providing an <em>‘invisible UX’</em> with not so fresh look is much better than building a trendy interface with a bad experience. It is <strong>much simpler</strong> to restructure the UI rather than rebuild the whole logic, flow, and functionality. It doesn’t really matter how beautiful the interface is if it’s not making lives convenient and easy.</p><p>When I just started my career as a UX Designer, I didn’t even think about flows, emotions, context, and thinking. The only thing I focused on was <em>‘pixel-pushing’ </em>to an ideal state with perfect sizes, shadows, buttons, and animations. I didn’t realize the main thing is <em>‘behind-the-scenes’</em> of every product which meant research, analysis, and testing.</p><p>So <strong>don’t over-prioritize</strong> UI over UX or vice versa. Your product should strike a perfect balance between creativity and functionality. While the aesthetic aspects are essential for UX, they should not override the functionality of your website. Users want creativity, but they also want tasks to be completed easily.</p><h3>2. Copying Design without Testing</h3><p>Oh, this is a tasty one. Copying designs isn’t bad as long as<strong> it’s done appropriately</strong>. By <em>‘done appropriately’ </em>I meant validate the design in terms of success or failure and conduct testings in terms of usability and information architecture.</p><p><strong>You can’t just predict</strong> the feature whether it will be useful or not without validations. <strong>You can’t just rely </strong>on your intuition or sense of aesthetics. Validation is an essential part of every design process and it doesn’t really matter if your process is agile or waterfall.</p><p>Based on my observations, a lot of Junior UX-ers simply take out designs from other sources or products only because it’s <em>‘nice and clean’. </em>Partially it is correct, you take out inspiration and style from those interfaces, but how do you know will it perfectly fit into your system and style as well? That’s the question you should be asking yourselves.</p><p>During my career start, I was copying as well. <strong>Fake it till you make it</strong>, right? However, those designs majorly failed and such fails led to negative outcomes. And these outcomes really taught me some things.</p><p>I’ve seen a lot of interfaces being stolen from platforms like Dribbble or Behance. Those are websites where you can mainly(!) share your UI skills and spread some news around. I honestly don’t think they are supposed to be a <em>‘personal portfolio website’</em> for everyone.</p><p><strong>Here is a tip:</strong> always test your solutions on real users, build some prototypes or (as Lean UX suggests) launch and measure your results. Measuring your result will help you drive towards the right direction.</p><h3>3. Not doing Research</h3><p><strong>What is Research</strong> and why it is so vital?</p><p>UX Research is used to understand the user’s needs, behavior, experience, and motivations through various qualitative and quantitative methods to inform the process of solving for user’s problems. In other words, UX Research is a <strong>set of investigative methods</strong> performed to add insights and context. There is a long list of methods performed by user research, but at its center is the user and how they think, behave — their needs and motivations. Generally speaking, UX research does this through observation techniques, task analysis, and other feedback methodologies.</p><p>To be honest, <strong>I used to neglect</strong> Research back in the days. I tended to think everyone is like me: technology-oriented, digitally advanced and passionate person. That was a really huge misconception which led to bad ideas, solutions, and preferences.</p><p><strong>Research is the blood</strong> for your project. It prevents us from designing for one user: ourselves. You can’t just sell sweets to people with diabetes. Know your audience, know your business, know your product’s back-side things. The more you know, the more accurate will be the outcome.</p><h3>4. Letting trends guide your thinking</h3><p>That’s what I mean. We’ve seen a lot of <em>“trendy” </em>interfaces and animations throughout the whole Internet, isn’t it? But have you seen all of them being built? I suppose nope. Beautiful doesn’t always mean useful. And efficient <strong>doesn’t always mean</strong> effective.</p><p>Trends change quickly. One pattern was popular last week, and it’s not gonna be actual the following week. This is really frustrating seeing how other Junior Designers think in terms of trends only, not in terms of functionality or usability, but <em>‘trendy’.</em></p><p>On the other hand, I do agree, trendy stuff helps your product grow and attract some additional attention. <strong>Besides that</strong>, too many changes (‘cuz trends aren’t constant) really confuse users and inconsistency leads to bad UX as well.</p><p>Halfway here, yikes!</p><h3>5. No communication</h3><p>This topic was also covered in <a href="https://uxdesign.cc/what-i-learned-while-being-a-product-designer-intern-at-startup-62d2c6c27f85?source=friends_link&amp;sk=4487d84a83b375b7a0a6931c2b797cf1">my first article</a>. Go and check it out!</p><p>Are you an outgoing person? You better be. As a Designer, <strong>you are responsible</strong> for the whole process not only in terms of UX and UI, but also for team collaboration, processes between other departments and customer development.</p><p>You have to explain every single decision you made as a Designer. How Devs will understand your designs without having a conversation. Right, they won’t. The process always involves Devs and Managers into the UX lifecycle. While proposing some solutions, Devs are that ‘superheroes’ who will implement those solutions into real life.</p><p>How can you understand user needs without asking them? Yep, you can’t. UX involves users as a <strong>‘center of the universe’</strong> and it is vital to gather around their needs and preferences through conversations during interviews, surveys, and discussions. It is better to be an adaptable person, thus you can get along with almost every user.</p><h3>6. Overconfidence</h3><p>Confidence is great, overconfidence is not. It is better to be shy rather than being super confident. Shy Designer will validate every single solution, every single step in potential solutions. Over-confident Designer won’t do either of those.</p><p>As a Designer, you <strong>have to be aware</strong> of what to expect from designs, and that awareness should be minimized through iterations, testings, validations and, of course, research.</p><h3>7. Misusing Usability Testing</h3><p><strong>First things first,</strong> what is Usability Testing? It is a series of actions performed towards the product’s usability to discover and identify pain points, usability issues, success metrics, emotions, and preferences.</p><p>In a fast-paced environment, it is kinda complicated to conduct Usability Testings, however, it is still a great technique for issue identification. In most cases, Designers <strong>tend to solve consequences but not reasons</strong>. Testings will help you find reasons and prevent them before launching phase.</p><p>Yes, sometimes you might be confident in what you do, due to some UX basics and principles, however, definitions are abstract and <strong>may vary from service to service.</strong> Do some tests, know your user and their problems, solve them before they realize that.</p><h3>8. UX is not only screen</h3><p>Finally, the last chapter, where <strong>I made a huge mistake</strong> while being Junior UX-er (I’m still thinking I’m Junior, but that’s not the point).</p><p><strong>I tended to think</strong> UX is only inside the display, not even considering the users’ credentials (age, lifestyle, and preferences). I thought that UX begins when an individual starts using the website/app and ends when he/she closes it. I didn’t even consider emotions and expectations. These misconceptions led to bad logic, functionality and complicated flow.</p><p>Moreover, I wasn’t really thinking about user scenarios as I was sure in the accuracy of my designs (what a joke!). <strong>And I was almost fired.</strong></p><p>So now I’m planning and researching everything first, try to outplay every possible scenario, think strategically and prevent future mistakes ‘cuz of bad design.</p><p>Work out every possible solution, whether it is bad for business or good, whether it is bad for user or good. You’ll never know until discovered. Avoid thinking only inside the display, think outside it and you’ll notice better ideation and process. Think of emotions, preferences, business and service in a whole range, not only in terms of forms and buttons.</p><h3>Summary</h3><p>Well, here it is. We’ve done it. Now you know about 8 basic mistakes that the majority of Junior (and Entry-level) UX Designers make. And me, of course.</p><p><strong>To sum up</strong>, research is your best friend. Do not neglect it, don’t be over-confident in your solutions, it is better to be a shy individual. Test first, analyze second, launch third. Be an easy-going person, chat a lot (but not overreact), be consistent and think broadly.</p><p>Hope you learned something new here. I would love if you did. ‘Cuz the best way to learn something is to share the gained knowledge and experience. Learn from the community and give to the community.</p><p>So, the next chapter will be (hopefully) about popular mistakes UI designers make. That would be interesting. See ya, fellas!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fb3e808%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fb3e808%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Fb3e808%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href">https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab0bdd7c1ed6" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/8-mistakes-every-junior-ux-designers-make-ab0bdd7c1ed6">8 Mistakes Junior UX Designers make.</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7 Common UX Design Myths]]></title>
            <link>https://uxplanet.org/7-common-ux-design-myth-ce254486ae6?source=rss-a7e21870e796------2</link>
            <guid isPermaLink="false">https://medium.com/p/ce254486ae6</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[visual-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Alisher Satybaldin]]></dc:creator>
            <pubDate>Tue, 16 Jul 2019 09:37:12 GMT</pubDate>
            <atom:updated>2019-07-31T03:19:39.698Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>And how to avoid them.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0ohcZCH2tA-a9wft" /><figcaption>Photo by <a href="https://unsplash.com/@halgatewood?utm_source=medium&amp;utm_medium=referral">Hal Gatewood</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Greetings everyone, fellow seekers of truth. It’s about time to bust some myths around UX/Product Design.</p><p>First of all, I wanted to thank everyone who read my last story about <a href="https://uxplanet.org/things-i-wish-i-knew-when-i-started-designing-3963050f850c"><em>“Things I wish I knew when I started Designing”</em></a>, cuz’ it got really widespread and I hope it helped some newbies to find their career path as well. And I am really excited to discuss with you all other topics related to the UX.</p><p>Honestly speaking, I’m not that much skilled in UX Design, however I’ve already faced those misconceptions during the design process. Some of them are really <em>“popular”</em>, some are based on specific data and may vary from service to service.</p><p>Let’s roll.</p><h3>Myth #1: UX = UI</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ab8Qy07xeFTBqiv-pZU8Ew.png" /></figure><p>One of the most popular misconceptions of all time. People that aren’t in this area might think those two disciplines are the same and represent same results and outcomes. But, actually, no.</p><p>Well, I’m not gonna go deep in details of each area, cuz’ there are so much topics been already discussed throughout the whole Internet. Instead, I will try to explain my vision as simple as possible.</p><p><strong>UX</strong> stands for “<em>User Experience” </em>and involves end-user interaction with the company, its products and services. In other words, this is a process of defining users’ problems and solving them before they realize it.</p><p><strong>UI</strong> stands for <em>“User Interface” </em>and involves color codes, buttons, forms, text fonts, visual hierarchy and etc. It is responsible for visual product perception, while making the interface more attractive, aesthetic and sometimes <em>“trendy”.</em></p><p>So, as you can see, UX is more about science and UI is more about art.</p><p>The picture below demonstrates my vision of a UX and UI design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gI7DKoVaUTMDGiSlUmD4JA.png" /></figure><p>Well, you may wonder what CX stands for. <em>“Customer Experience” </em>to be exact, but that’s not kinda topic to discuss it here. We’ll cover it later on (I promise).</p><p>But some people might think <em>“Why UX covers UI? These are different disciplines which interact with each other, not inside each other”. </em>And they will be right. However, let’s consider basic stages of UX Design process (in short):</p><h4>Understand</h4><blockquote>If you have four hours to chop down a tree, spend the first three hours sharpening your axe. — Popular proverb</blockquote><p>Well, this is the stage where you try to identify your brand, users and deliverables. You have to comprehend the user’s pain points by answering the following question: <em>What’s their problem?</em></p><h4>Research</h4><p>This stage gonna be the <em>“blood”</em> of your project. Things you will identify, discover and challenge will be the foundation layer for your product’s lifecycle.</p><p>Some great tools for user research:</p><ul><li>Interviews</li><li>Surveys</li><li>Usability Tests</li></ul><h4>Analyze</h4><p>During this step, you will be (obviously) analyzing all gathered information from the previous stage in order to specify most important elements.</p><p>Couple of ways to make an analysis:</p><ul><li>Customer Journey map</li><li>User Personas</li></ul><h4>Design</h4><p>Here comes the <em>“art”</em> part. This is the stage where you literally <em>“push pixels”</em> in order to reach the desired outcome. That means building:</p><ul><li>User Flow</li><li>Mockups</li><li>Colors</li><li>Buttons</li><li>Icons</li><li>Images</li><li>Components</li></ul><p>Sounds like the<em> “UI thing”</em> isn’t it? This whole stage is about User Interface Design and its principles. This is where you have to design in terms of your product/service, brand guidelines and some <em>“trendy things”</em>.</p><p>Of course, you can start designing the User Interface for some <em>“fake concepts” </em>and mockups, but for the real product which will be used by thousands or (hopefully) millions of users, it is inevitable to lay out a rigid foundation for your product.</p><p><strong>Remember</strong>: this is an iterative process which means you won’t have an ideal solution at first time. You’ll have to design, redesign, erase everything and start from scratch all over again.</p><h4>Launch</h4><p>Typically the last stage where you release your product’s features, solutions, improvements to your audience. Generally speaking, this is not formally the last step, cuz’ you’ll have to iterate and return to the Analysis again, to measure your improvements whether you succeeded or not.</p><p>By this time, you can easily identify between UI and UX, their deliverables, processes and vision.</p><p>Let’s move onto the second myth.</p><h3>Myth #2: Users don’t scroll</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9oCGEMdZz4ggmgbnMEvmlA.png" /></figure><p>One of the most serious misleadings is that Designers, Devs and Managers tend to think that people usually do not scroll, and there is no necessity in providing information at the bottom of a web page or mobile app. They might be right since all important information is almost always above the fold, but in order to make sure that people will scroll, several design principles should be followed and interesting content should be also provided.</p><p>People do scroll. And nearly half of them even scroll till the bottom of the page.</p><p>Here is <strong>some research</strong> proving users’ scrollings:</p><ul><li><a href="https://time.com/12933/what-you-think-you-know-about-the-web-is-wrong/">What You Think You Know About the Web Is Wrong</a></li><li><a href="https://www.cxpartners.co.uk/our-thinking/the_myth_of_the_page_fold_evidence_from_user_testing/">The myth of the page fold: evidence from user testing</a></li><li><a href="https://www.clicktale.com/resources/blog/resourcesbloginvest-in-customer-experience-software/">Unfolding the Fold</a></li></ul><p>Those investigations really found out that people actually scroll and they scroll a lot. In mid-nineties people didn’t scroll that much, why? My suggestion (in addition) is that impact of social networks takes place. The logic of <em>“feed”</em> had a significant influence on every user’s experience and, currently, scrolling has become an essential part of every web page, mobile app, etc.</p><p><strong>Keep in mind</strong> that content above the fold will still get the most attention and is also crucial for users in deciding whether your page is worth reading at all.</p><h3>Myth #3: You’re like your user</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vZ_HKULoC2TS0RVYGRPU5g.png" /></figure><p>While designing, let’s say, a website, some Designers suggest like everyone is like them. They expect the same vision, same logic, functionality and emotions while using a product. This causes a strong bias and usually leads to a bad design or useless purpose of the website. Why?</p><p><strong>The problem</strong> is that you as a Designer already know a lot about thy product, its advantages and drawbacks. You are passionate and know how it operates and you have a deep-down knowledge about its back side things. Users, in contrast, don’t really care that much because they want to get things done using your website. Moreover, attitudes, goals and expectations vary as well.</p><blockquote><em>Knowing how people will use something is essential. — Donald Norman</em></blockquote><p>Many of your users are coming to your site or using your product for the very first time. Many of them have a goal in mind and are using your product because they believe it will help them achieve that goal. And others are cautiously poking around, cuz’ little unsure due to previous experiences left them confused and dissatisfied.</p><p><strong>How to avoid it?</strong> Conduct a research. Fortunately, there are a bunch of tools and techniques you can implement to easily understand your target audience’s behavior and emotion patterns. Exempli gratia:</p><ul><li><strong>Surveys</strong> — set of specific questions distributed to a large number of respondents in order to identify pain points and results.</li><li><strong>User Interviews</strong> — conducted a conversation with current (or potential) users in order to obtain results in terms of their preferences, behavior and vision of a product.</li><li><strong>Usability Testing</strong> — set of specific tasks provided to a user with your product in order to identify pain points, user problems and success metrics.</li></ul><p>Research is your best friend and should not be neglected even if time frames are restricted. It helps you to discover future user problems and build a solution before they relize it.</p><h3>Myth #4: Design means looking good</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CAmVszRBzT2Gf0Ny8t2NHQ.png" /></figure><p>Many people around the world define design that is something visually attractive and elegant. They tend to assume design as a decoration, visual result, but not a process. It is incorrect, though. Design is more likely how it works and operates, rather that looks and feels. UX Design is not only visually attractive (like illustrations and graphics) but also functional and useful.</p><p>What <strong>designers say</strong> about how do they define design:</p><blockquote>“What is design to me? Like design I think it’s best to break the problem up until you find the simplest solution.” — Paul Scrivens</blockquote><blockquote>“Design is a plan for arranging elements in such a way as best to accomplish a particular purpose.” — Charles Eames</blockquote><p>Thus, <strong>the aim of great design</strong> is to actually solve problems. Design is based on comprehension of how users see the world, how they behave, what emotions do they feel and their context as well. It’s just not about colors and font styles, it is also about prototyping, research, testings and science.</p><p>Uh, I’m feeling like a mythbuster (shoutout to Jamie and Adam!).</p><h3>Myth #5: More choices = higher satisfaction</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YLbPTpdlNWdiUcj1MHJqhA.png" /></figure><p>Nope. That’s another misconception over there. Yes, having choices is a good thing and users are satisfied if they are in control of what they do.</p><p>Despite this, the more choices product offers, the harder it is to understand the product itself and its interface and functionality. Some studies showed that too many choices lead to <em>“decision paralysis” — </em>complete lack of ability to make a decision. This leads to frustration, which finally leads to refusion of using your product. In other words, as the decision time increases, the user experience suffers. You don’t want this to happen, do you?</p><p>Let’s take a stepback to basics. <a href="https://lawsofux.com/hicks-law.html"><strong>Hick’s Law</strong></a><strong> </strong>states that “the time it takes to make a decision increases with the number and complexity of choices”. Thus, Designers should provide an optimal quantity of choices in order to maximize the outcome.</p><p><strong>Here is a tip:</strong> simplify choices for the user by breaking down complex tasks into smaller steps, or combine similar tasks into high-end categories. You can even highlight/emphasize the recommended options to avoid information overload and decision paralysis.</p><h3>Myth #6: Users make optimal choices</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jD5PyvPAo06mQnJqYd3gNg.png" /></figure><p>That’s an ideal world, where customers make optimal decisions based on a product/service. They scan the page to find every specific piece of information, but studies found out this is not in real life and users tend to choose a somewhat reasonable option that catches their eyes.</p><p>In other words, people choose a link that is even slightly connected to what they are looking for and expect some specific outcome from that link. Here is some joke about it:</p><blockquote>A QA Engineer walks into a bar. Orders 1 beer. Orders -0 beers. Orders 2.5 billion beers. Orders -15 beers. Orders affsdffssfd. Orders lizard. Orders 9999dg36 beers. The first real customer walks into a bar and asks where the bathroom is. The bar bursts in flames, everyone is dead.</blockquote><p>This is really g(old) joke, which represents real-life mistakes of every newbie team. They expect a user to make a choice they really want to but didn’t realize there are too many other options to be considered.</p><p>Steve Krug wrote in his book <a href="https://www.amazon.com/Think-Common-Sense-Approach-Usability/dp/0789723107"><em>“Don’t Make Me Think”</em></a><em> </em>(strictly insist on reading this masterpiece) that users tend to guess the option because there is no penalty in a mistake and it’s fun.</p><p>Try to <strong>make</strong> options as clear as possible, <strong>provide</strong> possible outcomes of what to expect and <strong>investigate</strong> every little scenario that might come up even from the deep-down area of your website/app, cuz’ as Murphy’s Law states <em>“anything that can go wrong will go wrong”</em>.</p><h3>Myth #7: People read on the Web</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*svZ76NNfoxGTGWoV0PLZvg.png" /></figure><p>Basically, people read on the web word-by-word when they are actually interested in the content. But in general, they just scan pages thru some keywords that will catch their eye and likely will skip irrelevant information.</p><p>Here is <strong>some research</strong> made:</p><ul><li>Jakob Nielsen’s eye-tracking study from 2008 indicated that <a href="https://t.umblr.com/redirect?z=http%3A%2F%2Fwww.useit.com%2Falertbox%2Fpercent-text-read.html&amp;t=M2M0ZjdlY2NiZDNjNTNjOTk3ZDg2Yjg5NjQ0M2RkYWM3ODk4ZWJlNixYUlVseGpncw%3D%3D&amp;b=t%3AfIR3gaVrEcGakJWUzP9Grg&amp;p=https%3A%2F%2Fuxmyths.com%2Fpost%2F647473628%2Fmyth-people-read-on-the-web&amp;m=1">less than 20% of the text content is actually read</a> on an average web page.</li><li>Steve Krug claims in <a href="https://www.amazon.com/Think-Common-Sense-Approach-Usability/dp/0789723107"><em>“Don’t Make Me Think”</em></a> (again, read it) that one of the most important facts about web users is that they don’t read, they scan.</li></ul><p>But when actually <strong>people read?</strong> Firstly, when they are really interested in the content. Secondly, when the interface is well-structured and organized.</p><p>So, try to organize the hierarchy of your content properly, clarify paragraphs (if there are so much text), play with contrast and identify the keywords of each paragraph to deliver meaningful information to the reader.</p><p><strong>As an example,</strong> you can see how I did to this article. If you scan through the text, you’ll see how keywords are highlighted, hierarchy is correct and even images help you to navigate between topics. Thus, you’ll be able to quickly scan thru the titles and catch relevant information only, without wasting some time.</p><h3>Summary</h3><p>We’ve done it. It was a very <em>“mythbusting”</em> adventure. But a little disclaimer: don’t rely on my research only, do your own. Products significantly differ from one another, thus, services vary as well, target audience, deliverables and emotions also different. And never forget that research is your best friend and a solid positive foundation for your product’s future.</p><p>Do not try to design just for design. Aesthetics and clearance is not a crucial part of your product. Your product should solve problems and shouldn’t create other ones.</p><p>There are so many topics left to cover, I’m already working on <em>“Habits of a Designer”</em> and I hope we’ll get thru them later on. Spread the word to your fellow design friends and discuss with them. Adequate discussion is one of those great habits, though.</p><p>Thanks and see ya later!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fb3e808%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fb3e808%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Fb3e808%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href">https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce254486ae6" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/7-common-ux-design-myth-ce254486ae6">7 Common UX Design Myths</a> was originally published in <a href="https://uxplanet.org/">UX Planet</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 wish I knew when I started designing.]]></title>
            <link>https://uxplanet.org/things-i-wish-i-knew-when-i-started-designing-3963050f850c?source=rss-a7e21870e796------2</link>
            <guid isPermaLink="false">https://medium.com/p/3963050f850c</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[user-interface]]></category>
            <dc:creator><![CDATA[Alisher Satybaldin]]></dc:creator>
            <pubDate>Thu, 28 Mar 2019 18:36:53 GMT</pubDate>
            <atom:updated>2019-03-29T19:23:45.979Z</atom:updated>
            <content:encoded><![CDATA[<h3>Things I wish I knew when I started designing</h3><h4>Sharing some personal experiences.</h4><p>Hello there! Hope everything’s great with y’all.</p><p>It’s been a while since I posted <a href="https://uxdesign.cc/what-i-learned-while-being-a-product-designer-intern-at-startup-62d2c6c27f85">my first article</a> and, if you didn’t read this, I highly encourage you to do it, seriously.</p><p>So, to begin with, let me tell you something. I guess, this topic wouldn’t be useful to the Senior part of the community, I mean to those, who has at least 2 or 3 years of real work experience, because those individuals already faced that obstacles during their career start. But I do strongly recommend this to beginners or recent graduates, since I made some crucial mistakes I am going to share with you.</p><p>Yep, mostly it will be connected to the Design, however, there will be couple of general cases, thus, even those who are out of the Design might also discover something interesting. I’ll try to make it as easy as possible, that’s how concept of my articles works.</p><p>So, get yourself comfortable, prepare a cup of tea and here we go.</p><h3>Be flexible, stay focused</h3><p>Have you ever heard about “T-shaped skills”? No? I’ll explain it to you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/367/1*TnTk4CZsgxobA-CK9zWsiA.png" /><figcaption>T-Shaped Skills Model</figcaption></figure><p>T-shaped skills actually describe specific attributes of an employee. The top bar of “T” letter demonstrates the capability in a lot of areas, whilst the vertical bar demonstrates the deep-down knowledge and expertise in one particular area.</p><p>In my case, I’ve got a knowledge in some Design areas, namely: Graphic Design, Illustrations, Web/Mobile Design, sort of Motion Design and Branding. Since then, I found myself really interested in Web/Mobile Design and started to dig deeper and that’s how I got my vertical bar of “T” letter.</p><p>Currently, I’m in Product Design and this is where my other skills are really in need. Because the Product Design is not only about UI and UX, it is also about full product lifecycle, starting from problem identification, idea generation and finishing with some high-fidelity mockups and prototypes as solutions. At this role I am also responsible for some visual components of a product (it may vary from some web banners to brand guidelines and animations).</p><p>Thus, if you are new to design and technologies, try to find out what really interests you and who you will become in couple of years. Once you identified your specific area, be more expert in this by digging deeper and deeper.</p><h3>Pencils before Pixels</h3><p>The name of a title speaks for itself. You got an idea? Sketch it. You got a potential solution? Sketch it. You stuck during your design process? Start sketching from scratch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UH82BZ2B5rXTkYN7DJNq8w.jpeg" /><figcaption>Sketching example</figcaption></figure><p>But what is sketching? It is a rapidly executed drawing usually intended to represent an idea, concept or a solution. In other words, it is a pictorial representation of thoughts or some picture in your mind. Sketching helps you identify early stage issues that might be faced in future, when building prototypes.</p><p>Let’s say you need to design the checkout process for your app or product. Firstly, analyze the problem, find out possible solutions and outcomes and which of them are the most suitable for your TA (Target Audience). Then, based on your research sketch some screens and the flow of that process.</p><blockquote>“Drawing is not what one sees but what one can make others see.“— <strong>Edgar Degas</strong></blockquote><p>Well, as a Product Designer, my process was everything like I mentioned above. We got a problem, I started some basic analysis and research, then, based on my findings I proposed some hypothesis on how to overcome the issue. My proposals were supported with those sketches and, eventually, they became prototypes which could be used for some usability and information architecture testing.</p><p>You will spend 20% of your time and skills to do that drawing, however, those drawings will bring you 80% of your main result.</p><p>And that’s where the “Pareto Principle” takes place.</p><h3>The “Pareto” thing</h3><p>I bet everyone heard the term “Pareto Principle” and I guess majority of you know what exactly this means. However, I’ll make some things clear.</p><p>The Pareto Principle, or some call it 80/20 rule, states that, for many events, roughly 80% of the effects come from 20% of the causes. The term is originated from Italian economist — Vilfredo Pareto, who noticed that 80% of Italy’s land was owned by 20% of the population. In other words, 20% of the effort will generate 80% of the result.</p><p>Though, you may heard some variations, namely:</p><ul><li>80% of errors are caused by 20% of code</li><li>80% of sales come from 20% of sales staff</li><li>80% of attention is spent on 20% of the web page</li></ul><p>However, some figures may vary depending on a situation. But how is it connected to UX/UI Design?</p><p>Well, if you’ll do your UX research in terms of your product’s usability issues, you’ll might notice that fixing only several major problems will satisfy 70% to 80% of all users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*yTCMgoOrAmvCpwo6Jnoz9Q.png" /><figcaption>Of the 33 usability problems identified across 50 users, fixing nine of them would address 72% of all poor interactions.</figcaption></figure><p>The image above demonstrates the problems users faced while trying to rent a car on the enterprise website. Basically, of the 33 usability issues identified among 50 users, fixing nine of them will resolve 72% of all interaction problems. Thanks to Jeff Sauro’s article and research. For further reading, it can be accessed <a href="https://measuringu.com/pareto-ux/">here</a>.</p><p>As a Product Designer, I had faced a Pareto rule as well. In fact, while I was redesigning the UX of a specific webpage, I did some sketches (as I mentioned earlier). Those sketches took roughly 20% of my time and skills, however, the result and idea it brought to me was nearly 80% of what I really wanted. Drawings significantly reduced my time wastage and improved my analytical thinking skills as well.</p><h3>Analysis and Research are your best friends</h3><p>Did I mention analysis? Oh yes, and I will do it again. I mean, analyze everything you working with. Got a problem? Make some analysis. Too much of work to do? Make an analysis and prioritize things.</p><p>As a UX/Product Designer, you will face huge amount of user problems, for example: the flow of a website is bad and you lose your potential clients; navigation is awful and users just close the page/application; bad conversion rates at a specific webpages; and so on and so for.</p><p>While you got those problems, start with simple analysis. Identifying the problem right and accepting the right task will resolve the issue on approximately 80% of your main result. Oh, “80%” again. Funny, isn’t it? Now you know how everything is interconnected.</p><blockquote>“Do research. Feed your talent. Research not only wins the war on cliche, it’s the key to victory over fear and its cousin, depression.” — Robert McKee</blockquote><p>When I was receiving tasks, I kept questioning “why?” on every single fact, hypothesis and idea. Simple questions made my concentration pretty accurate. Starting from simple problem identification helped me navigate towards the right solution. Moreover, doing the UX Research supported my findings and ideas. Since then, I do really spend lil’ bit more time on doing research and analysis than expected, cuz’ those factors will influence the whole product in the future.</p><p>There’s not so much left to cover. Seriously.</p><h3>Programming? Sure, why not</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0Pz4IYlahikAfrdb8MZnbQ.jpeg" /><figcaption>Code, code, code</figcaption></figure><p>And the Award of the “most discussed question of all time” goes to “Should designers code?”. Well, it depends. (Most suitable answer of all time, I’m not kidding).</p><p>I mean, it depends because of you. You and nothing else matters. If you are planning to be a great Product Designer or, hopefully, Chief Design Officer (CDO), you should know at least how the system works and how Developers interact with each other. On the other hand, if you want to be an Illustrator or Graphic Designer, probably you don’t need programming at all. Cuz’ that’s not your area of specialization, right?</p><p>But I can say one thing. Learn basics of technology and how it works, at least it won’t be shameful of you not knowing how ordinary PC or system performs. This knowledge will help you understand the technology world and bring so many ideas to your creative mind; and, perhaps, you might be the second Jony Ive, isn’t it?</p><p>Well, I got my Bachelor’s in Software Development, so I do know some advanced things of how system operates. Moreover, working closely with Devs improved my analytical thinking skills and broadened my mind in terms of Programming. And now I can easily get along with Developers and make some friends there. And yes, I am planning to be a Developer later on. I love that.</p><h3>Ideas and discussions, discussions and ideas</h3><p>Never, never and again never refuse your ideas. Doesn’t matter how unbelievable they are, doesn’t matter how futuristic they are. Do not be afraid of any idea that comes to your mind. Be only afraid of not generating them. Note them down, even while taking a bus or a subway. Sort them out later on or discuss with your colleagues/friends.</p><blockquote>“Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.” — Scott Adams</blockquote><p>As a Designer, brainstorming process is really helpful and your job is to solve problems. Idea generation is the essential part of that process. It helps you to resolve issues in a very extraordinary way, however, you have to be aware of “over-unusualness” cuz’ you might break down the whole system or strategy.</p><p>Think a lot. Give your thoughts some space. Allow yourself some mistakes, but be aware of which ones to keep. Have a conversation with Devs or Product Manager, evolve yourself and one day you’ll be thankful for not stepping back.</p><h3>Conclusion</h3><p>So, to conclude my article, firstly, thanks for reading this. We made it.</p><p>Back to business.</p><p>Well, try to find out what really interests you the most and who do you see yourself in a 5 years or so. Then focus on one specific area and have a deep-down knowledge in it. Do learn some programming or technology things, whether you’ll be connected to Devs or not. Remember about “Pareto” stuff and drawings, cuz’ they’ll reduce your time and improve your thinking skills. It is better to show your proposal once, rather that explaining it a hundred times. Oh, and do not hesitate to propose some ideas and opinions, even if they are impossible to implement. Who knows, may be your idea will be game-changing?</p><p>And one more thing… Do not be afraid of who you want to be. Never.</p><p>Hope you learned something today and I’ll be very happy if you did. See ya soon, fellow seekers of truth, and there’s more to come!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fb3e808%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fb3e808%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Fb3e808%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href">https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3963050f850c" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/things-i-wish-i-knew-when-i-started-designing-3963050f850c">Things I wish I knew when I started designing.</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I learned while being a Product Designer Intern at Startup]]></title>
            <link>https://uxdesign.cc/what-i-learned-while-being-a-product-designer-intern-at-startup-62d2c6c27f85?source=rss-a7e21870e796------2</link>
            <guid isPermaLink="false">https://medium.com/p/62d2c6c27f85</guid>
            <category><![CDATA[user-interface]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Alisher Satybaldin]]></dc:creator>
            <pubDate>Sun, 14 Oct 2018 18:27:45 GMT</pubDate>
            <atom:updated>2018-11-16T17:41:45.925Z</atom:updated>
            <content:encoded><![CDATA[<h3>What I learned while being a product designer at a startup</h3><h4>Yeah, it’s about Design, of course, and a bit of myself.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nwA0eWmDU-7rk4hOpBkFJw.jpeg" /></figure><blockquote>“Stay hungry, stay foolish” — Steve Jobs.</blockquote><p>Greetings, fellow seekers of truth! This is my first post here, on Medium, and first blog post in my entire life, wow. I was always interested in writing, cuz’ words actually matter, you know.</p><p>Well then, let’s make something clear. Some of you, oh wait, all of you may wonder who am I and why am I writing. I don’t know, actually. But I like to express my thoughts via texts.</p><p>Straight to the point, I’m a 23-year old Product Designer who was an Intern at <a href="https://foxout.kz/">Foxout</a>. So this is, basically, an online ticketing platform for cinemas, theaters, sports events, etc. And you may wonder, where is it located, I bet you do. I’ll tell you, it’s in Almaty, Kazakhstan. Google it and you’ll be definitely surprised, yep.</p><p>To be honest, I got my Bachelor’s Degree in Software Engineering. You may ask me <em>”but why Product Design”</em>? I love it, but at the same time, I love coding as well.</p><p>However, I want to be a professional Product Designer who has abilities in Front-End programming (yeah, I do coding occasionally) in the next two or three years, at the same time gathering experience and skills in coding. Yeah, and after that, I am planning to be a Full-Stack Developer with perfect Design skills, cuz’ I believe this is a good skill stack for the future.</p><p>I worked at <a href="https://foxout.kz/">Foxout</a> for nearly 5 months and I learned several crucial things that I’m about to write. Hope you will find it useful or at least this won’t waste your time. So here we go.</p><h3>Communication Matters</h3><p>Well, you may think <em>“Oh Lord, seriously?”</em> but let me tell you what. That’s not exactly a usual chatting you face in a daily life, this is something bigger than just a <em>“communication”</em>. The level of understanding between the Designer and Developer (doesn’t really matter Front-End or Back-End) is vital. You have to be aware of Developer’s skills, interests, and vision of a product.</p><p>Fortunately, I had common interests with Front-End Developer and this helped me a lot. In fact, he has a very good sense of Design and, basically, receiving positive feedback really motivated me and made me proud of what I did.</p><p>Apart from that, working closely to a Developer team taught me how the website is actually built, its architecture and tools. But we’ll focus on it later on.</p><p>But what about <em>“usual communication”</em>? Oh, this is where it gets interesting. So, the <a href="https://foxout.kz/">Foxout</a> is a startup, where the agile environment (SCRUM) takes place. Thus, there is no such thing as <em>”boss”</em> or the person, who has more influence than you. Everybody is equal and this is truly great.</p><p>Going out for a lunch or dinner together with colleagues made the working environment very friendly. You can discuss everything you are interested in and they will always support the conversation, even trying to make a joke out of you or do something stupid. You literally can’t feel yourself awkward, cuz’ colleagues won’t make you think that way.</p><p>Yeah, there is such thing as <em>”CEO”</em>, however, she (yep, woman) won’t make you feel sad, trying to cheer you up or give some advice. And, yes, they always support outstanding ideas and ambitions.</p><h3>Time Management is everything</h3><p>Do you plan your day/week/month ahead? I mean, not in your mind, but using a notebook or a laptop. This actually makes a lot of sense. Check it out, you’ll be shocked by how much influence those notes can bring to your productivity and daily lifestyle.</p><p>While attending SCRUM meetings I noticed that every team member had its own notebook to make a status report. Moreover, during those meetings, all team members proposed some ideas of how to overcome the constraints faced during last week.</p><p>In the beginning, while receiving tasks I didn’t make notes to my book or laptop, relying on my memory and sense of responsibility. However, I did forget some points and felt myself bad, but, eventually, I got used to making notes of every single change being suggested. And this improved my time management skills to a whole new level.</p><p>Alongside with that, <em>”note-making”</em> really simplifies your planning as well as demonstrates the status of your task while reviewing it at the end of the day. Try it out, seriously.</p><blockquote>“The most efficient way to live reasonably is to make a plan of a day every morning and examine the results obtained every night” — Alexis Carrel.</blockquote><p>Still here? Perfect.</p><h3>Professional skills aren’t essential at some point</h3><p>This is what surprised me the most. I thought that being a professional with perfect skill stack will really make me a <em>”wanted”</em> person, however, my theories were broken apart into small pieces while working at <a href="https://foxout.kz/">Foxout</a>. And here is why.</p><p>At the beginning I was just gathering information and adapting to a workflow of the company, constantly improving my professional skills and trying to get along with colleagues. I thought it will be useful for them to be a versatile person, simultaneously designing and coding, however, eventually I realized it is better to be a more social-friendly Junior Designer rather than being a Senior Designer sociopath.</p><p>It is really harder to develop your soft skills rather than technical. You can be a very good Developer/Designer, but does it really make sense if you are an inadequate and closed person? I guess not.</p><p>In contrast, being a social-friendly and outgoing individual significantly increases your chances to be hired or at least be interested. Yes, you should have technical skills but it doesn’t matter how good they are. You always can develop them easily, in comparison to soft skills.</p><blockquote>“Soft skills are the hard skills” — Amy Edmondson.</blockquote><p>Seriously, do not forget that.</p><h3>Prototyping does make a lot of sense</h3><p>To begin with, let’s just define what <em>”prototype”</em> means.</p><p>A prototype is a physical representation of your product idea. It can be a very simple model made of cardboard or a very sophisticated one made almost identical to a real product by using advanced technologies.</p><p>Well, in my case it was an iOS Application. Honestly speaking, I didn’t make prototypes of every single feature being implemented, cuz’ I really thought I would make it at the end, however, early stage prototyping helped me to clarify whether I did it right or not. Here are some points being discovered:</p><ul><li><strong>A better understanding of the design and how it works.</strong> Prototyping not only demonstrates strong visualization of the product, but it also helps Designers easily comprehend of what they are designing, why and who they are designing it for.</li><li><strong>Early feedback.</strong> One of the most crucial aspects of product development is to gather feedback. Yeah, prototyping with all core functionalities helps Designers and Developers gather reviews even at early stage of development — whether adding new features or remastering product’s components.</li><li><strong>Early changes save time and cost.</strong> Changes towards the end would mean not just radical restructuring but also more speculation and rework. I mean, it’s much better to redo some parts at the beginning rather than changing something at the end of product development. Seriously, who would do that? Hence, be prepared.</li></ul><p>All in all, I do recommend you start prototyping every little change being offered or implemented. This will save you lots of money and, especially, time.</p><h3>Technology can make or break your product</h3><p>It’s no surprise that technology and skill stack also plays a crucial part in every product. You may think this is very easy to build a website with online payments that should be 100% secure for transactions, aren’t you?</p><p>But have you ever wondered how Developers choose the appropriate technologies, analyzing and identifying their own benefits and drawbacks? That’s a really complex process that needs a very detailed attention to even a minor issue or incompatibility. Cuz’ in the future, when the whole system is built, that single element can ruin everything you worked so hard for.</p><p>Well, close collaboration with Devs gave me real product experience and the backbone of the system. I was introduced to technologies, how those technologies contribute to each other and why they chose them. Also, I heard stories of how they were choosing the right stack and how they met deadlines at the start of their career, and I realized you have to finish everything on time, of course.</p><p>It was really easy for me to comprehend the information and workflow process of Development team, I even helped them, cuz’ as you remember, I got my Bachelor’s in Software Engineering. However, if you are out of programming, do read articles about it and be kind to Developers, they have a tough life, tho.</p><p>Yeah, we had some minor payment malfunctions couple of months ago and this is where technology can, actually, break your product or make it worse. Despite this, everything’s working pretty fine at a current state.</p><h3>Conclusion</h3><p>Still reading this? Wow, that’s really cool. We are almost done.</p><p>So to conclude everything, it really does matter of who you actually are. Not in terms of your technical skills, but in terms of your personality. As I mentioned, it’s better to be a socially outgoing person with a bunch of ideas and ambitions but without rich technical skills, rather than being sociopathic professional. It is easier to evolve your technical skills rather than soft ones.</p><p>And do not forget about time management, get everything planned and have a <em>”Plan B”</em> in case if everything is messed up. Do mind of your team’s ambitions, ideas, skills, and preferences. If you are working close to Developers team (like me), be aware of their preferences and do not make their life even harder.</p><p>Hope you read till the end and I really appreciate your effort reading this <em>”article”</em>. We made it.</p><p>Thank you so much and there is more to come. I’ve already got a couple of topics to discuss.</p><p>See you soon!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=62d2c6c27f85" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/what-i-learned-while-being-a-product-designer-intern-at-startup-62d2c6c27f85">What I learned while being a Product Designer Intern at Startup</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>