My Approach

Start with the human experience.

The first question I ask on any project isn't "what do we need to say?" It's "who is this person, and what do they actually need right now?"

In AEC, that might be a project manager evaluating construction technology at the start of a complex build. At Salesforce, it was a new customer logging in for the first time, trying to get value from an expensive platform investment before doubt set in. In both cases, the content that helped them most was the content that understood what they needed at that exact moment and gave them precisely that.

Lead with content rather than design.

The best content work I've done happened when content had a seat at the table early enough to shape what was being built, not when it arrived at the end to describe it.

Content strategy isn't a layer applied on top of a finished product. It's part of the design process itself. When a checklist item is placed in the right order, it changes how a user moves through a product. When a product page is structured around user needs rather than internal org charts, it changes what a buyer decides.

Getting that trusted in an organization takes time and evidence. I've done it by showing up prepared, speaking in outcomes, and building the case with work that proves content strategy is a product discipline.

Systems and standards that persist.

Good content at scale requires more than good writing. It requires a system with clear principles, defined standards, and governance that outlasts any individual project.

I've built content frameworks for multi-product AEC ecosystems, digital agencies serving dozens of clients, and enterprise software teams serving hundreds of thousands of users.

A framework that only works when I'm in the room isn't a framework. It's a dependency. I build systems designed to scale without me, and standards clear enough that anyone on the team can apply them with confidence.

Advocacy is part of the work.

Part of my job is always making the case for content. That means translating quality into business outcomes for executives who think in metrics. It means explaining how a content architecture decision will help a user solve their issue all by themselves.

What it looks like to work with me.

I come in as a strategic partner, not a vendor. I'll ask hard questions about who the content is really for and what it's really doing. I'll push back when I think a decision will create problems downstream. And I'll build toward something that's not just good at launch but structured to stay good as it grows.

If that sounds like the kind of collaboration you're looking for, I'd love to talk.