<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" encoding="UTF-8" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" xmlns:atom="http://www.w3.org/2005/Atom/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:fireside="http://fireside.fm/modules/rss/fireside">
  <channel>
    <fireside:hostname>web01.fireside.fm</fireside:hostname>
    <fireside:genDate>Fri, 29 May 2026 16:24:50 -0500</fireside:genDate>
    <generator>Fireside (https://fireside.fm)</generator>
    <title>Standing in the Fire - Episodes Tagged with “Documentation”</title>
    <link>https://standinginthefire.fireside.fm/tags/documentation</link>
    <pubDate>Mon, 10 Mar 2025 13:15:00 -0400</pubDate>
    <description>Dive into the fire with Kris, Garrett and John — three owners of Fireside.fm who know what it’s like to stand in the flames of entrepreneurship. In 'Standing in the Fire,' we tackle everything from the latest trends in podcasting to the realities of running a SaaS business. No scripts, no filters — just real talk about what it takes to keep the fire burning. Join us as we explore the triumphs, struggles, and surprising lessons learned along the way.</description>
    <language>en-us</language>
    <itunes:type>episodic</itunes:type>
    <itunes:subtitle>Real Talk for Founders in the Heat of SaaS Growth.</itunes:subtitle>
    <itunes:author>Very Good Software</itunes:author>
    <itunes:summary>Dive into the fire with Kris, Garrett and John — three owners of Fireside.fm who know what it’s like to stand in the flames of entrepreneurship. In 'Standing in the Fire,' we tackle everything from the latest trends in podcasting to the realities of running a SaaS business. No scripts, no filters — just real talk about what it takes to keep the fire burning. Join us as we explore the triumphs, struggles, and surprising lessons learned along the way.</itunes:summary>
    <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/c/c9b954c7-1299-4109-89e9-cc7f4d382e43/cover.jpg?v=2"/>
    <itunes:explicit>no</itunes:explicit>
    <itunes:keywords>Podcast hosting, SaaS entrepreneurship, Fireside.fm, Software development, Marketing strategy, Customer experience, Podcast analytics, Team collaboration, Product improvement, Startup journey</itunes:keywords>
    <itunes:owner>
      <itunes:name>Very Good Software</itunes:name>
      <itunes:email>john@fireside.fm</itunes:email>
    </itunes:owner>
<itunes:category text="Business">
  <itunes:category text="Entrepreneurship"/>
</itunes:category>
<itunes:category text="Business">
  <itunes:category text="Marketing"/>
</itunes:category>
<item>
  <title>6: The Art of Sharing Knowledge in Teams</title>
  <link>https://standinginthefire.fireside.fm/6</link>
  <guid isPermaLink="false">e30f6704-fd8b-46ed-99c3-469b6dda7e81</guid>
  <pubDate>Mon, 10 Mar 2025 13:15:00 -0400</pubDate>
  <author>Very Good Software</author>
  <enclosure url="https://op3.dev/e/aphid.fireside.fm/d/1437767933/c9b954c7-1299-4109-89e9-cc7f4d382e43/e30f6704-fd8b-46ed-99c3-469b6dda7e81.mp3" length="14180847" type="audio/mpeg"/>
  <itunes:episodeType>full</itunes:episodeType>
  <itunes:author>Very Good Software</itunes:author>
  <itunes:subtitle>John, Kris, and Garrett dive into the challenge of capturing, organizing, and sharing company knowledge. From technical documentation to internal playbooks and video walkthroughs, they explore the best ways to ensure critical information doesn’t get lost.</itunes:subtitle>
  <itunes:duration>28:09</itunes:duration>
  <itunes:explicit>no</itunes:explicit>
  <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/c/c9b954c7-1299-4109-89e9-cc7f4d382e43/cover.jpg?v=2"/>
  <description>&lt;p&gt;How does a growing SaaS company keep track of important knowledge? From server setups to customer success playbooks, every company builds a wealth of internal information—but too often, that knowledge is scattered, siloed, or locked away in someone’s head.&lt;/p&gt;

&lt;p&gt;In this episode, John, Kris, and Garrett explore how to document and share company knowledge effectively. They discuss real-world challenges, like merging Rails apps and ensuring critical infrastructure knowledge isn’t lost, as well as how to balance text-based documentation with video walkthroughs. &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Takeaways:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Company knowledge management is crucial for team efficiency.&lt;/li&gt;
&lt;li&gt;Identifying challenges in knowledge sharing helps improve processes.&lt;/li&gt;
&lt;li&gt;Technical documentation should be thorough and accessible.&lt;/li&gt;
&lt;li&gt;Centralizing information can streamline communication.&lt;/li&gt;
&lt;li&gt;Choosing the right tools is essential for effective documentation.&lt;/li&gt;
&lt;li&gt;Video can enhance knowledge transfer but should be concise.&lt;/li&gt;
&lt;li&gt;Documentation needs to be regularly updated to remain relevant.&lt;/li&gt;
&lt;li&gt;AI has the potential to automate documentation processes.&lt;/li&gt;
&lt;li&gt;Creating a culture of knowledge sharing is important.&lt;/li&gt;
&lt;li&gt;Feedback from users can guide improvements in knowledge management.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Key Quotes:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;"If you document nothing, the only knowledge management system you have is luck."&lt;/p&gt;

&lt;p&gt;"Slack is great for quick answers but terrible for long-term knowledge storage."&lt;/p&gt;

&lt;p&gt;"Your team should always know where to look before they have to ask."&lt;/p&gt;

&lt;p&gt;"Documentation is a moving target." &lt;/p&gt;
</description>
  <content:encoded>
    <![CDATA[<p>How does a growing SaaS company keep track of important knowledge? From server setups to customer success playbooks, every company builds a wealth of internal information—but too often, that knowledge is scattered, siloed, or locked away in someone’s head.</p>

<p>In this episode, John, Kris, and Garrett explore how to document and share company knowledge effectively. They discuss real-world challenges, like merging Rails apps and ensuring critical infrastructure knowledge isn’t lost, as well as how to balance text-based documentation with video walkthroughs. </p>

<p><strong>Takeaways:</strong></p>

<ul>
<li>Company knowledge management is crucial for team efficiency.</li>
<li>Identifying challenges in knowledge sharing helps improve processes.</li>
<li>Technical documentation should be thorough and accessible.</li>
<li>Centralizing information can streamline communication.</li>
<li>Choosing the right tools is essential for effective documentation.</li>
<li>Video can enhance knowledge transfer but should be concise.</li>
<li>Documentation needs to be regularly updated to remain relevant.</li>
<li>AI has the potential to automate documentation processes.</li>
<li>Creating a culture of knowledge sharing is important.</li>
<li>Feedback from users can guide improvements in knowledge management.</li>
</ul>

<p><strong>Key Quotes:</strong></p>

<p>"If you document nothing, the only knowledge management system you have is luck."</p>

<p>"Slack is great for quick answers but terrible for long-term knowledge storage."</p>

<p>"Your team should always know where to look before they have to ask."</p>

<p>"Documentation is a moving target."</p><p>Links:</p><ul><li><a title="Notion" rel="nofollow" href="https://click.fireside.fm/e/MTc0ODEy">Notion
</a></li><li><a title="Google Docs" rel="nofollow" href="https://click.fireside.fm/e/MTc0ODEz">Google Docs
</a></li><li><a title="Dropbox" rel="nofollow" href="https://click.fireside.fm/e/MTc0ODE0">Dropbox
</a></li><li><a title="GitHub Wikis" rel="nofollow" href="https://click.fireside.fm/e/MTc0ODE1">GitHub Wikis
</a></li><li><a title="Loom" rel="nofollow" href="https://click.fireside.fm/e/MTc0ODE2">Loom
</a></li><li><a title="ScreenFlow" rel="nofollow" href="https://click.fireside.fm/e/MTc0ODE3">ScreenFlow
</a></li><li><a title="Screen Studio" rel="nofollow" href="https://click.fireside.fm/e/MTc0ODE4">Screen Studio
</a></li><li><a title="Buy Back Your Time" rel="nofollow" href="https://click.fireside.fm/e/MTc0ODE5">Buy Back Your Time
</a></li><li><a title="dnsimple" rel="nofollow" href="https://click.fireside.fm/e/MTc0ODIw">dnsimple
</a></li><li><a title="Obsidian" rel="nofollow" href="https://click.fireside.fm/e/MTc0ODIx">Obsidian
</a></li></ul>]]>
  </content:encoded>
  <itunes:summary>
    <![CDATA[<p>How does a growing SaaS company keep track of important knowledge? From server setups to customer success playbooks, every company builds a wealth of internal information—but too often, that knowledge is scattered, siloed, or locked away in someone’s head.</p>

<p>In this episode, John, Kris, and Garrett explore how to document and share company knowledge effectively. They discuss real-world challenges, like merging Rails apps and ensuring critical infrastructure knowledge isn’t lost, as well as how to balance text-based documentation with video walkthroughs. </p>

<p><strong>Takeaways:</strong></p>

<ul>
<li>Company knowledge management is crucial for team efficiency.</li>
<li>Identifying challenges in knowledge sharing helps improve processes.</li>
<li>Technical documentation should be thorough and accessible.</li>
<li>Centralizing information can streamline communication.</li>
<li>Choosing the right tools is essential for effective documentation.</li>
<li>Video can enhance knowledge transfer but should be concise.</li>
<li>Documentation needs to be regularly updated to remain relevant.</li>
<li>AI has the potential to automate documentation processes.</li>
<li>Creating a culture of knowledge sharing is important.</li>
<li>Feedback from users can guide improvements in knowledge management.</li>
</ul>

<p><strong>Key Quotes:</strong></p>

<p>"If you document nothing, the only knowledge management system you have is luck."</p>

<p>"Slack is great for quick answers but terrible for long-term knowledge storage."</p>

<p>"Your team should always know where to look before they have to ask."</p>

<p>"Documentation is a moving target."</p><p>Links:</p><ul><li><a title="Notion" rel="nofollow" href="https://click.fireside.fm/e/MTc0ODEy">Notion
</a></li><li><a title="Google Docs" rel="nofollow" href="https://click.fireside.fm/e/MTc0ODEz">Google Docs
</a></li><li><a title="Dropbox" rel="nofollow" href="https://click.fireside.fm/e/MTc0ODE0">Dropbox
</a></li><li><a title="GitHub Wikis" rel="nofollow" href="https://click.fireside.fm/e/MTc0ODE1">GitHub Wikis
</a></li><li><a title="Loom" rel="nofollow" href="https://click.fireside.fm/e/MTc0ODE2">Loom
</a></li><li><a title="ScreenFlow" rel="nofollow" href="https://click.fireside.fm/e/MTc0ODE3">ScreenFlow
</a></li><li><a title="Screen Studio" rel="nofollow" href="https://click.fireside.fm/e/MTc0ODE4">Screen Studio
</a></li><li><a title="Buy Back Your Time" rel="nofollow" href="https://click.fireside.fm/e/MTc0ODE5">Buy Back Your Time
</a></li><li><a title="dnsimple" rel="nofollow" href="https://click.fireside.fm/e/MTc0ODIw">dnsimple
</a></li><li><a title="Obsidian" rel="nofollow" href="https://click.fireside.fm/e/MTc0ODIx">Obsidian
</a></li></ul>]]>
  </itunes:summary>
</item>
  </channel>
</rss>
