Enterprise SaaS • Feature

Making Enterprise Data Mapping Accessible

Motion-blurred landscape in amber and pale blue, with a text cursor blinking in a white input box at the centre

Role: Product Designer
Timeline: 4 weeks
Team: Akhil Kooliyatt (Product Architect)Harikrishnan AU (Product Manager)Sumethan B (Engineer)

Overview

A technical workflow was blocking business users

The existing mapping experience relied on JSLT, making transformations difficult for non-technical users to understand and configure.

The challenge

Mapping configurations often required technical support.
Errors could disrupt integrations and delay deployment.
Transformation logic was difficult to interpret.

Key insight

The opportunity was to make transformation logic accessible through the interface while preserving the control needed for complex configurations.

Solution

Reframing how users configure transformations

I redesigned the workflow around structured mapping rules, translating a code-centric process into a configurable interface built around how users inspect and manage transformations.

Smart mapping for a purchase order as a table: each target field with its type, an empty source column, and every row marked Unmapped

Turning transformation logic into configurable rules

I replaced direct JSLT editing with structured conditions and results, making the logic behind each mapping easier to inspect and configure.

The same table with Contract connected as a source: most fields now mapped from contract fields, a few still unmapped, and the pointer on Save

Final designs

Completed purchase order mapping: every target field, including nested customer and product fields, mapped from the contract

Source field picker: a searchable tree of contract fields with their types, such as Order ID (Text) and Buyer (Object)

Connected sources bar with Contract added, above All, Mapped and Unmapped filters

Rule builder for an if condition: if Customer type equals Corporate, the result is Approved, otherwise Pending

Outcome

A mapping workflow built around user control

The redesigned experience shifts configuration from raw transformation syntax to structured rules, making mapping logic more visible within the workflow.

Independent configuration
A visual interface for managing mappings without directly editing JSLT.
Inspectable logic
Transformation conditions and results presented in a structured format.
Less engineering dependency
A more understandable workflow reduced the need for repeated technical intervention.

Reflection

Simplifying doesn't mean hiding complexity

The challenge was deciding which parts of the underlying logic users needed to see and control. Further validation would help establish how well the new interaction model supports increasingly complex mapping scenarios.