Take the 2-minute tour ×
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It's 100% free, no registration required.

Is it advisable to notify a person for remove operations such as rejection, delete, removals, etc. For example, if I share to someone a document and later on if it's removed. Should it be notified to that person.

Other examples are if a person sends me a friend request and if I reject, do any notification has to be sent.

share|improve this question
    
I don't know about how others seeing this question would perceive it, but for me it's not complete. Please elaborate. –  AndroidHustle Mar 9 '12 at 9:33
2  
Can you expand on what you mean here? This isn't a specific question that can be given an answer at the moment. Can you add in some context and more details please. –  JonW Mar 9 '12 at 9:40
    
For example, if I share to you a document and I remove it later. –  krishnajay Mar 9 '12 at 9:42
    
Also consider the rejections in case of friend requests, invitation to join a group, etc. –  krishnajay Mar 20 '12 at 6:07

3 Answers 3

notify and allow undo (if possible, otherwise warn before if the operation is not reversible).

Follow Never Use a Warning When you Mean Undo

share|improve this answer
    
Note that I had read and answered this before the question had been changed to reveal that: the person that does the removal isn't the person to be notified but the person that was removed. In which context this answer doesn't make as much sense. –  Dan D. Mar 11 '12 at 12:29

Yes,simply because people like be in control of their actions and be aware of the current state of the system (Neilson's heuristics). By taking that power aware ,you are opening your system to potential issues causes by people accidently making mistakes and deleting stuff which they didn't want to.

These are the heuristics which I was referencing to :

Visibility of system status The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.

Error prevention Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action

User control and freedom Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.

share|improve this answer

Yes it is advisable to notify a person(or a complete team) for any failure, success, rejection, approval in every term. suppose you sit in an exam and you did the basic things, how will you come to know that you are pass or fail? someone have to notify you that you score this much in the exam,

There is kind of Action and Reaction, you did something and everyone who is concerned with the thing should be notified about the action.

if there is a mail undelivered we got an error (notification) in gmail, that the mail is not delivered to the recipient. so user is informed(notified) about the failure if gmail don't provide such notification how would user know that his mail is not delivered.

and what you have said in your comment

For example, if I share to you a document and I remove it later.

system should notify that the document has been removed by user, by doing this both will be informed about the action.

share|improve this answer
    
Internet mail delivery is "best effort", not "guaranteed delivery" - display of an error message (say, by Gmail) is only possible if the mail relay that failed delivery decides to send us a notification of the error. Not all relays do - many don't, by policy, to avoid encouraging spammers. –  Bevan Mar 10 '12 at 4:12

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.