<?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 Punit Dwivedi on Medium]]></title>
        <description><![CDATA[Stories by Punit Dwivedi on Medium]]></description>
        <link>https://medium.com/@iampunit?source=rss-3362f40cda66------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*_ntgtOjPGGDhTdtjSGwEQw.png</url>
            <title>Stories by Punit Dwivedi on Medium</title>
            <link>https://medium.com/@iampunit?source=rss-3362f40cda66------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 19:20:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@iampunit/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[The Power of Moments: The UX of Peak-End Rule]]></title>
            <link>https://medium.com/design-bootcamp/the-power-of-moments-the-ux-of-peak-end-rule-79ebfc37116a?source=rss-3362f40cda66------2</link>
            <guid isPermaLink="false">https://medium.com/p/79ebfc37116a</guid>
            <category><![CDATA[laws-of-ux]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[peak-end-rule]]></category>
            <dc:creator><![CDATA[Punit Dwivedi]]></dc:creator>
            <pubDate>Sat, 09 Sep 2023 19:02:46 GMT</pubDate>
            <atom:updated>2023-09-13T23:54:33.376Z</atom:updated>
            <content:encoded><![CDATA[<p>Imagine going on a thrilling ride at an amusement park. You climb to the top, and then whoosh, you zoom down at top speed. That exciting part is the “peak” of the ride. Now think about how the ride finishes — it might be a smooth glide back to where you started or a sudden stop. That ending is the “end” of the experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AdwSI2ZueKTgq7zT" /></figure><p>The <strong>Peak-End Rule</strong> tells us something interesting: our brains don’t remember everything about an experience. Instead, they pay special attention to two things — <strong>the most exciting part (the peak)</strong> and <strong>how it all finishes (the end).</strong> These two moments have a big impact on how we feel about the whole experience.</p><h3>The Peak: The Most Exciting Moment</h3><p>Let’s talk about the first part of the rule: the peak. Think about a concert where the music is fantastic, and the singer performs an incredible solo. That amazing solo is the “peak” moment, and it’s something you won’t forget.</p><p>For websites or apps, it could be when you find something really cool, like a great article or an easy way to use a feature.</p><blockquote>Lesson 1: Businesses can make important moments special to leave a strong impression.</blockquote><h3>The End: How It All Wraps Up</h3><p>Now, let’s move to the end. Imagine you’ve just finished reading an amazing book, and you come to the last few pages. Those final lines are important because they shape how you remember the whole story.</p><p>In the digital world, it’s like when you finish buying something online, and you see a message thanking you for your purchase. That “end” feeling matters a lot.</p><blockquote>Lesson 2: Making the end of an experience pleasant can make people remember it fondly.</blockquote><h3>Real-Life Example: Amazon Prime Video</h3><p>Think about watching shows on Amazon Prime Video. When one episode ends, they often suggest the next one to keep you hooked. <strong>This makes you want to keep watching.</strong> It’s a good example of how they use the “end” to keep you engaged.</p><h3>Putting It All Together</h3><p>While the peak and end are important, we shouldn’t forget about everything in between. Think of it like your daily commute — it might have boring parts, but your memory mainly focuses on the crazy traffic jam (the peak) and finally getting to work (the end).</p><blockquote>Lesson 3: Even though the peak and end matter a lot, the whole experience still counts.</blockquote><h3>How to Use the Peak-End Rule</h3><p>So, how can we use this idea in everyday life? It’s about finding chances to create memorable peaks and nice endings, while also making sure the journey is enjoyable.</p><p>Remember, the peak and the end are like bookends for our memories. But all the moments in between are important too. By making the best of the peak and end, we can shape how people remember what we do.</p><p>In short, the Peak-End Rule is a powerful tool. Whether we’re making websites, creating content, or just living life, understanding and using the magic of the peak and end can make a big difference.</p><p>So, as you go through life, think about making your exciting moments even more exciting, making your endings satisfying, and making everything in between as fun as possible. That way, people will remember the good times and smile.</p><p><strong>And that’s the story of the Peak-End Rule — an idea that helps us make our memories even better.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=79ebfc37116a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-power-of-moments-the-ux-of-peak-end-rule-79ebfc37116a">The Power of Moments: The UX of Peak-End Rule</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to set your UX research target and create insightful questions.]]></title>
            <link>https://iampunit.medium.com/determine-research-goals-and-questions-e2eb1d8272d4?source=rss-3362f40cda66------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2eb1d8272d4</guid>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[empathy]]></category>
            <dc:creator><![CDATA[Punit Dwivedi]]></dc:creator>
            <pubDate>Fri, 13 May 2022 07:19:31 GMT</pubDate>
            <atom:updated>2023-03-26T09:00:39.298Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey there! Are you interested in conducting UX research but not sure where to start? Well, don’t worry! I’m here to help you out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yzZGkPvK3PkMMga2.jpg" /></figure><h3>Determine research goals</h3><p>Let’s begin by talking about how to determine your research goals and questions. It’s essential to make sure that your interviews are worthwhile for both you and the participants. To do that, you need to <strong>set clear goals for the interview.</strong> As a UX designer, you should think about what you want to learn from the interviews. Are there any user problems or pain points that you need to empathize with??</p><p>Here are some examples of common research goals when it comes to empathizing with users:</p><ul><li>I want to understand the processes and emotions that people experience around the problem my product is trying to solve.</li><li>I want to identify common user behaviors and experiences with tasks that my product is trying to address.</li><li>I want to understand user needs and frustrations as they relate to the product I’m designing.</li></ul><h3>Write interview questions</h3><p>Writing interview questions can be a bit tricky, but don’t worry, I’ve got some tips for you!</p><p>There are a few best practices to keep in mind when writing interview questions:</p><ul><li><strong>Ask open-ended questions.</strong> Open-ended questions allow the person being interviewed to answer freely, instead of with a simple “yes” or “no.” For example, if you’re designing an app to help people find a sharing cab, you should ask “Could you describe your experience with finding and scheduling cabs?” instead of “Have you ever used an app to find a shared cab?” Keep in mind that the questions you ask during interviews should not lead or pressure participants towards a desired response; instead, asking open-ended questions lets participants share their true thoughts and perspectives.</li><li><strong>Keep questions short and simple.</strong> It should be easy for interview participants to understand what you’re asking.</li><li><strong>Ask follow-up questions.</strong> During the empathize phase of the design process, interviews should be conversational, so encouraging participants to elaborate is a best practice. After a participant answers an interview question, try asking them “Why?” or use the phrase, “Tell me more about that” to keep the conversation flowing.</li></ul><p>Research is an essential part of the UX design process and empathizing with users. Taking time to outline the goals for your research will help ensure the feedback you obtain is valuable.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2eb1d8272d4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Define problem statements]]></title>
            <link>https://iampunit.medium.com/define-problem-statements-2efe67445a07?source=rss-3362f40cda66------2</link>
            <guid isPermaLink="false">https://medium.com/p/2efe67445a07</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[problem-solving]]></category>
            <dc:creator><![CDATA[Punit Dwivedi]]></dc:creator>
            <pubDate>Thu, 12 May 2022 09:01:11 GMT</pubDate>
            <atom:updated>2022-05-12T09:01:11.532Z</atom:updated>
            <content:encoded><![CDATA[<p>Identifying the problems that users face is one of the most important parts of UX design. But as critical as research is to the UX design process, some of your work will still require a small amount of “mind reading” about the user’s experience. That might seem like it’s contradicting the rule of never making assumptions, but sometimes users just won’t feel comfortable or know how to express exactly what their problem is and how it affects them. In this reading, you’ll learn how to define unspoken pain points and use them to form strong problem statements.</p><h3>The connection between pain points and problem statements</h3><p>As a reminder, <strong>pain points</strong> are any UX issue or friction that frustrates the user and blocks them from getting what they need. Minimizing pain points keeps users happy and encourages them to keep interacting with the product. So, how do UX designers find and define pain points?</p><p>Think about the dog walker app and one of our user personas, Arnold. Arnold is in his late fifties, and his kids have encouraged him to upgrade to a smartphone. Arnold is a leader at his company, and not used to admitting he’s uncomfortable with technology. After his wife died, Arnold became the primary caregiver of the family’s animals. But, he works over sixty hours per week, and is unable to take his three dogs on twice-daily walks. Arnold is turning to the dog walker app for help.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tVm7oHTAIXFyiYGM" /></figure><p>You learned earlier that there are four categories pain points can fall into:</p><ul><li><strong>Financial</strong>, or money-related pain points.</li><li><strong>Product</strong>, which are pain points related to quality issues.</li><li><strong>Process</strong>, which are pain points related to the user’s journey.</li><li><strong>Support</strong>, which are pain points related to getting help from customer service.</li></ul><p>Identifying the pain points your user is experiencing will help you find potential problems that your design can solve. Arnold’s pain points fall into the process category. His biggest challenge is that he’s not technologically savvy, so he struggles to understand how to use the app.</p><p>Now that you’ve identified Arnold’s pain points, you need to be sure you know enough about his needs to write a problem statement.<strong> Problem statements </strong>provide a clear description of the user’s need that should be addressed. To build a problem statement, you can utilize the 5 Ws framework.</p><h3>The 5 Ws and H: who, what, when, where, why, and how</h3><p>The most common framework used to create problem statements is the 5 Ws and H framework. After you define the user’s pain points, you can answer who, what, when, where, why, and how to solve the user’s problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3RblnKzESouT35QQ" /></figure><p><strong>Who</strong> is experiencing the problem? Knowing your users and their background is key to creating successful solutions for them.</p><p><strong>What</strong> are the pain points you’re trying to solve? Determining a user’s pain points early allows you to answer the rest of these questions and clarify the context of the pain points.</p><p><strong>Where</strong> is the user when they’re using the product? A user’s physical context matters to your design.</p><p><strong>When</strong> does the problem occur? Maybe it’s right after the end of a long and tedious process, or maybe it’s something that happens daily. Knowing when the problem occurs can help you better empathize with the user’s feelings.</p><p><strong>Why</strong> is the problem important? Knowing how this problem affects your user’s experience and life will help to clarify the potential consequences.</p><p><strong>How</strong> are users reaching their goals by using the product? Understanding how users reach their goals allows you to map the user journey that they take through your product.</p><p>To design a solution that fits the needs of your users, you have to understand the problem from their point of view. Thinking through the 5 Ws and how forces you to write out who the user is and describe the full context of the problem from the user’s perspective.</p><p>Okay, back to the dog walker app! You know a bit about Arnold already, but use the skills you’ve learned so far to confirm you know enough to solve his pain points.</p><ul><li><strong>Who:</strong> A busy executive</li><li><strong>What:</strong> Arnold wants to hire a daily dog walker for his three dogs.</li><li><strong>Where:</strong> Arnold is likely using the app at work, on the go.</li><li><strong>When:</strong> Arnold gets frustrated when he opens the app, starting from the very beginning of the user journey.</li><li><strong>Why: </strong>Arnold doesn’t have a lot of experience with phone apps or similar technology.</li><li><strong>How:</strong> Arnold wants to go easily from the home screen of the app to the list of dog walkers to the confirmation screen.</li></ul><p>Ta-da! You were able to successfully answer all six questions. Now that you’ve thought through your user’s needs, you’re ready to define the final problem statement.</p><h3>The problem statement formula</h3><p>So, how do you create a problem statement? Start by defining who the user is and what their needs and motivations are. Here’s the formula we introduced in the video:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*niKbof5yXnE0Nb3s" /></figure><p>Okay, now apply the formula to Arnold. Arnold is a busy professional who needs a dog walker. But what’s the insight? His phone! His kids gave him a shiny, new smartphone. Arnold shared that he often struggles with technology and is having an issue navigating the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IRmANNu-bYpK7hwE" /></figure><p>Arnold is a busy executive who needs an easy app experience to hire a dog walker because he’s not technologically savvy.</p><h3>The impact of problem statements</h3><p>Problem statements provide clarity about your users’ goals and help UX designers identify constraints that prevent users from meeting those goals. Problem statements also help your team measure success. If you expect that Arnold and users like him will engage the most with your app, you should make the app clear and easy for them to understand.</p><p>The designs you create matter! Empathize with your user as much as you can to make a product that they’ll want to interact with and use every day.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2efe67445a07" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Who are my users?]]></title>
            <link>https://iampunit.medium.com/who-are-my-users-fb823e0d2247?source=rss-3362f40cda66------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb823e0d2247</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <dc:creator><![CDATA[Punit Dwivedi]]></dc:creator>
            <pubDate>Thu, 28 Apr 2022 07:01:29 GMT</pubDate>
            <atom:updated>2022-04-28T07:01:29.525Z</atom:updated>
            <content:encoded><![CDATA[<p>In the field of user experience design, the “user” comes first. A <strong>user</strong> is a person who is trying to solve a problem and is looking for a product or service to help them solve it. The <strong>user experience</strong> is the journey that the user takes with that product or service. As a UX designer, your goal is to keep the user at the center of every decision you make, and to do that, you need to get to know your user.</p><p>Most of the initial UX research that you conduct at the beginning of the project will be focused on getting to know the characteristics of your users, their goals, and their pain points. Understanding the user empowers you to design experiences that are helpful or easy to use.</p><p>One of the key challenges of getting to know your users is avoiding taking a narrow view of the user, or making assumptions about what users need based on stereotypes. Users who seem to be different from one another might actually have shared wants and needs. Make sure to step back and get a clear picture of <em>all </em>your potential users–which often means that you’ll need to specifically plan to address the needs of users who are often overlooked.</p><p>To reach as many users as possible, you’ll consider questions such as these as part of your user research approach:</p><ul><li>Do my users have impairments or disabilities to consider–whether temporary, situational, or permanent?</li><li>How familiar are my users with technology?</li><li>How are my users accessing the product or service?</li><li>Where and when are my users accessing the product or service?</li><li>Have I considered all my potential users?</li></ul><p>The goal for user research is to get the widest possible selection of potential users to include as research participants. Make sure to consider income level; demographic data such as age, gender, and ethnicity; educational background; and geographic location.</p><h3>Do my users have impairments or disabilities to consider?</h3><p>You might be surprised to find out that more than 1 billion people around the world have a disability, out of a global population of 7.8 billion. In the U.S., one in four adults identifies as having a disability. The term <strong>accessibility</strong> refers to the design of products, devices, services, or environments for people with disabilities. As a UX designer, it’s important to keep users with disabilities in mind as you design features or new products. Designing for accessibility isn’t an obstacle, but a way to get your products to as many users as possible.</p><p>Accessibility is about making products accessible to all people, whether they have a disability or not. Think about inclusive product features that increase magnification, like enlarged fonts. Or features that help everyone understand videos, like closed captions.</p><p>Throughout the rest of the certificate program, you’ll learn more examples of how features that were initially designed for users with disabilities became universally used by non-disabled people as well. You’ll also learn more about how to effectively apply accessibility principles to your designs.</p><h3>How familiar are my users with technology?</h3><p>User experience doesn’t just focus on the experience of existing users, however. It also includes paying attention to the needs of people who are about to become users. Nearly a billion people, of all ages, all around the world, are getting online for the very first time.</p><p>When it comes to designing for this emerging population of potential users, their level of <strong>digital literacy</strong> is a key consideration. The American Library Association defines digital literacy as “the ability to use information and communication technologies to find, evaluate, create, and communicate information, requiring both cognitive and technical skills.” People with limited digital literacy might not be familiar with certain design patterns, calls to action, or icons that those of us with more online experience take for granted. For example, they might not know what “swipe” means in relation to a touchscreen. They may not even know what a touchscreen is. This can affect their confidence and willingness to explore new technology.</p><h3>How are my users accessing the product or service?</h3><p>It’s important to keep in mind that not all users will access your product or service in the same way due to the cost and availability of devices and internet services. These factors are often due to other broader and historical factors in the markets you might be designing for.</p><p>Some users might not have reliable or unlimited access to the internet. This might be because the data they have purchased has run out or because their network coverage is inconsistent or sporadic. As a UX designer, you should try to find ways to take the offline experience into account as well. For more examples of ways you can create a rich offline experience for your users, check out the article <a href="https://web.dev/offline-ux-design-guidelines/"><em>Offline UX design guidelines</em></a> on web.dev.</p><h3>Where are my users accessing the product or service?</h3><p>In some cases, you might be designing a product or service intended for use by people in various locations around the world, which creates some additional considerations, like local languages and cultural norms. Keep in mind that cultures and norms are ever-changing as people integrate and recontextualize technology in their lives, so you’ll need to continue to research potential users to identify shifts in user problems, preferences, and usage patterns over time.</p><p>Users who speak languages other than the primary language of the product or service you’re designing might want or need to switch languages on their device depending on what they’re trying to accomplish. For example, a user might want to read in Hindi but type using the English keyboard. Or the user might encounter a concept that cannot be easily translated from one language to another. Designing a multilingual keyboard option, and using universally-recognized icons, like an icon with a local currency sign for a banking app, are just a few key ways UX designers can make it easier for users in different locales.</p><h3>Key takeaway</h3><p>Your goal as a UX designer is to solve a user problem by creating a design that makes every user feel like you designed the experience just for them no matter who they are, where they live, how much they earn, what their abilities are, or how highly they’re educated. Gaining a comprehensive understanding of your user’s context is an important place to start, and you’re already on your way.</p><h3>Resources for more information</h3><p>If you want to learn more about some top reasons why user research is important to the field of UX design, check out the article <a href="https://careerfoundry.com/en/blog/ux-design/the-importance-of-user-research-and-how-to-do-it/"><em>What is user research, and what’s its purpose?</em> </a>on CareerFoundry.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb823e0d2247" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Thinking: A UX design framework]]></title>
            <link>https://iampunit.medium.com/design-thinking-a-ux-design-framework-18695c6970aa?source=rss-3362f40cda66------2</link>
            <guid isPermaLink="false">https://medium.com/p/18695c6970aa</guid>
            <category><![CDATA[google]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <dc:creator><![CDATA[Punit Dwivedi]]></dc:creator>
            <pubDate>Thu, 28 Apr 2022 06:37:39 GMT</pubDate>
            <atom:updated>2022-04-28T06:38:54.668Z</atom:updated>
            <content:encoded><![CDATA[<p>In the world of UX design, a <strong>framework</strong> is a conceptual tool that provides guidance on the best practices and processes for solving problems and building solutions that solve the problems of real users. Frameworks provide structure for the design process and foster collaboration, which can spark innovations. Most UX designers follow a specific framework or process when approaching their work, from the first idea all the way through to the final launch of a product.</p><p><strong>Design Thinking</strong> framework to sequence the assignments that contribute to the designs that you’ll create throughout the program. The Design Thinking framework is a user-centered approach to problem-solving that includes activities like research, prototyping, and testing to help you understand who your user is, what their problems are, and what your design should include.</p><p>The Design Thinking framework involves the following phases: empathize, define, ideate, prototype, and test.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UN2s2KI46RZK7EnA" /></figure><p>Though it may sound like a linear process, the Design Thinking framework should be iterative, which means that you’ll repeat certain phases as you refine your designs. For example, depending on the feedback you receive during testing, you might need to conduct additional research, brainstorm new ideas, or develop new prototypes.</p><p>Let’s look at the five phases of the Design Thinking framework to learn more about which activities you’ll perform during each one. Keep in mind that the Design Thinking framework as presented here is an idealized model for UX designers to follow, so you might see some variation in its implementation between different companies, teams, or projects.</p><h3>Empathize</h3><p>During the <strong>empathize</strong> phase, your primary goal is to learn more about the user and their problems, wants, and needs, and the environment or context in which they’ll experience your design. The most important part of the empathize phase is to step away from your assumptions and guesses and let your research findings inform your decision-making in later design phases.</p><p>Your user research might include user surveys, interviews, and observation sessions, and you might also need to conduct some research on the competitors’ products to determine how your user frames competitors’ products as part of their daily life and daily problem-solving.</p><h3>Define</h3><p>In the <strong>define</strong> phase, you’ll analyze your research findings from the empathize phase and determine which user problems are the most important ones to solve, and why. This will drive you toward a clear goal for the design of the product.</p><p>The most important outcome of this phase is a clear problem statement, which is a description of the user’s need that your designs will address. You might also develop a value proposition, which is a summary of why your user would or should use the product or service that you’re designing.</p><h3>Ideate</h3><p>After you land on a user problem and establish why it’s an important one to solve, it’s time for the <strong>ideate</strong> phase. The goal of ideation is to come up with as many design solutions as possible — don’t settle for your first solution because the most obvious solution is not always the right one.</p><p>Ideation involves collaborative brainstorming with other members of your team to generate as many solutions as possible to a problem. This could include marketing, engineering, product management, or any other stakeholders for the product or service. During brainstorming sessions, you should explore all possible solutions. Don’t focus on whether something is a “good” or “bad” idea, just collect as many ideas as you can. The important thing here is to keep this process judgment-free.</p><p>After brainstorming, you’ll then analyze your potential solutions and start to make choices about which ones are the best options to pursue as prototypes. You might return to user or competitive research to help you narrow down your ideas, and you might also create user flows to illustrate how the user will interact with your solution.</p><h3>Prototype and Test</h3><p>After you have an idea of how to solve the problem, you’re ready to enter the <strong>prototype</strong> phase, where your goal is to produce an early model of a product that demonstrates its functionality and can be used for testing. The <strong>test </strong>phase is critical to developing the right solution to address your user’s problem, and an organized approach to testing can help you create exceptional user experiences.</p><p>Prototyping and testing are interconnected, which means that you’ll test your designs at each stage of prototype development rather than waiting to test until after the working prototype is complete. If the design is too polished the first time you present it to users, you might not get as much feedback. Think about ways to include testing throughout the design process, so that you’re iterating your designs based on user feedback instead of other reasons.</p><p>For example, you might test the concepts behind your design by presenting users with a simple sketch, wireframe, or a sitemap. Taking what you learned, you might iterate on that design to a more detailed design on paper (known as a low-fidelity prototype) and conduct another round of user testing. At some point, you’ll iterate the design again into a working, interactive model using a software program (also known as a high-fidelity prototype) and test that as well. You might also consider testing more than one prototype at the same time to get feedback on multiple solutions, or testing the same prototype on multiple platforms, such as a laptop, tablet, and smartphone.</p><p>The goal of testing prototypes is to continue to refine the prototype as you gain insight into whether the design for your product or service is easy to use and solves the user’s problem. At some point, you’ll finalize a prototype, and then you’ll provide it to developers, who will then turn your design into a product.</p><h3>Key takeaways</h3><p>The Design Thinking framework is only one type of framework that UX designers use to organize their approach to designs, often based on the product they’re designing and the organization they’re working for. No matter which frameworks you use in your career, they all have a few core principles in common:</p><ul><li>Focus on the user.</li><li>Create solutions that address the user’s problems.</li><li>Collaborate with teammates across departments.</li><li>Validate your designs.</li><li>Iterate as needed to design the right user experience.</li></ul><p>Throughout the rest of the certificate program, you’ll learn more about each of the phases of the Design Thinking framework and complete practice activities to gain more experience with designing user experiences end-to-end.</p><h3>Resources for more information</h3><p>For more about the Design Thinking framework, check out the following resources:</p><ul><li><a href="https://www.youtube.com/watch?v=6lmvCqvmjfE"><em>Design Thinking 101</em></a> by Nielsen Norman Group</li><li><a href="https://www.youtube.com/watch?v=Tvu34s8iMZw"><em>The Design Thinking Process — An Introduction (2021)</em></a> by Career Foundry</li><li><a href="https://xd.adobe.com/ideas/guides/ux-design-process-steps/"><em>UX Design Process: Everything You Need to Know </em></a>by Adobe</li><li><a href="https://www.interaction-design.org/literature/topics/design-thinking"><em>What is Design Thinking?</em></a> by The Interaction Design Foundation</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18695c6970aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The influence of company size and industry]]></title>
            <link>https://iampunit.medium.com/the-influence-of-company-size-and-industry-4d5c2760ffba?source=rss-3362f40cda66------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d5c2760ffba</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <dc:creator><![CDATA[Punit Dwivedi]]></dc:creator>
            <pubDate>Wed, 27 Apr 2022 11:42:31 GMT</pubDate>
            <atom:updated>2022-04-27T11:42:31.101Z</atom:updated>
            <content:encoded><![CDATA[<p>Have you always dreamed of working with a close-knit group at a startup? Or landing a job at your favorite company? Depending on where you end up working, your job as a UX designer could be quite different! In this reading, you’ll explore how UX design roles can vary depending on the company’s size and industry.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M9CXMcukQZ6kWRT4t3pMQg.jpeg" /></figure><h3>Startups and small businesses</h3><p><strong>Startups</strong> are new businesses that want to develop a unique product or service and bring it to market. <strong>Small businesses</strong> are privately owned businesses with few employees. A lot of UX designers are excited to start work at startups or small businesses because they can see the impact of their work more quickly and develop a broader range of skills.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*LKOs8QEdINLtuljC" /></figure><ul><li><strong>Team size: </strong>Close-knit team and able to work directly with upper management.</li><li><strong>Growth:</strong> Opportunity for growth due to taking on many responsibilities (visual design, interaction design, user research, and more).</li><li><strong>Creativity:</strong> Usually more creative freedom with fewer guidelines and processes.</li><li><strong>Impact:</strong> Lots of impact on final products, with few people working on a project.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*uvN8t2YgtqAWguXO" /></figure><ul><li><strong>Mentorship: </strong>Fewer mentors to choose from within a smaller company.</li><li><strong>Responsibility:</strong> Most of the responsibility for a UX project falls solely on you, which can be stressful if you have little UX experience.</li><li><strong>Speed: </strong>Have to be comfortable working quickly and launching work that isn’t perfect, with little oversight.</li></ul><h3>Big companies</h3><p>At a big company, like Google, you’re likely to work in teams on a specific project. Lots of UX designers want to work at big companies with the people who developed some of the most well-known products in the world. UX teams at larger companies tend to be more compartmentalized by specialization, making it easier for you to become an expert in one particular area of UX.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*f46MxYcQzO2iQY8U" /></figure><ul><li><strong>Mentorship</strong>: A variety of experienced designers and other UXers to learn from.</li><li><strong>Growth</strong>: Lots of opportunity for growth because there are many levels of designers and management.</li><li><strong>Guidelines</strong>: Clearer guidelines to keep products uniform and on brand.</li><li><strong>Team size</strong>: More people working on one project, which means you’re better able to focus on your specific responsibilities.</li><li><strong>Specialization</strong>: Opportunity to focus on one particular area of design.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*st90Z6TGcuZGLAjw" /></figure><ul><li><strong>Team size:</strong> May feel less impactful or important as a contributor with lots of other designers on the project.</li><li><strong>Impact: </strong>May feel small at a company with so many features and products.</li><li><strong>Guidelines:</strong> Defined guidelines can be restrictive to creativity.</li></ul><h3>Design agencies</h3><p>A <strong>design agency</strong> is a one-stop-shop for visual brands, products, and services. Working at a design agency can be similar in some ways to working at a small business or startup, except you have multiple companies as your clients. Many agencies tend to work on a broad range of products, so you can explore many kinds of styles and approaches to UX design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*Y-msyxjYcUNi3HXB" /></figure><ul><li><strong>Impact: </strong>Lots of impact on projects, if you’re the only UX designer on the team.</li><li><strong>Networking:</strong> Opportunity to work with senior stakeholders, different teams, and diverse clients.</li><li><strong>Exposure:</strong> Exposure to lots of companies and industries with different clients.</li><li><strong>Resume:</strong> Potential to work with large brands and display that work in your portfolio.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*p234UlvxbDJmq2xO" /></figure><ul><li><strong>Mentorship:</strong> Lack of mentorship if you are the only UX designer on a project.</li><li><strong>Monotony:</strong> Depending on the agency, you could work only on the same type of projects.</li><li><strong>Ownership:</strong> Might not be able to work on a project from start to finish.</li><li><strong>Finished product:</strong> Products you work on might not launch, depending on client priorities.</li></ul><h3>Advertising agencies</h3><p>A lot of UX designers work at <strong>advertising agencies,</strong> which are teams of creatives hired by clients to build marketing campaigns. Sometimes called “creative technologists,” these designers work to create ads for brands using UX principles. This is a great option if you’re open to learning some interesting skills outside of a core UX design role.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*yFBxM_lPm1--o6eV" /></figure><ul><li><strong>Autonomy:</strong> Little to no middle management means more autonomy over your work.</li><li><strong>Learning:</strong> Opportunity to learn about other disciplines, like branding, marketing, and graphic design.</li><li><strong>Variety:</strong> Every project is different based on the client.</li><li><strong>Networking:</strong> Work with a bunch of different brands, clients, and teams.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*cloIg2TE3NtPCKJW" /></figure><ul><li><strong>Specialization:</strong> Wide variation in projects, so you might not be able to hone in on specific skills easily.</li><li><strong>Relevance:</strong> Work may often involve branding and marketing, and might not focus on UX design.</li></ul><h3>Freelancers</h3><p><strong>Freelancers</strong> are self-employed UX designers who are hired by clients for their independent services. Being a freelancer gives you a lot of freedom, and it’s a great way for new UX designers to gain experience in the field and add work to their portfolio.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*f8AxuY68gMW_rmnZ" /></figure><ul><li><strong>Schedule:</strong> Set your own hours since you’re self-employed.</li><li><strong>Flexibility:</strong> Can freelance while working another job or balancing competing priorities.</li><li><strong>Autonomy:</strong> Choose the work that you want to do.</li><li><strong>Experience:</strong> Build your portfolio, especially if you don’t have a full-time UX job.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*5F4MRSkjS3HsNx2a" /></figure><ul><li><strong>Structure:</strong> No one to report to, which means you have to be responsible for getting work done on time.</li><li><strong>Stability:</strong> Less stable than working for a company or agency, since work is not always guaranteed.</li><li><strong>Business:</strong> Manage the logistics of your own business, such as filing taxes, billing clients, and more.</li><li><strong>Mentorship:</strong> Lack of readily available mentors since you’re working by yourself.</li></ul><h3>Deciding where to work</h3><p>Everyone’s goals as a UX designer are different, so think about what’s most important to you when choosing a place to work. Consider questions like:</p><ul><li>Do you enjoy a lot of structure and processes, or do you like to define your own work and schedule?</li><li>Do you value working on a big team, or are you more comfortable working alone?</li><li>Do you want to focus mainly on UX design, or are you interested in broadening your skill set?</li></ul><p>Considering your career goals and how you work best will help you start to figure out the kind of company that might be the best fit for you. Good luck!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d5c2760ffba" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>