home / skills / coowoolf / insighthunt-skills / waterline-model
This skill helps you diagnose team problems by prioritizing surface-level structural issues before diving into personality conflicts.
npx playbooks add skill coowoolf/insighthunt-skills --skill waterline-modelReview the files below or copy the command above to add this skill to your agents.
---
name: Waterline Model
description: Diagnose team problems by checking structural issues (goals/roles) at the surface before diving deep into personality conflicts. 80% of team problems are structural, not personal.
---
# The Waterline Model
> "Your only goal as a manager, if you do nothing else, is clear roles and clear expectations." β Molly Graham
## What It Is
Imagine a team as a boat. Problems **below the waterline** sink the boat. Leaders often dive deep (scuba) to fix "people problems" first, but they should **snorkel first**. Start at the surface with structural issues (goals/roles) before addressing interpersonal dynamics.
## When To Use
- Friction, confusion, or **underperformance** within a team
- Before assuming conflict is due to **"difficult people"**
- When teams are **fighting** over responsibilities
- As a diagnostic before any team restructuring
## The Model
```
π SURFACE (Snorkel First)
βββββββββββββββββββββββββββββββββββββββββββ
β 1. GOALS β Does team know destination? β
β 2. ROLES β Who owns what? β
β 3. EXPECTATIONS β What does good look? β
βββββββββββββββββββββββββββββββββββββββββββ
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
βββββββββββββββββββββββββββββββββββββββββββ
β 4. SKILLS β Can they do the job? β
β 5. MOTIVATION β Do they want to? β
β 6. PERSONALITY β Is there true clash? β
βββββββββββββββββββββββββββββββββββββββββββ
π DEPTH (Scuba Later)
```
## Core Principles
### 1. Snorkel Before You Scuba
Check structural alignment before analyzing personality conflicts.
### 2. Clarify Goals
Does the team know what the destination is?
### 3. Clarify Roles
Does everyone know who owns what part of the elephant?
### 80% Rule
**80% of team problems are structural**, not personality-driven. Fix structure before blaming people.
## How To Apply
```
STEP 1: Ask "What number were you hired to drive?"
βββ If answer is vague β Goal problem
STEP 2: Ask "Who owns [specific task]?"
βββ If multiple people claim it β Role problem
βββ If no one claims it β Role problem
STEP 3: Ask "What does good look like?"
βββ If answer is vague β Expectations problem
STEP 4: Only After 1-3 Are Clear
βββ Consider skills, motivation, personality
```
## Common Mistakes
β Assuming conflict is due to "bad culture" or "difficult people"
β Jumping straight to personality assessments
β Reorganizing teams without first clarifying goals
## Real-World Example
Graham often finds that when teams are fighting, simply asking "What number were you hired to drive?" reveals that no one actually knows their specific accountability.
---
*Source: Molly Graham, Lenny's Podcast*
This skill helps leaders diagnose team problems by checking surface-level structural issuesβgoals, roles, and expectationsβbefore diving into personalities. It treats teams like a boat: snorkel at the surface first to resolve whatβs causing friction, then scuba into skills, motivation, and personality if needed. Using this model prevents misattributing structural problems to people and reduces unnecessary reorganizations.
The skill walks through a quick set of diagnostic questions: who owns which outcomes, what the teamβs destination is, and what success looks like. If answers are vague or overlapping, it identifies goal, role, or expectation problems and recommends clarifying them. Only after surface issues are resolved does it prompt exploring skills, motivation, and personality conflicts.
What if roles and goals are clear but problems persist?
Then proceed to examine skills, motivation, and personalityβthose deeper factors matter once structure is sound.
How long should the snorkel diagnostic take?
A focused 15β30 minute conversation per issue is often enough to reveal surface misalignment.