Lateral Team Transfer Dialogue

Template Overview

Supporting internal mobility retains high-performing employees by providing fresh career challenges within your organization. This template structures lateral transfer dialogues, assesses role suitability, aligns transition timelines, and ensures orderly project handovers.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Internal Transfer Dialogue: [Employee Name]"
date: [YYYY-MM-DD]
current_manager: "[[Current Manager Name]]"
receiving_manager: "[[Receiving Manager Name]]"
employee: "[[Employee Name]]"
current_team: "Client UI Applications"
target_team: "Core Audio & Systems Architecture"
proposed_transfer_date: "[YYYY-MM-DD]"
tags: [internal-mobility, career, transfer, talent-retention]
---

# Lateral Team Transfer Dialogue — [Employee Name]

## 1. Motivation & Career Direction
- **Career Aspiration:** Desires deeper engagement with low-level macOS systems programming, CoreAudio drivers, and on-device Whisper optimizations.
- **Track Record:** 2 years of exceptional frontend UI delivery; spearheaded the live-preview Markdown editor refactor.
- **Mutual Benefit:** Retains proven company talent while strengthening the systems engineering bench.

## 2. Technical Competency & Growth Plan
| Required Competency | Current Proficiency | Gap Mitigation Plan |
|---|---|---|
| **Swift & Objective-C Bridges** | Intermediate | Pair on ScreenCaptureKit audio pipeline with [[Marcus Vance]] |
| **C++ Whisper Bindings** | Fundamental | Complete internal whisper.cpp architectural study module |
| **System Architecture Knowledge** | Advanced | Ready to contribute immediately |

## 3. Handover Plan & Knowledge Transfer
- [ ] Complete documentation for the Table Navigation component library.
- [ ] Transfer primary code review ownership of live-preview editor to [[Peer Engineer]].
- [ ] Conduct two 60-minute recorded pairing sessions on editor decoration architecture.

## 4. Transfer Timeline & Transition Milestones
- **Weeks 1–2:** 80% current team wrap-up / 20% target team onboarding.
- **Weeks 3–4:** 50% project handover / 50% new feature development.
- **Week 5:** 100% formal transition to target team with updated reporting hierarchy.

## 5. Sign-Off & Approvals
- [x] Current Manager Approval: Confirmed with transition roadmap.
- [x] Receiving Manager Approval: Confirmed headcount requisition open.
- [x] Employee Confirmation: Reaffirmed enthusiasm for systems role.

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "Transfer Chat: David Miller"
date: 2026-10-04
current_manager: "[[Marcus Vance]]"
receiving_manager: "[[Alex Chen]]"
employee: "[[David Miller]]"
tags: [internal-mobility, career]
---

# Transfer Chat: David Miller

## 1. Dialogue Summary
David Miller discussed his desire to transition from general developer tooling to Core Audio engine development. Marcus Vance and Alex Chen approved the transition with a 4-week structured handover period.

## 2. Key Handover Milestone
David will finalize documentation on FTS5 index rebuild procedures before moving full-time to audio capture optimization.

When to Use and When to Avoid

When to Use

• Use during internal mobility explorations and lateral career transfer discussions.
• Use to negotiate fair transition timelines between sending and receiving managers.
• Use to create structured handover and skill gap mitigation roadmaps.

When to Avoid

• Avoid using to resolve active disciplinary performance issues.
• Avoid using before open headcount has been verified with leadership.

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Analyze the internal transfer dialogue audio recording:
1. Summarize the employee's career motivations and desired target team.
2. Outline the agreed project handover milestones and phased capacity transition timeline.
3. List competencies requiring targeted mentorship and follow-up approval dates into Markdown.

Your data remains securely on your Mac with zero cloud exposure.