I lead from inside the work. As a manager, I focus on the structure around the work: who owns what, how decisions get made, and where Content Design judgment needs to show up.

Every call we make starts with the customer, grounded in what research tells us they need and what the data shows they actually do.

I don't manage from a distance. I write, revise, and ship content alongside the team, from a single error message to tooltips at scale. Staying close to the work keeps my standards real and my feedback useful.

In practice: Hiring, operating model design, decisions grounded in customer research and data, hands-on writing and revision.

I design the systems that produce content, not just the outputs. Frameworks, workflows, governance, and knowledge bases that let teams ship clear, consistent content at scale. Standards embedded in workflows scale further than standards held in any one person's head.

The goal isn't to centralize Content Design. It's to put Content Design judgment everywhere it needs to be. For AI, that means I define what our AI content tools know and how we know they're working, and I partner with engineering to build them.

In practice: Knowledge base authoring, prompt and golden set curation, quality evaluation for AI-generated content, content patterns embedded in design systems.

When content is right, nobody notices. That's the point.

The smallest piece of content often shows up at the biggest moment. Something failed. Money is on the line. A customer is deciding whether to trust the product. Nobody is reading for pleasure in that moment. They want to know what happened, why it matters, and what to do next.

That's why craft matters to me. It's choosing the one word that removes doubt, cutting the sentence that makes someone hesitate, and doing the hard thinking so the customer doesn't have to. Most content problems are decision problems in disguise, and good Content Design solves the decision before anyone sees the words.

I started as a teacher, and I still think like one.

Before my tech, I spent eight years teaching elementary school in Florida and the Pacific Northwest. Nothing tests an explanation like a room full of kids. If it doesn't land, you'll know in about four seconds, and it's on you to try again.

I still use that every day. Good content is just a really good explanation that shows up right when someone needs it. And the best part of leading a team is the same as the best part of teaching: watching someone figure out they're better at something than they thought.

In practice: Clear explanations at the moment of need, frameworks people can learn from, helping the team grow.