Skip to content
Trending storyDeveloping

Every republishes Katie Parrott's guide to retiring or revisiting AI workflows

1 article1 sourcesince Nov 6Last article 13h ago ·

Overview

AISummary of 1 article

Every republishes Katie Parrott's July guide on deciding which AI workflows to keep, redesign, revisit, or retire.

The republication follows Every's Thesis: 2027 conference. Parrott says a workflow that fails today may work later, as new tools hide technical difficulty or fit a workflow better. As an example, she cites Tend, a Codex-native system Dan Shipper built to pull email, Slack, meeting notes and company updates into one place. Parrott says she first thought she did not need it.

Written by AI from the articles below · updated Nov 6, 11:34 AM ET

Check the sources:

Article timeline

The articles in this story. Times are ET.

Nov 6
  1. EveryBlog
    Every republishes Katie Parrott's guide to retiring or revisiting AI workflows

    AIEvery republishes Katie Parrott's July piece on deciding which AI workflows to keep, redesign, revisit, or retire, following its Thesis: 2027 conference. Parrott says a solution that fails today may work later as new tools abstract away technical difficulty or fit a workflow better. She cites Tend, a Codex-native system Dan Shipper built to pull email, Slack, meeting notes, and company updates into one place, which she initially thought she did not need.

Heat Trend

Not enough continuous observations to show a trend yet.