<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>automation on jwogrady</title>
		<link>https://www.jwogrady.com/tags/automation/</link>
		<description>Recent content in automation on jwogrady</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 21 Sep 2026 17:25:00 -0500</lastBuildDate>
		
			<atom:link href="https://www.jwogrady.com/tags/automation/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Give away the train, own the track</title>
				<link>https://www.jwogrady.com/posts/give-away-the-train/</link>
				<pubDate>Mon, 21 Sep 2026 17:25:00 -0500</pubDate>
				<guid>https://www.jwogrady.com/posts/give-away-the-train/</guid>
				<description>&lt;p&gt;People ask why you would publish the thing you sell. Here is the reasoning,&#xA;and it holds up better than the instinct to hide it.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-premise-underneath-all-of-it&#34;&gt;The premise underneath all of it&lt;/h2&gt;&#xA;&lt;p&gt;&lt;strong&gt;If people could see an owner work, and know what they thought, most of the&#xA;production and publishing could be automated.&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;That is the bet. Not that AI writes your marketing — that the expensive,&#xA;irreplaceable input is an owner&amp;rsquo;s knowledge and judgement, and everything&#xA;downstream of that input is machinery. Extract the thinking while the work is&#xA;happening, and what remains is a scheduling problem: dispatch a crew to&#xA;capture some field media, and the rest runs.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Evidence Storytelling</title>
				<link>https://www.jwogrady.com/posts/evidence-storytelling/</link>
				<pubDate>Mon, 21 Sep 2026 11:00:00 -0500</pubDate>
				<guid>https://www.jwogrady.com/posts/evidence-storytelling/</guid>
				<description>&lt;p&gt;If you run a business and you have ever thought &lt;em&gt;we should really be writing&#xA;about this&lt;/em&gt;, and then not written about it for eight months —&lt;/p&gt;&#xA;&lt;p&gt;this one&amp;rsquo;s for you. I&amp;rsquo;ve been you. I&amp;rsquo;m partly still you.&lt;/p&gt;&#xA;&lt;p&gt;Here&amp;rsquo;s the thing I want to put a name to, because we built it this week and&#xA;it works: &lt;strong&gt;Evidence Storytelling.&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-problem-stated-plainly&#34;&gt;The problem, stated plainly&lt;/h2&gt;&#xA;&lt;p&gt;Every business is told to produce content. Every business owner knows why&#xA;they don&amp;rsquo;t.&lt;/p&gt;</description>
			</item>
			<item>
				<title>A screenshot tool for a machine with no screenshot tool</title>
				<link>https://www.jwogrady.com/posts/screenshots-that-fit/</link>
				<pubDate>Sun, 20 Sep 2026 18:58:00 -0500</pubDate>
				<guid>https://www.jwogrady.com/posts/screenshots-that-fit/</guid>
				<description>&lt;p&gt;Sixteen entries in and not one of them has shown anything. Every finding today&#xA;has been &lt;em&gt;described&lt;/em&gt; — a byte count, a directory listing, a config block&#xA;retyped into a fenced code block. That&amp;rsquo;s fine for a number and useless for a&#xA;layout, and it means I&amp;rsquo;ve been asking the reader to trust the retyping.&lt;/p&gt;&#xA;&lt;p&gt;So I went looking for a screenshot tool and found that this box doesn&amp;rsquo;t have&#xA;one. Not chromium, not playwright, not imagemagick, not scrot, not even&#xA;Pillow. WSL here is a compiler and a text editor&amp;rsquo;s remote end, and nothing&#xA;else.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
