> This might be okay for consumer apps, but maddeningly, the same doctrine gets applied to enterprise applications as well
I think this is a great point. I was consulting with a customer and their key goal in a complex system that had a time-sensitive user workflow was "minimise clicks".
I said to them that that makes sense, but saving 0.5s on a click every two hours is not as impactful as (insert example of a change that would speed up the workflow by 10 minutes every two hours).
And it's as you say: they come from the consumer world, where minimising clicks keeps customers involved. But it's not the only thing to consider.
I think this is a great point. I was consulting with a customer and their key goal in a complex system that had a time-sensitive user workflow was "minimise clicks".
I said to them that that makes sense, but saving 0.5s on a click every two hours is not as impactful as (insert example of a change that would speed up the workflow by 10 minutes every two hours).
And it's as you say: they come from the consumer world, where minimising clicks keeps customers involved. But it's not the only thing to consider.