Metrics and quantitative ux results in really bad software, making it rigid while optimizing for the wrong things.

The most obvious example is Google creating multiple steps for Login where you have to enter your password after you put in your user.

I wonder what metric lead to that decision or was it a political decision to make it seem like their "old" software has some new feature.

▲

saltcured 20 hours ago | parent [-]

If you mean Google website login, that step is needed because the email address is used to determine which identity provider to use. E.g. I have three different accounts that branch off from that same initial login flow.

One is my person "gmail.com" account, and the other two go through enteprise identity providers related to my employment and their G-Suite licenses. So after I put in one of these three email addresses, I get prompted for the appropriate next step. Only one of them involves giving a password to a Google server. The other two are redirects to completely separate login systems operated by my employer.

	▲	TheLegace 13 hours ago \| parent [-]
		I mean I get it logically makes sense. But it still seems like a waste of time for a small percentage of use cases. Maybe a better approach is put in your login have it automatically detect if it requires an identity provider. Gray out the password to signal to the user password is not necessary and automatically redirect. Less clicking, don't break flow and think of a smoother solution.