<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>INSIGHTS, by Varun Vashisht</title>
    <link>https://varunvashisht.com/blog/</link>
    <atom:link href="https://varunvashisht.com/blog/rss.xml" rel="self" type="application/rss+xml" />
    <description>A field journal on PMO, enterprise transformation, and embedding generative AI into delivery. Written by Varun Vashisht, Senior Program Manager, TPM &amp; Business Architect.</description>
    <language>en</language>
    <lastBuildDate>Fri, 12 Jun 2026 17:14:19 GMT</lastBuildDate>
    <item>
      <title>The most expensive way to sound like everyone else.</title>
      <link>https://varunvashisht.com/blog/the-most-expensive-way-to-sound-like-everyone-else/</link>
      <guid isPermaLink="true">https://varunvashisht.com/blog/the-most-expensive-way-to-sound-like-everyone-else/</guid>
      <description>A meme about asking a frontier model for a LinkedIn post, and the uncomfortable rule it illustrates: AI multiplies the quality of the question.</description>
      <pubDate>Fri, 12 Jun 2026 12:30:00 GMT</pubDate>
      <author>noreply@varunvashisht.com (Varun Vashisht)</author>
      <category>AI Tooling</category><category>Prompting</category><category>Content</category>
    </item>
    <item>
      <title>Which model, when. And do we really need Fable?</title>
      <link>https://varunvashisht.com/blog/which-model-when/</link>
      <guid isPermaLink="true">https://varunvashisht.com/blog/which-model-when/</guid>
      <description>Claude, OpenAI and Gemini now sell the same three tiers. A routing rule for picking between them, and an honest answer on the new top model.</description>
      <pubDate>Fri, 12 Jun 2026 00:00:00 GMT</pubDate>
      <author>noreply@varunvashisht.com (Varun Vashisht)</author>
      <category>AI Tooling</category><category>Model Selection</category><category>Claude</category><category>Procurement</category>
    </item>
    <item>
      <title>The Mindset Tech PMs Need Right Now (Hint: It&apos;s Not What You Think)</title>
      <link>https://varunvashisht.com/blog/the-mindset-tech-pms-need-right-now-hint-it-s-not-what-you-think/</link>
      <guid isPermaLink="true">https://varunvashisht.com/blog/the-mindset-tech-pms-need-right-now-hint-it-s-not-what-you-think/</guid>
      <description>A short post for project managers in tech about working with AI tools without losing your mind, or your team&apos;s trust.</description>
      <pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
      <author>noreply@varunvashisht.com (Varun Vashisht)</author>
      <category>project management</category><category>AI tools</category><category>leadership</category><category>tech careers</category><category>mindset</category><category>team management</category><category>software delivery</category>
    </item>
    <item>
      <title>The four AI tools that actually stuck. A six-month receipt.</title>
      <link>https://varunvashisht.com/blog/four-tools-that-actually-stuck/</link>
      <guid isPermaLink="true">https://varunvashisht.com/blog/four-tools-that-actually-stuck/</guid>
      <description>Most of the AI subscriptions we bought in 2024 are gone now. Four survived. Here&apos;s why, and what they have in common.</description>
      <pubDate>Tue, 12 May 2026 00:00:00 GMT</pubDate>
      <author>noreply@varunvashisht.com (Varun Vashisht)</author>
      <category>AI Tooling</category><category>Procurement</category><category>PMO</category>
    </item>
    <item>
      <title>Who&apos;s quietly cancelling their AI subscriptions?</title>
      <link>https://varunvashisht.com/blog/whos-quietly-cancelling-their-ai-subscriptions/</link>
      <guid isPermaLink="true">https://varunvashisht.com/blog/whos-quietly-cancelling-their-ai-subscriptions/</guid>
      <description>Well, well, well. Look who&apos;s quietly cancelling their AI subscriptions.</description>
      <pubDate>Sat, 09 May 2026 07:29:00 GMT</pubDate>
      <author>noreply@varunvashisht.com (Varun Vashisht)</author>
      <category>AI</category><category>Engineering</category><category>Opinion</category>
    </item>
    <item>
      <title>The status update that said nothing. A small autopsy.</title>
      <link>https://varunvashisht.com/blog/the-status-update-that-said-nothing/</link>
      <guid isPermaLink="true">https://varunvashisht.com/blog/the-status-update-that-said-nothing/</guid>
      <description>A six-paragraph weekly status report told leadership nothing. Here are the four sentences I&apos;d cross out, why, and what to write instead.</description>
      <pubDate>Tue, 05 May 2026 00:00:00 GMT</pubDate>
      <author>noreply@varunvashisht.com (Varun Vashisht)</author>
      <category>PMO</category><category>Communication</category><category>Status Reports</category>
    </item>
    <item>
      <title>Two PMOs I have been, and the one I will not be again.</title>
      <link>https://varunvashisht.com/blog/two-pmos-i-have-been/</link>
      <guid isPermaLink="true">https://varunvashisht.com/blog/two-pmos-i-have-been/</guid>
      <description>Across fourteen years I&apos;ve run two different kinds of programme office. One of them I&apos;d build again. The other I keep getting hired to dismantle.</description>
      <pubDate>Tue, 21 Apr 2026 00:00:00 GMT</pubDate>
      <author>noreply@varunvashisht.com (Varun Vashisht)</author>
      <category>PMO</category><category>Career</category><category>Governance</category>
    </item>
    <item>
      <title>What the junior PM noticed that the rest of us missed.</title>
      <link>https://varunvashisht.com/blog/what-the-junior-pm-noticed-that-the-rest-of-us-missed/</link>
      <guid isPermaLink="true">https://varunvashisht.com/blog/what-the-junior-pm-noticed-that-the-rest-of-us-missed/</guid>
      <description>Six weeks into a stuck programme, the most junior person in the room asked a single question that unstuck everything. A short post on what we lose by deferring to seniority.</description>
      <pubDate>Wed, 08 Apr 2026 00:00:00 GMT</pubDate>
      <author>noreply@varunvashisht.com (Varun Vashisht)</author>
      <category>PMO</category><category>Communication</category><category>Field notes</category>
    </item>
    <item>
      <title>The meeting that could have been a paragraph.</title>
      <link>https://varunvashisht.com/blog/the-meeting-that-could-have-been-a-paragraph/</link>
      <guid isPermaLink="true">https://varunvashisht.com/blog/the-meeting-that-could-have-been-a-paragraph/</guid>
      <description>A weekly architecture review I attended for two years. Six pages of decisions across 104 sessions. What it taught me about which meetings deserve to keep their hour.</description>
      <pubDate>Tue, 24 Mar 2026 00:00:00 GMT</pubDate>
      <author>noreply@varunvashisht.com (Varun Vashisht)</author>
      <category>Meetings</category><category>PMO</category><category>Communication</category>
    </item>
    <item>
      <title>Where Generative AI quietly pays off inside a PMO</title>
      <link>https://varunvashisht.com/blog/genai-quietly-pays-off-pmo/</link>
      <guid isPermaLink="true">https://varunvashisht.com/blog/genai-quietly-pays-off-pmo/</guid>
      <description>Requirements drafting, status synthesis, RAID summaries. The unglamorous wins.</description>
      <pubDate>Mon, 03 Feb 2025 00:00:00 GMT</pubDate>
      <author>noreply@varunvashisht.com (Varun Vashisht)</author>
      <category>GenAI</category><category>PMO</category><category>Automation</category>
    </item>
    <item>
      <title>Building a PMO that engineering actually wants to work with</title>
      <link>https://varunvashisht.com/blog/building-a-pmo-engineering-wants/</link>
      <guid isPermaLink="true">https://varunvashisht.com/blog/building-a-pmo-engineering-wants/</guid>
      <description>Cadences, RAID hygiene, and the rituals that turn governance into a velocity engine.</description>
      <pubDate>Wed, 15 Jan 2025 00:00:00 GMT</pubDate>
      <author>noreply@varunvashisht.com (Varun Vashisht)</author>
      <category>PMO</category><category>Agile</category><category>Governance</category>
    </item>
  </channel>
</rss>