<?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 Rishivaths M S on Medium]]></title>
        <description><![CDATA[Stories by Rishivaths M S on Medium]]></description>
        <link>https://medium.com/@rishivaths?source=rss-fc8048ee7ef5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*5h2rLrvolU9dfVsA_8OQ4w@2x.jpeg</url>
            <title>Stories by Rishivaths M S on Medium</title>
            <link>https://medium.com/@rishivaths?source=rss-fc8048ee7ef5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 03:51:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rishivaths/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 Design Process Is Dead — Here’s What’s Replacing It]]></title>
            <link>https://medium.com/@rishivaths/the-design-process-is-dead-heres-what-s-replacing-it-3e799627ac73?source=rss-fc8048ee7ef5------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e799627ac73</guid>
            <category><![CDATA[ai-in-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[ux-design-process]]></category>
            <dc:creator><![CDATA[Rishivaths M S]]></dc:creator>
            <pubDate>Wed, 04 Mar 2026 18:19:22 GMT</pubDate>
            <atom:updated>2026-03-04T18:19:22.915Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZCD7irjhG0x1mr-kSI6LfQ.png" /></figure><p>A few years ago, I could confidently say what “good design process” looked like.</p><ul><li>Discovery</li><li>User interviews</li><li>Diverge → converge</li><li>Wireframes</li><li>High-fidelity mocks</li><li>Iteration</li><li>Handoff</li></ul><p>It felt structured. Predictable. Professional. Today? That playbook feels… incomplete. Not because design thinking is wrong. But because the <strong>environment around it has fundamentally changed. </strong>And most designers are still pretending it hasn’t.</p><p>This is what I’m seeing replace it—in real product work, not theory.</p><h3>1. Engineering Speed Has Broken the Old Flow</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mBZCaA_h7wdAY-cV_8fHJg.png" /></figure><p>In the past, engineering bandwidth was expensive. So we spent time validating ideas before implementation. Now?</p><p>Engineers can:</p><ul><li>Spin up working prototypes in hours.</li><li>Use AI to scaffold full flows.</li><li>Experiment without asking for design mocks first.</li></ul><p>I’ve seen this happen inside teams.</p><h4>Old World Scenario</h4><p>We’d spend:</p><ul><li>2 weeks researching a feature.</li><li>1 week mocking flows.</li><li>Another week iterating before handoff.</li></ul><p>Only then would engineering begin.</p><h4>New World Scenario</h4><p>An engineer says:</p><blockquote><em>“What if we tried this?”</em></blockquote><p>By the afternoon, there’s a working version in staging.</p><p>And suddenly the conversation shifts from:</p><blockquote><em>“Should we build this?”</em></blockquote><p>to:</p><blockquote><em>“How do we make this cohesive?”</em></blockquote><p>That shift changes the designer’s role entirely.</p><p>You are no longer the gatekeeper of when something gets built.</p><p>You become the multiplier of how well it comes together.</p><h3>2. Design Work Is Splitting Into Two Modes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DaF5bxJ8Ts5ol1BfkK6UUQ.png" /></figure><p>I’ve started seeing my work fall into two very different buckets.</p><h4>Mode 1: Execution Partner</h4><p>This is where most of the energy is today. Instead of delivering perfect mocks, I:</p><ul><li>Sit with engineers while they build.</li><li>Refine interactions live.</li><li>Adjust spacing, copy, and flows in real time.</li><li>Help connect features into a coherent system.</li></ul><p>Example:</p><p>An engineer builds a new “smart assist” flow using AI. It works. But:</p><ul><li>The entry point isn’t obvious.</li><li>The empty state feels abrupt.</li><li>The system response tone feels inconsistent.</li></ul><p>Instead of redesigning from scratch, I:</p><ul><li>Add affordance cues.</li><li>Introduce guided prompts.</li><li>Align the voice with the product’s existing language.</li><li>Simplify the interaction states.</li></ul><p>It’s less about pixel ownership.<br>More about shaping experience quality under speed.</p><h4>Mode 2: Short-Horizon Vision</h4><p>The second bucket is direction-setting.</p><p>But not the old 2–5 year vision decks.</p><p>Today, vision lives in:</p><ul><li>3–6 month horizons.</li><li>Prototypes instead of presentations.</li><li>Experiments instead of polished narratives.</li></ul><p>In one project, instead of building a grand roadmap deck, I created:</p><ul><li>3 scrappy interactive concepts.</li><li>A clickable prototype exploring different mental models.</li><li>A lightweight narrative explaining trade-offs.</li></ul><p>The goal wasn’t perfection.</p><p>The goal was alignment.</p><p>When engineering can build anything quickly, someone still needs to answer:</p><blockquote><em>What are we moving toward?</em></blockquote><p>That’s where design still has enormous leverage.</p><h3>3. Mocking Is No Longer 70% of My Job</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aIQ28jGydZWfZi3KjIkM1A.png" /></figure><p>If I look at how I used to spend my time:</p><ul><li>60–70% mocking and prototyping</li><li>20% collaboration</li><li>10% coordination</li></ul><p>Now?</p><ul><li>30–40% exploration in Figma</li><li>30–40% jamming directly with engineers</li><li>A meaningful chunk in implementation-level decisions</li></ul><p>Sometimes I’m:</p><ul><li>Tweaking CSS directly.</li><li>Adjusting component states.</li><li>Reviewing pull requests for UX nuance.</li></ul><p>This didn’t exist in my workflow a few years ago.</p><p>Design is moving closer to the product itself — not just the artifact of the product.</p><h3>4. Figma Isn’t Dead — But Its Role Has Shifted</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IjhoKJn_HE9WKXJDqZZxgQ.png" /></figure><p>There’s a loud debate happening:</p><p>“Is code the new design tool?”</p><p>My take?</p><p>Code is incredible for execution.<br>But Figma is still unmatched for divergence.</p><p>When I’m exploring:</p><ul><li>8 different layouts.</li><li>Multiple mental models.</li><li>Micro-typography directions.</li><li>Interaction rhythm variations.</li></ul><p>I want a canvas.</p><p>Code today is linear.<br>Exploration requires non-linearity.</p><p>So I use:</p><ul><li>Figma for exploration.</li><li>Code for refinement.</li><li>AI for acceleration.</li></ul><p>It’s not either/or.</p><p>It’s layered.</p><h3>5. Discovery Is Happening Through Shipping</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dyRBTmmZ4ZR2fe9UNbI0dA.png" /></figure><p>With AI-powered features, something changed.</p><p>You cannot fully predict:</p><ul><li>How users will prompt.</li><li>What use cases will emerge?</li><li>Which workflows become dominant?</li></ul><p>You can’t mock nondeterminism.</p><p>So instead of over-theorizing, we:</p><ul><li>Launch early under clear “preview” framing.</li><li>Observe behavior.</li><li>Iterate aggressively.</li></ul><p>In one case, we released a feature knowing:</p><ul><li>It wasn’t fully polished.</li><li>It had rough edges.</li></ul><p>But we communicated clearly:<br>“This is early. We’re learning.”</p><p>What mattered wasn’t perfection.</p><p>What mattered was visible iteration.</p><p>Trust today is built through speed + responsiveness.</p><p>You lose trust if you ship early and go silent.<br>You gain trust if you ship early and improve weekly.</p><h3>6. The Hidden Pressure: Keeping Up</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tyqfWZtfDQoMdQgwFQfZLQ.png" /></figure><p>There’s an emotional side to this shift that no one talks about enough.</p><p>Designers feel like:</p><blockquote><em>“I can’t keep up with engineers shipping all day.”</em></blockquote><p>But here’s the truth:</p><p>Engineers are saying:</p><blockquote><em>“How do I keep up with my own agents?”</em></blockquote><p>AI didn’t just speed up output.</p><p>It increased cognitive load.</p><p>Everyone feels behind.</p><p>The solution isn’t to work faster.</p><p>It’s to:</p><ul><li>Teach principles instead of enforcing pixels.</li><li>Strengthen design systems.</li><li>Empower engineers with design literacy.</li><li>Focus on coherence over control.</li></ul><p>When I review work now, I don’t just say:<br>&quot;Move this button.”</p><p>I explain:<br>&quot;This button needs prominence because users don’t discover this action naturally.”</p><p>That scales.</p><h3>7. Craft Is Not Dead. It’s Moving.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b7EcoMhe66aj_XlmjilLVw.png" /></figure><p>Some designers fear this shift means craft will disappear.</p><p>I don’t think that’s true.</p><p>Craft just moved.</p><p>It moved from:</p><ul><li>Perfect mocks to System thinking under velocity.</li></ul><p>It moved from:</p><ul><li>Polished artifacts to Cohesive product ecosystems.</li></ul><p>It moved from:</p><ul><li>“Trust the process&quot; to “Respond to reality”</li></ul><h3>Where I Think This Is Going</h3><p>The designer of the next five years will not be:</p><ul><li>A Figma specialist.</li><li>A process defender.</li><li>A gatekeeper.</li></ul><p>They will be:</p><ul><li>A direction-setter.</li><li>A velocity enabler.</li><li>A coherence architect.</li><li>A principle teacher.</li><li>A systems thinker.</li></ul><p>The craft still matters.</p><p>But momentum matters more.</p><p>And if we don’t evolve with the speed of engineering, we risk becoming decorative instead of foundational.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e799627ac73" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Built a Fake User. It Made My Designs More Real]]></title>
            <link>https://medium.com/@rishivaths/i-built-a-fake-user-it-made-my-designs-more-real-65d5639b9c36?source=rss-fc8048ee7ef5------2</link>
            <guid isPermaLink="false">https://medium.com/p/65d5639b9c36</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[user-personas]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Rishivaths M S]]></dc:creator>
            <pubDate>Thu, 18 Dec 2025 08:23:10 GMT</pubDate>
            <atom:updated>2025-12-18T08:23:10.603Z</atom:updated>
            <content:encoded><![CDATA[<p>I built a user persona GPT in an afternoon, and it changed how I validate design ideas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SzgzP9IJ4AsQD7m2FwzMUA.png" /></figure><p>A few months ago, I caught myself doing something I’ve done many times before. I was designing a feature, fairly confident about it, and telling myself:</p><blockquote>“Users will definitely understand this.”</blockquote><p>Deep down, I knew this confidence was built on assumptions.</p><p>User interviews were scheduled for later. Stakeholders wanted quick answers now. And I needed a way to <strong>pressure-test my thinking</strong> before things went too far. That’s when I tried something simple:</p><p><strong>I created a User Persona GPT.</strong></p><p>Not a complex AI model.<br>Not a research replacement.<br>Just a simulated user I could talk to.</p><p>What surprised me wasn’t the accuracy—it was how <strong>quickly it exposed my blind spots</strong>.</p><h3>What Is a User Persona GPT (In Simple Terms)?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ThoxvEEhYrbJEWoGCqaymg.png" /></figure><p>A user persona GPT is basically this: You describe a user so clearly that GPT starts <strong>thinking, reacting, and responding like that user</strong>.</p><p>Instead of asking:</p><blockquote><em>“What would the user think?”</em></blockquote><p>You ask:</p><blockquote><em>“Hey, user — what do you think about this?”</em></blockquote><p>It feels like having a <strong>stand-in user</strong> sitting next to you while you design.</p><h3>Why I Felt the Need for It</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5ysbCok-vtVtvxaTaIW1tQ.png" /></figure><p>As designers, we often work in this messy middle:</p><ul><li>Early ideas</li><li>Half-formed hypotheses</li><li>Incomplete data</li><li>Strong opinions in the room</li></ul><p>We still need to make decisions.</p><p>A persona GPT helps answer questions like</p><ul><li>“Is this confusing, or am I overthinking?”</li><li>“Would this actually solve their problem?”</li><li>“What would make them drop off?”</li></ul><p>It doesn’t give perfect answers.<br>But it gives <strong>direction</strong>—and that’s incredibly useful early on.</p><h3>How Simple It Actually Is to Set One Up</h3><p>You don’t need code.<br> You don’t need to train a model.</p><p>You just need <strong>clarity</strong>.</p><h4>Step 1: Describe the User Like You’re Explaining Them to a Teammate</h4><p>Here’s an example prompt I used:</p><h4>🔹 Sample Persona Setup Prompt</h4><pre>You are a 34-year-old working professional living in a metro city.<br>You have a full-time job and limited time.<br>You are comfortable using apps but get easily frustrated by long flows.<br>You value speed, clarity, and transparency.<br>You don’t like reading too much text and prefer clear actions.<br><br>Respond like a real user.<br>Be honest, sometimes impatient.<br>If something is confusing, say so.<br>Do not suggest design solutions unless I ask.</pre><p>That’s it.</p><p>No fancy language.<br> Just human context.</p><h3>The First Time I Tested a Hypothesis</h3><p>I had an assumption:</p><blockquote><em>“This new onboarding flow is simple enough.”</em></blockquote><p>So I showed the flow (step by step) to the persona GPT and asked:</p><h4>🔹 Sample Validation Prompt</h4><pre>You are seeing this app for the first time.<br>Here’s the onboarding flow:<br>1. Sign up<br>2. Choose preferences<br>3. Add payment<br>4. Confirm<br><br>What are you thinking at each step?<br>Where do you feel unsure or annoyed?</pre><p>The response surprised me.</p><p>The persona wasn’t confused by the flow — <br> it was <strong>annoyed by the timing of payment</strong>.</p><p>That wasn’t something I had questioned before.</p><p>That one insight changed the order of steps in the flow.</p><h3>Using It to Get Early User Insights</h3><p>Once set up, the persona GPT became my go-to for exploration.</p><p>I used it to ask things like:</p><h4>🔹 Insight Exploration Prompts</h4><pre>What would make you trust this app?</pre><pre>What feels unnecessary here?</pre><pre>If you had only 30 seconds, what would you focus on?</pre><pre>What would make you abandon this flow halfway?</pre><p>The answers weren’t “facts” — <br> but they revealed <strong>emotional reactions</strong>, which are often harder to see early.</p><h3>Iteration Became Faster (and Less Risky)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/796/1*7zwFpJRl-BbdDxJjAqarKQ.jpeg" /></figure><p>Instead of waiting for research rounds:</p><ul><li>I tested an idea</li><li>Adjusted assumptions</li><li>Tested again</li><li>Then took the refined version to real users</li></ul><p>This meant:</p><ul><li>Better interview questions</li><li>More focused usability tests</li><li>Fewer surprises later</li></ul><p>The persona GPT didn’t replace research — <br> it made my research <strong>more intentional</strong>.</p><h3>The Most Important Step: Reality Check with Real Users</h3><p>After real user interviews, I did something critical.</p><p>I compared:</p><p><strong>What real users said vs What the persona GPT predicted?</strong></p><p>Sometimes it matched closely. Sometimes it was completely off. That gap was gold. I updated the persona prompt based on real insights.</p><h4>🔹 Example Adjustment</h4><p>Before:</p><blockquote><em>“User doesn’t mind reading instructions.”</em></blockquote><p>After interviews:</p><blockquote><em>“User skips instructions and relies on visual cues.”</em></blockquote><p>The persona got better.<br> More realistic.<br> More useful.</p><h3>What This Tool Is—and What It Is Not</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/794/1*IsBjBmiAMN4V1LUqiBIViw.jpeg" /></figure><p>Let’s be clear.</p><p>This is not:</p><ul><li>A replacement for user research</li><li>A source of truth</li><li>An excuse to skip interviews</li></ul><p>This is:</p><ul><li>A thinking partner</li><li>A hypothesis validator</li><li>A fast feedback loop</li></ul><p>Used responsibly, it helps you design with <strong>more empathy, not less</strong>.</p><h3>Final Thoughts</h3><p>I didn’t build a complex AI system. I built a <strong>simple persona GPT</strong>.</p><p>And that small step:</p><ul><li>Saved time</li><li>Reduced assumptions</li><li>Improved decision-making</li><li>Helped me understand users earlier and better</li></ul><p>Sometimes, the most powerful tools aren’t the fanciest ones. They’re the ones that help you ask better questions — before it’s too late.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65d5639b9c36" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unlocking Product Variants: A Merchant’s Journey]]></title>
            <link>https://medium.com/@rishivaths/unlocking-product-variants-a-merchants-journey-2400ea0f6980?source=rss-fc8048ee7ef5------2</link>
            <guid isPermaLink="false">https://medium.com/p/2400ea0f6980</guid>
            <category><![CDATA[b2b]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-case-study]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Rishivaths M S]]></dc:creator>
            <pubDate>Mon, 24 Mar 2025 17:41:19 GMT</pubDate>
            <atom:updated>2025-03-24T17:41:19.151Z</atom:updated>
            <content:encoded><![CDATA[<p>A B2B UX case study in which I solved a discovery challenge for merchants. Following my switch to the B2B world, this was one of the most exciting and challenging problems to work on. Let’s see how this was solved.</p><h3>About Pincode Business</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*ZiEnITF4BEmipBO7LWwhgg@2x.png" /></figure><p>Pincode business is designed for the <strong>merchants</strong>, and empowers them to <strong>handle orders</strong> efficiently directly from the merchant’s mobile devices. Every employee within the store can log in and contribute to managing orders, ensuring a smooth operational flow.</p><p>I was assigned to solve this problem, and as a <strong>solo UX designer,</strong> I crafted the entire flow, did a bit of research and field visit, user testing, synced with the product team, backend engineers, and frontend engineers, and shipped it with the prototype.</p><h3>Overview</h3><h4>Description of the problem</h4><p>Our merchants struggle to discover the variants of a product (e.g., 500 g, 1 kg, 2 kgs) while managing their inventory or listing items online. This results in missed sales opportunities, reduced customer satisfaction, and inventory inaccuracies.</p><h4>Project goal</h4><blockquote>Help merchants discover variants of a product</blockquote><p>Design to simplify how merchants discover and manage item variants, ensuring a seamless and accurate process that minimises time and effort while maximising sales opportunities.</p><h3>Setting out to solve</h3><h4>Analysing the current experience and why it is not working?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*2a3WjZvRvkN2aLDSVzTckg@2x.png" /></figure><p>I was looking at the existing designs and was analysing what could have gone wrong. I synced with the product manager and found out merchants struggled with identifying all potential variants and often relied on manual processes or incomplete vendor catalogues. Sometimes the search is not accurate, and they have to browse further, spending a lot of time. The product manager highlighted the need for a scalable solution that could work across multiple product categories.</p><h4>Defining the challenge with a field visit</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*dbe5gXQOFUhN_crnUTkd-Q@2x.jpeg" /><figcaption>Images captured during the field visit at a supermarket</figcaption></figure><p>I visited the physical stores, including small grocery shops and large retail chains, to observe how merchants behave and how they discover and manage variants. I sought ideas to club store behaviours to the app that could make the experience easy for them. I noticed these key behaviours of the merchants and what happens in the supermarket:</p><h4>1. The merchants environment is very busy</h4><p>Their days are filled with multitasking, quick decision-making, and customer interactions, all aimed at ensuring the supermarket runs like a well-oiled machine. This constant busyness reflects their dedication to keeping the store stocked, appealing, and welcoming for shoppers.</p><h4>2. They user scanner to add items to inventory</h4><p>Scanners play a crucial role in supermarket operations, especially in inventory management. These devices streamline the process of adding items to the store’s inventory system, ensuring efficiency, accuracy, and real-time data updates.</p><h4>3. All variants of an item is placed in the same rack</h4><p>One common strategy is placing all variants of a product on the same rack or in the same section. This approach benefits both customers and store management by improving accessibility, enhancing the shopping experience, and streamlining inventory control.</p><h3>Possible solutions</h3><p>Based on the field study and some discussions with the product, I came up with the <strong>How might we</strong> approach this problem? Here are the statements:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*SEYfpgMqtCtQ3TzRDYlusg@2x.png" /></figure><h3>The solution</h3><h4>1. Introduce scan feature</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*Qln6PTwPnGIDB7BmuGzjvg.gif" /></figure><p>As we know that the merchants mostly scan in their system to add products to their inventory, I aligned this to the product, and the product team was happy to introduce this functionality to our app. Because every product in the store has a unique barcode, the scanner can quickly retrieve product information from the inventory database, including name, price, and quantity, by reading the barcode.</p><h4>2. Link all variants</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*hE9dsJ8HqqwMiLtESMr2pA.gif" /></figure><p>It is easier for merchants to navigate when items are logically grouped or linked by variants to a base item. This makes it easier for the merchant to keep their products visible and provide them with fast access to add or modify variants.</p><h3>Over coming backend challenges</h3><h4>Getting a shared understanding with the engineering team</h4><p>We know we want to add these features, but a significant backend implementation is required, so I had to persuade them of this. By addressing scalability, accuracy, and user needs, I was able to persuade the backend engineers that the system guarantees a smooth experience for merchants. This innovation will improve the app’s overall functionality in addition to better inventory management. I made a case rooted in user needs by demonstrating the value of the scan feature, which can allow users to quickly access product details, view all variants, and make informed decisions. I also explained the benefits of how linking variants to a base product simplifies navigation, enhances search functionality, and ensures consistency in product data</p><h3>Designs</h3><h4>1. Scan feature</h4><p>As the backend prepared to deploy this feature, I began working on the designs and prototype. First, I looked at the scan screen and how the process of finding the items would start.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/796/1*TalaAUhXqkzQR79tNspT4A.gif" /></figure><h4>2. Linking all variants on the PDP</h4><p>I started drawing some sketches and looked into how all the variants could be included in the product details page. Here are some of the sketches I did during the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*-mSF2xtyZYz7NaGrK4UNDA@2x.jpeg" /><figcaption>Sketches created for this project</figcaption></figure><p>I started exploring the designs on Figma after finishing the sketches. I came up with three final versions that I thought would work well for connecting all of the variants to a single product. To get some input, I showed them around to some stakeholders and my peers. I then listed some pros and cons to decide which would be the best route to go forward.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*NTW1cbLpnVK8cHQ7uSTv1A@2x.jpeg" /></figure><h4>The decision behind iteration 3</h4><p>Since the third iteration checked off every HMW statement, I chose to use it in this case. Additionally, it largely resolves the issue by connecting all variants and their actions with minimal interactions. This design is scalable for upcoming enhancements and has future potential.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*AE8CTq1qtg-EEqG1LxlUnA@2x.jpeg" /></figure><h4>3. Redesigning the view item details page</h4><p>I redesigned the page to a section with a dropdown feature. Instead of taking the user to another page and back again, this allows them to view details within the page more quickly. By examining the data, I restructured the page so that the least used action is at the bottom.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/796/1*O931Ceikw-Rs8PpbFLLWkA.gif" /></figure><h4>4. And there is some more!</h4><p>How I treated the edge case, error case, and multi-level variant screens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*mAj40wOPYQ7Jj9P-cCzbUw@2x.jpeg" /></figure><h3>User testing &amp; impact</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*IcGPoomuIYzAEfW0fR4vJQ@2x.jpeg" /></figure><h4>Testing with the merchants</h4><p>I developed a prototype and tested out the experience with merchants. <strong>Eight out of ten merchants</strong> were pleased with the new flow after noticing the variants tab. They expressed their increased confidence in managing large inventories.</p><h4>Quantitative Results</h4><p>We took this feature live and found that sellers were adding <strong>2x products </strong>now on their live catalogue. A <strong>60% time reduction</strong> in finding and adding variants was noticed after measuring some feedback. This problem was largely resolved by the variants tab. We observed that connecting the variations helped to eliminate duplicates of items discovered in the inventory.</p><h3>Conclusion</h3><p>The redesigned variant discovery experience significantly enhanced merchants’ workflows by combining user-friendly design with powerful features. Future enhancements could include offer creation, batch import, and supporting multilingual merchants.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2400ea0f6980" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Shifted from Visual Design to Product Design]]></title>
            <link>https://medium.com/@rishivaths/how-i-shifted-from-visual-design-to-product-design-3db2ce8f0ded?source=rss-fc8048ee7ef5------2</link>
            <guid isPermaLink="false">https://medium.com/p/3db2ce8f0ded</guid>
            <category><![CDATA[ux-design-process]]></category>
            <category><![CDATA[transitioning]]></category>
            <category><![CDATA[visual-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Rishivaths M S]]></dc:creator>
            <pubDate>Sun, 01 Dec 2024 11:11:59 GMT</pubDate>
            <atom:updated>2024-12-01T11:11:59.757Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Turl0WLatzhmyyq2" /><figcaption>Photo by <a href="https://unsplash.com/@startaeteam?utm_source=medium&amp;utm_medium=referral">Startaê Team</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The transition from visual design to product design is a journey that requires adaptation, learning, and unlearning. As someone who was initially rooted in the world of visual design, I found this shift to be both challenging and rewarding. It wasn’t just about changing the tools I used or adopting a new job title; it was about shifting my mindset, developing new skills, and thinking about design in a more holistic way.</p><p>I’ll share my personal experience and the steps I took to make the transition from visual designer to product designer, offering some insights for those considering the same path.</p><h3>The Foundation of Visual Design</h3><p>As a visual designer, my primary focus was on the aesthetic elements of a project. I was responsible for creating polished interfaces, ensuring that my design composition with elements like color, typography, and layout were visually appealing and aligned with the brand’s identity. My work revolved around making designs look good and ensuring they were user-friendly at a surface level where I was looking for good CTRs.</p><p>Visual design requires an eye for detail and a deep understanding of design principles such as hierarchy, alignment, and composition. I worked closely with business and marketing teams but often without a deep connection to the broader product or its overall user experience (UX).</p><h3>The Realization: There’s More to Design Than Aesthetics</h3><p>The first turning point came when I started working more closely with product designers who were involved in the entire product lifecycle — from ideation and research to wireframing and prototyping. While my work focused largely on the final visual details, product designers were concerned with how the design solved real-world problems, met user needs, and fit into the broader product strategy.</p><p>What struck me was how product designers approached design holistically. They didn’t just consider how something looked; they considered how it worked. This shift from focusing purely on visual aesthetics to thinking about the function and usability of a product was eye-opening for me.</p><p>I began to realize that to truly create meaningful user experiences, I needed to understand more than just the visual elements. I needed to dive into user research, learn about usability principles, and understand the context in which users interacted with the product. I could no longer think of design as a standalone process; it needed to be embedded within the entire product development cycle.</p><h3>The Opportunity</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BfWmESilvcsJD02O" /><figcaption>Photo by <a href="https://unsplash.com/@son_of_media?utm_source=medium&amp;utm_medium=referral">Dylan McLeod</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>One day I got a call from my boss(Covid WFH days) and asked if I could do anything for the product design team for a task because they were running low on bandwidth. The first thing that came to mind was this quote:</p><blockquote>“For years, kids have been asking me what’s the greatest superpower. I always say luck. If you’re lucky, everything works. I’ve been lucky.” — Stan Lee</blockquote><p>I said “yes” right away, and we got on a call. It was with one of the product design leaders and he briefed me to design a few widgets for the platform that they are designing. I got access to Figma and I started exploring some designs for it. The team was happy with my swiftexecution and some of my widgets were developed and went live on the app.</p><h3>The Transition Process</h3><p>The process of creating the widgets was so much fun that I decided it was time to consider my interests in product design. Shifting from visual design to product design meant I had to expand my skill set beyond color palettes and typography. Here are some of the key areas where I had to grow:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VSZsWMdbc-wRDY3a" /><figcaption>Photo by <a href="https://unsplash.com/@amayli?utm_source=medium&amp;utm_medium=referral">Amélie Mourichon</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4><strong>1. Learning the Fundamentals of Product Design</strong></h4><ul><li><strong>Self-Education:</strong> I immersed myself in blogs, books, and online courses. Resources like <em>Designing for Interaction</em> by Dan Saffer and platforms like Coursera and Interaction Design Foundation became my go-to.</li><li><strong>Understanding User-Centered Design:</strong> I learned how to conduct user research, create personas, and map user journeys. These were eye-opening experiences as they shifted my focus from visuals to functionality.</li><li><strong>Information Architecture (IA):</strong> I needed to understand how users navigated a product and how to structure information so that users could easily find what they were looking for. This meant learning about flowcharts, site maps, and user journeys, which were new to me but crucial for designing intuitive products.</li><li><strong>Product Strategy:</strong> I needed to think more broadly about the product’s goals and the market context. This required understanding how my design choices fit into the larger product strategy and how design can contribute to achieving business objectives.</li></ul><h4><strong>2. Expanding My Toolset</strong></h4><ul><li>As a visual designer, tools like Photoshop and Illustrator were my staples. Transitioning to product design meant mastering tools like Figma, Sketch, and prototyping platforms like InVision and Adobe XD.</li><li>I also explored tools for wireframing (Balsamiq) and learned basic principles of interaction design.</li></ul><h4><strong>3. Hands-On Experience</strong></h4><ul><li>I volunteered to take on small UX tasks in existing projects, like creating wireframes or testing prototypes.</li><li>Collaborating with product managers and developers taught me how to consider technical constraints and business goals.</li></ul><h4><strong>4. Adopting a Problem-Solving Mindset</strong></h4><p>Visual design often begins with a creative brief, but product design starts with a problem. I began approaching design challenges by asking:</p><ul><li>Who is the user?</li><li>What is their pain point?</li><li>How can we solve it effectively?</li></ul><h4><strong>5. Mentorship and Collaboration</strong></h4><p>One of the most valuable aspects of my transition was connecting with experienced product designers who mentored me. They provided insights into the day-to-day responsibilities of a product designer, shared resources, and gave me feedback on my work. I also collaborated with product designers on various projects, which helped me understand the nuances of their workflow.</p><h3>Challenges I Faced</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5fH5m2CODqXNaiba" /><figcaption>Photo by <a href="https://unsplash.com/@tateisimikito?utm_source=medium&amp;utm_medium=referral">Jukan Tateisi</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><ol><li><strong>Letting Go of Perfectionism: </strong>In visual design, perfection is paramount. In product design, speed and iterative improvement matter more. It was challenging to embrace the idea of shipping an MVP (Minimum Viable Product) and refining it later.</li><li><strong>Learning to Collaborate Closely: </strong>Product design involves constant collaboration with stakeholders, developers, and users. Shifting from a solitary design process to a team-oriented approach took time.</li><li><strong>Navigating Ambiguity: </strong>Unlike visual design, product design doesn’t always start with a clear brief. Understanding how to frame problems and ask the right questions was a skill I had to develop.</li></ol><h3>What Helped Me Thrive in Product Design</h3><h4><strong>1. Empathy:</strong></h4><p>My background in visual design gave me a strong sense of empathy for users. This translated well into creating intuitive, user-friendly experiences.</p><h4><strong>2. Attention to Detail:</strong></h4><p>My visual design roots made me keenly aware of small details that elevate a product, like micro-interactions and accessibility considerations.</p><h4><strong>3. Continuous Learning:</strong></h4><p>The world of product design is vast, and I remain committed to learning. Participating in design meetups and reading case studies helps me stay updated.</p><h3>The Outcome: Becoming a Product Designer</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VZmss86jSxe-TE8n" /><figcaption>Photo by <a href="https://unsplash.com/@dtravisphd?utm_source=medium&amp;utm_medium=referral">David Travis</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>After several months of learning and hands-on experience, I eventually landed my first role as a product designer internally within the org. Today, as a product designer, I feel more fulfilled. I’m no longer just creating interfaces; I’m shaping user experiences and solving meaningful problems. My journey from visual design to product design wasn’t linear, but it was transformative.</p><p>What I enjoy most about product design is that it’s not just about how something looks but how it works. The satisfaction of seeing a product evolve from a rough idea to a polished, user-friendly experience is incredibly fulfilling.</p><h3>Final Thoughts: Why It Was Worth It</h3><p>Shifting from visual design to product design has been one of the best decisions I’ve made in my career. It allowed me to grow as a designer and expand my impact on the products I work on. I learned to think more holistically and became a better communicator, collaborator, and problem solver.</p><p>If you’re considering making the same transition, my advice is simple: embrace the learning curve, stay curious, and don’t be afraid to step out of your comfort zone. Product design is a multidisciplinary field that combines creativity with empathy, strategy with execution. The skills you develop along the way will not only make you a better designer but will also give you the ability to shape products that truly resonate with users. With curiosity, persistence, and a willingness to learn, you can broaden your impact and create designs that are not only beautiful but also purposeful.</p><h4>Additional Resources for Aspiring Product Designers</h4><p><strong>Books:</strong></p><ul><li><em>Don’t Make Me Think</em> by Steve Krug</li><li><em>Lean UX</em> by Jeff Gothelf</li><li><em>The Design of Everyday Things</em> by Don Norman</li></ul><p><strong>Courses:</strong></p><ul><li>The Foundation of UX design by Google</li><li>Interaction Design Foundation (IDF)</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3db2ce8f0ded" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>