home / skills / coowoolf / insighthunt-skills / personal-operating-manual

personal-operating-manual skill

/career-development/personal-operating-manual

This skill helps onboarding teams faster by capturing a leader's values, work style, and communication preferences in a personal operating manual.

npx playbooks add skill coowoolf/insighthunt-skills --skill personal-operating-manual

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
3.1 KB
---
name: Personal Operating Manual
description: A document created by a leader that articulates their values, quirks, and expectations to accelerate mutual understanding with their team. Use when onboarding new team members or taking over a new team.
---

# Personal Operating Manual

> "If you don't start putting those things in early, people will just invent those things. And then you'll have a house that got added on to 17 times." — Claire Hughes Johnson

## What It Is

A document created by a leader that articulates their **values, quirks, and expectations** to accelerate mutual understanding with their team.

## When To Use

- **Onboarding new team members**
- **Taking over a new team**
- After **promotion to leadership**
- As a **team-building exercise**

## Personal Operating Manual Template

```markdown
# [Your Name]'s Operating Manual

## My Top 3 Values
1. [Value 1] — Story/origin of why this matters to me
2. [Value 2] — Story/origin
3. [Value 3] — Story/origin

## My Work Style
- Introvert ◀️────▶️ Extrovert:  [X]
- Task ◀️────▶️ People-Oriented: [X]
- Morning person / Night owl:     [X]

## How I Communicate
- I prefer [async/sync] for [context]
- Default response time: [X hours/days]
- Best way to get my attention: [method]

## My Operating Principles
1. "[Principle 1]" — What this means in practice
2. "[Principle 2]" — What this means in practice
3. "[Principle 3]" — What this means in practice

## What I Expect From You
- [Expectation 1]
- [Expectation 2]

## What You Can Expect From Me
- [Commitment 1]
- [Commitment 2]

## How to Give Me Feedback
- [Preferred method]
- [What to avoid]
```

## Core Principles

### 1. Define Top Values
Select 3 core values (e.g., Integrity, Curiosity) and identify the personal stories/trauma that formed them.

### 2. Map Work Style
Plot yourself on axes of Introvert vs. Extrovert and Task-Oriented vs. People-Oriented.

### 3. Articulate Principles
Write down your "rules of engagement" (e.g., "Build self-awareness to build mutual awareness").

### 4. Publish & Iterate
Share this document with the team and ask for their manuals in return.

## How To Apply

```
STEP 1: Self-Reflect
└── What formed your values?
└── What are your communication quirks?
└── What triggers frustration for you?

STEP 2: Write First Draft
└── Be specific, not generic
└── Include the "why" behind each item

STEP 3: Share with Team
└── Present in team meeting or onboarding
└── Invite questions and clarifications

STEP 4: Request Reciprocity
└── Ask team members to create theirs
└── Use as conversation starters in 1:1s

STEP 5: Iterate
└── Update based on feedback
└── Revisit annually
```

## Common Mistakes

❌ Listing generic values (like "honesty") without explaining specific behaviors

❌ Creating the manual but never actually sharing it

❌ Treating it as static instead of a living document

## Real-World Example

Claire sharing her principle of "Say the thing you think you cannot say" so her team knows that her direct feedback is meant to be helpful, not brutal.

---
*Source: Claire Hughes Johnson, Lenny's Podcast*

Overview

This skill helps leaders create a Personal Operating Manual: a short, shareable document that explains your values, work style, communication preferences, and expectations. It speeds up mutual understanding during onboarding, role changes, or team building by making implicit norms explicit. The manual is designed to be specific, actionable, and iterated over time.

How this skill works

You reflect on three core values with the stories that shaped them, map your work style on simple axes (introvert–extrovert, task–people), and list clear operating principles and commitments. The template captures communication defaults (preferred channels, response time), expectations you have of teammates, and how they can give feedback. You publish the manual, present it to the team, request reciprocity, and update it regularly.

When to use it

  • Onboarding a new hire so they understand how you work and what you expect
  • Taking over or reorganizing a team to establish norms quickly
  • After a promotion to leadership to reduce assumptions and misalignment
  • As a team-building exercise to surface differences and improve collaboration
  • When recurring miscommunications suggest unclear expectations

Best practices

  • Choose three concrete values and include a short story or example for each
  • Be specific about behaviors (e.g., "I reply within 24 hours on async messages")
  • Share the manual early and present it in a team meeting for Q&A
  • Ask team members to create and share their own manuals for reciprocity
  • Treat the document as living—review and revise it at least annually

Example use cases

  • A new product manager joins and reads the leader's manual to understand decision style and feedback preferences
  • A leader takes over a legacy team and publishes their operating manual to reset expectations
  • A newly promoted director publishes commitments and what they expect from leads during decision-making
  • Teams exchange manuals during a kickoff workshop to surface working differences and reduce friction
  • A manager uses the manual to clarify escalation paths and preferred communication channels

FAQ

How long should a Personal Operating Manual be?

Keep it concise—one to two pages with focused sections. Prioritize clarity over completeness.

Will this replace 1:1 conversations?

No. It supplements conversations by documenting defaults, then you use 1:1s to clarify and adapt.