Leadership operating style
How I lead.
By making ownership clear, keeping technical decisions tied to delivery outcomes, and creating enough structure for people to do serious work — without hiding behind process.
01
Team Building
I have grown an engineering team from just me to 24 engineers, distributed across the US and organized as several teams, each with its own lead. That work is hiring, mentoring, role clarity, technical coaching, and helping senior engineers take ownership without routing every decision through me.
The goal is not more headcount. The goal is a team that can make good decisions, recover from ambiguity, and deliver without burning trust.
See it in practice: Sixteen years of Skyward →02
Delivery Cadence
I prefer practical operating rhythms: clear priorities, visible risks, increments small enough to inspect, and direct communication when tradeoffs change.
On enterprise platforms, my team owned the finished product. That meant coordinating executives, product stakeholders, domain experts, and partner engineering teams in India, Brazil, Egypt, Mexico, and Europe, and integrating their work into what we delivered.
Process is not the product. It earns its keep when delivery gets more predictable and decisions get easier to audit.
See it in practice: Fifteen years with Syngenta →03
Technical Trust
I stay close enough to architecture, code, data, reliability, and operational constraints to evaluate tradeoffs with senior engineers. I do not need to be the deepest specialist in every subsystem — I need enough range to ask useful questions and spot weak assumptions.
That matters most in platform modernization, where the hard part is rarely a framework choice.
The hard part is sequencing change while the business still needs the system to run.
See it in practice: 20 systems to AWS in six months →04
Stakeholder Management
I translate between business goals, product constraints, and engineering reality. That means naming risk early, keeping promises precise, and connecting technical-debt conversations to operational or commercial consequences.
I am comfortable being the person who makes ambiguity discussable — instead of letting it leak into missed dates, vague architecture, or quiet team frustration.
See it in practice: Platform partnerships that lasted a decade or more →05
Sustainable Ownership
I have repeatedly worked toward transition-to-internal-team models, where mature systems, practices, and roadmaps end up owned by the organization that depends on them. That requires documentation, mentoring, observability, operational hygiene, and honest conversations about what the team is ready to own.
The best outcome is not a team that depends on one heroic operator.
See it in practice: The Syngenta handoff, 2026 →Why I do this
Agriculture runs on handshakes. It is a trust-based industry where reputation is the only durable currency, and I have worked the same way my whole career — a fifteen-year working relationship does not survive on contracts alone.
The point of modernizing legacy systems is not the technology. It is freeing people to do the things humans are actually good at — solving problems and being creative — instead of filling out forms.
We are citizens of our community first and business leaders second.
