[bena]

I'm not a UX developer by trade, but I've had to develop UX in my time so I've picked up some things.

It's not about how fast you get to something.

You talk to users and they will go on and on and on about "clicks". Anyone talking to you about the number of clicks doesn't understand UI let alone UX. Making everything "one click" away is how you get those massive button interfaces. It's just information overload and even harder to navigate than something that would take more clicks to navigate.

Another way to think about this is that a book takes many "clicks" to write. And a book that was written in one "click" wouldn't be good to read. Some long books are quick to read and some short books take forever to read. Flow is way more important than number of actions.

Realizing that always shooting for "easier" is a mistake.

Things must flow. Except where they shouldn't. Sometimes you want to actually put in resistance. Sometimes you want to make sure that what a user does is actually what they want to do. You want them acting with purpose and intention. If something has a large effect on the system, you want people to not accidentally do that. The best way to do that is to make it slightly involved.