Connecto generates reports for users to review and make business decisions. It’s in the early stages of development and doesn’t utilize an API to transmit data, so users must manually feed information into the system by uploading XML files, which get parsed and distributed into new reports.
When a user uploads a file that contains a parsing error, it prevents ingestion, and they’re unaware that the affected file didn’t upload in the app and assume it is functioning as expected.
The solution provided users with a summary of the upload, the ability to fix errors, and removed development team resources from the process. It saved time, eliminated confusion, and gained users’ confidence in the application.
Users informed the product team that they received an error message when uploading files into the system. However, they noticed that some reports were distributed to the table.
I conducted user interviews to learn about their experience.
To integrate data into Connecto Application:
I synced with the development team and asked the questions below to understand how the process worked on the backend.
Questions for Dev:
Parsing Process (Backend):
I used the insights to define a persona to understand the target user and provide a better context for me to solve their problems.
I explored a few solutions and shared them with the team.
What would the next steps look like for users?
We decided to move forward with displaying upload information and allowing users to resolve issues.
There were 2 Paths that I had to consider for the flow – uploads that have errors and uploads without errors:
Uploads with Errors
Uploads without Errors
Before landing on the final wireframes, I presented and tested them with stakeholders.
After several iterations, I moved forward with high-fidelity designs.
I incorporated feedback into the final designs and provided annotations in the files handed off to the development team.