By not allowing users to make mistakes or give them flexibility

I am working on a product that should be easy to use and easy to configure, competition to a large extent requires a long setup period, and in some cases comes to an individual solution for each client. One part of our application is now expanding based on customer requests, and it looks like we will need to make it very flexible so that each client can have a lot of control over how it behaves. The problem is that I do not want the system to be too customizable, as I believe that this complicates the learning process and work. I’m also worried that he is opening the door to someone, confusing something for himself, sort of giving them a gun, although I don’t actually point him at their foot for them.

Has anyone else encountered a similar dilemma in putting power in the hands of users? How did you solve it? and what was the result?

+3
source share
10 answers

I usually don’t like subscribing to the idea that all users are stupid, but there is a rule that can still be applied:

If you give them an opportunity, they will break it

Now it's up to you to give you the opportunity to do potentially dumb things. Or better yet, design it so that when they make the stupid voodoo that they do, it can be undone or restored from the error state gracefully.

+5
source

Joel , , , .

, , :

, , .

. , .. , , , . , Clearcase PVCS, - 90% - , .

.

, , , . .

+4

TurboTax (http://turbotax.intuit.com/). , , --- , , , .

, , 80% , .

+2

. . ol 1040 , .

, , :

, ; , ; , .

( , , , , , , related ).

. , , , .

. , .

. , , , , .


, . .

+2

:

  • .

  • , ( , ). , , , ---- .

, .

+1

, , .

. , : ( ) ?

, -, , , , , , , . , , , .

, , , .

+1

, . , . , , , ( , ).

, , , .

, .

0

Jeff Atwood . .

0

Firefox . , : config. , , .

0

, , . , ( , ), , .

0
source

Source: https://habr.com/ru/post/1706398/


All Articles