Living Progress - Women's Community Savings - Mobile App Wireframe Challenge

Welcome to Living Progress - Women's Saving Group - Mobile App Wireframe Challenge!

This project aims at creating a e-ledger mobile application that helps to simplify record keeping by digitizing it, thereby increase accuracy and improve data security. We are looking for wireframe (axure) solutions based on requirements from our client. We’re also looking to the community to come up with interesting ideas for the workflow - we’re absolutely open to creative solutions!

At the end of this wireframe challenge, we are looking to have a complete solution for the user experience and flow of the application.

This challenge is part of the HPE Living Progress Challenge Blitz Program (Secure top placements in the leaderboard to grab addiitional cash prizes)

Round 1

Initial Wireframe Concepts of the below scenarios for checkpoint review.
01. Dashboard/Landing Screen
02. Saving Passbook (User focused)
03. Savings Journal (Management Committee focused)
04. Loan Passbook (User focused)
05. Loan Journal (Management Committee focused)
06. Request a Loan

Any additional features or screens that will help explain your idea.

Round 2

Final Wireframe Concepts for all given requirements with any checkpoint feedback implemented.
Any additional features or screens that will help explain your idea.

This mobile application (e-ledger) would facilitate the existing record keeping - credits, debits, lending activities, lending calculators, loan repayment schedules, loan tracking, portfolio reporting.

Wireframe Expectations:
- Include wireframe call-outs and notes as required.
- Provide us with your interaction and click-path thoughts and suggestions
- The screens must be very easy to use and intuitive. Keep that in mind when create your solution for the layout and flow information.
- We are focussing on android mobiles, have your wireframes with size 360 x 640px (portrait), Note: height can expand based on content

Problem:
75% of the world’s poorest people do not have a formal bank account. Currently there is a solution to these people and it’s called community-based savings groups (also known as village banks) which are specifically designed and targeted to meet the needs of the rural poor for whom access to even the most basic financial services is extremely limited. 

Client’s award-winning “WORTH Savings-group program” has reached nearly 400,000 women in 14 countries. It is important to understand what this program is about in-order to create this mobile application:
- Poor, primarily rural women get together in groups of 25 with a women’s economic empowerment model that integrates savings-led microfinance, literacy and numeracy, group banking, and micro-enterprise development, while strengthening social networks and empowering women to have a voice in their communities.
- Participants in each of the groups save/credit money on a weekly basis.
- The group’s savings are pooled, managed by the group independently, and available in short-term, low- interest loans to members, primarily for income generation.
- At the end of the six-month financial cycle, interest earned is distributed proportionately to group member’s savings, and members can decide to spend or to save it during the next cycle.

Currently, when the groups come together for their weekly meetings, all of the village bank transactions are recorded in each of the ledgers by hand. Group financial activity is currently tracked through paper, a system which is time-consuming and with greater opportunity for errors. The handwritten updating of ledgers is very cumbersome and vulnerable to errors - those errors, in turn, are very difficult to reconcile across the varied forms. So, there is an opportunity to further improve this program to more effectively serve its participants

Solution - The e-Ledger:
A shift from labor-intensive, handwritten paper records to digital accounting would drastically reduce banking transaction costs and the women’s opportunity costs for WORTH participation. This would also allow the client to enhance and improve existing training on micro-business and capital usage for existing groups while also including more women in the program.

This will be an online system (mobile hybrid app) to simplify record keeping, increase accuracy and improve data security:
- This mobile application would facilitate the existing record keeping - credits, debits, lending activities, lending calculators, loan repayment schedules, loan tracking, portfolio reporting.

Suggested Screens:
Below are some of the screens that we would like you to explore, please feel free to add any other screens that you think would be appropriate.

Each “Women’s Savings Group” nominates their Management Committee. Each Management Committee member has specific responsibilities that will keep her busy during the meeting and for this reason it is important that each member take responsibility for filling out her own passbooks. The Management Committee is made up of four officers - the Chairperson, Secretary, Treasurer, and Controller.

IMPORTANT:
All the below screens would be common to all users (i.e. individual members as well as management committee), but in some screens management committee members could have additional functionalities, we have mentioned the specific functionality the different management committee members will have. So, in-order to show the differentiation - please have separate flows for a Normal user and Management committee user.

01 Dashboard/Landing Screen:
- Recent transactions that were done by them as well as the group transactions that were done would be great to be shown in this screen.
- It would nice to show the “Member savings stats”  that could include the share of village-bank ownership and pending payout; payout includes savings accrued and ROI, which is group interest earned prorated according to share of ownership and provide option to view a detailed account statement.
- Some way to display what the anticipated savings contribution should be ahead of time (ahead of the meeting), and it could also include the group-level cash in-flow from anticipated loan payments as well. These two (anticipated savings deposits and loan payments) combined with any cash-on-hand constitute the funds available for mobilizing in the pending meeting.
- Come up with your ideas for navigation that allows them to navigate to different screens in the app (Savings passbook, savings journal, loan passbook, loan journal, account summary).

02 Saving Passbook (User focused):
- The Savings Passbook has the member’s name and details of her savings transactions in it (similar to bank account statement). Note: We don’t need to show all the past transaction details, probably limit them to show the details of past 90 days or past 7 transactions.
- This saving's passbook records her mandatory, and voluntary savings as well as any withdrawals on a weekly basis. (Mandatory weekly savings contributions are agreed upon with the week. Voluntary is any savings contribution above that amount. Both should be tracked.)
- Saver records their weekly savings on her device and it is transmitted to the Management Committee’s device. There are two different user flows depending on what type of currency they are using (hard/physical cash or e-cash):
- - - - Hard Cash (physical cash in hand): User would input in the app what they want to add to savings. They would hand that physical money to the treasurer. The treasurer counts the money out load (for transparency) and accepts the money entered by the saver in her device which will then be recorded in Savings Journal.
- - - - e-cash (digital cash within the app): This works similar to the Hard Cash user flow. Except the user is not handing over the physical cash to treasurer, instead they are transferring funds directly from the user’s app to the Management Committee’s Savings Journal/ device. The user would still receive a notification as receipt.

Note: Management Committee would see in the Savings Journal who all made their weekly deposits, failure to meet mandatory weekly savings contributions must be recorded, with contingent penalty. So, at the end of the meeting, Management Committee would call out who did not make deposits and would record the penalty in the app under Savings Journal and would transmit that to the save. The same would also then apply to the making of weekly loan payments and penalties for missing a loan payment….We should allow the management committee user to enter their penalty amount for a user in the app and think on how can we show this late penalty for a member? - looking for your ideas!

03 Savings Journal (Management Committee focused):
- This section/ screen is only visible and accessible by the Management Committee
- The Savings Journal is very similar to saving's passbook, it complements the Savings Passbook but records all group members’ savings and is held by the Management Committee, as a backup and consolidated record.
- Transactions (Savings or loan payments) recorded by the members in their device are accepted by the management committee (treasurer), come up with thoughts on how these need to be shown/captured?
- Upon Treasurer’s confirmation of deposit or withdrawals, member’s savings deposit or withdrawal flows into Savings Journal (in case of Loan repayments it is saved in Loan journal).
- Needs electronic signature of accepting Management Committee member.
- Failure to meet mandatory weekly savings contributions must be recorded, how should it be shown?

04 Loan Passbook (User focused):
- The Loan Passbook is each member’s record of her loan taken and also the repayments that were made or scheduled.
- Member records her weekly loan payment on her device and it is transmitted to the Management Committee;
- Treasurer counts the cash out loud and confirms the payment received in the app as the member pays, for group transparency;
- Chairperson (unless absent) then accepts/confirms the transaction received from the person making the payment and it is recorded in both the Loan Passbook and Loan Journal.
- The user receives a notification in their app that the loan payment/ transaction has been accepted/ completed. This notification servers as the user’s receipt. 

05 Loan Journal (Management Committee focused):
- This section/ screen is only visible and accessible by the Management Committee
- The Loan Journal is very much like the Loan Passbook, except as the Savings Journal it records the transactions of all group members.
- It is signed by the member in the presence of the Controller and is kept in the bank as a complement to the member’s Loan Passbook.

06 Request a Loan:
- Loan Passbook loan request and payment transactions should flow into the Loan Journal.
- Members should be able to see who has previously received or has loans outstanding, to facilitate equity in loan issuance.
- Member enters loan, terms and payment; Treasurer confirms in app; interest calculated based upon terms.
- Terms are determined and agreed upon at the group level and are applicable throughout the cycle.
- Interest is calculated based upon group-set rate and is transparently available to member as she makes her loan request.
- Member’s Debtor Agreement (form which they are filling out) is submitted with loan request.  
- Treasurer announces the transaction and counts out the money, after which the Secretary recognizes the loan as issued in the Loan Journal.
- The loan issuance flows into the member’s Loan Passbook, including accepted terms;  

07 Accounts Status/Summary:
- Mini-statements of past few transactions for members;
- Group liquidity statements (cash on-hand, e-wallet and bank balances). The statements would include items like (looking forward to your basic ideas for these below reports and also overall framework for reports screen):
- - - - Balance savings contributions (information coming from Savings Journal section)
- - - - Loan outstanding balances (Information coming from Loan Journal section)
- - - - Loan payments and amounts (Information coming from Loan Journal section)
- - - - How much cash on hand does/ should the group have. This is calculated from savings contributions minus loan payments + anticipated loan payments minus pending loan requests.
- - - - e-wallet/ e-cash balances
- - - - Outside bank balances (regular/ large banks the user might have money with). Money in outside banks needs to be manually input by the management Committee , there is no way to connect the two accounts together. (There also needs to be recognition of excess funds transferred from the groups cash box to external secure depositions -- to banks or to the e-wallet/box.)

New to axure RP, get started right-away!!
Here are some quick tutorials to help you get started http://www.axure.com/support

Target Audience:
- Poor Women Members of the savings group
- Managing Committee (Chairperson, Treasurer, Secretary, Controller) members of the savings group

Judging Criteria:
Your submission will be judged on the following criteria:
- User experience
- Completeness and accuracy of the areas of functionality and content
- How well your wireframes provide a consistent user flow and clear information architecture for the application

Submission & Source Files:
Preview Image    
Create your preview image as one (1) 1024x1024 JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.

Submission File
Generated HTML files with all the requested contest requirements stated above.

Source Files
Wireframes should be built in axure. The resulting files should have generated HTML files. Also, all the content must be listed and the pages are linked together to show page flow.

Final Fixes
As part of the Final Fix phase, you may be asked to remove, update, or change some features of the wireframe.