
I redesigned an immersive geospatial visualization tool so users can upload subsurface results, adjust configurations, and interpret outputs with clarity.
I conducted customer research and usability testing, designed the end-to-end workflow for the main interface and customization panels, and built a centralized design system for the company.
Boundary Remote Sensing Systems (Boundary RSS) is a B2B SaaS startup whose geographic information system (GIS) platform supports subsurface exploration.
Its flagship application lets users upload their own data or pull seismic, well log, magnetic, and gravity data from across the US, all in one place.

The immersive, 3D visualization viewport should allow users to upload shapefiles and generate a spatial analysis, but the existing interface presents significant challenges:
Once results were processed, users couldn't adjust them and had to request any changes from the Boundary team.
Essential tools or actions were hidden or unclear, making it difficult to find features, modify inputs, and understand outputs.

How might we help users explore and customize their spatial results on their own, without confusion?
Since I was new to GIS myself, I started by evaluating the interface against GIS UX heuristics across 4 core flows. I then ran exploratory usability tests with 2 industry experts and interviewed 3 current customers.

Fragmented workflow
Users struggled to move from uploading data to viewing spatial outputs to placing an order.

High cognitive load
Dense features, numerous files, and technical jargon overwhelmed users, especially first-timers.

Minimal guidance
With icon-only buttons and no labels or tooltips, new users relied on trial and error to modify and view their results.
Streamline the workflow
Create a clear, guided path from upload to output to order.
Simplify language and layout
Replace jargon, declutter dense features, and give the visualization more room.
Build in guidance
Add labels, tooltips, and in-context help so users don't have to learn by trial and error.
Unify the visual system
Establish consistent styles, components, and interaction patterns.
The original journey had several fork points where users had to make a decision, and every change to their output cost a fee.
I partnered with engineering and finance to identify where payments were truly necessary and which steps could be cut, creating a more linear workflow.

I explored a dual-panel layout that separated layer management from viewing controls. Sketching let me work through the interface's structure and test it with stakeholders before moving to higher fidelity.

Mid-fi reviews sparked debate over visual hierarchy, especially on the upload screens and sidebars. I kept returning to my design requirements, primarily reducing cognitive load, to guide decisions.

The redesign needed a shared foundation with engineering. I compiled GIS UX standards for layout, defined a brand-aligned color palette, and used AI to speed up building reusable components.


Upload your subsurface data either through files or through a URL. If there is any additional types of data that you want to analyze, select the options.
The left side panel acts as a dataset management section. Select the types of filters and layers that needs 3D analysis.
Change the visual effects of the visualization. Key features include: a legend, map style, 2D/3D, draw ROI, measurement, annotations, screen capture, and zoom features.
90%
of usability testers expressed a positive experience.
“The controls are straightforward and there’s more flexibility than I expected” — Participant 3
15
more customers joined the release waitlist
After the first preview was released, the customer waitlist increased with peaked interest for the product.
100%
approval from stakeholders for Phase 2
Phase 2 includes AI analysis, in-app purchasing, and advanced 3D animations.
This was my first experience with GIS and subsurface imaging. I was unfamiliar with terminology and standards, but had a product to deliver.
I researched scientific articles about subsurface analysis and used AI to summarize and read through PRDs so that I could understand what I was even designing
When the project first started, I was expected to have high-fidelity prototypes in 3 days — no research, no testing.
I communicated with leadership so that I had adequate time and resources for QUALITY. I also created a “UX dictionary” with terms that other team members could refer to for a shared understanding (“wireframe” vs “prototype”)