<?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[Design Department - Medium]]></title>
        <description><![CDATA[Colleagues and friends share experience with the world - Medium]]></description>
        <link>https://medium.com/design-department?source=rss----392cc39f00db---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Design Department - Medium</title>
            <link>https://medium.com/design-department?source=rss----392cc39f00db---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 00:04:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/design-department" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Continuous Discovery Habits: How to Deal with User Interviews]]></title>
            <link>https://medium.com/design-department/continuous-discovery-habits-how-to-deal-with-user-interviews-a5945bdccfa?source=rss----392cc39f00db---4</link>
            <guid isPermaLink="false">https://medium.com/p/a5945bdccfa</guid>
            <category><![CDATA[collaborative-work]]></category>
            <category><![CDATA[user-interviews]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[continuous-discovery]]></category>
            <dc:creator><![CDATA[Julia Pchelova]]></dc:creator>
            <pubDate>Tue, 30 May 2023 09:05:23 GMT</pubDate>
            <atom:updated>2023-05-30T09:05:23.777Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*YtKk06o6OMv9RuXDSLjTMw.png" /><figcaption>The path through obstacles</figcaption></figure><p>Product teams need to keep in touch with customers on a regular basis — it’s simple. However, the world works differently. Despite the fact that the product community as a whole supports the development of products under the guidance of the customer, it is still difficult for most companies to implement this operating model when flexible teams independently make decisions about what to create next based on research and insights. We want to tell you how a B2B product has implemented a modern technology called Continuous Discovery.</p><h4>Problem</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Wg4_9eMhAZ_aHJHjxgwx0A.png" /><figcaption>Wasting time</figcaption></figure><p>We are faced with the fact that conducting interviews with our users has become very labor-intensive. We need to notify our users about the problem we want to discuss, write to everyone, and arrange a meeting, among other things. It is not profitable for us to pay for companies that help in hiring respondents or use other resources.</p><h4>Saving Time and Resources</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*dhbiRtkGY_mVdM4wTMxbTg.png" /><figcaption>Reference to Theresa Torres’ book “Continuous Discovery Habits”</figcaption></figure><p>The product manager of our team advised the design team to read “Continuous Discovery Habits” by Teresa Torres and consider whether we can use continuous research in our process. This approach is convenient because, once we have made an effort to create an environment for constantly hiring our users for interviews, the team no longer needs to spend resources on finding respondents and sending invitations. This becomes an automated process.</p><h4>Collaborative Efforts</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*SXeKlWB6-FC4SymKGpldAQ.png" /><figcaption>Upgrading workflow</figcaption></figure><p>We started our work on the implementation of this research by discussing with analysts, developers, product managers, and designers whether this process is suitable for us at all and whether it is worth investing effort in it. For the research, Teresa suggests creating a trio from the product team members — 1 PM, 1 designer, 1 developer. In our case, we wanted to include an analyst in this process. However, the planning of the research part has been postponed until we figure out how it will work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*FonVTX1Nir6jnx0KqNXtNw.png" /><figcaption>Recruiting users for research</figcaption></figure><p>We organized a meeting with the development team, demonstrated our idea, and asked them to consider how we could implement a separate pool of users into our database, add and remove users from there, and send them invitations every 30 days. Those who have already been contacted should be marked in the database to avoid spamming them with an invitation to an interview for the next 30 days. While the developers were thinking about the database architecture, the designers were creating a user flow to cover all the corner cases. By the next iteration, the analyst had applied the user flow, the tester had applied the requirements, and the designer already had layouts in which the user could independently include themselves in the pool of loyal users who would help to develop our product. The last stage was verifying the invitations, which we decided to send directly to the application for better conversion with the marketing department.</p><h4>Database Development and Adaptability for Panel Users</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Y9tKbFPmGG7PYeOdYctE9A.png" /><figcaption>Reducing the scope of tasks</figcaption></figure><p>The difficulties during the implementation stage were mostly related to the development and adaptability of our database for panel users. For all the features we were unsure about, we decided to try with an MVP and added an additional column to the database, along with an “if-else” condition when sending invitations from our admin panel.</p><h4>Results</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*z31g5NNs41MLMtqh0OzOsQ.png" /><figcaption>Improving the result</figcaption></figure><p>During the week, over 30 respondents responded and almost all of them were hired. The collection of contacts for the product manager took only 15 minutes… whereas before the changes it would have taken several days of focus.</p><p>Our future plan is to add additional columns to display the context for determining the target audience for any specific research.</p><p>Feel free contact us in case of any questions!</p><p>Lead Product Designer <a href="https://medium.com/u/a7b66e14951d?source=post_page-----aae832c1afc0--------------------------------">Bjorn the UX Dog</a>: mkinezumichg@gmail.com | <a href="https://dribbble.com/marinamelnik91">dribbble</a></p><p>UI designer <a href="https://medium.com/u/c2b1672d462?source=post_page-----aae832c1afc0--------------------------------">Alexandr</a>: aminibaev@hotmail.com | <a href="https://dribbble.com/minik">dribbble</a></p><p>Product Designer <a href="https://medium.com/u/b08a3a4738cc?source=post_page-----aae832c1afc0--------------------------------">Julia Pchelova</a>: pchelovajul@gmail.com</p><p>Product Designer Aleksandr: alecchernov@gmail.com | <a href="https://www.facebook.com/alecchernov">facebook</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5945bdccfa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-department/continuous-discovery-habits-how-to-deal-with-user-interviews-a5945bdccfa">Continuous Discovery Habits: How to Deal with User Interviews</a> was originally published in <a href="https://medium.com/design-department">Design Department</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Пункт назначения — смерть]]></title>
            <link>https://medium.com/design-department/%D0%BF%D1%83%D0%BD%D0%BA%D1%82-%D0%BD%D0%B0%D0%B7%D0%BD%D0%B0%D1%87%D0%B5%D0%BD%D0%B8%D1%8F-%D1%81%D0%BC%D0%B5%D1%80%D1%82%D1%8C-7a871d023e2a?source=rss----392cc39f00db---4</link>
            <guid isPermaLink="false">https://medium.com/p/7a871d023e2a</guid>
            <category><![CDATA[podcast]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-interface]]></category>
            <category><![CDATA[usability]]></category>
            <dc:creator><![CDATA[Bjorn the UX Dog]]></dc:creator>
            <pubDate>Tue, 29 Nov 2022 13:18:22 GMT</pubDate>
            <atom:updated>2022-11-29T13:18:22.211Z</atom:updated>
            <content:encoded><![CDATA[<h3>Пункт назначения — смерть</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/505/1*Xq6TXz9i-oll0pPr3IoVYQ.jpeg" /><figcaption>AI generated image: Enterprise’s death in Star Track</figcaption></figure><p>Антон Ельчин, восходящая звезда Голливуда, погиб под колесами своего собственного автомобиля. Это история так же трагична как и невероятна: как плохой дизайн мог привести к цепи событий, конечным пунктом которых стала смерть?</p><p>Слушайте новый эпизод подкаста Трукрайм Дизайн про плохой дизайн интерфейсов, который приводил к катастрофам, в <a href="https://podcasts.apple.com/ru/podcast/%D1%82%D1%80%D1%83%D0%BA%D1%80%D0%B0%D0%B9%D0%BC-%D0%B4%D0%B8%D0%B7%D0%B0%D0%B9%D0%BD/id1629655357?i=1000587820906">Apple Podcasts</a> и <a href="https://music.yandex.ru/album/22793220/track/109355610">Яндекс.Музыке</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fanchor.fm%2Ftruecrimedesign%2Fembed%2Fepisodes%2F--e1req61&amp;display_name=Anchor+FM+Inc.&amp;url=https%3A%2F%2Fanchor.fm%2Ftruecrimedesign%2Fepisodes%2F--e1req61&amp;image=https%3A%2F%2Fd3t3ozftmdmh3i.cloudfront.net%2Fproduction%2Fpodcast_uploaded%2F26370273%2F26370273-1654719197076-1dbaaa8674874.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=anchor" width="400" height="102" frameborder="0" scrolling="no"><a href="https://medium.com/media/290be58dd93ca71b99b00cc566541016/href">https://medium.com/media/290be58dd93ca71b99b00cc566541016/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a871d023e2a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-department/%D0%BF%D1%83%D0%BD%D0%BA%D1%82-%D0%BD%D0%B0%D0%B7%D0%BD%D0%B0%D1%87%D0%B5%D0%BD%D0%B8%D1%8F-%D1%81%D0%BC%D0%B5%D1%80%D1%82%D1%8C-7a871d023e2a">Пункт назначения — смерть</a> was originally published in <a href="https://medium.com/design-department">Design Department</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Plego: how to create scalable design system]]></title>
            <link>https://medium.com/design-department/plego-how-to-create-scalable-design-system-aae832c1afc0?source=rss----392cc39f00db---4</link>
            <guid isPermaLink="false">https://medium.com/p/aae832c1afc0</guid>
            <category><![CDATA[ux-designer]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design-process]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Bjorn the UX Dog]]></dc:creator>
            <pubDate>Sun, 23 Oct 2022 09:37:04 GMT</pubDate>
            <atom:updated>2022-10-23T19:36:54.398Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G3k8WHUsGiSL_jhVIekHoQ.jpeg" /><figcaption>What we know about flow?</figcaption></figure><p>A flow state is precious for long-term projects. It gives you the fruit of results and allows you to enjoy the journey toward the desired outcomes. People love to talk about the flow state, love to emphasize the value of the flow state, and love to guide how to reach this state. But how often can you say: Today, I have done the task without any obstacles and the necessity to pay the technical debt?</p><p>Neither of us — members of the product design team into a pretty big and pretty complex HR tech product — can say that we can “just take a seat and draw a solution.” It hurts, so we have decided to look at what if we can create a process where all of our product designers can focus on creating solutions, where creating an actual layout can be as easy “as playing Lego.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aZKXhb5_MFkrss6a0QLHmA.jpeg" /><figcaption>Meet the team</figcaption></figure><p>We grew up from the UX team of the One, where Marina started a fight to survive in the product with an already enormous existing interface with an absolute mess in Figma under the guise of a “UI kit.” But the challenge has been accepted due the work contract was signed up. There was the reality that the backlog was growing because our product was selling well. It meant that features should be produced somehow, and the team of one should be growing accordingly.</p><h3>The Challenge accepted</h3><p>The main problem, which had to be solved, was the inability of the Product designer to give a correct estimate of the task’s capacity. How can you predict how long you will accomplish the first version of the layout if you don’t know what elements are present in the system?</p><p>In addition, a peculiarity of our product strengthened the problem. We have an applicant tracking system with more than several dozen of modules and complex hidden logic. A primary user of our UI is a professional, who meets some knowledge prerequisites, to be able to aim his work tasks — eventually, our UI can be determined as complex.</p><p>The high density of elements, abundance of cognitive load, multilevel navigation, and connectivity of modules are all presented in our product and multiplied even a small design task by the system complexity.</p><h3>Ok, Doc… How can be solve the problem?</h3><p>At the beginning of the journey, as the first member of the department, Marina has got a legacy, which consisted of an already existing interface and a huge backlog of tasks. So, it was crucial to make the interface manageable and reduce the time to market at once.</p><p>The solution was to ignore the common spectrum of maturity for design systems and split the roles of consumer and creator of our design system from the beginning.</p><p>It allowed us to invest more resources into creating an easy-to-use design system and fixing problems of existing UI, while Product designers are focusing on creating a solution for product issues.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*Qnr-D2Wcc30uKn7Zs8HoAQ.jpeg" /><figcaption>The structure of the department</figcaption></figure><h3>Lack of consistency</h3><p>We realized that we greatly lack consistency and rigor in our design. Instead of starting to build a design system from scratch, we carefully looked through what we had already created. We already had a UI kit. There were complex heavy elements. Some of them were quite large, so we separated them to the atomic level. It would allow anyone using the design system to combine the atoms and molecules to form organisms that fit the needs of any page and the content. It was very important for us to eventually get flexible building blocks that could work in combination with each other in any combination. We also looked for similar elements, but not the same, and agreed on the same style. Research of all elements and styles was carried out both in the UI kit and in the production. Similar visual elements and functions were collapsed into one, other components were completely reassembled (for example, dropdown).</p><p>The color palette was limited to a small number of shades with a clear purpose of use, the same applied to other design tokens. For example, instead of the same shades of gray (#F5F5F5 and #F9F9F9) or buttons with different borders, we established common standards.<br>Such restrictions, of course, bind the hands of designers quite strongly. But this allows us to quickly develop new functions, reusing what is already ready, and not generate unconstitutionality in the future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FJdjfxETbgggVgP0RJ0e7w.jpeg" /><figcaption>How inconsistency was removed</figcaption></figure><h3>Building components</h3><p>The main goal was to create a Lego-like constructor from which to create a layout. A kind of framework tool within the development team for UX designers. We called our system “Plego” (Potok + Lego).<br>Each component has all possible states, which are switched through the settings panel in a couple of clicks. Inside, the components must have a clear structure and clear naming of layers and groups (No Frame 1, 2, 3), for easy support and reuse in the future. All product pages were moved to the library in the form of layouts, so that the designer did not need to reassemble the pages already, but only make changes to them if necessary.<br>This allowed UX designers to avoid using a separate Wireframe library, and design features to see the result immediately. And most importantly, all this greatly reduced the time from the design sprint to the design review.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6X8HZ5Plnc5HIPYRrUzcOA.jpeg" /><figcaption>Work with components</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BAVMaVH0KRHr2EXsqpuffw.jpeg" /><figcaption>What is behind of the ready layout</figcaption></figure><h3>The fruit of result</h3><p>A design system will always improve speed and quality in the long run. After the design sprint, we need to quickly demonstrate the first version for discussion with the team. With a design system, we can focus on the main problem instead of how a button has to look. Most of the interface is built with existing components.<br>Passing functions from designers to developers is less error-prone because developers can easily identify the building blocks used in projects and find the appropriate components and styles in the codebase. Standardization helps developers use code as efficiently as possible and ensure that the resulting user interface is consistent and consistent with the design. Improved reuse of existing implementations also means fewer bugs and cheaper refactoring.<br>A consistent design is often created using predefined components. This allows developers and stakeholders to make decisions quickly without wasting precious time on disputes. This saves time that can be used to create a product and make additional improvements.<br>Overall, a design-based, systematic approach to user interface development simplifies collaboration and communication and helps teams deliver a high-quality user interface with a shorter time to market<br>We strive to create as few components as possible that can be applied to a large number of use cases. However, we do not prevent the creation of new components. After testing them, they can be added to the system. <br>Sometimes a new component replaces an existing component because the new component is highly reusable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-2DEUKyQ9987u-rFwlM74g.jpeg" /><figcaption>Our product design process flow</figcaption></figure><p>A well-made design system also reduces cognitive load and increases the speed of development overall. Reusable components rely on each other, which creates a uniform appearance, feel, and behavior of the product. Just as consistency increases, so does user efficiency. Because designers and developers aren’t caught up in redundant questions or repetitive work, they’re freed up for projects that deliver more business value.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/870/1*bYtY73BAPXgKtFXOSxs_7Q.jpeg" /></figure><p>Feel free contact us in case of any questions!</p><p>Lead Product Designer <a href="https://medium.com/u/a7b66e14951d">Bjorn the UX Dog</a>: mkinezumichg@gmail.com</p><p>UI designer <a href="https://medium.com/u/c2b1672d462">Alexandr</a>: aminibaev@hotmail.com | <a href="https://dribbble.com/minik">dribble</a></p><p>Product Designer <a href="https://medium.com/u/b08a3a4738cc">Julia Pchelova</a>: pchelovajul@gmail.com</p><p>Product Designer Aleksandr: alecchernov@gmail.com | <a href="https://www.facebook.com/alecchernov">facebook</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aae832c1afc0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-department/plego-how-to-create-scalable-design-system-aae832c1afc0">Plego: how to create scalable design system</a> was originally published in <a href="https://medium.com/design-department">Design Department</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>