<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Product-Thinking on Jake Worth</title>
    <link>https://jakeworth.com/tags/product-thinking/</link>
    <description>Recent content in Product-Thinking on Jake Worth</description>
    <image>
      <title>Jake Worth</title>
      <url>https://jakeworth.com/twittercard.png</url>
      <link>https://jakeworth.com/twittercard.png</link>
    </image>
    <generator>Hugo -- 0.159.1</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 29 Oct 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://jakeworth.com/tags/product-thinking/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Acceptance Criteria That Actually Work</title>
      <link>https://jakeworth.com/posts/acceptance-criteria-that-actually-work/</link>
      <pubDate>Tue, 30 Sep 2025 03:37:56 -0400</pubDate>
      <guid>https://jakeworth.com/posts/acceptance-criteria-that-actually-work/</guid>
      <description>&lt;p&gt;Acceptance criteria, or AC, describe what a feature or bugfix does. Writing them is an art, and some AC work much better than others. So, how do we make them work? By including a little more detail.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How I Approach Feature Requests</title>
      <link>https://jakeworth.com/posts/how-i-approach-feature-requests/</link>
      <pubDate>Wed, 14 May 2025 17:40:42 -0400</pubDate>
      <guid>https://jakeworth.com/posts/how-i-approach-feature-requests/</guid>
      <description>&lt;p&gt;Receiving feature requests is part of running a software team. Here&amp;rsquo;s how I handle them.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Two-Follow-Up Rule for Closing Support and Internal Tickets</title>
      <link>https://jakeworth.com/posts/hit-it-twice/</link>
      <pubDate>Tue, 04 Mar 2025 09:28:10 -0500</pubDate>
      <guid>https://jakeworth.com/posts/hit-it-twice/</guid>
      <description>&lt;p&gt;I recently learned a practice for customer communication that I&amp;rsquo;d like to document. It&amp;rsquo;s called &amp;ldquo;Hit It Twice.&amp;rdquo;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Product Technique: Asking &#39;What&#39;s the Why?&#39;</title>
      <link>https://jakeworth.com/posts/whats-the-why/</link>
      <pubDate>Mon, 30 Oct 2023 00:00:00 +0000</pubDate>
      <guid>https://jakeworth.com/posts/whats-the-why/</guid>
      <description>&lt;p&gt;One of my favorite product hacks is asking: &amp;ldquo;What&amp;rsquo;s the why?&amp;rdquo;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
