<?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 Smita Mohith K on Medium]]></title>
        <description><![CDATA[Stories by Smita Mohith K on Medium]]></description>
        <link>https://medium.com/@smitamohithkanakula?source=rss-12b73afdc5b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*GE5tg3jrrXW447NoD3FG_g.jpeg</url>
            <title>Stories by Smita Mohith K on Medium</title>
            <link>https://medium.com/@smitamohithkanakula?source=rss-12b73afdc5b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 03:01:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@smitamohithkanakula/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[UX is not required]]></title>
            <link>https://medium.com/@smitamohithkanakula/ux-is-not-required-2a0fc2a66ce9?source=rss-12b73afdc5b------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a0fc2a66ce9</guid>
            <dc:creator><![CDATA[Smita Mohith K]]></dc:creator>
            <pubDate>Wed, 29 Oct 2014 09:27:19 GMT</pubDate>
            <atom:updated>2014-10-29T09:27:19.296Z</atom:updated>
            <content:encoded><![CDATA[<h2>‘UX IS NOT REQUIRED’</h2><h4>Is it true in this information age?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/801/1*pqjPsEVuQw5utpy1PuZP-Q.jpeg" /></figure><h4>Sounds familiar?</h4><blockquote>I am sure every UX designer at some point of time has heard this coming it from PMs and higher ups. I have few examples where compromising on UX pays huge cost at the end of a project. People who make the in the early stages of a project, says the following -</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/758/1*ySVv2mdrGXCK1PA788EFRw.jpeg" /></figure><p>It is too late to realize a mistake. At this stage, majority of the development efforts are already put in and rolling out deliverables. This inappropriate decision now can have an impact on effort estimates leading to timelines not being met. Deliverables are already approved &amp; opening the discussion thread is painful and time consuming. PMs who co-ordinate projects focus on the outcome viz. developed product and ensuring that the timelines are met. Hence, they refrain from accepting major design changes that can obstruct the development cycles.</p><p>Why did all this happen? Did someone check Why UX was not a part of the project in the initial phases of design? And Why person responsible for UX is to be blamed for the lack of attributes that make the product a differentiator in the industry?</p><p>IMHO — to avoid such a situation, below pointers can be adopted in planning projects that involves design efforts.</p><h4>1. User Centric Approach –</h4><p>UX Designers are true advocates of the end users for the products. These are the people who are responsible for product success, as they embed the attributes into the user interface that enrich the experiential aspect of the product. Let them pave the way for the team by taking key decision along with Client.</p><h4>2. Shared Responsibility –</h4><p>Defining scope of the project and setting right expectations with the Client always leads to a happy &amp; continued relationship. This can be achieved by appropriate handshake between Design &amp; Development teams. Representatives from each team must participate in defining scope &amp; effort estimates to ensure feasibility &amp; accurate closure.</p><h4>3. UX in Long Run –</h4><p>UX Designer not only works towards creating tactical designs that enriches user experience but also ensures that those designs meet the Client’s expectations. Any concerns raised by the Client regarding UX must be directed to the UX Designer ensuring quick &amp; appropriate closure on open items retaining the integrity in designs.</p><h4>4. Creativity in Design –</h4><p>Imagine, you were asked to watch a movie &amp; listen only to the dialog and told not to pay any attention to songs or the story. I know, that it sounds weird… Design thinking involves a holistic approach, considering many aspects before filtering down to what is really needed. UX Designers bring value to the table, thinking beyond the scope so as to ideate on scenarios true to the end users of the product. Often, new ideas emerge from such thought process, that can make the product different from its competitors or even make the product a pioneer.</p><h4>5. Knowing the Known –</h4><p>Lastly, it is of utmost importance to understand the implications in <strong>not</strong> engaging a UX Designer in the project. In fact, introducing a UX Designer at inappropriate junctures does not really impact the UX of the product to a great extent. Approach needs to be well thought through and planned considering all the pro &amp; cons of having/not having a UX Designer involved.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a0fc2a66ce9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>