Cross-Functional Friction — Translating Between Worlds
P63.mentoring-collaboration.02 · Audience: guest, it-ml, language-pro · Prerequisites: Coaching Stories — Growth You Caused
A hospital rolls out a new intake form. The lawyer insists on three consent paragraphs; the nurse says patients in pain will not read three paragraphs; the developer says the tablet screen fits eight lines; the interpreter points out that the Somali version runs 40% longer. Four professionals, all competent, all right — and the meeting ends in polite frustration, each privately concluding the others "don't get it". Nobody here is difficult. Four working worlds are colliding, each with constraints the others cannot see. This module is about cross-functional friction as a translation problem — and about the collaborator who makes their own world legible instead of waiting to be understood.
When collaboration across professions grinds, the instinctive diagnosis is character: the lawyer is pedantic, the designer is precious, the engineer is rigid. The better diagnosis is almost always structural. Each profession optimizes for a different failure it has been burned by — the lawyer for the lawsuit, the nurse for the patient harmed, the engineer for the 3 a.m. outage — and each speaks a compressed dialect that encodes those burns. What sounds like obstruction is usually a constraint you cannot see, expressed in a language you do not speak. Interviewers who ask about working with other functions are testing exactly this: do you reach for the character explanation or the translation one?
ⓘ Concept: Behind every 'difficult' function is a constraint you can't see
Why it matters — The reframe changes both your behaviour and your story. Behaviourally, 'they're being difficult' has no move except escalation or endurance, while 'they're protecting something I can't see' has an obvious move: ask what it is. Narratively, a story told as personalities ('the legal team was impossible') quietly tells the interviewer you will call their colleagues impossible too; a story told as translation ('I realized their three paragraphs were armour against a specific regulation, and our real fight was over screen space, not principle') shows a colleague who converts friction into information. The people problem is rare; assume translation first and you will be right most of the time — and fair the rest.
🗣️ From a linguist's perspective: False friends between professions
Every professional life crosses borders: the teacher and the ministry inspector, the interpreter and the conference organizer, the developer and the compliance officer. You already own a translation story — this module is the craft of telling it as one.
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.
Keeping your files on this device
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.
🎓 Practice ladder
2 graded rungs · ~22 minTwo mentor-graded craft rungs. Rung 1 gives you a jargon-dense status note and a non-specialist stakeholder who must act on it by Friday — rewrite it so she can. Rung 2 is your own cross-functional friction story, told as a translation problem with both sides' constraints fairly stated. A low-stakes story is always accepted; the grader assesses the telling, never the life.
Rung 1 — Translate the status note (explorer)
Loading exercise…
Rung 2 — Your friction story, as translation (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?
Later in Mentoring & Collaboration