Working with me

What it's actually like to have me on your team.

Operating principles

Direct, no fluff

I say the thing. If a plan won't work, I'll tell you why before we've spent a quarter finding out. I'd rather have a short uncomfortable conversation than a long comfortable failure, and I extend the same invitation in reverse: tell me plainly when I'm wrong.

Principles over rules

Rules break at the edge cases, which is exactly where trust and safety work lives. I try to give teams a small set of principles and real decision authority instead of a thick binder. When someone understands why, they can handle the case the rulebook never imagined.

Systems and externalized memory

I write things down, obsessively. Decisions, context, and commitments live in shared systems, not in my head or yours. It makes the work legible, it makes handoffs clean, and it means the team's memory survives any one person's vacation.

Launch gates with real acceptance criteria

Nothing ships on vibes. Every launch has written acceptance criteria agreed before the work starts, and the gate holds even when the deadline is loud. That discipline is what lets us move fast the rest of the time.

Human at the helm

I build and run AI-heavy systems, and the standard is the same everywhere: AI does the volume, a human owns the judgment. Use AI to make people hyper-effective. Never use it to work a reviewer to death or to launder a decision nobody wants to own.

Detection humility

Probability is not ground truth. I won't claim a detector is certain, and I won't let marketing claim it either. "Deepfake likely" is an honest sentence. "This is real" is not one I'll sign.

How I delegate

I hand people problems, not tasks, with the context to own them: what outcome we need, what the constraints are, and where the landmines live. Then I get out of the way and stay reachable. Progress reports I like are short and honest, especially the bad news. Bad news early is a gift. Bad news late is a crisis.

How I work best

I'm AuDHD, and I run my work life with that as a design input rather than a footnote. Deep focus is my superpower, so I guard maker time and batch meetings. Pattern recognition across systems is where I add the most value, so point me at the gnarliest cross-domain problem you have. Externalized memory, written agendas, and clear acceptance criteria aren't bureaucracy to me, they're how I turn a fast brain into a reliable one. If you need a quick answer, write it down and I'll get you a better one than you'd get from catching me in a hallway.

If this sounds like a team you'd want to build with, say hello.