Content designer by trade. Systems thinker by nature. Journalist by training. People person by heart.
About
I’ve spent 20 years making sense of complexity—finding the signal in the noise, asking better questions, shaping the story, and making complicated information clear enough for people and teams to understand why something matters and what to do with it.
I started in newsrooms as a journalist, then moved into digital and mobile experiences. Since then, I’ve worked across content ecosystems, product design, accessibility, systems, mobile platforms, and AI-assisted experiences as a strategist and content designer.
Today, that work takes many forms. Depending on the problem, I might write and prototype a sensitive product flow, synthesize research into strategic direction, build a language system, use AI to streamline a workflow, or create a repeatable way for teams to make better decisions at scale.
I enjoy work that goes deep, and I’m most useful when the context is fragmented, the stakes are high, and no single discipline has the full picture.
I connect people, research, data, product goals, technical constraints, and business needs so teams can move forward with a shared understanding.
My approach
My throughline is the ability to understand complicated systems and information without losing sight of the people who make and use them.
Plot the context. Design the path. Scale what works.
It starts with one core principle: good content is how a product explains itself. Everything else follows from making that explanation clear, useful, and durable.
Curiosity and questions are the sharpest tools I own. Before I write a word or map a flow, I ask: What are we actually trying to say or do? To whom? And why should they care? I gather the evidence and find the context distributed across research, product decisions, teams, and technologies.
Sometimes the problem is a word. Sometimes it is the product logic underneath it. I identify what people need to understand, what the product needs to accomplish, and where user, business, technical, legal, or policy needs collide. I learned the rules like a pro so I can flex, bend, or break them intentionally—and explain why.
Every flow tells a story. The person using the product is the main character, and the experience should guide them through the decisions required to do what they came for. I use language, structure, interaction, and hierarchy to make the product’s logic visible and the next step clear.
Confusion is a bug, not a feature. Jargon, vagueness, inaccessible patterns, and flows that do not add up are product defects. Clarity is a form of respect, and accessibility belongs in the architecture—not at the end of the process.
When a decision is reusable, you do not solve the problem only once. You create a principle, pattern, standard, workflow, or source of truth that becomes the next team’s starting point. That protects the reasoning behind the decision and frees people to focus on the next problem.
Shipping is not the finish line. I look at what the work actually changes—what people do, what the data shows, and whether it delivers the intended value. If it doesn’t, I use the evidence to refine it, rethink it, or stop investing in what isn’t working.
Beyond the work
I helped run a nonprofit animal rescue for 10 years as a founding volunteer, managing events, operations, and a revolving door of volunteers. I’ve also fostered more than 500 dogs and cats—plus birds, rabbits, and guinea pigs. Chaos management is a transferable skill.
I also co-founded a theater company, where I performed, wrote grants, and helped steer the company’s direction. I’ve had a play produced onstage and have written scripts and novellas. Storytelling is one of the ways I understand people and the world.
Neither is separate from how I approach design. Both have taught me about behavior, communication, collaboration, improvisation, competing needs, discipline, responsibility, and what happens when a plan encounters actual living beings.
The work I do matters deeply to me. I care about context because it shapes the experience, systems because they determine whether the experience holds together, and creativity because it opens better possibilities. Most of all, I care about the people who build and use these experiences—their interactions ultimately decide whether a product succeeds.
Also, I’m less serious in person. The rigor is real, but so is the laugh.