Onboarding Buddy Check-In Log

Template Overview

Joining a new organization involves absorbing immense tacit knowledge, cultural norms, and workflow nuances. The Onboarding Buddy Check-In template provides a welcoming, low-pressure framework for new hires to ask candid questions, resolve laptop setup friction, and build peer relationships.

Markdown Template Structure

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

---
title: "Buddy Check-In: [New Hire Name]"
date: [YYYY-MM-DD]
buddy: "[[Tenured Peer Name]]"
new_hire: "[[New Team Member Name]]"
onboarding_week: "Week 2 / Environmental Integration"
tags: [onboarding, buddy, culture, peer-support]
---

# Buddy Check-In — [New Hire Name]

## 1. Informal Vibe & Friction Check
- **How was your second week?** "Feeling much more oriented. Successfully cloned the monorepo and passed the local test suite."
- **Current Friction Points:** "Wasn't sure where team RFC discussions happen or who approves production pull requests."
- **Energy & Welcome:** Feeling supported by the team; appreciated prompt Slack answers on architecture channels.

## 2. Tooling & Environment Health
- [x] Local developer vault initialized in standard Markdown folder.
- [x] macOS developer certificates and local Xcode command line tools configured.
- [ ] GPG commit signing key configured in local Git configuration.
- [x] Access verified for internal issue tracker and staging environments.

## 3. Cultural & Team Navigation Tips
- **Async Communication Culture:** The team values thorough Markdown write-ups over reactive Slack threads.
- **Meeting Norms:** Camera is optional; meetings start 2 minutes past the hour; bot recorders are strictly prohibited.
- **Who to Ask For What:**
  - Database schema alterations: [[Alex Chen]]
  - Design component library: [[Julian Vance]]
  - Apple Silicon audio entitlements: [[Marcus Vance]]

## 4. Next Week's Milestones & Action Items
- [ ] [[New Hire Name]] Submit first small bug-fix pull request to staging branch.
- [ ] [[Buddy Name]] Introduce new hire to cross-functional design partners during coffee catch-up.

Filled Real-World Example

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

---
title: "Buddy Check-In: Liam Foster"
date: 2026-10-08
buddy: "[[Rachel Adams]]"
new_hire: "[[Liam Foster]]"
onboarding_week: "Week 1"
tags: [onboarding, buddy, culture]
---

# Buddy Check-In: Liam Foster

## 1. Check-In Notes
Liam completed his first week smoothly. Resolved a minor macOS permission hitch regarding ScreenCaptureKit during local development.

## 2. Unwritten Rules Shared
Rachel walked Liam through our commit message standards and explained why we enforce brand-free codebase rules to protect white-label architecture.

When to Use and When to Avoid

When to Use

• Use during weekly peer buddy sessions across a new hire’s first 90 days.
• Use to troubleshoot developer environment quirks and explain unspoken cultural norms.
• Use to help new team members navigate cross-functional relationships.

When to Avoid

• Avoid using for formal managerial performance reviews or compensation negotiations.
• Avoid using for disciplinary documentation.

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Analyze the onboarding buddy check-in recording:
1. Summarize any technical tooling hurdles or procedural confusion experienced by the new hire.
2. Outline cultural tips and team relationship advice shared by the tenured peer.
3. List next week's onboarding milestones and action items into clean Markdown.

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