1
GETTING STARTED
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.
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
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.
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
4
CASE CONTEXT
5
REVIEW FLOW
Reconstructed desktop screens · Fictional names and record values · Client branding removed
DELIVERY
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.





