<?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 on: Privacy-First Product Development in 2025: A Minnesota PM&#8217;s Post-Cookie Playbook	</title>
	<atom:link href="https://davidohnstadminnesota.com/why-privacy-first-product-development-is-critical-in-a-post-cookie-world/feed/" rel="self" type="application/rss+xml" />
	<link>https://davidohnstadminnesota.com/why-privacy-first-product-development-is-critical-in-a-post-cookie-world/</link>
	<description>Minnesota Outdoors — Hiking, Boundary Waters &#38; North Shore Adventures</description>
	<lastBuildDate>Mon, 26 Oct 2026 15:24:45 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.2</generator>
	<item>
		<title>
		By: Building AI and Web3 Products: Lessons from a Minnesota Product Manager - David Ohnstad Minnesota		</title>
		<link>https://davidohnstadminnesota.com/why-privacy-first-product-development-is-critical-in-a-post-cookie-world/#comment-2389</link>

		<dc:creator><![CDATA[Building AI and Web3 Products: Lessons from a Minnesota Product Manager - David Ohnstad Minnesota]]></dc:creator>
		<pubDate>Mon, 26 Oct 2026 15:24:45 +0000</pubDate>
		<guid isPermaLink="false">https://davidohnstadminnesota.com/?p=61#comment-2389</guid>

					<description><![CDATA[[&#8230;] When I&#8217;m evaluating whether to invest in an AI feature, I&#8217;m less likely to be swayed by &#8220;because AI is the future&#8221; and more likely to ask: &#8220;Will this actually solve a customer problem? Can we explain it? Can we support it? What&#8217;s the ROI?&#8221; In Silicon Valley, sometimes the narrative comes first and the customer value comes second. Here, it&#8217;s the reverse. For more on this, see privacy considerations in product development. [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] When I&#8217;m evaluating whether to invest in an AI feature, I&#8217;m less likely to be swayed by &#8220;because AI is the future&#8221; and more likely to ask: &#8220;Will this actually solve a customer problem? Can we explain it? Can we support it? What&#8217;s the ROI?&#8221; In Silicon Valley, sometimes the narrative comes first and the customer value comes second. Here, it&#8217;s the reverse. For more on this, see privacy considerations in product development. [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Product Roadmaps in the Age of AI: A Minnesota PM&#039;s Guide to Balancing Flexibility and Vision - David Ohnstad Minnesota		</title>
		<link>https://davidohnstadminnesota.com/why-privacy-first-product-development-is-critical-in-a-post-cookie-world/#comment-2379</link>

		<dc:creator><![CDATA[Product Roadmaps in the Age of AI: A Minnesota PM&#039;s Guide to Balancing Flexibility and Vision - David Ohnstad Minnesota]]></dc:creator>
		<pubDate>Mon, 26 Oct 2026 15:20:16 +0000</pubDate>
		<guid isPermaLink="false">https://davidohnstadminnesota.com/?p=61#comment-2379</guid>

					<description><![CDATA[[&#8230;] A new open-source language model gets released. Suddenly, the approach you spent two quarters designing is no longer optimal. Or your team discovers that a specific AI capability you were planning to build natively is now available through an API that&#8217;s cheaper, faster, and more reliable than building it yourself. Or—and this happened to us—you realize that the AI model you were betting on has serious limitations around data privacy that make it unsuitable for your enterprise customers, and you need to pivot entirely. For more on this, see privacy considerations in product planning. [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] A new open-source language model gets released. Suddenly, the approach you spent two quarters designing is no longer optimal. Or your team discovers that a specific AI capability you were planning to build natively is now available through an API that&#8217;s cheaper, faster, and more reliable than building it yourself. Or—and this happened to us—you realize that the AI model you were betting on has serious limitations around data privacy that make it unsuitable for your enterprise customers, and you need to pivot entirely. For more on this, see privacy considerations in product planning. [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Building for Scale: Product Lessons from Minnesota&#039;s Fastest-Growing Tech Companies - David Ohnstad Minnesota		</title>
		<link>https://davidohnstadminnesota.com/why-privacy-first-product-development-is-critical-in-a-post-cookie-world/#comment-2377</link>

		<dc:creator><![CDATA[Building for Scale: Product Lessons from Minnesota&#039;s Fastest-Growing Tech Companies - David Ohnstad Minnesota]]></dc:creator>
		<pubDate>Mon, 26 Oct 2026 15:19:37 +0000</pubDate>
		<guid isPermaLink="false">https://davidohnstadminnesota.com/?p=61#comment-2377</guid>

					<description><![CDATA[[&#8230;] Jamf&#8217;s growth story is instructive here. The company started by solving a real problem: Apple device management in enterprise environments. They didn&#8217;t guess at what enterprises needed. They talked to IT directors, systems administrators, and security teams—over and over. That deep customer understanding informed every feature, every product decision, and ultimately every scaling decision. For more on this, see navigating privacy in product development. [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] Jamf&#8217;s growth story is instructive here. The company started by solving a real problem: Apple device management in enterprise environments. They didn&#8217;t guess at what enterprises needed. They talked to IT directors, systems administrators, and security teams—over and over. That deep customer understanding informed every feature, every product decision, and ultimately every scaling decision. For more on this, see navigating privacy in product development. [&#8230;]</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
