HeyJaredWhile You Were Working
The AI development that matters most this week — and what to do about it.
- Indexed issues, last 90 days
- 9
- Latest publication
- Sep 18, 2026
- Audience
- Checking…
- Earliest in this view
- Jul 9, 2026
Latest issues
AI Spend Belongs in the Workflow (opens the original)
Read excerpt
<img alt="" class="sizing-normal" height="819" src="https://substackcdn.com/image/fetch/$s_!R-f2!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4fb8469f-a86e-4f4e-aa6d-2ef21f1c17a6_1600x900.png"
Don’t Move the Workflow Until the New One Is Better (opens the original)
Read excerpt
The migration sounded useful until it started sounding like copyingWe were discussing how to move a set of internal workflows into a newer admin surface.The good version of the plan was pretty sensible. Take the first few workflows, build them properly, turn what we learn into shared knowledge and AI-guided skills, then use that to move the next ones faster.I like that direction. The first workflows should teach the company how to do the next ones.But there is an easy way for this to go wrong. A
AI Can Rebuild the Service. It Still Has to Prove It Can Fail. (opens the original)
Read excerpt
The old service failed, so the rebuild suddenly looked reasonableA legacy service failed recently.In public, the safe version is this: an old internal service was responsible for important page text across many customer-facing pages. Titles, headings, the bits of the page that both users and search engines rely on. When it failed, recovery needed engineering help and a temporary workaround.The immediate move was obvious. Extend the protection around the old service. Make the cache last longer. D
The Best Support Ticket Is the One You Stop Creating (opens the original)
Read excerpt
The support backlog was describing several different problemsA customer issue came into a meeting with one broad label: pending, missing, unresolved.Support could see the contacts. The rest of the company could see a large backlog. It would have been quite easy to treat that as a support-capacity problem: improve the reply, update the help content, add automation, perhaps give an AI agent more of the volume.But the contacts were coming from different places.Sometimes no source record existed. So
Nobody Owns Your AI Roadmap (opens the original)
Read excerpt
Three roadmaps for one workflow is not alignmentA commercial workflow had ended up with three roadmaps around it.One track was looking at the CRM. One was looking at AI. One was closer to the daily operational work. Each one made sense from its own seat. Each team could point at real problems and real things to build.That is what made it dangerous.If the three plans had simply continued, the company would probably have got milestones, prototypes, demos and tactical fixes. It would also have got
Publishing over time
Last 90 days. Choose a month to open its work.
Recurring subjects
Named in the text we hold. One piece can cover several.
Audience
No verified audience measurement yet.
About this data
Counts cover the work we have indexed. Tone needs enough text and a confident classification. Excerpts and episode notes are not full articles or transcripts.
Identity or attribution wrong? Suggest a correction.