📊 Displaying Data Without Overload
Architecting a scalable system for clarity navigating over a million dynamic data points without cognitive overload.
Data UI
Information Architecture
GIS Integration
Problem to be Solved:
OnWater was trying to display weather conditions, water conditions, 100,000+ POIs, and 425,000+ mapped waterbodies (whoa, that’s a lot of data!). But instead of feeling powerful, the map felt overwhelming. Users didn’t know what to look at, where to start, or worse yet, if they should even trust the data.
What would Success Look like?
Reducing cognitive load, guiding users to meaningful data without clutter, and building trust through intuitive, layered interaction.
Project Outcomes:
  • Significantly reduced bounce rate for first-time users
  • Discovered and highlighted most-used map features
  • Increased interaction with map layer toggles and POI filters
  • Positive feedback from both casual users and conservation partners
  • Map became a primary planning tool, users positively reported no longer needing 2 or 3 external apps
Introduced Zoom-Level Data Hierarchies

I mapped visual complexity to map zoom level; more data revealed as users zoomed in.

This reduced overload and helped users explore without feeling lost.

Simplified Point-of-Interest Visibility

I partnered with GIS to reprioritize POIs based on type and proximity, reducing redundancy and clutter.

Important icons were easier to find without overwhelming the screen.

Designed a Visual System for Weather & Flow Conditions

Weather and flow were core to planning but they needed to feel lightweight.

I designed compact overlays and condition drawers that didn’t compete with map clarity.

Visualized Species Data Without Breaking Conservation Ethics

We visualized fish species locations through heat mapping and data layers rather than specific pins of honey holes, aka "Hot Spotting".

This respected habitat sensitivity while still guiding users toward useful info.

Post Mortem / Reflections

Designing data-heavy tools taught me the value of progressive disclosure and restraint.

The key wasn’t showing more data, it was showing less at the right time. Letting users focus helped them feel more informed, not more overwhelmed.

Collaborating with the GIS team was key to the success of this project; we had to align on taxonomy, API capabilities, and what data was “safe” to surface.

In a future version of this project, expect to see the design and structure of base map layer defaults that are both preset and personalized and remembered past usage/saved states on open.