Mentoring in public without performing: the operable version

I care about “Mentoring in public without performing” for one practical reason: it either leaves clearer ownership next week, or it was theater.

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

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

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.

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.

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

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

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.

3

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

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

4

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.

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.

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.

Scenes

A junior with a strong copilot ships fluent PRs. Mentorship is teaching them to distrust fluent wrongness: invariants, authz edges, and “what breaks at 10x load.” Without that coaching, you accelerate confident mistakes.

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.

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.

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

Write one page while the decision is still warm — context, options, choice, owner, revisit date. Verbal alignment on Mentoring in public without performing evaporates under ordinary calendar pressure, and Slack archaeology is a poor substitute for a decision record.

Failure modes

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

• 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.
• AI tools introduced without coaching on verification, data boundaries, or accountability.

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.

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.

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.

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

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

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.

Close

Grow judgment in public artifacts. Hallway wisdom does not compound.

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