🧭 Readme

I originally wrote this for new teammates and stakeholders. I share it publicly because clear expectations create higher-trust, higher-output teams. If we work together, this is how I tend to think and operate.

Last updated: November 2025

Who I am

At heart, I’m a product transformation architect: I care less about individual features and more about the systems that consistently produce good features.

Core philosophy

Systems that ship, teams that thrive

The throughline in my work is simple:

Build systems that make it easier to ship good work, without burning people out.

I think of process as guardrails on a mountain road: they should give talented people the freedom to drive fast while staying safe. When process becomes theater, I’m usually the one asking, “Is this still serving us?”

Context over control

I lead by:

You won’t see me micromanaging tickets. You will see me asking questions, unblocking, and pushing us back to the outcomes we’ve agreed on.

Execution and strategy together

I don’t believe product leaders (or PMs) should choose between “strategic” and “execution” work. The real craft is:

I’m comfortable jumping from a board-level conversation on bets and runway into a working session with a squad to design how we’ll actually ship the next slice.

Lean teams, giant results

I’ve seen teams of 4 outperform teams of 40 when:

I don’t optimize for headcount; I optimize for leverage.

How I approach product

Taste & tools

I gravitate toward tools with a point of view. A few that resonate with how I think:

On the AI side, I’m currently deep into Cursor, n8n, and conversational models like ChatGPT / Claude — not just as assistants, but as building blocks for AI-native workflows and “vibe-coded” prototypes.

Offline, I shoot with a Fuji X-T50. The tactile controls and constraints force intentionality. I bring that same bias for intentional systems into product work.

AI: user flows and agent flows

I believe product leaders need to tinker to really understand AI’s leverage. Right now my exploration is centered on questions like:

At Float, I learned that meaningful AI integration isn’t just about user flows; it’s about agent flows — what the system does in the background on behalf of users and teams. I often literally sketch these as a second layer under user flows.

Collaboration & remote work

Great products come from great collaborations, but collaboration ≠ meetings. Leading teams across 15+ time zones, I’ve found that async-first workflows often create deeper alignment than a room full of people reacting in real time:

We still meet — but the meeting is usually the end of the thinking, not the beginning.

How I work day-to-day

Strategy & transformation work

When I’m brought in to “fix product” or help scale it, you’ll see me:

I prefer:

Small, well-framed experiments → honest feedback → iterate or roll back.

With squads and teams

Working with squads, you can expect me to:

I’m happy to get into the details when it’s useful — but I try not to disempower teams by taking the work out of their hands.

Communication & time

Async vs sync

1:1s

In 1:1s, you’ll often hear me start with:

“What’s on your mind?”

I’m not looking for status reports (we have tools for that). I want to hear:

Time management

I treat my calendar as a focus tool, not just a meeting grid:

I also protect some time for being a present parent and human. I’m transparent about those boundaries and expect teammates to have (and defend) theirs too.

Feedback & decision-making

How I give feedback

You can expect feedback from me to be:

I’ll give feedback both in the moment (if appropriate) and in more reflective 1:1 settings.

How I like to receive feedback

I’d rather hear the hard thing early. Useful feedback for me usually:

Written or live are both fine — whatever feels safest and clearest for you.

Decisions

My decision-making blends:

I’m biased toward:

When a decision is made, I like to write it down: the decision, why we made it, what we’ll watch, and when we’ll revisit.

The “Operating System” metaphor

The simplest way I can describe my role is this:

I’m there to help you install and evolve the operating system for your product organization.

Not just to ship one big feature, but to:

Beyond work

Why I share this

I’ll keep evolving how I work as I learn from new teams, technologies, and contexts. But if you’ve read this far, you should have a clear sense of what it’s like to collaborate with me.

If this resonates and you’re exploring:

I’d love to continue the conversation.