AI literacy as a coaching problem

Most teams endorse “AI literacy as a coaching problem” quickly and operationalize it slowly. With AI in the loop, mentorship shifts toward verification, taste, and accountability. Syntax was never the hard part.

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

Measure what you claim to care about. If AI literacy as a coaching problem only appears in kickoff slides and never in review, incident, or planning artifacts, it is branding. Put a verification signal where people already look.

On AI literacy as a coaching problem, 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.

A scene from delivery

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.

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

Mechanisms

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.

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

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.

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

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.

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

Another texture

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.

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 AI literacy as a coaching problem, 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:

• 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.
• AI tools introduced without coaching on verification, data boundaries, or accountability.
• Feedback that arrives only at review time, when grades feel political instead of formative.

What to do this month

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

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

Critique privately and specifically. Vague encouragement teaches nothing. Vague criticism teaches fear. Specific critique tied to a reusable pattern teaches 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.

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.

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.

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.

Close

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

On AI literacy as a coaching problem, keep the loop short: write the decision, name the owner, verify the outcome.