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 > ## 🧭 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. > <p>Hello everyone. I'm Lenni Ojala and everything I've been learning in my profession I've been learning from other people and mentoring has been a big part of it. Today I will tell you what mentoring is, how to find mentors and how to be one. And as Mary said in the intro, I'm also celebrating something. I graduated from university 20 years ago. So this day marks my career. 20 years building software.</p> <p>My degree was a mix of telecommunications engineering, project management, marketing, creativity and even some gender studies. I have always been curious of many things. One of my most memories from that time is from a leadership course. Our professor told us how he led mobile phone innovation and manufacturing: focus on important things before urgent ones, because if you find yourself doing only fire fighting something needs to change earlier in the process.</p> <p>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.</p> <p>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.</p> <p>Let me tell you about the most impactful one-time mentoring I ever received. This happened when I lost my job — a team I really liked, at a conference. I approached her and asked, would you be open to mentoring me, once I'd been laid off. When we met, she gave me two valuable pieces of advice. First, she had seen me at the speakers' dinner before the conference and made an observation that I looked uncertain — she assumed I was probably new, but on the way back to the hotel in the tram, when she heard me talking, she realized: this person has been around the block, they know their stuff. She told me I belong in those discussions and should carry myself with more confidence. The second advice was that she wanted to learn about me, my situation, and my way of leading. Two weeks later I signed a contract to lead a team of four engineers with a very familiar stack.</p> <p>Role models as mentors: pay attention to people around you, observe how they work, how they lead, how they make decisions, and how they are gloriously imperfect humans. My roller derby coach, Pepper, is my role model. She is individually incredibly talented, but what I admire is what she gives to the players around her, to grow — because it's a team, not a single star. Every training session with Pepper is like a stand-up comedy show. And then there's her focus — when we are training a drill, she is completely present, nothing else exists outside. After training together for a year or so, I approached her and asked: could you talk about leadership with me? I found out she actually leads projects and people outside of roller derby, in a completely different field — a nice perspective outside my own tech bubble. From Pepper I've learned that I can be my full self, my sometimes freaky and often ambitious self — the focus and the fun, they live together, they are not opposites. You can find mentors everywhere. Trust your intuition.</p> <p>How do I mentor? I always start with the disclaimer to use only the advice that feels right for you — I am looking at your situation through my lens, opinionated, please take what fits your life, I'm not telling the truth, take it or leave it. Last year a recent graduate approached me. She was working in a kiosk — not just selling newspapers, she was processing passport deliveries, selling event tickets, handling sports lottery, and doing parcel orders across multiple systems, some of which are maintained by my team. She wanted to break into tech but couldn't get interviews in this job market. I started asking questions and found out she was also onboarding new colleagues. We rewrote her CV completely to show what she actually did, and I was very direct about which unpaid coding projects she should do and which not, to save her energy for what she needed elsewhere. Within months she landed her first job in tech — a customer support role. The best developers I know come from support backgrounds, because they are the people who understand what the customer needs.</p> <p>Another time I was mentoring a developer who wanted to change companies but couldn't get interviews because her JavaScript stack was seen as old-fashioned. When I asked questions, I found out she was the sole developer of a full-stack application used by thousands of students, maintaining it in production alone, and had just shipped a major usability improvement to meet usability standards. She thought she needed to study something new — I disagreed gently: you do not need to study, you need to frame what you already have. She landed a new job and learned the new technologies on the way.</p> <p>When mentoring, if the mentee doesn't have a specific question, I often start with the GROW model, widely used in coaching: I ask about their goals and dreams, and about their reality — what are you doing, with whom do you work, what do you like to do more, what do you like less. Then we generate options together, and I always ask them to add one completely over-the-moon option, because it lets us be more creative. Then we pick one option and commit to one small first step. Even when I use this structure, I label the moment when I'm switching to mentoring — I say, now I'm going to tell you what I actually think, take it or leave it.</p> <p>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.</p> <p>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.</p> <p>What stayed with me the most, collecting mentoring stories from people around me, was this: being seen. People do get valuable career advice from mentoring, but a big part of it is simply feeling seen, cherished, and valued. And what do I get from mentoring? One bonus I didn't expect: mentoring is my communication laboratory. The skill I struggle with most is listening, and in mentoring I get to train that listening muscle, because there's no power difference in the room — I'm not the boss, I'm not writing the performance review or deciding salary, I can just listen. This makes me a better listener, and it transfers to my team too.</p> <p>My advice for anyone who mentors: be curious, listen actively, every mentee has a unique situation. Tell about your lived experience — tell shamelessly about your lived experience.</p>, Mentoring That Actually Changes Careers, Lenni Ojala, 01m0fkbx3x1kt01jr8ssm06zyf.