Growing seniors who can grow others: naming the owner

“Growing seniors who can grow others” stops being abstract the moment you ask who gets paged when it fails.

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.

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.

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.

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.

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.

2

Quarterly: seniors run a teaching session from a real failure (escaped defect, bad hand-off, stale RAG answer).

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

3

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

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.

4

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

On Growing seniors who can grow others, keep the loop short: write the decision, name the owner, verify the outcome.