Explore every episode of the podcast Build your first AI workflow
| Title | Pub. Date | Duration | |
|---|---|---|---|
| One tested step at a time | 13 oct. 2026 | 00:06:09 | |
Hey! I'd love to hear your thoughts, send me a voice note. Grace leads a customer support team and was sure her scheduled job had failed. It had run on the dot; she had switched her notifications off. She checks the run that happened without her, then chooses one upgrade somebody will use, or none. Go deeper: the three things a job should never have at once, and when not to upgrade. | |||
| When nobody's watching | 13 oct. 2026 | 00:06:13 | |
Hey! I'd love to hear your thoughts, send me a voice note. Omar builds the pipeline summary at his kitchen table every Monday at six thirty. He puts the job on a schedule, checks the instructions, the source access and the time before confirming, and decides what the job does when something is missing. Go deeper: the old export that produced a plausible summary nobody should have trusted. | |||
| A claim you can stand behind | 13 oct. 2026 | 00:06:27 | |
Hey! I'd love to hear your thoughts, send me a voice note. Priya reads what customers say for a living, and an AI summary told her exactly what she wanted to hear. She brings a second source in, asks three questions of the result (is it right, is it useful, what did it assume) and turns what she finds into a guideline. Go deeper: why smooth writing makes errors easier to miss, and what a claim needs before you stand behind it. | |||
| Change one thing | 13 oct. 2026 | 00:06:29 | |
Hey! I'd love to hear your thoughts, send me a voice note. Marcus plans dinner for a family of four, and his AI meal plan put braised short ribs on soccer night. He adds one standard, keeps everything else the same, and runs the job again in a fresh conversation. Now he can tell what the change did. Go deeper: why a fresh conversation is the real test. | |||
| Access, not copies | 13 oct. 2026 | 00:07:57 | |
Hey! I'd love to hear your thoughts, send me a voice note. Nadia is a project manager who has copied forty task updates into a Monday email for two years. With Cassandra she picks the job, connects one source with only the doors it needs, describes the job in five parts, and checks the first run against the board. Go deeper: why "easy to check" decides which job goes first, and where your data goes before you connect anything. | |||