5-15 Report
| Category | Communication / Managing Up |
| Origin | Yvon Chouinard (Patagonia founder); popularized by Paul Hawken in Growing a Business; practiced by Will Larson |
| Surfaced in OS | Mar 24, 2026 |
Core Concept
A weekly written report that takes no more than 15 minutes to write and no more than 5 minutes to read. Reports cascade upward: each person writes one, their manager reads several (5 min each), then synthesizes their own 15-minute report for their manager. The result is a lightweight, scalable information flow that gives leaders real signal without adding meeting overhead.
The Format
- Main achievements — What got done this week? What are you most proud of or satisfied with?
- Concerns — Is there anything worrying you, in or outside of work?
- Team morale — How are you feeling? What’s the morale of the people around you?
- Leadership feedback — Is there anything I (your manager) could be doing better, differently, or more of?
Why It Works
- Constraint drives quality. The 15-minute writing limit forces writers to prioritize — you can’t include everything, so you include what matters.
- Reading scales. A manager with 6 reports spends 30 minutes reading and has real signal on their entire org. No meeting required.
- Cascade creates synthesis. Each layer summarizes the layer below, so executive leadership gets progressively compressed signal — not raw noise and not filtered silence.
- Concerns surface early. The explicit “concerns” section gives people a low-friction way to flag problems before they become crises. This directly supports Never Surprise Your Manager.
- Morale becomes visible. Most managers don’t know team morale until it’s too late. Asking weekly makes it a leading indicator instead of a lagging one.
How to Practice It
- Writers take notes throughout the week rather than writing last-minute on Friday — the report should reflect the whole week, not whatever’s top of mind at 4 PM.
- Managers must respond to every report. Even a brief acknowledgment. If people write into a void, they stop writing. This is Incentives Drive Behavior in action.
- Keep the time constraint sacred. If reports are taking 45 minutes to write, the format has drifted — cut back to the four sections, no more.
- Don’t turn it into a status report. The power is in the concerns and morale sections, not the achievements list. If you only get task updates, coach people to include the human signal.
Where to Apply
- A new senior leader role: Introducing 5-15s as direct reports ramp on initiative ownership gives you weekly signal without adding more meetings. Pairs naturally with an Engineering Initiative One-Pager — the one-pager frames the project, the 5-15 provides ongoing pulse.
- Scaling communication: As the management layer gets built, 5-15s create an information flow structure before formal processes are in place.
- Will Larson’s practice: Takes him ~10 minutes. Writes at lethain.com/weekly-updates.
Related Patterns
- Never Surprise Your Manager — the 5-15 is the mechanism that prevents surprises
- Five Sacred Duties — duty #1 (communicate priorities) and #4 (evaluate performance) are both served by this cadence
- Transparency vs Comprehension — the 5-15 delivers comprehension, not raw transparency: pre-synthesized, constrained, actionable
- Incentives Drive Behavior — responding to every report rewards the surfacing behavior
- Ladder of Leadership — the 5-15 pushes people up the ladder by asking them to synthesize their own situation