ABOUT
Operations · UX · Systems · Communication
ANNA TRACY
A LITTLE CONTEXT
I've never been especially interested
in staying in one lane.
My work has moved through design, client service, legal operations, marketing, technology, and automation.
On paper, those can look like separate disciplines. In practice, they tend to ask me the same question:
How can this be made clearer, easier, or more useful?
01
I tend to end up in the middle of complicated things.
THE THROUGH LINE
Different disciplines,
one way of thinking.
Sometimes that means a client-facing process no one quite knows how to explain. Sometimes it is a website that has grown harder to use than it should be. Sometimes it is repetitive office work that could be automated, or a system that technically functions but asks too much of the person using it.
I like figuring out what is actually creating the friction, separating the important parts from the noise, and building something that makes the next step easier to understand.
HOW I GOT HERE
My path has been
usefully nonlinear.
01
DESIGN
Theatre taught me how to work inside constraints.
My design background taught me that ideas only matter if they can survive budgets, deadlines, technical limits, collaboration, and the realities of production.
02
CLIENT WORK
Service taught me to translate complexity.
Working directly with clients taught me how differently people process information, especially when the subject is unfamiliar, stressful, or when the stakes are high.
03
OPERATIONS
Legal work taught me to think in systems.
Legal operations pushed me beyond individual tasks and toward understanding how information, software, people, deadlines, and client needs interact.
04
TECHNOLOGY
Automation taught me to question repetition.
Once I started building scripts, integrations, and lightweight internal tools, repetitive work stopped feeling inevitable.
02
WHERE MY WORK OVERLAPS
I'm most useful
between disciplines.
Operations
Understanding how work actually moves between people, tools, deadlines, and competing priorities.
Experience Design
Looking at where people hesitate, get lost, misunderstand something, or have to work harder than necessary.
Technology
Using automation, integrations, lightweight code, and better tools to remove repetitive friction.
Communication
Understanding how work actually moves between people, tools, deadlines, and competing priorities.
HOW I TEND TO WORK
I usually start
with the friction.
01
Look at what is actually happening
Before changing anything, I want to understand how people are currently working, including the awkward workarounds that never made it into the official process.
02
Find the part creating unnecessary effort
The visible problem is not always the real one. A confusing page may actually be an information-architecture problem. A repetitive task may actually be a handoff problem.
03
Make the solution as simple as it can be
I prefer small, understandable systems over elaborate solutions that create more maintenance than they remove.
04
Watch what happens after launch
Real use usually teaches more than the first design. I expect systems to evolve once people start relying on them.
THE WORK I'M DRAWN TO
Give me something
a little messy.
01
Processes with too many steps
04
Repetitive work everyone assumes has to stay repetitive
02
Interfaces people have learned to tolerate
05
Problems that sit awkwardly between job descriptions
03
Information that is technically correct but difficult to use
06
Systems that need both technical and human thinking
03
OUTSIDE THE WORK
I'm usually
making something anyway.
The same curiosity that shows up in my professional work tends to follow me home.
I like sewing, building small tools, pulling apart game systems, gardening, learning languages, experimenting with design software, anything to do with tea, and generally finding projects that give me an excuse to understand how something works.
I’m less interested in having one defining hobby than I am in continuing to learn things badly, then slightly less badly.