Product leadership
Doximity
Scaling clinical communication.
- On-call clinician workflows
- Trust and delivery metrics
Product leadership in healthcare and finance.
Product leadership in healthcare and finance.
Building trustworthy systems for regulated teams.
I design safety rails that keep AI accountable so people stay in control in high-stakes settings.
I build tools that keep people in control when stakes are high: clear decision ownership, review paths that work, and reliable recovery when things go wrong. I focus on decision quality under constraints, especially when requirements are fuzzy but the risk is real. I help teams make escalation and accountability explicit so decisions can be reversed safely and fast. I design for end-to-end failure modes: who notices the break, who can fix it, and how quickly. I translate risk, safety, and accountability into operational practice—logs, ownership, and measurable outcomes.
The Proof
A quick scan of the teams and outcomes I have led.
Product leadership
Scaling clinical communication.
Platform strategy
Consumer-directed health experiences.
Founder
Financial immunization for doctors.
Methodology
The research practice behind my product decisions.
My product work is grounded in Ethotechnics—research on decision quality, escalation paths, and reliable recovery in real-world systems.
I evaluate systems by what happens when something goes wrong—and who has the power to force it to change.
Ethotechnics
Full-Stack Context
Three lenses that connect my engineering roots to product and systems leadership.
The Engineer
Focus: The Code
I started in bioengineering, learning how constraints shape behavior.
The Founder
Focus: The Product
I build tools that remove friction for users at Doximity and Andwise.
The Theorist
Focus: The System
I study how institutions allocate time, delay, and decision authority.
Writing
Essays, notes, and audits on building trustworthy systems.
Stop designing for the idealized "Hero User." Learn how to build resilient interfaces that work when your user is stressed, tired, and operating on 15% battery.
Quick details
How to Design for Cognitive Scarcity
Stop designing for the idealized "Hero User." Learn how to build resilient interfaces that work when your user is stressed, tired, and operating on 15% battery.
Resilience is a subsidy we pay to cover the cost of structural failure
Quick details
Optimizing the User
Resilience is a subsidy we pay to cover the cost of structural failure
The interface is dying because the “User” is obsolete. On the post-user web, AI agents, friction economics, and the rise of adversarial infrastructure.
Quick details
The Post-User Web
The interface is dying because the “User” is obsolete. On the post-user web, AI agents, friction economics, and the rise of adversarial infrastructure.
Across healthcare, bureaucracy, and customer service, systems increasingly avoid decisions while appearing responsive. This essay argues that modern governance operates by distributing exhaustion rather than delivering outcomes.
Quick details
We're On It! The Age of Abundant Acknowledgement
Across healthcare, bureaucracy, and customer service, systems increasingly avoid decisions while appearing responsive. This essay argues that modern governance operates by distributing exhaustion rather than delivering outcomes.
The loading screen is a weapon. "Pending" is a governing strategy of attrition designed to make you carry the weight of the process until you give up.
Quick details
Pending: The political economy of waiting
The loading screen is a weapon. "Pending" is a governing strategy of attrition designed to make you carry the weight of the process until you give up.
We keep describing our institutional crisis as one of 'belief' or 'truth.' But in practice, the bottleneck is 'standing.' An essay on why 'we hear you' is a trap, and how to distinguish between providing input and triggering obligation."
Quick details
Credibility/standing as an access-control system
We keep describing our institutional crisis as one of 'belief' or 'truth.' But in practice, the bottleneck is 'standing.' An essay on why 'we hear you' is a trap, and how to distinguish between providing input and triggering obligation."