Skip to main content
Commonmark migration
Source Link

1. Get user consent

Recording usability sessions should not be a huge concern if you have good security policies in place to protect the information you collect. You must to have your participants agree to the procedure. You can find sample consent form [here][1]here.

2. Allow the user to provide fake info

To further ease concerns that the user may have about their private information, you can either let the user provide fake information about themselves during the usability test, or you can provide fake information for them. Consider the affect this will have on the user going through the flow. [1]: http://infodesign.com.au/usabilityresources/usabilitytestingmaterials/

1. Get user consent

Recording usability sessions should not be a huge concern if you have good security policies in place to protect the information you collect. You must to have your participants agree to the procedure. You can find sample consent form [here][1].

2. Allow the user to provide fake info

To further ease concerns that the user may have about their private information, you can either let the user provide fake information about themselves during the usability test, or you can provide fake information for them. Consider the affect this will have on the user going through the flow. [1]: http://infodesign.com.au/usabilityresources/usabilitytestingmaterials/

1. Get user consent

Recording usability sessions should not be a huge concern if you have good security policies in place to protect the information you collect. You must to have your participants agree to the procedure. You can find sample consent form here.

2. Allow the user to provide fake info

To further ease concerns that the user may have about their private information, you can either let the user provide fake information about themselves during the usability test, or you can provide fake information for them. Consider the affect this will have on the user going through the flow.

deleted 83 characters in body
Source Link

1. Get user consent

Recording usability sessions should not be a huge concern if you have good security policies in place to protect the information you collect. You must to have your participants agree to the procedure. You can find sample consent form [here][1].

2. Provide "fake personal info" thatAllow the user can reference in the usability testto provide fake info

To further ease any concerns that the user may have about their private information, you can either let the user providing any realprovide fake information about themselves that is secureduring the usability test, or you can provide "fake"fake information for them to use. You just need to describe to them to "pretendConsider the affect this is your information for xyz" and when they get to fill in those parts of your software they referencewill have on the information you provideduser going through the flow. [1]: http://infodesign.com.au/usabilityresources/usabilitytestingmaterials/

1. Get user consent

Recording usability sessions should not be a huge concern if you have good security policies in place to protect the information you collect. You must to have your participants agree to the procedure. You can find sample consent form [here][1].

2. Provide "fake personal info" that the user can reference in the usability test

To ease any concerns about the user providing any real information about themselves that is secure, you can provide "fake" information for them to use. You just need to describe to them to "pretend this is your information for xyz" and when they get to fill in those parts of your software they reference the information you provided. [1]: http://infodesign.com.au/usabilityresources/usabilitytestingmaterials/

1. Get user consent

Recording usability sessions should not be a huge concern if you have good security policies in place to protect the information you collect. You must to have your participants agree to the procedure. You can find sample consent form [here][1].

2. Allow the user to provide fake info

To further ease concerns that the user may have about their private information, you can either let the user provide fake information about themselves during the usability test, or you can provide fake information for them. Consider the affect this will have on the user going through the flow. [1]: http://infodesign.com.au/usabilityresources/usabilitytestingmaterials/

Source Link

1. Get user consent

Recording usability sessions should not be a huge concern if you have good security policies in place to protect the information you collect. You must to have your participants agree to the procedure. You can find sample consent form [here][1].

2. Provide "fake personal info" that the user can reference in the usability test

To ease any concerns about the user providing any real information about themselves that is secure, you can provide "fake" information for them to use. You just need to describe to them to "pretend this is your information for xyz" and when they get to fill in those parts of your software they reference the information you provided. [1]: http://infodesign.com.au/usabilityresources/usabilitytestingmaterials/