Mentoring That Actually Changes Careers  🔗 **Source:** [Mentoring That Actually Changes Careers](https://www.youtube.com/watch?v=PPM2ODdo2t8#transcript) > [!note]+ Document Notes > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > > > [!note] Provenance note: the source transcript's ASR tool mislabeled this talk's language as Finnish ("fi") due to auto-speech-recognition noise, but the talk itself is delivered entirely in English. The doc's HTML content is a lightly cleaned-up reconstruction of the English paragraphs from that noisy transcript — a deviation from strict verbatim-only sourcing, disclosed here for transparency. > > --- > tags: [mentoring, career-development, leadership, coaching, workplace-relationships] > author: Lenni Ojala > source: Conference talk (YouTube) > reference: https://www.youtube.com/watch?v=01m0fkbx3x1kt01jr8ssm06zyf > date created: 2026-08-20 > > --- > > # 🏷️ Title: Mentoring That Actually Changes Careers > <!-- deep-read:sections start --> ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - No external links or citations were spoken in the talk beyond a quote attributed to the speaker's own mentor, Hannah. ## 📝 Summary - Lenni Ojala, marking 20 years in software, gives a personal-narrative talk distinguishing mentoring from sponsoring, coaching, and teaching, then walks through the "levels" of mentoring (peer, next-level, skip-level, reverse) and several concrete mentoring stories from both sides of the relationship. - Why it matters: mentoring is often conflated with coaching or sponsorship in workplace programs, which leads mentors to apply the wrong technique (e.g., pure questioning) when a mentee actually wants direct experience-based advice. - Key stakeholders: individual contributors and managers seeking career mobility, workplace mentorship-program designers, and mentors themselves, who Ojala argues also benefit — mentoring functions as low-stakes practice for listening skills. - Risks/tradeoffs: mentors who assume rather than ask what a mentee needs can waste the relationship's value, as in Ojala's own admitted mistake with a PhD-holding mentee who needed practical orientation, not GROW-model coaching questions. - Bottom line: mentoring works when mentors are curious, ask before assuming, and are willing to "tell shamelessly" about their own lived experience rather than withholding opinions in the name of neutrality. ## 📖 Main Content - **Core distinctions.** Mentoring = guiding growth via shared lived experience and direct advice. Sponsoring = actively using positional power/influence to open doors or promotions (a stronger, rarer intervention). Coaching = provoking new thinking through questions, withholding direct advice. Teaching = transferring a specific skill or tool. Ojala's talk stakes out mentoring as the middle ground: opinionated advice-giving without the institutional lever of sponsorship. - **Levels of mentoring**: peer (same level, e.g. two engineering managers comparing notes on a specific initiative like continuous-delivery adoption), next-level (one level up, understanding a target role without the political charge of your own manager), skip-level (two levels up — described as the most career-impactful for promotion because it reveals how bigger decisions are made), and reverse (a junior person mentors a senior one — most effective outside one's own company, to avoid power-dynamic interference). - **Personal origin story**: after being laid off, Ojala approached a speaker at a conference and asked for mentoring. The mentor's two pieces of advice were experiential (noticing Ojala's posture/confidence at a dinner and correcting the self-perception) and relational (a genuine interest in Ojala's situation before giving guidance). Two weeks later, Ojala signed a contract leading a four-person engineering team. - **Role-model mentoring**: Ojala's roller derby coach, Pepper, is cited as an unofficial leadership mentor — noted for developing teammates (not just her own skill), total presence during drills, and modeling that seriousness/focus and fun/personality aren't opposites. The lesson generalizes: mentors don't have to come from your own professional domain. - **Two mentee case studies**: (1) a recent graduate working a multi-system kiosk job who wanted to break into tech — Ojala helped reframe her existing (unpaid-labor-adjacent) systems experience on her CV rather than pushing new coding side-projects, and she landed a customer-support tech role within months. (2) A sole full-stack developer maintaining a widely used app in an "old-fashioned" JS stack who assumed she needed to learn new technology to be hirable — Ojala's reframe was that she needed better self-presentation of existing depth, not new study, and she got a new job while picking up newer tech on the job. - **The GROW model** (Goals, Reality, Options, Way forward/commit) is used as the default coaching structure when a mentee has no specific question, with an explicit twist: always add one "over-the-moon" unrealistic option to unlock creative thinking, and later explicitly switch registers ("now I'm going to tell you what I actually think") when moving from coaching mode into mentoring mode. - **The key mistake**: mentoring a PhD-credentialed former researcher new to corporate work, Ojala defaulted to GROW-model coaching questions when the mentee actually needed literal orientation ("how does this corporate thing work?") — a case of assuming rather than asking, framed as the talk's central cautionary lesson. - **Meta-benefit for the mentor**: mentoring functions as a low-power-differential space to practice listening (no performance-review or salary authority in the room), which Ojala says transfers back into her own management practice. ### 🗒️ Notes // No timestamps present in the reconstructed transcript (ASR-noise cleanup removed original timing markers); dense notes provided without timestamp subheadings. - Mentoring ≠ sponsoring ≠ coaching ≠ teaching — this fourfold distinction is the spine of the talk and is worth using as a diagnostic before starting any mentoring relationship or program. - The "levels" framing (peer/next-level/skip-level/reverse) is a practical taxonomy that maps directly onto how to *seek out* mentors, not just how to *be* one. - Both mentee case studies hinge on reframing existing experience rather than acquiring new skills — a repeated pattern that could itself become a checklist item for career mentors ("is this a skills gap or a narrative gap?"). - The central failure story (PhD mentee) is notable for being self-disclosed rather than hypothetical — a credibility-building rhetorical choice. - Quote from Hannah (Ojala's own mentor, described as building both workplace mentoring programs and bike-repair mentoring programs for women): mentoring is framed as reciprocal, and its core offering is unconditional support plus willingness to answer hard questions. ## 📚 References - No primary sources, studies, or named external publications were cited in the talk. The only attributed non-Ojala voice is Hannah, described only as the speaker's own mentor and workplace-mentoring-program builder — no full name, publication, or verifiable source given. ## 🗣️ Paraphrase - Opening: Ojala frames the talk as a personal retrospective marking 20 years since graduating with an eclectic degree (telecom engineering, project management, marketing, creativity, gender studies), and recalls an early leadership lesson from a professor about prioritizing important-but-not-urgent work to avoid perpetual firefighting. - Definitions section: mentoring is distinguished sharply from sponsoring (using influence/position to move someone's career), coaching (question-driven, advice-withheld), and teaching (skills/tool transfer) — mentoring sits in a permission-to-advise middle zone. - Levels section: peer, next-level, skip-level, and reverse mentoring are each defined by relative organizational position and what each is best suited for (skip-level for promotion insight, reverse for humility and staying current). - Layoff story: a chance conference encounter after a layoff produces career-changing advice about confidence and being genuinely seen, followed by a fast job outcome. - Pepper story: a non-professional leadership role model (roller derby coach) demonstrates that mentors can come from entirely outside one's field, and that seriousness and personality can coexist. - Two mentee stories: both resolve via reframing existing experience, not new skill acquisition. - GROW model section: a structured coaching tool used as a default opener, paired with an explicit verbal signal when switching from coaching to mentoring register. - Mistake story: a self-critical account of assuming a mentee's need (coaching) instead of asking (she needed direct informational answers), used to state the talk's central lesson. - Hannah quote and closing reflections: mentoring reframed as being about feeling "seen," and as unexpectedly valuable to the mentor's own listening skills — closing advice is to be curious, listen actively, and share lived experience without hedging. ## 📰 Newsletter - 🎤 **Mentoring, unpacked**: Lenni Ojala's 20-years-in-software retrospective draws a clean line between mentoring, sponsoring, coaching, and teaching — a distinction worth stealing for any WordPress community mentorship program (Core, Training, Community teams all run informal mentoring already, often without naming which mode they're actually in). - 🪜 The **peer / next-level / skip-level / reverse** ladder is a ready-made framework for structuring WordCamp speaker mentorship or Core contributor onboarding — skip-level conversations in particular are flagged as the highest-leverage move for anyone chasing a promotion or a bigger contribution role. - 🧭 The talk's most transferable lesson: **ask before you coach**. A mentor who assumes a GROW-model coaching session is what's needed — instead of a mentee who just needs a straight answer — can waste the whole relationship. Good checklist material for anyone running Community or Training mentor-matching. - 🛼 Bonus: leadership role models don't have to be in tech at all — Ojala's roller derby coach gets equal billing with her professional mentors. ## ✅ Action Items #### DevRel - Developer advocacy: build a lightweight "mentoring mode selector" (mentor/sponsor/coach/teach) into any DevRel mentorship-matching intake form so both sides name the mode explicitly before a first session. - Education: run a workshop teaching the GROW model plus the "ask, don't assume" correction as a single 60-minute session for new internal mentors. - Developer experience: none directly applicable — this talk is about interpersonal mentoring, not tooling/docs. - Developer marketing: not applicable — no marketing content in this source. - Community management: use the peer/next-level/skip-level/reverse taxonomy to structure a mentor directory so members can self-select the level of mentoring they're seeking. - Internal/external/cross-project: encourage skip-level mentoring conversations across project boundaries (e.g., a contributor mentored by a maintainer two tiers up in an adjacent open-source project) to reduce internal power-dynamic friction, per Ojala's point about reverse mentoring working best outside one's own org. #### OSPO - Policy & Governance: not directly addressed in this source. - License Compliance: not applicable. - Security Management: not applicable. - Software Inventory: not applicable. - Developer Support: incorporate the "reframe existing experience, don't assume a skills gap" lesson into contributor-support consultation hours — many contributors underestimate transferable experience the same way both of Ojala's mentees did. - Community Engagement: consider a formal reverse-mentoring track pairing senior maintainers with newer contributors, framed explicitly (per the talk) as most effective when it crosses organizational boundaries. - Strategic Alignment: not directly addressed. #### Community - Maintainers: skip-level mentoring conversations (contributor <-> maintainer two tiers removed) could be formalized as a recurring "ask a maintainer" rotation. - Contributors: build reframing/CV-style "show what you actually did" support into first-issue onboarding materials, mirroring the kiosk-worker case study. - Sponsors: not directly addressed — this talk does not cover sponsorship funding models. - Ecosystem: cross-project reverse mentoring (as above) could double as a light-touch ecosystem coordination mechanism. #### WordPress - Core: pair new contributors with skip-level mentors (e.g., component maintainers) rather than only peer mentors, to accelerate understanding of release-cycle decision-making. - Core Performance: not directly addressed. - Core AI: not directly addressed. - **Core Program Team:** consider naming which "mode" (mentor/coach/sponsor/teach) each formal program role is playing, to avoid the exact mismatch Ojala describes in her key-mistake story. - Mobile: not directly addressed. - Playground: not directly addressed. - Community: adopt the four-level mentoring taxonomy for WordCamp speaker mentorship matching. - Training: incorporate the GROW model plus explicit mode-switching language into Training team mentor certification materials. - Marketing: not directly addressed. - Support: apply the "reframe don't re-skill" lesson to Support team onboarding for volunteers moving from support into development roles. - Design: not directly addressed. - Documentation: not directly addressed. - Photos: not directly addressed. - TV: not directly addressed. - Polyglots: not directly addressed. - Accessibility: not directly addressed. - Meta: not directly addressed. - CLI: not directly addressed. - Hosting: not directly addressed. - Tide: not directly addressed. - Openverse: not directly addressed. - Themes: not directly addressed. - Plugins: not directly addressed. #### The WPOCC - Programs: consider a formal skip-level mentoring track within any WPOCC fellowship program, explicitly named as such. - Projects: not directly addressed. - Funding experiments: not directly addressed. ### FAIR - Technical independence: not applicable to this source. - Policies and covenants: not applicable to this source. - Productized governance artifacts: not applicable to this source. ## 🧪 Hypotheses - H1: Mentees who receive help "reframing existing experience" rather than acquiring new skills land new roles faster than those pushed toward upskilling alone. - H2: Naming the mode of a mentoring relationship explicitly (mentor vs. coach vs. sponsor vs. teacher) at the outset improves mentee-reported satisfaction versus unnamed/implicit relationships. - H3: Skip-level mentoring relationships correlate with higher promotion rates than peer-only mentoring relationships. - H4: Reverse-mentoring relationships that cross organizational boundaries produce more candid feedback than those within the same organization. - H5: Mentors who actively mentor others report improved active-listening performance in unrelated management contexts (the "communication laboratory" effect). ### 📊 Methodology - H1/H2 could be tested via a matched-pairs survey of program-based mentees, comparing self-reported job-search outcomes against whether their sessions were framed as skills-development vs. narrative-reframing, and whether mode was explicitly named. - H3 is testable retrospectively using existing internal promotion data cross-referenced with self-reported mentoring relationship type, if an organization tracks mentoring participation. - H4 would require a controlled comparison of reverse-mentoring pairs inside vs. outside a shared employer, rated by both parties for candor/psychological safety. - H5 could use a pre/post 360-review listening-skill rating for managers who start a mentoring relationship as the mentor. ### ❓ Questions - Does the "ask before assuming" failure mode scale differently in formal (assigned) mentoring programs versus organic, self-initiated ones like Ojala's conference-dinner story? - How much of the reframing success in both mentee case studies is attributable to Ojala's specific coaching skill versus the general technique being replicable by less experienced mentors? - Is skip-level mentoring's promotion advantage causal, or does it select for mentees who are already more visible/ambitious? - What happens when a mentee explicitly wants sponsorship but a mentor can only offer mentoring — how should that mismatch be surfaced early? ### 🔮 Future Research - A longitudinal study tracking mentee career trajectories against which "level" of mentoring (peer/next-level/skip-level/reverse) they primarily received. - Comparative research on mentoring outside one's professional domain (the "Pepper effect") versus within-domain mentoring, on leadership-skill transfer. - Study of the "ask, don't assume" failure mode as a general mentoring anti-pattern, potentially generalizable beyond career mentoring into other advisory relationships (therapy-adjacent coaching, technical pairing, etc.). ### 💡 Implications - Practice: mentorship program designers should build in an explicit "mode-naming" step and should train mentors on the GROW model *and* on recognizing when GROW is the wrong tool. - Policy: organizations with formal mentoring programs could require intake questions that distinguish "I want advice" from "I want to think out loud" from "I want you to open a door for me," routing accordingly. - Security: not applicable to this source. - Education: the CV/self-presentation reframing technique used in both mentee case studies is directly transferable to career-services and bootcamp coaching curricula. - Funding models: not directly addressed — the talk is about interpersonal technique, not funding mechanisms. ### 🧠 Learning Styles Assessment - Reading level estimate: approximately Flesch-Kincaid grade 8–9 (conversational, narrative, low jargon density) based on sentence length and vocabulary in the reconstructed transcript. #### 👀 Visual learners - Present: none — this is an audio talk with no described slides beyond an incidental "please move to the next slide" aside. - Improve: add a simple diagram of the four mentoring levels and the mentor/sponsor/coach/teach quadrant when adapting this into written or slide form. #### 🔊 Aural learners - Present: the source is itself a spoken conference talk — strong native fit. - Improve: none needed; format already serves this learner type well. #### 🗣️ Verbal learners - Present: strong use of definitions (mentoring vs. sponsoring vs. coaching vs. teaching) and concrete personal analogies (roller derby coach as leadership model). - Improve: a short glossary card of the four core definitions would reinforce retention for readers of the notes rather than listeners of the talk. #### 🧩 Kinesthetic learners - Present: the GROW model is presented as a usable, steppable framework. - Improve: a fillable GROW-model worksheet or a "reframe your CV" exercise modeled on the two mentee case studies would give this audience something to do, not just read. #### 🧠 Logical learners - Present: the fourfold taxonomy (mentor/sponsor/coach/teach) and the four-level ladder (peer/next-level/skip-level/reverse) are both clean, comparable structures. - Improve: a decision-tree ("what does your mentee actually need?") would formalize the talk's central lesson for logical learners. #### 🧑‍🤝‍🧑 Social learners - Present: the entire talk is built from named relationships (Hannah, Pepper, two anonymized mentees). - Improve: a discussion-prompt version of the two mentee case studies for peer-group workshop use. #### 🧘‍♀️ Solitary learners - Present: the closing reflection ("what stayed with me... was being seen") invites personal reflection. - Improve: add a self-check prompt — "what kind of mentoring do I actually need right now?" — for solo readers. #### 🌿 Naturalistic learners - Present: none directly. - Improve: not a strong fit for this content; no natural sustainability/ecosystem angle to add without forcing it. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: the Reader-stored content is plain paragraph HTML with no heading structure of its own (source is a raw transcript reconstruction). - Improve: adding H2/H3 landmarks per topic segment (as done in this notes document) would materially improve screen-reader navigation of the source content itself. #### Keyboard navigation - Present: not applicable — text-only document, no interactive elements. - Improve: not applicable. #### Contrast and readability - Present: not assessable from transcript text alone (Reader's own rendering handles this). - Improve: not applicable to the underlying content. #### Text resizing and reflow - Present: plain paragraph text reflows natively. - Improve: not applicable. #### Media and captions - Present: this document is itself the recovered/cleaned transcript, functioning as a caption substitute for the original video. - Improve: the original video's auto-captions were unreliable enough to require ASR-noise cleanup (see provenance note above) — flag the source video for a proper caption pass if it's ever redistributed. #### Forms and interactions - Present: not applicable — no forms in this source. - Improve: not applicable. #### Standards reference - Primary applicable WCAG 2.2 AA gap: 1.3.1 Info and Relationships (heading structure), addressed in this notes document but not in the raw source content. ### 🌍 DEIB Assessment #### Cultural breadth - Present: single narrator, no explicit multi-region framing, though the talk implies a European tech-conference setting. - Improve: the talk would benefit from acknowledging that mentoring norms (e.g., directness, hierarchy comfort with skip-level conversations) vary significantly across cultures. #### Inclusive language - Present: gender-neutral framing throughout ("mentee," no gendered assumptions about roles); pronouns used for named individuals (Hannah, Pepper, mentees) appear respectful and specific. - Improve: none needed. #### Neurodiversity support - Present: consistent narrative structure (definition → story → lesson) repeated across sections aids predictability. - Improve: the talk moves quickly between stories without strong verbal signposting in the original delivery; explicit section markers (as reconstructed here) help. #### Representation - Present: both mentee case studies feature women in non-traditional entry paths into tech (kiosk worker, sole self-taught-adjacent developer), and the speaker credits a non-corporate role model (roller derby coach). - Improve: no other representation gaps identified within the scope of a single personal talk. #### Psychological safety - Present: Ojala explicitly frames her own advice as opinionated and optional ("take it or leave it"), and self-discloses a mentoring mistake — both build psychological safety for the audience. - Improve: none needed. ### ✅ Logical Validity #### Strong reasoning - The talk's central argument (mentoring fails when mentors assume rather than ask) is supported inductively by two contrasting personal case studies — the two mentees who *were* asked and reframed successfully versus the PhD mentee where assumption led to a mismatch. This is a coherent, if anecdotal, inductive structure. - The mentor/sponsor/coach/teach taxonomy functions as a clear conceptual (definitional) argument — location: opening third of the talk — and is used consistently as a frame for later stories, which is a logically sound structural choice. #### Fallacies - **Hasty generalization** (mild): the entire argument rests on a small number of personal anecdotes (one layoff story, two mentee stories, one mistake story) generalized into universal mentoring advice. Location: throughout. Explanation: personal experience is being used as if it were representative data. Fix: the talk could explicitly flag its evidence as anecdotal/n-of-a-few rather than presenting conclusions as generally proven. - **Appeal to personal experience** (mild, related to above): "This happened when I lost my job" and similar framings substitute lived experience for broader evidence throughout. This is a reasonable rhetorical choice for a conference talk but weakens claims if treated as generalizable research. #### Tone of voice - Warm, self-deprecating, and confessional — the speaker foregrounds a personal failure (the PhD mentee mismatch) as the talk's central lesson, and repeatedly hedges her own advice as opinion rather than fact ("take it or leave it," "I'm not telling the truth"). ### 🛡️ DARVO Analysis - Not applicable to this source — the talk contains no accusation, denial, attack, or victim-offender reversal dynamic. Ojala openly owns her mentoring mistake without deflecting blame or reframing herself as a victim; this is the opposite of a DARVO pattern. ## 🎯 Conclusion - Bottom line: mentoring is a distinct discipline from sponsoring, coaching, and teaching, and its single biggest failure mode is mentors substituting assumption for curiosity — ask what a mentee needs before defaulting to a coaching framework like GROW. - Practical next steps for readers: (1) before your next mentoring conversation, ask explicitly what mode the other person wants (advice, questions, connections, or skills); (2) look for mentors outside your own field, not just senior people in your exact job; (3) if you mentor others, treat it as practice for your own listening skills, not just a favor you're doing for someone else. ## 🧱 Refactor Appendix ### 🔄 Refactor Appendix — Mentoring That Actually Changes Careers > Density: 2–5 Literature atoms (H3), 0–3 Permanent candidates (H4). > Konik claim-header rules: present tense, declarative, ≤10 words, searchable, unique. > Atomicity: one declarative sentence per atom. #### 📚 Literature Split Pad (H3) ##### [H1] Ask what a mentee needs before coaching them > [!quote] > "This was a real mistake: I was pushing my own agenda instead of listening to what she actually needed." **Context & use**: From the PhD-mentee story, the talk's central cautionary lesson. **Why it matters**: Directly actionable checklist item for any mentor-matching program. <!-- atomicity: 1 idea ✓ --> ##### [H2] Mentoring is guidance through shared experience, not questions > [!quote] > "in mentoring I am allowed to tell about my own experience and give direct recommendations — that is often the most valuable part" **Context & use**: Core definitional distinction from coaching. **Why it matters**: Clarifies role boundaries for anyone designing a mentorship program. <!-- atomicity: 1 idea ✓ --> ##### [H3] Skip-level mentoring is the most career-impactful move > [!quote] > "if you want to get promoted this is actually the most impactful and powerful move — you understand the decisions being made and how your work fits into the bigger picture" **Context & use**: From the levels-of-mentoring section. **Why it matters**: Concrete, actionable career advice. <!-- atomicity: 1 idea ✓ --> #### 🔖 Atomic Split Pad (H4) ##### [P1] Reframing existing experience beats acquiring new skills **Claim**: A mentee blocked from job opportunities often needs help narrating existing experience, not new credentials. **Evidence pointer**: [[#H1]], both mentee case studies (kiosk worker, sole developer). **Scope & conditions**: Holds when the mentee already has relevant transferable experience that's poorly framed on paper; breaks when there's a genuine skills gap. <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Cross-reference with GROW model literature (Whitmore) for a fuller coaching-vs-mentoring comparison — #xref - [F2] Consider building a "which kind of help do you need" intake question into any Community/Training mentor-matching form — #articleseed <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/Mentoring That Actually Changes Careers.md|Mentoring That Actually Changes Careers by Lenni Ojala]] ## Highlights - By definition mentoring is individual guiding growth of another, and when mentoring we are allowed to tell about our lived experience — that's the core of mentoring. Mentoring is not sponsoring: sponsors actively open doors, offer a job promotion, use influence to move someone's career forward — that is powerful and I encourage everyone in that position to use that power to help others. When I mentor I use my network for the mentee's benefit and give advice, but usually mentoring is also not coaching: in coaching the intention is to provoke new thinking through questions, not to give advice; in mentoring I am allowed to tell about my own experience and give direct recommendations — that is often the most valuable part. Mentoring is also not teaching new tools, like AI tools, more effectively at work — the focus is not skills transfer, we are talking about wider approaches and what the work actually feels like. ([View Highlight](https://read.readwise.io/read/01m0fm7pjx480yj3ry2zh6912h)) - Note: Core definitional distinction: mentoring vs. sponsoring vs. coaching vs. teaching. - Tags: atom/literature/h2 - Different kinds of mentoring: a single meeting that may stay in touch for occasional questions. A program with a plan — you meet five times, set the goal and then work through the plan together. Peer mentoring: talking at someone at your level — for me that is a fellow engineering manager or a senior engineering manager. This year I have been exactly in this kind of relationship, talking about how to lead the transition to continuous delivery in my own team. Next-level career mentoring: talking with someone one level above you — not your own manager, preferably someone who lives in a similar reality. They help you understand what it actually feels like to be in that role, and how to work with your own manager more effectively. Skip-level mentoring: talking with someone two levels up. I have been told that if you want to get promoted this is actually the most impactful and powerful move — you understand the decisions being made and how your work fits into the bigger picture. Reverse mentoring twists the dynamic: someone less experienced mentors you. If you are a senior leader, getting mentored by someone who actually builds the software can be eye-opening. It works best outside your own company, where power dynamics don't get in the way. ([View Highlight](https://read.readwise.io/read/01m0fm7tb6ekc3s8brnjj2ebbc)) - Note: The four levels of mentoring: peer, next-level, skip-level, reverse. - Tags: atom/literature/h3 - What can go wrong in mentoring? Ask and listen, don't assume. My biggest lesson as a mentor was when I was mentoring someone in a workplace program. She had a PhD in fire signal processing and had been working as a scientific researcher for about 10 years after her PhD. She asked me how does this corporate thing work? I got excited, I pulled out the GROW model and started asking coaching questions and guiding her toward goals and options. But she didn't need that — she was literally asking how does a workplace function, what are the social rules here. This was a real mistake: I was pushing my own agenda instead of listening to what she actually needed. The essence of mentoring is being there for the other person. ([View Highlight](https://read.readwise.io/read/01m0fm779rqx3285vmg8gtf4t4)) - Note: The talk's central cautionary lesson — ask what a mentee needs before assuming. - Tags: atom/literature/h1 - A quote from Hannah, my mentor, a senior leader who has built several workplace mentoring programs and also programs for women who cycle and want to learn to repair their bikes: mentoring each other is essential in this world. We all need to feel like we have someone on our side who will always cheer us on and will never let hard questions go unanswered. Mentors can help us push ourselves and open doors in ways we never imagined possible. This reciprocal relationship makes both people better, and I hope that everyone reaches out to a mentor they feel they can learn from. ([View Highlight](https://read.readwise.io/read/01m0fm7xywrcn63edka0yxxrqn)) - Note: Hannah's reciprocal-relationship framing of mentoring's core value. - Tags: atom/zettel/z1