<?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 Setu Kathawate on Medium]]></title>
        <description><![CDATA[Stories by Setu Kathawate on Medium]]></description>
        <link>https://medium.com/@setumad?source=rss-4f6545ae1780------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*xzitlwqO2CFFJ0L-enK5iQ.jpeg</url>
            <title>Stories by Setu Kathawate on Medium</title>
            <link>https://medium.com/@setumad?source=rss-4f6545ae1780------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 22:15:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@setumad/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[Qualities of great leaders]]></title>
            <link>https://uxdesign.cc/qualities-of-great-leaders-479d10790792?source=rss-4f6545ae1780------2</link>
            <guid isPermaLink="false">https://medium.com/p/479d10790792</guid>
            <category><![CDATA[relationships]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[inspiration]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Setu Kathawate]]></dc:creator>
            <pubDate>Sun, 30 Jun 2019 03:23:33 GMT</pubDate>
            <atom:updated>2019-07-03T02:13:13.404Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HoOCF538ICIavlfK6EdoeQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@amyhirschi?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Amy Hirschi</a> on <a href="https://unsplash.com/search/photos/boss?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I’ve been fortunate to have worked with some great leaders. Their mentorship and guidance have been very instrumental in my growth both professionally and personally. Through my interactions with these people, I have observed certain qualities and behaviors that sets them apart from the others and make them the influential leaders that they are.</p><ul><li>They’re always peaceful, pensive and very relaxed. There is very little agitation or urgency in their demeanor.</li><li>They have an air of confidence and humility (and not overconfidence or arrogance) around them.</li><li>Their speech is calm, calculated, articulate and direct. There is little fluff and ambiguity.</li><li>They’re extremely good listeners. They patiently listen to what the other person is saying and take their time to process the information before responding. They do not appear to be in a hurry to speak their mind.</li><li>They’re good at asking ‘Why’s. They ask questions to understand and get to the bottom of an issue and not out of malice or to test the knowledge of another person.</li><li>They tend not to judge others and accept them the way they are before offering help to grow/improve where necessary.</li><li>They show genuine care and respect for everyone they interact and work with.</li><li>There’s a genuine desire and intent in them to help others grow and overcome issues in their professional/personal lives.</li><li>They seem to be very self-assured and comfortable in their skin.</li><li>They’re very good at saying ‘No’ to things that do not matter.</li><li>They’re very conscious, intentional and conservative about their time.</li><li>They lead their team by removing the blockers for people to do their job and succeed. They tend to show faith and confidence in their team to solve a problem, no matter how complex it is. They do not micromanage or do the job themselves.</li><li>They’re good at managing their ego and do not let it come in the way while having conversations with others.</li><li>They approach people with kindness and empathy.</li><li>They encourage and allow the space for their team to do experiments, make mistakes and learn from them.</li><li>They’re good at forgiving people without holding any negative opinions of feelings about them.</li><li>They’re open, direct and transparent in their communication.</li><li>They put others’ needs and success before their own.</li></ul><p>Have you observed any other qualities or behaviors in leaders that you are influenced by? Let me know in the comments.</p><p><em>Shoutout to </em><a href="https://www.linkedin.com/in/ACoAAADIYFgB1kolkUK0bVvc6FnPBvdo2tvJ_Xg/"><em>Cliff Sexton</em></a><em>, </em><a href="https://www.linkedin.com/in/ACoAAADQrQIBybMzbsVTywk7aN9vlWm9utRJZ3U/"><em>Francis (Bill) Hughey</em></a><em>, </em><a href="https://www.linkedin.com/in/ACoAAACuhjQB23eYT6HZVYhu1H9VGYUSTFbs1U4/"><em>Rick Johanson</em></a><em>, </em><a href="https://www.linkedin.com/in/ACoAAAH4zkoBw7MtBNZd0kRtMuBksf5SVkW0Jb0/"><em>J.B. Chaykowsky</em></a><em>, </em><a href="https://www.linkedin.com/in/ACoAAAC8_mkBlOi32SwcEbHdFm4zuztxAgNZV30/"><em>Dan Gamber</em></a><em>, </em><a href="https://www.linkedin.com/in/ACoAAAEbfAoB9Xu-TYvoNgzGrPXCAreJe4EFKVc/"><em>Patrick Aguilar</em></a><em>, </em><a href="https://www.linkedin.com/in/ACoAAAC9-7kBbPOGRmXm8-07YWGY4G7qGIaDqiQ/"><em>Vincent Baskerville</em></a><em>, </em><a href="https://www.linkedin.com/in/ACoAAAEqi-MBkKAeDQodkpTf3eHyEWN9oTGsaWk/"><em>Ha Phan</em></a><em>, </em><a href="https://www.linkedin.com/in/ACoAAABP-YcBA7V0VB4cmoIU9ku2tCjHGiEa490/"><em>Irish Malig</em></a><em>, </em><a href="https://www.linkedin.com/in/ACoAAAAZUe4Bc_tvuw66h6Q8pPhv_QHpZmSRE-o/"><em>Kate Wolf</em></a><em>, </em><a href="https://www.linkedin.com/in/ACoAAAp3ImYBW47yAFVyBmORFVxCpcLtpT2zsek/"><em>Joan Branham</em></a><em>, </em><a href="https://www.linkedin.com/in/ACoAAAAE84wBeLUgy9fIa5hp94rKXzqqC0RxxRU/"><em>Loki Muthu</em></a><em> who have been very helpful at various times in my journey.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=479d10790792" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/qualities-of-great-leaders-479d10790792">Qualities of great leaders</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beginner Mentality For UX Designers]]></title>
            <link>https://blog.prototypr.io/beginner-mentality-for-ux-designers-cd15e84ac1c0?source=rss-4f6545ae1780------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd15e84ac1c0</guid>
            <category><![CDATA[growth-mindset]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[beginner-mind]]></category>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[Setu Kathawate]]></dc:creator>
            <pubDate>Sat, 25 May 2019 09:13:07 GMT</pubDate>
            <atom:updated>2019-05-30T09:36:26.657Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RSEL-bAt10IBtILzP3-SeA.jpeg" /></figure><p>A friend who is trying to get into UX was asking me about some of the beginner mindset to become a UX Designer. Having gone through the beginner phase (I think because at times I still feel like a beginner), here are some of my learnings on how to develop and nurture the beginner mindset and get started in UX.</p><h3><strong>Find Something You Enjoy Doing</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*V0_JHaYnEGDvCHH60iQdhA.gif" /><figcaption>Do what you enjoy doing</figcaption></figure><p>This is probably the most important aspect of beginning something — It has to be enjoyable and fun for you. Do not pick something up just because a bunch of people have started talking about it in social media. Avoid getting distracted by the latest buzzwords. If you don’t enjoy doing the work or if it doesn’t bring you joy, it won’t last long.</p><p>A good place to start doing what you enjoy is by stopping doing things that you don’t. Now, I don’t recommend you cold-quit the job you currently have to pursue your passion. However, start by identifying activities that bring you joy, those that don’t and find ways to gradually do more of what makes you happy until you can start doing that full-time and make a living off of it.</p><p>This is particularly important because the work we do has a huge impact on our overall happiness and satisfaction. If you’re doing something that makes you happy and increases your energy, it doesn’t feel like work anymore and getting through hard days will become much easier.</p><h3>The Secret Ingredient For UX</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/244/1*APNQx_S3I-KPIkeLLIs_eA.gif" /></figure><p>I wish I learned this in the design school — There is no single UX/Design process to solve a problem. Every business problem is unique needs its own UX process. We cannot fit a problem into a prescribed process and expect to solve it efficiently. Understand the basics to get started and improvise as you go. Ideas and processes change very often depending on the nature of the problem and the learnings that come from them. Be willing to abandon ideas when you find something that’s not working and look for something else that works.</p><p>UX is a game of hypothesis — Frame a hypothesis, validate it through various methods, and pivot based on the outcome. With each iteration, the team moves from a point of low confidence to higher confidence in the problem. Don’t obsess over the little details early on.</p><h3>Accept Yourself</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*prm-NuMY9Ysf-legDmYqpw.gif" /></figure><p>With a desire for growth, we often try to change or ‘re-invent’ ourselves to become a different person. While it’s a good idea to become ‘better every day’, we could end up ignoring who we are today and everything we’ve achieved in the past. Growth and learning cannot happen by berating ourselves and distorting our reality. It has to begin with the acceptance of our strengths and weaknesses. By accepting the reality, we would be able to re-assess and change the expectations we set for ourselves. Nobody is good at everything, let alone being perfect. In fact, it’s perfectly OK to not chase perfection. Our strengths and weaknesses make each of us unique and this uniqueness is what makes good teams thrive.</p><p>Accept who you are, your strengths and more importantly, weaknesses. Give yourself enough space and time to grow and work on things that are important to you. Acknowledge your achievements and successes but do not rest on your laurels. Take confidence from them to learn new things and grow.</p><p>Avoid seeking change from a place of rejection. Rather seek growth from a place of curiosity and a desire for constructive learning.</p><h3>Be Curious</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*fu0pnUy7sBzAXaVxboBo5A.gif" /><figcaption>Be curious</figcaption></figure><p>One of the good things about being a UX designer is the constant opportunity to learn something new. Treat every situation as an opportunity to improve your own understanding of the process, people or product. If you are already familiar with something, treat that as an ‘assumption’ and talk to other people to ‘validate’ your assumptions and hypotheses.</p><p>Avoid going into a learning opportunity with a presupposition of what you want to hear. The more open-minded and curious you are, the more you can learn.</p><h3>Become Comfortable Saying “I don’t know”</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*2oaF6WInVK3X2xOeqMQTHg.gif" /></figure><p>For many of us, the environment we grow up in or work in does not encourage vulnerability or offer the freedom to say “I don’t know”. And when it does, our ego usually prevents us from being vulnerable in front of someone and admit that we don’t know something. This can prevent us from learning new things from other people.</p><p>Luckily, UX is a field where it’s not just ok to say ‘I don’t know’ but you’re encouraged to say so. As designers, often working in areas we have very little to no background knowledge in and the only way to learn and design the right solution is to admit that we don’t know and be open-minded to dig deeper and learn more. Practice the ‘5 Whys’ method to understand the first principles of any topic.</p><p>It’s better to feel stupid for a few minutes or days than to remain stupid forever.</p><h3>Become Comfortable With Making Mistakes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*IMrGsbZQCygGYMhRtqATlw.gif" /><figcaption>Make Moar Mistakes</figcaption></figure><p>We often don’t make as many mistakes as we should be doing out of the fear of failing. It feels safer to stay inside our comfort zone. The fear of failure prevents us from exploring and learning new things and as a result, we choose to do things that are easy, familiar and less risky. However, making mistakes and failing is the best way to learn and grow.</p><p>When you pick something new and the fear of failure creeps in, realize that nobody is judging you. And more importantly, do not judge yourself. If you’re learning a new design tool, do not start expecting Airbnb-like screens. Your first hundreds of designs will be terrible. But every single attempt will be slightly better than the previous one. Push through the initial period of mediocrity and once the magic of <a href="https://fourminutebooks.com/the-compound-effect-summary/">compound-effect</a> kicks in, you will start seeing the returns.</p><h3>Become Comfortable With Ambiguity</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*ny0Z7HXdyDC6J2yyQZDktg.gif" /><figcaption>All of us get lost</figcaption></figure><p>Facing an ambiguous situation with no clear answers can be scary and anxiety-inducing. However, in order to become better designers, we need to embrace the ambiguity and see that as an opportunity to learn something new. Chaos and confusion are quite common in product development. The next time you face such situations, do not avoid or react to it. Instead, pause for a moment and make a list of the questions that would shed more light on the situation. Identify all the unknowns and assumptions, find out who can help provide answers to those questions and reach out. More often than not, you will be able to find the answers you are looking for.</p><h3>Introspect</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/245/1*A1IW26RLAwOOEe8e_tvVcw.gif" /><figcaption>Look beneath the surface</figcaption></figure><p>Spend some time away from the distractions and introspect about the situations where you felt confident doing something and situations where you felt threatened, afraid or confused. The former are situations where you used your strengths and the latter are situations where your weaknesses came in your way of being successful in your effort. Have an honest conversation with yourself and make a list of your strengths and weaknesses. You can also try talking to someone who knows you well. Find out what they think you are good at or areas where you could improve.</p><p>Once you have a list you’re happy with, prioritize the list of weaknesses and make a list of action items that you can take to overcome the weakness. Start small and identify the ‘Minimum Viable Effort’ needed so that you do not overwhelm yourself. Changing habits and behaviors is a slow process and it takes time and constant effort. Go slow.</p><h3>Find Mentors</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*lesbtqT1iiCCjorRVzXVow.gif" /></figure><p>Having mentors to talk to and get advice from can have a huge impact early in the career. Speaking to people who have more experience than us helps us discover some of our internal biases, irrational assumptions and learn tactics and strategies to overcome those issues. Seek out people whose ideas resonate with you, someone who you think you can learn from and find out if they’re available to mentor you. If you don’t already have a mentor, there are a couple of things you can do to find mentors:</p><ul><li>Reach out to Senior Designers, Product Leaders or anyone else who you find inspiring. Set up 1:1s with them and if there’s a connection, you can develop a mentor-mentee relationship.</li><li>Leverage LinkedIn’s rich UX community of UX Designers and get connected with the people you admire and respect.</li><li>LinkedIn also has a mentoring feature on the website called ‘Career Advice’. Based on your preferences, you will be suggested people who can provide career advice. Use the tool to your advantage.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AaBFoQMXLS3hPOk_d_QAJA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xfB_hQkSK1-UOwSjGN2qIw.png" /><figcaption>Career Advice on LinkedIn</figcaption></figure><p>If there’s one thing I did differently in my UX career from my previous is having mentors to guide me. I regularly reach out to my mentors and they have helped me grow both personally and professionally. I feel extremely grateful and lucky to have met some very smart and more importantly kind people in my journey so far.</p><h3>Share Your Learnings</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*8KTgVrVkcRRwIFL3u8zfXw.gif" /><figcaption>Sharing is learning</figcaption></figure><p>Lastly, share your learnings and knowledge. One of the best advice I got from a mentor is: “If you want to get strong at your craft and grow, teach other people”. Teaching is a great way to solidify your understanding of a topic is to teach other people. By explaining other people, you will be forced to get to the basics and first principles of a given topic. The more people you teach, the better you become by the magic of repetition. It also helps build your confidence in that subject and public speaking which are valuable skills for anyone doing UX.</p><p>Teaching and helping others grow can be a rewarding experience. As you learn something new, find ways to share that knowledge with others so that the repetition doesn’t just help cement your own understanding but it also helps other people who are trying to learn and grow in the field.</p><p>Thanks for reading this article. I hope it was helpful. If you know of other techniques and strategies that you have used or come across to learn better, please share them in the comments. I’d love to learn more.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff51076%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Ff51076%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Ff51076%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href">https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd15e84ac1c0" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/beginner-mentality-for-ux-designers-cd15e84ac1c0">Beginner Mentality For UX Designers</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Design Process]]></title>
            <link>https://medium.com/@setumad/my-design-process-ad36bc4d8a83?source=rss-4f6545ae1780------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad36bc4d8a83</guid>
            <category><![CDATA[problem-solving]]></category>
            <category><![CDATA[ux-process]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Setu Kathawate]]></dc:creator>
            <pubDate>Mon, 13 Aug 2018 02:48:49 GMT</pubDate>
            <atom:updated>2018-08-15T01:38:23.053Z</atom:updated>
            <content:encoded><![CDATA[<h3>An Evolution</h3><p>My design process has been constantly evolving ever since I started working on my start-up in 2015. When I first started, my design lexicon was limited to designing website screens on photoshop. In my mind, I was designing for a desktop, but I had no idea if what I was designing translated well to a desktop (It didn’t). Over the course of 3 years, I traveled half-way across the world, worked with some incredibly smart people, at some great organizations and as a consequence, my design process has undergone a world of change.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LFkx_R1KLIN2mQ7ZiH5gYw.png" /><figcaption>One of the first screens I had designed for Eventosaur in March 2015. I cringe a bit when I see it now, but I’m also proud of it.</figcaption></figure><h3>Thinking Beyond The Design Tools</h3><p>As I worked with different teams, on a multitude of problems, I learned that Design is a lot more than just pushing pixels on my favorite design tool. It was a structured process to solve problems in the world and a way to reduce risks while building products. It’s a tool to empathize with people, understand problems and identify the right problem to solve within the constraints of time, technology and budget. I learned that the UX process is not a template for the sake of elongating a portfolio page, rather it’s a Swiss knife to bridge the knowledge gaps between teams, strengthen relationships, improve collaboration, make sense of ambiguity and increase cohesion within diverse teams that are solving complex problems. It took me a while and a lot of mistakes to change how I think and look at design. Once I moved past my honeymoon phase of pretty UI and prototype design, I started to think about the larger context and implications of design. I began asking more Whys. Why does design matter? Why does the design process matter? The more I asked, the more I realized how much I do not know. It was uncomfortable at first, but it was liberating once I made peace with not having answers to everything.</p><p>Design is not an activity to satisfy our own ego. It’s about creating solutions for people we may never meet and help them achieve their goals with the least amount of friction. Addition of value is not necessarily achieved by adding features or UI elements. If taking away features off of a product can make it easier for a person to finish the task, that’s good design.</p><p>Why is all of this important you ask? Building software for people we don’t know is an expensive business and the risks involved are high. One of the best ways to reduce the risks is by getting a better understanding of the end-users, the problem to be solved and having a shared understanding of all the information within the product team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aayyXoBmxKsRq_doo0NJSQ.png" /></figure><h3>The Process</h3><p>Every design problem and project is unique and the methods I use to address and solve the problems can vary slightly depending on the size of the problem, project timeline etc. Nonetheless, I do follow a structured high-level process of approaching and solving problems. Here is a brief overview of some of the steps I would take and the people I would collaborate with when working on design problems.</p><p><strong>Kickoff</strong></p><p>The purpose of a Kick off is to understand the high-level goals and requirements of a project. This meeting includes representation from the business stakeholders, clients, development team and the UX team. In this meeting we identify the problem, our assumptions, goals and risks about the problem at hand. This process is important so that as a team we acknowledge our assumptions — what we know, what we don’t ; the risks involved in the project — what can go wrong and what we can do about it ; the goals of the users, business and the product team. One of the main outputs from this meeting is an ‘Hypothesis’ that works like an anchor and a frame of reference for the rest of the following research process.</p><p><strong>Research</strong></p><p>Building products based on assumptions is like driving on a highway blindfolded. It’s definitely possible to drive but we may not be able to travel too far. The goal of user research is to validate or invalidate our assumptions and hypothesis. Through various research methods like user interviews, contextual inquiry, surveys, role-playing, user-journey mapping etc. I learn more about the users, their behaviors and mental-models, their fears, desires, needs and goals. Once the data is collected, I synthesize the data with the team to identify themes and trends in what we learned from the users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-14Kq8fb2-hyQAHekh9J1Q.jpeg" /><figcaption>Synthesis to make sense of large amounts of user research data</figcaption></figure><p><strong>Alignment</strong></p><p>This is another meeting with the larger team that was involved in the kick-off. The purpose of this meeting is to share the research findings with the team and validate if our assumptions and hypothesis were right. If the research suggestes otherwise, this is an opportunity to course-correct and make adjustments to the problem we’re solving. With the understanding of users and their needs, this meeting helps the team identify the user personas and the problems that are worth solving and those that aren’t. Through various prioritization exercises like stack ranking and 2x2 matrix ranking, the top priorities and the scope of the MVP are identified.</p><p><strong>Ideation</strong></p><p>Once I have a clear understanding of the problem and the scope, I move to the ideation process. Through design studios and whiteboarding sessions I work with the team to explore a wide breadth of ideas to solve the identified problems for the respective personas. After we have a large set of ideas, the team is asked to rank the top ideas that are seem functional and feasible and the process is repeated. Through multiple iterations, we start getting closer to a skeleton of the solution. I would then use these sketches to create digital wireframes to get a rough idea of hierarchy of information, general layout and structure of the product. With this, I would also create a low-fidelity prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vLC_3vv8ExnuXS-U8wVV4w.jpeg" /><figcaption>Whiteboarding exercises help in quickly exploring ideas without getting attached</figcaption></figure><p><strong>Testing and Iteration</strong></p><p>The next step of the process is to validate our idea. I’d test the usability of the prototype by putting it in front of users and asking them to complete few tasks they would normally have to do to achieve their goal. Through these usability studies, we would discover if what we believed was the solution is actually working as intended for the users we are trying to build the product for. This is an opportunity to identify what’s working for the users, what’s not and what can be improved. Through iterations the rough edges are polished and the team has a good understanding of what the solution is and what the user needs to achieve their goal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HaOyuzDIP4sSqVnddd5hEg.png" /><figcaption>Wireframes for the Eventosaur Partner App</figcaption></figure><p><strong>Visual Design and Mockups</strong></p><p>In this step I use various interaction design and usability principles to create high-fidelity mockups that are usable, meaningful and aethetically pleasant. At this step I would either create a design system or use an existing design system to create mockups resemble the final product. This is where I would create pixel perfect designs and design specs that make it easy for the developers building the product to get a clear understanding of how the interactions work and how the product should look. I use my knowledge of HTML/CSS and programming concepts to translate the design language to code, understand constraints if any and find workarounds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kl4y6V4XOcX8AP6VHf3VSw.png" /></figure><p><strong>Collaboration</strong></p><p>The process I explained above is very involved and takes a lot of time. As a designer, I cannot do all of this by myself. I rely upon the team and other people involved in the project for information and support throughout the project. Solving complex problems ranging from healthcare to supply chain, I am usually never the expert in the subject. Through collaboration, I learn more about the process from people who have better understanding in the subject and use my research and design skills to design products that solve problems for the business and the users.</p><p><strong>Why I believe in the process</strong></p><p>My journey into design hasn’t been easy, especially having to start and survive in a new country and having to live away from my family. But I never regretted making the choice of becoming a designer. When life outside got stressful because of separation, strange visa and immigration policies, I found solace and refuge in design. Solving design problems negated the stress and even helped me solve my personal problems as a designer. I don’t see Design Thinking as a process or tool restricted to solve design problems only. It’s a much broader tool to improve how we think and approach all problems.</p><p>Professionally, I love this Design Thinking because it’s a very efficient process for taking a team from chaos to clarity. I have seen people go from ‘What the hell are we doing??’ at the beginning of a project to “This is amazing! High-fives!” in less than a month of doing Research and Design to build software. And that’s a satisfying feeling to see people feeling more secure and confident about the problems they’re trying to solve. This is a process I have learned through my experience of designing various products and working with various diverse teams and organizations. Design and problem-solving is a vast ocean of knowledge and I am barely scratching the surface. There is still plenty of things out there for me to learn and that’s what I love about being a designer. There’s always something new to learn each day, there are so many amazing people I get to collaborate with and learn from. More than anything, I get the greatest satisfaction when I use my knowledge to design solutions that make someone’s life better.</p><blockquote>“Design isn’t about the quality ideas but quality thinking.”</blockquote><p>You can learn more about the projects I have worked on in my portfolio: www.setumadhava.com</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad36bc4d8a83" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[16 tips for better user interviews]]></title>
            <link>https://uxdesign.cc/tips-for-better-user-interviews-c06d5ee0f96f?source=rss-4f6545ae1780------2</link>
            <guid isPermaLink="false">https://medium.com/p/c06d5ee0f96f</guid>
            <category><![CDATA[user-interviews]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[research-methods]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Setu Kathawate]]></dc:creator>
            <pubDate>Fri, 27 Jul 2018 04:52:31 GMT</pubDate>
            <atom:updated>2018-08-01T12:05:25.143Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rvCXltfo303ejZUemaczPw.jpeg" /><figcaption>Image credit: Nik MacMillan</figcaption></figure><p>User interviews are one of the most common and accessible forms of user research methods. Interviews, when done right, reveal fascinating insights about people’s behavior, their motivations, fears, needs and desires. However, it takes a lot of careful planning and execution to ensure the information we get are consistent and remain ‘pure’. There are many things that can go wrong while doing user interviews. Here are some of the things that can be of help to avoid the errors that can otherwise corrupt or compromise the research data.</p><h4>1. Talk to the right people</h4><p>The kind of data we get depends on the kinds of people we interview. A business class flyer might offer a perspective that’s very different from an economy flyer. So if we’re designing for the economy experience, it would be a bad idea to interview a person who flies business class. Know who your users are and interview only those people that you want to solve the problem for.</p><h4>2. Involve stakeholders and the product team</h4><p>As much as possible, try to include members from the business and the product team when doing interviews and have them observe or better, take notes. Building products is a team effort and everyone involved in the process should be aware of who their users are, their pain-points, needs and motivations to make sure the team is solving the right problem. Also, having a diverse participation provides an opportunity to understand the problem from different perspectives.</p><h4>3. Well communicated schedule and logistics</h4><p>If you’re not the one scheduling the interviews, make sure you communicate the schedule (when and where the interviews should happen), duration of the interviews, the user group and the number of participants needed for the interviews with the person in charge of planning very clearly before the study. Also, conducting user interviews can be tiring. Be sure to provide sufficient buffer between interviews so that you don’t end up getting drained by the third or forth successive interview which compromise the questions you ask or the note taker’s efficiency/enthusiasm to take notes.</p><h4>4. Number of interviews</h4><p>When it comes to user interviews, more isn’t always better. A good rule of thumb is — talking to 5–7 people will uncover 80% of the information. Anything more than that, we start hear repeated information which doesn’t add a lot of value.</p><h4>5. Don’t prepare the script &amp; question alone</h4><p>Work with the partners when building the script and questions to be asked. Especially when we, as a researchers or designers, aren’t the subject matter expert in the product space you’re interviewing at. Working with partners helps us understand what area of the problem to focus on, knowing what answers to possibly expect to hear and get a general context of what users might say. This planning should happen after the kick-off meetings where the assumptions, goals and hypothesis are generated.</p><h4>6. Capturing consistent data</h4><p>One of the goals of the interview is to ensure the data captured remains consistent so that when synthesizing we can see patterns and trends emerge. This can be done by making sure we ask all the questions to every participant. Avoid introducing new questions half way through a study, even if it seems interesting. Having a certain insight from a single person when the other participants did not get a chance to share their thoughts on the topic can create ambiguities during synthesis.</p><h4>7. Be curious</h4><p>Even if you’re very certain about the answer to a question, ask the question anyway — It’s not about what we know, it’s about trying to understand what the participant has to say about the question. We need to fight against our biases, assumptions and instincts and remain curious. This comes by practice. Also, don’t assume participants wouldn’t know the answer to a question and skip a question. Ask anyway and see what they have to say about it. If you start hearing useless information, you can move on to the next question. (Unless you’re constrained by time).</p><h4>8. Be a good listener</h4><p>Listening carefully helps us pick up what users are saying and dig deeper to learn more about interesting behavior and insights. What people usually say isn’t always what they actually do. It takes a bit of probing to know the whys behind what they’re saying. The better we listen, the better data we can gather. Attentive listening is also important because people take their time out to talk to us and it’s just considerate to give them our full attention and make them feel they’re being heard.</p><h4>9. Ask more ‘Why’s</h4><p>People are not always great at explaining the whys behind what they do and it’s our job to help them articulate their motivations or reasons behind their goals, actions. Listen carefully and whenever necessary, ask the participants to explain why they say/think something the way they did. It helps us avoid making assumptions about users’ behaviors.</p><h4>10. Avoid leading questions</h4><p>Avoid asking questions that make the participant tell you what you want to hear. For example, instead of asking “Do you agree at using feature X to view the operational efficiency data is a pain?”, which almost always gets a ‘yes’ as an answer, it gives a better understanding of their thinking when we break it down and ask “Can you tell me about a time you used feature X? What did you use it for? How did you feel? Why did you feel that way?”. We must always be aware of what questions we ask and how we influence the users’ responses. Biased information can be very misleading when synthesizing the research data and this can result in incorrect product decisions. Better questions yield better insights.</p><h4>11. Repeat questions tactfully</h4><p>It’s ok to repeat certain critical questions in a couple of different ways even if some of the participants might feel a bit annoyed by it. Knowing if they stay consistent with what they say helps reinforce the data we gather. Or perhaps asking questions in different ways helps people think differently about a problem and gives us more insights. In my experience, I have rarely seen people getting annoyed and they are always happy to answer the questions even if they have to repeat what they previously said.</p><h4>12. Diligent note-taking</h4><p>Create a note-taking template that provides enough space for the note-takers to take notes for each question. Ask your note takers to take as much notes as possible. It’s also a good practice to record all interviews so that you can revisit them later in case there is any doubt or ambiguity while synthesizing. <strong>ALWAYS</strong> make sure you take the users’ permission before recording them.</p><p>Pro tip: Taking notes on stickies during the interview makes it easier for synthesis.</p><h4>13. Test your script before the study</h4><p>Once the script and questions are prepared, have them reviewed by other researchers, designers and business partners in the team to make sure there are no leading questions and the questions are designed to validate or invalidate the assumptions and hypothesis.</p><h4>14. Test all tech before the study</h4><p>Be present in the room at least 30 minutes before a study to make sure all the necessary tech (audio/video recorders, screen sharing/recording software, phone lines etc) are all working. I once used Quicktime screen capture to record a set of remote usability studies. After all the studies were done, I opened them to check if I had got all the data. To my horror, the software had recorded only the screen and not the audio because I have to separately select the audio recording option. Do a dry run of all the tech you’re planning to use before the research study to make sure they’re working as expected.</p><h4>15. Be mindful of the time</h4><p>In an ideal world, we would have all the time in the world to dig deep and ask participants to explain the whys behind everything they say. But seldom we have such luxury in reality. Usually, time goes very fast during interviews and as an interviewer, it’s important to be mindful of the time. A good way to do this is by prioritizing the questions before the study. Make a list of critical questions that you must get answers to and a list of good to have questions that can be skipped. Don’t spend too much time digging into one question if it risks missing out on other important questions.</p><h4>16. Cut people, politely</h4><p>Most people generally do not get a chance to talk about their pains and concerns. When they get a chance, some people tend to use these interviews as their therapy sessions and pour out all their needs and concerns. As an interviewer it’s your job to ensure the interview doesn’t spin out of control and spend all the time talking about an interesting incident the participant experienced. When such digressions occur, interrupt politely and say ‘this is really interesting. Let’s return to this after the next set of questions’ and move on.</p><p>There are many more nuances to successful interviewing and data collection. However, in the interest of time and attention, I will stop here. I hope this was helpful. If you found this article interesting and would like me to write about anything else related to UX, please let me know in the comments.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c06d5ee0f96f" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/tips-for-better-user-interviews-c06d5ee0f96f">16 tips for better user interviews</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Exploring alternative Lyft app experience]]></title>
            <link>https://medium.com/@setumad/exploring-alternative-lyft-homepage-experience-2a840fd4a7fd?source=rss-4f6545ae1780------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a840fd4a7fd</guid>
            <category><![CDATA[redesign]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-exercise]]></category>
            <category><![CDATA[lyft]]></category>
            <dc:creator><![CDATA[Setu Kathawate]]></dc:creator>
            <pubDate>Thu, 26 Oct 2017 00:14:16 GMT</pubDate>
            <atom:updated>2017-10-26T07:30:21.750Z</atom:updated>
            <content:encoded><![CDATA[<p>I love how Lyft has simplified my daily commute and changed my intra-city travel behavior. Last week while I requested for a ride and waited for the car to show up, my designer instinct kicked in and I started wondering how the app was designed the way it was designed and what other solutions, flows or patterns could the design team have explored before settling on what we see right now. This made me curious and I spent a rainy Seattle weekend exploring alternative ways of interacting with the app.</p><p>Before I begin, we must know that there is a very good chance that the design team would have considered these explorations and might not have implemented because of various UX/business reasons which is not publicly available.</p><p>Ideally a project like this would be informed by data from the research and usability studies, usage analytics and user feedback. I showed some of my early sketches and wireframes to my colleagues to get a general idea before working on the app over the weekend. Since this exercise isn’t affecting any users, I went ahead with the assumptions.</p><h3><strong>Current Homepage Experience</strong></h3><p>When the app is opened, before requesting for a ride, we see the screen shown below. The car selection modal is open by default. The modal, along with the address bar and the primary CTA occupy 48% of the map space.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*MzoQ9A5-Z55E_PZqmTsRIA.png" /><figcaption>48% of the map space covered</figcaption></figure><p>When the modal is closed, it reveals a significant portion of the map with only 18% of the map being covered in the bottom half. However, the car information (i.e the number of seats and duration) that is in the modal are no longer visible when it is collapsed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*om74xwxoyI_vV_q-Y9KPeQ.png" /><figcaption>18% of the map space covered</figcaption></figure><p><strong>Research</strong></p><p>I ran a short informal interview with my colleagues at work to get a sense of how they were using the app and what they thought of the existing layout. What I learned was:</p><ul><li>Having a map based interface, it’s important for a users to see their location on the map.</li><li>Users do not frequently change the type of car.</li></ul><h3>Alternative Homepage Design</h3><p>With some rough sketches, I came up with a few early ideas. I put the wireframes in front of my colleagues and observed them using it. People mentioned that they were comfortable with the existing interface for the most part, except that they said they wished to see their location clearly on the map.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q8QJyGL6cQzPax1vJeOwdw.png" /></figure><p>Based on these findings, I came up with a design goal:</p><p><strong>Allow users to select a car type without reducing the map space on the screen.</strong></p><p>By moving the car selection out of the address field into it’s own separate bar we get an additional 22% of the map screen space. The wider car-type selector accommodates car-related information &amp; selecting other car types without having to open the modal. This design change provides 3 benefits while taking up only 8% of additional screen space.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/964/1*RfqGNcfqG5goH3Z7E8mHrg.png" /></figure><p>Users can click on the car and it opens the modal as it does in the current app. The modal has been made larger to keep it’s size consistent with the bar it expands from.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/817/1*z7V1zv2HfPCLk2iAVvwuJA.png" /><figcaption>Different car types can be selected</figcaption></figure><p><strong>Hypothesis: </strong>By keeping the modal collapsed by default, a user gets to see a larger map upon opening the app. This avoids having a user’s location hidden behind the modal if they happen to be situated in such a position when the app is opened.</p><p>The modal has two buttons at the bottom — a collapse button &amp; a ‘My location’ button. The location button functions as a substitute to the default ‘My location’ button which gets hidden when the modal is open.</p><p>The ‘Users’ location’ button is kept within the car-selection modal to maintains the consistency of the button position. It also affords easier recognition and stays consistent with users’ expectations since the button exists in the same position in the current app, when the modal is open.</p><h3>Risks</h3><p>The new design now occupies slightly higher percentage of map space when the car-type modal is collapsed — 26% as compared to 18% in the current design. It also occupies more space when the modal is open.</p><p>Keeping the ‘My location’ button within the car selection modal might introduce confusion in a user’s expectation of what that button might do in the given context. Alternative position for the button was explored as highlighted below, but its location is ergonomically inconvenient and users with tall phones might find it hard for a single-handed operation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*mn1SdxQsqPKAKkEF1H0pvQ.png" /><figcaption>Hard to reach ‘My Location’</figcaption></figure><h3><strong>Other Designs Explored</strong></h3><ol><li>The concept below explores positioning the CTA button along with the address bar. The car selection modal sits below this group making it more accessible for a single-handed use. This increases the map space usage to 82% along with the swipeable car-type selector.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*SNi8tDBOCgX3NaMJqtGVtA.png" /><figcaption>Reduces map space encroachment, and includes the swipe-able car selection pattern</figcaption></figure><p>However, this pattern doesn’t perform well when there is a longer text in the CTA button as seen below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/367/1*OwTQGGkpfKPsWbGA07EaIw.png" /><figcaption>Set Dest…Oops</figcaption></figure><p>2. This concept combines the three functions, i.e selecting car-type, address bar and ’Set Pickup’ CTA, into a single unit. The CTA button label is replaced by an arrow which takes a user to the next step. This pattern has the best use of map space, however, without a label, it would be hard for a user to know what this button does. Also the destination page was beyond the scope for this project and I did not explore the next steps for this version.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*t0l1q_leo9E4vuCeSQps4Q.png" /><figcaption>One bar to rule ’em all!</figcaption></figure><h3>Profile Page</h3><p>The current app has a minimal user profile page with most of the app functions being present in the drawer menu. Also, clicking on the avatar icon in the homepage opens the navigation drawer which is traditionally done using a hamburger icon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/877/1*HQnbf5ZdBYoxGCAb7i7qqA.png" /></figure><h3>Alternative Profile Page Design</h3><p><strong>Design Goal: Design a profile page that contains all the necessary functions &amp; information a user needs.</strong></p><p>I created a unified experience which contains a user’s profile and also the important menu items in the same page. I designed two versions of the profile page with minor changes in the content, button positions &amp; visual design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/669/1*KcD5URNQ88x3gSDKm00d7g.png" /><figcaption>Alternative profile page design</figcaption></figure><p><strong>Adding an alias</strong></p><p><strong>Hypothesis: </strong>Drivers usually find it hard to pronounce names that are long and culturally different. A user’s name is taken from his/her Facebook profile and currently the name cannot be changed. Providing a way to add an alias allows a user to set the name they prefer to be called or one that’s easier to pronounce.</p><p>The ‘Add alias’ link affords a user to click on it and set an alias. The modal dialog was chosen since there is only one action to be taken.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xaHPwfNMOH6I9UTiFKXsLw.png" /><figcaption>Adding an alias makes it easy for drivers to say hard names (like the author’s name)</figcaption></figure><p>Alternatively, this action can also be completed in the edit profile page.</p><p>Running an A/B test &amp; studying the use frequency of the alias option would confirm which pattern works best for the users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WG5VYC_cVGKezx-qF0a2uA.png" /><figcaption>Adding alias in the settings page</figcaption></figure><p><strong>Profile Page Version 2</strong></p><p>Exploring an alternative visual, content &amp; layout design<strong>.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/657/1*VQ8hmPh2yLzGvaFUnShkSw.png" /></figure><h3><strong>What I would do if I had more time/resources?</strong></h3><p>In a work setting, the next thing I would do is to get some peer feedback on the designs to understand their perspectives &amp; consider any ideas that they might have.</p><p>After that, the next step would be to test the hypothesis with real users. This is done by building a functional prototype using tools like Framer or Invision and creating a usability study plan that describes the goal of the study, user tasks, success metrics, interview questions &amp; participant profiles. Running the study with 6–8 users usually uncovers 80% of the usability issues.</p><p>The success or failure of the design can be measured by analyzing quantitive findings like time on task, success rate, SUS scores etc and qualitative findings like interviews, user quotes and by observing non-verbal feedback. Based on the feedback and study findings I would iterate on the designs that didn’t work for users and run more tests until all the issues are satisfactorily resolved.</p><p>The final step would be to create high-fidelity mock-ups and redline the designs using tools like Zeplin before sending them to the dev team for turning the designs into code.</p><p>While this is a general process, every design project is unique and the testing &amp; iteration process will vary depending on the user goals, business goals &amp; development schedule.</p><h3><strong>You made it!</strong></h3><p>If you made it till here, you’re awesome! I’d love to hear your thoughts and feedback on this exercise. Thank you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a840fd4a7fd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing Humble Products]]></title>
            <link>https://medium.com/@setumad/humble-product-design-ec4b80ecece?source=rss-4f6545ae1780------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec4b80ecece</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Setu Kathawate]]></dc:creator>
            <pubDate>Fri, 20 Jan 2017 23:27:22 GMT</pubDate>
            <atom:updated>2017-01-21T00:40:11.552Z</atom:updated>
            <content:encoded><![CDATA[<p>As designers we spend an incredible amount of time thinking about how we can create an amazing interaction or the most beautiful interface for our application. At least I did. But my whole understanding of product design changed yesterday when I read something in Alan Cooper’s ‘About Face’.</p><blockquote>“… the ultimate user interface can often be no interface.”</blockquote><p>At first it seemed like a simple quote, but as I paused and thought about it, it was like (apologize the cliché) getting hit by a speeding train of realization. This realization was substantial.</p><p>Let’s think about this with a common scenario. You’re traveling in a public bus trying to reach your office. The bus stops at multiple bus stops along the journey to pick other people up. But as a passenger, do you enjoy the fact that bus stops so frequently on the way? How many times have you wished that all the stops were empty or nobody had to get down in between and the bus just took you straight to your destination, non-stop? I get this feeling almost every-time I travel by bus. And this is perhaps one of the reasons why we hail taxis. We reach our destination fast because a taxi (with all it’s spacious comforts of-course) doesn’t stop anywhere enroute to destination.</p><p>Our experience with products is something similar. We get annoyed when a product regularly interrupts us while we’re using it. And we are pleasantly surprised when we get a task done without realizing that we used some product. This is what differentiates a successful product from one that annoys us every-time we use it. What makes a product successful is how it is designed. This is the basis of my realization and what I would call ‘humble-product design’.</p><p>Every user has a goal when they start using a product. A person wants to look at the pictures of other people. He wants to find that awesome restaurant that serves his favorite food. He wants to send a message to his friends or family who is on the other side of the planet and hear back from them. To get to their goals, people use apps like Instagram, Yelp or WhatsApp. On a regular day, at no point people would open an app to look at the app itself or to appreciate how beautiful the colours are or how readable the typography is. People use the app to get their job done and once done, they close and get along with their lives. Would you ever open Uber’s app if you didn’t have to travel anywhere? A successful design is like a taxi ride. It lets users achieve their goals without getting in their way. This is what makes a product ‘invisible’.</p><p><strong><em>“… the ultimate user interface can often be no interface”</em></strong>. A great product is one that a user wouldn’t notice during the journey of their goal. For the user, it does not matter what app or website or product they use as long as their work gets done with the least amount of friction and cognitive overload.</p><p>When a product starts to draw attention towards itself, it builds friction. A classic example is the latest MacBook’s Touchbar. I don’t mean to say it’s a bad product. It’s a great piece of innovation and there have been some great minds and effort put behind it. But as a product, it explicitly draws its user’s attention. While working, a user’s attention is on the main screen, on the task he’s doing and not on the device itself (except when the device is brand new). With the Touchbar however, a user has to constantly take their attention away from the main screen and look at its tiny screen and get back to their task on the bigger screen. This breaks the continuity in their task. They’re repeatedly made aware of the secondary display’s existence and the need to look at it when performing the Touchbar based tasks. A product, seeking attention. (With internalization, we get used to these interactions just like we stop caring about the bus stopping at bus-stops, but habit cannot be considered a substitute for creating satisfactory experiences)</p><p>This fact means a lot for us designers and it’s quite humbling. We spend a great deal of time trying to come up with really cool interaction patterns and spend an incredible amount of time getting to the best combination of colours for our product. But for a user none of that really matters if the product can’t successfully get them to their goals. I’m not saying creating patterns or getting that beautiful colour palette is not important. People love apps and websites which look great, but the ones loved most are the ones that also ‘work’ great. This is what makes a product humble. One that stands out of a person’s way and helps them get to their goal fastest. One that doesn’t seek attention for itself but lets people focus on their goals.</p><p>In turn, this is also what makes a designer humble. When we design a product or interface keeping its user’s goals in mind, the need to create something shiny and impressive falls away. It provides a lot more clarity when deciding between different design patterns. The one that works best is not the interaction or feature that looks the coolest, but the one that takes a person to his goal with least friction.</p><p>This idea is not rocket science. In fact it’s one of the most commonly heard lessons about product design — “Focus on users”. But in retrospect, this is one of the hardest skills for a designer to master. As human beings we all crave attention and validation. We go to great lengths to do something impressive and collect people’s approval. That’s how we get our dopamine hit and feel good when we get 100 likes on our profile picture. For a designer though, this a curse. When we try to build something unique, we think of creating designs that we can impress our users with. Something that can grab people’s attention and make them go ‘Ooh this is sexy!’. But we must remember that when we use a product as a user, we do so more to get some task done &amp; less to appreciate the creative beauty of its design. (Apologize the cliché again) A product should always be means to an end but never the end itself. It should be as invisible and behind the scene as it can possibly be. And to design such a product, we should lose the desire to garner any attention that we intend to with our designs. This takes great amount of effort to master and this is what makes great products great.</p><p>You may ask, so what makes a product attractive, if it’s made so invisible? That’s where the micro-interactions, colours and animations kick in. These secondary components of a product supplement the main goal and enhance a user’s experience. A subtle animation when switching between the screens is a great touch but it lasts only as long as the transition is complete. People enjoy the animation for a small moment before their focus gets back on their goal. A user appreciates a good choice of typeface and line spacing for only so long before they get immersed in the content they’re reading. Or maybe they don’t even notice the typography because it’s letting them dive straight into the content. These small moments of delight act as a catalyst to enhance their overall experience, but by themselves cannot help the user complete his goals.</p><p>This was a humbling realization for me. It’s embarrassing to admit, but I would always give a lot of attention to designing products and interactions that would make a user appreciate my skill. But as I thought more about what do people really enjoy when using the products, it’s less about design and more about what they’re interested in getting done. As designers the sooner we learn to relinquish attention, the sooner we can ship successful products. This was a great lesson for me and going forward, I hope the products I design go as unnoticed as possible.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec4b80ecece" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why New Year makes no sense]]></title>
            <link>https://medium.com/@setumad/why-new-year-makes-no-sense-d57172c118ef?source=rss-4f6545ae1780------2</link>
            <guid isPermaLink="false">https://medium.com/p/d57172c118ef</guid>
            <category><![CDATA[new-years-resolutions]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Setu Kathawate]]></dc:creator>
            <pubDate>Sat, 31 Dec 2016 08:15:52 GMT</pubDate>
            <atom:updated>2016-12-31T09:41:53.291Z</atom:updated>
            <content:encoded><![CDATA[<p>I am going to say something very controversial. You’re free to agree or disagree with me. These are my personal thoughts.</p><p>While I was working on some interesting ideas this evening, I realized something . It’s New year’s eve and I’m sitting in my room, working away and it’s surprisingly making me very happy. For a while I was confused. Why was I happy when I am working while I should be partying or spending time with people talking about how the year went? Have I become so lonely? Maybe I have, but that should have me sad. It didn’t. So there has to be some other reason. I started getting curious about this weird sense of comfort I was feeling on New year’s eve.</p><p>I turned off my phone, lights and any other possible distraction except the gentle music of flute in the background and started thinking more about this situation. The thinking led me to a very strange realization. Why should I be celebrating the new year in the first place?</p><p>Let’s look at it scientifically. What’s a ‘year’? It’s a concept of date and time, that we have created. In the nature, it is the time taken by the Earth to go around the Sun. And this, the earth has been doing for the last 3.6b years of its existence. We have realized this fact only in the last few thousand years. That brings me to the next question, what exactly does January 1st represent? It’s certainly not the date the earth started spinning around the sun. It’s an arbitrary point of time in space that our planet passes through every 365 days. Now what’s so special about this point? Nothing. Think about it, the new year is just another point in space like any other. It’s one among the 364 other points around the Sun that the Earth passes through. And the fact is, whether we want it or not, the Earth will pass through this point every year like it has been while we or our concept of date or time didn’t exist or when it ceases to exist.</p><p>This is what makes me question our idea of celebration of the event. What exactly are we celebrating here? What have we done for this moment to happen? Nothing. It’s not like we are putting effort to make the Earth spin around the sun and we celebrate one year of pushing the planet. It’s just a random day we all choose to go out, drink, burst crackers and wish each other for no logical reason. I mean, what makes January 1st so special that February 1st or March 1st or any other day of the year does not enjoy? It’s not like at 12am on January 1st the stars in the sky glow brighter or the trees start talking. We’re simply celebrating something we never really achieved.</p><p>If you’re still reading at this point, I appreciate your patience. Since I have made such blatant accusations on the humanity for celebrating New Year’s day, let me explain what I think we should be celebrating. We should be celebrating progress and success. We should celebrate events that mark a positive change we make in our personal lives or to the world. Events that bring joy or happiness in someone’s lives, be it our own or better, someone else’s, that’s something that deserves a celebration. And that way, we get an opportunity to celebrate way more. It frees us from the social obligation of celebrating on a particular day of the year whether it makes sense to celebrate or not. Till now I was trying hard to come up with a plan for the new year when I was not being sure about why I had to celebrate. Being comfortable about this idea has made me feel much more relaxed.</p><p>This idea holds true for another overly hyped day — the birthday. Truth be told, I do not understand what makes birthday so special. It’s just another day in our lives. It’s not like a major significant biological change happens in our body on our birthday. And we definitely didn’t make an effort to move to that day. The day just happened like any other day. The whole idea of celebrating it is just an arbitrary social concept that as a society we have constructed. And most of us feel obligated to celebrate the day by spending time and money when that time could be spent towards making some meaningful progress, which deserves a celebration.</p><p>And that’s when I got the answer to the question I first had. I was being happy working because I was making some progress in my life. I was learning something new and doing something I enjoyed doing. I was celebrating whatever I was doing by being happy and I did not feel the need of a fancy ‘New Year Party’ to be happy. If I was good enough, I can be productive everyday and be equally happy.</p><p>This brings me to set fire to the third and final random concept, the ‘New Year Resolutions’. If the new year really held a major significance, then all our resolutions would’ve stayed true. It doesn’t because a lot of us aren’t too serious about our resolutions. We just make them because it’s a socially accepted norm. It’s ‘cool’ to make a list of things and put it on our Facebook page to tell people all the cool things we ‘plan’ to do. We would probably do them if someone kept track of it for the next 364 days. But since it realistically doesn’t happen, most resolutions drop like dead leaves. Making a resolution on the New year’s day is just the same as making one on March 18th or September 7th or any other random day. The concept of January 1st being a special day, is just our mental conception and nothing more. For resolutions, 365 days is too far apart to keep up and when we can’t keep up our resolutions, we end up getting demotivated.</p><p>(In case you’re wondering how to break out of the invisible social forces that forces us to do things we don’t want to do, here’s an excellent article that talks more on this topic — <a href="http://waitbutwhy.com/2014/06/taming-mammoth-let-peoples-opinions-run-life.html">http://waitbutwhy.com/2014/06/taming-mammoth-let-peoples-opinions-run-life.html</a>)</p><p>I instead propose we focus on making each day, a day of resolution. Waking up everyday and setting ourselves goals and targets that improves someone else’s life or our own life, puts us in a better position to achieve our goals and be happier. If we’re able to do this consistently, we do not need a random day to have a fancy phantom celebration to be happy or make one-time-resolutions to become better versions of ourselves. And that, is probably my new year’s resolution.</p><p>That said, I do like one thing about this time of the year. The discounts and offers that come up across stores. ;)</p><p>If you still think I talking BS and you want to celebrate the new year,I encourage you to go ahead. My startup will even help you with your party. Just ping me or go to <a href="http://www.eventosaur.com./">www.eventosaur.com.</a> You have every right to do whatever makes you happy. If you agree with me, thank you. Let’s spend time doing things that make sense to us.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d57172c118ef" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The changing dynamics of social media]]></title>
            <link>https://medium.com/@setumad/the-changing-dynamics-of-social-media-3749e1293e9a?source=rss-4f6545ae1780------2</link>
            <guid isPermaLink="false">https://medium.com/p/3749e1293e9a</guid>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[facebook]]></category>
            <category><![CDATA[social-media-biases]]></category>
            <dc:creator><![CDATA[Setu Kathawate]]></dc:creator>
            <pubDate>Sun, 20 Nov 2016 19:47:47 GMT</pubDate>
            <atom:updated>2016-11-20T19:49:24.660Z</atom:updated>
            <content:encoded><![CDATA[<p>There is something really interesting going on in the internet these days and the more I think about it, the more it makes me feel like I’m waking up in the middle of a roller coaster ride. It’s a ride for fun, but it’s scary to look down and it’s a ride which might never stop. Last week in my interaction design class, we had a very interesting discussion on the topic of personalization of web services that touched upon the most recent happenings in the US that got me thinking about how social media and the content we consume are influencing our behavior and decisions. Two events that happened last week — The Presidential election in the US and the demonetization reform by the Prime Minister in India, have made me start to question everything I’ve believed in.</p><p>It’s not anymore a secret that social media has been using our personal information to provide us tailored content and advertisements. While not all of us feel comfortable with that idea, on some levels we have rescinded to the fact and made peace with it. But there’s more to what’s happening that we aren’t aware of. Our behavior and personal/political preferences have started shaping what we read and see on the internet. Personalization has become the next step in the evolution of the internet. Our Google search results are tailored to who we are, where we are and what we like to see. And similarly, the posts we see on Facebook are generally on things that we believe in. The algorithms analyze our behavioral patterns by the links we click, the people or pages we follow and what we post and the rest of what we see is tailored based on these behavioral patterns.</p><p>The media has never enjoyed a vantage point as good as the one they hold today. They have extremely good access to the citizen and convey news, messages and ideas. And for the most part we base our beliefs and understanding of the world based on which media we follow and generally end up taking the side our favorite media houses talk from. When I look into the news I follow, nearly every one of them come with a very one sided perspective and my beliefs tend to see the world from the same perspective.</p><p>This is where the power of social media and personalization come in. What we see on popular social networks is no more a one size fits all content (or in other words, neutral). When searching for the same query, my Google search won’t show the same results as it would for you. My Instagram feed is no more chronological and shows me the most popular photos based on an algorithm. This is true about Facebook as well. Most of us gather our knowledge of the world from Facebook — from our friends, their thoughts and opinions, the pages/people we follow and …… what we ‘Like’ (Liking isn’t as innocuous as it seems). And Facebook uses this knowledge to tailor the content we see on our feed. This is the personalization of products to provide us more relevant stuff, be it content or advertisements.</p><p>This personalization, fortunately or unfortunately started to influence our political views as well and the result is an echo bubble that starts showing us things we only want to see and believe. While showing relevant content is great, it pushes us away from the facts and makes us more biased than we should probably be about certain important things. This was evident last week when the election results flipped out everyone I knew. I did not immediately understand the outcome when most of everything I saw and everyone I interacted inclined clearly towards one side. That’s what made me realize the small bubble I live in. I am surrounded (or have surrounded myself) with people who believe in one idea. And it was the same with the demonetization news. A big majority of my timeline opined towards one side while a small set of people had the diametrically opposite views.</p><p>The unfortunate reality is, much of what we see and the sources of our information are inherently biased. Neutrality is not encouraged as much as forming a right leaning or left leaning ideology. It’s even harder to find a source that truly provides a third perspective from a different vantage point. This leaves us with no option but to deviate towards one side and form an opinion based on the opinions thrown at us. While I’m not against having an opinion or taking political sides, I am concerned that we’re not making these choices on our own. These choices are being imposed upon us by algorithms. We are no more fully in control of what we choose to believe.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/458/1*W91oGGM-g38PuYOUkfkTFA.png" /><figcaption>It’s interesting how Facebook decided to show me these two entirely contradicting posts right next to each other.</figcaption></figure><p>So, how did this happen? Unfortunately, the answer to this question is not an easy one. As species, we are always evolving, getting continually better than what we were a day ago. At least that’s what is happening with technology. It has always been changing, evolving and getting smarter, much faster than our minds and behaviors evolve. Artificial intelligence is getting smarter everyday and we’re almost at that point where AI is much a part of our lives as the clothes we wear and the food we eat. In this purview, we can simply call this evolution.</p><p>The next question that would arise would probably sound something like “So what do we do next? Can we stop the robots from taking over the humans?”. The answer to this would also be a no (unless moving to the mountains is an option). We cannot stop technology from evolving, get smarter and make the world a better and comfortable place to live in. This has been the essence of humanity.</p><p>This leaves us with one realistic option — Evolve with the technology. We must get smarter and try to keep up pace with the changes that are happening around us. We must realize that not everything we see and read is necessarily the fact. We should take every claim, statement and judgment our favorite media ‘artists’ create with a pinch of salt, because they’re forming an opinion of their own and presenting us with the perspective they believe is right. These beliefs may have taken form due to various reasons unbeknownst and unexplained to us. And they will continue to do so because that’s how they keep their cash registers ticking.</p><p>As consumers, we should start getting smarter about making out the difference between an emotion influenced bias and factual realities. I believe that not every person who voted for Trump is a misogynist who goes around racially abusing everyone in his sight, not every person who voted for Clinton is a genius who clearly knew what the world wanted. Similarly in the other side of the world, the demonetization is not the most radical, world-changing move and nor is it a cunning plan to make people run between ATMs and bank branches. We must understand that running a country is not as simple as these superficial judgements we are exposed more to. There are far greater complications and consequences involved in these decisions and we must make a serious attempt to understand and view these developments from all possible perspectives. I wish technology provided us better access to unbiased education on these topics and helped us develop more informed opinions. Till that happens we should develop more empathy and be more analytical before forming our own opinions. When we realize our dynamics with artificial intelligence and network based communication, our relationships with social media would be healthier. If we continue fueling quick opinions and dramatic sentiments, we end up creating grand echo chambers which ultimately consumes us and when realities happen, as they always did, we become too fragile to accept them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3749e1293e9a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Prototyping & Usability Testing]]></title>
            <link>https://medium.com/@setumad/prototyping-usability-testing-c2eba8d8fc0c?source=rss-4f6545ae1780------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2eba8d8fc0c</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Setu Kathawate]]></dc:creator>
            <pubDate>Tue, 10 May 2016 03:55:28 GMT</pubDate>
            <atom:updated>2016-05-10T03:55:28.571Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve spoken about the importance of user research in a product development cycle in my <a href="https://setublogs.wordpress.com/2015/11/28/what-is-user-research-and-why-is-it-important/">previous blog</a>. What comes after a solid user research is the phase of prototyping and testing, and these are just as critical as user research. Research, Prototyping and, Usability Testing form the salt and spices of a well balanced dish (yes, we care a lot about food). A dish can be cooked without salt or spice, but you won’t have too many people liking it. The story is very similar in the case of product development too. A product built on assumptions and poor testing will eventually find itself difficult to accommodate the needs of its users and will need more fixing,which translates to a lot of wasted time.</p><p><strong>A Wireframe is not a prototype.</strong></p><p>While it’s very easy to get confused between a wireframe and a prototype, they’re quite different. A wireframe is a rough visualization of the proof of concept. They are stuff that we sketch on paper or on tools like Balsamiq that gives a rough idea of what an interface looks like. However, the scope of a wireframe ends there. A collection of wireframes that are related to each other and help a user complete a task flow qualifies as a prototype. Mockups are similar to wireframes too, just that their fidelity (level of detail) would be different.</p><p><strong>What is prototyping?</strong></p><p><a href="https://www.youtube.com/watch?v=_g4GGtJ8NCY">Prototyping</a> is a quick an easy way to validate our ideas based on the research information we have. It is a proof of concept and not the actual product itself. And it should not be the actual product. Prototyping is done in the very early stages of ideation to understand what works for users and what doesn’t in order to quickly iterate based on the learnings from these tests. An important thing to note about prototyping is that ‘Prototypes are messy’. And that is how they should be. When thinking of testing, it’s very easy to confuse a prototype for a high-fidelity mockup. They’re two different entities altogether. While usability testing is done on both the interfaces, the purpose and the goals of the testing are very different. With a low fidelity prototype we test if users can figure out their way through the task and reach their goal in the expected way. A high fidelity mockup test would reveal if people can find the right buttons or if they like the colors. Understanding what we’re testing is very important to get the right data.</p><p><strong>Usability Testing</strong></p><p>Usability testing is an amalgamation of art and science. It is more than just watching users complete a task using a prototype or product. The real purpose of conducting a usability testing is not to see if a user can complete the task, but why they’re doing what they’re doing. It’s not a test of the users but of their interaction with the system. If you read the previous sentence clearly, I defined two important facets of design: Interaction Design and Usability Testing. Interaction design is all about creating a dialogue between a user and a system while Usability testing is about understand how the dialogue takes place. While conducting a usability test, it’s all about reading between the lines.</p><p>While usability testing is a very detailed subject in itself, I will give a quick list of the most important things to consider before and while conducting a usability test.</p><ul><li>When testing with a low fidelity prototype (A set of wireframes), we should make it clear to the participants that they’re not testing an actual product and it is just a proof of concept built to validate the design decisions. Using the findings of the usability test we would build a high fidelity prototype/mockup.</li><li><a href="https://www.nngroup.com/articles/recruiting-test-participants-for-usability-studies/">Recruit</a> wisely. Do not get people who’d be biased and who are involved in the working of the project. Getting unbiased and candid feedback is the most effective way to build a solid product. Also, do not test with more than 6–8 users per iteration. That’s a good enough number to uncover most usability issues in the prototype.</li><li>Explain the purpose of the test to the participants clearly. When they know why they’re doing something, they’ll have more ownership on their actions and they’ll be more involved in the test, which will give us better findings.</li><li>Remind the users that they’re not being tested, but the prototype and whatever they do are not any of their mistakes. This helps them be more candid with their opinion.</li><li>Always ask participants to ‘think out loud’. <a href="https://www.nngroup.com/articles/thinking-aloud-the-1-usability-tool/">Think-out-loud</a> is a beautiful process to understand the psychology of our users. Asking them to speak out what they’re thinking lets us know their thought process which is very important in understanding their mental model.</li><li>Another thing to remember is that people do not remember instructions very well. They tend to get distracted and veer away from the task or may stop thinking out loud. As moderators, we’ve to be aware of their actions and give subtle reminders to think out loud or take another look at the task list.</li><li>If they’re completing a specific task, hand them a clear task list that tells them what they’re supposed to achieve. Also, do not be too specific with the tasks. For example, instead of telling ‘Click on the back’ button’, tell ‘do task x’. Let them figure out where to click. Also, having a clear task list will help participants stay on the task and not get distracted and lost in the middle of a task.</li><li>Before every new task, ask them to read out the task loud. This will keep the task more firmly in their mind.</li><li>Avoid helping users or giving them leading hints. Telling them ‘Ok you can press that button now’ is a direct hint and when people are testing, they WILL more often than not, click it even if they didn’t want to. As tempting as it is to help people when they seems lost, it’s important to know that they do not get such help when they’re using the product on their own. Let participants explore and figure their way out all the while making notes of what’s going on.</li><li>If a person cannot find something and asks you what to do next, do not tell them what to do, rather respond back with a question that helps you learn more. For example, when they cannot find a back button to a webpage, get stuck and ask for help, ask them what they’d usually expect in such a scenario, what they want to do and if they were to design the webpage, where they’d put the back button. It’s amazing how many things we think of as obvious are a total mystery to other people. And sometimes people give the best suggestions from their experience.</li><li>When you find that they’re completely lost and cannot find their way around, give them a couple of minutes to see if they can recover from the error. If they still cannot, give a subtle hint to see if they can find their way from there. If that doesn’t work as well, note that as a major usability issue, ask them what they’d expect and move them to the next task. At any point, Do not make them feel like they’re dumb.</li><li>It’s very important to constantly ask them to explain their actions and decisions. But their explanations must be taken with a pinch of salt. There is a difference between what people do and what they tell. This is why every usability test must have a well triangulated recording process. Usually usability tests will have a moderator, a note taker, screen and audio/video recording tools to correlate data.</li><li>Give close attention to their expressions. People are usually quite expressive and usually give out subtle feedback using non-verbal hints. For example a soft ‘hmmmm!’ to express surprise or a quick ‘oh shit!’ are all very important hints that something they didn’t expect happened. It’s important to note these moments and ask them with a follow-up question ‘please tell me why you said ‘oh shit!’.</li><li>The purpose of a usability test is not always to find faults in a system. If they like something, it is just as important to ask them why they liked it. Even if they do not tell, as moderators, we must make sure to find out the positives of the design. Knowing what worked will give designers a direction to go forward and iterate the design.</li><li>Start and end the usability test with a short interview. Before the test ask users about their experience using similar products, their frustrations, likes and their expectations. End it by asking their experience using the prototype, what they liked or disliked about it, what was most challenging and what they’d change if they could. Understanding their thought process is the goal of a usability test.</li></ul><p>Knowing these points above is very important for a successful prototype design and testing. While it appears simple, its quite hard to stay focused while creating prototypes and testing with users. It’s very easy to slip into the user mentality and when we lose focus, we end up losing a lot of data and waste considerable amount of time both for us and the participants.</p><p>Prototyping and Usability studies are the equivalent to a physical structure’s foundation. While it may take some extra time and effort, going through these processes gives a product a very solid backbone which can later be used to build upon during successive iterations. This avoids the problem of building a product and later discovering it doesn’t work for its user. This is the reason why companies like Facebook, Google and Twitter put such heavy emphasis on research and design. They understand their users’ needs, goals and frustrations before designing a product and that’s what makes a cult-following billion dollar product.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2eba8d8fc0c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Choosing To Become A UX Designer Was The Best Decision I Ever Made]]></title>
            <link>https://medium.com/@setumad/why-choosing-to-become-a-ux-designer-was-the-best-decision-i-ever-made-c7705d834a86?source=rss-4f6545ae1780------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7705d834a86</guid>
            <category><![CDATA[problem-solving]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Setu Kathawate]]></dc:creator>
            <pubDate>Tue, 29 Mar 2016 19:33:23 GMT</pubDate>
            <atom:updated>2016-03-29T19:33:23.987Z</atom:updated>
            <content:encoded><![CDATA[<p>I always believe things happen in life for a reason. I’m studying master’s in Human Centered Design and Engineering at the University of Washington. As a graduate looking to get some experience and make some money, I applied for several positions to work as a Research Assistant on campus. I couldn’t make it, some due to lack of experience and some due to mismatch in role. Although I was upset, I never stopped looking and luckily I got a chance to work on a research project at the Department of Psychiatry as a User Researcher.</p><p>The objective of the project was to study stress patterns in people and come up with interventions that can help people cope better with stress. As a part of the research, I had to interview people and ask them questions, some of which no one would have ever asked them before. This was an opportunity for people to really open up to things they would probably find very uncomfortable talking in their private lives. Most of the times I could relate to what people were saying with my own stress patterns. Things like getting the feeling of being lost, losing focus, anxiety were some recurring themes.</p><p>However, one interview changed my perspectives. I interviewed a middle aged person, who had several complications in his life. He was suffering from several health, familial and financial issues which were compounding the stress levels in him. He suffered from sleep apnea which made it difficult for him to sleep for more than 2 hours at a stretch. Although, I had seen similar issues in my life before, this was the first time I heard in the shoes of someone believed to solve his problem. And while I felt I had big problems in life, I was humbled by learning the magnitude of problems people faced every day in their lives. Although the interview left me a bit shaken by the end, it gave me a reassurance I was always looking for — That choosing to become a UX Designer was the best decision I have ever made.</p><p>As a designer, my job is to listen to a user, empathize with his/her problems, and come up with solutions to problems that I previously thought had no solutions to. And this, is what I beleieve is the greatest challenge for a designer. It’s not just about designing interfaces and making things prettier, it’s about solving problems that make a significant difference in people’s lives. It’s about designing experiences that make people’s lives better. Be it with Eventosaur or the research work I’m doing at The university, every project poses me with unique problems in people’s lives and coming up with solutions to those problems is what drives me and gives me the greatest joy.</p><p>I am by no means a successful designer or a problem solver. I am far from that, but having made the choice to be on that path is what I am most satisfied with. Some day I hope to meet that person I interviewed and listen to him say “The solution your team designed helped me sleep better now and that makes me feel good” and I would have done my job.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7705d834a86" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>