<?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 Vadim Kurnevich  on Medium]]></title>
        <description><![CDATA[Stories by Vadim Kurnevich  on Medium]]></description>
        <link>https://medium.com/@vadim.kurnevich.96?source=rss-93e6978207f2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*bqfWvEqBVrggI3EKiViJlQ.png</url>
            <title>Stories by Vadim Kurnevich  on Medium</title>
            <link>https://medium.com/@vadim.kurnevich.96?source=rss-93e6978207f2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 21:58:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vadim.kurnevich.96/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[3 подхода во заимодействии программист-дизайнер.]]></title>
            <link>https://medium.com/design-pub/3-%D0%BF%D0%BE%D0%B4%D1%85%D0%BE%D0%B4%D0%B0-%D0%B2%D0%BE-%D0%B7%D0%B0%D0%B8%D0%BC%D0%BE%D0%B4%D0%B5%D0%B9%D1%81%D1%82%D0%B2%D0%B8%D0%B8-%D0%BF%D1%80%D0%BE%D0%B3%D1%80%D0%B0%D0%BC%D0%BC%D0%B8%D1%81%D1%82-%D0%B4%D0%B8%D0%B7%D0%B0%D0%B9%D0%BD%D0%B5%D1%80-e8a492f35bb9?source=rss-93e6978207f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8a492f35bb9</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[designer]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[developer-tools]]></category>
            <dc:creator><![CDATA[Vadim Kurnevich ]]></dc:creator>
            <pubDate>Wed, 11 Dec 2024 11:25:02 GMT</pubDate>
            <atom:updated>2024-12-26T16:36:33.926Z</atom:updated>
            <content:encoded><![CDATA[<h3>3 подхода во заимодействии программист-дизайнер</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b0YQdoi4o-svuxJoshf-VQ.png" /></figure><p>Привет, я Вадим, продуктовый UX/UI дизайнер. В этой истории расскажу к каким практикам я пришел при передаче макетов девелоперам.</p><p>Впервые столкнулся с вопросом передачи макетов в 2018, изучал HTML, CSS, общался с программистами на работе и в баре. Мой подход продиктован исключительно собственным опытом работы и не претендует на абсолютную истину.</p><p>В зависимости от сложности проекта и вовлеченности дизайнера я выделил 3 подхода, о них и расскажу ниже.</p><h3>Базовый подход</h3><ol><li>После завершения работы над макетами и необходимыми компонентами поместите их отдельно — на отдельную вкладку в файле или в отдельный файл. Так вы создадите базовый MVP <strong>UI-kit</strong>.</li><li>Покажите программисту макеты в Figma: проведите обзор интерфейса, компонентов и оставленных пометок (если они есть). Решите, что лучше для взаимодействия — провести созвон или оформить все в письменном виде.</li><li>Объясните, где искать стили и как экспортировать элементы. <strong>Важно</strong>: следите за правильным неймингом слоёв в макете, иначе программисту будет сложно разобраться.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/791/1*lgtnYtLaBjObGhOMOb-SCg.png" /></figure><p><strong>Когда подходит</strong></p><ul><li>Небольшой проект (landing page, небольшой e‐commerce…)</li><li>У вас нет прямого доступа к разработчикам</li><li>Не прописаны требования к дизайн спецификации</li><li>Дизайнер имеет слабое влияние на проект и команду (аргументы далеко не всегда услышаны другими членами команды)</li></ul><h3><strong>Медиум подход</strong></h3><ol><li>Перед началом создания UI свяжитесь с программистами. Уточните технические ограничения, обсудите, какие компоненты проще и быстрее реализовать. Возможно, разработчики смогут переиспользовать готовые библиотеки (например, для сложных в реализации drag&amp;drop) вместо разработки с нуля.</li><li>При создании компонентов распишите, в каких случаях используется каждое состояние. Оформите эти данные в отдельный файл или на вкладку в Figma. И вот мы создали MVP <strong>Design guidelines</strong>.</li><li>Если программисты не знакомы с Figma dev-mode, объясните его основные возможности, отправьте обучающие ссылки и уточните, потребуется ли он им в работе.</li><li>Если сроки реализации ограничены, обсудите с командой альтернативные дизайн-решения. Либо договоритесь о создании MVP-реализации с участием дизайнера, программиста и менеджера, с условием доработки в будущем.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/972/1*Xc32lhMMcUQEX8JduXBVug.png" /></figure><p><strong>Когда подходит</strong></p><ul><li>Среднего размера проект.</li><li>Есть прямой доступ к программистам, у вас есть периодические звонки.</li><li>Вся кросс-функциональная команда синхронизирована, есть общие дейлики, ретроспективы.</li><li>Дизайнер погружен в процессы, может немного на них влиять.</li></ul><h3>Продвинутый подход</h3><ul><li>Попросите разработчиков предоставить доступ к фреймворкам (папкам с кодом, где прописаны компоненты, соответствующие дизайну). Если это невозможно, назначьте звонок, чтобы они показали визуализацию кода компонентов.</li><li>Договоритесь о создании страницы, где будет отображаться визуализация компонентов из библиотек, обновляющаяся при изменении кода. Проверьте, чтобы стили и состояния этих компонентов соответствовали тому, что задизайнено в фигме. Так вы получите MVP<strong> Design system</strong>.</li><li>Свяжите ваш файл фигма ссайтом-фреймворком для удобного перехода и проверки соответствия дизайна и кода. Совместно с разработчиками обсудите, какие элементы нужно дополнить в Figma или фреймворке для полного соответствия первого и второго.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TkPCDgc2XS9w2lMgjOR0bw.png" /></figure><p><strong>Когда подходит</strong></p><ul><li>Крупный долгосрочный проект</li><li>Есть прямой доступ к программистам, есть регулярные звонки, общие чаты, вы познакомились с тех‐лидами.</li><li>К дизайнеру прислушиваются, он имеет голос в команде, дизайнер может влиять на процессы в команде.</li></ul><h3>Заключение</h3><p>Эффективное взаимодействие между дизайнером и программистом зависит от масштаба проекта, уровня вовлеченности дизайнера в проект, отношений внутри команды.</p><p>Как вы уже поняли, <strong>UI-kit, Design guidelines, Design System</strong> помогают в коммуникации с разработчиками, отслеживании всех несостыковок в реализации фичей.</p><p>Вы можете строить свои процессы/фреймворки, которые помогут взаимодействать. <strong>Главная цель </strong>— наладить взаимопонимание с командой разработчиков и реализовать макеты в точности как было задумано.</p><p>Спасибо что дочитали!<br>Надеюсь, материал был полезным!)</p><p>По вопросам сотрудничества мы можем поговорить в <a href="https://www.linkedin.com/in/vadikun/">Linkedin</a> или в <a href="https://t.me/vad_6991">телеграм</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8a492f35bb9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-pub/3-%D0%BF%D0%BE%D0%B4%D1%85%D0%BE%D0%B4%D0%B0-%D0%B2%D0%BE-%D0%B7%D0%B0%D0%B8%D0%BC%D0%BE%D0%B4%D0%B5%D0%B9%D1%81%D1%82%D0%B2%D0%B8%D0%B8-%D0%BF%D1%80%D0%BE%D0%B3%D1%80%D0%B0%D0%BC%D0%BC%D0%B8%D1%81%D1%82-%D0%B4%D0%B8%D0%B7%D0%B0%D0%B9%D0%BD%D0%B5%D1%80-e8a492f35bb9">3 подхода во заимодействии программист-дизайнер.</a> was originally published in <a href="https://medium.com/design-pub">Дизайн-кабак</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-pub/%D0%BC%D0%B5%D1%82%D0%BE%D1%80%D0%B8%D0%BD%D0%B3-%D0%BD%D0%B0%D1%87%D0%B8%D0%BD%D0%B0%D1%8E%D1%89%D0%B8%D1%85-%D0%B4%D0%B8%D0%B7%D0%B0%D0%B9%D0%BD%D0%B5%D1%80%D0%BE%D0%B2-b78b8673c170?source=rss-93e6978207f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/b78b8673c170</guid>
            <dc:creator><![CDATA[Vadim Kurnevich ]]></dc:creator>
            <pubDate>Tue, 06 Aug 2024 08:46:59 GMT</pubDate>
            <atom:updated>2024-08-13T13:42:02.692Z</atom:updated>
            <content:encoded><![CDATA[<h3>Меторинг начинающих и молодых дизайнеров. Переделываем CV</h3><p>Привет, я Вадим, менторю с 2020 года. 10+ довольных студентов.</p><p>Месяц назад я взял на менторинг троих студентов, договорились пока что на 5 занятий с каждым, ниже пойдет речь о том, как мы работаем со студентами.</p><p>Сразу скажу, что данная статья не является истиной в последней инстанции, это скорее кейс из личного опыта менторинга.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nY5ERAbdIV4MtmnZN358YA.jpeg" /><figcaption>Источник — <a href="https://www.freepik.com/free-vector/internship-job-training-illustration_11107581.htm#fromView=search&amp;page=1&amp;position=16&amp;uuid=301aa25c-8cf8-4429-8e48-2028cc781fc4">Ссылка</a></figcaption></figure><h3><strong>Быстрый результат</strong></h3><p>Студенту нужно получить быстрый результат, чтобы увидеть ценность занятий с вами как с ментором. Более того, сейчас сложно найти работу, соответственно CV стало играть важную роль при отклике на вакансию. Мы со всеми 3 студентами сначала прорабатывали СV.</p><p>Мне это помогло узнать детальный бэкграунд каждого студента и в дальнейшем строить программу менторинга.</p><p><strong>Основные проблемы в резюме студентов:</strong></p><ol><li>Опыт расписан не полностью</li><li>Опыт расписан некорректно</li></ol><h3>Неполный опыт</h3><p>Часто начинающие специалисты стесняются некоммерческих проектов, хотя именно на них можно много чему научиться. Важно отметить что студенческий и некоммерческий это разное. В студенческом вы делаете полностью выдуманный кейс. В некоммерческом, по сути волонтерском, вы делаете реальный продукт/фичу, иногда на неполный рабочий день.</p><blockquote>Делал сайт другу, это не полная работа, мне за это не платили, да и дизайнил(а) я по 2–4 часа в день.</blockquote><p>Такой опыт нужно обязательно указывать в CV. Это реальный опыт!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zvwl_wxP-v7oSTa1chwE-w.png" /></figure><p>Если у вас опыт работы в дизайнах с перерывами, рекомендую посчитать, сколько итого опыта в дизайнах вышло и указать это число в верхней части CV, так как в вакансиях часто указывают требуемое количество лет. Это число сразу зацепит глаз рекрутера.</p><p>Также важно вспомнить как можно больше деталей о подработках, фрилансах, помощи на каких-либо проектах. Это все засчитывается за опыт работы!</p><p><strong>Пример</strong></p><p>Студентка мне сказала, что она делала какой-то сайт для друга, года 3 назад, но уже не помнит что там делала, в CV это не указано. Я настоял, чтобы она вспомнила, нашла того самого знакомого, собрала инфу. Как результат “всплыли” 3 дополнительных месяца опыта, весьма неплохой кейс, даже пару выводов оформили.</p><h3>Некорректно раписанный опыт</h3><p>Актуально тем, кто меняет профессию. Если вы подаетесь на вакансию UX/UI дизайнера, вы в праве указывать, что работали на сталелитейке, железной дороге или еще где-то.</p><blockquote>Я проводила инструктажи по технике безопасности для тех, кто работает у станка.</blockquote><p>Расписанные обязанности не дадут вашему CV веса, возможно, таже отторгнет рекрутера. Если у вас не было пересечения с дизайном, подумайте над следующим:</p><ol><li>Какие основные софт скилы нужны в дизайне интерфейсов?</li><li>Какие софт скилы вам удалось прокачать на прошлом месте работы?</li><li>Есть ли общее из пунктов 1 и 2? Если да, стоит записать!</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*efbqBC_WyuL1Ra4QTZ1zhA.png" /></figure><p><strong>Пример с железной дорогой</strong></p><p>Студентка работала на железной дороге, проводила ли инструктаж по технике безопасности многим сотрудникам. То есть имеется скилл knowledge-sharing. Я попросил вспомнить, как это проходило, были ли общие моменты, которым она научились, возможно были проблемы или заминки, которые быстро решала. В результате мы сжали данный опыт в CV и рапсисали основные поинты, которые помогут в поиске работы UX/UI дизайнером.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YSzC2G3b93FzfljE8nqTJA.png" /></figure><p><strong>Пример с програмистом</strong></p><p>В CV студента было написано, что был опыт работы прогером и расписаны технические задачи которые выполнялись. Но как это связано с дизайном? Удалось ли что-то почерпнуть? Мы полностью переписали 4 года опыта работы, вспомнили моменты как студент работал с дизайнерами, как передавались макеты, чего делать не стоит или что нужно сделать.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oL2tOKaMQ_DXUzTOoRkEhA.png" /></figure><h3>После CV</h3><p>Когда первый результат уже есть, он нравится и мне и студенту, мы договариваемся о продолжении занятий.</p><ol><li>С первым студентом мы стали прокачивать визуалы и делать новый кейс на behance.</li><li>Со вторым мы готовим по методу STAR продуктовый кейс в Notion.</li><li>С третьим мы имитируем собеседования и учимся правильно отвечать на вопросы менеджеров и дизайн-лидов.</li></ol><h3>Результат</h3><p>3 из 3 студентов решили, что однозначно стоит продолжать занятия. Для меня это большая победа и я очень рад успехам ребят!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/996/1*xpgUrniYt6JC8-0Qe91-cA.png" /><figcaption>Источник — <a href="https://www.freepik.com/free-vector/man-woman-touching-each-other-when-work-is-done_11879356.htm#fromView=search&amp;page=1&amp;position=44&amp;uuid=18f13b0f-e9e9-4775-850e-03594f62b621">Ссылка</a></figcaption></figure><h3>Как я строю процесс</h3><ol><li>Прошу выслать CV и портфолио заранее, чтобы я понаходил моменты, над которыми нужно работать.</li><li>Проговариваем ожидания и технические детали, узнаю чего хочет студент.</li><li>Собственно определяем точки соприкосновения и стартуем занятия!</li></ol><p>Спасибо что дочитали!<br>Надеюсь, материал был полезным!)</p><p>По вопросам менторинга можете писать мне в <a href="https://t.me/vad_6991">телеграм</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b78b8673c170" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-pub/%D0%BC%D0%B5%D1%82%D0%BE%D1%80%D0%B8%D0%BD%D0%B3-%D0%BD%D0%B0%D1%87%D0%B8%D0%BD%D0%B0%D1%8E%D1%89%D0%B8%D1%85-%D0%B4%D0%B8%D0%B7%D0%B0%D0%B9%D0%BD%D0%B5%D1%80%D0%BE%D0%B2-b78b8673c170">Меторинг начинающих дизайнеров</a> was originally published in <a href="https://medium.com/design-pub">Дизайн-кабак</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I designed taping module in a beauty app and we increased sales of subscriptions by 12%]]></title>
            <link>https://medium.com/design-bootcamp/how-i-designed-taping-module-in-a-beauty-app-and-we-increased-sales-of-subscriptions-by-12-d1c6277dd109?source=rss-93e6978207f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/d1c6277dd109</guid>
            <category><![CDATA[research]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Vadim Kurnevich ]]></dc:creator>
            <pubDate>Mon, 24 Jun 2024 16:32:50 GMT</pubDate>
            <atom:updated>2024-06-24T22:58:23.349Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vtHWVZvwOGKzqFRZIybdiA.png" /></figure><h3>Product</h3><p>Mobile beauty app forYou “Cosmetologist in your pocket”, 1+ mln downloads on <a href="https://play.google.com/store/apps/details?id=app.foryou&amp;hl=en&amp;gl=US">Play market</a>.</p><h3>Task</h3><p>Design instructions for applying and removing taped strips from the face, and generally deep into taping technology.</p><p>Global product hypothesis: adding taping module will increase paid subscription sales by 10–15%.</p><h3>My role</h3><p>I have been a product UI/UX designer since the very beginning of the creation of this app; communicate closely with the founders, especially at the implementing stage of a new functionality.</p><p>I also work with graphic designers after creating wireframes to talk about layouts and the specifics of drawing future illustrations.</p><h3>Context</h3><p>After we created the MVP, paid subscriptions and story articles, we didn’t know how to expand our audience reach and at the same time give existing users new techniques for caring for their faces. At this time, taping began to gain popularity.</p><p>This procedure is popular among athletes to restore and fix muscles after injuries. Strips with a special product are glued to the face and carefully removed after 2–8 hours, the muscles become toned and the skin tightens.</p><h3>Research</h3><p>Here I deep into the topic of taping, researched the interest of the audience and created a user flow with a cosmetologist.</p><h3>Discovery</h3><p>Here we interviewed some employees, analyzed the main flows for compliance with user expectations, and conducted a heuristic assessment.</p><h4>Google the technology</h4><p>In order to understand what we have to implement, I started looking for all the information on the Google. Key points:</p><ul><li>Since our application is about taking care of the face, I was looking for information about taping the facial muscles.</li><li>As we have to explain the value of taping in the application, I immediately went looking for evidence of good/bad results: the opinions of athletes, coaches, and rare beauty bloggers.</li><li>Since you need to prepare for the procedure, I described the objects and actions with them: you need cosmetic strips, they can be cut with scissors and glued to the face in any direction.</li><li>Also as we will have to warn in advance about various consequences, I found warnings: incorrectly applying the strips can ruin the skin or make the muscles worse.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vhFlgGmaCBQikdMhhmkUJQ.png" /></figure><h4>Value proposition and product statement</h4><p>Since at this stage we as a team still thought that this was a medical topic in sports and had little to do with cosmetology, I compiled a value proposition for potential and existing users of the application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fqgzbb27wsdXG5i3XiEAOQ.png" /></figure><p>Since it was difficult for our team to read the value proposition, I wrote a Product statement (more precisely, a feature statement). This formulation clearly helped the team understand what we would be working on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zhb_pY9VWONu8tAygSty9g.png" /></figure><h4>Hypotheses</h4><p>Before conducting research with users, I made hypotheses:</p><ol><li>The user has already heard about beauty tapes.</li><li>The user has no experience using tapes, did not order or test strips.</li><li>The user has an interest in the procedure at the level of trying it once or for a short period of time.</li></ol><h4>User research</h4><p>Since tapes are a new beauty technology that many have already heard about, I wanted to conduct Desirability studies with users who have heard about them.</p><p>To recruit people for the study, I organized a questionnaire inside our application. Among the 148 respondents, the answers were as follows:</p><ul><li>I don’t know anything — <strong>29</strong></li><li>heard but not used — <strong>117</strong></li><li>tried it with a cosmetologist — <strong>2</strong></li><li>tried it myself — <strong>0</strong></li></ul><p>The first and second hypotheses were confirmed.</p><p>After 9 interviews with those who heard but did not use, we came up to the conclusion that users have very little theoretical knowledge about tapes. The third hypothesis was partially confirmed, since 7/9 of the respondents doubt that they will wear tape strips on their face for more than 2–3 hours at home, or any hours in public space.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wcgMg3aAuts79FzSTerHjA.png" /></figure><h4>User flow with a cosmetologist</h4><p>In order to draw up the correct instructions for applying tapes to the face, the founders found an experienced cosmetologist. Having 2 calls the cosmetologist and I documented the key steps, importance of instructions and recommendations, allergies and side effects from taping.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n-x3GmskfVzXYeZV1X2i2A.png" /></figure><h3>Information Architecture of app and Screen mapping</h3><p>Since we were faced with the task of quickly and cheaply assembling a module with taping, I compiled the information architecture of the application in order to understand which implemented elements of the application could be reused. We reuse 80% of the elements in taping module.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cgz_58m4lME0U7zb3OkQBA.png" /></figure><p>Next, I compiled a map of screens based on the user flow, where I placed new and existing information elements inside each screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wlSmR5GDU4D4oIMNjE8U_g.png" /></figure><h3>Paper prototyping</h3><p>To imagine what the future functionality might look like inside the application, the founders and I drew sketches on paper. This helped outline the composition of future screens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q8yMKsVmySqatJva3etaxA.png" /></figure><h3>UI design</h3><p>I quickly put together an interface so that we could quickly assign the task to graphic designers to draw the necessary illustrations and send screenshots to development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IRYhLFs_J_DMGO7IcrdO4g.png" /></figure><p><strong>Taping main page and instructions page:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9c6tkqSxOEogzPI5DiUGHg.png" /></figure><h3>Analytics and results</h3><p>After the launch of the module, sales soared by <strong>12% in the first 3 months</strong>, then they began to fall, and a year later they returned to the same level before the creation of the tape module.</p><h3>Additional insight</h3><p>Since research into taping with users did not lead to many results, we rewrote the script on the fly. After 9 interviews, we discovered another opportunity for our application: few people know how to properly apply cream to their face. Further contextual research confirmed this and we began to work on this problem.</p><h3>Conclusion</h3><ul><li>According to AppHud, the sales were increased <strong>by 12% over the next 3 months,</strong> and we did not launch paid advertising and made only an in-app banner and several posts on Instagram and Telegram.</li><li>Due to the fact that the new module consists of <strong>80% old components</strong>, we saved approximately <strong>60 hours on development</strong>.</li><li>Additional insight opened up <strong>a new topic</strong> for us to research and design, although we did not expect to receive it.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d1c6277dd109" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/how-i-designed-taping-module-in-a-beauty-app-and-we-increased-sales-of-subscriptions-by-12-d1c6277dd109">How I designed taping module in a beauty app and we increased sales of subscriptions by 12%</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Drag&Drop of tables]]></title>
            <link>https://medium.com/design-bootcamp/drag-drop-of-tables-c14e11055404?source=rss-93e6978207f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/c14e11055404</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[patterns]]></category>
            <dc:creator><![CDATA[Vadim Kurnevich ]]></dc:creator>
            <pubDate>Wed, 05 Jun 2024 11:50:15 GMT</pubDate>
            <atom:updated>2024-06-12T16:31:41.069Z</atom:updated>
            <content:encoded><![CDATA[<h3>Drag&amp;Drop for tables</h3><p>How we designed d&amp;d functionality for tables in interface.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/994/1*oP8FVnc2hcuk-bj5FM7bLQ.png" /></figure><p><strong>Background</strong></p><p>Drag&amp;drop feature is time-consuming for implementation and testing.</p><p>Therefore, we implemented ‘cheap’ functionality ‘Move to right’, ‘Move to left’ buttons for table columns and ‘Move up’, ‘Move down’ buttons for table rows. It requires many clicks (thus, efforts) from users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/817/1*g44Y8-yl0Z2QpyyJjACOxQ.png" /><figcaption>Row moving</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/817/1*70xvIaxyXM8hsGmDcmdp1Q.png" /></figure><p>As we have many tables in interface, we prioritized d&amp;d realization for table columns and rows, when the team has some time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/817/1*-5X1mXZSg_PJj28ybOfE1g.png" /><figcaption>Drag&amp;Drop for rows</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/817/1*VBf-dUNkIHZfSgB6iMbqWA.png" /><figcaption>Drag&amp;Drop for columns</figcaption></figure><p><strong>Gestures overview</strong></p><p>First of all, we need to explore what other gestures can be implemented for for covering our interface needs.</p><p><a href="https://m2.material.io/design/interaction/gestures.html#properties">Material design</a> define 3 types of gestures:</p><ul><li>Navigational</li><li>Action</li><li>Transform</li></ul><p>We defined Drag&amp;Drop as a ‘Pick up and move’ transform gesture. This gesture logic we will discuss below.</p><p><strong>D&amp;D advantages</strong></p><ul><li>D&amp;D is a very good pattern when a user need to move elements in a list. It enhance the speed of interaction.</li><li>D&amp;D is more intuitive and closer to real world interaction for users than usual buttons. In main scenario, wherever the user put the cursor, the table column or row will be dropped at that place.</li><li>User controls the column/row moving from starting the drag till dropping to the specific place Friendly to touchscreens.</li></ul><p><strong>D&amp;D disadvantages</strong></p><ul><li>The main issue is accessibility one. Dragging the item can be difficult for people with motor impairments. D&amp;D can be even impossible for those who rely on keyboard navigation and screen readers.</li><li>If you have a scrollable space, it will be complicated for users to identify of where the component can be dropped.</li><li>As this pattern seems intuitive, the different states of interface can be look the default state.</li><li>We may use grab icon, but it is not an obvious indicator for users. There are multiple icons that fit to drag gesture.</li><li>There are no clear drag–and–drop signifiers like buttons, icons etc.. In this case how user will understand if this components can be dragged and where it can be dropped.</li><li>Technical realization is complicated, we will talk about it a bit later.</li></ul><p><strong>Define components, taking part into the action</strong></p><p>We created a shortened version of Blueprint to point out all interactions between the user and system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M60hW050RpJJr4dGh7eUow.png" /></figure><p>Actions the user does:</p><ol><li>User hover the grab handle icon inside the row/column</li><li>User press the mouse</li><li>User start moving the mouse to another place</li><li>User move the mouse across the board</li><li>User unpress the mouse and drop the row/column in a specific place</li></ol><p>Actions the system does:</p><ol><li><strong>Card</strong> appeared to hover state</li><li><strong>Cursor</strong> changed to ‘press hand’ state</li><li>Card place started to have a specific ghost state</li><li>The <strong>indicator</strong>, which show where the card can be dropped, appeared</li><li>Old place of dragged card disappeared, other cards moved and dragged card appears in correct place</li></ol><p>After that we defined what components take pat into the d&amp;d action:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/839/1*VSuN_FyV9HxWpcPPlE6xpA.png" /></figure><ol><li>Dragged element</li><li>Cursor</li><li>Dropped indicator</li></ol><p><strong>Now we need to design all states of these components</strong></p><p><strong>Dragged element.</strong> <br>We designed default state, hover state, dragged state, ghost state. There multiple ways to show the dragged:</p><ol><li>Show the whole element (Trello cards, Figma board).</li><li>Show partly transparent element (Bookmark panel Google Chrome, Linkedin web-site header).</li><li>Show the instruction of what you can do with dragged element (Gmail mail).</li><li>Show the shortened version of the element (E-commerce cards, table rows).</li><li>Avoid such element state (Figma layers).</li></ol><p>We defined the variant 4.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/914/1*PCWO8KF-5HYfxyIoZUlQ_A.png" /></figure><p><strong>Cursor.</strong> <br>There is no 100% correct way to indicate grab cursor state even in <a href="https://learn.microsoft.com/en-us/windows/win32/menurc/about-cursors">Windows</a> and <a href="https://support.apple.com/ru-ru/guide/mac-help/mh35695/mac">MacOS</a> guidelines. That’s why we picked up multiple combinations, discussed across team and selected the most ‘classic’ variant (var 1).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*TesqvhSOWToTKL09VGqQhA.png" /><figcaption>Windows cursors combinations</figcaption></figure><p><strong>Dropped indicator animation.</strong> <br>Here is the most complicated part. We had a chat with developers. We had a dilemma. Should we animate the components movement in a real time or firstly select the dropping place and after that animate the movement of all components.</p><p>Variant 1 is the best one as it shows system feedback immediately, but Dev team said that second variant is easier to realize so we continue with Variant 2.</p><p>Variant 1</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*xjUbbW0RPbHDaUQH1U1d1A.gif" /><figcaption>Example from <a href="https://www.pinterest.com/pin/570268371548411142/">https://www.pinterest.com/pin/570268371548411142/</a></figcaption></figure><p>Variant 2</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1001/1*8Q5ugKWIiO_zHCoOkc1ycg.gif" /></figure><p><strong>Dropped indicator 1.</strong> We have to show where the component will be dropped so we show it as a vertical or horizontal line depending of context.</p><p><strong>Dropped indicator 2.</strong> We added 2 states of the card, which are following user cursor: shortened state consist of just a part of head text. This allows users not to save the space and not to forget what component is dragged.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1001/1*WUFkvGYo8tLFYO6681WKOQ.png" /><figcaption>We show the part of the text in ‘dragged’ state of the row.</figcaption></figure><p>This experience works good if you have big complicated dragged elements like complex cards or table columns/rows if the first column has a text.</p><p><strong>When the animation starts</strong></p><p>It’s the biggest dilemma in this work.</p><p><strong>First animation</strong> starts when the user grab the component and move it in 1 pixel aside. In this case the ghost card state appears, the card itself appeared in a shortened version and follow the cursor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1001/1*enz5AgmoPmpDNUPBGsJIwQ.gif" /></figure><p><strong>Second animation</strong> starts when we move dragged component outside the edges of its ghost state. Dropped indicator line is appeared. Line is moving according the cursor movement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1001/1*8Q5ugKWIiO_zHCoOkc1ycg.gif" /></figure><p><strong>Third animation</strong> starts when user dropped the component. Ghost state disappeared, components are moved, dropped card appears in place where dropped indicator line was, dropped indicator line disappears.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1001/1*nsk7likM414KYZYxy4miJQ.gif" /></figure><p><strong>Touchscreen</strong></p><p>As we have D&amp;D icons which are 1cm*1cm size, it fits to a usual human finger. Algorithm is the same as on desktop: user should tap D&amp;D icon, constantly take a finger on screen, take of the finger when decided to drop the component.</p><p>Remember that there will be no card hover state on touch screen.</p><p><strong>Accessibility (briefly)</strong></p><ul><li>Ability to access D&amp;D icon via keyboard</li><li>Ability to access D&amp;D icon via screen reader. For more information <a href="https://www.youtube.com/watch?v=ZtIfXvN1udE&amp;ab_channel=DrDeniseMRobinson">take a look this video on Youtube</a> of the details.</li><li>All states of all components should be visually differentiated by users.</li></ul><p><strong>Implement and tech limitations</strong></p><p>For the dev team there was a challenge to implement Drag&amp;Drop. They used Angular library, as it’s a requirement from client side, and added some custom styles.</p><p>The reasons why we simplified dragged state and avoid showing all content are the following:</p><ul><li>- When dragging a large amount of content (1, 10, or 25 cells in a row or column), the dragged data can be too big, leading to some delay in loading the data into the dragged component. This might give users the impression that the interface is working with delays.</li><li>The table’s coding is a linear process where cells are coded first, then combined into rows, and rows into a table. Technically, we don’t have columns, but they are needed for dragging. To solve this, a dragged column is simplified within a rectangle along with text from the header cell. When the column is dropped, the table cells simply change their placement.</li><li>While a fully operational drag&amp;drop Angular framework could have been used, it lacked the ability to apply custom styles.</li><li>React libraries, known for their flexibility, were another option. However, they did not align with the client’s requirements.</li></ul><p>*I’m not an engineer, thus just trust these words.</p><p><strong>What we didn’t complete</strong></p><p>Unfortunately, we didn’t design micro-animations. D&amp;D elements change their states not smoothly thus it will be implemented on next release.</p><p>The system should give the user immediate feedback, that’s why on next release all elements in table will be moving while dragged element is not dropped.</p><p><strong>Conclusions</strong></p><ul><li>Drag&amp;Drop is a pattern where system feedback on each step is vital for users, especially if you design complex service. Think about all animations.</li><li>It’s a very cool pattern to make interface more flexible and user-friendly.</li><li>It takes much time to implement it in interface so make sure alternative solutions don’t solve your issues.</li></ul><p>Thanks for reading this article!<br>Very hope it was interesting and useful!</p><p>For collaboration and creating amazing projects we may have a conversation in <a href="https://www.linkedin.com/in/vadikun/">Linkedin</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c14e11055404" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/drag-drop-of-tables-c14e11055404">Drag&amp;Drop of tables</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we learnt Accessibility for UX/UI designers]]></title>
            <link>https://medium.com/design-bootcamp/how-we-learnt-accessibility-for-ux-ui-designers-946c886c8954?source=rss-93e6978207f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/946c886c8954</guid>
            <category><![CDATA[wcag-guidelines]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[user-centered-design]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Vadim Kurnevich ]]></dc:creator>
            <pubDate>Tue, 14 May 2024 10:36:08 GMT</pubDate>
            <atom:updated>2024-05-16T15:12:30.702Z</atom:updated>
            <content:encoded><![CDATA[<p>In this article you will find how we learnt Accessibility for UX/UI designers and what topics we covered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oS_CesOZ-6MnGYO4lZVj0w.png" /></figure><h3><strong>Context</strong></h3><p>Due to a very specific client visual tastes, we had so many light gray colors in texts, especially input labels and help texts. In a time stakeholder team was changed and now we really have an opportunity to make design a bit more accessible.</p><h3><strong>Task</strong></h3><p>We agreed to have multiple design meetups to fresh our knowledge in Accessibility, study new things from WCAG 3.0.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8avqINzrRdRZkhYiryJmOA.png" /></figure><h3><strong>How we got prepared</strong></h3><p>Our team defined that development and management topics in Accessibility will not be covered. We studied some key points this, but is out of design responsibility.</p><p>After that our team found different Accessibility guidelines from organizations and communities. Each guide has it’s unique knowledge. WCAG guides seemed us a bit high-level, while we wanted to have practical knowledge.</p><p>We took:</p><ul><li><a href="https://www.w3.org/TR/WCAG22/">WCAG 2.2</a></li><li><a href="https://www.w3.org/WAI/standards-guidelines/wcag/wcag3-intro/">WCAG 3.0</a></li><li><a href="https://a11y.mts.ru/definitions">MTC</a></li><li><a href="https://help.bolt.com/get-started/policies/accessibility/">BOLT</a></li><li><a href="https://www.udemy.com/course/the-ux-designers-accessibility-guide">Udemy Accessibility course</a></li><li>and many many articles</li></ul><p>As I was responsible to prepare meetups, I suggested 9 topics, which cover all guidelines.</p><p>After that we scheduled 9 meetups across design team and I presented the materials.</p><h3><strong>Meetups</strong></h3><p><strong>‘No stupid question’ approach<br></strong>During the meetup any person can interrupt the speaker and ask questions, sometimes we had 2x time longer meetups but it made sense.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kiU4scrFsYaAIeWJApqV8w.png" /></figure><p><strong>Statistics<br></strong>During each meetup we learnt statistics and disabilities, that help us to find arguments on meetings with stakeholders. When you provide quantities, stakeholders listen to you!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*19Mu_z38rHv_bdr9eCnufA.png" /><figcaption><a href="https://monsido.com/blog/accessibility-statistics">Link </a>to source</figcaption></figure><p><strong>Difference betweenWCAG guidelines<br></strong>We learnt difference between WCAG 2.2 and WCAG 3.0 guidelines and discussed which one to use in order to follow best practices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ebx7DG_A_tmfLwO6W7JFmA.png" /></figure><p><strong>Check-list<br></strong>At the end of each presentation together we formed a check-list of how to act and fix the issues, what we should remember as well as the instruments to test our designs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9tcJXlrtOQYlyxFbqiy68A.png" /></figure><h3><strong>Outcomes we use daily</strong></h3><ul><li>Designers started to use more ‘accessibility’ arguments during the meetings with BA and client team.</li><li>We started to use APSA contrast checker from WCAG 3.0 and refused from others.</li><li>We started to change our design system and reduce using of light gray colors for texts approximately in 20%.</li><li>The texts to links, buttons, notifications started to be more clear.</li></ul><h3><strong>Further actions</strong></h3><p>As we have a new design team on the project, we started deep them into our ‘accessibility’ pathway, help writing the texts.</p><p>Our plan is to get rid of all light-gray texts during 2 months (depending on dev team capacity) and add Accessibility guide to our design system in order to avoid using light colors for important content.</p><p>Thanks for reading this article!<br>Very hope it was interesting and useful!</p><p>For collaboration and creating amazing projects we may have a conversation in <a href="https://www.linkedin.com/in/vadikun/">Linkedin</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=946c886c8954" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/how-we-learnt-accessibility-for-ux-ui-designers-946c886c8954">How we learnt Accessibility for UX/UI designers</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</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-pub/%D0%BE%D0%BD%D0%B1%D0%BE%D1%80%D0%B4%D0%B8%D0%BD%D0%B3-%D0%BD%D0%BE%D0%B2%D0%BE%D0%B9-%D0%B4%D0%B8%D0%B7%D0%B0%D0%B9%D0%BD-%D0%BA%D0%BE%D0%BC%D0%B0%D0%BD%D0%B4%D1%8B-fc65404f580d?source=rss-93e6978207f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc65404f580d</guid>
            <category><![CDATA[communication-skills]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[onboarding]]></category>
            <dc:creator><![CDATA[Vadim Kurnevich ]]></dc:creator>
            <pubDate>Fri, 01 Mar 2024 13:08:48 GMT</pubDate>
            <atom:updated>2024-03-05T18:06:34.745Z</atom:updated>
            <content:encoded><![CDATA[<p>Как мы онбордили новую команду дизайнеров на проекте</p><p>Процесс онбординга сопровождается большим количеством вопросов со стороны нового сотрудника. Более того, скорость работы нового дизайнера в начале будет ниже средней скорости уже опытных ребят.</p><p>Нас на проекте 2 дизайнера, и тут приходит целая команда из 3 человек со своим тим-лидом, вы в разных часовых поясах с новой командой, и у вас есть 1–2 часа в день на коммуникацию!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SLYSYsaIW3eyG5Czw8pu9g.png" /></figure><h3>Задача</h3><p>Ввести в проект новых ребят, чтобы они как можно быстрее вникли и приступили к работе, учитывая, что примерный скоуп работ клиент им уже обозначил.</p><p>Четкого процесса онбординга дизайнеров на проект у нас не было, так как проект относительно молодой и приход нового дизайнера был редкостью.</p><p>Помимо создания общего чата с новыми дизайнерами и комментариев в фигме, мы решили сделать процесс более последовательным и четким.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E662Cf0Ifi3Mw5lx4VWrgg.jpeg" /><figcaption>Картинка взята <a href="https://www.freepik.com/free-vector/lawyer-justice-law-composition-with-doodle-characters-lawyers-with-paper-sheets-vector-illustration_23306546.htm#fromView=search&amp;page=1&amp;position=5&amp;uuid=69697372-a2f4-4585-9412-7f8059e15ad3">отсюда</a></figcaption></figure><h3>Первый созвон</h3><p>После создания общего чата в Teams, мы сразу же договорились на созвон, чтобы познакомиться, узнать у кого какой опыт в дизайнах интерфейсов и хобби.</p><p>Далее мы пошли от общего к частному:</p><ul><li>сначала рассказали в целом о чем сервис, который разрабатываем</li><li>рассказали про структуру файлов в фигме и структуру каждого файла</li><li>обсудили как храним макеты: где должны лежать актуальные в разработку макеты, где рабочие мокапы, а где просто концепции и идеи</li><li>процесс репортинга и коммуникации с БА командой и разработчиками</li></ul><h3>Документация</h3><p>Мы написали документацию по процессу работы над макетами, и отдали ее после первого созвона</p><p>Что в документации:</p><ul><li>Шаг за шагом весь процесс от создания мокапа до перемещения в вкладку для разработчиков</li><li>FAQ. Вопросы, которые возникали у каждого из нас на разных этапах процесса</li></ul><blockquote>Чтобы все следовали процессам из документации, напоминайте команде о ней почаще!</blockquote><h3>Карта сайта</h3><p>Этот артефакт я сделал для себя еще когда пришел на проект. Это помогло быстро сложить картинку в голове: сколько у нас функционала, где и какие взаимосвязи, иерархия.</p><blockquote>По моему опыту, новый дизайнер на проекте делает скрин-мап или юзер флоу, чтобы лучше понять связи функционала. Карта сайта помогает двигаться от общего к частному и быстрее разобраться в функционале.</blockquote><h3>Гайдлайны и UI-kit</h3><p>На общем созвоне мы также презентовали гайдлайны и UI-kit, но попросили смотреть его после документации и карты сайта. Что мы тут рассказали:</p><ul><li>структура гайда и кита</li><li>где лежат самые часто используемые элементы</li><li>специфичные кейсы, которых еще нет в документации</li></ul><blockquote>По гайдлайнам у новой команды в ближайшем будущем возникало много вопросов. Мы отнеслись к этому как наблюдатели: документировали все идеи ребят, вопросы по тому, что понятно и не очень, поскольку сами могли уже не заметить подобных вещей.</blockquote><h3>Ревью сессии</h3><p>Новая команда приступила к созданию мокапов. Каждый день начинается с того, что нужно просматривать макеты новых ребят, что-то уточнять или рассказывать, давать комментарии в фигме. Если вопросы касаются всей команды, мы сразу скидываем в общий чат.</p><blockquote>Еще никогда в наших файлах не было столько комментов как сейчас…</blockquote><h3>Капля дегтя</h3><p>Прошел месяц. Все еще есть вопросы к хранению и переносу макетов. На эту тему у нас еще будут звонки.</p><p>Новая команда периодически пропускает комментарии бизнес-аналитиков по макетам. Поскольку от коммуникации БА и дизайнеров зависит правильность и качество макетов, мы дополнительно обсудим контекст таких ситуаций.</p><p>Вначале практически вся коммуникация с новой командой проходила через их тим-лида. Теперь с нами спокойно коммуницируют все ребята.</p><h3>Результаты</h3><p>Новая команда втянулась быстро и уже через 2 недели ребята начали показывать первые готовые мокапы.</p><p>Весьма много времени ушло на изучение гайдлайнов и китов, так как у нас не было отдельного звонка по ним (к сожалению).</p><p>Взаимовыгода. Новая команда подмечает ваши рабочие моменты, а вы их. Взаимные фидбэки по макетам очень помогают развиваться. Помните, что они ваши союзники и вы их!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I1_7jofD9xVJSOvk69BFkg.jpeg" /><figcaption>Картинка взята <a href="https://www.freepik.com/free-vector/team-business-people-putting-hands-up-together_18734146.htm#fromView=search&amp;page=2&amp;position=23&amp;uuid=40f5fef7-5ebc-4814-97f3-0cf5dfa53779">отсюда</a></figcaption></figure><h3>Далее по планам</h3><p>Поскольку мы раньше многое не успевали делать, новая команда готовит инициативы того, что нам нужно поправить в гайдах и функционале. Мы со своей стороны тоже формируем такие идеи.</p><p>Далее мы объединим все наши идеи, структурируем, придем к бизнес-аналитикам и попросим внести их в приоритеты на проекте. Когда вас пятеро, выше вероятность повлиять на приоритеты в рамках проекта.</p><h3>Наши советы</h3><ul><li>подготовьте заранее письменную документацию по основным процессам в команде: хранение фалов, контакты тим лидов и менеджеров, FAQ, документирование изменений в макетах и т. д.</li><li>любые UX-артефакты будут полезны: карта сайта, персоны, юзер-флоу — это все стоит изучить новой команде до работы над макетами</li><li>созвонитесь с новыми ребятами, а лучше несколько раз с промежутком 1 неделя, так как большинство мелких вопросов задается и разрешается устно</li><li>У новых дизайнеров не замылен взгляд, и вместе вы улучшите опыт взаимодействия пользователей с вашим сервисом</li></ul><p>Спасибо что дочитали!<br>Надеюсь, материал был полезным!)</p><p>По вопросам сотрудничества и создания потрясающих проектов мы можем поговорить в <a href="https://www.linkedin.com/in/vadikun/">Linkedin</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc65404f580d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-pub/%D0%BE%D0%BD%D0%B1%D0%BE%D1%80%D0%B4%D0%B8%D0%BD%D0%B3-%D0%BD%D0%BE%D0%B2%D0%BE%D0%B9-%D0%B4%D0%B8%D0%B7%D0%B0%D0%B9%D0%BD-%D0%BA%D0%BE%D0%BC%D0%B0%D0%BD%D0%B4%D1%8B-fc65404f580d">Онбординг новой дизайн команды</a> was originally published in <a href="https://medium.com/design-pub">Дизайн-кабак</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I organized the redesign of an admin service, reducing task completion time by 20%]]></title>
            <link>https://medium.com/design-bootcamp/how-we-used-double-diamond-framework-and-what-we-outcome-e191a2f6b974?source=rss-93e6978207f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/e191a2f6b974</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[double-diamond]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[framework]]></category>
            <dc:creator><![CDATA[Vadim Kurnevich ]]></dc:creator>
            <pubDate>Wed, 06 Dec 2023 21:39:11 GMT</pubDate>
            <atom:updated>2024-06-24T16:24:36.440Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7MEzht-CFl8dSMvm9yy1_Q.png" /></figure><h3>About the project</h3><p>Service help to manage donation processes from large companies to non-commercial organizations. For example, Coca-Cola wants to donate $1 million to the homeless people in Africa or to the unemployed in California. Admin service employees set it up so that Coca-Cola managers go into the service itself, select a verified volunteer organization and send them money.</p><h3>Task</h3><p>Redesign existing admin portal in order to make it usable and easy-to-work there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n80QTONCWZlqCiR6wiDoug.png" /></figure><h3>My role</h3><p>I was on the project as a Product Designer and responsible for organizing the admin service redesign process: collecting feedback from three different teams, rebuilding the service in accordance with current business processes, and a create UI redesign.</p><h3>Portal audience</h3><p>There was identified 2 audiences. A team of business analysts in our company and a client-success team (CS team) in the client’s company perform tasks for large companies.</p><p>There is a team of managers in the client’s company, consisting of department heads, they are responsible for various areas in portal: sales, technical support, accounts.</p><h3>Problem</h3><p>For more than 15 years, the service has acquired a large number of new features that were integrated into the system in isolation from business processes:</p><ul><li>The service features were isolated from each other and did not work as a single organism, which started to make the user journey difficult.</li><li>The behavior of some components did not meet user expectations, which delayed the time to complete certain work.</li><li>Navigation and texts in the interface are written in “technical” language, which is incomprehensible to new employees therefore onboarding for newcomers lasts for 1.5–2 months</li></ul><h3>Metrics</h3><p>The client’s main wish was that employees’ work in the service would be 15–20 percent faster and more efficient. The time to complete a certain task in the service was taken as a metric.</p><h3>Discovery</h3><p>Here we interviewed some employees, analyzed the main flows for compliance with user expectations, and conducted a heuristic assessment.</p><h3>User interview</h3><p>During our team’s daily meetings, I heard the BA team discuss problems with the portal several times, so I decided to schedule an interview with them. The second designer and I created a script for the interview and scheduled calls. We interviewed using the “5 Why’s” technique to get to the core of problems. Everything was written out in an Excel spreadsheet. We asked about other similar services, problems with our service, where problems arise and how they are solved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z_B0WkdB-zgjyh4mILGu3w.png" /></figure><p>Next, together with the Product owner, the three of us analyzed the answers. 4 out of 5 respondents gave similar answers regarding the context of the problems. The respondent is given a certain task: to create system objects, set up the process of accepting applications from volunteer organizations, set up the paying process. And all the smaller problems lie within these tasks. So we came to the conclusion that our service has 3 main processes and their problems need to be analyzed.</p><p>First, I asked each of the 5 employees to whom I had direct access to estimate each of the 3 processes. The average setup of 1 out of 3 processes takes 1.5–2 hours for an experienced specialist and 3–4 hours for a new one. For us, this is the main metric.</p><h3>Screen map</h3><p>Next, I created a screen map of each process. In the screen map it became clear that:</p><ul><li>some intermediate actions turn out to be dead ends and the user needs to click back several times to continue working on the system.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-KqEImIYkJjUD4DM2ON6Eg.png" /></figure><ul><li>system objects that have a common meaning are located in different parts of the navigation (for example, mailbox roles are located far from the mailboxes themselves)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wnZY9kEEgMYQ47ZkPzVveQ.png" /></figure><p>The screen map confirmed most of the problems that users described during interviews.</p><h3>Heuristics analysis</h3><p>Since the screen map revealed only those inconveniences that were heard from respondents during the interview, I conducted a heuristic analysis of all 3 processes in order to identify other inconveniences in using the service.</p><p>Here are some conclusions from the heuristics:</p><ul><li>Correspondence between the system and the real world: a large number of terms and lack of explanations.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5T_tAy9dmFWAxXU_bAZCZQ.png" /></figure><ul><li>User control and freedom: the absence of “Undo” or “Redo” buttons lengthens the process of working with the system</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zVSDaDZ2gNjIZYuiKORYNQ.png" /></figure><ul><li>Consistency and standards: the work process is inconsistent, also the same button on page 1 opens the functionality in this tab, and on page 2 in a new tab.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jvJCXHFS6agJkv74mYuCaQ.png" /></figure><p>By the time I did the heuristic analysis, feedback came from a team of employees on the client side with a list of what they didn’t like about the interface and what features they wanted to see in the future. Separately, the product interviewed the management team on the client side and they sent their wish list.</p><p>PO and me discussed feedback:</p><ol><li>We received some suggestions from the team of employees as additional features that we will develop during the redesign a little later.</li><li>Based on wishes from the management team, we identified a fourth additional process: the process of setting up the personalization of sent letters. Since the fourth process is performed by employees separately from the other three, we will consider it after we have worked on the 3 already identified processes.</li></ol><h3>Design</h3><p>We decomposed the existing interface into an Information Architecture and reassembled the 3 main processes in the system.</p><h3>Information architecture</h3><p>To better understand what components a service consists of, what units of information, I decomposed it into an Information Architecture. Next we will use IA components in the redesign.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sC_-X3ECruODVokQKDk97A.png" /></figure><h3>Block scheme creation</h3><ol><li>We called the product and, based on one specific client company of our service, compiled a detailed description of what each of the 3 processes is about, what variables they have and how they work.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cwZoX46ElZbKLU8gbe9P5Q.png" /></figure><p>2. Based on the brief description, I put together a flowchart of how each flow works for the client company. This helped turn a story about a business process into an algorithm.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3490-uU788Y5VuG2EwB0cA.png" /></figure><p>3. I put the elements of the Information Architecture of our service on the elements of the flowchart and the structure of the future service was obtained.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*do5bdczYhowdOnk8p9JXqw.png" /></figure><h3>UI design</h3><p>I assume our team decided to move away from the green color in interface towards a more accessible blue. The original green failed any contrast test, and darker versions looked muddy. We made several key screens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7MEzht-CFl8dSMvm9yy1_Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FsZg-BbpoM3x_dOHGSOgjg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W_gQp57GULOwEAtjPHTy7g.png" /></figure><h3>Results</h3><p>We conduct feedback session with the same respondents. We showed new mockups, talked about changes in flows, and asked to estimate implementation of each flow. The average estimation is 1–1.5 (it was 1.5–2) hours for an experienced specialist and 2–3 (was 3–4) hours for newcomers.</p><p>After that, I organized a call with the BA and development teams. We estimated the time required to implement the redesign at a high level. I also wrote a guide: what the designer should work on in the future if the project is unfrozen.</p><h3>Conclusion</h3><ol><li>Identified all problems of the service</li><li>Conducted 5 user interviews</li><li>Created biggest Information Architecture in my life</li><li>Solved the user problems</li><li>Reduced the time to complete tasks in portal up to 20%</li></ol><p>For collaboration and creating amazing projects we may have a conversation in <a href="https://www.linkedin.com/in/vadikun/">Linkedin</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e191a2f6b974" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/how-we-used-double-diamond-framework-and-what-we-outcome-e191a2f6b974">How I organized the redesign of an admin service, reducing task completion time by 20%</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX after launching MVP]]></title>
            <link>https://medium.com/design-bootcamp/ux-after-launching-mvp-73871ec9a6d8?source=rss-93e6978207f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/73871ec9a6d8</guid>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[custdev]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Vadim Kurnevich ]]></dc:creator>
            <pubDate>Tue, 26 Sep 2023 22:04:02 GMT</pubDate>
            <atom:updated>2023-09-27T19:07:24.269Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r-gHkrLkg9UizIZSeZ6Sew.png" /></figure><p>Hey there!</p><p>I’m Vadzim, UI/UX designer with over 5 years experience in Interface designs. In my work I emphasize accessibility, content structure and user interaction. I like helping startups to create good User Experience and make the product more accessible and usable.</p><p>It’s my first article, I hope you will enjoy it!)</p><p>Today I want to tell you about what we did after launching MVP app in Play Market and how design work can help all the team members.</p><p>During 3 months the founder, co-founder and I were working on creating MVP of face massage app. It was a challenging process but the most interesting and challenging work was further.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jr2KxrAxPuKtGbG_6ExQqQ.png" /><figcaption>Big scary table of custdevs transcriptions</figcaption></figure><h3>Custdevs</h3><p>After a couple of months we launched MVP and we had 100–150 unique users. We understood that we need to ask existing and potential users about experience in the app, preferences in face massages, cosmetics etc. From that time I was responsible for holding custdevs.</p><p>The first challenge was to write a good script. I reached out to the cosmetologist who helped us to create face massages. This person has the biggest knowledge in the domain so I put down many questions and learned lots of information. After that I put down some questions from a developer about AR technology. My script looked like a cold marketing survey. I started to form a story. I rephrased questions into a warm conversation style, starting from the beginning: What’s your experience in cosmetology, when you started to take care about your face… also adding technique ‘5 why questions’. I tested the last version of the script on our new team member, polished it and finally I was ready to hold the first custdev in my life!</p><p>We created a form inside the app with a proposition to be interviewed. Actually people were excited to go to the interview, so we rapidly closed the form receiving 15 forms. Spoiler: we had only 11 interviews as we didn’t find convenient time to speak with other 4 persons.</p><p>I strongly suggest to schedule 3–4 custdevs during the day. No more, especially if you have small experience there. I requested each respondent for an audio recording. My firs interview was 50 minutes long, I used lots of parasite words with long pauses from my site, I forgot to say ‘Hello’ and present myself. I was lucky with a respondent as she was patient and supportive. Audio recording helped me to understand my mistakes and rebuilt the script. The last 11th interview was 35 minutes long, I even had time to make notes during it without losing the quality of a call!</p><p>Interviews helped our product to understand what our users want, but also it helped me to work with people, be more communicative and be an empathetic person. On this step most team members didn’t understand what I’m doing it for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*96jY9Hfi5o0gawcNoTGmNw.png" /><figcaption>Personas we created</figcaption></figure><h3>Personas</h3><p>I documented all 11 interviews in the excel table. It’s a lot of data. I decided to group respondents according to their answers. I suddenly realized that we had 3 personas!</p><p>I formed 3 personas based on respondents’ answers. I put down a photo, experience, motivation, needs, behavior. I was against putting the age to each persona but in our case the age really made sense. Also the text style is built from first person ‘I would like..’, ‘I want…’ in order to enhance the empathy to users.</p><p>After that I presented personas to our team. People were not very motivated and didn’t understand how it can help but at that time we had a rapidly growing team and everyone needed to be very user-oriented.</p><p>So personas helped not only to understand what users we have. On this step I presented to our team who we are designing for. It helped our colleagues get deep into the context, but just a little bit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QhqbykbJLEYJfVfeHIqvbg.png" /><figcaption>CJM for persona 2</figcaption></figure><h3>Customer journey</h3><p>But it was not enough! We went further and created a Customer Journey Map for each persona. So I prepared a simple draft, but didn’t fill it. I also created a detailed timeline of how much time we need to spend filling each column. During a one-hour session call we put the information into one CJM. There were 8 people so I moderated the call with the help of our project manager. Thanks to good moderation and following the timeline, we got insights from each team member for CJMs in time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sscyXDqr5uFF78dstqxAHQ.png" /><figcaption>Opportunities revealed from CJM of person 2</figcaption></figure><p>Having completed CJMs it was easy to reveal Opportunities for the app. For instance as an opportunity we explored the need to work on increasing customization even in the free version, fixing some technical moments with the AR module.</p><p>CJM was neither theoretical nor realistic. We didn’t have big experience in it, didn’t spend much time (usually startups don’t have enough resources to cover all UX) but we had real insights from our audience. On this step, having such an interesting workshop across all colleagues, it helped all of us to understand the value of such activities and sharing information about our audience.</p><p>Long story short</p><ul><li>Obviously, UX artefacts helped our team to create good designs in the future, scale the product</li><li>Interviews, personas and CJM helped to deep colleagues into the context who we are doing for</li><li>Team workshops is the best activity to ex0plain anything</li></ul><p>Thanks for reading this article!<br>Very hope it was interesting and useful for you to read it!</p><p>For collaboration and creating amazing projects we may have a conversation in <a href="https://www.linkedin.com/in/vadikun/">Linkedin</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=73871ec9a6d8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/ux-after-launching-mvp-73871ec9a6d8">UX after launching MVP</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>