<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Root Cause Analysis &amp; 8D Blog | SolveR by Galileon</title><description>Notes on 8D, root cause analysis and quality problem-solving from the team building SolveR — practical guidance for manufacturing teams.</description><link>https://galileon.si</link><language>en</language><item><title>Five Signs Your 8D Report Is Closed But Not Fixed</title><link>https://galileon.si/blog/five-signs-8d-report-closed-not-fixed</link><guid isPermaLink="true">https://galileon.si/blog/five-signs-8d-report-closed-not-fixed</guid><description>Most 8D reports look finished. Five checks, readable in the paperwork alone, show whether the defect actually stopped.</description><pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate><category>8D</category><category>Root cause analysis</category></item><item><title>Poka-Yoke for Knowledge: Why Your FMEA Stays Empty</title><link>https://galileon.si/blog/poka-yoke-for-knowledge</link><guid isPermaLink="true">https://galileon.si/blog/poka-yoke-for-knowledge</guid><description>The FMEA is not empty because people are lazy. It is empty because writing knowledge down costs the person who writes it.</description><pubDate>Mon, 24 Aug 2026 00:00:00 GMT</pubDate><category>FMEA</category><category>Poka-yoke</category></item><item><title>Two Years to Describe One Defect: What Toyota&apos;s Recall Teaches About Problem Definition</title><link>https://galileon.si/blog/problem-definition-toyota-recall-8d</link><guid isPermaLink="true">https://galileon.si/blog/problem-definition-toyota-recall-8d</guid><description>Toyota needed two years to pin down one software defect. The fix took weeks. What the recall file teaches about problem definition in 8D, and how to do it right.</description><pubDate>Tue, 18 Aug 2026 00:00:00 GMT</pubDate><category>8D</category><category>Problem definition</category><category>Root cause analysis</category></item></channel></rss>