Building an Impact Logs Culture: Beyond the Brag Document

Julia Evan's concept of the "brag document" was a breakthrough. For the first time, individual contributors had a framework for tracking their own impact. But brag documents have a limitation: they're private, unvalidated, and disconnected from career progression.

From Brag Docs to Impact Logs

Impact logs take the brag document concept and make it collaborative. The key differences: they're visible to managers (so they inform promotion decisions), they're skill-tagged (so they connect to career frameworks), and they can be endorsed (so there's validation beyond self-report).

The Manager's Role

Managers should be endorsing impact logs weekly, not just during performance review season. When a team member logs "Led incident response for the payments outage — resolved in 47 minutes, 0 data loss", that's evidence of incident management skill at a senior level. Endorse it. Tag it. Reference it later.

Making It Stick

The teams with the strongest impact log cultures do three things: they make logging easy (2 minutes max), they make it part of existing rituals (end-of-sprint, weekly 1:1s), and they visibly use logs in promotion and growth conversations. When people see that logging impact actually leads to recognition, the habit sticks.

The goal isn't documentation for its own sake. It's building an organizational memory of who did what, when, and what skills it demonstrated. That's the foundation of fair, evidence-based career progression.