Mentoring in public without performing: evidence over enthusiasm

The useful version of “Mentoring in public without performing” is narrower than the slogan: With AI in the loop, mentorship shifts toward verification, taste, and accountability. Syntax was never the hard part.

I will stay on this thesis — no adjacent manifesto, no tour of every neighboring discipline.

Measure what you claim to care about. If Mentoring in public without performing only appears in kickoff slides and never in review, incident, or planning artifacts, it is branding. Put a verification signal where people already look.

Resist the urge to expand scope into neighboring slogans. If a control does not make Mentoring in public without performing more operable for the next person, leave it for another note. Dilution is how coherent essays become stitched scrapbooks.

Practices with enough detail to copy

Cadence beats intensity. These hold when they fit inside weeks people already live.

1

Quarterly: seniors run a teaching session from a real failure (escaped defect, bad hand-off, stale RAG answer).

Critique privately and specifically. Vague encouragement teaches nothing. Vague criticism teaches fear. Specific critique tied to a reusable pattern teaches judgment.

2

When AI drafts: require a human verification note in the PR describing what was checked and how.

The psychology of asking for help is shaped by what got rewarded last time someone asked. If asking is punished as weakness, AI tools will hide mistakes instead of surfacing uncertainty.

3

Every month: one public sponsorship act — authorship, presentation, or incident lead.

Stretch ownership without a safety net is abandonment. Stretch ownership with a named coach, a kill switch, and a debrief is how judgment grows.

4

Every 1:1: one concrete coaching ask, one ownership shift, one written follow-up.

Sponsor publicly. Put someone’s name on the design review invite, the RFC author line, the customer-facing postmortem. Private belief in someone does not compound; public sponsorship does.

Feedback that lands after incidents should arrive within days, tied to a specific decision or omission, and paired with a practice rep. Delayed generic feedback teaches nothing useful.

Pair on the decision, not only the code. Have the mentee write the tradeoff paragraph first, then implement. Judgment is a writing skill under time pressure as much as it is a coding skill.

Seniors need deliberate practice teaching. If the scoreboard only rewards personal velocity, judgment does not scale past one hero.

Scenes

A senior is excellent individually and absent as a teacher. Promotion criteria still overweight personal output. Leadership then wonders why the bench is thin. Change the scoreboard: teaching artifacts count.

A mentee ships a migration with a written plan and a debrief for the team. That single loop teaches more than six months of vague “visibility” talk.

AI-assisted workflows arrive without coaching norms. People paste secrets into tools, accept insecure snippets, and skip tests because the model “looked sure.” Literacy clinics on one failure mode per month beat a single all-hands about AI.

Tradeoffs

The tradeoff in public sponsorship is risk to your own reputation. Take it. That is part of the job. Private cheerleading costs you nothing and buys them little.

With AI drafting, the tradeoff is review load. Explicit verification notes reduce merge regret more than asking people to “be careful.”

The tradeoff in not stealing the work is short-term speed. You will be slower this afternoon so the team is faster next month. Leaders who cannot tolerate that tradeoff become permanent critical path.

When pressure rises, teams drop the unowned practice first. Put Mentoring in public without performing in the path of work — templates, checklists, review norms — or admit it was optional applause.

On Mentoring in public without performing, care that never changes next week’s ownership is performance. Stretch a thin slice, coach the decision, and leave an artifact someone else can reuse.

Failure modes

Each of these is a missing control, not a personality problem:

• AI tools introduced without coaching on verification, data boundaries, or accountability.
• Stealing the work under the banner of helping — the mentee never practices judgment under load.
• Seniors rewarded only for personal output, so teaching becomes unpaid overtime.
• Mentorship as calendar filler: 1:1s that never change assignments or ownership.

Promotion packets should be assembled from artifacts already in the open: RFCs, incident leads, teaching reviews. If the packet requires secret knowledge, mentorship failed earlier.

Teach the verification step out loud when models draft. Juniors copy what seniors check — or what seniors skip.

Keep a light written trail of growth so progress is not a vibe only the manager remembers. Promotion packets should not require archaeology.

Use review comments as teaching artifacts. Prefer “here is the pattern and why it matters in production” over drive-by nits. A review that only polices style teaches compliance, not craft.

Career conversations should change next week’s work: a stretch ownership, a public design, a safer incident role — not only aspirational titles twelve months out.

Seniors need deliberate practice teaching: lead a review huddle, write the onboarding doc, own feedback quality. If you only reward personal velocity, teaching becomes unpaid overtime.

Pairing as coaching is not surveillance. Time-box it, name the learning goal, and leave an artifact. Surveillance pairing produces compliance; coaching pairing produces judgment.

Close

If your calendar is full, shrink the loop — do not cancel the coaching.

If someone new cannot explain Mentoring in public without performing from your artifacts in fifteen minutes, the practice is still private.