Understand the different demands and constraints which both technical and non technical team members were facing.
Get to see people in the environment where they perform tasks
Able to pick up on details the user might not be aware of
The current process of manually requesting data from the devs is time consuming for both technical and non technical teams.
Data comes back raw in the format of spreadsheets. This makes it harder for users to understand.
Working remotely and asynchronously means time is always of the essence, and waiting on people outside of expected workflows is inefficient.
One of the key issues faced for team members was the way the data was represented by default.
The data was raw and took time to synthesise for both technical and non technical team members.
Below are examples of what the data looked like in the database.
I learned a lot about data representation and the importance of clarity in conversation and representation data. I learned about how different team members will use the same data for different things.
More in depth, dynamic data representation and interaction
Allowing users to view and interact with a data set in multiple ways would give them multiple perspectives on on their data which may aid in better decision making.
Sharing features and snippets
The ability to have sharing features for the dashboard would allow for better collaboration in decision making and expression of ideas; especially for asynchronous teams
This project although simple, was not easy, I enjoyed the challenge of learning about data representation and adding it to my locker. I feel I have grown through this project by builing such bespoke tools for a niche community