ENTERPRISE UX / WNS

ENTERPRISE UX / WNS

ENTERPRISE UX / WNS

Trade platform redesign

Trade platform redesign

Trade platform redesign

The client wasn’t sure we could redesign its platform. I spent three weeks showing options and shipping small changes with the team. Once we had earned his trust, he gave us nine weeks for the full redesign.

The client wasn’t sure we could redesign its platform. I spent three weeks showing options and shipping small changes with the team. Once we had earned his trust, he gave us nine weeks for the full redesign.

The client wasn’t sure we could redesign its platform. I spent three weeks showing options and shipping small changes with the team. Once we had earned his trust, he gave us nine weeks for the full redesign.

FIRST 3 WEEKS

Earn the client’s trust

Design-system options, stakeholder conversations, and small shipped improvements.

NEXT 9 WEEKS

Redesign the platform

Research, workflows, role-based dashboards, and a reusable Appian design system.

1

GETTING STARTED

I had to get a seat at the table.

I had to get a seat at the table.

I had to get a seat at the table.

The developers were already improving speed. The project head and I worked directly with the stakeholder to earn his trust, while I showed design-system variations and checked what Appian could support.

The developers were already improving speed. The project head and I worked directly with the stakeholder to earn his trust, while I showed design-system variations and checked what Appian could support.

25 OF 100 LICENSES WERE IN USE

The client wanted to put the other 75 licenses to work.

Users worked around dense screens and exported records to Excel. The client wanted more of its team to complete that work in the platform.

My role

My role

Lead UX Designer · About 12 weeks · Appian and Figma

Lead UX Designer · About 12 weeks · Appian and Figma

RESEARCH

Research & structure

I led interviews, surveys, and workflow observation, defined three personas, and reorganized the information around their work.

DESIGN

Interfaces & system

I explored visual directions, redesigned the screens, and built reusable Appian patterns for queues, case details, and review flows.

COLLABORATION

Earning the redesign

The project head and I earned the stakeholder’s trust. I showed design-system options and helped the team ship small improvements.

DELIVERY

Working with developers

I checked Appian feasibility with about two frontend developers within the wider team and reviewed implementations in development.

2

RESEARCH & DESIGN APPROACH

Understand the work, then set the hierarchy.

Understand the work, then set the hierarchy.

Understand the work, then set the hierarchy.

I used stakeholder interviews, user surveys, and workflow observation to understand where the platform got in the way. I defined three personas and reorganized the information architecture around makers, reviewers, and managers.

I used stakeholder interviews, user surveys, and workflow observation to understand where the platform got in the way. I defined three personas and reorganized the information architecture around makers, reviewers, and managers.

RESEARCH FINDING → DESIGN RESPONSE

Too much information competing

Group the record and bring case context to the top.

Unclear priorities by role

Give makers, reviewers, and managers distinct starting views.

Low confidence in data

Keep case details and verification states visible.

Designing at a density I wasn’t used to.

Designing at a density I wasn’t used to.

I usually push toward cleaner, more minimal interfaces. Here, people needed a lot of information to do their work. I had to make that density easier to read while keeping the detail available.

I explored design-system variations, then used hierarchy, spacing, consistent labels, and status treatments across the screens. Tables stayed where people needed to compare records; summaries and steps helped them navigate the detail.

The frontend developers and I checked what Appian could support. We used standard components where they met the need, reserved custom work for changes that justified it, and reviewed priorities with stakeholders each week.

3

WORK QUEUES

Give each role a useful starting point.

Give each role a useful starting point.

Give each role a useful starting point.

Makers, reviewers, and managers received different views of their work, with task counts, deadlines, and filters above the queue.

Makers, reviewers, and managers received different views of their work, with task counts, deadlines, and filters above the queue.

BEFORE

The capture queue starts with dense filters and a long table.

AFTER

The maker dashboard puts workload summaries and filtering above the records.

BEFORE

A dense capture queue with long filters and a table.

AFTER / RECONSTRUCTED

Maker task dashboard with workload summaries and filters.

4

CASE CONTEXT

Put the case summary before the detail.

Put the case summary before the detail.

Put the case summary before the detail.

The old case view put long nested sections beside an equally dense sidebar. I moved progress and key case details to the top, grouped the record, and kept related tasks close by.

The old case view put long nested sections beside an equally dense sidebar. I moved progress and key case details to the top, grouped the record, and kept related tasks close by.

BEFORE

Nested navigation and record details compete for space.

AFTER

Progress, KYC status, and key details establish context before the longer record.

BEFORE

Nested navigation and record details competed for space.

AFTER / RECONSTRUCTED

Case summary with progress, KYC status, and key details first.

5

REVIEW FLOW

Keep the current step in view.

Keep the current step in view.

Keep the current step in view.

I moved the review screen’s horizontal tabs into a vertical step list. Reviewers could see their section and its verification state while reading details and adding comments.

I moved the review screen’s horizontal tabs into a vertical step list. Reviewers could see their section and its verification state while reading details and adding comments.

BEFORE

A row of tabs separates the sections from the review content.

AFTER

The step list sits beside the details, comments, and next action.

BEFORE

Horizontal tabs separated the review sections from the work.

AFTER / RECONSTRUCTED

Vertical step list with verification state beside the details.

Reconstructed desktop screens · Fictional names and record values · Client branding removed

DELIVERY

Four workflows. Three roles.
All designs reached production.

Four workflows. Three roles.
All designs reached production.

Four workflows. Three roles.
All designs reached production.

We delivered the redesigned workflows and a reusable Appian design system. The stakeholder was impressed; developers described the difference during internal testing as night and day.

I reviewed implementations in development. After moving to another project, I did not have access to the production versions or later license-use metrics.

Client details are omitted under NDA. Screens are reconstructed with fictional data.