<?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 Dima Plotnikov on Medium]]></title>
        <description><![CDATA[Stories by Dima Plotnikov on Medium]]></description>
        <link>https://medium.com/@dim.plotnikov?source=rss-f7287fcf1ac7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*pbwYZ_Oe7OyywvDNsiQRLQ.jpeg</url>
            <title>Stories by Dima Plotnikov on Medium</title>
            <link>https://medium.com/@dim.plotnikov?source=rss-f7287fcf1ac7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 23:54:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dim.plotnikov/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[Writing Effective Documentation for Designers and Product Teams]]></title>
            <link>https://medium.muz.li/writing-effective-documentation-for-designers-and-product-teams-01bb7cadaa24?source=rss-f7287fcf1ac7------2</link>
            <guid isPermaLink="false">https://medium.com/p/01bb7cadaa24</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[design-system-operations]]></category>
            <category><![CDATA[team-management]]></category>
            <dc:creator><![CDATA[Dima Plotnikov]]></dc:creator>
            <pubDate>Wed, 24 Jan 2024 12:50:18 GMT</pubDate>
            <atom:updated>2024-01-24T12:50:18.629Z</atom:updated>
            <content:encoded><![CDATA[<h4>Best practices for crafting clear and useful documentation.</h4><p>Lately, I’ve found myself frequently writing documentation for designers and other product development team members. At some point, documentation seamlessly integrated into my daily routine, covering various aspects, and providing me with an opportunity not only to refine this skill but also to systematize the process and teach my colleagues. Now, I would like to share specific tips that can help make any guideline clear and user-friendly.</p><h3>Why Is Documentation Necessary?</h3><p>Any product begins with an idea, then evolves into something greater, and, receiving the necessary response and support from the community, starts to grow and develop. As the number of developers increases, communication undergoes a rapid evolution.</p><p>Initially, there is an opportunity to discuss everything offline, being in the same room. Then, meeting planning becomes necessary, and as the amount of information grows exponentially, there arises a need for systematization.</p><blockquote><strong>The reason for the necessity of any documentation lies in the scale of teams and the impossibility of conveying essential information through other means.</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k2OrTJD3SUhbkq061v0GGQ.png" /></figure><h3>Documentation Types We Will Cover</h3><ul><li><strong>Design system specification</strong>. The most complex aspect, considering how extensive design systems and component libraries can be.</li><li><strong>Product development process.</strong> Guideline that should be present in any product team, starting from the startup phase.</li><li><strong>Team management guide.</strong> In parallel with the product development process, it’s important to begin describing the team development process around the product.</li><li><strong>Newcomer onboarding checklist.</strong> Typically, this checklist depends on the size of the company. Sometimes onboarding can take pretty long. It’s important to guide newcomers during this period and make it clear what needs to be done.</li><li><strong>Brandbook and style guide.</strong> An integral part of any product that will be advertised and promoted externally.</li></ul><h3>Design System Specification</h3><blockquote><strong><em>Target Audience:</em></strong><em> Product designers, Front-End/Back-End developers, Business analysts, Product managers, QA specialists, and UX copywriters.</em></blockquote><blockquote><strong><em>Includes:</em></strong><em> Description of patterns, components, and fundamental principles of the design system.</em></blockquote><blockquote><strong><em>Consequences of absence:</em></strong><em> Loss of consistency and increased development time due to poor communication of existing components. Reduced learnability of the product due to inconsistencies in behavioral patterns.</em></blockquote><blockquote><strong><em>The main issue I encounter when designers describe a component or pattern are a lack of understanding of why they are doing it.</em></strong></blockquote><p>In such articles, you can find everything: component descriptions, their dimensions, as well as variations and states. However, this is something any developer can see by simply finding the component in the design library.</p><p>Unfortunately, quite often, these descriptions do not address the key questions — when the component can be used and what needs to be taken into account.</p><p>After testing several variations of the article structure describing a pattern or component, I have come to the following conclusions:</p><ol><li>While collaborating on documentation with colleagues, align on a template that would assist everyone in creating descriptions following a unified structure. Unfortunately, the loss of consistency in descriptions will only add chaos instead of aiding its utilization.</li><li>Include a screenshot of the component at the beginning of the description. The reality is that teams may refer to this pattern or component <strong>by different names</strong>. Only by seeing its illustration can everyone understand specifically what is being discussed.</li><li>Incorporate links to the library where this component is included. This link should be well-separated from the content and preferably placed at the very beginning of the page. This will help the team navigate to the specific component and see it in action.</li><li>After providing the core information about the component, list use cases where it is already in use. By use cases, we mean its application in various contexts where the component serves different purposes. <em>For example, a checkbox can be used with a label for confirming a specific action, and it can also be employed in a table for bulk selection.</em></li><li>When describing dimensions, focus on constraints — both the minimum and maximum possible sizes. Consider the entire functionality and the potential scaling of the component. If the component includes text, specify the acceptable character count.</li><li>The most crucial part of the specification is the usage guide. I would recommend approaching this section only after covering all use cases to comprehend the entire spectrum of the component’s utilization. Here, you should outline the prerequisites for using this component, and the limitations derived from UX analysis. It’s essential to differentiate between the capabilities of the component itself, which may exceed recommended settings.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UNUEOY5Ml5QW51EcwlpPog.png" /><figcaption>Illustration of the component specifications page.</figcaption></figure><h3>Product Development Process</h3><blockquote><strong><em>Target Audience:</em></strong><em> Project managers, product designers, business analysts, and product managers.</em></blockquote><blockquote><strong><em>Includes:</em></strong><em> Step-by-step guide, dependencies, and responsibilities in product development.</em></blockquote><blockquote><strong><em>Consequences of absence:</em></strong><em> Lack of team cohesion, particularly on a large scale. Failure to carry out necessary actions for the effective evolution of the product.</em></blockquote><p>Unfortunately, I’ve often seen a scenario where in one team, a business analyst is creating mockups while a designer is defining user stories. In another team, it might be the other way around. While this arrangement might be comfortable for everyone, when it comes to QA questions about reported bugs, confusion can arise regarding who should address them.</p><p>The entire process, from initiating work on a feature to supporting it in production, should be standardized.</p><p>What recommendations would help in this description?</p><ol><li>Start with the basics — describe the development stages and define the roles involved in the process. Gradually add details — meetings, and necessary actions for each participant. With all this outlined, it will be easier to understand how to structure the information.</li><li>Create a roadmap for the feature or product and specify responsibilities at each stage.</li><li>Visualize all processes using charts; utilize standard tools for this. Visualization is much more effective for information perception than a table or list.</li><li>This documentation should be part of the onboarding for new team members. If not emphasized during onboarding, a new team member is likely to introduce changes to the process.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1RvPGjayHyubKSCjDyySdg.png" /><figcaption>Sample process description for Business Analysts and Product Designers.</figcaption></figure><h3>Team Management Guide</h3><blockquote><strong><em>Target Audience:</em></strong><em> Managers from any department.</em></blockquote><blockquote><strong><em>Includes:</em></strong><em> Essential instructions for team development — maintaining motivation, setting development plans, goals, etc.</em></blockquote><blockquote><strong><em>Consequences of absence:</em></strong><em> Lack of motivation among team members.</em></blockquote><p>If you work in a company with a large number of employees, describing a team development plan becomes inevitable. Typically, this initiative stems from top management or the human capital department, and all departments adhere to the culture and rules related to employee motivation — goal setting, personal KPIs, quarterly reviews, etc.</p><p>I’ve had to document all the activities mentioned above. Honestly, covering all the necessary aspects of working with employees with straightforward instructions is quite challenging but crucial. As I discovered after a brief investigation, many individuals don’t even know how to conduct a proper 1–1 meeting and completely misunderstand its purpose.</p><p>Here, I can offer the following advice:</p><ol><li>Creating this documentation requires a thorough analysis of the current employee management practices and the desired standard. Conduct several interviews with managers, and gather feedback on what, in their view, works well and what doesn’t.</li><li>Remember that your target audience is managers who go through all stages with employees and need to understand what needs to be done at each step. <em>For example, the onboarding checklist should not only be with the employee but also with the manager to understand what information to provide to the new hire and when.</em></li><li>Don’t hesitate to describe even elementary activities, such as conducting reviews and setting goals for employees. Explain how to do it correctly and what to achieve from the employee during such meetings.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*91wRcCBHXta8eDN7dyqclA.png" /></figure><h3><strong>Newcomer Onboarding Checklist</strong></h3><blockquote><strong><em>Target Audience:</em></strong><em> New employees of the company.</em></blockquote><blockquote><strong><em>Includes:</em></strong><em> List of necessary steps for immersing into the company culture and product.</em></blockquote><blockquote><strong><em>Consequences of absence:</em></strong><em> Prolonged training for new employees. Extended period of not understanding the company’s principles of operation.</em></blockquote><p>With onboarding documentation, it’s either straightforward and serves its purposes or it doesn’t.</p><p>The most common mistake I’ve encountered is overcomplicated documentation instead of a simple checklist. The specialist creating this documentation is often at a different level of understanding of the processes, making it seem elementary to someone who has just started working in the company.</p><p>What advice can be offered in this regard?</p><ol><li>Keep the onboarding documentation simple, including only the essentials. Acknowledge that a new employee won’t be able to learn everything, even with a description of all aspects of the company’s operations.</li><li>The onboarding checklist should be easily accessible and serve as a step-by-step guide. Keep all materials for onboarding separately, including only links in the checklist.</li><li>Divide the onboarding list by days, specifying what exactly the new employee should go through each day. Time-bound tasks simplify understanding and reduce anxiety for the employee, who is undoubtedly concerned about the speed of information intake.</li><li>Experiment with different approaches. Gather feedback after the employee completes onboarding to understand what aspects of the documentation were not covered and why.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rvg82OQaEA7avvQny5W8RQ.png" /><figcaption>Onboarding page structure.</figcaption></figure><h3><strong>Brandbook and style guide</strong></h3><blockquote><strong><em>Target Audience:</em></strong><em> Marketers, marketing designers, marketing copywriters, and external agencies.</em></blockquote><blockquote><strong><em>Includes: </em></strong><em>Guidelines covering all the basics of product positioning: tone of voice, font specifications, colors, illustrations, etc.</em></blockquote><blockquote><strong><em>Consequences of absence: </em></strong><em>Reduced effectiveness of the marketing team. Lack of product recognizability.</em></blockquote><p>This type of documentation is usually handled by a marketing designer or manager. A brand book may overlap with the description of the design system in terms of specifying fonts, colors, etc. However, since the target audience differs, it is preferable to have a separate brand book as a supplement to the design system description.</p><p>How to create an effective brand book?</p><ol><li>First and foremost, consider whether there is a need to keep the entire brand book as a cohesive document. It might be worthwhile to create a one-pager for agencies that print marketing materials or prepare PowerPoint presentations for you.</li><li>Define a simple structure for slides/pages where you describe colors, icon styles, etc., and adhere to this structure throughout the brand book. It makes sense to try different structures at the very beginning to achieve the most suitable one.</li><li>Begin creating the brand book only after understanding the entire spectrum of possible marketing activities — from social media campaigns to producing stand banners and booths for exhibitions.</li><li>Emphasize good navigation in the brand book. Duplicate the section name on each slide, and include page numbers, and possibly clickable options for quick navigation to the next section. The problem with most brand books is that they are voluminous and contain a vast amount of information.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kYgoVh3fgmXRk-apPWOiEg.png" /><figcaption>Example of incorporating navigation elements into the brand book slides.</figcaption></figure><h3>Summary</h3><p>Any documentation requires periodic review and updates when there is an opportunity to test it in action.</p><p>Among the most important considerations, I would add not to forget about the inclusion of points such as accessibility. This is truly crucial in today’s context.</p><p>Overall, creating any document is only a small part of the work in this direction. There are many more challenges in its proper communication. But that’s a separate topic. I hope this article serves as your notebook for creating any documentation. Best of luck!</p><p>Feel free to add me on <a href="https://www.linkedin.com/in/plotnikov-dmitry/">LinkedIn</a>.</p><figure><a href="https://muz.li/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gvj1OPVrIjsVqPYlxT4Phg.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=01bb7cadaa24" width="1" height="1" alt=""><hr><p><a href="https://medium.muz.li/writing-effective-documentation-for-designers-and-product-teams-01bb7cadaa24">Writing Effective Documentation for Designers and Product Teams</a> was originally published in <a href="https://medium.muz.li/">Muzli - Design Inspiration</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Widespread mistakes made in the creation and scaling of design systems]]></title>
            <link>https://medium.muz.li/widespread-mistakes-made-in-the-creation-and-scaling-of-design-systems-2f4135922008?source=rss-f7287fcf1ac7------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f4135922008</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[design-strategy]]></category>
            <category><![CDATA[uikit]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Dima Plotnikov]]></dc:creator>
            <pubDate>Mon, 30 Aug 2021 14:22:18 GMT</pubDate>
            <atom:updated>2021-08-30T19:54:59.881Z</atom:updated>
            <content:encoded><![CDATA[<h4>PRODUCT DESIGN</h4><h4>5 things you need to think about in defining strategy and organizing the design team</h4><p>We’re all already pretty familiar with design systems. Recently, this topic has gained considerable popularity. It seems like hype is over, but many product companies are actively involved in their systems creating and getting their first bumps now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9wgS2XEKlw2NZBFOMi7yCw.png" /><figcaption>Design System Creation Process</figcaption></figure><p>In this selection, I would like to review some frequently observed mistakes when my colleagues are sharing the workflow of the design system in their projects, complaining about how complicated their development is. Meanwhile, they often express that it would probably be easier to live without it. Maybe it is so.</p><p>I don’t claim to be an adherent of adding bureaucracy to projects. However, I firmly believe that if you build it right, all your components could play a symphony, similar to a smoothly coordinated orchestra. I think it’s what your product needs.</p><h4>1. <strong>Creating a design system from scratch where it is not necessary.</strong></h4><p>It sounds crazy. But regrettably, this is the most common mistake made by teams starting on a product. They build their design system rather than buying an existing one. Considering that in some cases, they could have done with the UI kit at all.</p><p>Let’s try to draw a parallel. Now, let’s imagine that you are a beginning entrepreneur. You have start-up capital, and you need to decide how to house your employees. There is a 99% chance you will rent an office and do a quick renovation rather than buying your premises. This is the right thing to do, as spending a great part of your capital without prior validation of your business model is very risky.</p><p>Also, there is no reason to make this investment at an early stage with design systems. Moreover, if you buy real estate, you can immediately know the price, and when you create and maintain a design system, the cost is generally higher than you expected.</p><p><strong>Consequences of the mistake:</strong></p><ul><li>Loss of a huge budget when you start the product work.</li><li>The unplanned deceleration in the process of your product creation.</li><li>The transition to a hybrid model of advanced UI whale during product development. Reorienting of staff also engaged in the creation of design system.</li></ul><p><strong>What can we do to prevent it?</strong></p><blockquote>There are ready-made systems in the market that can fill all your product needs at the start of its creation. They typically include a set of components, patterns library, ready documentation. They also provided with support and regular updates. Some famous products as Twitter, Spotify have gone this way.</blockquote><h4>2. <strong>The process of creating and reviewing new components is overloaded.</strong></h4><p>This problem is often seen while extending library components.</p><p>We are often inspired by the experience of large companies when learning about their current processes. However, we forget that they have come to this model over time.</p><p>What do I mean? So let’s take a look at the path of creating a single component in a large and evolved design system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v_bo9f4Iw0c7Bcio-bkV7Q.png" /><figcaption>Component Creation Process</figcaption></figure><p>For each of these stages, it takes about 1–2 meetings of the different levels of staff. However, if there are difficulties at any stage, additional calls and discussions are possible. Thus, one component may take several weeks to complete.</p><p>It looks logical for companies like Atlassian or IBM. But, sadly, this model is also sought by younger products. Thus, they slow down the speed of creating components where they are extremely needed. Accordingly, it affects the design speed of the product itself.</p><p>The additional braking factor is the overloaded accounting of component development status.</p><p>I have seen a version where the staff of 3 professionals working on the system had to mark status in several tools simultaneously. They created a base in Excel, a table in Notion, and a separate space in Confluence. Also, these things are adopted from larger companies.</p><p><strong>Consequences of the mistake:</strong></p><ul><li>The extreme slowdown in the creation of new components.</li><li>Time loss in case of irrelevant created component.</li></ul><p><strong>What can we do to prevent it?</strong></p><blockquote>Occasionally, it is necessary to optimize the validation and review components. It is necessary to eliminate unnecessary steps that have no value. The important thing is to keep your eye on the ball to understand which part the component creation process takes in your product life. And whether it corresponds to the pre-defined product development plan.</blockquote><h4>3. <strong>The focus shifts away from the design of the product itself.</strong></h4><p>You probably have heard the saying that design systems are killing creativity. There are many articles about it on the Internet. The lack of freedom is mentioned almost everywhere to generate fascinating, creative solutions. The reason for this is the restrictions that the library of patterns and components imposes on the designer.</p><p>Of course, it’s possible that someone really wants to have all the freedom and pursue extraordinary solutions. In this case, the design system is unnecessary at all. But mostly, I heard this opinion when experts began to work on the system too early, and the work balance over product was lost.</p><p>At the time of active design system implementation, the max percentage of resources that must be allocated comes to 50%.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x2gHq8oNBCM6AJSfEewOmQ.png" /><figcaption>Team Resources Allocation</figcaption></figure><p>After the main part of the component and pattern library is built, and basic documentation is written, the support is usually provided by no more than 10–15% of resources.</p><p>The important thing is to realize that the system implementation should be started after the main concept of the product is ready. This means that a full UX research is done, all the main high-fidelity pages of the future product are formed and tested.</p><p><strong>Consequences of the mistake:</strong></p><ul><li>Unexplored potential in product visualization.</li><li>Resource loss for recycling components.</li></ul><p><strong>What can we do to prevent it?</strong></p><blockquote>The allocation of resources to activity team streams is always a floating issue. Keeping a perfect balance between building the system and improving the performance of the product itself is challenging. In this case, we need to remain flexible. Meanwhile, we shouldn’t save time on planning, setting goals, and coordinating with all the product’s stakeholders.</blockquote><h4>4. <strong>Incorrect team composition and scaling.</strong></h4><p>Imagine that you are building a house and hire builders when necessary. In the beginning, you need to dig a pit, and you ask for excavator services. But then the bricklaying begins and the bricklayers do their job. If you haven’t had time to recruit professionals to plaster the walls on time, you’re more likely to ask the bricklayers whether some of them can perform this service. In this way, some specialists also part-time perform other work on your future home.</p><p>Something similar occurs in the construction of the design system when you don’t have a correctly composed team. The only difference is that overlapping responsibility is unavoidable at the start. For instance, the interaction designer will be the researcher, the architect of the component, and the executor of its final design.</p><p>This is a normal situation for starting work on a system. But as you progress, you must scale the team appropriately. To understand which specialists and how many of them to hire, I suggest returning to the scheme of creating a component, we discussed earlier. As you remember, this is the way of creating components in a large developed design system. I will provide the minimum composition of the team, which should be enough to work at this stage of maturity, below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TyM06ijEk76uS13dTYs5qw.png" /></figure><p>And this team composition may be enough to start a design system:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1qM6thWkedC-IGKH-lwV4w.png" /></figure><p><strong>Consequences of the mistake:</strong></p><ul><li>Low speed of design system construction.</li><li>Low-quality implementation through the work of non-core specialists at certain stages.</li></ul><p><strong>What can we do to prevent it?</strong></p><blockquote>We are back to defining strategy and planning. It is advisable to make footnotes for each step in the roadmap and specify the composition at each stage of the system’s development. Accordingly, it is better to launch a search and recruitment campaign about 2–3 months before the next stage in the roadmap.</blockquote><h4>5. <strong>The lack of evolution in system design to favor scalability.</strong></h4><p>With the extension of our system, we feel like we’ve done something huge. The formidable construction will cover all our UI design needs and optimize our work in general. This process has taken a long time, possibly several years. Technology has certainly changed during this time. Everybody remembers the days when product design was mainly designed with Adobe Photoshop.</p><p>At the time of writing, there is a flowering and absorption of the market by Figma. This tool has revolutionized the design and cooperative collaboration process, and it is rapidly evolving. The auto-layout and variants are appearing, more systematic updates are announced. It is similar to front-end frameworks, where React has long surpassed Angular in popularity. All of this may not be relevant in 2–3 years. It is important to be aware of trends and tool updates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DPiIYtPasvj9pi3FEbr3cw.png" /><figcaption>Design System Scaling and Evolution</figcaption></figure><p>As we discussed before, your design system is a living organism, and it is equally important to allocate the resource and time for its renewal. In the case of the purchase of an existing one, this responsibility rests with the creators. The only thing you have to do is to make sure that your final interface has no unexpected bugs caused by component updates.</p><p>If you develop a design system by yourself, all responsibility regarding its relevance rests with you. Thus, you always have to strike a balance between scaling up and upgrading existing components. Unfortunately, the majority prioritize the first, which leads to a loss of relevance, and strongly affects the performance of your constructor in the future.</p><p><strong>Consequences of the mistake:</strong></p><ul><li>Resource overrun to keep the system design up-to-date.</li><li>The difficulty in recruiting staff and motivating them to work with outdated technology.</li></ul><p><strong>What can we do to prevent it?</strong></p><blockquote>It is necessary to keep abreast of trends and react to the appearance of new tools and frameworks in time. It is necessary to study them and assess the various scenarios for further development, including an immediate transition to new technologies or a slow transition with a gradual allocation of the resource.</blockquote><p>If the decision needs to be made while building a design system, a fairly common option is to refine along an already agreed with stakeholder’s path, using a minimum allocation of resources for a parallel update to the existing library.</p><p>Building quality and the well-coordinated constructor is a process, which complexity is usually underestimated. Unfortunately, everyone makes similar mistakes that they don’t like to recall publicly. I have experienced it myself and have seen my colleagues burned out along the end of the arduous journey of forming libraries and putting the product on a new track. But I still believe that design systems are the future and that interface design will become automated.</p><figure><a href="http://bit.ly/2MaZPRz"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IhOJjMQPqC2L13cGj0YqpQ.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f4135922008" width="1" height="1" alt=""><hr><p><a href="https://medium.muz.li/widespread-mistakes-made-in-the-creation-and-scaling-of-design-systems-2f4135922008">Widespread mistakes made in the creation and scaling of design systems</a> was originally published in <a href="https://medium.muz.li/">Muzli - Design Inspiration</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Ensure Value-driven Design in the Website]]></title>
            <link>https://uxplanet.org/how-to-ensure-value-driven-design-in-the-website-ec75d80fa5b2?source=rss-f7287fcf1ac7------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec75d80fa5b2</guid>
            <category><![CDATA[value-based-design]]></category>
            <category><![CDATA[data-driven]]></category>
            <category><![CDATA[website-design]]></category>
            <category><![CDATA[value-driven]]></category>
            <category><![CDATA[analytics]]></category>
            <dc:creator><![CDATA[Dima Plotnikov]]></dc:creator>
            <pubDate>Sat, 12 Sep 2020 21:04:54 GMT</pubDate>
            <atom:updated>2020-09-17T16:31:34.683Z</atom:updated>
            <content:encoded><![CDATA[<h4>USER EXPERIENCE</h4><h3>How to Ensure Value-Driven Design in Your Website</h3><h4>Analysis and practical examples</h4><p>In our design practice, we often come across ambitious marketing decisions that arise impulsively and reflect unmet expectations from the current website performance. These decisions have very little data to back them up and they are not explained by a long-term strategy. But at the same time, they require a lot of effort for implementation.</p><p>What is behind these decisions? Is it a value-driven or emotional need?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ujp0__UTjPSg9ve8r9p3Kw.png" /></figure><p>Let’s look at an example of a <strong>value-driven need</strong>:<br>“We are launching 3 new services that will enable us to reach a larger consumer audience. Before establishing a data science team, let’s evaluate what is needed and prepare the change-list for our website”.</p><p>Here’s an example of an <strong>emotional need</strong>:<br>“We are tired of our website, it looks like everyone else, let’s do a redesign. We want to refresh it and make it look different from others…”</p><p>There is a difference, right?</p><p>The value-based solution offers a specific product to the end-user. It is a need that we discovered, responded, and expectedly improved the performance.</p><p>Acting from emotional decisions, we run the risk to come to the wrong conclusions. Here we essentially roll the dice. For example, the look of a website might reflect the unique brand. Changing it can lead to negative results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4h8LZyBHdaP_VswZbW8qPQ.png" /></figure><p>We’ll explore best practices using the examples for the service company website. We will see how value-driven thinking can be applied to the website evolution process.</p><h3>Indicating specific performance targets</h3><p>Usually, we start by setting objectives for the website. At this stage, it’s important to be realistic.</p><p>First of all, it’s a good idea to talk with the stakeholders in the company. It could be the engagement department, marketing department, etc. The purpose is to find out how they use the website to achieve their own business targets.</p><p>Practically, interviewing department heads at the beginning of the process will allow us to get the broadest view of the expectations from the website, and further make a comparative analysis for prioritization.</p><p>After this we set objectives. A good framework for structuring the business targets of the website is the “Smart<strong><em>”</em></strong> template (<strong><em>s</em></strong>pecific, <strong><em>m</em></strong>easurable, <strong><em>a</em></strong>chievable, <strong><em>r</em></strong>elevant, and <strong><em>t</em></strong>imely). This framework allows us to write down the objectives as points aiming towards achieving the concrete result.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h9G8oiV1p4jbjMG1Aw6Tog.png" /><figcaption>You can get the template following the <a href="https://www.notion.so/Template-for-setting-your-website-objectives-8de6e348c636410ea8bc3942a14a48b5">link</a></figcaption></figure><p>You can fill out the table involving all stakeholders in the brainstorm session. Documented goals will literally create a clear vision and keep everyone on the same page. They lead to a focused approach and strategic thinking.</p><p>Each goal should have set time-referenced <a href="https://en.wikipedia.org/wiki/Performance_indicator">KPIs</a>. For example, an increase in traffic by 7% in the upcoming 4 months.</p><h3>Solving the user’s problem</h3><p>It’s easy for visitors to get stuck on the website where things that matter to us are a maze to them. Indeed, they don’t care who we are or how good the service we provide. They came to the website because they have a problem they need to solve.</p><blockquote>Website shouldn’t be a platform for service promotion. It needs to provide ​​a solution to the problem.</blockquote><p>This is a regular mistake on many websites. All services info is presented in the inner pages or components on the main page. It includes description, specifications and that’s all.</p><p>For some of the clients, of course, specifications and details will be important, so they will come in handy as well. But most people don’t order services guided by their description. They do it intuitively, based on their feeling if the service is solving the problem they brought to the website or not. This is what we sell them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4MkF_bOMwlzGXF0EJoyB3w.png" /></figure><p>We are not selling a car by laying out the entire lineup with detailed descriptions. But we first ask the client “Why do you need a car?” in order to choose what the client needs and present only one or two models.</p><p>And similarly, IT services can’t be sold directly, due to including highly qualified specialists, exciting workshops, and a full range of activities divided into sprints. We sell a completed product that will facilitate the client’s business processes. It will give him the opportunity to earn money and no longer remember that this was a problem some time ago.</p><p>Every business has pain points. As better we make research and discover the client’s difficulties, as better, we will be able to meet their needs. Only conducting interviews with users and asking questions about the problems they face, can help to understand these needs, sort them out, and create a <a href="https://uxstudioteam.com/ux-blog/value-proposition/"><strong>meaningful value proposition</strong></a>.</p><h3>Showing tangible results</h3><p>The next important component for value-driven design is the building of an understanding of the end result. It is important not to be abstract here.</p><blockquote>The client should clearly project the impact of the efforts on the results of his business.</blockquote><p>In my practice, I have often seen that clients were aware of the importance of a well-considered service and were confident in the developers’ expertise but still were not always sure what the final result they would get. And most importantly, they couldn’t understand how to measure the positive and negative scenarios.</p><p>In different words: We have created a service, but what exactly will it provide? How will the client’s business change after our involvement?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_9T3iEwQbVIhBD78dY3LmA.png" /></figure><p>Information that the company has already done 350 websites doesn’t bring the value. It also makes no sense to show the awards of well-known companies that have contacted you. It may look spectacular, but it will not be Youeffective. They could entrust you with an insignificant role in the project.</p><p>Reaching the Case Study page, the user wants to know exactly what we had to deal with, what the situation was at the beginning, and what was the process of solving the problem, and what were the business indicators after cooperation. It will be especially convincing for the clients whose case is identic to the described one on the website.</p><p>There are the most common KPI that we use to measure the performance:</p><ul><li><strong>Net promoter score</strong></li><li><strong>Customer Satisfaction Score</strong></li><li><strong>Customer Effort Score</strong></li><li><strong>Basis Points (BPS)</strong></li></ul><p>What kind of indicators to use in the proposal depends on the specifics of the service provided. But it definitely gives the message of aiming at results, instead of selling the service itself.</p><h3>Turning customers into heroes</h3><p>Another mistake service companies usually do is positioning themselves as heroes by means of collaboration with a client.</p><p>Typically, the list of clients is published as a collection of awards with brief explanations of the experience, where we tend to take more credits and believe that we look perfect in this way.</p><p>This way, we are missing the opportunity to convey another value to the customers — <strong>empathy for success</strong>. The companies looking for a contractor are essentially playing the role of Luke Sky Walker and want to find Master Yoda, who will be leading them to their goal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ikIuxgNyfXcOvswsbztcYg.png" /></figure><p>By making a hero from the client, it makes clear that we associate our own success with theirs and we have a personal stake in helping them build their business.</p><blockquote>McKinsey research has shown that 70% of buying experiences are based on how the customer feels they have been treated</blockquote><p>I’ve seen a lot of heatmaps, which showed that the user is particularly interested in the portfolio. Then he moves to the services, reads the description, and visits the page “about the company” to get familiar with the company. If the portfolio section is designed correctly and the client’s success is highlighted first, and you are displayed as an assistant, the website visitors will understand your values and it will immediately inspire confidence.</p><p>If you want potential clients to care about your company, first show that you care about them. Putting the customer in the spotlight will definitely increase loyalty and open up new business opportunities.</p><h3>Testing assumptions with analytics</h3><p>Value-driven decisions don’t come directly from analytics. We need this quantitative data only to confirm or deny the hypotheses we are testing.</p><p>When we see a need, we are formulating a hypothesis to satisfy it. And at this stage, it’s okay to sometimes make emotional conclusions as well. The challenge is to make sure that our thoughts are correct and that the decisions based on emotions make sense. Analytics helps combine emotion and science.</p><p><strong>A/B test</strong> works best for hypothesis testing. But it doesn&#39;t fit if, for example, we are adding an element for a tactical long-term goal and want to test its effectiveness. In this case, validation is possible through general statistics from a long period of time.</p><p>It’s important to set a time frame for the validation of each performance goal. In my opinion, the ideal period is 2 weeks for each test. After this period, we make conclusions from the results. Some tests may take less time. While we are following the data, it’s possible to make minor adjustments to eliminate the inaccuracy of the result.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V1slB3CdaKHU9nS9bLK15A.png" /></figure><p>At the end of the test, we can come back to the questions that were raised at the beginning of the experiment and answer them:</p><ul><li>How did the client respond to the new strategy?</li><li>What was the most successful on the way to the contact form</li><li>How many visitors increased on a specific page on the website?</li></ul><h3>Revising and adjusting strategy long the way</h3><p>One of the certain things to remember from documenting the strategy is that it is a living document. Extremely important to <strong>continually review the strategy</strong> and make adjustments based on test results or new requirements.</p><p>A good example is a current situation. The world has significantly changed with the outbreak of COVID-19. A large part of the business has gone online. Therefore, it is time to update personas and rethink the positioning strategy according to the changes in the target audience.</p><p>This will be followed by a list of changes to adapt the website to the new reality.</p><p>It could be the implementation of different information policy in the blog or approach modification in some of the service activities. Maybe it will make sense to highlight a short message on the main page of how you run discoveries, workshops, and meetings, in general at this period time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lNabj7uM_DegiFsJz-15-Q.png" /></figure><p>And of course, it could be the opposite: we can keep everything the same and create the impression that there are no changes in the company. It makes sense if we feel that customers expect this kind of behavior.</p><p>To obtain qualitative data from users&#39; behavior on the website, I would recommend such a tool as <a href="https://www.hotjar.com/"><strong>Hotjar</strong></a>. In addition to basic analytics, it allows us to test user behavior on a specific page. There is also the possibility of creating a survey or collecting quick feedback. But you need to be careful with this. This type of testing is not suitable for all audiences.</p><p><strong>Resources I found helpful:</strong></p><ul><li><a href="https://www.linkedin.com/pulse/from-data-driven-value-driven-company-isabelle-fl%C3%BCckiger/">From a data-driven to a value-driven company</a> by Isabelle Flückiger</li><li><a href="https://www.nngroup.com/articles/perceived-value/">Perceived Value in User Interfaces</a> by Aurora Harley</li><li><a href="https://www.mckinsey.com/business-functions/marketing-and-sales/our-insights/why-the-customer-experience-matters">Why the customer experience matters</a> by Bill Javetsky</li><li><a href="https://the-pastry-box-project.net/meg-lewis/2015-december-15">Value-Based Design</a> by Meg Lewis</li><li><a href="https://www.nngroup.com/articles/risks-imitating-designs/">The Risks of Imitating Designs (Even from Successful Companies)</a> by Kathryn Whitenton</li><li><a href="https://www.nngroup.com/articles/original-top-ten-mistakes-in-web-design/">Original Top 10 Mistakes in Web Design</a> by Jakob Nielsen</li><li><a href="http://www.dubberly.com/wp-content/uploads/2008/06/ddo_article_cooper.pdf">Goal-Directed Design Process</a> by Alan Cooper</li></ul><p><em>Feel free to get in touch with me on </em><a href="https://www.facebook.com/pIotnikov/"><em>Facebook</em></a><em>, </em><a href="https://www.behance.net/d_plotnikov"><em>Behance</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec75d80fa5b2" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/how-to-ensure-value-driven-design-in-the-website-ec75d80fa5b2">How to Ensure Value-driven Design in the Website</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[How to get executive buy-in for your design system approach]]></title>
            <link>https://medium.muz.li/how-to-get-executive-buy-in-for-your-design-system-approach-8bdf2e5976c9?source=rss-f7287fcf1ac7------2</link>
            <guid isPermaLink="false">https://medium.com/p/8bdf2e5976c9</guid>
            <category><![CDATA[uikit]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[team-alignment]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Dima Plotnikov]]></dc:creator>
            <pubDate>Thu, 09 Jul 2020 09:07:33 GMT</pubDate>
            <atom:updated>2020-10-08T19:23:59.015Z</atom:updated>
            <content:encoded><![CDATA[<h4>PRODUCT DESIGN</h4><h3>How to Get Executive Buy-in for Your Design System Approach</h3><h4>Argument collection to convince the product stakeholders to build a design system</h4><p>Today, design systems are mentioned in almost every conference dedicated to Internet marketing. Media makes ratings of the most successful cases, and big brands are actively working on their implementation. In this article, we’ll talk about why design systems are needed and how to correctly implement them in business.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KslHsEfT36mH42nnHvVJSQ.jpeg" /></figure><h3><strong>What is a design system</strong></h3><p>The term itself appeared in the middle of the 20th century. During this period, design systems were actively in demand in retail: supermarkets and product manufacturers used them to create the identity of their packaging.</p><p>With the Internet, web design has confidently stepped into our world. Until the end of the 2000s, it was quite primitive: the websites were a series of chaotic flash-animations and were completely uncomfortable to use. There was no such term as usability.</p><p>The situation changed after 2010 when people thought about <strong>how to make the site user-friendly and optimize the resources of the team that works on it</strong>. These problems had to be solved by the design system.</p><p>In fact, such systems on the web are elements of the visual part of the brand. They consist of small particles: fonts, colors, shapes, icons, transparency, and rounding. The components of the site are assembled of those — buttons, input fields, text blocks, forms, filters, and bar elements. Meanwhile, the code is attached to them, which allows the layout designer to quickly construct new projects.</p><p>The first meaningful attempt to create such a system was made by <strong>Google</strong>. In 2014, the <a href="https://material.io/design">Material Design</a> project was launched, which changed the interface of Youtube, Google Maps, and other services of the corporation. Later, similar systems appeared at large international brands — banks and online services. We could find the best examples of the design system on some web platforms. The most famous of them were <a href="http://styleguides.io/">styleguides.io</a> and <a href="http://designerlynx.co/">designerlynx.co</a>.</p><h3><strong>Who needs a design system?</strong></h3><p>Design systems are convenient for the end-user. Practically, everything is implemented for him. Everyone should feel equally comfortable surfing the company’s content through an application or a desktop browser.</p><p>Large services that often updating current products and launch new ones require such systems. A good example is <a href="https://airbnb.design/building-a-visual-language/">Airbnb</a>. According to the creators, building the design system was worth the investment and a huge leap forward. Since the design language and code are often shared, they can build and release features on all native platforms at roughly the same time. Development became generally much faster.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IBxATO9H6r14y17aQ8okeA.jpeg" /><figcaption>Airbnb’s Design System Component Page</figcaption></figure><p>Design systems are also in demand for small fast-growing projects, as they facilitate to quickly launch new services, including new sections and functions on sites.</p><h4><strong>In general, a design system is able to achieve the following business objectives:</strong></h4><ul><li><em>Increase brand recognition</em> — a company, that designed every detail of the service’s interface, will be captured by customer’s memory much longer;</li><li><em>Optimize the work of the team</em> — the design system will take over part of the operating issues that assigned to developers and designers;</li><li><em>Save time</em> — it will be much easier to assemble new pages: just pull out the prepared elements from the data library and construct them in a single puzzle;</li><li><em>Will provide media publicity</em> — the business community is keenly interested in fresh design system projects.</li></ul><p>Today, banks, online platforms, and service providers use design systems in our world. It is important for them that the user feels as comfortable as possible, using their products from any device. One more example of an interesting case of the Uber design system can be found <a href="https://brand.uber.com/guide">here.</a></p><blockquote>The design system increases employee confidence in the products of their company and positively affects the brand reputation. Its integration can be a good PR step and improve the company’s position in the digital services market.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OjMNOj7gUaerWeBSAeuRuw.jpeg" /></figure><h3><strong>Deciding between the design system and Ul-kit</strong></h3><p>But the question is many companies manage with a regular UI kit and feel quite good. Why do they need a design system?</p><p>To understand, we’ll first agree on the terms. UI kit is a set of interface elements for a website — buttons, tabs, arrows, sliders, etc. All visual components of the project are stored in the UI kit. And, if necessary, on their basis you can construct the whole website.</p><p>The design system is a broader concept, which includes both the <strong>philosophical part</strong> (brand values) and the <strong>applied one</strong> — guidelines, brand book, and UI kit. It’s a set of brand components with the maximum upgrade presented as one package. And lastly, UI kits are translated into code, which allows you to assemble new projects even faster.</p><h4><strong>It makes sense to create a design system, and not just a UI kit, if:</strong></h4><ul><li>The company has several related products that require systemic scaling;</li><li>The company got the necessity to optimize the work of development teams;</li><li>The brand doesn’t have a single visual language;</li><li>There is already a completed UI kit, but there is no single data library that could be used by both developers and designers.</li></ul><p>If we are talking about a startup, it is better to concentrate on key business processes — the development of the sales funnel, product, and desired service level. These actions will provide a profit in the short term.</p><p>Speaking about the design system, everything is a bit more complicated — they won’t bring money here and now. This is a <strong>long-term project</strong> that focused on the strategic development of your brand. Developing a good design system takes at least six months and requires specialists in the state who will devote almost all of their working time to it.</p><p>It will take at least one designer, who will draw the elements, components, templates, and the developer who will connect them to code. If the customer does not want to invest his money and time into this, you can completely get by with the regular UI kit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T65pPmHa8GkaBFyluklgJg.jpeg" /></figure><h4><strong>Before you start developing a design system, you need to complete several actions:</strong></h4><ol><li>Align and agree with the whole development team. This project will require the mobilization of all workforce. The easiest way is to motivating colleagues, explaining the design system will simplify their work: creating new projects will be easier and faster.</li><li>Define the criteria to be used to measure the effectiveness of the system. This may be increasing of customer loyalty or website conversion;</li><li>Be ready to <strong>maintain the relevance</strong> of the design system. It will take a lot of time until the final version has launched. During this time, the team may have new ideas, and the system should be able to ensure them. Only in this way, the system will be effective.</li></ol><h3><strong>Bringing the value of a design system to the product stakeholders</strong></h3><p>Creating a design system is obviously profitable for designers and developers. Because it simplifies their work. But all developers have faced one problem — how to convince all stakeholders or your product management of the advantages of implementing such a system?</p><ol><li><strong>Define the pain of your company for today</strong><br>As we learned above, not every company needs design systems. If you are an agency, offer them to customers who have a stable market position and a strong digital base. Small startups and companies could exist with the UI kit.</li><li><strong>Collect the feedback</strong><br>Contact with the product manager or customer support staff. These people will help you understand what problems a business faces every day. Think of the solution based on design system implementation and offer the arranged proposal to the management.</li><li><strong>Focus on the result</strong><br>Usually, the head is not aware of design systems. He just wants to see the result of your work. Therefore, it’s crucial to emphasize the outputs of the implementation of the system instead of focusing on the workflow. Those are optimization of the work of designers and developers and customer satisfaction, who would certainly appreciate the updated service.</li><li><strong>Show business benefits</strong><br>Visual design is a subjective thing, it is difficult to immediately evaluate its profit. You can come from another angle and evaluate the effectiveness of the system for the company itself. The design system automates the process of developing new products and simplifies the work of the team.</li></ol><blockquote>This allows you to reduce the huge amount of operating work and focus employees on creativity and strategy.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*48n55uA3EWh7A1MjSZ3ZIQ.jpeg" /><figcaption>Accessibility Scale. A peace of accessibility scale of <a href="https://eleks.com/">Eleks</a>’ Design System</figcaption></figure><p>A good design system will perfectly handle the task of optimizing the company staff — the necessity for a huge team of designers and developers will simply disappear. Tell your boss about this, and you will not meet the skepticism of your idea.</p><p><strong>Resources we found helpful:<br></strong><a href="http://atomicdesign.bradfrost.com/">Atomic Design</a> by Brad Frost<br><a href="https://www.smashingmagazine.com/2017/07/designing-perfect-date-time-picker/">Designing The Perfect Date And Time Picker</a> by Vitaly Friedman</p><p><em>Feel free to get in touch with me on </em><a href="https://www.facebook.com/pIotnikov/"><em>Facebook</em></a><em>, </em><a href="https://www.behance.net/d_plotnikov"><em>Behance</em></a><em>.</em></p><figure><a href="http://bit.ly/34kSkxu"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PpfitldOodpAtws_LCuLuA.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8bdf2e5976c9" width="1" height="1" alt=""><hr><p><a href="https://medium.muz.li/how-to-get-executive-buy-in-for-your-design-system-approach-8bdf2e5976c9">How to get executive buy-in for your design system approach</a> was originally published in <a href="https://medium.muz.li/">Muzli - Design Inspiration</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>