Story
Daniel is a 30-year-old UGA graduate that enjoys cross fitting, going to the lake to wake board, and sharing laughs over a few drinks. He is very involved within his community, volunteering at varies events though out the year. He is also involved with the local church in his city, he loves volunteering his time there but doesn’t think the church really needs his money, so he would rather give elsewhere.

He is very passionate about non-profit organizations such as the Aids Walk, friends going on mission trips, food drives, homeless outreach, etc. He is motivated to give to a cause and see the results of his efforts versus giving to the church and not really knowing what the money is being used for. With this mind set he doesn’t end up giving often, weeks will past where he doesn’t come across a friend or company that sparks his interest. He wants to get more involved — not only with his time but with his money.

Pain Points
1. Has to accumulate, then calculate his earnings.
2. Bad at saving and setting money aside.
3. Cannot find places to volunteer or serve.
4. Doesn’t know where his money is going after giving.
The main goal of the flows is to figure out what screens are needed within the app. The first go around I did them wrong. I did not add the system operation in the triangle. So instead of having 6 screens I really had 12 screens. When revisiting the flows I noticed I did not need as many screen as I had in the previous version. I began to simplify the steps and really understand what the user would do next based on my first flows. I went from the original 12 screens to only 6. I do think these numbers will change after the usability test, but for now I am pleased with making the user go through half as many steps as I originally planned.
The first screen is a login screen. I feel as though the user needs to have a profile for this app, to set up all the information that goes into it. I heard tons of feed back on the first screen, “I would never log in with Facebook” or on the other hand “Oh, that makes sense, and it’s a lot easier to log in with Facebook. I think providing back options will be crucial.
For the second screen I decided to hit the user with something personal right away, asking what is their interest? I think it is a great way for the user to interact with the app before asking or putting any information in. As they click and scroll through the “interest page” the ones chosen will grey out and have a check mark over them.
Once hitting the bottom of the screen or the user scrolls up a “next” button will appear across the bottom of the screen.
After clicking next, it will ask you if you would like to volunteer your time or donate?
After clicking “money” it will ask you what your two week wage is?
After inputting your wage this screen will appear and ask you to slide to show giving options. When you slide, it will show you the percentage and money amount. When landing on the amount you want to give the done button will either appear or change colors.
Based on your previous selection of interest the system will process non-profit organizations within your interest. The user can scroll thought and click on any organization that sparks their interest. When the user clicks or tries to slide, this over lay will pop up reminding them they have 2% of their two week wage to give.
After clicking on any said organization it will take the user to their profile. Including an image, subhead, goal meter, description, up down buttons, percentage of giving, and lastly the give button. When you click on the up arrow the percentage will appear in the middle box. When ready to give, you push the GIVE button and the next screen confirms the donation.
Observations
After hearing all the feedback from the prototyping I am encourage, feeling as though I am heading in the right direction. Don’t get me wrong, I probably will change every screen and order of each screen after it, but hearing people say, “I would so use this” is a good sign. The one thing that stuck out to me the most from all the feed back was all the different opinions and view points. Some people would give blindly if they are interested enough, while wouldn’t give a penny unless they know exactly where the money is going.
     The most consistent feed back I received through out the tests was a way of making the user feel appreciated after donating time or money. Do something that rewards them for there time and effort. A reward or a feeling of appreciation can come in many different shapes and sizes. That is one part I am still puzzled as to what I am going for my final implementations.
     There are many things I didn’t think through or take into consideration when going through my flows and sketches. A lot of these issues/opportunities were brought to my attention. One big one was, why use percentage of giving instead of a money amount? It gets confusing when talking about the users percentage and the companies percentage. Why not just use a dollar amount and let that dollar amount translate into real world things. For example if the non-profit of choice is Atlanta Mission, and you go to give instead of showing the percentage of giving you could show the amount of people you would reach by scrolling left to right. Simulteneously seeing the amount you would give and the lives you would impact by your donations.
Conclusions
I learned a valuable lesson from prototyping for the first time. User feed back is an essential part in creating an app. With hearing and seeing people go through your app without any prior knowledge of your concept. After talking with a variety of users I came to many conclusions; first always listen before chiming in. I found myself interrupting the users when they were trying to give me valuable feed back, defending my thinking instead of accepting their thoughts and suggestions. Second, watch where the users tap. So many times the users would be tapping and trying to find how to go to the next screen, most of the time it was in the lower half of the screen which is most easily accessed. Third, people want to relate to your app. So many people mentioned; huh, this makes sense! I would actually use this to give to organizations.
Next Steps
After going through multiple stories and pain points in every day life I feel as though I have landed on a story and concept that I am passionate about designing. The next step is to take what I have learned from this experience and build on what I have that will makes sense and people will feel comfortable and passionate about giving. I will put the organizations before the money. People want to see what they are giving to rather then giving and then picking their organization. I also want to intergrate a place that they can share their experience with their peers after giving. I look forward to users going through the updated sketches and flows and seeing the progress.
Benefits
When researching apps and thinking through my concepts, my initial thoughts were to create an app that allowed users to tithe and budget their money within the church.  After speaking with a handful of people I started noticing a trend; people want to know where there money is going. When attending a mega church people throw this statement around a lot “does the church really need my money?” Whether this is true or not people feel as though their minimal tithe and offering won’t make a huge impact within the church and are looking for answers outside the walls of routine and tradition.
Purpose Statement
The purpose of this app is to provide an alternative way to give. This will create a more interactive way for people to connect to organizations of their choice and stay connected after the initial donation.
Brag Points
1. Customize your organizations based on your interests.
2. Easily calculates your giving.
3. You know exactly where every penny is going.
Back to Top