A modern, streamlined vector-editing experience that replaced Planet’s outdated tools with an intuitive, scalable interface—reducing friction, improving efficiency, and boosting user engagement across geospatial workflows.
Business problem:
Users were abandoning Planet Explorer’s vector editing tools due to outdated, unintuitive UI controls. This created a risk of churn to competitor mapping tools and slowed workflows, reducing overall platform engagement.
User problem:
Planteers (internal users) struggled to create, edit, and save geospatial vectors efficiently. Pain points included confusing edit modes, unclear feedback on changes, and a poor hierarchy of toolbar controls. Users described interactions as “clunky,” “hard to find,” and “unpredictable.”
Technical problem:
The system’s UI was fragmented and inconsistent, making feature scaling difficult. Existing components were not reusable, slowing down engineering and design velocity.
Why this matters:
A modernized, consistent vector editing interface would streamline workflows, reduce user friction, increase retention, and position Planet Monitoring as a self-contained platform for spatial analysis.
Designing under these constraints required: prioritizing high-impact usability changes, leveraging co-design sessions with engineers, and aligning with Planet’s existing design system to reduce rework.
Experience principles:
Hypotheses:
Future-state vision:
A unified, intuitive vector editing workflow that allows users to create, edit, and save polygons directly on the map without leaving the platform—streamlining tasks and increasing engagement.
Business alignment:
By improving the vector workflow, Planet would retain users, reduce reliance on external mapping tools, and accelerate feature adoption within the platform.
Handoff to development was straightforward due to the tight collaboration from the start. We provided Figma specs, component documentation, and prototype links to the engineering, QA, and product management teams.
The handoff process utilized Figma Inspect and live documentation in Jira to track progress and maintain version control. Since much of the design work happened in co-creation sessions, developers were already familiar with decisions made. Notes and annotations were included directly in Figma, documenting every interaction and rationale derived from live design iterations. This reduced back-and-forth and ensured everyone shared a clear understanding of expected behaviors.
Execution highlights:
Key Takeaway:
Early, collaborative co-design with engineers and users transforms complex workflows into intuitive, scalable interfaces. By aligning UX strategy with business goals and technical
