Growing seniors who can grow others: evidence over enthusiasm

The useful version of “Growing seniors who can grow others” is narrower than the slogan: 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.

When pressure rises, teams drop the unowned practice first. Put Growing seniors who can grow others in the path of work — templates, checklists, review norms — or admit it was optional applause.

Resist the urge to expand scope into neighboring slogans. If a control does not make Growing seniors who can grow others more operable for the next person, leave it for another note. Dilution is how coherent essays become stitched scrapbooks.

A scene from delivery

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.

That scene is the thesis under calendar pressure. The response is not another status meeting — it is a control.

Mechanisms

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.

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

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.

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.

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

Measure what you claim to care about. If Growing seniors who can grow others only appears in kickoff slides and never in review, incident, or planning artifacts, it is branding. Put a verification signal where people already look.

Another texture

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

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

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.

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.

On Growing seniors who can grow others, 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:

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

What to do this month

• Every month: one public sponsorship act — authorship, presentation, or incident lead.
• Every 1:1: one concrete coaching ask, one ownership shift, one written follow-up.
• When AI drafts: require a human verification note in the PR describing what was checked and how.

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.

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.

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.

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

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

If someone new cannot explain Growing seniors who can grow others from your artifacts in fifteen minutes, the practice is still private.