<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" 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:content="http://purl.org/rss/1.0/modules/content/" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:podcast="https://podcastindex.org/namespace/1.0"><channel><generator>Alitu</generator><title><![CDATA[Release 1997 P2 staging QA]]></title><description><![CDATA[Release verification show. Not a production podcast.]]></description><itunes:summary><![CDATA[Release verification show. Not a production podcast.]]></itunes:summary><language>en-gb</language><podcast:medium>podcast</podcast:medium><podcast:podping usesPodping="true"></podcast:podping><podcast:guid>44cbabde-43ce-5d24-b472-bae781c915ac</podcast:guid><atom:link href="https://staging.feeds.alitu.com/24639163" rel="self" type="application/rss+xml"></atom:link><itunes:type>episodic</itunes:type><itunes:owner><itunes:email>release-1997-p2@alitu-test.com</itunes:email><itunes:name>Release QA</itunes:name></itunes:owner><itunes:author>Release QA</itunes:author><podcast:person>Release QA</podcast:person><itunes:explicit>false</itunes:explicit><itunes:image href="https://staging.feeds.alitu.com/24639163/85ccac97-79bb-4083-9e93-f5d1ea3e4cf6.jpg?t=1793387915000"></itunes:image><itunes:category text="Technology"></itunes:category><item><guid isPermaLink="false">c003dae4-2068-4b73-9691-3f3731313f60</guid><itunes:title><![CDATA[Tiny Tweaks, Big Time Savings]]></itunes:title><title><![CDATA[Tiny Tweaks, Big Time Savings]]></title><description><![CDATA[This episode is a concise check-in on how small workflow changes produce outsized time savings. The hosts contrast rushing into flashy automation with building processes people actually trust, arguing that calm, repeatable systems consistently outperform clever but brittle shortcuts. They run experiments with natural pauses, mid-sentence corrections, and closely grouped words to make transcript selection and editing easier. Practical examples show how tiny behavioral or structural edits—deliberate pauses, clearer phrasing, and predictable phrasing blocks—help editors and teams find and reuse content faster. Ultimately the takeaway is simple: design for reliability and human-friendly patterns, not just automation for automation’s sake.]]></description><pubDate>Fri, 30 Oct 2026 19:21:48 GMT</pubDate><itunes:duration>00:08:37</itunes:duration><enclosure url="https://staging.feeds.alitu.com/24639163/c003dae4-2068-4b73-9691-3f3731313f60.mp3?t=1793388514000" length="8269286" type="audio/mpeg"></enclosure><itunes:episodeType>full</itunes:episodeType></item></channel></rss>