I don’t disagree in general—certainly UI changes are easier than infrastructure changes—though there is a caveat, illustrated by the old story about the repairman who took a large repair fee to fix a complicated piece of machinery, and then gave the thing a good thwack, whereupon it worked again; to the client’s protestations that such an easy “fix” was hardly worth the hefty bill—after all, all the guy did was hit the machine once!—the technician replied “yeah, but you gotta know where to hit it…”.

So with UX: many of the changes are easy to make, it’s knowing which ones to make and how, that’s the trick of it.

As for what to prioritize—this is something to consider: https://www.nngroup.com/articles/aesthetic-usability-effect/ (though not to try and apply unreflectively!)

Finally, implementation details (including infrastructural ones) can make it harder or easier to make changes to the UI and layout and so on. (For example, the CSS component of the LW 2.0 codebase is a , which makes it actually not very easy to make many of the sorts of changes which should be easy to make.)