Systems that hold up under pressure.
Work
Operations, systems, and the people who make them work.
Most of my work sits at the intersection of technology and operations — where systems, people, expectations, and institutional mission all meet.
Operating principles
How I tend to lead.
The best technical work is not only engineered well. It is operated well, communicated clearly, and supported by people who trust each other.
Clarity, accountability, and consistency.
Teams that can actually operate.
Case study 01
From reactive to reliable.
Building operational structure in growing environments.
In several roles, I have stepped into environments where the technology worked, but the operation around it needed more structure. Systems were fragile, ownership was unclear, and teams were spending too much energy reacting.
The work started with clarity: defining ownership, setting expectations for support and response, and putting better structure around how changes were made. From there, the focus became consistency — standardizing environments, reducing tribal knowledge, and creating repeatable practices the team could rely on.
Just as important was the people side: creating room for questions, mentoring team members into ownership, and building enough trust that responsibility could be shared instead of avoided.
Case study 02
Supporting mission-driven work.
Aligning technology with research and institutional needs.
Research and museum environments bring a different kind of responsibility. The goal is not just uptime. It is helping scientists, researchers, staff, and public-facing teams do their work without unnecessary friction.
That means balancing flexibility with stability, supporting a wide range of tools and workflows, and making infrastructure feel invisible when it is doing its job well.
A big part of the role is translation: helping technical teams understand institutional priorities, helping leadership understand constraints and tradeoffs, and being a steady colleague people can work through complex problems with.
Case study 03
Leading through change.
Modernizing systems while keeping operations intact.
Modernization is rarely just a technical project. It is an operational one. Whether moving to cloud platforms, reworking infrastructure, or evolving internal systems, the challenge is how to move forward without breaking what people rely on today.
My approach is steady and deliberate: understand what actually matters day to day, sequence change so it does not disrupt critical work, and keep communication clear enough that people know what is changing and why.
The mentor and colleague part matters here. Change lands better when people feel supported, when learning is expected, and when leaders help make the path forward feel manageable instead of imposed.
Recognition
Consistent peer recognition.
I have been recognized by OnCon every year from 2022 through 2026, most recently in late April 2026, for leadership in technology and operations.
I appreciate that kind of recognition most when it reflects the work behind the work: building trust, mentoring people, strengthening operations, and helping teams do meaningful work consistently.