Personal details


34
views
0
11 weeks ago by
Link to the audit of existing personal details patterns:
https://digital.westpacgroup.com.au/confluence/display/CPL/Forms+-+Personal+details

1. Upload examples of what you've used for your project (and what worked/didn't work)
2. Comment on the patterns that are posted below (and why you think it works, doesn't work)

- - -

The audit showed that there are generally 4 parts to capturing personal details:

1. About you
2. Contact details
3. Address details
4. Employment details

Sometimes these were all in the same section, or sometimes they were sub sections of the personal details page.

Currently looking at it as a bigger pattern as opposed to the individual, smaller patterns that make it up (eg. date of birth) - need to establish boundaries (where does the pattern start and end).

5 Answers


0
11 weeks ago by
About you

About you tends to capture:

  • Title
  • Name
  • Known by any other name
  • DOB
  • Marital status
  • Gender (Title can help capture this too)
  • Tax info
  • Employment type
More often than not, the 'About you' section appeared on the second step of the form, after the user provided product/finance details. However, if it was a short form, it tended to appear on the first page.

Recent trends also show that some forms are placing name and email at the very start of the form and then pre-populating these two fields when the customer reaches the About you section (for drop-off reengagement or save for later purposes).

About you, example 1:

 

About you, example 2:
Also includes contact details


About you, example 3:
Also includes contact and address details

0
11 weeks ago by
Contact details

Contact details tends to capture:
  • Phone number (sometimes with an ability to add another)
  • Email

Contact details, example 1

 

Contact details, example 2

 

Contact details, example 3

 

 

0
11 weeks ago by
Address

Address tends to capture:
  • Residential address
  • Mailing address
  • Length of time at this address

If address was a single field with auto suggest it tended to be in the 'About you' section.
On the other hand, if Address capture had multiple fields, it tended to be in it's own sub-section called 'Address' or 'Residential address'

Address, example 1
Single field, auto suggest

 

Address, example 2

 

Address, example 3

 



0
11 weeks ago by
Employment details

Employment tends to capture:
  • Employment type
  • Industry
  • Occupation
  • Employer
  • Length of time with this employer
Employment, example 1

 

Employment, example 2

 

0
11 weeks ago by

Hi Am

Ha. Took me a while but i found the upload image button. Here are the current designs we are proposing to use for the CSH program.

Thanks

Brad




 

 

Please login to add an answer/comment or follow this question.

Similar posts:
Search »
  • Progress stepper
    Link to the audit of existing stepper patterns: https://digital.westpacgroup.com.au/confluence/di...
  • Placeholder text
    Link to the audit of placeholder text patterns: https://digital.westpacgroup.com.au/confluence/di...
  • Validation - success
    Link to audit and desk research: https://digital.westpacgroup.com.au/confluence/display/CPL/Valid...
  • Mandatory & optional form fields
    Link to audit and desk research: https://digital.westpacgroup.com.au/confluence/pages/viewpage.ac...
  • CTA button group (group of call-to-action buttons)
    Link to audit and desk research: https://digital.westpacgroup.com.au/confluence/display/CPL/Forms...
  • Help text
    Link to audit and desk research: https://digital.westpacgroup.com.au/confluence/display/CPL/Help+...
  • Loading pattern
    Link to the loading pattern audit: https://digital.westpacgroup.com.au/confluence/display/CPL/Loa...
  • Search pattern
    1. Upload examples of what you've used for your project (and what worked/didn't work) 2. Comment ...
  • Mobile Wallet (AKA Tap n' Pay)
    1. Upload examples of what you've used for your project (and what worked/didn't work) 2. Comment ...
  • Validation - errors
    1. Upload examples of what you've used for your project (and what worked/didn't work) 2. Comment ...