Katrice

Williams-Dredden

⁕

Senior Product Designer focused on enterprise systems, workflows, and operational tooling.

Stats

About

Latest Projects

Services

Process/FAQ

Contact

Available to work

Home

Studio

case study

Putting workflow ownership back in operations' hands.

Putting workflow ownership back in operations' hands.

Putting workflow ownership back in operations' hands.

A no-code platform that lets 210+ operations users build, configure, and publish workflows without touching engineering once.

A no-code platform that lets 210+ operations users build, configure, and publish workflows without touching engineering once.

A no-code platform that lets 210+ operations users build, configure, and publish workflows without touching engineering once.

Role

Lead Product Designer

Lead Product Designer

Platform

Workflow Studio · Financial Services

Workflow Studio · Financial Services

Timeline

18 months • 2023–present

18 months • 2023–present

Discipline

Enterprise UX · No-Code SaaS

Enterprise UX · No-Code SaaS

|

Enterprise Fintech

|

2023–present

The problem

Operations teams needed to configure workflows fast but every change meant a 2-3 weeks.

Operations teams needed to configure workflows fast but every change meant a 2-3 weeks.

Operations teams needed to configure workflows fast but every change meant a 2-3 weeks.

Business users had no way to self-serve. Every workflow configuration, no matter how small, required an engineering ticket, sprint planning, and QA. Teams were blocked. New products couldn't launch. Compliance configurations fell behind. Engineering was buried in tickets that had nothing to do with core infrastructure.

Business users had no way to self-serve. Every workflow configuration, no matter how small, required an engineering ticket, sprint planning, and QA. Teams were blocked. New products couldn't launch. Compliance configurations fell behind. Engineering was buried in tickets that had nothing to do with core infrastructure.

Business users had no way to self-serve. Every workflow configuration, no matter how small, required an engineering ticket, sprint planning, and QA. Teams were blocked. New products couldn't launch. Compliance configurations fell behind. Engineering was buried in tickets that had nothing to do with core infrastructure.

2–3 week delays per request

100% engineering dependency

No self-service path for ops

No workflow visibility

Compliance gaps piling up

The Solution

Self-service workflow configuration, built for ops.

Self-service workflow configuration, built for ops.

Self-service workflow configuration, built for ops.

An 8-step guided platform that lets operations teams build forms, configure business rules, map processes, and publish to production. No code required.


I designed every touchpoint: the form builder, rules engine, wizard tracker, and the governance gate that ensures every workflow meets compliance before it ships.

An 8-step guided platform that lets operations teams build forms, configure business rules, map processes, and publish to production. No code required.


I designed every touchpoint: the form builder, rules engine, wizard tracker, and the governance gate that ensures every workflow meets compliance before it ships.

An 8-step guided platform that lets operations teams build forms, configure business rules, map processes, and publish to production. No code required.


I designed every touchpoint: the form builder, rules engine, wizard tracker, and the governance gate that ensures every workflow meets compliance before it ships.

Research & Discovery

Discovery surfaced three root problems, not one.

Discovery surfaced three root problems, not one.

Discovery surfaced three root problems, not one.

Before designing anything, I ran stakeholder interviews with ops leads, bankers, and engineers to map where the real friction lived.

Before designing anything, I ran stakeholder interviews with ops leads, bankers, and engineers to map where the real friction lived.

Before designing anything, I ran stakeholder interviews with ops leads, bankers, and engineers to map where the real friction lived.

PROCESS

How I worked across 18 months.

How I worked across 18 months.

How I worked across 18 months.

01

Discovery

Stakeholder interviews, workflow mapping, competitive analysis, problem framing

Research

01

Discovery

Stakeholder interviews, workflow mapping, competitive analysis, problem framing

Research

01

Discovery

Stakeholder interviews, workflow mapping, competitive analysis, problem framing

Research

01

Discovery

Stakeholder interviews, workflow mapping, competitive analysis, problem framing

Research

02

Concepts & IA

8-step wizard architecture, user flows, low-fi wireframes, Salt DS alignment

Design

02

Concepts & IA

8-step wizard architecture, user flows, low-fi wireframes, Salt DS alignment

Design

02

Concepts & IA

8-step wizard architecture, user flows, low-fi wireframes, Salt DS alignment

Design

03

Build & Iterate

Form Builder, Rules Engine, Governance gate, high-fi Figma, component library

Build

03

Build & Iterate

Form Builder, Rules Engine, Governance gate, high-fi Figma, component library

Build

03

Build & Iterate

Form Builder, Rules Engine, Governance gate, high-fi Figma, component library

Build

04

Test

Usability sessions, think-aloud protocols, accessibility audit, stakeholder sign-off

Validate

04

Test

Usability sessions, think-aloud protocols, accessibility audit, stakeholder sign-off

Validate

05

Scale

50 to 210+ users, Audit Log and Email Viewer modules, ongoing discovery

Ongoing

05

Scale

50 to 210+ users, Audit Log and Email Viewer modules, ongoing discovery

Ongoing

05

Scale

50 to 210+ users, Audit Log and Email Viewer modules, ongoing discovery

Ongoing

05

Scale

50 to 210+ users, Audit Log and Email Viewer modules, ongoing discovery

Ongoing

04

Test

Usability sessions, think-aloud protocols, accessibility audit, stakeholder sign-off

Validate

Feature 01: Form Builder

Drag, drop, configure. No code required.

Drag, drop, configure. No code required.

Drag, drop, configure. No code required.

A three-panel form builder: elements catalog on the left, live canvas in the center, field settings drawer on the right. Every element is drag-and-drop with real-time preview so ops users see exactly what their form will look like before publishing.

A three-panel form builder: elements catalog on the left, live canvas in the center, field settings drawer on the right. Every element is drag-and-drop with real-time preview so ops users see exactly what their form will look like before publishing.

A three-panel form builder: elements catalog on the left, live canvas in the center, field settings drawer on the right. Every element is drag-and-drop with real-time preview so ops users see exactly what their form will look like before publishing.

• 12 element types: text, textarea, date, dropdown, checkbox, number, file upload

• Inline field settings: label, placeholder, helper text, required, min/max length

• Layout elements: panels, columns, tabs, stepper, data grid

• Searchable elements catalog with ⌘K palette

• 12 element types: text, textarea, date, dropdown, checkbox, number, file upload

• Inline field settings: label, placeholder, helper text, required, min/max length

• Layout elements: panels, columns, tabs, stepper, data grid

• Searchable elements catalog with ⌘K palette

• 12 element types: text, textarea, date, dropdown, checkbox, number, file upload

• Inline field settings: label, placeholder, helper text, required, min/max length

• Layout elements: panels, columns, tabs, stepper, data grid

• Searchable elements catalog with ⌘K palette

Feature 02: Rules Engine · Hero Feature

Conditional logic, without the jargon.

Conditional logic, without the jargon.

Conditional logic, without the jargon.

The Rules Builder was the most technically complex feature and the one I'm most proud of. The breakthrough was reframing "conditional logic" as "if / then rules," plain language ops users already used in spreadsheets and email.


I adapted Monday.com's automation pattern into a banking-grade enterprise UI, letting users define triggers, conditions, and actions without writing a single line of code.

The Rules Builder was the most technically complex feature and the one I'm most proud of. The breakthrough was reframing "conditional logic" as "if / then rules," plain language ops users already used in spreadsheets and email.


I adapted Monday.com's automation pattern into a banking-grade enterprise UI, letting users define triggers, conditions, and actions without writing a single line of code.

The Rules Builder was the most technically complex feature and the one I'm most proud of. The breakthrough was reframing "conditional logic" as "if / then rules," plain language ops users already used in spreadsheets and email.


I adapted Monday.com's automation pattern into a banking-grade enterprise UI, letting users define triggers, conditions, and actions without writing a single line of code.

• If / then rule builder with field-level conditional chaining

• Rules configured same-day, not in two weeks

• Adapted Monday.com patterns for enterprise banking context

• Designed for non-technical ops users, zero engineering jargon

• If / then rule builder with field-level conditional chaining

• Rules configured same-day, not in two weeks

• Adapted Monday.com patterns for enterprise banking context

• Designed for non-technical ops users, zero engineering jargon

Feature 03: Governance and Publishing

Every workflow validated before it ships.

Every workflow validated before it ships.

Every workflow validated before it ships.

Within banking, compliance isn't optional. I designed a publish gate that runs a validation checklist before any workflow reaches production, surfacing errors and missing configurations inline, not at the end.

Within banking, compliance isn't optional. I designed a publish gate that runs a validation checklist before any workflow reaches production, surfacing errors and missing configurations inline, not at the end.

• 7-step wizard tracker always visible, no orientation loss

• Inline validation: errors surface per field, not at publish

• Draft → Review → Approved → Published state model

• Audit trail attached to every published version

• 7-step wizard tracker always visible, no orientation loss

• Inline validation: errors surface per field, not at publish

• Draft → Review → Approved → Published state model

• Audit trail attached to every published version

Product Gallery

The full picture.

The full picture.

The full picture.

85%

85%

faster workflow delivery
faster workflow delivery

40%

40%

40%

Fewer engineering handoffs
Fewer engineering handoffs
"I don't need a developer to write my email. I shouldn't need one to build my form either."
"I don't need a developer to write my email. I shouldn't need one to build my form either."
Ops Analyst · Usability Session
Ops Analyst · Usability Session

Design Decisions

The choices that made it work.

The choices that made it work.

The choices that made it work.

Words they already knew

"Conditional logic" made ops users freeze. Reframing as "if / then / do" unlocked self-service overnight.

Never lost in the process

Eight configuration steps is a lot to hold in your head. A persistent wizard tracker meant users always knew where they were and what was left.

Errors where they happen

Surfacing compliance issues at publish meant hours of work hit a wall. Moving validation inline, field by field, made errors fixable before they compounded.

Pick, place, configure

Five competitor audits pointed to the same mental model. Catalog left, canvas center, settings right, no one had to learn a new pattern.

Familiar pattern, new context

Monday.com's automation editor was already in ops users' muscle memory. I adapted it for banking compliance instead of inventing something new.

Built for the system, not just the feature

Every new component — side nav, drawer, wizard tracker — was contributed back to Salt DS. Studio felt native because it was.

Product Gallery

What 18 months of design delivered.

What 18 months of design delivered.

What 18 months of design delivered.

85%

Faster workflow delivery
Configuration went from 2–3 weeks in an engineering queue to same-day self-service

210+

Active users at scale
Grew from 50 at launch with no dedicated training program or support team

40%

Fewer engineering handoffs
Engineering freed from routine workflow tickets to focus on core infrastructure

$75K

Estimated annual savings
In recaptured engineering time across workflow configuration and maintenance
Before vs. After: Workflow Delivery Time
Time per configuration requestn went from 2–3 weeks in an engineering queue to same-day self-service

Before: Engineering queue

2–3 wks

After: Workflow Studio

Hours

Want to see how I think
about compliance UX?

Want to see how I think
about compliance UX?

Want to see how I think
about compliance UX?

Next: the Audit Log micro-app: contextual, drawer-based, and built for real-time compliance visibility inside an active workflow.

Next: the Audit Log micro-app: contextual, drawer-based, and built for real-time compliance visibility inside an active workflow.

Next: the Audit Log micro-app: contextual, drawer-based, and built for real-time compliance visibility inside an active workflow.

Audit log case study

Katrice

Williams-Dredden

⁕