Campaign #ForChange is a social service application that lets the user do challenges to support a campaign and make a donation from it
This project focuses on feature improvement to increase user engagements, mainly on new users
Started from problems and solution ideas found within the Remote Working Simulation hosted by Campaign.com, then I take my own approach to translate those ideas into user flow and wireframe for Campaign #ForChange app improvement
I tested my newly-built wireframe prototype into real users to see how the ideas work and gain new insights for future improvement
The first problem discovered is based on my personal experience using the Campaign #ForChange app. For a new user, I feel that there is too much friction on the onboarding process the flow to complete a campaign. Then I planned to redesign this app to be less-friction
The problems I found before was still a biased assumption. I decided to backup what I have found with reflecting at what Campaign #ForChange app compared to the competitors: Kitabisa and BenihBaik. Those applications are providing a kind of similar service: charities and make donations.
First, I want to know minimum steps for new user to onboard into each application and start the first action (which is completing a campaign). I found that Kitabisa needs 6 steps for new user to onboard in the app and start the first action, including login/signup and topic personalization. BenihBaik only needs 2 steps that consisted of login items.
Finally, Campaign #ForChange itself needs 6 steps to onboard the user and let them start the first action. But, compared to Kitabisa, user personalization on Campaign #ForChange app is a little more redundant, such as challenge-choosing method and challenge type. You can check the full documentation here
Second, I summarize the insights I found from each app's flow. Kitabisa have a personalization feature yet provide a straightforward flow for new user. BenihBaik is too straightforward by just providing the user to login/signup (it is not bad, tho). While, Campaign #ForChange app have redundant personalizations compared to Kitabisa.
That's not over. I also found that Campaign #ForChange app home screen is not engaging enough for new user to discover and find the challenges they want. The "metrics" above which Campaign refers as social tracker is nice, but it is too big to accommodate more space for other sections. The tradeoffs are, Campaign #ForChange app, cannot place a categories selector in the 'above the fold' which Kitabisa and BenihBaik can. It also doesn't show a gallery of challenges that new users need to find challenge they wanted right from 'above the fold'
The approach I used here as a designer is Hick's Law where if there are too much choices to be made, users tend to be frustrated. I decided to discount the flows needed for user to onboard into the app by getting rid of redundant personalization. Also, I want user to have a choice to 'skip' challenge when the previous version "forces" users to complete a challenge first before they can explore the other contents inside the app
There is only a minor change I want to apply for Campaign #ForChange app. I didn't make a big change for the pages for onboarding process. Instead, I revamped the home screen layout, especially the content in the 'above the fold' section. I make the social tracker more subtle but still accessible to provide more space. Also, I put the categories selector and carousel of campaigns to encourage new users to take challenges more by making it visible.
I did a quick-testing of the wireframe prototype to one of my friend who doesn’t know anything about Campaign.com yet. In the first phase, I asked him to explore the original Campaign #ForChange app to get him familiarized. Then, I ask him to try the prototype I built to get insights of which version has better engagement for new user
Tested user implies that the home page in the new designed prototype is more intuitive to use. It means that the “above the fold” solution has solved the problem. But, he doesn’t comment much about the revamped onboarding steps. It means either the solution’s impact is too low or it has solved the “noticed problem” so he seems quiet about it.
Minor improvements I offered in this project can potentially increase user engagement. But, it needs more in-depth research and iterations before being assigned to the Campaign #ForChange app’s future development roadmap