Andrea Harter

Senior UX Designer, based in St. Louis

I turn fragmented problems into systems people, and AI, can act on.

By day I design for complex enterprise software, the kind with a hundred edge cases and no clean answer. After an earlier life in footwear design and marketing, I still like that kind of problem best.

UX & interaction design Systems & decision architecture Applied AI

7+ yrs
Senior-level product & UX design in complex B2B / enterprise SaaS
Enterprise scale
Multi-entity case-management systems: permissions, workflows, and the edge cases that come with them
Cross-functional
Works directly with product and engineering to shape scope, sequencing, and delivery

Where I actually spend my time

Four areas, and what that's looked like in real projects.

01

Systems synthesis

There's usually one problem hiding inside five separately-scoped issues. I map the states, relationships, and tradeoffs underneath it, so the team builds from one shared picture instead of five patched symptoms.

02

Decision architecture

On a big project, half the battles aren't about the design. They're about what's actually decided, and where that decision lives. I track what's confirmed, what's still proposed, what's evidence versus assumption. Then I write down the why, so nobody has to reconstruct the reasoning from memory six months later.

03

AI-assisted workflows

I build the workflow around the AI tools I use: evaluation, delivery, and a handoff document that tells the next tool what's already been decided, so it doesn't start from scratch.

04

Accessible interaction craft

I design what happens at every step a component or workflow can hit, including the broken ones, and build in accessibility from the first sketch, not the last.

Case studies from enterprise systems work

View all work

Small tools, built to be played with

Case studies show finished work. This is the unfinished stuff: small, working experiments, documented and interesting beats polished.

View all lab experiments

Working style

I'm a systems thinker who does my best work in the parts other people find exhausting: where what users expect, what the product actually does, and what engineering can realistically build all pull in different directions. My job is to figure out what's actually going on, get a cross-functional team aligned on it, and take the problem from a vague first conversation to a shipped outcome, then write it all down so nobody has to reverse-engineer my thinking later.

Let's talk

Reach out for the password to a case study, or to talk about a role.