
I work with growing organizations to install the structure and strengthen the decision-making required to move smoothly when scaling — without losing sight of the culture they want to keep — and then design and implement the systems to support it.
Let’s create the system that supports your goals and your culture.
I send daily field notes and occasional deep-dives for leadership, operations, and systems professionals tired of “best practices” that don’t work in real systems with real humans.
Sign up here. You’ll get a few notes right away and can decide if it’s for you. Unsubscribe anytime.
I design cohesive operating systems built on decision clarity and real operational structure. Then we layer in tools and workflows your team can actually use, so the whole thing sticks.
With human-centered governance and data provenance leading the workflow design and tooling, you end up with a system that is both as usable as it is scalable.
Functionally, a Governance & Systems Officer (CGSO) would be a better fit. I legit may have just made that title up! I joke but accuracy and precision matter when it comes to taxonomy.
This is a role that consolidates fucntions that most organizations require. Mst organizations do not have good name or description for it:
The person whodesigns the operating environmentin a way that reflectsreality.
Authority, decisions rights, workflows, systems, and people actually have come together for the system to stick.And I mean actual reality — not an idealized version of workflow that won't hold under load.
Operational governance goes hand-in-hand with data provenance — regardless of how complex or simple your data is — and it's what's required for a system to become the way you operate.
But complexity in operations is increasing. Your systems won't handle your next chapter — and you know it.
The question is not "what are you going to do about that?"
The question is when.
Addressing it is not optional.
(My clients are the people for whom that last sentence was extra.)
Most organizations I work with are moving fast.
They're expanding, scaling, acquiring, and refining how they operate to meet those demands.
Meanwhile, their systems evolved organically and no longer map to how they actually operate, and the pace of change adds weight and strains resources.
High effort, chaos, drama, whatever you want to call it, is a sign that scaffolding is missing. That structure is what makes growth smooth.
We start with discovery to define the real challenges—mapping what’s functional, what’s creating friction, and where the structural gaps live.
Then we build systems that reflect your actual processes, support your culture, and grow with you.
No bloated tools, generic templates, or cookie-cutter solutions. Just calm, thoughtful, infrastructure that fits—so you can be ready for what's next.

I realize that's not a high bar, and it is worth mentioning for precisely that reason.
Implementing systems takes patience and grit. Even the smoothest projects have frustrating moments. When those moments happen, you want someone who’s easy to work with and genuinely on your side.
A collaborative straight-shooter who is mildly amused but unfazed by chaos? That's me.