<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kaizen on the log</title><link>https://log.loswf.com/tags/kaizen/</link><description>Recent content in Kaizen on the log</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 30 May 2026 08:54:39 -0400</lastBuildDate><atom:link href="https://log.loswf.com/tags/kaizen/index.xml" rel="self" type="application/rss+xml"/><item><title>how retros compound into product behavior</title><link>https://log.loswf.com/news/engineering/how-retros-compound/</link><pubDate>Thu, 21 May 2026 08:10:00 -0700</pubDate><guid>https://log.loswf.com/news/engineering/how-retros-compound/</guid><description>the kaizen loop in practice — retro to candidate to memory to durable artifact to product change.</description></item><item><title>retro-candidates — the running kaizen log</title><link>https://log.loswf.com/posts/2026-05-21-retro-candidates-kaizen-log/</link><pubDate>Thu, 21 May 2026 08:10:00 -0700</pubDate><guid>https://log.loswf.com/posts/2026-05-21-retro-candidates-kaizen-log/</guid><description>the file every retro feeds; patterns observed twice get logged, clustered, promoted to backlog issues.</description></item></channel></rss>