<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="https://www.shannonweb.net/wp-content/plugins/seriously-simple-podcasting/templates/feed-stylesheet.xsl?v=2"?><rss version="2.0"
	 xmlns:content="http://purl.org/rss/1.0/modules/content/"
	 xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	 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/"
	 xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	 xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	 xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"
	 xmlns:podcast="https://podcastindex.org/namespace/1.0"
	 xmlns:ssp="https://castos.com/seriously-simple-podcasting/namespace/1.0"
	>
		<channel>
		<title>Products Liability</title>
		<atom:link href="https://www.shannonweb.net/feed/podcast/shannonweb-studios-products-liability-a-managerial-perspective/" rel="self" type="application/rss+xml"/>
		<link>https://www.shannonweb.net/podcasts/shannonweb-studios-products-liability-a-managerial-perspective/</link>
		<description>Products Liability: A Managerial Perspective is a ShannonWeb Studios production, hosted by digital assistants Harry and Emma, built as a companion podcast for Professor Shannon&#039;s BLAW4318 course at Seton Hall University&#039;s Stillman School of Business. Across 37 episodes, Harry and Emma work through the doctrine that governs defective-product law, case by case, from MacPherson v. Buick to the 2026 K.G.M. v. Meta verdict, applying the FAIR Framework to show what each ruling means from a manager&#039;s desk, not just a courtroom. It&#039;s one of several course podcasts ShannonWeb Studios produces for Professor Shannon&#039;s Legal Studies courses.</description>
		<lastBuildDate>Fri, 11 Sep 2026 03:01:15 +0000</lastBuildDate>
		<language>en-US</language>
		<copyright>© 2026 John H. Shannon, All Rights Reserved</copyright>
		<itunes:subtitle>A Managerial Perspective</itunes:subtitle>
		<itunes:author>ShannonWeb Studios</itunes:author>
		<itunes:summary>Products Liability: A Managerial Perspective is a ShannonWeb Studios production, hosted by digital assistants Harry and Emma, built as a companion podcast for Professor Shannon&#039;s BLAW4318 course at Seton Hall University&#039;s Stillman School of Business. Across 37 episodes, Harry and Emma work through the doctrine that governs defective-product law, case by case, from MacPherson v. Buick to the 2026 K.G.M. v. Meta verdict, applying the FAIR Framework to show what each ruling means from a manager&#039;s desk, not just a courtroom. It&#039;s one of several course podcasts ShannonWeb Studios produces for Professor Shannon&#039;s Legal Studies courses.</itunes:summary>
		<itunes:owner>
			<itunes:name>John H. Shannon</itunes:name>
			<itunes:email>jhs@jhshannon.net</itunes:email>
		</itunes:owner>
		<itunes:explicit>false</itunes:explicit>
		<itunes:image href="https://www.shannonweb.net/wp-content/uploads/2026/08/Shannonweb_Logo.png"></itunes:image>
			<image>
				<url>https://www.shannonweb.net/wp-content/uploads/2026/08/Shannonweb_Logo.png</url>
				<title>Products Liability</title>
				<link>https://www.shannonweb.net/podcasts/shannonweb-studios-products-liability-a-managerial-perspective/</link>
			</image>
		<itunes:category text="Education">
			<itunes:category text="Courses"></itunes:category>
		</itunes:category>
		<itunes:category text="Business">
							</itunes:category>
		<googleplay:author><![CDATA[ShannonWeb Studios]]></googleplay:author>
			<googleplay:email>jhs@jhshannon.net</googleplay:email>			<googleplay:description>Products Liability: A Managerial Perspective is a ShannonWeb Studios production, hosted by digital assistants Harry and Emma, built as a companion podcast for Professor Shannon&#039;s BLAW4318 course at Seton Hall University&#039;s Stillman School of Business. Across 37 episodes, Harry and Emma work through the doctrine that governs defective-product law, case by case, from MacPherson v. Buick to the 2026 K.G.M. v. Meta verdict, applying the FAIR Framework to show what each ruling means from a manager&#039;s desk, not just a courtroom. It&#039;s one of several course podcasts ShannonWeb Studios produces for Professor Shannon&#039;s Legal Studies courses.</googleplay:description>
			<googleplay:explicit>No</googleplay:explicit>
			<googleplay:image href="https://www.shannonweb.net/wp-content/uploads/2026/08/Shannonweb_Logo.png"></googleplay:image>
			<podcast:locked owner="jhs@jhshannon.net">yes</podcast:locked>
		<podcast:guid>054d85e1-43bf-58e4-a9a3-e99a44626172</podcast:guid>
		
		<!-- podcast_generator="SSP by Castos/3.17.0" Seriously Simple Podcasting plugin for WordPress (https://wordpress.org/plugins/seriously-simple-podcasting/) -->
		<generator>https://wordpress.org/?v=7.1</generator>
<site xmlns="com-wordpress:feed-additions:1">180678347</site>
<item>
	<title>Episode 1.2: What Is a Product? The Boundary Question That Matters More Than Ever</title>
	<link>https://www.shannonweb.net/podcast/episode-1-2-what-is-a-product-the-boundary-question-that-matters-more-than-ever/</link>
	<pubDate>Thu, 06 Aug 2026 09:56:39 +0000</pubDate>
	<dc:creator><![CDATA[ShannonWeb Studios]]></dc:creator>
	<guid isPermaLink="false">bde1fd96-20f4-5a90-8225-b8076a17dc71</guid>
	<description><![CDATA[<p>Is a hamburger a product, or a service? The law actually answers that one cleanly: restaurant food is a good by definition. But that clean answer is the exception, not the rule, and this episode uses it to set up one of products liability law&#8217;s hardest boundary problems: distinguishing goods from services under the &#8220;which predominates&#8221; test for genuinely mixed transactions, illustrated through a hair salon selling product alongside a styling service. It then pushes the test to its breaking point with software, SaaS subscriptions, and generative AI. Using the FAIR Framework&#8217;s Imagination lens, it argues that managers must anticipate where courts will draw lines the law hasn&#8217;t yet settled. The episode anchors this frontier question in a real March 2026 verdict, K.G.M. v. Meta, where a jury found Meta and Google negligent over social media&#8217;s addictive design, without ever having to decide whether a platform counts as a &#8220;product,&#8221; a case this series returns to throughout the semester.</p>]]></description>
	<itunes:subtitle><![CDATA[Is a hamburger a product, or a service? The law actually answers that one cleanly: restaurant food is a good by definition. But that clean answer is the exception, not the rule, and this episode uses it to set up one of products liability law&#8217;s har]]></itunes:subtitle>
	<content:encoded><![CDATA[<p>Is a hamburger a product, or a service? The law actually answers that one cleanly: restaurant food is a good by definition. But that clean answer is the exception, not the rule, and this episode uses it to set up one of products liability law&#8217;s hardest boundary problems: distinguishing goods from services under the &#8220;which predominates&#8221; test for genuinely mixed transactions, illustrated through a hair salon selling product alongside a styling service. It then pushes the test to its breaking point with software, SaaS subscriptions, and generative AI. Using the FAIR Framework&#8217;s Imagination lens, it argues that managers must anticipate where courts will draw lines the law hasn&#8217;t yet settled. The episode anchors this frontier question in a real March 2026 verdict, K.G.M. v. Meta, where a jury found Meta and Google negligent over social media&#8217;s addictive design, without ever having to decide whether a platform counts as a &#8220;product,&#8221; a case this series returns to throughout the semester.</p>]]></content:encoded>
	<enclosure url="https://www.shannonweb.net/wp-content/uploads/2026/06/1-2_Harry_What_Is_a_Product.mp3" length="12473199" type="audio/mpeg"></enclosure>
	<itunes:summary><![CDATA[Is a hamburger a product, or a service? The law actually answers that one cleanly: restaurant food is a good by definition. But that clean answer is the exception, not the rule, and this episode uses it to set up one of products liability law&#8217;s hardest boundary problems: distinguishing goods from services under the &#8220;which predominates&#8221; test for genuinely mixed transactions, illustrated through a hair salon selling product alongside a styling service. It then pushes the test to its breaking point with software, SaaS subscriptions, and generative AI. Using the FAIR Framework&#8217;s Imagination lens, it argues that managers must anticipate where courts will draw lines the law hasn&#8217;t yet settled. The episode anchors this frontier question in a real March 2026 verdict, K.G.M. v. Meta, where a jury found Meta and Google negligent over social media&#8217;s addictive design, without ever having to decide whether a platform counts as a &#8220;product,&#8221; a case this series returns to throughout the semester.]]></itunes:summary>
	<itunes:explicit>false</itunes:explicit>
	<itunes:block>yes</itunes:block>
	<itunes:duration>00:13:00</itunes:duration>
	<itunes:author><![CDATA[ShannonWeb Studios]]></itunes:author>	<googleplay:description><![CDATA[Is a hamburger a product, or a service? The law actually answers that one cleanly: restaurant food is a good by definition. But that clean answer is the exception, not the rule, and this episode uses it to set up one of products liability law&#8217;s hardest boundary problems: distinguishing goods from services under the &#8220;which predominates&#8221; test for genuinely mixed transactions, illustrated through a hair salon selling product alongside a styling service. It then pushes the test to its breaking point with software, SaaS subscriptions, and generative AI. Using the FAIR Framework&#8217;s Imagination lens, it argues that managers must anticipate where courts will draw lines the law hasn&#8217;t yet settled. The episode anchors this frontier question in a real March 2026 verdict, K.G.M. v. Meta, where a jury found Meta and Google negligent over social media&#8217;s addictive design, without ever having to decide whether a platform counts as a &#8220;product,&#8221; a case thi]]></googleplay:description>
	<googleplay:explicit>No</googleplay:explicit>
	<googleplay:block>yes</googleplay:block>
</item>

<item>
	<title>Episode 1.1: The Map of Products Liability: Three Defects, Three Theories</title>
	<link>https://www.shannonweb.net/podcast/episode-1-1-the-map-of-products-liability-three-defects-three-theories/</link>
	<pubDate>Thu, 06 Aug 2026 09:56:00 +0000</pubDate>
	<dc:creator><![CDATA[ShannonWeb Studios]]></dc:creator>
	<guid isPermaLink="false">1aff8d55-4025-518d-891e-1431f528f304</guid>
	<description><![CDATA[<p>When Samsung&#8217;s Galaxy Note 7 batteries started catching fire, the company faced a question every product manager eventually confronts: what kind of defect are we actually dealing with? This episode maps the foundational architecture of products liability law through the three ways a product can go wrong: manufacturing defects (unit-specific production errors), design defects (flaws built into an entire product line, illustrated through the Ford Pinto), and failures to warn (inadequate disclosure of known risks). Using the FAIR Framework&#8217;s Flexibility lens, the episode shows why each defect type demands a different managerial response; misdiagnosing the problem wastes resources and multiplies liability exposure. It closes by previewing a question that runs through the whole semester: how this decades-old taxonomy holds up against software, algorithms, and AI systems that resist tidy classification. When Samsung&#8217;s Galaxy Note 7 batteries started catching fire, the company faced a question every product manager eventually confronts: what kind of defect are we actually dealing with? This episode maps the foundational architecture of products liability law through the three ways a product can go wrong: manufacturing defects (unit-specific production errors), design defects (flaws built into an entire product line, illustrated through the Ford Pinto), and failures to warn (inadequate disclosure of known risks). Using the FAIR Framework&#8217;s Flexibility lens, the episode shows why each defect type demands a different managerial response; misdiagnosing the problem wastes resources and multiplies liability exposure. It closes by previewing a question that runs through the whole semester: how this decades-old taxonomy holds up against software, algorithms, and AI systems that resist tidy classification.</p>]]></description>
	<itunes:subtitle><![CDATA[When Samsung&#8217;s Galaxy Note 7 batteries started catching fire, the company faced a question every product manager eventually confronts: what kind of defect are we actually dealing with? This episode maps the foundational architecture of products lia]]></itunes:subtitle>
	<content:encoded><![CDATA[<p>When Samsung&#8217;s Galaxy Note 7 batteries started catching fire, the company faced a question every product manager eventually confronts: what kind of defect are we actually dealing with? This episode maps the foundational architecture of products liability law through the three ways a product can go wrong: manufacturing defects (unit-specific production errors), design defects (flaws built into an entire product line, illustrated through the Ford Pinto), and failures to warn (inadequate disclosure of known risks). Using the FAIR Framework&#8217;s Flexibility lens, the episode shows why each defect type demands a different managerial response; misdiagnosing the problem wastes resources and multiplies liability exposure. It closes by previewing a question that runs through the whole semester: how this decades-old taxonomy holds up against software, algorithms, and AI systems that resist tidy classification. When Samsung&#8217;s Galaxy Note 7 batteries started catching fire, the company faced a question every product manager eventually confronts: what kind of defect are we actually dealing with? This episode maps the foundational architecture of products liability law through the three ways a product can go wrong: manufacturing defects (unit-specific production errors), design defects (flaws built into an entire product line, illustrated through the Ford Pinto), and failures to warn (inadequate disclosure of known risks). Using the FAIR Framework&#8217;s Flexibility lens, the episode shows why each defect type demands a different managerial response; misdiagnosing the problem wastes resources and multiplies liability exposure. It closes by previewing a question that runs through the whole semester: how this decades-old taxonomy holds up against software, algorithms, and AI systems that resist tidy classification.</p>]]></content:encoded>
	<enclosure url="https://www.shannonweb.net/wp-content/uploads/2026/06/1-1_Emma_Three_Defects_Three_Theories.mp3" length="11742188" type="audio/mpeg"></enclosure>
	<itunes:summary><![CDATA[When Samsung&#8217;s Galaxy Note 7 batteries started catching fire, the company faced a question every product manager eventually confronts: what kind of defect are we actually dealing with? This episode maps the foundational architecture of products liability law through the three ways a product can go wrong: manufacturing defects (unit-specific production errors), design defects (flaws built into an entire product line, illustrated through the Ford Pinto), and failures to warn (inadequate disclosure of known risks). Using the FAIR Framework&#8217;s Flexibility lens, the episode shows why each defect type demands a different managerial response; misdiagnosing the problem wastes resources and multiplies liability exposure. It closes by previewing a question that runs through the whole semester: how this decades-old taxonomy holds up against software, algorithms, and AI systems that resist tidy classification. When Samsung&#8217;s Galaxy Note 7 batteries started catching fire, the company faced a question every product manager eventually confronts: what kind of defect are we actually dealing with? This episode maps the foundational architecture of products liability law through the three ways a product can go wrong: manufacturing defects (unit-specific production errors), design defects (flaws built into an entire product line, illustrated through the Ford Pinto), and failures to warn (inadequate disclosure of known risks). Using the FAIR Framework&#8217;s Flexibility lens, the episode shows why each defect type demands a different managerial response; misdiagnosing the problem wastes resources and multiplies liability exposure. It closes by previewing a question that runs through the whole semester: how this decades-old taxonomy holds up against software, algorithms, and AI systems that resist tidy classification.]]></itunes:summary>
	<itunes:explicit>false</itunes:explicit>
	<itunes:block>yes</itunes:block>
	<itunes:duration>00:12:14</itunes:duration>
	<itunes:author><![CDATA[ShannonWeb Studios]]></itunes:author>	<googleplay:description><![CDATA[When Samsung&#8217;s Galaxy Note 7 batteries started catching fire, the company faced a question every product manager eventually confronts: what kind of defect are we actually dealing with? This episode maps the foundational architecture of products liability law through the three ways a product can go wrong: manufacturing defects (unit-specific production errors), design defects (flaws built into an entire product line, illustrated through the Ford Pinto), and failures to warn (inadequate disclosure of known risks). Using the FAIR Framework&#8217;s Flexibility lens, the episode shows why each defect type demands a different managerial response; misdiagnosing the problem wastes resources and multiplies liability exposure. It closes by previewing a question that runs through the whole semester: how this decades-old taxonomy holds up against software, algorithms, and AI systems that resist tidy classification. When Samsung&#8217;s Galaxy Note 7 batteries started catching fire, the comp]]></googleplay:description>
	<googleplay:explicit>No</googleplay:explicit>
	<googleplay:block>yes</googleplay:block>
</item>
	</channel>
</rss>
