John Cutler critiques the recurring pattern of slides that wrap AI into old SDLC diagrams with logos, claiming the 'bottleneck has moved' and that the answer is settled, even as new methods appear weekly. The essay argues this confident framing outruns the evidence and misleads practitioners. The point matters because product and engineering leaders make resourcing and process decisions based on these simplified narratives. Treating the bottleneck story as solved can lock teams into premature conclusions while the underlying work is still changing.
01Key takeaways
- Be skeptical of slides that present AI-era process changes as already solved.
- Check whether a claimed bottleneck shift is backed by observed data from your own team.
- Expect the methods and vocabulary around AI-assisted development to keep changing quickly.
- Avoid locking in process decisions based on a single fashionable framing.
- Ask what specific evidence supports any confident claim about where the constraint sits.
02Key sections
- The recycled diagram problem
- Cutler objects to decks that repackage a decades-old software development lifecycle with AI logos added. The visuals suggest novelty without real rethinking of the work.
- Claims that the bottleneck has moved
- The common refrain that the constraint has shifted is presented as settled fact. Cutler questions how much evidence actually supports it.
- Fast-changing methods and false certainty
- New named approaches keep arriving weekly, which makes declaring the matter figured out look premature. The gap between the pace of change and the confidence of the claims is the core tension.
03From the post
“My goodness. If I see another slide with a 2005-era SDLC diagram sprinkled with little AI logos and a bunch of words suggesting “the bottleneck has moved” or that this has all been figured out, when in reality every week there’s something new like Loop Engineering, or _____________.”
04Frameworks mentioned
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.