Designing consent within a Data Recipient software application
FeaturedAuthor
Regional Australia Bank
Description
If you're faced with the challenge of designing a Data Recipient (DR) application that involves consent flow, this guide will help you.
It includes links to wireframes, screen designs, mock-ups and other extensive creative assets that were created as part of the development of Regional Australia Bank's initial online lending CDR use case.
Regional Australia Bank worked in partnership with Greater Than Experience to plan, design and implement the online lending CDR user experience.
https://www.greaterthanexperience.design/
Audience
Customer Experience, Customer Engagement, Legal, Compliance, Risk and Digital teams.
What's Included?
What's it look like?
We've used illustrations, icons and hopefully an engaging, simple content style to ensure the result appeals to a wide consumer audience. Multiple options for elements of consent are provided in the wireframes.
We aimed for good Readability of all content based on the Hemingway app - which is free - throughout.
http://www.hemingwayapp.com/help.html
How do I use this?
The visual assets, wire-frames and end to end experience designs are included to show you the approach that Regional Australia Bank used to create the Data Recipient CDR consumer experience that was launched on 1 July 2020.
These assets are provided to help kick-start and accelerate your own development work as a Data Recipient.
The use case for these designs is Online Lending and design outputs are based on v 1.3 of the CX Guidelines.
Conditions of Use
These resources are provided freely for anyone to use. They are provided without any warranty or assurance of completeness. No credit or reference to Regional Australia Bank as the original author is required.
If you enhance or further develop these templates or create a different approach, you are encouraged to publish them on this site so everyone can benefit.
-
Okay, so this has been my bread and almond butter for years. ❤️ the fact that this stuff is being shared openly.
Something that feels like it's missing is a more robust description of the consumer outcome focused metrics, how to design for them, how to test them etc. This video will help with that: https://youtu.be/pNp5p__CS00
Ultimately consent is only consent if ewe can evidence the action was informed, freely given etc.
I also know Mike and the CX team have pulled together some great stuff. More here: https://www.notion.so/Data-Standards-Body-Phase-3-CX-Metrics-f494e325d76c44deb2d7f014e22b6186
Please sign in to leave a comment.
Comments
1 comment