deep data portal
New method of data collection for on-field researchers.
New method of data collection for on-field researchers.
This project is a continuation of the bioacoustics research phase to develop tools that contribute to wildlife conservation. After developing a mobile app (link this to DeepData Capture) for data collection in the field, we designed a companion tool to import, store, and analyze acoustic data using custom-trained AI models. As the sole UX/UI designer, I was responsible for the entire design process. This included creating an intuitive interface for researchers to manage large datasets and visualize AI-generated insights.
This project is a continuation of the bioacoustics research phase to develop tools that contribute to wildlife conservation. After developing a mobile app for data collection in the field, we designed a companion tool to import, store, and analyze acoustic data using custom-trained AI models. As the sole UX/UI designer, I was responsible for the entire design process. This included creating an intuitive interface for researchers to manage large datasets and visualize AI-generated insights.
Role
UX Designer
Information Architect
User Researcher
UX Designer
Information Architect
User Researcher
Duration
3 months
Team
James Yab (Team Lead)
Daan Eeltik (App Developer)
Muhammad Fattash (Programmer)
Jaime Pena (Programmer)
Rafay Chaudry (Programmer)
Utsav Das (Programmer)
James Yab (Team Lead)
Daan Eeltik (App Developer)
Muhammad Fattash (Programmer)
Jaime Pena (Programmer)
Rafay Chaudry (Programmer)
Utsav Das (Programmer)
THE PROBLEM
THE PROBLEM
What do we do with the data after we collected it?
What do we do with the data after we collected it?
Since this is a continuation of the bioacoustics research project, we needed a platform to store the data & organize it for further analysis. Researchers were struggling to organize and analyze audio datasets collected from the field. Without a centralized platform, insights were lost in fragmented workflows. After further discussion, we opted to create another internal software tailored to our organization’s research needs.
Since this is a continuation of the bioacoustics research project, we needed a platform to store the data & organize it for further analysis. Researchers were struggling to organize and analyze audio datasets collected from the field. Without a centralized platform, insights were lost in fragmented workflows. After further discussion, we opted to create another internal software tailored to our organization’s research needs.
Diagram of workflow after data collection
BRIEF
BRIEF
Requirements of desktop application
Requirements of desktop application
The research and engineering team handed me a detailed requirements document based on fieldwork from the Osa Peninsula Bioacoustics Project. My job was to translate their technical needs into something researchers could actually use in the field.
Key priorities I identified:
Clear visualization of AI-analyzed bioacoustic and image data
Interactive mapping to show sensor locations and field data
Scalability to support multiple ecosystems and conservation projects
I used these priorities to design an intuitive interface that could handle complex data without overwhelming researchers working in remote settings.
The research and engineering team handed me a detailed requirements document based on fieldwork from the Osa Peninsula Bioacoustics Project. My job was to translate their technical needs into something researchers could actually use in the field.
Key priorities I identified:
Clear visualization of AI-analyzed bioacoustic and image data
Interactive mapping to show sensor locations and field data
Scalability to support multiple ecosystems and conservation projects
I used these priorities to design an intuitive interface that could handle complex data without overwhelming researchers working in remote settings.
Summary of Technical Requirements Brief
goal
Based off of the provided feedback and the requirements, how might we create a desktop tool that transforms raw expedition data into clear, actionable insights for wildlife conservation?
IDEATING
IDEATING
Putting pen to paper
Putting pen to paper
Facing a creative block with so many requirements, I switched to pen and paper. I mapped out the information architecture first; imagining how researchers would move through projects, ecosystems, data analysis, and maps. Once I understood the workflow, I sketched layout options to visualize how everything could fit together. Working traditionally helped me think through the complexity before committing to digital designs.
Facing a creative block with so many requirements, I switched to pen and paper. I mapped out the information architecture first; imagining how researchers would move through projects, ecosystems, data analysis, and maps. Once I understood the workflow, I sketched layout options to visualize how everything could fit together. Working traditionally helped me think through the complexity before committing to digital designs.
DESIGN
DESIGN
Main features
Main features
With so many features and requirements to organize, I kept the main navigation to 5 tabs following Hick's Law, which explained limiting choices to reduce cognitive load for researchers who needed quick access in the field.
To handle the depth of functionality without cluttering the interface, I added a left sidebar with icon-based subtabs. This gave users a consistent way to navigate within each section without scattering buttons across every page. Icons made scanning faster, especially for repeat users who'd memorize the visual patterns.
Key Design Decisions:
Color-coded status alerts - Equipment warnings and high-priority events (like poacher detection) use yellow and red to grab attention immediately
Data-dense layouts – Researchers needed to see a lot at once, so I prioritized information hierarchy over minimalism, using tables, cards, and charts that could display multiple data points without feeling overwhelming
Ecosystem templates – Predefined and custom ecosystem cards with visual previews made it easy to start new projects or switch between conservation sites
Map-first approach – The map isn't just a feature; it's central to how researchers understand sensor locations, activity patterns, and field data spatially
Toggles and filters – Built-in controls for toggling data layers, filtering by date ranges, and switching between table/grid views gave researchers flexibility without adding complexity
With so many features and requirements to organize, I kept the main navigation to 5 tabs following Hick's Law, which explained limiting choices to reduce cognitive load for researchers who needed quick access in the field.
To handle the depth of functionality without cluttering the interface, I added a left sidebar with icon-based subtabs. This gave users a consistent way to navigate within each section without scattering buttons across every page. Icons made scanning faster, especially for repeat users who'd memorize the visual patterns.
Key Design Decisions:
Color-coded status alerts - Equipment warnings and high-priority events (like poacher detection) use yellow and red to grab attention immediately
Data-dense layouts – Researchers needed to see a lot at once, so I prioritized information hierarchy over minimalism, using tables, cards, and charts that could display multiple data points without feeling overwhelming
Ecosystem templates – Predefined and custom ecosystem cards with visual previews made it easy to start new projects or switch between conservation sites
Map-first approach – The map isn't just a feature; it's central to how researchers understand sensor locations, activity patterns, and field data spatially
Toggles and filters – Built-in controls for toggling data layers, filtering by date ranges, and switching between table/grid views gave researchers flexibility without adding complexity
Final draft
PRODUCT
This was the final design I delivered before my internship ended. While I didn't get to see the development through to completion, I'm proud of establishing the design foundation and solving key UX challenges for the team.
This was the final design I delivered before my internship ended. While I didn't get to see the development through to completion, I'm proud of establishing the design foundation and solving key UX challenges for the team.
MOVING FORWARD
MOVING FORWARD
Where I'd take it
Where I'd take it
Since my internship ended right as I wrapped up the design, I wasn’t able to see the final product in action. If I had more time, I would have liked to:
Expand on search and filtering tools to make navigating large datasets more efficient.
Refine the data visualization options (e.g., species trends over time, layered mapping) to give researchers deeper insights.
Conduct another round of usability testing on the final prototype to validate changes before development.
Record end-to-end task flows (like uploading, reviewing, and analyzing datasets) from the prototype to share with the team for easier alignment.
Since my internship ended right as I wrapped up the design, I wasn’t able to see the final product in action. If I had more time, I would have liked to:
Expand on search and filtering tools to make navigating large datasets more efficient.
Refine the data visualization options (e.g., species trends over time, layered mapping) to give researchers deeper insights.
Conduct another round of usability testing on the final prototype to validate changes before development.
Record end-to-end task flows (like uploading, reviewing, and analyzing datasets) from the prototype to share with the team for easier alignment.
TAKEAWAYS
User testing brings hidden gaps to light
User testing brings hidden gaps to light
Using Maze for the first time opened my eyes to how much value comes from testing. The feedback I got from researchers pointed out issues I hadn’t considered, and it really reinforced how important it is to design with the user, not just for them.
Using Maze for the first time opened my eyes to how much value comes from testing. The feedback I got from researchers pointed out issues I hadn’t considered, and it really reinforced how important it is to design with the user, not just for them.
Design–developer handoff is an ongoing conversation
Design–developer handoff is an ongoing conversation
I also learned a lot about working directly with developers. Since I was the only designer on the team, I had to figure out how to communicate my ideas clearly and adjust when something wasn’t technically possible. Those back-and-forth conversations were just as much a part of the design process as wireframes or mockups.
I also learned a lot about working directly with developers. Since I was the only designer on the team, I had to figure out how to communicate my ideas clearly and adjust when something wasn’t technically possible. Those back-and-forth conversations were just as much a part of the design process as wireframes or mockups.
Ending without outcomes was still growth
Ending without outcomes was still growth
Even though I left the internship before seeing results, I walked away with stronger skills in research-driven iteration, clearer communication with engineers, and a better understanding of how to make complex tools feel approachable.
Even though I left the internship before seeing results, I walked away with stronger skills in research-driven iteration, clearer communication with engineers, and a better understanding of how to make complex tools feel approachable.
other projects
