Works

Scope:

UX Design

Year:

2020 - 2022

OVERVIEW

To secure institutional funding and prepare for a successful IPO (which the company achieved in late 2024), Synspective needed to pivot from acting as a raw satellite data provider to offering a scalable, high-margin commercial SaaS platform.

Mission

Pivot Synspective from a raw satellite data provider to a high-margin commercial SaaS platform ahead of their IPO (successfully achieved in late 2024).

The Commercial Tension

Executive buyers held the budgets but don't know how to interpret complex scientific charts. The software interface had to become a clear sales tool that non-experts could understand in a single demo.

Target Market

High-value enterprise and government contracts (civil engineering, mining, defense, and sinking infrastructure like Kansai Airport).

PROBLEMS

Engineering-led MVP lacked the clear visual hierarchy needed to convert corporate buyers
Intense cognitive overload separating minor, safe land shifts from active, dangerous structural hazards
Raw, short-term data views completely hid slow, creeping terrain failures that only manifest over months
Assumed users wanted deep, raw variable controls; customer feedback proved they needed automated, pre-interpreted anomaly alerts

MY ROLE

I was the sole product designer on this project for a long time (until a UX researcher joined) leading the strategy, UI architecture, and creating modular templates. At the same time, I had to manage regular alignment loops between satellite engineers, front-end developers, and sales managers. Weekly design-engineering frameworks helped the team translate data science into a complex yet approachable UI.

DIRECTION

I reframed dense satellite radar data into a three-tier risk-alert dashboard, balancing rapid executive overviews for buyers with advanced filter parameters for deep investigations.

The information architecture map allowed me to align developers, engineers, and me as a designer about the overall structure of the product and what elements we want to show and how these are connected logically inside the product since a lot of the processed data is relatively complex.

Dashboard and map view wireframe: this layout helped us discuss where we highlight crucial information and critical interaction points

SOLUTIONS

The traffic light hierarchy: This helped abstract raw millimetric variations in land displacement into clear algorithmic states: Green (stable), Yellow (inspect), and Red (urgent action). This allowed non-technical users to react in seconds, while experts retained the ability to configure backend calculation thresholds.

Designing around temporal gaps: Addressed natural data delays between satellite flyovers by introducing an interactive custom historical increment selector. Viewing data over weeks or months exposed slow, hidden structural settling that short-term views completely obscured.

Technical pragmatism: I also partnered with engineers to reshape the map-drawing tools around rigid code limitations, protecting the launch timeline without hurting the user experience.

Strategic design library leverage: Adopted IBM’s open-source Carbon Design System. Utilizing a thoroughly documented framework simplified the component creation process, built immediate trust with front-end coders, and allowed for quick iterations of fully functional prototypes.

OUTCOMES

Unified design framework: Turned the custom map layouts and data components into a shared design system. This created a consistent UI across parallel SaaS products and cut down on redundant layout work for other internal teams.

Accelerated prototyping for sales: Having a ready-to-use component library enabled product teams to build interactive, high-fidelity sales demos in days instead of weeks, making it much faster to pitch to new enterprise clients, which was crucial to attract more business and allow the company to secure more fundings.

Clearer risk analysis for engineers: Simplified complex satellite data by introducing a dedicated timeline and millimeter threshold filters. This allowed civil engineers to track land displacement and spot structural risks quickly without getting overwhelmed by dense information, making Synspective the go-to alternative for approachable yet complex SaaS products.

LEARNINGS

Designing for data reality: In highly technical products, you can’t design under the assumption that the backend works instantly. Because handling heavy satellite data comes with real API limits and processing delays, I learned that the UX has to actively manage those latencies. That means using clear loading states and data-freshness indicators so the software never feels broken to the engineers using it

Knowing when not to build from scratch: When project timelines are incredibly tight, a designer's value isn't in drawing custom buttons or dropdowns. Choosing to use an established framework like IBM Carbon allowed us to completely skip the visual design debt and focus 100% of our energy on the actual problem: making complex map layouts and timelines easy to read. This left me and the team plenty of time to work on technical feasibilities and the overall user experience.

Embracing data density for specific users: This project taught me that standard UX advice about keeping interfaces "clean" and full of whitespace doesn't always apply to expert tools. The civil engineers checking for structural risks didn't want a minimalist dashboard; they needed a high density of information visible at once. The goal wasn't to hide data, but to organize it logically through proper filtering.