Available for Hire

Available for Hire

Making a Complex Query Language Approachable

Interaction Design

Interaction Design

Prototyping

Prototyping

UI Design

UI Design

Control video resolution and playback speed in the YouTube player.

How might we help new users understand and leverage JupiterOne's graph query capabilities without compromising power and flexibility?

How might we help new users understand and leverage JupiterOne's graph query capabilities without compromising power and flexibility?

How might we help new users understand and leverage JupiterOne's graph query capabilities without compromising power and flexibility?

Project Summary

Challenge

JupiterOne's graph-based security platform offered powerful insights through its query language, J1QL. However, new customers faced two critical barriers: understanding what they could ask for in the vast data model, and learning how to write effective queries. This technical complexity was becoming a significant blocker for customer adoption.

JupiterOne's graph-based security platform offered powerful insights through its query language, J1QL. However, new customers faced two critical barriers: understanding what they could ask for in the vast data model, and learning how to write effective queries. This technical complexity was becoming a significant blocker for customer adoption.

Approach

Through conversations with our security team, solutions team, and customers, we developed a strategic solution benefitting all sides. We synthesized the vast data model into a compact, browsable interface helping users build an intuitive understanding of the platform's possibilities.

Rather than fully hiding J1QL, we recognized it would remain the most powerful way to leverage the platform. This insight led us to pursue a UI design that mirrored J1QL's core structure, providing guardrails while familiarizing users with the language patterns.

Through conversations with our security team, solutions team, and customers, we developed a strategic solution benefitting all sides. We synthesized the vast data model into a compact, browsable interface helping users build an intuitive understanding of the platform's possibilities.

Rather than fully hiding J1QL, we recognized it would remain the most powerful way to leverage the platform. This insight led us to pursue a UI design that mirrored J1QL's core structure, providing guardrails while familiarizing users with the language patterns.

Solution

The final system supported both immediate and long-term user needs by:

  • Making the data model intuitively browsable through clear categories

  • Providing structured ways to build queries that taught the language

  • Creating a natural progression from guided to advanced usage

The final system supported both immediate and long-term user needs by:

  • Making the data model intuitively browsable through clear categories

  • Providing structured ways to build queries that taught the language

  • Creating a natural progression from guided to advanced usage

Impact & Learnings

The impact was immediate and measurable: new customers now wrote their first custom query within one day of data integration, down from an average of 21 days. This dramatic improvement validated our approach of teaching complexity rather than hiding it, leading to prioritization of advanced query capabilities in subsequent releases.

The impact was immediate and measurable: new customers now wrote their first custom query within one day of data integration, down from an average of 21 days. This dramatic improvement validated our approach of teaching complexity rather than hiding it, leading to prioritization of advanced query capabilities in subsequent releases.

Project Details

  • Who: Designer + engineer pair. Pulled in engineers to support implementation as needed.

  • How Long: ~3 months (initial discovery to live in production)

  • What Tools: Figma for UI design. Code-based prototyping led by engineer.

  • Who: Designer + engineer pair. Pulled in engineers to support implementation as needed.

  • How Long: ~3 months (initial discovery to live in production)

  • What Tools: Figma for UI design. Code-based prototyping led by engineer.

Slides

You can click through the slides directly.

You can click through the slides directly.

Get in touch!

Always excited to connect with fellow curious minds and creators—let’s make something great together!

Available for Hire

©2025 Patrick Morgan

Get in touch!

Always excited to connect with fellow curious minds and creators—let’s make something great together!

Available for Hire

©2025 Patrick Morgan

Get in touch!

Always excited to connect with fellow curious minds and creators—let’s make something great together!

Available for Hire

©2025 Patrick Morgan