Transform Canvas: Visual Pipeline Editor

Reimagining data preparation through visual context and intuitive navigation

Product Design Leadership

Transform Canvas Visual Pipeline Editor
Transform Canvas: Visual pipeline editor with node-based data transformation

Background

Data Preparation Journey

Data Preparation Journey

Existing Data Preparation Editor

1
Linear Stage List Flat list hides relationships between pipeline stages
2
No Visual Connections Users can't see data flow or dependencies
3
Errors Not Surfaced Must click into each stage to find issues
4
Limited Context Data grid shows one stage; no pipeline overview

Challenge

Linear Thinking in a Non-Linear World

Users were struggling to build and debug complex data pipelines in data prep editor. The linear list view couldn't represent the true relationships between datasets, stages, and pipelines.

The existing data preparation editor presented users with a fragmented, step-based interface that obscured the relationships between transformation stages. Users struggled to understand their pipeline's structure, locate errors, and navigate efficiently through complex data workflows.


Goals

Transform the data preparation experience by providing a visual, intuitive interface—augmented by AI-assisted formula authoring—that empowers users to understand, navigate, and manage complex data pipelines with confidence.

Visual Pipeline Representation

Provide a holistic view of the entire data pipeline, making relationships and data flow immediately visible

Reduced Debugging Time

Surface errors and issues directly on the canvas, eliminating the need to hunt through individual stages

Intuitive Navigation

Enable users to quickly jump between stages and maintain context while editing

Self-Service for All Users

Empower IT analysts to build and maintain pipelines independently without engineering support

Improved Onboarding

Reduce the learning curve for new users through visual representation of data concepts

AI-Assisted Formula Authoring

Help users write complex transformation formulas with a Copilot expression builder, turning a repetitive, syntax-heavy task into a guided, natural-language experience

My Role

Design Leadership & Team Mentorship

  • Led a team of 2 designers and 1 researcher
  • Worked with PM and development team in a phased release approach
  • Conducted customer interviews to understand user needs and pain points
  • Performed competitive audit to identify industry best practices
  • Provided design reviews and mentoring to designers on the team

Target Users

Based on our research, we identified three distinct user personas with different needs, technical backgrounds, and workflow patterns. Nina, the IT Analyst, represents our primary target user.

Nina, IT Analyst
Nina
IT Analyst
Primary Persona
Background
5+ years in IT analytics. Comfortable with business data but not a developer. Relies on visual tools.
Goals
Create and maintain data pipelines independently without requiring engineering support.
Pain Points
Gets lost in complex pipelines; struggles to debug errors without seeing full context.
Marcus, Data Engineering Expert
Marcus
Data Engineering Expert
Background
8+ years in data engineering. Expert in SQL and ETL. Prefers code but uses visual tools for collaboration.
Goals
Build efficient, scalable pipelines quickly. Needs keyboard shortcuts and advanced features.
Pain Points
Tool feels slow compared to code-based approaches; lacks power user features.
Priya, Implementation Consultant
Priya
Implementation Consultant
Background
3+ years implementing Workday. Configures systems for clients. Deep product knowledge.
Goals
Configure complex pipelines for clients efficiently and train them on usage.
Pain Points
Hard to explain pipeline structure to clients; demo scenarios are difficult to set up.

Process

Our design process combined rigorous user research with iterative concept development, allowing us to deeply understand user needs before crafting solutions.

Phase 1: Discovery Research
Conducted 6 in-depth interviews with existing users to understand workflows, identify pain points, and map mental models for data preparation.
Phase 2: Concept Validation
Facilitated 6+ moderated testing sessions with interactive prototypes, conducting task-based scenario testing and preference testing for visual approaches.
Phase 3: Design & Iteration
Created comprehensive design specifications and worked with engineering to refine solutions based on technical constraints and user feedback.
Phase 4: Release Planning
Collaborated with product management to prioritize features for the multiple release scope, balancing user needs with development capacity.

Key Research Insights

Our research revealed four critical insights that shaped the design direction:

1

Expertise Impacts Approach

Prism experts and Data Engineering experts approach pipeline creation differently. Prism experts think in terms of the UI flow, while DE experts think in terms of data transformations and SQL operations.

"I think about what data I need at the end and work backwards, but the tool makes me build forwards step by step." — Senior Data Engineer
2

Visual Representations are Essential

Users consistently drew diagrams on whiteboards or in documentation to understand their pipelines before returning to the tool. The mental model was inherently visual, but the tool was not.

"I always sketch out my pipeline on paper first. I can't keep all the connections in my head when I'm just looking at a list." — IT Analyst
3

Small UI Issues Compound

Individual friction points like extra clicks, hidden menus, and lack of keyboard shortcuts accumulated into significant productivity losses over time, especially for power users building complex pipelines.

"It's not one big thing that's broken—it's death by a thousand paper cuts. Each task takes just a few extra clicks, but it adds up." — Prism Analyst
4

Context Must Stay Visible

When editing a specific stage, users lost visibility of the overall pipeline context. This forced constant mental effort to remember where they were and how changes might impact downstream stages.

"I changed a field name and broke three things downstream. I didn't even know those stages existed until the errors appeared." — Implementation Consultant

The Solution: Transform Canvas

Transform Canvas provides a visual, interactive representation of the entire data pipeline, allowing users to see all stages, their connections, and status at a glance while maintaining the ability to drill into any stage for detailed editing.

To tackle the most error-prone part of data prep—authoring transformation logic—we introduced a Copilot Expression Builder. Instead of recalling function syntax by hand, users describe what they want in plain language and the copilot generates a ready-to-review expression, making complex formulas approachable for analysts of every skill level.

1
Visual Pipeline Canvas Connected stage diagram showing all transformations and data flow at a glance
2
Error Indicators Red badges surface issues immediately without clicking into stages
3
Secondary Pipeline Branching pipelines visible on the same canvas with clear connections
4
Stage Details Panel Edit stage configurations without losing pipeline context
5
Data Preview Real-time data grid showing transformation results

Key Features

  • Holistic Pipeline View: See the entire pipeline structure at once with zoomable, pannable canvas that shows all stages and their relationships.
  • Inline Stage Editing: Edit stage configurations directly on the canvas without losing context of the overall pipeline structure.
  • Copilot Expression Builder: Write complex transformation formulas with an AI copilot that turns natural-language intent into valid expressions-removing a repetitive, syntax-heavy task and reducing formula errors.
  • Surfaced Errors: Errors are visually highlighted on the canvas with clear indicators, making troubleshooting immediate and intuitive.
  • Expand/Collapse Branches: Manage complexity by collapsing branches you're not working on, focusing attention on relevant stages.
  • Keyboard Navigation: Full keyboard support for power users to navigate, select, and edit stages without touching the mouse.
  • Real-Time Updates: Changes to one stage immediately reflect across the canvas, showing downstream impacts instantly.

Before & After

The Transform Canvas fundamentally changed how users interact with data pipelines, replacing a fragmented step-based interface with a unified visual experience.

Before: Step-Based Editor
  • Linear, sequential navigation through stages
  • No visibility of pipeline relationships
  • Errors hidden within individual stages
  • Users had to mentally track dependencies
  • Required multiple clicks to navigate between stages
  • No way to see downstream impact of changes
After: Transform Canvas
  • Visual, holistic view of entire pipeline
  • Clear representation of all connections
  • Errors surfaced directly on canvas
  • Dependencies visible at a glance
  • One-click navigation to any stage
  • Real-time updates show change impacts

Final Designs


Results & Impact

The Transform Canvas delivered measurable improvements across key metrics, validated through post-launch research and production monitoring.

70% Reduction in debugging time
+25 NPS score increase
40% Fewer support tickets
3x Self-serve pipeline creation
"The new canvas view completely changed how I work. I can finally see my whole pipeline and understand what's happening at each step. Debugging used to take hours—now it takes minutes."
— Customer feedback, IT Analyst at Fortune 500 company

Platform Approach

The new canvas-based editor has become the de facto standard for Workday Data Modeler.

Enable data administrators to create tenanted data sources that blend Workday data, using the familiar Visual Pipeline Editor interface, enabling report creators to use views that are easy to understand and built for their reporting needs.


Reflections

This project reinforced several key principles that I carry into all my design work, while also teaching me new lessons about designing complex data tools.

  • Research Methodology Matters: Splitting research into discovery and validation phases allowed us to deeply understand problems before jumping to solutions. The foundational interviews revealed insights we wouldn't have uncovered with concept testing alone.
  • Persona-Driven Design: Having Nina as our primary persona kept the team aligned on who we were designing for. When debates arose about features, we asked "What would Nina need?" and it clarified our direction.
  • Visual Context is Power: Users' natural instinct to draw diagrams told us everything we needed to know. When users are creating their own visualizations to understand your tool, the tool should provide that visualization.
  • Phased Delivery Builds Trust: Delivering a focused release scope with clear future enhancements built stakeholder trust. Users appreciated knowing what was coming next, and engineering could plan capacity more effectively.