01
Trust Backbone
Every scalable system needs trusted ground: identity, provenance, rules, and explainable boundaries. Without trust, intelligence becomes theater.
Truth→Intelligence→Scale
Operating system
You’re hiring the framework, not just the output.
The throughline is not industry, medium, or artifact. It is a repeatable way of making ambiguity usable: establish trust, compress decision time, move people across the emotional gap.
02
Time-to-Confidence
The product metric that matters when users are under pressure: how long before they know what to do next?
Land→Orient→Act
03
State Transition Design
Do not design screens first. Design the crossing between two states: anxious to capable, stuck to moving, skeptical to trusting.
Pressure→Bridge→Motion
Case files
Proof that the framework has carried weight.
Three contexts. Same pattern: reduce ambiguity, establish trust, and create the next useful move.
Case 01 — Clinician reach
WebMD / Medscape
Clinical education products that turned passive content into practice, feedback, and confident decision-making.
$25Mportfolio
Millionsclinicians
0→1product lines
SystemSimulation, VR, trivia, and decision-based learning products built around clinical rehearsal.
PatternTrust through rehearsal before real-world pressure.
Case 02 — Platform scale
Elsevier / Shadow Health
A scaled healthcare EdTech platform organization operating across software, simulation, delivery, and trust.
95+team
9direct leaders
Platformmodernization
SystemClearer product/engineering rhythms, delivery systems, and simulation-development alignment.
PatternScale through operating clarity, not heroics.
Case 03 — Regulated trust
Regulated Health Systems
Clinical research and healthcare systems where adoption depends on rules, workflow fit, and stakeholder trust.
ContextPPD + clinical research
Domainregulated workflows
Patterntrust systems
SystemDecision support and workflow thinking for environments where novelty cannot outrun trust.
PatternConfidence under constraint before scale.
Workshop
Five rooms. One throughline.
The rooms are not separate identities. They are different workbenches for the same problem: turning latent potential into visible movement.
01 — The Signal Room
Signal
Product strategy, healthcare simulation, AI, EdTech, and trust systems. This is where noise becomes actionable intelligence.
Decision: Make trust the system layer before adding intelligence on top.
Range
The other benches in the workshop.
These are not résumé lines. They are the inputs that keep the work specific, tactile, curious, and resistant to generic thinking.
Line choice
Mountain biking
Momentum, terrain reading, risk calibration, and choosing the cleanest line when the path is changing underneath you.
speed + judgmentModular thinking
LEGO head
Bricks make architecture visible. Constraints are not the enemy; they are the design language.
systems you can holdTaste research
Unfamiliar food
Menus you cannot fully decode. Markets that reset your assumptions. Flavor as a fast route into culture, memory, and pattern.
curiosity under uncertaintyWorld model
Travel
Great Wall, Taj Mahal, Hiroshima, street markets, train stations, wrong turns. The best research often starts without a script.
field notes everywhereFast feedback
Tennis + pickleball
Footwork, anticipation, reset discipline, and the humility of finding out immediately whether your strategy works.
read → move → adjustAnalog repair
1980s boomboxes
Belts, contacts, cracked plastic, old speakers, signal noise. Restoration is a vote for repair over replacement.
Physical making
Painting, clay, LEGO systems, repaired boomboxes, and maker-space concepts all come from the same impulse: make the idea tangible enough to test. The hand catches what language hides.
Now
What I’m building and exploring now.
Current work is framed as signal, not status. The goal is to show direction, judgment, and active learning without turning the homepage into a job-search dashboard.
That same impulse also shaped MKR BAR, a social maker-space concept built around accessible projects, shared tools, and the belief that adults need low-friction places to make things by hand.
Available selectively
Product leadership conversations
Director / VP product roles where trust, platform strategy, healthcare education, and AI adoption matter.
Building
Keel / confidence engine
A decision layer for coaching, pattern recognition, and the next best move when teams are buried in signal.
Writing
Wonder State — novel
A story about AI agents, identity erosion, emotional antibodies, and what remains when the machine performs you better than you do.
Experimenting
Physical AI bench
Robotics, LeRobot-style workflows, 3D prints, LEGO systems, and the practical edge where software touches matter.
Not a product leader with hobbies.
A product leader with an operating system. The making, writing, hiking, biking, LEGO systems, tennis, travel, food curiosity, robotics, old boomboxes, and strange machines are not side quests. They are how the system stays honest: tools amplify judgment, but they do not replace it.
Products fail when they mistake activity for movement. Teams fail when they add intelligence before trust. Interfaces fail when they explain more but help less.
The work I care about shortens the gap between pressure and agency. It gives people a clearer next move, a stronger sense of ground, and enough confidence to begin.