---
title: 'Know All, Tell Not'
synced_from_vault: true
vault_source: 03-living-docs/patterns/Know-All-Tell-Not.md
public: true
type: pattern
category: leadership
tags:
  - pattern
  - leadership
  - intent-based-leadership
  - delegation
  - coaching
created: 2026-03-08T00:00:00.000Z
origin: 'Dave Paola, blog draft (2024); L. David Marquet, Turn the Ship Around'
---

| | |
|-|-|
| **Category** | Leadership |
| **Origin** | Dave Paola, blog draft (Aug 2024); L. David Marquet, *Turn the Ship Around* |
| **Surfaced in OS** | Mar 8, 2026 (imported from ZK) |

---

## Core Concept

A "know all, tell not" leader understands the power of **not giving the team the answer** — even when they know it, even when they're right. By telling your team the answer, you rob them of the most valuable thing they joined for: the chance to learn by figuring it out themselves.

---

## The Observation

Early in his career at Bloc, Dave had smart people on his team who seemed to operate at half horsepower. They weren't energized. They had fuel in the tank but weren't using it. Hard engineering challenges existed, junior people needed coaching, experiments needed running — yet the team felt flat.

He even asked them directly. Nobody could articulate the problem.

The realization came from reading Marquet: **the leader was giving them the answers.**

---

## The Mechanism

When you tell your team the answer to a problem, you:

1. **Remove the challenge** — "design this fancy architecture" sounds engaging but in practice rarely is. "Why does this bug keep happening for this specific user?" is genuinely interesting. But only if you let them solve it.
2. **Short-circuit learning** — people don't learn by being told. They learn by figuring it out.
3. **Train dependency** — the team learns to wait for you instead of thinking for themselves.

Yes, it hurts productivity. But only in the extreme short term. On any other timescale, you're forcing the team to engage, giving them actual challenges, and developing their capabilities.

---

## The Practice

Next time you're tempted to chime in with the answer: **refuse.** Trust the team to figure it out. They'll come through and they'll feel better about themselves.

And, as a bonus, you'll have extricated yourself from the process. Now you can go home and eat dinner.

---

## Where I've Seen It

- **Bloc** — the founding observation. Smart engineers operating at half capacity because Dave was solving problems for them.
- **Later teams** — applied deliberately with senior ICs, with stronger results over months than any single tactical answer would have produced.

---

## Related Patterns

- [Ladder of Leadership](/patterns/ladder-of-leadership) — "know all, tell not" is the behavioral discipline that pushes people UP the ladder. Giving answers keeps them at rung 1-2.
- [Right vs Effective](/patterns/right-vs-effective) — sometimes being right (knowing the answer) is less effective than staying quiet
- [Busy vs Productive](/patterns/busy-vs-productive) — the leader who stops giving answers may look less productive but is far more effective
- Challenge as Compensation — the team needs the challenge; removing it removes a form of compensation

---

## Cross-References