A Different Kind of Operations Leader
A more useful introduction than a job history is the question a leader asks when something is not working, and the system that question leads to.
The question
Most operations leaders are introduced by where they have been: a function, an industry, a list of tools. I would rather be introduced by the question I ask when something is not working, which is always the same one. What system is producing this result?
That question changes what you see. A missed target is rarely a people problem or a technology problem on its face. It is usually a handoff nobody owns, a definition that two departments hold differently, or a decision made without a clear view of the work. The result is what the structure was built to produce, and until the structure changes, the result will return no matter how hard good people push against it.
It is also a harder question to ask than it sounds. Asking who caused a result is quick, and it ends the conversation with a name. Asking what produced it takes longer, and it often points back at the arrangement everyone, including the person asking, has been working inside. The first question protects the structure. The second puts it on the table.
How I learned to see it
I learned to see this from the inside. I began in financial aid, a regulated environment where one process touches students, federal rules, and several offices at once. As a counselor and systems analyst I used the system every day, and I wrote SQL reporting that the office kept using after I left. At Columbia College Hollywood I automated the financial aid workflow from FAFSA submission through award notification as assistant director. Later I diagnosed the revenue operations of other organizations, built a complete revenue operating system at P3 Cost Analysts, and moved into data governance and decision support at Walmart and Adobe. Each step added something new: using the system, fixing it, building it, and governing it.
What stayed with me from those years is how much the work looked like the system rather than the people in it. The same counselors, placed in a different arrangement of offices and rules, would have produced a different year. That is a modest observation, but the rest of my career has been built on it.
What I do now
Today, as Managing Director of Revuity Systems, I do the whole job for clients. I diagnose the operation, design the better one, implement it, and stay to run it afterward, across more than 24 engagements. At the Higher Education Assistance Group, a regulated Title IV operation that depended on manual work and spreadsheets now runs on a governed multi-agent platform, and case-processing capacity rose 25% without added headcount.
The first weeks of an engagement are unglamorous. I sit with the people closest to the work and ask them to show me how a single case moves, from the moment it enters to the moment it is done. I note every place it waits, and at each one I ask who knows where it stands. The gaps in those answers are usually where the structure is working against the people inside it.
I use data science, analytics, and engineering throughout, because a design that nobody builds is only an opinion. But they are the supporting clause. The leading one is the question, and the discipline to keep asking it until the structure behind the symptom is clear.
What it means for a hiring manager
For a hiring manager, this is what it means in practice. I will want to understand how your operation actually works before I change any part of it. I will tell you plainly what I find. And I will measure whether it improved.
None of that requires a new tool to begin. It requires an operation willing to be looked at, and a result worth improving.
If this describes an operation you’re responsible for, the diagnostic is where that conversation starts.
How engagements begin
