<?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 Bindu Dayanand on Medium]]></title>
        <description><![CDATA[Stories by Bindu Dayanand on Medium]]></description>
        <link>https://medium.com/@bindu.dayanand?source=rss-b181ae0ad97a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*KWPf2ORFnyn-N778ieBGmw.png</url>
            <title>Stories by Bindu Dayanand on Medium</title>
            <link>https://medium.com/@bindu.dayanand?source=rss-b181ae0ad97a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 12:50:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bindu.dayanand/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 Hidden Friction in a “Change Plan” Journey]]></title>
            <link>https://medium.com/@bindu.dayanand/the-hidden-friction-in-a-change-plan-journey-c2ffd996acae?source=rss-b181ae0ad97a------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2ffd996acae</guid>
            <category><![CDATA[mobile-app-design]]></category>
            <category><![CDATA[design-friction]]></category>
            <category><![CDATA[user-flow]]></category>
            <category><![CDATA[user-journey]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Bindu Dayanand]]></dc:creator>
            <pubDate>Sun, 12 Jul 2026 15:25:25 GMT</pubDate>
            <atom:updated>2026-07-12T15:25:25.121Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pyz9M0-vNZFmgGEWdn5D9Q.png" /></figure><blockquote><em>“Sometimes the biggest UX problems aren’t in the main flow. They’re in what happens when users change their minds.”</em></blockquote><p>When designing a <strong>Change Plan </strong>feature for a sports management platform, the primary user journey seemed straightforward.</p><p>A student could:</p><ol><li>Navigate to <strong>My Plan</strong>.</li><li>Tap <strong>Change Plan</strong>.</li><li>Browse available plans.</li><li>Select an effective date.</li><li>Submit the request.</li></ol><p>The request would then appear in the admin portal, where an administrator could review it, update the student’s package, and even change their assigned batch if necessary.</p><p>Everything worked.</p><p>Or so I thought.</p><h3>The Edge Case That Changed Everything</h3><p>While reviewing the complete journey, I noticed an important business rule:</p><p><strong>A student can submit only one plan change request per month.</strong></p><p>That meant if a student accidentally chose the wrong package or changed their mind before the request was approved, they couldn’t simply submit another request.</p><p>Their only option was to <strong>withdraw the existing request</strong>.</p><p>On paper, this solved the problem.</p><p>But from the user’s perspective, it introduced a new one.</p><h3>The Missing Piece</h3><p>Imagine this scenario.</p><p>You request to upgrade from a one-month package to a three-month package. A few minutes later, you realize you selected the wrong plan. You withdraw the request.</p><p>And then…It disappears. There is no confirmation.</p><p>No history. No indication that a request was ever made.</p><p>The screen simply returns to its original state.</p><p>As a user, questions immediately arise:</p><ul><li><em>Was my withdrawal successful?</em></li><li><em>Did my request actually get cancelled?</em></li><li><em>Can I submit another request now?</em></li></ul><p>The system knew the answer.</p><p>The user didn’t.</p><h3>The Solution</h3><p>Instead of treating withdrawn requests as deleted, I introduced a lightweight <strong>Request History</strong> page.</p><p>From the <strong>Change Plan</strong> screen, users can now access their previous requests through a simple text button.</p><p>Each request displays its current status, such as:</p><ul><li>Pending</li><li>Approved</li><li>Rejected</li><li>Withdrawn</li></ul><p>Now, withdrawing a request no longer feels like deleting it.</p><p>It becomes another state in the request lifecycle.</p><p>Users gain visibility into what happened and confidence that the system has recorded their action.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dSIJGFMvHu2JAYOb-X4Bqg.png" /><figcaption>The redesigned flow introduces transparency into the plan change journey by allowing students to submit, withdraw, and revisit past requests instead of losing track of them after withdrawal.</figcaption></figure><h3>Why a Separate Page?</h3><p>One option was to show previous requests directly on the Change Plan screen.</p><p>I decided against it.</p><p>The primary goal of that screen is to help users submit a new request.</p><p>Adding historical information would compete for attention and increase visual complexity.</p><p>Instead, a secondary text action keeps the main flow focused while making request history available whenever users need it.</p><h3>What I Learned</h3><p>This project reminded me that successful UX isn’t only about helping users to complete tasks.</p><p>It’s also about helping them understand what happened after they completed them.</p><p>Sometimes, the most valuable design decisions come from asking one simple question:</p><blockquote><strong><em>“What happens after this?”</em></strong></blockquote><p>In this case, answering that question transformed a disappearing action into a transparent, trustworthy experience.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2ffd996acae" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing a Smarter Batch Scheduling Experience for Sports Academies]]></title>
            <link>https://medium.com/@bindu.dayanand/designing-a-smarter-batch-scheduling-experience-for-sports-academies-fb41ef0d4332?source=rss-b181ae0ad97a------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb41ef0d4332</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-interface]]></category>
            <category><![CDATA[product-thinking]]></category>
            <category><![CDATA[sports-management]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <dc:creator><![CDATA[Bindu Dayanand]]></dc:creator>
            <pubDate>Thu, 02 Jul 2026 15:24:35 GMT</pubDate>
            <atom:updated>2026-07-02T16:00:18.905Z</atom:updated>
            <content:encoded><![CDATA[<p>One of the features I recently worked on was improving how academy admins create and manage training batches in a sports management platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I3EhQzAwmWkKtjj5LuJC0Q.png" /></figure><p>The platform allows admins to:</p><ul><li>Create batches</li><li>Assign coaches</li><li>Configure weekly training schedules</li><li>Edit or delete existing time slots</li><li>Manage schedules across multiple centres</li></ul><p>On paper, the workflow was complete. It supported all CRUD (Create, Read, Update, Delete) operations.</p><p>But while reviewing the scheduling flow, one thing became obvious:<em> The experience involved a lot of repetitive work.</em></p><h3>The Existing Workflow</h3><p>Every batch required admins to configure training slots for each day of the week.</p><p>Let’s say a cricket academy runs practice from <strong>6:00 PM to 7:30 PM</strong> every weekday.</p><p>To create this schedule, the admin had to:</p><ul><li>Select Monday</li><li>Add the time slot</li><li>Repeat the same steps for Tuesday</li><li>Repeat again for Wednesday</li><li>Next, Thursday</li><li>And finally, for Friday</li></ul><p>The system worked exactly as intended.</p><p>The experience, however, <em>didn’t</em>.</p><p>The product was making users repeat the same action multiple times simply because the data belonged to different rows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/412/1*_007Yu6uKiXRVTsTCgvnaQ.png" /><figcaption>Existing flow: Every batch required admins to configure training slots for each day of the week.</figcaption></figure><h3>Understanding the Real Problem</h3><p>Initially, it seemed like a straightforward “copy to all days” feature.</p><p>But after understanding how sports academies actually operate, another requirement emerged.</p><p>Not every centre follows the same schedule.</p><p>For example:</p><ul><li>Centre A might run evening coaching on weekdays.</li><li>Centre B may only conduct weekend sessions.</li><li>Another centre could have different timings altogether.</li></ul><p>If we only allowed copying time slots across days, <em>we’d still force admins to recreate schedules for each centre.</em></p><p>The real problem wasn’t just repetitive scheduling.</p><p><em>It was repetitive scheduling across both </em><strong><em>days</em></strong><em> and </em><strong><em>centres</em></strong><em>.</em></p><h3>Designing the Solution</h3><p>The goal was to <em>reduce effort</em> without taking away flexibility.</p><h3>1. Copy Time Slots Across Selected Days</h3><p>Instead of creating the same slot multiple times, admins can now create it once and apply it to any combination of days.</p><p>Whether it’s weekdays, weekends, or a custom selection, the interaction happens in <strong>a single step.</strong></p><p>This removes repetitive input while keeping users in control.</p><h3>2. Centre-Level Assignment</h3><p>The second improvement was introducing centre-specific tagging.</p><p>Each time slot can now be assigned to one or more centres during creation or editing.</p><p>This means:</p><ul><li>Different centres can have different schedules.</li><li>A single schedule can be reused wherever applicable.</li><li>Administrators no longer need to duplicate the same configuration for every location.</li></ul><h3>Design Principles</h3><p>A few principles guided the final solution:</p><ul><li>Reduce repetitive interactions.</li><li>Preserve flexibility for different scheduling patterns.</li><li>Keep the interface simple despite supporting more complex configurations.</li><li>Design for scalability as academies expand to multiple centres.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/654/1*rgyqaFn5roZclSABE2jcVw.png" /><figcaption>Step 1: Admin selects a day, add time slots and selects centres.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/657/1*xtOzElweSK2C0BRoOR9mZQ.png" /><figcaption>Step 2: Admin can now configure the days that the time slots have to be copied to and click ‘Copy’.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/654/1*6ebXppqefKMa9XgfnM-TSQ.png" /><figcaption>The time slots will be copied for the selected days. The admin can now click ‘Save’ to confirm the time slots.</figcaption></figure><h3>The Outcome</h3><p>The final experience transformed scheduling from a repetitive administrative task into a much faster workflow.</p><p>Instead of creating identical entries over and over again, admins can now:</p><ul><li>Create a time slot once.</li><li>Apply it to selected days.</li><li>Assign it to relevant centres.</li><li>Edit or delete schedules whenever required without rebuilding them from scratch.</li></ul><p>This feature reminded me that good UX isn’t always about introducing new functionality. Sometimes<em> it’s about recognizing repetitive behaviour,</em> understanding why it exists, and designing an interaction that lets users accomplish the same goal with far less effort.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb41ef0d4332" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Growing Up with Music Made Me a Better Designer]]></title>
            <link>https://medium.com/@bindu.dayanand/how-growing-up-with-music-made-me-a-better-designer-f44c48b43674?source=rss-b181ae0ad97a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f44c48b43674</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[empathy]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[listening-skills]]></category>
            <category><![CDATA[music]]></category>
            <dc:creator><![CDATA[Bindu Dayanand]]></dc:creator>
            <pubDate>Fri, 27 Jun 2025 13:14:01 GMT</pubDate>
            <atom:updated>2025-08-01T12:33:53.822Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PY51_YcFfu2tgdoG" /><figcaption>Photo by <a href="https://unsplash.com/@mohammadmetri?utm_source=medium&amp;utm_medium=referral">Mohammad Metri</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I grew up in a home where silence was rare and song was constant. My mornings often began with the sound of my mother singing bhajans, soft and serene. On Sundays, retro film songs would drift through the house from the radio, setting the mood before the day even began.</p><p>From childhood till now, music has never been far from me. Whether it was the background score to a routine day or a tune stuck in my head all afternoon — there’s always been a song running somewhere, quietly shaping the rhythm of life.</p><p>Even as a listener, though, music taught me to pay attention. Not just to sound, but to feeling. Over time, I found myself tuning into the finer details — how the <em>raaga </em>sets the mood of a song, how a note curls ever so slightly to evoke emotion, how a composer weaves a melody through words and silences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Il2LoAfHEmnYXUxl" /><figcaption>Photo by <a href="https://unsplash.com/@aviguru?utm_source=medium&amp;utm_medium=referral">Avinash Guruvayoor</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>When you listen carefully, you don’t just hear music. You start to feel it.</blockquote><p>That kind of listening has stayed with me in ways I didn’t expect — especially as I stepped into the world of design. <strong>The way a singer listens to the <em>tanpura</em> to stay in tune is not so different from how a designer listens for cues in someone’s experience. </strong>When you train your ear to catch a delicate <em>ghamak</em> or the shift of a <em>raaga</em>’s<em> </em>mood, <strong>you also train your mind to notice the pauses, hesitations, and rhythms in how someone interacts with a product.</strong> You begin to sense when something isn’t flowing smoothly, when the melody of an experience feels off. Just like a composition needs balance and movement, so does a well-crafted interaction.</p><p>I think music also taught me <strong>empathy</strong>. As a student, I often mirrored my teacher’s style — imitating how she shaped a phrase or emphasized a note. That wasn’t just mimicry. It was a way of learning through feeling. You understand by becoming, just for a moment, the person you’re learning from.</p><blockquote><strong>That experience of stepping into someone else’s rhythm, of learning by observation and emotion — that’s at the heart of being a designer too.</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CDJWlwCsgQ_m_q8gUIc4jA.png" /><figcaption>From UX Collective: <a href="https://uxdesign.cc/the-links-between-ux-design-and-music-dance-performance-c413d69c69ea">https://uxdesign.cc/the-links-between-ux-design-and-music-dance-performance-c413d69c69ea</a></figcaption></figure><p>Artists, especially musicians — tend to listen first. We observe before responding. We learn by doing, again and again, until the practice becomes instinct. And I think those same instincts help us create better experiences for others. Because in both music and design, what we’re really trying to do is understand people a little better.</p><p>Today, I may not perform like I used to. But I listen more intently. I appreciate the pauses, the offbeat notes, the gentle surprises tucked inside a song. And maybe, in the act of listening, I’ve learned how to design with that same thoughtfulness.</p><p>After all, life always has a soundtrack. You just have to pay attention to hear it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f44c48b43674" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Chemistry to Creativity: My Path to UX Design]]></title>
            <link>https://medium.com/@bindu.dayanand/from-chemistry-to-creativity-my-path-to-ux-design-2b5d067be365?source=rss-b181ae0ad97a------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b5d067be365</guid>
            <category><![CDATA[instructional-design]]></category>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[chemistry]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Bindu Dayanand]]></dc:creator>
            <pubDate>Tue, 25 Mar 2025 11:35:58 GMT</pubDate>
            <atom:updated>2025-03-25T11:35:58.204Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7jDCbhx7DHWVTT5e" /><figcaption>Photo by <a href="https://unsplash.com/@goian?utm_source=medium&amp;utm_medium=referral">Ian Schneider</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>As a fresh chemistry graduate, I found myself in unexpected yet fertile terrain during the lockdown. I joined an Edtech company where I first dipped my toes into the world of <strong>content design</strong> and <strong>writing</strong>. Intrigued by the intricacies of designing effective learning experiences, I began diving deeper into researching content and <strong>curriculum development</strong> for school students.</p><p>This curiosity led me to a K-12 school with an <strong>in-house curriculum</strong>, where my learning curve steepened, and my skills flourished. Using the <strong>Understanding by Design (UbD)</strong> framework, I delved into crafting learning plans and assessments. I acquired foundational principles of education and gained hands-on experience with <strong>Learning Management Systems</strong>, mastering the art of designing impactful courses. My role as an <strong>instructional designer</strong> was both rewarding and transformative, but little did I know that this was just the beginning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/523/1*Wh8DAgXjx8Zs0V_L6N4frw.png" /><figcaption>Where Education Meets Experience: Bridging Instructional Design and UX Design Skills for User-Centric Solutions</figcaption></figure><p>A lucky opportunity came in the form of a <strong>design thinking challenge</strong>. Spread across weeks, this experience opened my eyes to the principles of design thinking, which became my creative awakening. Each stage thrilled me — starting with <strong>empathizing</strong>, where the creation of empathy maps reshaped how I approached problems, allowing me to truly understand users’ needs and see the world through their eyes. <strong>Defining </strong>the problem gave me clarity and direction, sharpening my focus on the challenges at hand. Then came the <strong>ideate </strong>stage, which sparked boundless excitement as I was generating a ‘<em>hundred ideas</em>’ and feeling the invigorating rush of innovation. <strong>Prototyping </strong>brought those ideas to life — it was an exhilarating process that filled me with a sense of accomplishment. I couldn’t wait to share my designs and test their impact. Finally, the <strong>testing </strong>phase, was immensely fulfilling; gathering user feedback and refining my solutions based on real interactions made the process even more meaningful. Together, these stages immersed me in the full cycle of problem-solving, leaving me inspired and deeply satisfied with the value of thoughtful, user-centric design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/862/1*-yJy4LuTZw2CN-5sBuRCxg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/950/1*xC3U0oyTS9JJUEHOmgikfw.png" /><figcaption>Snippets of high-fidelity mockups from the mobile app created during the Design Thinking Challenge</figcaption></figure><p>Through this challenge, I discovered a deeper passion: solving problems through thoughtful, user-centric design. The satisfaction of creating solutions that resonated with users was unparalleled. The principles of design thinking hooked me, and as I learned more, I realized they formed the foundation of UX design. That revelation set my career trajectory.</p><p>From then on, I committed to the path of UX design. I immersed myself in studying its principles and tools, fueled by a newfound passion for creating experiences that genuinely make a difference. And that’s how my journey transformed — through a series of steps, fueled by curiosity, into a creative adventure in UX design.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b5d067be365" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>