I’m usually invited to provide technical coaching.

I enjoy programming with programmers, testing with testers, and managing with managers. I join in the work, observe where we’re going, and offer techniques and habits intended to help us get there.

Along the way, we talk.

My impact, from most to least, stems from:

1. One-on-one conversations
2. Group conversations
3. Anything involving computers

There’s a noticeable drop-off from (2) to (3) — not because I’m an ineffective technical coach, but because I’m an effective coach. Whereas techniques and habits are slow to change, the right conversation can strengthen human connections, uncover insights, and improve conditions for further improvements.

I’m a technical coach. It gets me close enough to have influential conversations.