Mentorship Guide

Mentorship Guide

When to Use

Use this skill when the user is a mentor or mentee who wants to build structured, outcome-driven mentorship sessions rather than unstructured conversations.

Use when:

• A mentor asks how to structure their upcoming session with a mentee, including agenda design, time allocation, and focus areas
• A mentee wants a preparation framework before meeting with their mentor so they arrive with focused questions and progress documentation
• A mentorship pair wants to design a multi-session arc covering a defined period (6 weeks, 3 months, or a full program cycle)
• A mentor wants reflection question sets tailored to a specific career stage -- for example, a new manager navigating their first 90 days, or a senior individual contributor considering a pivot to leadership
• A program coordinator needs a repeatable session template they can give to multiple mentor-mentee pairs in a formal mentorship program
• A mentee wants a goal-tracking framework that ties session-level actions to longer-horizon career objectives and shows measurable progress over time
• A mentor asks how to handle a specific relational dynamic -- such as a mentee who is disengaged, a session that went off-track, or a relationship that has reached its natural conclusion

Do NOT use when:

• The user wants a personalized learning curriculum or skill-building roadmap -- use learning-path instead
• The user is asking what skills they are missing or where their gaps lie -- use skill-gap-analysis before using this skill
• The user wants executive coaching, therapy, performance management, or 360-degree feedback facilitation -- these are coaching or HR disciplines, not mentorship facilitation
• The user is a teacher or trainer creating educational materials for a classroom -- use the teaching subcategory skills
• The user is asking for career advice ("What should I do next in my career?") rather than session structure -- redirect to career-planning skills
• The user wants a general guide to "being a good mentor" philosophically -- this skill produces operational session artifacts, not essays on the value of mentorship

Process

Step 1: Establish the Mentorship Context

Before producing any artifact, gather the information that determines every structural decision.

• Role clarity: Is the user the mentor, the mentee, or a program coordinator? The session guide is structured differently depending on who owns the preparation workload.
• Relationship phase: Is this the first session (Foundation Phase), a mid-cycle session (Development Phase), an advanced session (Mastery Phase), or a closing session (Transition Phase)? Each phase has a different agenda rhythm.
• Session number and cadence: Ask which session number this is and how often the pair meets. A pair meeting weekly needs tighter agendas than a pair meeting monthly.
• Mentee's professional context: Job function, seniority level, industry, and the specific challenge or aspiration driving the mentorship. A software engineer targeting a Staff Engineer promotion has completely different content needs than a mid-career marketing professional pivoting into product management.
• Active goals: Ask if there are already-established goals from a previous session or program intake form. If not, the first session must include a goal-setting block.
• Session length: Standard is 60 minutes. Some pairs use 45 minutes (fast cadence, weekly) or 90 minutes (slower cadence, monthly). Time blocks in the agenda must match.

If the user cannot answer all of these, use the minimum viable defaults: assume 60-minute sessions, biweekly cadence, Development Phase, no prior goals established.

Step 2: Determine the Session's Primary Purpose

Each session should have exactly one primary purpose. Do not let sessions try to accomplish everything.

• Check-in and goal-setting sessions (Foundation Phase, Sessions 1-2): The primary work is trust-building and goal articulation. Use the GROW model (Goal, Reality, Options, Will) to structure the goal-setting conversation.
• Skill-building sessions: A specific competency is the focal point. The mentor shares frameworks, demonstrates thinking, or assigns deliberate practice. Assign at least one concrete task the mentee will complete before the next session.
• Challenge-processing sessions: The mentee brings a real, current problem. The mentor uses Socratic questioning -- asking questions rather than giving answers -- to help the mentee arrive at their own solution. The mentor should speak no more than 30% of the time in this session type.
• Feedback and accountability sessions: Review progress against goals from prior sessions. Use the SBI (Situation-Behavior-Impact) model for delivering feedback on observed or reported behavior.
• Network and opportunity sessions: The mentor helps the mentee map their professional network, identify sponsors, or prepare for specific opportunities (a promotion conversation, a conference presentation, a job application).
• Transition and closure sessions (Final 1-2 sessions): Structured reflection on growth over the full arc, explicit celebration of achievements, and creation of an independence plan the mentee will execute without the mentor.

Assign the session type before building the agenda. A session with no declared purpose becomes a wandering conversation.

Step 3: Build the Pre-Session Preparation Section

The quality of a mentorship session is largely determined before the session begins.

• Mentee preparation workload (required before every session): Progress update against the previous session's action items (specific, not general -- "I completed the first draft of the promotion case document" not "I worked on my goals"), one to three focused questions they want answered, and a declared desired outcome for this session.
• Mentor preparation workload: Review notes from the last session, specifically the action items they assigned. Prepare one to three observations or frameworks relevant to the mentee's current challenge. Identify one experience from their own career that is directly analogous to what the mentee is navigating.
• Shared document protocol: Best practice is a shared running document (a simple collaborative doc) where both parties add their pre-session notes 24-48 hours before the meeting. This prevents the first 15 minutes from being wasted on recall.
• Flag if this is Session 1: The pre-session prep for Session 1 is different -- the mentee should complete a brief self-assessment covering their top three professional goals, one sentence on the gap between where they are and where they want to be, and any specific skills or knowledge they hope the mentor can share.

Step 4: Design the Timed Agenda

The agenda is the operational core of the session guide. Every time block must have a clear owner and a clear output.

• 60-minute standard agenda:

  • Minutes 0-5: Personal check-in (unstructured, mentor-initiated, builds psychological safety)
  • Minutes 5-15: Progress review -- mentee reports on action items from last session using the pre-session document
  • Minutes 15-45: Deep work block -- this is the session's primary purpose (see Step 2 for the appropriate structure per session type)
  • Minutes 45-52: Action item generation -- mentee articulates 1-3 specific actions they will take before the next session, with deadlines and success criteria
  • Minutes 52-57: Reflection questions (mentee answers at least two; mentor answers at least one)
  • Minutes 57-60: Closing and logistics (confirm next session date, time, and topic)

• 45-minute compressed agenda (weekly cadence):

  • Minutes 0-3: Quick check-in
  • Minutes 3-10: Progress on last session's single action item
  • Minutes 10-35: Deep work (narrower scope than 60-minute version -- choose one question, not a topic)
  • Minutes 35-42: One action item
  • Minutes 42-45: Reflection and close

• 90-minute deep-work agenda (monthly cadence):

  • Minutes 0-10: Personal check-in and rapport
  • Minutes 10-25: Progress review -- more extensive because more time has passed
  • Minutes 25-65: Deep work block -- can include two sub-topics or one extended skill-building exercise
  • Minutes 65-78: Action items (up to 4, since the gap until next session is longer)
  • Minutes 78-86: Reflection questions
  • Minutes 86-90: Close, logistics, and mentor shares one recommended resource (article, book, person to contact)

• Do not compress the reflection block. The temptation is to run over on deep work and skip reflection. This is the most common mistake in mentorship facilitation. The reflection block is where insight consolidates into behavior change.

Step 5: Write the Reflection Question Set

Reflection questions are the most leveraged component of the session guide. Generic questions produce generic insight. Specific questions unlock real behavior change.

• Four mandatory closing reflection questions for the mentee (use these in every session):

  1. What is the single most important thing I'm taking away from today's session?
  2. What will I do differently in the next week because of this conversation?
  3. What am I still uncertain about, and how will I address that uncertainty?
  4. On a scale of 1-10, how well did I use this session? What would make it a 10?

• Session-type-specific questions (add 2-3 of these based on the session's primary purpose):

  • For challenge-processing sessions: "What assumptions was I making about this situation that the conversation challenged?" and "What did I avoid saying or asking today, and why?"
  • For skill-building sessions: "What is the earliest opportunity I have to practice what I learned today, and what specifically will I try?" and "What part of this skill feels most uncomfortable, and what does that discomfort tell me?"
  • For feedback and accountability sessions: "What pattern do I see across the feedback I've received over multiple sessions?" and "What am I consistently not doing that I say I will do -- and what is the real reason?"
  • For transition sessions: "What is the version of myself that emerged from this mentorship relationship, and how is it different from who I was when we started?" and "What would I tell my mentor-from-the-beginning that I wish I had known at the start?"

• One reflection question for the mentor (asked every session): "What did I learn or notice in this session that I want to carry forward in how I mentor?" This models vulnerability and mutual learning for the mentee.

• Between-session reflection prompt: Give the mentee one written reflection prompt to complete in their journal or notes document within 48 hours of the session, while the conversation is fresh. This is distinct from action items -- it is reflective, not task-based. Example: "Describe the moment in today's session where something clicked. What made it click?"

Step 6: Build the Goal-Tracking Framework

Goal tracking in mentorship requires three levels: session-level actions, milestone goals (4-8 week horizon), and horizon goals (3-12 month career objectives). All three must be visible at every session.

• Session-level action items: 1-3 items per session, each with a specific due date (not "by next session" -- an actual date), a success criterion ("I will know I've done this when..."), and a difficulty rating (Easy / Stretch / Hard). Balance the portfolio -- not all easy, not all hard.

• Milestone goals (the middle layer): These are the objectives that the mentorship arc is designed to achieve. They should be written in outcome language, not activity language. Bad: "Work on communication skills." Good: "Deliver a 10-minute presentation to senior leadership and receive unsolicited positive feedback on clarity from at least two attendees." Each milestone goal should have: a target date, a current status (Not Started / In Progress / On Track / At Risk / Complete), and a list of 2-5 session-level actions that contribute to it.

• Horizon goals (the outermost layer): These are the career-level ambitions that motivated the mentorship relationship. They are reviewed at the start of the mentorship arc, at its midpoint, and during the transition sessions. They should not change frequently -- if they are changing every session, the mentee lacks clarity and the mentor should facilitate a values and priorities conversation, not a goal-setting exercise.

• Goal health check: At every third session, explicitly review the full goal set. Ask: Is this goal still relevant? Is the timeline realistic? Has something happened in the mentee's work life that changes the priority? Goals that remain on the tracker but no one discusses are organizational debt -- they erode trust in the system. Remove or defer them explicitly.

• Scoring progress: At each session, rate each active milestone goal from 1-5: 1 = No progress, 2 = Some effort but no visible movement, 3 = Progressing as expected, 4 = Ahead of schedule, 5 = Complete. Calculate a simple average score at the midpoint review. An average below 2.5 signals that the goals were set too ambitiously, external blockers are unaddressed, or the mentee's commitment needs a direct conversation.

Step 7: Assemble and Deliver the Full Session Guide

Combine the outputs of Steps 1-6 into the structured session document.

• Present the guide in a format the user can immediately use -- it must be printable, pasteable into a shared doc, or readable on a phone during the session itself.
• Include a "Mentor's Private Notes" section at the end that the mentor completes after the session. This section is not shared with the mentee and captures: the mentor's honest assessment of the session's effectiveness, observations about the mentee's growth edge, and any concerns or celebrations to carry into the next session.
• Flag the session number on the guide. Session 1 and session 12 of the same relationship look completely different. The session number contextualizes everything.
• If this is Session 1, append the "Relationship Charter" section (see the Edge Cases section for details).
• If this is the final session, append the "Independence Plan" and "Relationship Celebration" sections.

Step 8: Offer the Multi-Session Arc Overview

After delivering the single session guide, offer to show the full arc structure.

• A 3-month mentorship arc with biweekly sessions contains approximately 6 sessions. Provide a session-by-session focus map showing what each session is designed to accomplish in sequence.
• A 6-month arc with biweekly sessions has approximately 12 sessions. Divide it into the four phases: Foundation (Sessions 1-2), Development (Sessions 3-8), Mastery (Sessions 9-10), and Transition (Sessions 11-12).
• Always note that the arc is a guideline, not a contract. Real life will shift priorities. The arc gives the pair orientation when sessions start to drift.

Output Format

## Mentorship Session Guide

**Mentor:** [Name or role]
**Mentee:** [Name or role]
**Session Number:** [#] of [total planned sessions]
**Session Date:** [Date]
**Duration:** [45 / 60 / 90 minutes]
**Relationship Phase:** [Foundation / Development / Mastery / Transition]
**Session Type:** [Check-in & Goal-Setting / Skill-Building / Challenge-Processing /
                  Feedback & Accountability / Network & Opportunity / Closure]

---

### PRE-SESSION PREPARATION

**Mentee completes 24-48 hours before session:**

| Item | Response |
|------|----------|
| Action items from last session | [Completed / Partially / Not completed -- explain] |
| Main thing I want to get out of today | [One sentence] |
| My three questions for this session | 1. [Question] / 2. [Question] / 3. [Question] |
| Current energy and headspace (1-10) | [Rating and one sentence explanation] |

**Mentor reviews before session:**

| Item | Notes |
|------|-------|
| Last session's action items (mentee committed to) | [List from prior session] |
| Relevant experience or framework to share | [What you'll bring] |
| One open question I want to ask this session | [The question] |

---

### SESSION AGENDA

**Total Duration:** [X minutes]

| Time Block | Activity | Owner | Expected Output |
|-----------|----------|-------|-----------------|
| 0-5 min | Personal check-in | Mentor opens | Psychological safety established |
| 5-[X] min | Progress review | Mentee | Status of last session's action items |
| [X]-[Y] min | Deep work: [Session topic] | [Owner] | [Specific output] |
| [Y]-[Z] min | Action item generation | Mentee leads | 1-3 specific commitments with dates |
| [Z]-[W] min | Reflection questions | Both | [Number] reflection questions answered |
| [W]-end | Close and logistics | Mentor | Next session confirmed |

---

### DEEP WORK BLOCK: [Session Topic]

**Primary question for this session:** [One specific, open-ended question]

**Mentor's facilitation approach:** [Socratic questioning / Direct teaching / Experience-sharing / Problem-solving together]

**Key frameworks or concepts to explore:**
- [Framework 1 with brief explanation]
- [Framework 2 with brief explanation]

**Mentee skill practice or exercise (if applicable):** [Specific activity, duration, and what mentor observes]

---

### REFLECTION QUESTIONS

**Mandatory closing questions for mentee (answer at least 2 of 4):**
1. What is the single most important thing I'm taking away from today's session?
2. What will I do differently in the next week because of this conversation?
3. What am I still uncertain about, and how will I address that uncertainty?
4. On a scale of 1-10, how well did I use this session? What would make it a 10?

**Session-type-specific questions for mentee (answer at least 1):**
- [Question tailored to this session's type and topic]
- [Question tailored to this session's type and topic]

**Reflection question for mentor (answer 1):**
- What did I learn or notice in this session that I want to carry forward in how I mentor?

**Between-session reflection prompt (mentee completes within 48 hours):**
[One written prompt for the mentee's journal or notes]

---

### ACTION ITEMS

| Action | Owner | Due Date | Success Criterion | Difficulty |
|--------|-------|----------|------------------|------------|
| [Specific action] | Mentee | [Date] | [How they'll know it's done] | Easy / Stretch / Hard |
| [Specific action] | Mentee | [Date] | [How they'll know it's done] | Easy / Stretch / Hard |
| [Optional mentor action] | Mentor | [Date] | [e.g., Send intro email to contact] | -- |

---

### GOAL TRACKER

**Session-Level Actions (this session):** See Action Items table above.

**Milestone Goals (4-8 week horizon):**

| Goal | Target Date | Status | Progress (1-5) | Session Actions That Contribute |
|------|-------------|--------|----------------|---------------------------------|
| [Outcome-language goal] | [Date] | In Progress | [1-5] | [Link to action items] |
| [Outcome-language goal] | [Date] | Not Started | [1-5] | [Link to action items] |

**Horizon Goals (3-12 month career objectives):**

| Goal | Target Date | Last Reviewed | Notes |
|------|-------------|---------------|-------|
| [Career-level objective] | [Date] | [Session #] | [Any changes in priority] |

**Goal Health Score (Sessions 3, 6, 9, 12...):**
Average milestone goal progress score: [X/5]
Action required if below 2.5: [Specific conversation or adjustment]

---

### MENTOR'S PRIVATE POST-SESSION NOTES
*(Not shared with mentee)*

| Item | Notes |
|------|-------|
| How effective was this session (1-10)? | |
| What did I notice about the mentee's growth edge? | |
| What concern or celebration do I carry into the next session? | |
| Did I talk too much? (Did mentee speak 60-70% of the time?) | |
| What would I do differently next session? | |

---

### SESSION SUMMARY (optional -- share with mentee)

**What we covered:** [2-3 sentences]
**Key insight from this session:** [One sentence]
**Next session focus:** [Tentative topic]
**Next session date:** [Date]

Rules

1. Every session must have exactly one declared session type. A session without a declared type -- Skill-Building, Challenge-Processing, Feedback & Accountability, etc. -- will drift. Declare the type before building the agenda.

2. The mentor must speak no more than 40% of the time in most session types. The exception is Skill-Building sessions where the mentor is actively teaching a framework, in which case 50/50 is acceptable. In Challenge-Processing sessions, the mentor speaks no more than 30%. If the session guide you produce has the mentor owning more than half the agenda blocks, redesign it.

3. Action items must be specific, dated, and have success criteria. "Work on the presentation" is not an action item. "Complete slides 1-8 of the promotion case presentation and share with mentor via shared doc by Thursday at 5pm" is an action item. Never produce an action item without a due date and a success criterion.

4. Do not conflate goals with activities. Milestone goals must be written in outcome language -- what will be true in the world when the goal is complete -- not in activity language (things to do). "Read a book about negotiation" is an activity. "Successfully negotiate a $15,000 salary increase in my next performance review" is a goal.

5. Reflection questions must never be yes/no questions. All reflection questions in the session guide must be open-ended and introspective. "Did you find this useful?" is not a reflection question. "What specifically shifted in how you think about this after today's conversation?" is a reflection question.

6. Do not skip the Mentor's Private Post-Session Notes section. This is not optional decoration -- it is the mechanism by which mentors improve their facilitation over time. Include it in every guide even if the user (the mentor) says they probably won't fill it out.

7. The goal-tracking framework must have all three levels. Session-level action items alone are not a goal-tracking framework. The tracker must show the three layers: session actions, milestone goals, and horizon goals. Omitting the horizon goals disconnects the sessions from the reason the mentorship relationship exists.

8. Never produce a session guide without asking the session number. Session 1 and Session 7 of the same mentorship relationship are completely different documents. A guide produced without knowing the session number will be structurally wrong -- it may include goal-setting work that was already done, or skip foundation-building that is still needed.

9. The between-session reflection prompt must be distinct from action items. Action items are tasks. The between-session prompt is reflective writing -- it has no deliverable, no deadline, and no success criterion. Confusing the two undermines the psychological function of each.

10. Do not recommend the mentee bring more than three questions to a session. More than three questions signals a lack of prioritization, which is itself a skill the mentor should help develop. If the user suggests the mentee should prepare five or six questions, trim it to three and explain why focus matters more than volume.

Edge Cases

The First Session Has No Prior Goals or Action Items

Session 1 requires a Relationship Charter block that does not appear in subsequent sessions. Include the following additional section:

• Relationship Charter (Session 1 only):
  • Logistics agreement: meeting cadence, platform, expected preparation time, communication norms between sessions (e.g., "We will not text each other except to reschedule -- all substantive questions go in our shared doc")
  • Confidentiality agreement: what stays in the room, what the mentor may share with others (e.g., if the mentor is also the mentee's skip-level manager, be explicit about what is protected)
  • Mentee's stated top three goals for the relationship (use GROW model -- articulate the Goal, describe current Reality, brainstorm Options, state Will/commitment)
  • Mentor's stated offering: what experiences and expertise the mentor can genuinely share, and honest acknowledgment of areas outside their expertise
  • Working style preferences: How does the mentee like to receive feedback? Direct and blunt, or framed and gentle? What does "a good session" feel like to each person?
  • Success definition: "We will know this mentorship relationship was a success when..." -- get a specific answer from both parties

Replace the Progress Review block in the agenda with a Goals Articulation block (20 minutes using GROW) for Session 1.

The Mentee Is Disengaged or Not Completing Action Items

When a mentee consistently fails to complete action items (two or more consecutive sessions), do not add more action items. Instead, design a session guide with a "Commitment Conversation" block in the deep work slot:

• The mentor opens with a direct, non-judgmental observation: "I've noticed that the action items from our last two sessions haven't been completed. I want to understand what's getting in the way, because I want this to be genuinely useful to you."
• Use the five-whys technique to understand the root cause -- the real barrier is rarely time (the stated reason) and is usually one of: the goal no longer feels relevant, the action item was too hard and the mentee felt embarrassed to say so, external circumstances have changed, or the mentee is questioning the value of the relationship itself.
• Depending on the root cause, either renegotiate the goals, reduce the difficulty rating of action items for the next two sessions, or have an honest conversation about whether the mentorship relationship should continue or be restructured.
• Do NOT design the session to avoid this conversation by filling time with other topics. The disengagement must be named directly in the session guide.

The Mentor Is More Junior or Peer-Level (Reverse Mentorship or Peer Mentorship)

In reverse mentorship (where a younger person mentors a more experienced person, often on technology or cultural topics) or peer mentorship (same seniority, different expertise), the standard power dynamic assumptions in the default guide do not apply. Modify the guide as follows:

• Remove language about the mentor "assigning" action items -- both parties generate action items collaboratively
• Add a mutual learning section to the reflection questions: "What did the mentor learn from the mentee in this session?" and "What did the mentee learn from the mentor?"
• In the deep work block, use co-exploration framing rather than teaching framing -- the mentor does not explain, they facilitate a joint investigation
• In peer mentorship, consider alternating which party "brings the problem" and which "facilitates" each session, and note this rotation explicitly in the session guide
• The Mentor's Private Post-Session Notes section remains, but its questions should be adjusted to peer framing: "How did this conversation change my own thinking?"

The Mentorship Is Approaching Its Planned End Date (Transition Phase)

The final two sessions of a formal mentorship arc require significant structural modification:

• Second-to-last session: Include a "Progress Inventory" block (25 minutes) where both parties review every milestone goal and rate its completion, then identify what the mentee needs to continue progressing without the mentor. This session should include a written "Growth Ledger" -- a co-created document listing specific skills developed, situations navigated, and moments of breakthrough during the arc.
• Final session: Replace the Deep Work block with an "Independence Planning" block. The mentee articulates three specific practices they will maintain independently (e.g., "I will continue doing monthly self-assessments using the GROW model"), three people in their network who can provide ongoing guidance in specific areas (named individuals, not categories), and one stretch goal they will pursue in the next 90 days without a mentor.
• Include an explicit "Relationship Celebration" block (10 minutes) -- not optional, not rushed. The mentor names something specific they admire about the mentee's growth. The mentee names something specific they are grateful for. This is a professional ritual that matters.
• Offer to produce an ongoing "self-mentorship" session template the mentee can use with themselves monthly after the formal relationship ends.

The Session Covers a Sensitive Topic (Mental Health, Discrimination, Ethics)

Mentors are not therapists, HR representatives, or ethics officers. When the session guide is being built around a topic that touches these areas:

• Add a clear "Scope Boundary" note at the top of the Deep Work block: "This session can explore how this situation is affecting your professional confidence and what choices you have in responding. It is outside the scope of this mentorship to provide legal advice, mental health support, or HR guidance."
• Include a specific referral prompt in the session guide: the mentor should proactively name the appropriate resource (EAP, HR, legal counsel) by name if the topic warrants it, not leave it to the mentee to figure out
• For topics involving workplace discrimination or harassment, the mentor must not promise confidentiality -- in many organizations, managers and mentors who are aware of discrimination have reporting obligations. The session guide must include a note reminding the mentor to clarify their own obligations before the conversation begins
• Adjust the reflection questions to be emotionally supportive without being therapeutic: "What would help you feel more resourced as you navigate this?" rather than "How does this make you feel?"

The User Wants a Full 6-Month Program Arc, Not a Single Session

When the user needs an arc overview (not just one session), produce a Session Map first, then the detailed guide for Session 1:

• Present the arc as a table: Session number, phase, session type, primary focus question, and key outcome
• Note explicitly that sessions 3, 6, 9, and 12 are "goal health check" sessions and will require a modified agenda structure
• The arc map is a planning tool, not a contract -- include this note prominently
• Offer to generate the full detailed session guide for any specific session in the arc on request

The Mentee Wants to Track Goals But Has No Current Mentorship Relationship

When a user asks for a goal-tracking framework as a standalone tool (not embedded in a live mentorship relationship), produce a self-mentorship tracker:

• Replace "mentor" and "mentee" with "self" throughout
• Add a monthly "self-check-in" session structure (30 minutes, self-guided) using all three goal levels
• Include a "personal board of advisors" mapping section -- a list of 4-6 people in the user's network who can provide informal guidance in specific areas, even without a formal mentor relationship
• Note that this is a reduced-effectiveness version of the full mentorship guide and encourage the user to seek a formal mentor if possible

Example

Input: "I'm a senior software engineer who just started mentoring a mid-level engineer on my team. She wants to move into a Staff Engineer role in the next 18 months. This is our second session -- we did a general goals conversation last time. She said her main goals were: getting more visible on cross-team projects, improving her technical design skills, and building her executive communication. I have 60 minutes. Help me build the session guide."

Output:

## Mentorship Session Guide

**Mentor:** Senior Software Engineer (Staff+ level)
**Mentee:** Mid-Level Software Engineer
**Session Number:** 2 of approximately 12 (estimated 6-month arc, biweekly)
**Session Date:** [Date]
**Duration:** 60 minutes
**Relationship Phase:** Foundation (transitioning to Development)
**Session Type:** Skill-Building (primary) + Feedback & Accountability (secondary -- reviewing
                  Session 1 action items)

---

### PRE-SESSION PREPARATION

**Mentee completes 24-48 hours before session:**

| Item | Response |
|------|----------|
| Action items from Session 1 | [Did I complete what I committed to? Be specific] |
| Main thing I want to get out of today | [One sentence -- what would make this session feel worth it?] |
| My top 3 questions for this session | 1. [Question] 2. [Question] 3. [Question] |
| Current energy and headspace (1-10) | [Rating + one sentence: what's on my mind going into this?] |

*Suggested mentee questions if she has not yet generated her own:*
- "I want to understand what separates a mid-level design doc from a Staff-level design doc -- can you show me the difference?"
- "How do I get pulled into cross-team projects when I'm not being invited yet?"
- "What does executive communication actually mean in practice at our company?"

**Mentor reviews before session:**

| Item | Notes |
|------|-------|
| Session 1 action items mentee committed to | [List from Session 1 -- if no formal action items were set, note this and address it in the session] |
| Relevant experience to share | Prepare a real example of a time you wrote or reviewed a design doc that got Staff-level attention -- bring the doc if shareable, or prepare to describe it specifically |
| One open question to ask | "What has happened in your day-to-day work in the past two weeks that's connected to any of your three goals?" |

---

### SESSION AGENDA

**Total Duration:** 60 minutes

| Time Block | Activity | Owner | Expected Output |
|-----------|----------|-------|-----------------|
| 0-5 min | Personal check-in | Mentor opens | Psychological safety; gauge mentee's current state |
| 5-15 min | Session 1 action item review | Mentee | Honest status report; uncover early blockers |
| 15-43 min | Deep work: Technical design doc quality at Staff level | Both (mentor leads first 10 min, then mentee drives) | Mentee understands the 3 specific dimensions that differentiate Staff-level design thinking |
| 43-50 min | Action item generation | Mentee proposes, mentor refines | 2-3 specific commitments with dates and success criteria |
| 50-56 min | Reflection questions | Both | At least 2 mentee reflections + 1 mentor reflection answered aloud |
| 56-60 min | Close and logistics | Mentor | Next session confirmed; tentative topic agreed |

---

### DEEP WORK BLOCK: What Makes a Design Doc Staff-Level?

**Primary question for this session:**
"When you look at a design doc from a Staff or Principal Engineer, what specifically is different about how they frame the problem, handle trade-offs, and anticipate audience -- and how do I develop those specific skills?"

**Mentor's facilitation approach:**
Start with direct teaching (10 minutes: share a real or anonymized example of a strong design doc you have written or reviewed). Then shift to Socratic questioning: show a design doc the mentee has written or is familiar with, and ask her to identify gaps using the framework you just introduced. Mentor observes and asks questions rather than corrects directly.

**The three dimensions that distinguish Staff-level design thinking:**

1. **Problem framing over solution description:** Mid-level engineers describe what they are going to build. Staff engineers articulate why this is the right problem to solve, what the cost of not solving it is, and what alternative problem definitions were considered and rejected. Ask the mentee: "In your last design doc, how much space did you spend explaining why this was the problem worth solving?"

2. **Explicit trade-off reasoning:** Mid-level engineers pick an approach and explain it. Staff engineers present 2-3 serious alternatives with honest pros/cons (including the pros of the approaches they are not recommending), and they make their reasoning about organizational constraints visible -- not just technical constraints. Ask: "What would a skeptical senior engineer think when reading your proposed approach? Have you anticipated and addressed that objection?"

3. **Audience-calibrated communication:** A Staff-level design doc can be read at two speeds. An executive or cross-functional partner can read the first two sections (problem statement and recommendation) and understand the decision in under 5 minutes. A technical reviewer can go deep into the appendix. Ask: "Who needs to approve or be aware of this design decision? Have you written for them, or have you written for yourself?"

**Mentee skill practice exercise (15 minutes):**
Bring or describe a current or recent design doc (or a project where one was needed). Mentor asks the mentee to rate her own doc on each of the three dimensions above (1-5). Mentor observes without immediately correcting -- then asks "What would you change in section X if you were writing for a VP who has 4 minutes to read it?" Mentor offers one specific observation per dimension, not a comprehensive critique.

---

### REFLECTION QUESTIONS

**Mandatory closing questions for mentee (answer at least 2):**
1. What is the single most important thing I'm taking away from today's session?
2. What will I do differently in the next week because of this conversation?
3. What am I still uncertain about, and how will I address that uncertainty?
4. On a scale of 1-10, how well did I use this session? What would make it a 10?

**Skill-building session-specific questions for mentee (answer at least 1):**
- "What is the earliest opportunity I have to apply the three-dimension framework -- is there a design doc I am writing now, or one coming up in the next two weeks?"
- "Which of the three dimensions (problem framing, trade-off reasoning, audience calibration) feels most foreign to me, and why do I think that is?"

**Reflection question for mentor:**
- "Did I give her space to figure things out herself, or did I jump to answers? What was one moment where I should have asked a question instead of teaching?"

**Between-session reflection prompt for mentee (complete within 48 hours):**
"Think about the last design doc or technical proposal you wrote. Rewrite the first paragraph the way a Staff Engineer would write it -- focused on the problem, not the solution. What was hard about that rewrite?"

---

### ACTION ITEMS

| Action | Owner | Due Date | Success Criterion | Difficulty |
|--------|-------|----------|------------------|------------|
| Identify one upcoming design decision (next 3 weeks) and write a 1-page problem framing section before writing any solution | Mentee | [7 days from session] | Problem framing section completed and shared in our shared doc for mentor to review | Stretch |
| Find and read one design doc written by a Staff or Principal engineer at your company -- annotate it for examples of the three dimensions | Mentee | [5 days from session] | Annotations added to a copy of the doc; bring 2 specific observations to Session 3 | Easy |
| Mentor sends 1-2 examples of strong problem framing from past design docs (anonymized if needed) | Mentor | [3 days from session] | Examples shared in shared doc | -- |

---

### GOAL TRACKER

**Milestone Goals (4-8 week horizon):**

| Goal | Target Date | Status | Progress (1-5) | Session Actions That Contribute |
|------|-------------|--------|----------------|---------------------------------|
| Write one Staff-level design doc (assessed by mentor as meeting all 3 dimensions) on a real project | [8 weeks from now] | In Progress | 2 | Action item 1 above; Session 3 deep work |
| Get named as a contributor or co-author on one cross-team technical document | [10 weeks from now] | Not Started | 1 | To be addressed in Session 4 (Visibility) |
| Deliver one technical update to a VP-level stakeholder and receive positive feedback on clarity | [12 weeks from now] | Not Started 

…(truncated)