Growing seniors who can grow others

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

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

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.

Write one page while the decision is still warm — context, options, choice, owner, revisit date. Verbal alignment on Growing seniors who can grow others evaporates under ordinary calendar pressure, and Slack archaeology is a poor substitute for a decision record.

Practices with enough detail to copy

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

1

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.

2

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

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.

3

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

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.

4

Every PR review: at least one comment that teaches a reusable pattern.

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.

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.

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

Scenes

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.

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.

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

For Growing seniors who can grow others, 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.

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

Failure modes

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

• Feedback that arrives only at review time, when grades feel political instead of formative.
• 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.

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.

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.

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

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

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.

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.

Close

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

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