Reporting data with Excel templates + email is manual, repetitive, confusing, and error-prone.
A webapp that guides users and automates + validates data handoff.
Circle K International (CKI) is a collegiate student-led organization that does community service.
Each month, the higher-ups want to know what each college's chapter has done.
3 software developers + 2 managers
As the sole designer for the project, I conducted user research and designed product.
Low fidelity UI
July 2018 to February 2019
I conducted ethnographic discovery and spoke with stakeholders to collect feedback about the existing solution.
"pretty confusing...organization [of information] that you have to figure out yourself"
"repetitive...could be simplified, especially...where data [are] manually copied"
"works, but it's very inefficient, both visually and functionally”
Previously collaborating directly with users gave me additional insight to easily empathize.
I synthesized discovery results into four problems with the existing solutions.
Steep learning curve
Training ~60 chapter representatives each year is difficult and often inadequate.
Data were disconnected between workbooks, requiring repetitive work.
One such instance: each month, ~60 reports from individual chapters are manually downloaded from email and aggregated onto another report.
Cells on the template are inconsistently locked, requiring the users to be cautious about which cells they edit.
This greatly adds to the cognitive load of Excel novices, who are afraid of messing up formulas.
Almost all users fall into three groups.
need to collect individual event reports to compile a monthly summary report, with minimal redundant work.
They also need to view trends and receive feedback from the District.
need to view parsed reports and analyze performance without manually downloading and scrutinizing each report from their email.
need to be able to effortlessly create and submit reports about events they organize.
The existing Excel template was used as a starting point to the designed solution to make the transition as seamless as possible.
The input fields should be organized so that they would be familiar to users of the existing solution while maintaining best web design practices to minimize cognitive load.
Demonstrative onboarding would effectively replace the user manual by walking new users through an example report.
Currently, emailing files implicitly and simply managed access to files.
The nature of webapps requires user accounts and explicit permission management to ensure appropriate access to view or share data.
Based on these findings, we hypothesized that a web app would enable all users to effortlessly complete their core flows by automating all the difficult, repetitive, manual, and error-prone tasks.
Low fidelity layouts
These low fidelity layouts focus on the data entry structure to ensure a smooth transition and quick onboarding and role management to ensure that each user group can accomplish their necessary goals.
The original objective was to ship an MVP. However, due to a lack of development resources and reprioritization of projects, the project was postponed.
The next steps would’ve been to conduct usability testing with the mockups to iterate on usability.
This was my first comprehensive product thinking project that was entirely centered around the user, their needs, and their painpoints.
It felt natural to empathize with them to understand how the current solution fell short of their needs and helping them imagine an ideal solution. ※