[TheOtherHobbes]

If you have the infrastructure to manage multiple versions and collect and analyse related information, adding/removing a blinking cursor or any other UI change and analysing the results should be trivial, because most of the process should be automated. Even in multiple territories and/or different user demos.

Unless you're reinventing the wheel for each modification.

[fivea]

> If you have the infrastructure to manage multiple versions and collect and analyse related information, adding/removing a blinking cursor or any other UI change and analysing the results should be trivial (...)

What leads you to believe in that? I mean, you have zero insight or understanding how things work or were designed. You have zero idea of where that blinking cursor comes from, let alone who owns that particular bit of code.

Let's think things through for a moment. Let's imagine you're talking about a blinking cursor in a random page from Google or Amazon. These are organizations where you have teams owning small widgets that show off only in specific pages, and that the page that you see in your browser come from a lengthy page engine pipeline that has all sorts of tests and failsafes, not to mention regional and localized deployments managed by whatever deployment policy.

This doesn't even take into account the whole workflow from product managers, who often demand data on the impact of touching a button.

You don't just edit a HTML file and hit save, don't you?