<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments for David Ohnstad	</title>
	<atom:link href="https://davidohnstad.net/comments/feed/" rel="self" type="application/rss+xml" />
	<link>https://davidohnstad.net/</link>
	<description>AI &#38; Machine Learning in Enterprise Software &#124; Product Management</description>
	<lastBuildDate>Wed, 09 Sep 2026 08:13:05 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1</generator>
	<item>
		<title>
		Comment on Google&#8217;s Generative AI Search Revolution: What Enterprise Software Companies Must Do Now by Enterprise AI Implementation: Why Teams Fail Without the Right Skills - David Ohnstad		</title>
		<link>https://davidohnstad.net/googles-new-generative-ai-search/#comment-883</link>

		<dc:creator><![CDATA[Enterprise AI Implementation: Why Teams Fail Without the Right Skills - David Ohnstad]]></dc:creator>
		<pubDate>Wed, 09 Sep 2026 08:13:05 +0000</pubDate>
		<guid isPermaLink="false">https://davidohnstad.net/googles-new-generative-ai-search/#comment-883</guid>

					<description><![CDATA[[&#8230;] For more on this topic, see Google&#8217;s Generative AI Search Revolution: What Enterprise Software Companies Must Do Now. [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] For more on this topic, see Google&#8217;s Generative AI Search Revolution: What Enterprise Software Companies Must Do Now. [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Why Enterprise AI Projects Fail After POC Success by Enterprise AI Implementation: Why Data Lineage Matters More Than Platform Promises - David Ohnstad		</title>
		<link>https://davidohnstad.net/why-enterprise-ai-projects-fail-after-poc/#comment-880</link>

		<dc:creator><![CDATA[Enterprise AI Implementation: Why Data Lineage Matters More Than Platform Promises - David Ohnstad]]></dc:creator>
		<pubDate>Mon, 07 Sep 2026 14:25:28 +0000</pubDate>
		<guid isPermaLink="false">https://davidohnstad.net/?p=231#comment-880</guid>

					<description><![CDATA[[&#8230;] connects directly to why enterprise AI projects fail after proof-of-concept success—the gap isn&#8217;t technical capability, it&#8217;s operational readiness. Teams prove the model [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] connects directly to why enterprise AI projects fail after proof-of-concept success—the gap isn&#8217;t technical capability, it&#8217;s operational readiness. Teams prove the model [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Google&#8217;s Generative AI Search Revolution: What Enterprise Software Companies Must Do Now by Enterprise AI Implementation: Why Data Lineage Matters More Than Platform Promises - David Ohnstad		</title>
		<link>https://davidohnstad.net/googles-new-generative-ai-search/#comment-879</link>

		<dc:creator><![CDATA[Enterprise AI Implementation: Why Data Lineage Matters More Than Platform Promises - David Ohnstad]]></dc:creator>
		<pubDate>Mon, 07 Sep 2026 14:24:59 +0000</pubDate>
		<guid isPermaLink="false">https://davidohnstad.net/googles-new-generative-ai-search/#comment-879</guid>

					<description><![CDATA[[&#8230;] For more on this topic, see Google&#8217;s Generative AI Search Revolution: What Enterprise Software Companies Must Do Now. [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] For more on this topic, see Google&#8217;s Generative AI Search Revolution: What Enterprise Software Companies Must Do Now. [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on The Real Impact of AI and ML on Enterprise Problem-Solving: Beyond the Hype by How Cross-Disciplinary Thinking Shapes Modern Problem Solving and Digital Identity - David Ohnstad		</title>
		<link>https://davidohnstad.net/the-real-impact-of-emerging-tech-trends-on-everyday-problem-solving/#comment-873</link>

		<dc:creator><![CDATA[How Cross-Disciplinary Thinking Shapes Modern Problem Solving and Digital Identity - David Ohnstad]]></dc:creator>
		<pubDate>Fri, 04 Sep 2026 09:03:18 +0000</pubDate>
		<guid isPermaLink="false">https://davidohnstad.net/the-real-impact-of-emerging-tech-trends-on-everyday-problem-solving/#comment-873</guid>

					<description><![CDATA[[&#8230;] As a result, individuals are now expected to operate across overlapping knowledge areas rather than within isolated expertise zones. For more on this, see AI and machine learning applications. [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] As a result, individuals are now expected to operate across overlapping knowledge areas rather than within isolated expertise zones. For more on this, see AI and machine learning applications. [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Google&#8217;s Generative AI Search Revolution: What Enterprise Software Companies Must Do Now by Enterprise AI Agents: Why Most Companies Should Wait - David Ohnstad		</title>
		<link>https://davidohnstad.net/googles-new-generative-ai-search/#comment-872</link>

		<dc:creator><![CDATA[Enterprise AI Agents: Why Most Companies Should Wait - David Ohnstad]]></dc:creator>
		<pubDate>Fri, 04 Sep 2026 09:01:40 +0000</pubDate>
		<guid isPermaLink="false">https://davidohnstad.net/googles-new-generative-ai-search/#comment-872</guid>

					<description><![CDATA[[&#8230;] Layer 2: Process Documentation Depth. Is your workflow documented at the decision-node level, not just the happy-path level? This is where most teams fail. They document what happens when everything goes right, but they haven&#8217;t mapped the 30+ edge cases where human judgment is currently required. An agent can&#8217;t replicate judgment—it can only follow rules. If your process relies on employees &#8220;knowing when something feels off,&#8221; that&#8217;s not a process an agent can execute. The test is simple: could a new hire follow your documentation and make the same decisions your senior team makes? If not, you haven&#8217;t documented the process—you&#8217;ve documented an outline. David Ohnstad ran this audit for a data validation workflow at Veeam and discovered that 40% of the &#8220;process&#8221; was tribal knowledge held by three engineers who had been there since launch. Automating that workflow would have meant losing the error-catching that happened when those engineers noticed anomalies that didn&#8217;t fit documented rules. The correct move was to extract that tribal knowledge into explicit validation rules first, test them for six months, and only then consider automation. For more on this, see Google&#8217;s generative AI search capabilities. [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] Layer 2: Process Documentation Depth. Is your workflow documented at the decision-node level, not just the happy-path level? This is where most teams fail. They document what happens when everything goes right, but they haven&#8217;t mapped the 30+ edge cases where human judgment is currently required. An agent can&#8217;t replicate judgment—it can only follow rules. If your process relies on employees &#8220;knowing when something feels off,&#8221; that&#8217;s not a process an agent can execute. The test is simple: could a new hire follow your documentation and make the same decisions your senior team makes? If not, you haven&#8217;t documented the process—you&#8217;ve documented an outline. David Ohnstad ran this audit for a data validation workflow at Veeam and discovered that 40% of the &#8220;process&#8221; was tribal knowledge held by three engineers who had been there since launch. Automating that workflow would have meant losing the error-catching that happened when those engineers noticed anomalies that didn&#8217;t fit documented rules. The correct move was to extract that tribal knowledge into explicit validation rules first, test them for six months, and only then consider automation. For more on this, see Google&#8217;s generative AI search capabilities. [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Google&#8217;s Generative AI Search Revolution: What Enterprise Software Companies Must Do Now by AI ROI in Enterprise: When Implementation Outpaces Measurement - David Ohnstad		</title>
		<link>https://davidohnstad.net/googles-new-generative-ai-search/#comment-866</link>

		<dc:creator><![CDATA[AI ROI in Enterprise: When Implementation Outpaces Measurement - David Ohnstad]]></dc:creator>
		<pubDate>Tue, 01 Sep 2026 11:10:16 +0000</pubDate>
		<guid isPermaLink="false">https://davidohnstad.net/googles-new-generative-ai-search/#comment-866</guid>

					<description><![CDATA[[&#8230;] For more on this topic, see Google&#8217;s Generative AI Search Revolution: What Enterprise Software Companies Must Do Now. [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] For more on this topic, see Google&#8217;s Generative AI Search Revolution: What Enterprise Software Companies Must Do Now. [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Google&#8217;s Generative AI Search Revolution: What Enterprise Software Companies Must Do Now by Enterprise AI Integration: Legacy Systems Don&#039;t Block Modern ML - David Ohnstad		</title>
		<link>https://davidohnstad.net/googles-new-generative-ai-search/#comment-865</link>

		<dc:creator><![CDATA[Enterprise AI Integration: Legacy Systems Don&#039;t Block Modern ML - David Ohnstad]]></dc:creator>
		<pubDate>Tue, 01 Sep 2026 11:03:52 +0000</pubDate>
		<guid isPermaLink="false">https://davidohnstad.net/googles-new-generative-ai-search/#comment-865</guid>

					<description><![CDATA[[&#8230;] For more on this topic, see Google&#8217;s Generative AI Search Revolution: What Enterprise Software Companies Must Do Now. [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] For more on this topic, see Google&#8217;s Generative AI Search Revolution: What Enterprise Software Companies Must Do Now. [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Enterprise AI Without Platform Replacement: 4 Myths Debunked by Enterprise AI Agent Costs: 4 Budget Myths Explained - David Ohnstad		</title>
		<link>https://davidohnstad.net/enterprise-ai-platform-replacement-myths/#comment-864</link>

		<dc:creator><![CDATA[Enterprise AI Agent Costs: 4 Budget Myths Explained - David Ohnstad]]></dc:creator>
		<pubDate>Tue, 01 Sep 2026 11:03:19 +0000</pubDate>
		<guid isPermaLink="false">https://davidohnstad.net/?p=155#comment-864</guid>

					<description><![CDATA[[&#8230;] David Ohnstad has seen this failure mode from both sides—as a Senior Data Product Manager shipping AI integrations at Veeam Software, and as the person debugging runaway agent behavior at 2 AM when cloud bills spike. The problem isn&#8217;t that AI agents don&#8217;t work. The problem is that most enterprise teams deploy them with assumptions borrowed from static automation playbooks—assumptions that break the moment an agent starts making decisions without human checkpoints. What follows are four myths that persist across enterprise AI implementations, why they survive despite mounting evidence, and what actually happens when you replace them with operational reality. For more on this, see Enterprise AI platform myths debunked. [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] David Ohnstad has seen this failure mode from both sides—as a Senior Data Product Manager shipping AI integrations at Veeam Software, and as the person debugging runaway agent behavior at 2 AM when cloud bills spike. The problem isn&#8217;t that AI agents don&#8217;t work. The problem is that most enterprise teams deploy them with assumptions borrowed from static automation playbooks—assumptions that break the moment an agent starts making decisions without human checkpoints. What follows are four myths that persist across enterprise AI implementations, why they survive despite mounting evidence, and what actually happens when you replace them with operational reality. For more on this, see Enterprise AI platform myths debunked. [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Why Enterprise AI Implementation Is Stalling — 2026 Data by Enterprise AI Success: Definition Before Development - David Ohnstad		</title>
		<link>https://davidohnstad.net/enterprise-ai-implementation-stalling-production-deployment/#comment-862</link>

		<dc:creator><![CDATA[Enterprise AI Success: Definition Before Development - David Ohnstad]]></dc:creator>
		<pubDate>Mon, 31 Aug 2026 16:37:05 +0000</pubDate>
		<guid isPermaLink="false">https://davidohnstad.net/?p=211#comment-862</guid>

					<description><![CDATA[[&#8230;] Before any architecture discussion, before vendor evaluation, before the data science team touches the project—David Ohnstad recommends running what he calls the Pre-Deployment Alignment Framework: a four-stage process that forces stakeholders to commit to measurable outcomes before anyone writes code. This is not a kickoff meeting. This is a structured negotiation where product, engineering, and business leadership agree on three binding elements: the decision the AI will support, the threshold at which the output becomes specific, and the feedback mechanism that will surface failure within 30 days of launch. For more on this, see enterprise AI implementation challenges today. [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] Before any architecture discussion, before vendor evaluation, before the data science team touches the project—David Ohnstad recommends running what he calls the Pre-Deployment Alignment Framework: a four-stage process that forces stakeholders to commit to measurable outcomes before anyone writes code. This is not a kickoff meeting. This is a structured negotiation where product, engineering, and business leadership agree on three binding elements: the decision the AI will support, the threshold at which the output becomes specific, and the feedback mechanism that will surface failure within 30 days of launch. For more on this, see enterprise AI implementation challenges today. [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Google&#8217;s Generative AI Search Revolution: What Enterprise Software Companies Must Do Now by Enterprise AI Governance: Why Risk Outpaced Control - David Ohnstad		</title>
		<link>https://davidohnstad.net/googles-new-generative-ai-search/#comment-859</link>

		<dc:creator><![CDATA[Enterprise AI Governance: Why Risk Outpaced Control - David Ohnstad]]></dc:creator>
		<pubDate>Mon, 31 Aug 2026 16:33:46 +0000</pubDate>
		<guid isPermaLink="false">https://davidohnstad.net/googles-new-generative-ai-search/#comment-859</guid>

					<description><![CDATA[[&#8230;] For more on this topic, see Google&#8217;s Generative AI Search Revolution: What Enterprise Software Companies Must Do Now. [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] For more on this topic, see Google&#8217;s Generative AI Search Revolution: What Enterprise Software Companies Must Do Now. [&#8230;]</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
