<?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 Vidhi Shah on Medium]]></title>
        <description><![CDATA[Stories by Vidhi Shah on Medium]]></description>
        <link>https://medium.com/@vidhishah29?source=rss-bdea8190966e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*nVEUBrv2kofL-SMV8NJTLQ@2x.jpeg</url>
            <title>Stories by Vidhi Shah on Medium</title>
            <link>https://medium.com/@vidhishah29?source=rss-bdea8190966e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 05:55:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vidhishah29/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[How to write KRAs that work.]]></title>
            <link>https://medium.com/@vidhishah29/how-to-write-kras-that-work-da7629f74777?source=rss-bdea8190966e------2</link>
            <guid isPermaLink="false">https://medium.com/p/da7629f74777</guid>
            <category><![CDATA[design-leadership]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[design-teams]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[career-development]]></category>
            <dc:creator><![CDATA[Vidhi Shah]]></dc:creator>
            <pubDate>Mon, 26 Oct 2026 16:53:12 GMT</pubDate>
            <atom:updated>2026-10-26T16:53:12.144Z</atom:updated>
            <content:encoded><![CDATA[<p>Most KRAs don’t survive the year. They get written in April and filed away, and by mid-year they’ve stopped reflecting how the year is going. When performance conversations come around, the manager and the designer are both working from memory and gut feel, and the objectivity is gone.</p><p>The format is fine. The problem is how people write them.</p><p>I’ve been on both sides of this, as the designer writing goals that felt like homework and as the manager reading twenty of them back to back. This is what I’ve learned about writing one that’s useful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zs1p99zBYbKHa58SkGuqag.jpeg" /></figure><p><strong>What a KRA is for</strong></p><p>A KRA (Key Responsibility Area) is the one written agreement between you and your manager about what good looks like for you this year: at your level, with the strengths you bring and the gaps you’re working on.</p><p>It sets the floor. How far above it you go is up to you. It has to hold up when priorities shift, because they will. You should be able to open it at any point in the year and use it to course-correct. And it should be specific enough that nobody argues, at year-end, about whether it was a good year.</p><p><strong>Where most designers go wrong</strong></p><p>Most KRAs are written in the language of activity. “I will work on 8 projects this quarter.” “I will deliver a design system update.” “I will collaborate with product.” These describe a job that already exists. They aren’t goals.</p><p>This matters more now than it did a few years ago. When AI can help you produce three times the output, counting output tells your manager almost nothing. A good KRA needs to go one layer deeper.</p><p><strong>The questions</strong></p><p>These are in no particular order. Juniors may not be able to answer all of them yet. The further up the ladder you go, the more of them you should be able to.</p><p>Before you start, have the basics in hand: your projects from the annual operating plan, your team’s goals, and a sense of direction from your manager.</p><p><strong>1. If you owned this product in every sense, what would you do?</strong><br> Is there a problem nobody has assigned to you, but you know is worth solving? Growth starts with spotting problems before they land on your desk. As the lines between design, product and engineering get thinner, this is the question that will separate people.</p><p><strong>2. What’s your strength, and how will you put it to use?</strong><br> No two people with the same designation are the same. Name what you’re good at, and commit to using it where people beyond your manager can see it.</p><p><strong>3. How will you show your work?</strong><br> Good work that nobody outside your pod knows about only does half its job. My team at Nykaa committed to a number of internal talks we called D-Talks, where a designer walked through one project in depth: the problem, the process, the impact. Presenting gave them the confidence to defend their work and the visibility they needed to grow.</p><p><strong>4. How comfortable are you with data, and how are you getting better at it?</strong><br> Most KRAs say “become more data-driven,” which means nothing. One designer on my team wrote “add 5 metrics to production to track user behaviour on our features.” You can count it, and by year-end it either happened or it didn’t. And with AI coding tools, a designer can now add that tracking herself instead of waiting for an engineer to find the time.</p><p><strong>5. What do you need to learn to do your job better?</strong><br> I mean the specific gap holding your work back this year, not a general wishlist. Some gaps are about craft: writing, systems thinking, prototyping in code, getting fluent with the AI tools your team uses. Others are about the part of the product you own. If you work on payments, it might be understanding risk and compliance. If you own search, it might be how ranking actually works. Name the gap, and say how you’ll close it.</p><p><strong>6. Is there something you can fix?</strong><br> Spend even a little while at a company and you’ll notice what doesn’t work. A handoff process that keeps breaking? No shared way for the team to brainstorm with AI, so everyone is figuring it out alone? Most people leave these out of their KRA because they feel like someone else’s job. The designers who pick them up anyway are the ones who stand out.</p><p><strong>7. How will you manage stakeholders, deliberately?</strong><br> It sounds too soft to measure, but it matters. The trick is to turn the intent into something tangible. One year my KRA said I’d run 6 product experience sessions with leaders across locations, so they’d see users’ frustrations firsthand. It also gave me a reason to talk to leaders I wouldn’t otherwise cross paths with.</p><p><strong>8. What are you giving back to the team?</strong><br> This one is non-negotiable for me. A KRA that only lists your own projects treats you as a solo contributor. What are you doing that leaves the team stronger than you found it? A workshop? A speaker series? A newsletter? A hackathon? A documented process?</p><p>For example:</p><ul><li>One designer started a newsletter sharing design results across the org, with an infographic for each project and the metric it moved. It changed how the company saw design.</li><li>Our UX writer started a channel of short, curious pieces about writing: the history of the em dash, why one word beats three, small things designers didn’t know they needed.</li></ul><p><strong>Bonus: what’s the risk you’re taking this year?</strong><br>Most KRAs are written to be achievable. But a KRA with no risk in it guarantees safe, incremental work. Name one thing you’re not sure you can pull off, like shipping a small feature end to end, in code, yourself. It shows your manager where your ambition is and gives you both something to work towards.</p><p><strong>If you’re the manager</strong></p><p>A KRA is as much your responsibility as your team’s. It’s an agreement, so be involved, as closely as your team size allows.</p><p>The real management happens in the conversation after the first draft. That’s where you set expectations, motivate, and usually push people further than they’d go on their own. It’s also where you make the goals objective enough that the year-end review is straightforward. The designer should leave with goals that are sharper, more specific, and stretch them in the direction they need to grow.</p><p><strong>Make it a living document</strong></p><p>A KRA written in April and next opened in March has failed. Two things keep it alive.</p><p>First, write goals that survive priority shifts. “Three self-initiated ideas go live this year” holds whether or not the roadmap does. “Ship the checkout redesign” dies the moment checkout gets deprioritised. The same goes for goals tied to a specific tool or workflow, which can go stale even faster when tools change every quarter.</p><p>Second, add a self-assessment column next to every goal. My team filled theirs in through the year, as a running record of what happened against what was written. By mid-year, it was the reference for our check-in. By year-end, it was the reference for the review. Neither of us argued about what the year looked like. We just looked at the document.</p><p>The questions above aren’t the contract. The answers are. And the answers only matter if someone comes back to them.</p><p>Write your KRA like it’s going to be read. Because if you write it well, it will be.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da7629f74777" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Write it, do it!]]></title>
            <link>https://medium.com/@vidhishah29/write-it-do-it-7e50e6b99524?source=rss-bdea8190966e------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e50e6b99524</guid>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[goal-setting]]></category>
            <category><![CDATA[planning]]></category>
            <category><![CDATA[lifestyle]]></category>
            <dc:creator><![CDATA[Vidhi Shah]]></dc:creator>
            <pubDate>Fri, 05 Sep 2025 08:44:43 GMT</pubDate>
            <atom:updated>2025-09-05T08:44:43.916Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x4A43nr1zM8dsxzKzWt38w.jpeg" /><figcaption>Image credits: Photo by Noémi Macavei-Katócz on Unsplash</figcaption></figure><p>Why is it that when we talk about goals, we usually think of careers or life with a timeline stretching into the future? “I want to make enough money to be able to buy a house in this city” or “ I will write a book someday”.</p><p>These days, I hear about goals around fitness &amp; wellbeing (which I think is great!) — from tracking daily protein intake, chasing that summer body for a holiday, or closing the rings on a smartwatch.</p><p>But we rarely think about goals as something lighthearted. What I want you to see is this: goal setting can be fun. Every day fun. You may have done this unconsciously, or you were inspired by a movement like bullet journaling, like I was and discovered the joy of little wins. <br>However it comes to you, here’s a story that might make you want to do it more often.</p><p><strong>An unplanned little experiment</strong></p><p>A few weeks ago, six of us, thirty-somethings with our chaotic mix of jobs, homes, and toddlers, escaped for a break for a long weekend.</p><p>We spent most of it sprawled on the sofa, music on, comedy shows playing, pushing each other to drink like the wild twenties version of ourselves… while also being secretly relieved when the chubbling plan we sooooo enthusiastically made got cancelled.</p><p>That evening, I tried a little social experiment to break the flow. <br>I passed around the hotel notepad and asked everyone to write a “fun” bucket list they’d like to tick off in the next 6 months. <br>It can’t be the obvious “earn xxx money”. Even if it has to be, it needs to define the “fun” thing they’d do with it.</p><p>I expected everyone to brush this off as a boring task, but I was pleasantly surprised to see the energy in the room shift. One item became four!<br>Ironically, I was the only one struggling to write these, as all my ideas seemed a little doubtful considering my life is largely ruled by an almost 2-year-old!</p><blockquote><strong>The excitement to share was real! We all had goals that would have otherwise slipped away. Some of them were small, some audacious enough to set our lives in a different direction altogether!</strong></blockquote><p>And just by saying them our loud, we became each other’s accomplices; Cheerleaders even in the smallest way. Now, each of us has more gratifications waiting to arrive, even if they’re not our own items to strike off.</p><h4>The power of writing it down 🖋️</h4><p>Here I am urging you all to write down your goals. Unlock the magic of turning a vague thought into action. <br>Let your goals be in all shapes and sizes as long as you have clarity. <br>You have a big dream? Let the first step be your goal!</p><p>Take your “I want to lose weight” → “fixing an appointment with a nutritionist” or “take a trial class for MMA”. <br>This itself will propell you into a momentum of achiveing a lot more.</p><p>A month before last, I was unhappy with the monotony that had set in and wanted to learn something new. I also kept feeling bad about not being able to workout — the only FOMO in my life right now.</p><p><strong>Writing this down flicked a switch.</strong></p><p>A Google search, two calls, and a Blinkit order for swim goggles later… I was ready to show up for a month-long swim course the next morning. <br>Learn something ✅ <br>Workout ✅</p><p>Some other fun ones that I have struck off my list:</p><ul><li><strong>A no-spend week.</strong> It pushed me to plan better, adjust with what I had, and reflect on my impulses. The joy of this accomplishment was unmatched!</li><li><strong>Swim with a turtle. </strong>This led me to plan a dive trip with women I didn’t know. Bonus: I did a night dive, and saw sea animals that light up in the dark. A core memory unlocked.</li></ul><p>You get the drill. The size doesn’t matter as long as you write it down. <br>And trust me, the joy of striking it off can become an addiction I’m happy to have.</p><p>So what are the 3 goals that you will write down now? Big, small, serious, silly — Anything that makes you feel alive.</p><p>And for me? This year, my goal is a solo trip. Think I’ll manage to strike if off?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e50e6b99524" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leading Across Functions. Uniting Across Locations]]></title>
            <link>https://medium.com/@vidhishah29/leading-across-functions-uniting-across-locations-41653783fe63?source=rss-bdea8190966e------2</link>
            <guid isPermaLink="false">https://medium.com/p/41653783fe63</guid>
            <category><![CDATA[empathy]]></category>
            <category><![CDATA[remote-team-management]]></category>
            <category><![CDATA[working-together]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Vidhi Shah]]></dc:creator>
            <pubDate>Tue, 12 Aug 2025 11:32:50 GMT</pubDate>
            <atom:updated>2025-08-12T11:48:01.796Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Lessons from three years of building a multidisciplinary team that worked as one, across cities, skills, and personalities.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*i1MOIkxErTEDUu_qMe3Ttw@2x.jpeg" /></figure><p>For three years, I led a multidisciplinary design team at Nykaa, spread across Bangalore, Mumbai, and Gurgaon — product designers, a UX writer, and a UX researcher. While the structure has since evolved, many of the habits and systems we built together still shape how I lead today.</p><p>It wasn’t about managing from afar — it was about leading with presence, even without always being in the same place. Most of our conversations happened over screens, calls, and the occasional, tightly-packed work trip. That setup nudged me into taking a few conscious steps I might not have otherwise.</p><p>Those years made me more emotionally attuned, sharper as a leader, and deeply invested in building a team that didn’t just work together, but thrived together. Here are some of the systems and rituals that helped us stay connected, grow with intent, and do great work together.</p><h3><strong>The shared growth vision</strong></h3><p><strong>is the backbone of long-term performance</strong></p><p>I’m a type-A person — I like a good plan, clear direction, and defined goals. So creating a growth path for my team felt natural. But it wasn’t just about craft or performance — it was also about who they were, what drove them, and most importantly, where I could gently push them.</p><p>We co-created individual growth visions that were motivating and realistic. They acted as our year-long compass — helping us align actions with aspirations, manage expectations, and stay focused.</p><blockquote>I liked to imagine 80% of what they knew they could do, 20% of what felt just out of reach — and 100% of what I knew they were capable of, especially with the right support.</blockquote><h3><strong>Habits that made us feel like a real team</strong></h3><ol><li><strong>Small talk → Big connection</strong></li></ol><p>Being spread across cities meant no watercooler chat. But those “How was the weekend?” or “Ooh, I like that outfit?” moments mattered more than we admitted. They created openness, which was the foundation of trust.</p><p>I started every call with a little bit of life: asking, listening, sharing. It wasn’t forced. <strong>It was just how I showed up.</strong> Over time, it made a visible difference. When your team feels safe enough to share their failures with you, that’s when you know the relationship is working.</p><p><strong>2. Keep the conversation going</strong></p><p>Not every update needed to wait for a standup. Thoughtful, asynchronous messages — a follow-up to a chat, a thread that extended an idea — did more than inform. They showed that I was actively thinking, building, and supporting. <strong>They showed I cared.</strong></p><p>It wasn’t about visibility. It was about momentum. Those timely nudges went a long way in showing the team I was present — even when I wasn’t in the same room.</p><p><strong>3. Micro moves that matter</strong></p><p>Individually, we were walking on different paths, but building mechanisms to support the team was often the seasoning that elevated the recipe.</p><p>One that worked wonders for us: a dedicated space for sharing references.</p><p>Think screenshots from real products, WIPs, inspirations, stakeholder decks — anything worth capturing. It removed the “where do I share this?” hesitation and made sharing feel effortless.</p><p>This tiny habit paid off in two big ways:</p><ul><li>It became a cross-referencing goldmine — especially in parts of the journey I led, like cart, checkout, payments, and post-order, where details shifted fast.</li><li>It gave us a visual record of progress over time — collectively, in context, and at a glance.</li></ul><h3>Rituals that built togetherness</h3><p>Some of the rituals I introduced began as ways to define my team — to shape who we were, how we worked, and how we showed up for each other. What I didn’t expect was how much they would give back.</p><p>Over time, something deeper emerged: a strong sense of togetherness. It wasn’t just about bonding — it sharpened how we collaborated, made feedback more natural, and built real ownership across the board.</p><p>Turns out, when people feel part of something, they do their best work. And that togetherness? It quietly became our superpower.</p><ol><li><strong>Virtual Coffeeshops</strong></li></ol><p>I love coffee shops. And I love the conversations they spark. So, I recreated that vibe with a recurring 45-minute virtual “coffeeshop” — no agenda, no work talk. Just idhar-udhar ki baatein.</p><p>It became our most loved ritual. People dialled in from home, holidays, airports — it didn’t matter. What mattered was the sense of ease and connection it created. In a world of calendar fatigue, this one never felt like a meeting.</p><p><strong>2. Design Crits</strong></p><p>Every three weeks, we hosted design crits. WIP work, open feedback, diverse thinking. The setup was simple — but the discipline was powerful.</p><p>I always let the team go first, and shared my feedback last. It created space for every voice, encouraged ownership, and taught designers to think and articulate more clearly.</p><p>Over time, this ritual made our work sharper, more fortified, and far more resilient to failure. We didn’t just design in silos — we sharpened each other.</p><p><strong>3. Vision decks</strong></p><p>This one’s still close to my heart.<br>In a high-speed product environment like ours, everyone’s chasing go-lives. Designers often end up helping others define success, while their own ideas stay stuck in “improvement backlog” limbo.</p><p>I wanted my team to be more than doers. I wanted them to lead.</p><p>So, we created Vision Decks: evolving slides where each designer logged one idea per slide — visually illustrated, clearly explained, and freely added anytime. No deadlines. No pressure. Just a safe place to think boldly.</p><p><strong>Impact:</strong></p><p>These decks didn’t just visualise ideas — they helped define my team. They became a quiet nudge to aim higher. They circulated within product teams, and before long, found their way into roadmap planning discussions.</p><p>This was no small shift. Traditionally, those conversations were product-only territory. But our decks opened up space. They gave us the tools to enter the room earlier — not just to <em>respond</em> to plans but to <em>shape</em> them.</p><p>The format helped: visual, concise, easy to absorb. But the real impact? It redefined our role. From designers executing briefs to thought partners influencing the brief itself. From participating in the solution to co-owning the opportunity.</p><blockquote><strong>The ideas weren’t just designed — they were <em>believed in</em> across the table and that’s when we stopped being <em>just</em> a design team. We started becoming design leaders.</strong></blockquote><p>If you have some rituals that help your team belong, I’d love to know. <br>Let’s chat!</p><p><em>At Nykaa, I led the design for high-impact funnels across Beauty and Fashion — from Cart and Checkout to Payments and Post-order. My team worked across platforms and cities, covering not just journeys, but the decisions, behaviours, and systems that powered them.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41653783fe63" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>