Coaching Stories — Growth You Caused

P63.mentoring-collaboration.01 · Audience: guest, it-ml, language-pro

Influencing Without Authority Cross-Functional Friction — Translating Between Worlds

LLM grading (this page):Real gradingOff — no LLM calls

"Tell me about someone you mentored from struggling to strong — what did you actually do?" A senior interpreter answers warmly: a junior colleague was overwhelmed in her first conference season, "so I took her under my wing, we talked a lot, I encouraged her, and by spring she was flying." Every word true, and the interviewer has learned nothing. Who diagnosed why she was drowning? What changed because of the mentor — a habit, a technique, a booth assignment? The story credits the mentor with the weather. This module is about mentoring stories where the other person's growth is the visible result and your specific actions are the load-bearing spine connecting the before to the after.

🗺️ So far you have built: the P60 answer architecture — decoding the question behind the question, STAR, calibration — and, if you took it, the story bank. This pillar applies that craft to a particular family of questions: the ones about how you work with, grow, and repair relationships with other people.

In this module you will: the coaching story: why 'they grew' is the result but never the evidence, how to diagnose the reason someone struggles before prescribing anything, the difference between scaffolding (they climb) and rescuing (you carry), and how to measure growth you caused — what they can do now that they could not do before. It closes on a two-rung ladder: diagnose a given struggling-colleague scenario, then tell your own mentoring story with the diagnosis, your actions, and the measurable change.

Step 1 / 5 — Their growth is the result; your actions are the spine

A mentoring question is decoded like any other (P60): the capability under test is causing growth in someone else — deliberately, repeatably, not by luck or proximity. That decoding has a sharp consequence for the telling. The happy ending belongs to the other person: they pass the probation, run the meeting, hold the booth. But an ending proves nothing about you unless the middle of the story is a chain of your own decisions that plausibly produced it. "I supported her and she improved" has a you-shaped hole exactly where the evidence should be.

ⓘ Concept: A mentoring story is graded on the causal chain, not the outcome

coaching story = their before → your diagnosis → your specific moves → their after, checkable

Why it matters — Interviewers hear 'I mentored juniors' constantly; what separates a real coach from a friendly desk neighbour is whether the candidate can name the mechanism — what they observed, what they concluded, what they changed, and how that change shows up in the mentee's work. A story that skips from 'she was struggling' to 'she was thriving' is unfalsifiable and interchangeable; a story with a visible mechanism survives every follow-up ('what exactly did you change?', 'how did you know it worked?'). This also keeps the credit honest: the mentee did the growing — your evidence is the scaffolding you built, not the person you claim to have built.

🗣️ From a linguist's perspective: The teacher's report card problem

A language teacher cannot claim credit for "the student improved" — students improve for a dozen reasons, including time. What a teacher can claim is the intervention: "her writing plateaued because she translated word-by-word from Russian, so I switched her to reformulation drills, and within a month her essays stopped reading like translations." The diagnosis and the drill are the teacher's; the improvement is the student's; the link between them is the story.

✅ Key takeaways

A mentoring question tests whether you cause growth deliberately. The mentee's happy ending is the result, never the evidence — the evidence is the causal chain of your own observations, decisions, and moves connecting their before to their after.
Diagnose before you prescribe. People struggle for different reasons — missing skill, missing clarity, missing confidence, wrong fit — and each demands a different move. One precisely observed cause makes you sound like a coach; three generic remedies make you sound like a bystander.
Scaffold, don't rescue. Rescuing transfers the work to you and teaches the person that struggle summons a saviour; scaffolding restructures the task so they complete it themselves, and is designed to be removed. Name the rescue you declined — that judgment is exactly what's being probed.
Measure growth as a capability delta: what they do unassisted now that they couldn't before, witnessed by someone who isn't you. The strongest close: the person you grew now grows others — which is also how 'raising the team's standards' is honestly measured.
The story shape: before → diagnosis → your moves → after. Ninety seconds, every follow-up question landing on something you actually did.
This module pointed the P60 evidence discipline at growth you caused in one person; the next widens the frame to collaboration across professions, where nobody is anybody's mentor and the friction to master is translation, not teaching.

Next: P63.mentoring-collaboration.02 — Cross-Functional Friction — Translating Between Worlds

Whether you have formally mentored anyone or not, you have caused growth in someone — a student, a junior, a peer who asked for help twice. The craft here is retrieving that incident and telling it so the mechanism shows.

Ask the mentor about this module

Ask a question about this content. The mentor explains and grounds its answer in what you are studying; asking is recorded as a learning signal, not a grade.

Images, PDF or text. Kept on this device only.

Keeping your files on this device

Keep a copy of the files I attach, in this browser

Off by default. The mentor always gets your file; this only decides whether your own copy stays here. Copies live in this browser only - they do not follow you to another device, and clearing site data removes them.

Ctrl/Cmd + Enter to send

🎓 Practice ladder

2 graded rungs · ~20 min

Two mentor-graded craft rungs. Rung 1 gives you a struggling new hire to diagnose: name why she is drowning and the scaffolding move that fits — not the rescue. Rung 2 is your own mentoring story in the full shape: diagnosis, your specific actions, measurable growth. A low-stakes story is always accepted; the grader assesses the telling, never the life.

Rung 1 — Diagnose, then scaffold (explorer)

Loading exercise…

Rung 2 — Your mentoring story (practitioner)

Loading exercise…

Try it yourself

A scratch console for this page's ideas — ungraded, nothing you run here is recorded.

Scratch console

A scratch console with the scientific stack (pandas, numpy, scikit-learn). Runs on the server — no network, resource-limited and measured.

Output appears here.

My notes on this module

Loading your notes...

Where next?

Continue

Cross-Functional Friction — Translating Between Worlds →

Mentoring & Collaboration · P63

Later in Mentoring & Collaboration

This module unlocks

Credit, Blame & Team Conflict

Go up a level