Career conversations that change next week’s work: evidence over enthusiasm

With AI in the loop, mentorship shifts toward verification, taste, and accountability. Syntax was never the hard part.

What follows stays on that claim: mechanisms, concrete scenes, and the failure modes that appear when the claim is ignored.

Resist the urge to expand scope into neighboring slogans. If a control does not make Career conversations that change next week’s work more operable for the next person, leave it for another note. Dilution is how coherent essays become stitched scrapbooks.

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

How it actually works

Install the smallest set of mechanisms that make success and failure legible. Skip the program name.

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.

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.

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.

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.

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.

When pressure rises, teams drop the unowned practice first. Put Career conversations that change next week’s work in the path of work — templates, checklists, review norms — or admit it was optional applause.

Where this shows up

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.

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

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

Write one page while the decision is still warm — context, options, choice, owner, revisit date. Verbal alignment on Career conversations that change next week’s work evaporates under ordinary calendar pressure, and Slack archaeology is a poor substitute for a decision record.

For Career conversations that change next week’s work, 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.

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 1:1: one concrete coaching ask, one ownership shift, one written follow-up.
• Quarterly: seniors run a teaching session from a real failure (escaped defect, bad hand-off, stale RAG answer).
• Every month: one public sponsorship act — authorship, presentation, or incident lead.

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.

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.

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

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

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 Career conversations that change next week’s work from your artifacts in fifteen minutes, the practice is still private.