<?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 Pulkit Vashishta on Medium]]></title>
        <description><![CDATA[Stories by Pulkit Vashishta on Medium]]></description>
        <link>https://medium.com/@PulkitV?source=rss-a7a6207f44b2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*ZGMBBh7IcovH19jy.jpg</url>
            <title>Stories by Pulkit Vashishta on Medium</title>
            <link>https://medium.com/@PulkitV?source=rss-a7a6207f44b2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 20:40:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@PulkitV/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[This Month as a Product Manager: Between Slack Fires and Quiet Lessons]]></title>
            <link>https://medium.com/@PulkitV/this-month-as-a-product-manager-between-slack-fires-and-quiet-lessons-ed0d22370125?source=rss-a7a6207f44b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed0d22370125</guid>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Pulkit Vashishta]]></dc:creator>
            <pubDate>Wed, 11 Feb 2026 15:23:39 GMT</pubDate>
            <atom:updated>2026-02-11T15:23:39.359Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Notes from a month where almost every decision came with a tradeoff</em></p><p><strong>Monday, 10:30 AM.</strong><br>Support escalates an issue.<br>Engineering says the proper fix needs multiple sprints.<br>Business wants movement this week.</p><p>I have 30 minutes to decide.</p><p>That was this month.</p><p>Not polished strategy decks.<br>Not clean “identify problem → ship solution → celebrate result.”<br>Just real product work: incomplete information, conflicting constraints, and decisions made before certainty arrives.</p><p>This is my journal from that month — what I learned, what I got wrong, and what I’m changing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vlhC-wZ_8H2XZOT358S9CA.png" /></figure><h3>Week 1: The illusion of control</h3><p>When pressure rises, I default to structure.<br>Impact vs effort. Scoring sheets. Prioritization frameworks.</p><p>They help — but this month reminded me they can also become a comfort blanket.</p><p>The shift for me was returning to a simpler sequence:</p><ol><li>What exact user pain are we solving?</li><li>Where in the journey does it break?</li><li>What’s the smallest change that can reduce pain quickly?</li></ol><p>Once we did that, discussions got sharper.<br>Less scoring theater, more decision clarity.</p><h3>Week 2: Dashboards gave patterns. Conversations gave truth.</h3><p>At one point, we were staring at low fulfillment and slicing data every way possible.<br>The charts were useful — but still incomplete.</p><p>Then came a field conversation that cut through days of analysis:</p><blockquote><em>“We don’t get return trips, so we don’t take forward trips.”</em></blockquote><p>One sentence explained what dozens of internal debates couldn’t. Qualitative feedback is as important as quantitative feedback. Sometimes, more so.</p><p>That week reset something for me:</p><ul><li>Analytics helps you find <em>where</em> pain exists.</li><li>Human conversations help you understand <em>why</em> it exists.</li></ul><p>You need both. Always.</p><h3>Week 3: Perfection is expensive. Learning is cheaper.</h3><p>This was the week I almost delayed a launch for “just one more refinement.”</p><p>More edge cases.<br>More flow polish.<br>More internal comfort.</p><p>Instead, we shipped a narrow version with guardrails:</p><ul><li>limited rollout,</li><li>clear instrumentation,</li><li>tight feedback loops.</li></ul><p>In parallel, we tested awareness variants in checkout.<br>Multiple internal opinions. One decisive result.</p><p><strong>Mini-example: We replaced design debate with an experiment.</strong><br><strong>Before:</strong> Teams disagreed on how to explain limits in checkout — each option had strong internal opinions.<br><strong>Decision:</strong> We ran a controlled test across three awareness patterns: animated bottom sheet, highlighted static section, and slide-in panel.<br><strong>After:</strong> The animated bottom sheet delivered a <strong>~30–40% lift in awareness</strong>, so we scaled it first instead of delaying for a full checkout overhaul.</p><blockquote><strong><em>What changed for me: if clean signal can come in days, opinion should not run for weeks.</em></strong></blockquote><p>That reinforced a principle I want to keep:</p><blockquote><em>Opinions are for hypotheses.<br>Experiments are for decisions.</em></blockquote><h3>Week 4: Many “big product problems” are friction problems in disguise.</h3><p>By the end of the month, a pattern became obvious.</p><p>A lot of pain wasn’t because we lacked major features. It was because we had small, repeated friction:</p><ul><li>unclear expectations,</li><li>defaults that shaped low-quality behavior,</li><li>too much information at the wrong time,</li><li>support issues that were actually product design issues.</li></ul><p><strong>Some of our best wins were boring on paper:</strong></p><ul><li>simplifying education moments,</li><li>reducing repeated prompts,</li><li>clarifying expectations earlier,</li><li>rethinking defaults that were quietly hurting funnel quality.</li></ul><blockquote>None of this looks heroic on LinkedIn.<br>But this is where product quality compounds.</blockquote><h3>The part PMs don’t say enough: this is emotional labor too</h3><p>This month had days where I felt I was disappointing everyone a little:</p><ul><li>too slow for growth,</li><li>too fast for engineering comfort,</li><li>too cautious for commercial urgency,</li><li>too practical for ideal product vision.</li></ul><p>That tension is part of the role.</p><p><strong>What helped me stay steady:</strong></p><ul><li>documenting decisions and rationale,</li><li>staying close to user reality when internal noise rose,</li><li>treating “not now” as a valid product decision (not avoidance).</li></ul><blockquote>PM work is not only prioritizing features. It’s absorbing ambiguity and still giving teams directional confidence.</blockquote><h3>My misses — I brought support into one loop too late</h3><p>Support had signal we could have used earlier.</p><p><strong>Change:</strong> support input is now part of discovery, not just post-launch review.</p><h3>Quiet wins I’m proud of</h3><p>Not every meaningful month has a flagship launch.</p><p>I’m proud that we:</p><ul><li>made faster decisions with simpler prioritization,</li><li>balanced data with field/user context,</li><li>chose phased rollouts over all-or-nothing launches,</li><li>used experiments to resolve debates quickly,</li><li>and improved our decision memory through better documentation.</li></ul><p>These are quiet wins.<br>But these are the wins that compound.</p><h3>Closing thought</h3><p>The hardest PM decisions are rarely between good and bad.<br>They’re between two incomplete options — both with tradeoffs — while the clock is running.</p><p>If this month taught me one thing, it’s this:</p><blockquote><em>Clarity beats complexity. Learning velocity beats planning comfort.</em></blockquote><p>If you’re a PM and this feels familiar, reply with one decision you reversed this quarter — and <strong>the signal that changed your mind</strong>.</p><p>I’ll compile anonymized responses into a follow-up piece:<br><strong>“5 PM decisions we got wrong — and what we changed.”</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed0d22370125" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Movie Review: Border 2 Talk at 60 km/h]]></title>
            <link>https://medium.com/@PulkitV/movie-review-border-2-talk-at-60-km-h-53fe4b1f774c?source=rss-a7a6207f44b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/53fe4b1f774c</guid>
            <dc:creator><![CDATA[Pulkit Vashishta]]></dc:creator>
            <pubDate>Sat, 07 Feb 2026 14:01:45 GMT</pubDate>
            <atom:updated>2026-02-07T14:01:45.170Z</atom:updated>
            <content:encoded><![CDATA[<h3>A car, a couple, a movie hangover — and the way war stories spill into everyday love.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VzdF_gqCtk-teGJPmYUEWQ.png" /></figure><p>We’d just watched <em>Border 2</em>.</p><p>Not “watched” the way you watch a film with a calm mind and a neutral heart. More like survived it. Let it wash over us. And now, as always, the real review was happening where it always happens for us — inside the car:</p><p>Without missing a beat, she added the kind of observation that only a spouse can deliver with deadly confidence:<br>“<strong>सुनील शेट्टी के दोनों बच्चे… ट्विन्स लगते हैं, है न?</strong>”</p><p>That’s the thing about marriage. You go in thinking you’ll discuss grand themes — love, purpose, destiny. You stay because someone can pivot from a military-action film to celebrity genetics in 0.3 seconds and it somehow makes sense.</p><p>She leaned back and exhaled the way people do when they’ve spotted a plot hole large enough to drive a truck through. “I feel like they cut-cut-cut scenes and stitched them with Fevicol. And then — ” she pointed at the dashboard like it was the director’s face — “<strong>पर AI थोड़ा सा Messy कर दिया।</strong>”</p><p>AI.</p><p>That word has become the modern explanation for everything, like “bad karma” used to be. Weird face on screen? AI. Strange editing? AI. Why the hero looked like he teleported? AI. Why the screenplay forgot its own promise? Definitely AI.</p><p>Then her voice shifted. Not angry, not emotional — something sharper. The tone that means she cares.</p><p>“Ten times they made us remember that <strong>शर्त</strong>,” she said. “Like a mantra. <em>Shart jeetni hai.</em> <em>Shart jeetni hai.</em> And in the end… <strong>बताया नहीं शर्त कौन जीता.</strong>”</p><p>(Bit of spoiler: The bet here meant the discussion between Varun Dhawan and his pregnant wife on whether it will be a boy or a girl.)</p><p>She paused like she was waiting for the universe to apologize.</p><p>I had no defense.</p><p>Because she was right: films like this don’t just tell a story. They set up a moral contract with the audience. You give your attention, your tears, your patriotism-on-rent for three hours, and in return they give you closure.</p><p>But closure, apparently, was not in the budget.</p><h3>The missing scene everyone wanted</h3><p>There was a moment my wife described that stuck with me.</p><p>Not an action sequence. Not the airstrikes. The moment she wanted was simple. At the end, she said, the film showed Varun going home. But not the way <em>she</em> wanted it.</p><p>“Why not show the full return of Varun Dhawan? Just… give us that.”</p><p>The idea that after all the chaos, a person can simply walk back into normal life, touch their mother’s feet, eat dal, and sleep without hearing explosions in their dreams.</p><p>She admitted something quietly then — something she almost laughed off, because we don’t like taking ourselves too seriously.</p><p>She said her eyes had filled up. Multiple times.<br>When the soldiers were leaving their homes.<br>When someone tied a rakhi.<br>When the story tried to show the weight of departure.</p><p>I didn’t tease her. I didn’t crack a joke. I just nodded, because I’d felt it too — those quick, embarrassing tears that come even when you know the film is manipulating you.</p><p>Maybe especially <em>because</em> you know.</p><h3>The US, China, and other passengers in the back seat</h3><p>Somewhere between a flyover and a toll plaza, we got into the part of the conversation that always happens after movies about nations:</p><p>Who supports whom.<br>Who plays what game.<br>Who is pretending neutrality.<br>Who is waiting to cash in.</p><p>My wife said China supports Pakistan. I said the US likes “control” and balance. We threw around theories the way people do when they’ve consumed drama and are now trying to explain the world using the same structure: villains, allies, twists, motives.</p><p>“People say a lot of things,” I added, because real life isn’t cinema and certainty is often just confidence wearing a costume.</p><p>That’s the thing about conversations like these. They aren’t Wikipedia pages. They’re emotional weather.</p><p>And they reveal something else too: how stories of war become stories of identity.</p><h3>The ending the film forgot — and the road remembered</h3><p>By the time we neared home, our debate had softened into a kind of tired affection.</p><p>The movie didn’t tell us who won the <em>shart</em>.<br>But the road did.</p><p>The shart was never really about winning a battle. It was about earning a feeling.</p><p>A feeling that things make sense.<br>That sacrifice leads somewhere.<br>That bravery is rewarded.<br>That the story <em>closes</em>.</p><p>But life rarely closes cleanly.</p><p>So we do what couples do: we create closure in conversation, in laughter, in “yaar why didn’t they just show that one last scene?”</p><p>As we turned into our lane, the city came back — dogs, guards, sleepy balconies. The war, for us, dissolved back into everyday life.</p><p>My wife unbuckled her seatbelt and sighed the final verdict, the one that matters more than any rating:</p><p>“Bas yaar… they should’ve told us. <strong>शर्त कौन जीता.</strong>”</p><p>I looked at her and smiled.</p><p>“In our car,” I said, “you won.”</p><p>She rolled her eyes — classic — then laughed.</p><p>And suddenly, that missing scene didn’t feel so missing anymore.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53fe4b1f774c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Efforts, Motivation and Ambition are related]]></title>
            <link>https://medium.com/@PulkitV/how-efforts-motivation-and-ambition-are-related-7a80d87cc346?source=rss-a7a6207f44b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a80d87cc346</guid>
            <dc:creator><![CDATA[Pulkit Vashishta]]></dc:creator>
            <pubDate>Sat, 17 Jan 2026 09:21:21 GMT</pubDate>
            <atom:updated>2026-01-17T09:21:21.218Z</atom:updated>
            <content:encoded><![CDATA[<p>I am a strong believer of putting efforts and getting things done. I see a lot of people in everyday life who give up when they face a challenging situation — in which the best you can do take one step towards understanding the challenge better. And these situations don’t have to be big, like people thinking to start their own business, people thinking to get in shape, people thinking to start working on their relationships, etc. The situations are much much smaller — like getting up to switch off light, get out to meet a friend, cook something to eat for others, write that msg to communicate.</p><p>And giving up is deeply ingrained in our systems from when the brains of humans started to develop. Daniel Kahneman in “Thinking Fast and Slow” explains it very beautifully with analogy of system 1 and system 2. System 1 is the intuitive one, and system 2 is for calculating and thinking. When people have to apply efforts to do something using system 2, many give up. Because it drains the body of glucose (energy source), and also deters us from multitasking — which everyone wants to do.</p><blockquote>This concept in itself is no interestingly explained that my thoughts flow in System 1 and System 2 manner. So you will see this reference coming up often.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tzDHjyzTdCFBc77W.jpg" /></figure><p>Understanding this phenomenon well has helped me understand the situations I face in my daily life. When is my system 2 needed. If I am lazy, that automatically gives me a clue that my system 2 is drained out of energy — so I want to ensure that behave in a certain way that helps me overcome that challenge.</p><p>Because motivation is a very strange phenomena. It is not that people around me are not motivated. They are. But a rush of motivation is then soon followed by a massive slowdown. Its like a product life cycle. You build your motivation — use it, and then it declines. And not always is this giving up directly related to physical tiredness, or mental drain. Many times it is just a the sense of achievement that makes people stop using their System 2 anymore — and then laziness overcomes.</p><p>Understanding that the first thought you have is not always the right one. So you always need that energy to figure out if the first thought was right. If you do not put that small effort of energy, to understand your first thought — then you are leaving your decisions to chance. Anything can happen from there on, and you will be responsible for it. Whether you decide to own that decision is upto you.</p><p>And hence comes my next set of motivational quote:</p><p>Ikigai explains this in a manner of “flow”. If you like it, &amp; you are good at it &amp; it is valuable to others, &amp; you make money out of it — best place to be in. You can do it day in and day out. But you need to put in efforts to find your flow every moment and every day. So staying active becomes all the more important. Activeness will bring you happiness and vice versa.</p><p>That small amount of energy you need to understand your first thought is the activeness that I am talking about. Every day, all the time, that small “Ok, lets try this” will help you stay active and allow System 2 to help you move in the right direction by not giving in to laziness.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_dFejycOgFcfDEwg" /></figure><p>Ambitions are so interlinked to the thinking that unless you make it easy for yourself to try things, your ambitions will not grow. What is ambition? A strong desire to do or achieve something. But how does it come, and how big that something can be, where does it stop — is what you need to build. It is a well known fact that you often see students who get into IIT after a rigorous effort of studies just give up on any further ambitions. They drain so much energy into one goal that after achieving, they retire only. Same could be in other fields as well.</p><p>So how do you stop this? How do you keep yourself going — to stay active, and not give in to laziness?</p><p>Understand this:</p><blockquote>“You are limited not by the opportunities you have, but by your ambitions”</blockquote><p>Ambition cannot be tangible. Ambition has be flowing. It should be relevant every day for as long as you are. Staying active is an ambition because you have to sustain it for as long as you are. Companies define their North Star metrics in such a way that it remains valid even if the company changes its direction. Successful businesses have a characteristic “to pivot quickly” and keep themselves relevant in the market. Thats what you need to do with your ambitions. Your achievements will come and go, but ambition has to stay relevant throughout.</p><p>Define yourselves well. Because that is how you will start seeing yourself, and that is how you will be seen. Courage to own your thoughts will come by becoming more active in every moment of every day.</p><p>In the end I want to leave you with a video that I watch often as a reminder that I own my thoughts and my efforts.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FnU_21GQ8tkk%3Fstart%3D2%26feature%3Doembed%26start%3D2&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DnU_21GQ8tkk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FnU_21GQ8tkk%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/9da94ad59f27077b3bd9f8096b8a3819/href">https://medium.com/media/9da94ad59f27077b3bd9f8096b8a3819/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a80d87cc346" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>