How I lead

An operating loop, not a job title

Leadership isn’t a rank - it’s a repeatable loop I run at every engagement: assess, set standards, build the system, then coach the team to run and improve it.

The loop

Four moves, repeated

The same sequence whether I'm running a full-time org or a fractional engagement.

  1. Assess

    Find where chaos needs order and order needs questioning. Understand the system, the team, and the constraints before changing anything.

  2. Set standards

    Make quality, delivery, and expectations explicit - from code review and testing to how decisions get made.

  3. Build the system

    Stand up the CI/CD, metrics, and rituals that let the team ship with confidence and scale beyond any one person.

  4. Coach the team

    Grow people to run and improve the system themselves - including adopting AI with real governance, not hype.

Stage fit

Where I do my best work

Thrive where chaos needs order, and order needs questioning. Best fit: Series A–C and assess-and-improve mandates.

Principles

What I lead by

Principle 01

Player-coach

Lead from the front and stay close enough to the code to make sound technical calls.

Principle 02

Improver, not maintainer

Join at inflection points and leave every team stronger than I found it.

Principle 03

AI with governance

Adopt agentic development with policy, training, and guardrails - measured, not hyped.

Principle 04

Transparency by default

Give leadership real visibility with metrics and honest reporting on the health of the work.