Technology leadership in healthcare
I lead technology across products, platforms, and operational systems, combining engineering depth, product judgment, and execution discipline to build software that works in the real world.
Recent scope
Internal healthcare operations platforms, consultation systems, and the data and automation layers underneath them.
Selected work
Internal operations platforms, telehealth infrastructure, and analytics systems where structure mattered as much as speed.
01
2025
Reframed a workflow-heavy internal platform around clearer stages, handoffs, and state logic so live operations could move with less ambiguity.
An internal healthcare platform redesign focused less on polish and more on reducing operational ambiguity, tightening workflow structure, and making the system easier to run under pressure.
02
2025
Strengthened consultation workflows around reconnect behavior, media state, and failure recovery under real network conditions.
03
2025
Reworked analytics and reporting workflows so operational teams could move from fragmented exports toward clearer, more actionable visibility.
What I do
Usually where product, systems, and operations are tightly coupled.
01
Leading products and engineering systems from concept through execution with a focus on clarity, speed, and durability.
02
Reshaping fragmented or legacy systems into cleaner, more scalable foundations.
03
Designing software that respects operational complexity instead of pretending it doesn’t exist.
04
Applying automation where it meaningfully reduces friction, improves throughput, and creates durable advantage.
Principles
A few views that shape the work before tools or frameworks do.
01
The goal is not more software. The goal is more capability per unit of effort.
02
Most systems break because teams automate complexity before reducing it.
03
Software should survive messy workflows, not just clean diagrams.
04
Usability, speed, trust, and clarity determine whether systems get adopted.
05
The best internal tools make work easier to think through, not harder.
06
Enterprise software does not get a free pass for being ugly or confusing.
Notes
Short essays with a point of view, not ambient commentary.
Internal tools usually fail before scale because unclear ownership, unstable state logic, and weak workflow structure harden into the product long before traffic is the real issue.
The strongest use of AI in operational environments is reducing repeatable friction across triage, communication, and follow-up, not simulating intelligence on top of weak workflow design.
Software design improves when it accounts for coordination costs, handoff friction, process exceptions, and uneven day-to-day operations instead of assuming a cleaner world than teams inhabit.
Conversation
Selective conversations on technology, product, systems, and advisory work.