<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Groundnote Blog</title>
    <link>https://groundnote.com.au/blog/</link>
    <description>Practical writing on meeting accountability, decision tracking, AI note verification, and meeting governance from Groundnote.</description>
    <language>en-AU</language>
    <atom:link href="https://groundnote.com.au/feed.xml" rel="self" type="application/rss+xml" />
    <lastBuildDate>Wed, 16 Sep 2026 00:00:00 +1000</lastBuildDate>
    <item>
      <title>Why "confirmed by AI" isn't the same as confirmed</title>
      <link>https://groundnote.com.au/blog/ai-confirmation-is-not-confirmation.html</link>
      <guid>https://groundnote.com.au/blog/ai-confirmation-is-not-confirmation.html</guid>
      <pubDate>Wed, 16 Sep 2026 00:00:00 +1000</pubDate>
      <description>An AI system marking a meeting outcome as high-confidence is not the same as a person confirming it. Why the distinction matters and how to keep it visible.</description>
    </item>
    <item>
      <title>The steering committee test: is your meeting actually working?</title>
      <link>https://groundnote.com.au/blog/steering-committee-test.html</link>
      <guid>https://groundnote.com.au/blog/steering-committee-test.html</guid>
      <pubDate>Wed, 16 Sep 2026 00:00:00 +1000</pubDate>
      <description>A simple three-question test to check whether a recurring meeting is producing real decisions and accountable follow-through, or just a good discussion.</description>
    </item>
    <item>
      <title>Picking a meeting AI tool: the questions that actually matter</title>
      <link>https://groundnote.com.au/blog/questions-that-matter-choosing-meeting-ai.html</link>
      <guid>https://groundnote.com.au/blog/questions-that-matter-choosing-meeting-ai.html</guid>
      <pubDate>Wed, 16 Sep 2026 00:00:00 +1000</pubDate>
      <description>Feature lists make every meeting AI tool look similar. Here are the questions that actually separate them, and where to check each vendor's answer.</description>
    </item>
  </channel>
</rss>
