×CAST Imaging · Case study
Selected work / Product design

CAST Imaging

Bring the value of software visualization forward

Senior Product DesignerJan–May 20231 designer · 2 engineers · 1 PM
CAST Imaging application list from my published portfolio.
CAST Imaging application list from my published portfolio.
Original CAST Imaging case study cover
01

Getting to the first useful graph

CAST Imaging maps an application’s source code and dependencies. A trial user needed to see what the tool could reveal about their own application. To get there, an administrator first uploaded and onboarded the code in Console. The user then switched to Imaging, found the application, and chose a use case before opening the graph. Any unresolved setup could send the user back to the administrator.

Scope, team, and trial challenges
Scope, team, and trial challenges
The original Console-to-Imaging workflow
The original Console-to-Imaging workflow
02

Prioritizing what blocked the trial

I interviewed existing clients and spoke with sales, customer success, CAST University, product, and engineering. I compared the problems by user impact and business impact. The split between Console and Imaging and the delay before graph access ranked as critical. Unclear navigation followed. Graph density mattered, but simplifying the graph would still leave new users waiting to reach it.

Planning and discovery
Planning and discovery
Prioritization matrix
Prioritization matrix
03

Designing one path from setup to analysis

I proposed a unified architecture to the team and VP of Product. From one Home, users could onboard an application or try a demo. A persistent application list showed progress and status, with search, filtering, and access to recent or favorite applications. Once an application was ready, its row opened the graph.

Proposed unified architecture
Proposed unified architecture
Application list and navigation
Application list and navigation
04

Making unfinished states useful

When an application was still processing or needed attention, the row opened a panel with completed steps, missing information, and available actions. A user could address a setup issue without losing their place in the list.

  • In progress — see what has completed and what is still running.
  • Requires attention or actions pending — see what is missing and act from the application panel.
  • Ready to view — open the graph directly from the application list.

After opening the graph, task groups such as Discover, Modernize, Investigate, and Optimize gave users a starting point while keeping technical detail available.

Application onboarding
Application onboarding
Intermediate onboarding states
Intermediate onboarding states
Application and analysis UI examples
Application and analysis UI examples
05

From landing page to graph

The walkthrough compares the original and redesigned landing pages and graph views. The redesign gives the graph room to work while keeping the surrounding navigation and details available for deeper investigation.

Original landing page
Original landing page
Redesigned landing page
Redesigned landing page
Landing page interactions
Landing page interactions
Original graph view
Original graph view
Graph view structure
Graph view structure
Redesigned graph view
Redesigned graph view
Graph interaction concepts
Graph interaction concepts
06

Outcome

My original portfolio reported 2× trial-to-paid conversion after the redesign. The published case does not include the starting conversion rate, cohort size, or measurement window.

Reported outcomes
Reported outcomes