Pattern 39: Exploit closure [Abstract]
AKA:

How to you ensure that users complete a set of related tasks or transaction?

Therefore

When designing workflows for your site decide what is the main task and force the user to complete necessary subsidiary tasks first. Provide FEEDBACK (41) as the various tasks are completed.

Next, consider ACCEPTABLE WORDING (50) in the way you give these instructions and confirmations.

An important principle of user interface design that derives from an understanding of psychology is exploiting closure. We are all familiar with the ‘I came in here for something but can’t remember what’ syndrome. It occurs because of the human tendency to be satisfied with tasks once we have achieved closure in one respect; we tend to omit completing ancillary tasks. This is why most bank ATMs make you take your card before taking the money. The alternative sequence is likely to cause errors because once you have the cash (closure of main task) you are likely to depart, forgetting the card and receipt. Unfortunately for the street sweepers the same principle is rarely applied to the receipt as well.

Browse the language	What is Wu?	Look at an example pattern sequence	Structure of the patterns
Comment on Wu	Contributors	Return to TriReme home page	Links to related sites