I'm a systems designer, operator, and advisor. I see the structure underneath things: the relationships, incentives, assumptions, technologies, and decisions shaping what happens next. My work is making those systems visible enough to understand, change, and build differently.
I've worked across revenue and pricing, data and technology, customer experience, organizational design, and the machinery required to scale a company. The domains change, but the work underneath them is often surprisingly similar: understanding how people, information, decisions, and resources move through a system—and what happens when they don't.
I tend to experience ideas spatially. Systems show up for me as patterns, relationships, and shapes—things I can often see before I can explain them. Much of my work has been learning how to translate what I see into words, structures, technology, and things other people can use.
That translation goes both ways. I can move between the abstract and the practical: from an idea about how something could work to the processes, tools, roles, and decisions required to make it real—and from something that isn't working back to the structure underneath it.
I build systems that hold at scale and under pressure.
I grew up with very little. There were years when my parents, raising six kids, brought in less than $500. We lived on a farm. Making do wasn't an idea; it was ordinary life.
I've spent much of my own life slightly outside the systems I'm in. I'm neurodivergent, queer, and a single parent. Some of that distance has been difficult. Some of it has been useful. I notice patterns, assumptions, relationships, and possibilities that can be harder to see from inside the thing itself.
My sister's accident changed our family, and the years that followed brought disability, care, institutions, advocacy, and dependency into much sharper focus. I learned how much of a person's life can depend on structures they didn't design and have very little power to change.
Eventually I found work where that way of seeing was useful. I've spent my career inside complicated organizations—untangling systems, connecting people and information, questioning assumptions, and building things that have to work in the real world, not just on paper.
I didn't arrive at this work by studying it alone.
