Mentoring in public without performing — working notes

Quiet teams often get this right before loud ones do: mentoring in public without performing — working notes is a system of habits, not a quarterly theme.

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

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.

When agents join the loop, treat them like junior systems: limited privileges, explicit tools, budgets, and a human who owns the outcome. Autonomy without audit is just distributed risk.

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

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

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.

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

In practice that means shorter cycles: decide, ship a thin slice, review what broke, coach the pattern into the next person. Long programs without those loops become status machines.

Psychology shows up in engineering as safety to ask questions. Without it, AI only accelerates confident mistakes.

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.

Coaching is the mechanism. Process is the memory. Tools are leverage — only when ownership stays human.