It's not about "knowing best" in that case, it's about familiarity and reducing cognitive load. When someone picks up a new piece of software, they have to fig

It's not about "knowing best" in that case, it's about familiarity and reducing cognitive load. When someone picks up a new piece of software, they have to figure out 1) does it solve their problem, 2) how do they use it, and 3) how do they solve their immediate problem with it? When you have familiar UI elements, actions, terms, and explanations, you can speed along Step 2 for minimal effort. If you introduce new interactions and ideas, you're adding a Step 2b that will not pay off in the short term. It might in the long term, but not right now. Every question, struggle, etc that you put in front of a user is one more reason to not use your software. Some users really NEED it and will overcome everything but that's not something to bet on.