Mentoring in public without performing: what fails first

Mentorship that survives calendar chaos is a set of small, observable loops — not a quarterly speech about growth.

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

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.

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

What fails when you skip it

Teams already have scars. Naming the failure modes precisely is faster than inventing a framework brand.

Seniors rewarded only for personal output, so teaching becomes unpaid overtime.

AI tools introduced without coaching on verification, data boundaries, or accountability.

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.

Controls that answer those failures

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

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.

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.

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.

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.

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.

A concrete scene

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 mid-level engineer wants promotion. Their manager talks about “visibility.” A better move: sponsor them to own a migration with a written plan, a kill switch, and a teaching review for the team afterward.

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 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.

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.”

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.

Specific feedback tied to a PR, RFC, or incident role compounds. Vague encouragement at review time feels kind and teaches nothing.

What to do this month

• Every 1:1: one concrete coaching ask, one ownership shift, one written follow-up.
• Every PR review: at least one comment that teaches a reusable pattern.
• Quarterly: seniors run a teaching session from a real failure (escaped defect, bad hand-off, stale RAG answer).
• When AI drafts: require a human verification note in the PR describing what was checked and how.

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

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

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.

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

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.

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.

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.

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.

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.