I'm a technical writer, information architect, and communications specialist who uses systems thinking to make complex information easier to understand, trust, and act on.
What I Do
Most of my work lives in the space between complicated systems and the people trying to use them. That means building technical documentation, multimedia instructional resources, web content, process guides, stakeholder communications, and research-based recommendations for audiences navigating unfamiliar or high-friction systems.
This portfolio brings together writing samples, case studies, and essays connected by one central question: Does the communication actually help people understand what matters and what to do next? I’m especially drawn to public-service communication, environmental and conservation work, accessibility, resilience, and systems that need to earn public trust.
How I Think
I do not think communication starts with the message. I think it starts with the system around the message.
Who needs this information? What are they trying to do? Where are they likely to get stuck? What assumptions are baked into the process? What would “this worked” actually look like?
That is the lens I bring to technical writing, information architecture, and communications work. I like working from the outside in: starting with the user, resident, customer, or stakeholder experience, then tracing the process backward to identify gaps, friction points, unclear ownership, and places where better structure can change behavior. To me, good communication is not just content. It is part of how systems (and the people within them) learn, adapt, earn trust, and help people take the next step.
What Informs My Work
Everything, honestly. My work is informed by personal experience, professional projects, volunteer work, hobbies, frustrations with bad interfaces, and a long-running habit of noticing when a system does or does not work for the people inside it.
I like learning how things work, why they were designed the way they were, and whether they actually do what they were built to do. That lifelong curiosity has shaped how I approach communication. I look for the structure underneath the experience: the process, the audience, the friction points, the assumptions, and the places where clearer information could make the system easier to navigate. Every experience adds another stone to the foundation for how I think about systems, people, and the interfaces between them.
Why Communication?
Systems are everywhere: products, services, civic institutions, informal groups, public processes, and the quiet structures that shape daily life. They matter because people have to live inside them.
That is why I think systems should be judged by how they interact with humans. Do they reduce confusion or create it? Do they make the next step easier or harder? Do they serve people, or do they demand that people serve them?
Communication is the bridge. It is how systems explain themselves, earn trust, support action, and become usable to the people they affect.