What I do
I help teams make sense of work that technically functions, but only because a lot of important context lives in people’s heads.
This usually shows up as:
processes that fall apart when someone is unavailable
repeated questions that no one has time to document
systems that feel fragile as teams grow
I go into those situations, figure out how things actually work, and turn that knowledge into documentation, training, or reference materials that other people can use without guesswork.
The goal isn’t speed or scale — it’s stability, clarity, and fewer things breaking when conditions change.
How I got here
I didn’t start out trying to “build clarity systems.”
I spent years inside teams where I was the person answering the same questions, handling edge cases, and making judgment calls that weren’t written down anywhere. Over time, it became clear that the work wasn’t hard because it was complex — it was hard because the rules lived in people’s heads.
Instead of jumping straight to design outputs, I started paying attention to:
what people were confused about
where decisions stalled or escalated
which explanations actually helped
That naturally led to documenting processes, creating examples, and translating messy reality into something other people could reliably use.
Sometimes that work takes the form of:
a clarity audit to figure out where confusion or risk really lives
documentation for a single fragile system
training or educational materials when understanding matters more than persuasion
The deliverables change, but the outcome is consistent:
less confusion, fewer repeated explanations, and systems that don’t depend on one person remembering everything.