Fifteen years
in design,
mostly where
a wrong read
costs something.
Enterprise security, IT operations, platforms built for people who read data for a living. The problem I keep ending up in: someone built something powerful, and now it's hard to tell what it's doing. A misread visualization or a confident-but-wrong AI output doesn't just confuse a user. It creates the conditions for a bad call.
Who I am
Complexity is the material I work with.
Most of my career has been in security software, IT operations, AI products: environments where the users aren't casually browsing. They're deciding whether to trust what they're looking at. It took me a few years to understand that "enterprise UX" isn't a category. It's a description of stakes.
Right now I'm at Tidal Cyber, where I own the design for a threat intelligence platform. The users are security analysts and architects mapping attacker behavior to their own defenses. Before that: Dell, where I led digital experience work, including a design system used across 6,000+ pages. Before that: ScienceLogic, designing the monitoring systems IT ops teams live in.
The thing I never let go of: whether the decision was right, and whether I can say why afterward. Sometimes a metric tells you. Sometimes it's four customers in four different sectors describing the same thing, and that's the data. I've spent a lot of time in rooms where UX and business strategy are the same conversation. I'm good in that room.
How I work
The work happens before
the mockups.
The artifacts matter. But the value is in what happens between the brief and the build: the questions asked, the assumptions surfaced, the tradeoffs named. I treat every project as a research problem first.
I work best in environments where design has a seat at the table early and collaborates closely with engineering. Most real design decisions happen in those conversations, long before anything is in Figma.
Enterprise software is built by people who understand the system deeply. That's also the trap. I anchor every design decision in how the user understands their work, not how the backend structures data. That tension, resolved thoughtfully, is where good enterprise UX lives.
Consistency saves attention. When users can rely on patterns, they can focus on the work. I invest in design systems because they scale trust: every component that behaves predictably is one fewer thing the user has to figure out.
With AI for skeptical professionals, the hard part is the interface that shows the reasoning. Users who can't see how a system reached a conclusion won't trust it, no matter how accurate it is. My job is to make that reasoning legible without overwhelming the workflow.
WCAG compliance and semantic markup belong in the foundation of a design system, so I build them in from the start. Partly because it's right, and partly because fixing it later is expensive for everyone.
Career
Where I've worked
and what I built.
I've moved through organizations at different stages and scales, from startup to Fortune 500. Each one has shaped how I think about design's role inside a product team.

Design owner across a threat intelligence platform used by security analysts, architects, and leadership to map adversary behavior against organizational defenses. Led design for NARC (AI legibility interface), ATT&CK Coverage Maps, the Tidal Cyber Design System, and the What's New / Unified Landing experience. NARC, Coverage Maps, and the first What's New release are in production; the design system is rolling out page by page with engineering.

Led "Expand Your YOUNIVERSE," a full worldwide marketing experience, end to end. It drove a 130% engagement lift. Built a webpart design system any Dell team could use across 6,000+ pages, with specs and documentation that removed per-page design review, and redesigned AEM workflows so marketing teams could publish on their own.

Designed IT operations management software used by enterprise IT teams to monitor, correlate, and respond to infrastructure events at scale. Collaborated closely with engineering to establish a consistent interface language across a complex, data-dense product.
Outside the work
Things that keep
me thinking.
A few things outside the day job that shape how I design.
Off the clock, I'm a mom of two soccer kids and a breast cancer survivor. I take boxing classes, oil paint, and build apps for fun. I'm a gamer too: Fortnite right now, with plenty of World of Warcraft, Sims 4, and Animal Crossing before that. Home is three cats, a dog, a snake, and some fish. And yes, I love Ford Mustangs, mine most of all.
The clearest version of any design rationale is the one you can explain in plain English. I write to figure out what I actually think.
Most enterprise UX research focuses on what people say they need. I'm more interested in what they actually do: the workarounds, the tab-switching, the rituals that reveal where a system is failing them.
I'm not an engineer, but I know enough React, TypeScript, and CSS to have useful conversations with the people who are. The handoff gets better when both sides understand the constraints.
I've mentored designers at Dell and through ADPList, and I'd like to do more of it. The jump from portfolio work to real product design is steeper than it looks, so I try to be honest about tradeoffs and specific with feedback.
IA is the design decision most users never see and most designers underinvest in. I could talk about nav patterns, labeling, and hierarchy for unreasonable lengths of time.
The question I find most interesting right now: how do you design an interface when the system's reasoning is probabilistic? I don't have a full answer yet, but I'm working on it.
Let's talk about
the work.
Open to Lead, Staff, and Principal UX roles, particularly in AI products, enterprise software, and cybersecurity tooling. If the problem is interesting, I'm interested.