<?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 Prasoon Srivastava on Medium]]></title>
        <description><![CDATA[Stories by Prasoon Srivastava on Medium]]></description>
        <link>https://medium.com/@prasoonsri22?source=rss-9a5099dcd358------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*-yvr_06UsUK6os3K0YZqug.jpeg</url>
            <title>Stories by Prasoon Srivastava on Medium</title>
            <link>https://medium.com/@prasoonsri22?source=rss-9a5099dcd358------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 12:54:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@prasoonsri22/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[Working with Component Library in Design System]]></title>
            <link>https://medium.com/@prasoonsri22/working-with-component-library-in-design-system-f4945533e732?source=rss-9a5099dcd358------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4945533e732</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[component-libraries]]></category>
            <category><![CDATA[visual-design]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Prasoon Srivastava]]></dc:creator>
            <pubDate>Tue, 28 Mar 2023 10:50:10 GMT</pubDate>
            <atom:updated>2023-03-28T10:50:10.459Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JsnTzKlJHZP2L4gCyPZjwg.png" /></figure><p>Design systems have become a crucial aspect of modern design processes. With design systems, organizations can create a unified language for their products or services, maintain consistency, and streamline their design workflow. <strong>One of the key components of a design system is the component library</strong>. In this article, we’ll explore how organizations can effectively work with component libraries to ensure the success of their design system.</p><h3>What are component libraries?</h3><p><strong>Component libraries are collections of reusable design elements</strong> that are used to create a consistent look and feel across an organization’s products or services. Components can be anything from buttons and icons to more complex design elements like tables and forms. By using components, designers can create new designs quickly and efficiently while maintaining consistency across the entire system. The best example for resuable components are Disney.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*977vOBDjidMS-76ttgELmw.gif" /><figcaption>Disney Reuses Animation</figcaption></figure><p>Let us see how we can work with component libraries</p><p>Creating a component library is just the first step. The real challenge is maintaining and updating it. Here are some tips on how organizations can effectively work with component libraries.</p><ol><li><strong>Define naming conventions and standards</strong></li></ol><p>To ensure consistency, it’s crucial to establish naming conventions and standards for your component library. Naming conventions should be clear and intuitive so that designers can easily find the components they need. Standards should be established for design elements like typography, color palettes, and iconography to ensure a consistent look and feel across the entire system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*leV1gm2S-_vahfR63tQTCw.png" /><figcaption>Correct way of naming any component</figcaption></figure><p>2. <strong>Document the components</strong></p><p>Documentation is critical for any design system. By documenting components, designers can easily reference them and understand how they should be used. Documentation should include information such as component name, description, usage, and any specific guidelines or constraints.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/324/1*QvnOxCh6NlDIQrU9eORywA.png" /><figcaption>Naming &amp; Documentation of Components</figcaption></figure><p>3. <strong>Use version control</strong></p><p>As with any software development project, version control is critical for design systems. By using version control, organizations can track changes made to the component library over time and collaborate more effectively with other designers and stakeholders.</p><p>4. <strong>Test the components</strong></p><p>Before adding components to the library, they should be thoroughly tested to ensure they work as expected. Testing should include both functional and visual testing to ensure the components are usable and consistent with the design system.</p><p>5. <strong>Gather feedback</strong></p><p>Feedback is crucial for improving the design system and ensuring it meets the needs of designers and stakeholders. Organizations should regularly gather feedback from designers and stakeholders and use it to inform updates to the component library.</p><h3>Conclusion</h3><p>Working with component libraries is critical for the success of any design system. By establishing <strong>clear naming conventions </strong>and <strong>standards, documenting components, using version control, testing components</strong>, and <strong>gathering feedback,</strong> organizations can create and maintain a successful design system that is efficient, consistent, and easy to use.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4945533e732" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Empathizing with Parents]]></title>
            <link>https://medium.com/@prasoonsri22/empathizing-with-parents-6bcc636e575?source=rss-9a5099dcd358------2</link>
            <guid isPermaLink="false">https://medium.com/p/6bcc636e575</guid>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[empathy]]></category>
            <category><![CDATA[television]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Prasoon Srivastava]]></dc:creator>
            <pubDate>Fri, 16 Dec 2022 06:49:55 GMT</pubDate>
            <atom:updated>2022-12-16T06:49:55.006Z</atom:updated>
            <content:encoded><![CDATA[<p>Let me take you back to a time when there were no DTH services and navigating to channels was so easy as we had only DD national and Metro channel to watch. Technology is enhancing, but our parents are not used to these changes. During COVID times my organization <a href="https://medium.com/u/a51ea09bf031">Newgen Software</a> gave me a wonderful opportunity in terms of sufficient time to empathize with my parents by providing me work from home.</p><p><strong>Challenge</strong></p><p>While working I always notice that my mother faces difficulties in operating television; she always asks me to navigate different categories of channels and then select according to it. After the desired channel selection, she always says why this is so complex to handle. I took this statement as a challenge to sort this out for my mother.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T_05XkncMm7kDEYpQXeeyA.png" /></figure><p><strong>Observation &amp; Solutions</strong></p><p>While working on this challenge, I started observing the pattern for my mother while watching television.</p><ol><li>She is not too much tech friendly</li><li>Faces difficulties in remembering channel numbers</li><li>Too many buttons on remote sometimes confuses her</li></ol><p>My first solution was to write all the categories and list major channels under it and stick it to nearest wall.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qdY8HNFaJW3ZIHQKXqtZkA.png" /></figure><p>This has solved 60% of problem where now she doesn’t have to memorize the channel numbers, but wait, there is still some problem left to this challenge. She has to walk again and again to the wall and has to look for channel numbers to change it.</p><p>This triggered a problem of accessiblity which needs to be addressed. Once again I observed a pattern that there are only few channels which she repetitively changes for which she doesn’t need categorization. So I interviewed her about all the serials which she used to watch daily and came up with few channel list which will cover all her daily needs.</p><p><strong>Conclusion</strong></p><p>After all ideation, I came up with the final approach to solve this challenge for her. <strong>I noted down all the channels</strong> and <strong>made a list of those channels which she watches daily</strong> and <strong>pasted it behind the television remote</strong>. <strong>I also hid all unnecessary buttons on remote</strong> which is of no use to her. This solved both her problems and resulted in: ease of accessibility and recognizing than recall.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3mKq14ktxRbvqnVZP2a_ng.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wJVH5GuQGI0C6e2VzWNYTQ.png" /></figure><p>This whole process also helped me in explaining my mother what I do for my living 😝. I am a User Experience Designer 😎</p><p><em>Leave some claps if you liked this article.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6bcc636e575" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>