Mentoring in public without performing

“Mentoring in public without performing” stops being abstract the moment you ask who gets paged when it fails.

Teaching judgment means letting people own a slice, fail without shame, and hear specific feedback before the lesson evaporates.

The rest develops that one idea with controls you can install and failure modes you can recognize.

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.

Keep the unit of progress small enough to finish under a full calendar: one owner clarification, one verification signal, one reversible control. Grand programs without weekly evidence become status machines.

How it actually works

Install the smallest set of mechanisms that make success and failure legible. Skip the program name.

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

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: lead a review huddle, write the onboarding doc, own feedback quality. If you only reward personal velocity, teaching becomes unpaid overtime.

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.

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.

When someone freezes asking for help, treat it as a systems smell. Latency to ask questions predicts incident severity. Psychological safety is an engineering control.

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

Where this shows up

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.

Feedback arrives only at performance review. By then it feels political. The fix is weekly specific notes tied to artifacts — PR comments, decision records, incident roles — so the review is a summary, not a surprise.

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.

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.

For Mentoring in public without performing, the inheritance test is blunt: after a week, can someone outside the original room explain what changed, who owns it, and how you will know if it breaks? If the answer depends on hallway memory, you still have a story — not a practice.

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.

Failure modes

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

• Seniors rewarded only for personal output, so teaching becomes unpaid overtime.
• Feedback that arrives only at review time, when grades feel political instead of formative.
• Mentorship as calendar filler: 1:1s that never change assignments or ownership.
• Stealing the work under the banner of helping — the mentee never practices judgment under load.

What to do this month

• When AI drafts: require a human verification note in the PR describing what was checked and how.
• Every 1:1: one concrete coaching ask, one ownership shift, one written follow-up.
• 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.

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.

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.

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.

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

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

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

The measure of mentorship is whether the next hard problem can be owned by someone else — with you still available, not required.

Carry the claim as a habit, not a brand: Mentoring in public without performing either compounds ownership or it was applause.