About

Designing Trust in AI

How I think about content, AI, and product design.

AI can process information at extraordinary speed, but people still decide whether to trust the outcome. That moment of trust isn't created by the model alone — it's shaped by the experience surrounding it.

I design the content systems that bridge that gap

Through information architecture, content strategy, conversational AI, and product design, I help transform complex enterprise workflows into experiences that feel clear, transparent, and dependable.

My work goes beyond writing interface copy. I define content models, architect knowledge systems, shape AI interactions, and establish governance that lets products scale consistently. Content should influence product architecture from the earliest stages of development — the way information is structured fundamentally shapes how people understand and use technology.

The same conviction, at different scales

Structure first

Content models and taxonomies aren't invisible infrastructure — they're the architecture that determines whether an AI system can retrieve the right answer, and whether a human can find it too.

Voice under pressure

In a conversational AI system, tone isn't decoration. It's what tells someone whether they're being helped or handled — especially in the moment an answer is uncertain.

Legibility as trust

A workpaper, an onboarding flow, a knowledge base — each earns trust the same way: by making the system's logic visible instead of asking people to take it on faith.

Governance that scales

A content system that only works while I'm maintaining it isn't a system — it's a bottleneck. Governance is what lets structure survive contact with growth.

Content design is becoming something broader

As AI becomes embedded in enterprise software, I see content design evolving into something broader: designing the communication systems that let people and AI work together with confidence.

That's the work that excites me most — not making an AI product sound trustworthy, but building the structure underneath it that makes it actually be trustworthy.

It's why I don't think of myself as someone who writes interface copy after the design is done. I think of myself as a content systems designer — someone whose materials are information architecture, conversational logic, and governance, as much as words on a screen.