Diagnosing before recommending
Organizations produce enormous amounts of information about how they are supposed to work – policies, procedures, job descriptions, performance reviews, strategies, operating models. But everyday practice is often very different.
Leaders can be removed from how work actually gets done, how consistently their vision is understood below the executive level, and how large the gap can be between regular practice and established best practice. I’ve spent much of my career working to close that gap by understanding the people, the work, and the systems well enough to distinguish the visible symptom from the underlying problem before anyone starts spending money on a solution.
What I’ve learned from running teams is that most people want to do good work. Performance problems are often less about willingness than about the environment around them – unclear expectations, bad business rules, poorly designed systems, competing priorities, and too little reinforcement or support. That’s why I’m skeptical of solutions that begin with training, technology, or reorganization before anyone has clearly defined the problem.

The auditor underneath
I started my career in performance auditing and consulting, where the job was to enter unfamiliar organizations, understand how they were supposed to work, and follow the evidence when reality looked different. That taught me to ask basic questions without assuming the answer, compare multiple versions of the same story, benchmark what I was seeing, and keep digging until the problem was specific enough to act on.
Later, I moved from advising organizations to running functions myself. Leading teams, budgets, priorities, and transformation changed how I thought about recommendations. A solution can be analytically sound and still fail if it ignores the systems, incentives, constraints, and people required to make it work.
That combination – auditor, advisor, and operator – still shapes how I approach complex problems today.
Experience from different perspectives
My work has crossed public-sector auditing, consulting, technology, healthcare, talent, and organizational transformation. I’ve investigated performance problems from the outside and owned them from the inside.
That has meant examining how public institutions perform, leading learning and talent functions inside complex organizations, and working on AI adoption and workforce enablement at scale. The settings have changed, but the underlying work has been remarkably consistent: understand what is actually happening, separate symptoms from causes, and help people make better decisions about what to do next.
My background includes graduate study in organizational performance and public administration, along with professional certifications in talent development, learning strategy, and process improvement.
How I work
I’m direct when I need to be, but I don’t believe candor has to come at someone else’s expense. I try to listen carefully, ask the question behind the question, and help people see the evidence for themselves.
My goal is not to arrive with the smartest answer in the room. It’s to help people understand the problem clearly enough that the right next move becomes easier to see.
If that sounds like the kind of conversation you need, I’d be glad to talk.