UX decisions made only at the interface level optimise for surface over system. The real choices happen upstream: what the user is trying to do, where the product meets their life, what friction they’re running into. These can’t be resolved by adjusting a button. Treating UX as a UI task confines it to a layer where it has limited leverage, cut off from the constraints that [[Design is scaling]] manages at the architectural level.
Pulling the conversation down to the interface too early is how you end up refining the wrong thing. [[Solve the problem not the feature]] gets lost here: the feature gets polished while the underlying friction goes unexamined. Keeping UX at the product level means asking what the user is actually trying to accomplish before deciding how any screen should behave.