Future of Data Sharing
Designing better applications for financial data sharing using Account Aggregators
About the project
Future of Data Sharing (FoDS) is an initiative by D91 Labs and Facebook to design a UX playbook for consented data sharing within Account Aggregators. Data Portability is an area of focus for Facebook. In 2019, they have published a white paper on the same, and recently have included Data Portability in Facebook's developer tools. Under the broader umbrella of Data Portability, this project delves deeper into understanding motivations and challenges in sharing personal data with financial institutions through qualitative research and subject matter expert discussions.
The results from the research exercise have been dissimilated into six design principles for anyone developing data sharing workflows using account aggregators. These principles are addressed to product, business and design teams at the fintech startups, to help build trustworthy financial products.
6 Design Principles of Data Sharing
Download the full report as PDF
DESIGN PRINCIPLE I
Establish authenticity to gain trust
Establish association with governing bodies granting the license and banking institutions to gain trust. This eliminates skepticism and allows users to try out the app with better confidence.
DESIGN PRINCIPLE 2
Provide contextual information
Educate your users with a short introduction about what Account Aggregators (AA) are and how they function. Break down the educational material into shorter snippets and surface them contextually to reduce cognitive load. For low literacy users, increase accessibility to the provided information by converting them into images, audio, video.
DESIGN PRINCIPLE 3
Nudge to make relevant choices
Empower users with relevant timely nudges that would ease their decision making process and eliminate fear of making a mistake.
Break down larger activities into smaller tasks for the user to act upon without cognitive overload.
DESIGN PRINCIPLE 4
Enable data sharing controls
Segregate your data requirement into mandatory and optional financial information. Educate users about why optional financial information is required and how it would benefit them.
Allow your users to pick and choose the financial information they posses or the ones they are willing to share.
DESIGN PRINCIPLE 5
Establish grievance redressal workflows
Surface customer care numbers and help desk chats at every possible touchpoint. Establish human contact through service executives who could help the users with their queries. Create support and help modules in native languages or through videos that could be accessible by the larger set of users.
DESIGN PRINCIPLE 6
Provide visual cues
Provide visual cues about the kind of financial information that is being pulled from Financial Information Providers (FIPs). Communicate reasons for errors and waiting time during the data sharing. Pinpoint the system responsible for the delay and further actionables that a user could perform to resolve them. Enable double confirmations at touchpoints where the user makes critical decisions. Notify the user every time whether the data being pulled is successful or not.