Leadership Philosophy
How I work
25 years of engineering leadership has given me some strong opinions. Here are the ones that shape how I show up.
Real Agile, not ceremony
Standups and sprints are tools, not the destination. I care about iterative delivery, clear ownership, and teams that can inspect and adapt without a ceremony budget. I've built Agile practices from scratch at a Medicaid payer, a manufacturing company, an airline, and a FedRAMP-authorized federal contractor. The context changes. The fundamentals don't. I know the difference between a team that's doing it and a team that's performing it.
Servant leadership
My job is to remove blockers, reduce friction, provide cover when the organization gets noisy, and make sure the people on my teams have what they need to do exceptional work. I don't measure success by my own output. I measure it by what my teams are able to produce and how they grow over time.
The force multiplier effect
The right leadership investment doesn't add to a team's capability linearly, it compounds it. At Bellese, consolidating a fragmented deployment process and building a Jenkins pipeline to automate coordination eliminated 12+ handoffs from a single release cycle. That's the kind of leverage I'm always looking for: structural changes that make the whole team faster, not just one person.
Role clarity scales teams
Expecting engineering managers to sit on the critical path for delivery produces predictable failure modes: technical ownership drifts upward, accountability blurs, and the work that actually scales teams — coaching, process clarity, risk management — gets deprioritized because execution always feels more urgent. Senior engineers and architects own technical direction and code quality. I own team health, delivery reliability, and long-term capability building. That's not bureaucracy. It's how durable engineering organizations are built.
Iterative improvement over big-bang transformation
Small, deliberate, measurable changes — compounding over time — are how engineering cultures actually get better. When I started the code quality initiative at Bellese, the first step was establishing a baseline: zero unit test coverage across most of the codebase. You can't set goals without a starting point. I've seen too many transformations launched with fanfare and abandoned six months later. I prefer boring consistency.
Mission matters
The last decade of my career has been almost entirely in healthcare, and that's not accidental. CareSource is a non-profit Medicaid payer serving hundreds of thousands of members across multiple states. Ad Hoc built and maintained Healthcare.gov for CMS. Bellese supports QMARS, a federal Medicare oversight program. When the systems I'm responsible for work correctly, real people get access to care they need. I've passed on opportunities in other industries specifically because I'd rather do meaningful work.
Fit
Where I do my best work
Organizations where Agile is a real value, not a brand
I thrive in environments where iterative delivery and team empowerment are genuinely how work gets done, not a layer of process on top of waterfall. If your standups are status meetings and your retrospectives are skipped, we should talk about that first.
Teams that want to be built, not managed
I invest in the engineers on my teams: career growth, honest feedback, space to own their work. I look for people who aren't afraid to contribute ideas and have enough humility to know their idea might not always be the best one. That combination is how real innovation happens.
Mission-driven companies
Healthcare, civic tech, education, non-profits — organizations where the work has consequences beyond the quarterly number. The last decade of my career was a deliberate choice to stay in healthcare. That orientation isn't going to change.
Complex, regulated environments
HIPAA, FedRAMP, CMS compliance, ATO — I know this terrain. I know when a new feature might push you outside an ATO boundary, what it takes to keep PHI out of non-prod environments, and how to deliver at pace without using compliance as an excuse for slow delivery.
I'm actively exploring full-time leadership roles and am also open to fractional or hourly engagements for the right organization. If you're not sure whether there's a fit, the best first step is a conversation.