<?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 Sagar Arora on Medium]]></title>
        <description><![CDATA[Stories by Sagar Arora on Medium]]></description>
        <link>https://medium.com/@sagararora372?source=rss-74e1d4ffff94------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*hLfczllIzsMUFXeUp9-62Q.jpeg</url>
            <title>Stories by Sagar Arora on Medium</title>
            <link>https://medium.com/@sagararora372?source=rss-74e1d4ffff94------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 00:27:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sagararora372/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[Designing Systems, Not Screens: Here’s How I’m Learning to think like a Product Designer]]></title>
            <link>https://medium.com/@sagararora372/designing-systems-not-screens-heres-how-i-m-learning-to-think-like-a-product-designer-c0dd54f27a39?source=rss-74e1d4ffff94------2</link>
            <guid isPermaLink="false">https://medium.com/p/c0dd54f27a39</guid>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <dc:creator><![CDATA[Sagar Arora]]></dc:creator>
            <pubDate>Sat, 23 May 2026 12:27:37 GMT</pubDate>
            <atom:updated>2026-05-23T12:27:37.742Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C_fgbB78OB5Ot8ikTJ489w.jpeg" /></figure><p>Starting in 2026, I made a decision. I am going to build an app this year. Honestly, the idea has been sitting in my head for a year, but I never really acted upon it. Something or the other happened, or let’s just say life happened. But this year, I made a promise to myself and committed wholeheartedly to it.</p><p>For the first few months, I didn’t rush. Instead, I observed how people lived, what problems I saw around me, and what kind of app I could build that would actually help. And one idea that stuck with me was building an app for couples, as I noticed around me, couples struggle to stay connected when life gets busy. Communication gaps come in. Things get chaotic.</p><p>But here’s what mattered to me: I wasn’t building this to make money or chase metrics. This is my real product, and I knew I’d make mistakes. So I set a different bar. I wanted to solve a real problem and I found one.</p><p>So like we were discussing, couples struggle to stay connected when life gets busy. And many apps try to fix this, but they just add more noise. I wanted to build something different, with intention and simplicity. Even if it helped one couple feel more connected, for me, that would be enough.</p><p>So that’s where I started.</p><p>But what I didn’t realise was how much I had to learn on the way, not just product thinking, but about myself as a designer.</p><h3>How I Used to Design</h3><p>When I first got the idea, I knew I needed a process. So I started with an AI tool. First, I used it to research the idea itself. Like, what’s the core concept here? How do I keep it focused?</p><p>Then I moved to features. I combined what AI suggested with my own research and what I saw in other apps. What features would actually work for couples?</p><p>After that, I used AI for the Information Architecture. It helped me decide on the flow of the app, the onboarding, home page and all the other modules.</p><p>Then I used another AI tool to build a prototype based on that. I made simple prototypes, tested them, took feedback on what could be better, and went back to prototyping. By the end, I felt like I had something solid to build, so I moved into designing screens, thinking about the colors, typography, and how it all looked.</p><h3>The Things I Overlooked</h3><p>When I finished the design phase, I thought my work here was done. But I knew there were gaps. I hadn’t thought through every edge case, every state, every scenario.</p><p>Instead of spending weeks going through apps and thinking it all through manually, I decided to be smart about it. I took screenshots of the screens I’d designed, uploaded them to the AI, and walked it through my entire process. I explained what each module was about, what I was planning to do on each screen, and then I asked- What am I missing? What edge cases haven’t I considered?</p><p>That’s when things got real.</p><p>Here are some of the things I discovered.</p><ul><li><strong>The Journal Back Button — </strong>I designed the happy path, where the user writes, saves, and goes back. But what about when they don’t finish? What happens if they accidentally hit back mid-way? What happens to their unsaved work? Do they lose it? Get a warning? Auto-save to drafts? I hadn’t considered any of this.</li><li><strong>The Journal Feedback Loop — </strong>After saving a moment, I didn’t design a confirmation straightaway. The data gets saved, but the user has no idea it worked: no notification, no message, nothing. Without this feedback, they don’t trust the system.</li><li><strong>The Title Character Limit — </strong>When designing the journal list, I had no character limit set for the titles. So one title could be 400 characters, while the other could be 50. Visually, this feels apart. This would cause the list to look broken and unbalanced.</li></ul><p>Now, all of this is part of system thinking. Understanding constraints. Designing for incomplete states, not just the ideal flow. Designing not just for the action to work, but for the user to know it worked. That’s what I realised from the examples above.</p><h3>Design Beyond the Happy Path</h3><p>When I was designing, I focused on one scenario, the ideal flow. For example, with the journal feature, I thought the user opens, writes a moment, saves it and goes back. That’s it. I didn’t think through all the other paths users might take. What if they quit midway? What if they need confirmation? What if their data breaks the layout? As a UI designer, I wasn’t trained to hunt for edge cases myself, hence I didn’t. Instead, I designed the happy path and moved on. It wasn’t until I went back to AI and asked directly, “What am I missing?” Now, here I understood how much I had missed and overlooked. That’s the shift.</p><p>So as a product designer, you can’t design one scenario and assume the rest will work out. You have to think actively through the broken paths, the messy data and the real user behaviour. One has to design beyond the happy path.</p><h3>How I’m Redesigning Now</h3><p>Now, when I design, everything is different. I’m applying those lessons to every new module. Right from the character limit, feedback loops, incomplete states, all of it is thought upfront.</p><p>Earlier, I used to design the happy path, then go back and hunt for edge cases, then redesign again. It was circular.</p><p>Now, I do the research first. I use AI and my personal research to map out the edge cases and different states, create prototypes using AI to make sure the whole product is coming along right before I even touch the design.</p><p>So now, when I actually start designing screens, I know everything is already covered. The process is linear instead of going back and forth.</p><h3>To Conclude</h3><p>Now this whole process may not come out as conventional; a lot of UX and product designers work differently, like using AI only for research, building the wireframes on Figma manually, then hand them off to UI.</p><p>But I am working as both a designer and a developer, so for me, this approach is faster and works far better. I use the tools available to me. I research edge cases upfront. I build them into the prototype before I design, and it works.</p><p>Will it stay this way forever? Most probably not.</p><p>I’ll keep refining, changing and improving the process as I learn more. There’s no perfect process. But as of now, this is working for me.</p><blockquote><strong>“The shift from UI designer to product designer starts when you stop designing only for ideal outcomes.”</strong></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0dd54f27a39" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Thinking: What It Is and How It Actually Works]]></title>
            <link>https://medium.com/@sagararora372/product-thinking-what-it-is-and-how-it-actually-works-d2055c1131ae?source=rss-74e1d4ffff94------2</link>
            <guid isPermaLink="false">https://medium.com/p/d2055c1131ae</guid>
            <category><![CDATA[ux-ui-design-thinking]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[product-thinking]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ui-ux]]></category>
            <dc:creator><![CDATA[Sagar Arora]]></dc:creator>
            <pubDate>Sun, 17 May 2026 04:31:00 GMT</pubDate>
            <atom:updated>2026-05-17T04:31:00.591Z</atom:updated>
            <content:encoded><![CDATA[<p>Product design consists of a lot of segments, and product thinking is one of the major parts. In this article, we’ll cover product thinking in detail and try to understand what it means, along with an example to see how it works in practice.</p><figure><img alt="An image where people are discussing about app problem and trying to find a solution. This is the featured image for the article “Product Thinking: What It Is and How It Actually Works”" src="https://cdn-images-1.medium.com/max/1024/1*Txxp-cB6i1KxgSx3WL4KGA.jpeg" /></figure><h3>What is Product Thinking?</h3><p>Product thinking, as the name suggests, is questioning whether a product is worth building before designing it.</p><p>First you think and check if this product you are thinking about is providing any value or if it’s solving any actual user problem; if it is, then you check if it aligns with your business goals.</p><p>So if both of these are true, then it becomes something worth investing time and effort into.</p><p>Now as a UI designer, I am used to moving straight into how a feature will look and function. But when it comes to product designing, what really differs is that before we even touch the screen, we first question if the particular feature is even required in the first place.</p><p>Let’s consider this very basic example. So let’s say if there is a request to add voice input to a to-do app, now as a UI designer, my first focus will be how it should look. But from a product designer thinking perspective, the first and most important question would be: Do users even need voice input? If the answer is no, then there’s no point designing it.</p><p>However, if the answer is yes, then we move forward. This shift from directly designing to first validating is what makes product thinking different. It’s not only about building things, but also about making sure we are building the right things.​​​​​​​​​​​​​​​​</p><h3>Identifying the Problem and Finding Solutions</h3><p>Let’s start with talking about the process involved in Product thinking.</p><p>The first thing we do is identify the problem. For this let’s take a food delivery app as an example.</p><p>Now, when we first examined the data, for example Google Analytics, we noticed a lot of users were abandoning their carts at the checkout stage. So to understand why, we went beyond the numbers. We conducted surveys and spoke with users; what stood out was the frustration around the convenience fees. Seeing it appear right at the end caught users off guard.</p><p>Now, from here, we needed real solutions. One option was introducing the convenience fee earlier, so there are no surprises. Now, of course, this led us to wonder if it might deter users too soon. The second option was leaving it at the checkout, considering that people might actually continue after committing to the process. Lastly, we considered offering a discount or incentive to make the fee easier to accept.</p><p>After navigating through all these options, the next step was to try them, test and see how users respond to them.</p><h3>Testing Possible Solutions</h3><p>Now that we have found the real problem and have some potential solutions in place, it’s time to see what actually works. Testing is important because it gives us real-world feedback. There are quite a few methods, and the most popular three are usability testing, A/B testing and behavioural analysis.</p><ul><li>During usability testing, we watch how people actually use the product, seeing what trips them up and how they react.</li><li>A/B testing splits users into groups, each seeing a different version, and we compare the outcomes.</li><li>Behavioral analysis also studies and considers the patterns, like where users drop off, or how they interact.</li></ul><p>One thing worth noting is that behavioural analysis shines when you have past data. However, if it’s a brand-new feature, usability testing and A/B testing might give clear insight.</p><h3>Making Sense of the Metrics: What Worked?</h3><p>So now that we have tested our solutions, it’s about the metrics. Here is where we get the real picture.</p><p>We ran the A/B test for about two weeks. Option A, which was showing the convenience fee earlier in the process, saw cart abandonment drop by around 18% compared to the original flow. On top of that, the overall conversion rate went from 54% to 61%. That’s a pretty significant jump.</p><p>Option B, which kept the fee at checkout, didn’t move the needle much. Abandonment stayed close to where it was before. And Option C, the discount incentive, did show some improvement but it wasn’t consistent enough to rely on long term.</p><p>So what does this tell us? Users weren’t opposed to the fee itself, they were just caught off guard by it. Once we gave them that information upfront, they were more comfortable completing the order. Sometimes the fix isn’t as complicated as we think, it just takes the right data to point you in that direction.</p><h3>Conclusion</h3><p>We’ve come full circle. We started by focusing on product thinking, considered a food delivery app as an example, identified the problem, tested a few solutions and checked the metrics. In the end, product thinking guided us the whole way, ensuring we designed something that actually works, in the right way possible.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2055c1131ae" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Designer’s Guide to Product Design in 2026 (Learning Beyond UI)]]></title>
            <link>https://medium.com/@sagararora372/a-designers-guide-to-product-design-in-2026-learning-beyond-ui-d8f7778ecc3b?source=rss-74e1d4ffff94------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8f7778ecc3b</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <dc:creator><![CDATA[Sagar Arora]]></dc:creator>
            <pubDate>Fri, 15 May 2026 14:27:55 GMT</pubDate>
            <atom:updated>2026-05-15T14:27:55.761Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jEhOYaQumPp6-obNbBwUSg.jpeg" /></figure><p>When most designers start their journey, they often begin with UI design. It’s the most visible and exciting part of the process- creating screens, experimenting with layouts, choosing typography, exploring color themes, and bringing an interface to life visually. It also feels tangible, because you can see the results almost immediately.</p><p>Many of these examples we come across when designing are on platforms like Dribbble, Behance or Pinterest, as these primarily showcase the visual side of design. Due to this exposure, it is very natural to associate design primarily with how the interface actually looks.</p><p>I was no different; I started in the same way. Over the past few years, while working as a UI designer, my focus has largely been on making interfaces visually clear, structured and aesthetically refined. However, over time, I started realising that design is actually a much broader concept than just the screens we see.</p><p>Behind every screen, there are quite deeper questions that are being answered.</p><ul><li><em>why does this feature exist in the first place?</em></li><li><em>what problem does it solve?</em></li><li><em>is this the most effective solution?</em></li><li><em>what can be prioritized?</em></li><li><em>what are the tradeoffs being made?</em></li><li><em>how does this particular decision impact the business?</em></li></ul><p>So this is where product design starts becoming more visible and clear.</p><p>Although I have some understanding of UX principles and how users interact with the interfaces, I realised that product design goes beyond that. It involves not only designing the UI and improving the overall visual experience, but also understanding the product as a whole, which also involves business goals, constraints and decision making.</p><p>This article is my starting point in building a clear and deep understanding of what product design really means.</p><h3>A Simple Understanding of Product Design</h3><p>So let me first define product design in the easiest way: it is basically the process of identifying user problems and then creating solutions that are useful, usable, and valuable for both the user and the business. This goes beyond just how a screen looks. It focuses on why something needs to be built, what problem it solves, and whether it actually improves the user’s experience in a more meaningful way.</p><h3>What Product Design Includes Beyond UI?</h3><p>As a UI designer, I already have a strong foundation in visual clarity, hierarchy, layout and interaction patterns. However, product design requires expanding the scope of thinking beyond the interface. Some of the key areas that become more important include:</p><h4>Understanding the Problem</h4><p>Instead of directly jumping into designing screens, more time is spent on understanding the problem itself and considering answers to these questions.</p><ul><li><em>what is the user actually trying to achieve?</em></li><li><em>is this even a real problem or just assumed?</em></li><li><em>how frequently does this problem occur?</em></li><li><em>how important is this problem to the end user?</em></li></ul><p>Design decisions start becoming problem-driven instead of screen-driven.</p><h4>Prioritisation</h4><p>We have to understand that not everything can be built at once. Product designers often need to decide between:</p><ul><li><em>which features are most important</em></li><li><em>what should be built first</em></li><li><em>what can wait</em></li><li><em>what’s not necessary at all</em></li></ul><p>It requires balancing user needs with business goals and technical feasibility.</p><h4>Thinking in Flows, Not Screens</h4><p>UI design often and usually focuses on individual screens. Product design focuses more on the complete experience.</p><p><strong>For example</strong>:</p><p>Instead of just designing a signup screen, the main focus expands to the entire journey.</p><ul><li><em>how does the user discover the product in the first place?</em></li><li><em>what motivates them to sign up?</em></li><li><em>what happens right after signup?</em></li><li><em>where might confusion occur?</em></li><li><em>what can drop the user off?</em></li></ul><p>So all in all, the goal is actually to create a smoother overall experience.</p><h3>Keeping a Balance of User Needs and Business Goals</h3><p>A product should primarily help the user, but along with that, it also needs to support business objectives, and most product designers often think about questions like:</p><ul><li><em>how does a particular feature support business growth?</em></li><li><em>Hhow will success be measured?</em></li><li><em>what impact a decision might have on revenue or retention?</em></li><li><em>how do user value and business value connect?</em></li></ul><p>These questions together add another layer of complexity to design decisions.</p><h4>Working with Constraints and Tradeoffs</h4><p>Every product has constraints like</p><ul><li><em>limited development time</em></li><li><em>technical limitations</em></li><li><em>changing priorities</em></li><li><em>stakeholder expectations</em></li></ul><p>Because of these constraints, the ideal solution is not always possible. Product design often involves making thoughtful tradeoffs and choosing the most practical approach.</p><h3>Why Does This Feel Challenging?</h3><p>Moving from UI design to product design can be quite challenging because the scope becomes even broader. There is no single correct answer to many product decisions. Often, multiple solutions can work, and the goal is to find the most effective one based on the available information. It requires becoming more comfortable with uncertainty and also learning to make decisions with incomplete data. It also involves asking better questions instead of jumping to conclusions.</p><h3>What’s My Current Understanding?</h3><p>Right now, my understanding is that product design is about taking responsibility for the effectiveness of the product, not just the interface. It means thinking beyond visual decisions and focusing more on:</p><ul><li><em>clarity</em></li><li><em>usefulness</em></li><li><em>simplicity</em></li><li><em>Impact</em></li></ul><p>It means understanding the problem before designing the solution. This shift in thinking feels like an important step in growing as a designer. As I continue my learning about product design, I aim to better understand different concepts like identifying meaningful problems, prioritizing product decisions, evaluating whether a solution is effective, simplifying complex ideas, making better design tradeoffs and more. From here on, I plan to explore these topics in future articles in depth.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8f7778ecc3b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 ways through which I am planning to earn using graphic designing skills]]></title>
            <link>https://medium.com/@sagararora372/5-ways-through-which-i-am-planning-to-earn-using-graphic-designing-skills-2b46ac908857?source=rss-74e1d4ffff94------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b46ac908857</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[graphic-design]]></category>
            <dc:creator><![CDATA[Sagar Arora]]></dc:creator>
            <pubDate>Tue, 10 Dec 2019 17:40:58 GMT</pubDate>
            <atom:updated>2019-12-10T17:40:58.596Z</atom:updated>
            <content:encoded><![CDATA[<p>This is my first article and this article is going to be about 5 different ways which will help me earn through my graphic designing skills.</p><p>A little about myself — I have been working, as well as learning graphic design for the past 2 years approximately. The first year of which I learned Adobe Photoshop and Illustrator which I self-taught myself through YouTube. Then I went ahead and learned Adobe Indesign and Corel draw and these days I am working as a full-time designer and learning and practicing UI/UX design because I want to transition in that field now.</p><p>So coming to the main topic of today, which is the 5 ways to earn through your graphic designing skills, which I am planning to do.</p><p>1) <strong>Freelancing</strong> — My first instinct was obviously to reach out to websites like freelancer or Fiverr but what I found out about these websites is that the supply is way more than the demand. That is, for every design, there are up to 40–50 designers willing to do the job for the minimum amount of wage, which could be as low as 5–10 dollars.</p><p>Hence, I found a different route, which is, making my website. Display on the website some of my best projects, like one would do on a portfolio. Making sure that the maximum amount of people visit the website would be my priority. Figuring out how to viewers on the website is a different topic altogether which I will talk about in another article.</p><p>2) <strong>Article writing</strong> — For this, I planned to just prepare a few articles, say around three to four, just to showcase my writing skills and then to go to a website like Envato tuts + (Envato tuts pays you for writing articles on their website, but you need a portfolio to showcase your work and a few articles for them to see whether you can write or not).</p><p>But then I realized that content creation is super important and I was like I gotta do that. So I decided to create my blog and I don’t think I will be disappointed.</p><p><strong>But why? Why create your own blog?</strong></p><p>Because blogs bring you leads and establish you as an expert or an authority and definitely give your website a boost in Google rankings.</p><p>Which is why I decided to continue with my own blog. Another thing I am planning to do is contribute to other’s blogs, not to earn. It would be just to expand my reach. Letting other people know that there is a new guy in the blogging town.</p><p>3) <strong>T-shirt store</strong> -The third way through which I am planning to earn money as a graphic designer is by selling my artwork. My main plan right now is to take my artwork creations and convert them into T-shirt designs, and then with the help of websites like TeeSpring — which only requires you go hand over your designs and the website will take of the things like orders, shipping, returns, exchanges, etc.</p><p>The only thing you have to do here is to create and market/promote your design. Everything else will be taken care of by them. And the best part of it is that you get to decide what would be the price of the t-shirt, which means you get to decide the value of money, of your art. Which makes the whole idea of it unique and cool.</p><p>4) <strong>YouTube</strong> — As we all know, YouTube is one of the most popular places for individual creators who love to share stuff and want to help and teach others using their knowledge. In the past few years, I’ve been wanting to make YouTube videos because that is a really good way of earning money and spending your time.</p><p>This platform is really nice as you have the liberty to post the exact content you want to and to explain things through your videos in your language and whatever you are comfortable in, the most. So posting YouTube videos is another thing I’m planning to do to earn money as a Graphic Designer.</p><p>5) <strong>Creating my course</strong> — What I am planning to do is kind of earning through passive income, in a way. What you do is create a highly informative and educative course, whose price would be affordable which would make sure that all of the people of this society can pay for it. All you do is market and promote that course. This can be done using websites like (Skillshare or Udemy) Although I haven’t gotten too deep into this topic yet, it is on my to-do list.</p><p>So, These were my 5 ways to earn money which I am going to use and work on, as a graphic designer, although for now, I am working as a full-time employee, so I don’t get much time to venture into these projects as much as I’d like to, but I do them as and when I get the time to. I hope you liked my article and learned something through it. If you have any questions, do let me know. If you like this and found it helpful in any way, do share this with your friends.</p><p>Thank you for stopping by.</p><p>Happy Holidays :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b46ac908857" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>