Greetings, Master adventurer. Every legend you admire was shaped by someone who took the time to teach them. Now the torch passes to you. In this quest, Mentorship Programs , you learn the quiet, compounding art of making other engineers better - not by doing their work, but by growing their judgment, opening their doors, and telling them the truth kindly.
Whether you mentor one junior over coffee or design a guild-wide program, this adventure gives you the frameworks to do it deliberately instead of by accident.
📖 The Legend Behind This Quest
In the old guilds, a master smith’s true legacy was never a single famous blade. It was the dozen apprentices who left their forge and lit forges of their own across the realm. The master’s reach multiplied with every student who surpassed them. The smiths remembered for centuries were the great teachers, not merely the great makers.
Mentorship is that multiplier. A line of code helps one product; a well-mentored engineer ships thousands of good decisions across a whole career. This quest teaches you to invest in people so their growth outlives any single project.
🎯 Quest Objectives
By the time you complete this epic journey, you will have mastered:
Primary Objectives (Required for Quest Completion)
Secondary Objectives (Bonus Achievements)
Mastery Indicators
You’ll know you’ve truly mastered this quest when you can:
🗺️ Quest Prerequisites
📋 Knowledge Requirements
🛠️ System Requirements
🧠 Skill Level Indicators
This 🔴 Hard quest expects:
The conversations are universal; the artifacts (growth plans, feedback logs) need a home. Pick where yours will live.
🍎 macOS Kingdom Path
Click to expand macOS instructions
```bash
# A private, versioned mentoring journal protects continuity
mkdir -p ~/mentoring/{growth-plans,feedback,one-on-ones}
cd ~/mentoring && git init
echo "# Growth Plan: " > growth-plans/template.md
```
</details>
### 🪟 Windows Empire Path
Click to expand Windows instructions
```powershell
mkdir $HOME\mentoring\growth-plans, $HOME\mentoring\feedback, $HOME\mentoring\one-on-ones
Set-Location $HOME\mentoring
git init
"# Growth Plan: " | Out-File growth-plans\template.md
```
</details>
### 🐧 Linux Territory Path
Click to expand Linux instructions
```bash
mkdir -p ~/mentoring/{growth-plans,feedback,one-on-ones}
cd ~/mentoring && git init
echo "# Growth Plan: " > growth-plans/template.md
```
</details>
### ☁️ Cloud Realms Path
Click to expand Cloud/Container instructions
```bash
# A shared but access-controlled doc keeps the plan visible to mentor and mentee
# Use your team wiki; keep raw feedback notes private to protect candor.
echo "Store growth plans in the shared wiki; keep feedback drafts private."
```
## 🧙♂️ Chapter 1: Mentoring, Coaching, and Sponsoring - Three Different Spells
*People use "mentor" for three different acts. Naming them lets you choose the right one. The biggest career accelerant - sponsorship - is the one most often skipped.*
### ⚔️ Skills You'll Forge in This Chapter
- Distinguishing mentoring, coaching, and sponsoring
- Knowing when to give answers vs ask questions
- Spending your own capital to advance someone
### 🏗️ Three Modes Compared
| Mode | You provide | Best when | Example |
| --- | --- | --- | --- |
| **Mentoring** | Your experience and answers | They lack context you have | "Here's how on-call usually goes; watch for X." |
| **Coaching** | Questions that unlock their thinking | They have the answer but can't see it | "What would have to be true for option B to work?" |
| **Sponsoring** | Your credibility, in rooms they're not in | They're ready but lack access | Naming them for the hard project in the staffing meeting |
```text
The sponsorship test — ask yourself once a quarter:
"Whose name did I say out loud, in a room they weren't in,
to put them forward for an opportunity?"
If the answer is "no one," you are mentoring but not sponsoring.
Mentoring is advice. Sponsorship is action that costs YOU something.
```
Mentoring is generous but cheap. Sponsorship is the rarer, costlier act: you put your own reputation on the line to advance someone. It is how careers actually accelerate.
### 🔍 Knowledge Check: Three Modes
- [ ] Give an example of when coaching beats mentoring
- [ ] Who have you sponsored - actually advocated for in a room they weren't in?
- [ ] Why does sponsorship cost the sponsor something?
### ⚡ Quick Wins and Checkpoints
- [ ] **Named the mode**: You identified which mode a recent conversation needed
- [ ] **Found a sponsorship target**: You named one person you could advocate for this quarter
## 🧙♂️ Chapter 2: Feedback That Lands - The SBI Model
*Most feedback fails because it is vague ("be more proactive"), late, or framed as a character flaw. The **Situation-Behavior-Impact** model fixes all three: it is specific, timely, and about actions, not identity.*
### ⚔️ Skills You'll Forge in This Chapter
- Structuring feedback with SBI
- Separating observable behavior from your interpretation
- Delivering hard feedback so it is heard, not deflected
### 🏗️ The SBI Template
```text
SITUATION — When and where, concretely:
"In yesterday's design review, when we hit the database section..."
BEHAVIOR — What you observed, not what you assume:
"...you cut off Priya twice before she finished her point..."
IMPACT — The effect it had:
"...and she went quiet for the rest of the meeting, so we lost her input
on the schema, which is her area of deepest expertise."
```
Then stop and listen. SBI describes; it does not prescribe. Let them respond before jumping to "so next time do X." For praise, use the exact same structure - specific praise ("In the incident, your calm timeline-keeping kept us focused") is far more motivating than "great job."
Pair SBI with the **Radical Candor** stance: *care personally* and *challenge directly* at the same time. Challenging without caring is obnoxious aggression; caring without challenging is ruinous empathy - the kindly silence that lets someone fail.
### 🔍 Knowledge Check: Feedback
- [ ] Rewrite "you need to communicate better" as an SBI statement
- [ ] What is the difference between behavior and interpretation?
- [ ] Why is "ruinous empathy" a failure of care, not an excess of it?
## 🧙♂️ Chapter 3: Growth Plans and One-on-Ones - The Long Game
*A growth plan turns "get better" into a route. A one-on-one is the recurring checkpoint where you walk it together. Neither works as a one-off; the magic is in the cadence.*
### ⚔️ Skills You'll Forge in This Chapter
- Co-writing a growth plan tied to a real next level
- Running one-on-ones the mentee owns
- Tracking growth without micromanaging it
### 🏗️ The Growth Plan Template
```markdown
# Growth Plan: (review monthly)
## Current level and target
From: <current level/role> -> To: , target ~
## The 2-3 gaps to close (from the leveling rubric)
1. <Gap, e.g. "leads design for medium-sized features end to end">
- Evidence we'll look for:
- Stretch opportunity:
2. <Gap #2>
## Strengths to lean into (don't only fix weaknesses)
- -> how to make it more visible/leveraged
## Support I (mentor) will provide
- <Specific commitment, e.g. "I'll get you on the X review">
## Owned by the mentee
- <What they will drive, so the plan isn't done TO them>
```
Run one-on-ones with this discipline: **it is their meeting, not your status update.** A simple agenda:
```text
1. Their topics first (always) — wins, blockers, frustrations
2. Growth-plan check — one small step since last time?
3. Feedback both directions — you give SBI; you ASK for SBI on yourself
4. One thing you'll each do before next time
```
Skipping a one-on-one quietly tells someone they don't matter. Protect the slot like production.
### 🔍 Knowledge Check: Growth and One-on-Ones
- [ ] What makes a growth plan "owned by the mentee" rather than imposed?
- [ ] Why should the mentee set the one-on-one agenda?
- [ ] How do you track growth without micromanaging?
## 🎮 Mastery Challenges
### 🟢 Novice Challenge: Practice SBI
**Objective**: Write three SBI statements - two constructive, one of praise - about real situations.
**Requirements**:
- [ ] Each names a concrete Situation, observable Behavior, and Impact
- [ ] No character judgments ("lazy", "brilliant") - only actions and effects
- [ ] Deliver at least one out loud to a real person
**Validation**: The recipient understands exactly what to repeat or change.
### 🟡 Intermediate Challenge: Build a Growth Plan
**Objective**: Co-author a growth plan with one mentee using the template.
**Requirements**:
- [ ] 2-3 gaps tied to a real leveling rubric or next role
- [ ] A stretch opportunity for each gap
- [ ] A section the mentee owns and drives
**Validation**: The mentee can describe their own plan back without reading it.
### 🔴 Advanced Challenge: Sponsor Someone
**Objective**: Advocate for a mentee in a room they are not in.
**Requirements**:
- [ ] Name them for a real opportunity (a project, a talk, a promotion case)
- [ ] Make a specific, evidence-backed case to the decision-makers
- [ ] Accept that your credibility is on the line
**Validation**: They get an opportunity they would not have gotten without you.
## 🏆 Quest Rewards & Achievements
**🎖️ Badges Earned**:
- 🏆 **Loremaster** - You transferred hard-won knowledge to another
- 🛡️ **Patron of the Guild** - You sponsored someone into a room they couldn't enter alone
**🛠️ Skills Unlocked**:
- **Structured Feedback (SBI)** - Specific, kind, actionable
- **Growth-Plan Design** - Turn "get better" into a route
**🔓 Unlocked Quests**:
- Building Technical Communities - Scale mentorship beyond one team
- Career Advancement - Help others (and yourself) level up deliberately
**📊 Progression Points**: +90 XP
## 🗺️ Next Steps in Your Journey
**Continue the Main Story**:
- 🎯 [Building Technical Communities](/quests/1111/building-technical-communities/) - Grow mentorship into a movement
**Explore Side Adventures**:
- ⚔️ [Career Advancement](/quests/1111/career-advancement/) - Plan the climb deliberately
- ⚔️ [Technical Leadership](/quests/1111/technical-leadership/) - Revisit the leadership core
### Character Class Recommendations
**💻 Software Developer**: Continue to [Career Advancement](/quests/1111/career-advancement/)
**🏗️ System Engineer**: Explore [Building Technical Communities](/quests/1111/building-technical-communities/)
**🛡️ Security Specialist**: Advance to [Technical Leadership](/quests/1111/technical-leadership/)
## 📚 Resources
### Official Documentation
- [Google re:Work - Manager guides](https://rework.withgoogle.com/guides/) - Evidence-based people practices
- [GitLab one-on-one handbook](https://handbook.gitlab.com/handbook/leadership/1-1/) - A public, detailed playbook
- [Center for Creative Leadership - SBI model](https://www.ccl.org/articles/leading-effectively-articles/closing-the-gap-between-intent-and-impact/) - The origin of Situation-Behavior-Impact
### Community Resources
- [Lara Hogan - Sponsorship vs mentorship](https://larahogan.me/blog/what-sponsorship-looks-like/) - The definitive short read
- [Plato - engineering mentorship community](https://www.platohq.com/) - Mentor matching for engineers
- [Rands - The Update, The Vent, and The Disaster](https://randsinrepose.com/archives/the-update-the-vent-and-the-disaster/) - One-on-one archetypes
### Learning Materials
- [Radical Candor framework](https://www.radicalcandor.com/the-book/) - Kim Scott on caring and challenging
- [Camille Fournier - The Manager's Path](https://www.oreilly.com/library/view/the-managers-path/9781491973882/) - Mentoring chapters
## 🤝 Quest Completion Checklist
- [ ] ✅ Completed all primary objectives
- [ ] ✅ Delivered at least one real SBI feedback statement
- [ ] ✅ Co-authored a growth plan with a mentee
- [ ] ✅ Identified or acted on a sponsorship opportunity
- [ ] ✅ Explored the resource library
- [ ] ✅ Identified your next quest in the journey
## 🕸️ Knowledge Graph
*Structured wiki-links connect this quest to the IT-Journey knowledge graph. Open the [Obsidian Graph View](/notes/obsidian/graph/) to explore connections.*
**Level hub:** [[Level 1111: Leadership & Innovation]]
**Overworld:** [[🏰 Overworld - Master Quest Map]]
**Prerequisites:** [[Technical Leadership: Leading Without Authority and Setting Tech Vision]]
**Unlocks:** [[Building Technical Communities: Growing Developer Ecosystems]] · [[Career Advancement Strategies: Growing from Engineer to Leader]]
**Obsidian docs:** [[Obsidian Knowledge Graph and Wiki Links]]
🎁 Rewards
⚡
90 XP
Badges
🏆 Loremaster - Transferred hard-won knowledge to another 🛡️ Patron of the Guild - Sponsored someone into a room they could not enter alone
Skills unlocked
🛠️ Structured Feedback (SBI) 🧠 Growth-Plan Design
Features unlocked
Continued progress through the Level 1111 Leadership & Innovation quest line
🕸️ Quest Network
Loading quest graph…
Click a node to open the quest · ⌘/Ctrl-click for a new tab · drag to
reposition · scroll to zoom.