Mentoring in public without performing: a field note

The interesting constraint is not speed. It is whether mentoring in public without performing: a field note leaves the next person more capable.

With AI in the loop, mentorship shifts. You coach verification, skepticism, and taste — not just syntax.

Juniors do not need motivational speeches. They need safe chances to own a slice, fail without shame, and hear specific feedback.

Process should be light enough to change. If your AI workflow cannot be updated when a model, connector, or compliance rule changes, you do not have a workflow — you have a ritual.

Mentorship that works looks like smaller loops: a review comment that teaches a pattern, a design note that names tradeoffs, a career chat that changes next week’s assignment.

Sponsor publicly, critique privately, and keep a written trail of growth so progress is not a vibe.

Sustainability shows up as fewer retries, right-sized environments, and CI that does not burn cycles for vanity. Efficiency is operational maturity.

On mentoring in public without performing: a field note, the leadership move is to make the invisible visible: ownership, verification, and the path for the next person.

Buy-versus-build debates should start from ownership. If nobody on your team can operate the failure mode, you did not buy a capability — you rented a demo.

I prefer written decisions over verbal ones. Memory is a poor archive, and AI tools make fluent improvisation cheap — which raises the value of durable context.

None of this requires a new framework brand. It requires attention, a short feedback loop, and the humility to change process when agents join the workflow.

Ask your team one question in standup this week: what did we make easier to own?