# TBM 450: The Loss of Positive Friction

DevFeed: [TBM 450: The Loss of Positive Friction](<https://devfeed.tech/articles/tbm-450-the-loss-of-positive-friction-122381.md>)

Original publisher: [Read original article](<https://cutlefish.substack.com/p/tbm-450-the-loss-of-positive-friction>)

Author: John Cutler

Published: 2026-11-07T23:03:14Z

Content type: opinion

Language: en

Sources: [The Beautiful Mess](<https://devfeed.tech/sources/the-beautiful-mess.md>)

Topics: [pair\_programming](<https://devfeed.tech/topics/pair-programming.md>), [human centric design](<https://devfeed.tech/topics/human-centric-design.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [attention](<https://devfeed.tech/tags/attention.md>), [constraint](<https://devfeed.tech/tags/constraint.md>), [multiplayer](<https://devfeed.tech/tags/multiplayer.md>), [product-development](<https://devfeed.tech/tags/product-development.md>), [reflect](<https://devfeed.tech/tags/reflect.md>)

## AI overview

Constraints can both slow work and improve its outcome by creating time for reflection, shared understanding, and course correction. The author argues that removing product-development friction--such as ROI reviews, remote pairing, and multiple rounds of document revision--can also remove those benefits. AI tools can turn a customer-call transcript into deployed changes quickly, but that speed may bypass questions about customer intent, design durability, and whether the work is worthwhile. The practical takeaway is to deliberately make room for those checks and team reflection, especially as AI-assisted workflows make solo work and immediate output easier.

## Source excerpt

A constraint can be "enabling" and "limiting" at the same time.