Your Data vs. Your Story

The story you tell about your work is almost always more coherent than the work itself. This is not because people lie. It is because narratives are built after the fact: they select, smooth, and sequence events into a version that makes sense. The version that makes sense is not the same as the version that happened — and the gap between the two is the most useful information you can collect about yourself.

Two channels, two reliabilities

Every professional runs two channels:

• The story channel — what you (or a colleague) say about work: intentions, explanations, self-assessments, the reasons a decision made sense.
• The behavior channel — what the record shows: the choices actually made under tradeoffs, the outputs delivered, the timestamps, the patterns across repeated situations.

The story channel feels more reliable because it is coherent, motivated, and comes from the person with the best access to their own intent. But intent is not behavior. Stories compress and smooth; they leave out the moments where the decision was inconsistent with the explanation. The behavior channel is noisier, but it is the only channel that does not argue for itself.

Why the divergence is valuable

The divergence between story and record is not a character flaw. It is calibration data. A concrete example: a project lead's story is "I am strong at parallel processing." Her project log tells a different version — whenever more than two critical tasks run simultaneously, delivery slips, and the delay appears in the record at a much higher rate than in single-tracked periods. The data point is not a judgment of her ability. It is a signal about which operating conditions produce her best output: sequenced critical tasks, not concurrent ones.

The same logic applies to teams. When a team's narrative says "we value honesty" and the record shows repeated avoidance of direct feedback, the divergence marks a gap between stated operating rules and actual ones. Divergence points are the highest-value information in any performance review, because they are the places where the model does not match reality. Finding them is not an accusation; it is an update opportunity.

How to make the comparison

1. Write your story down. Capture what you currently believe about your work style: your strengths, your bottlenecks, the conditions you think you need, the reasons behind your recent decisions.
2. Pull the record. Take your last ten real decisions or outputs — not the ones you planned, the ones you actually made. For knowledge workers the record is usually already already visible in different places: calendar blocks and their outcomes, email threads that resolved (or did not), decision documents, version histories, the projects you finished versus the ones you dropped. For each item, note the conditions, the choice, and the outcome.
3. Compare the two. Where does the story claim one thing and the record show another? List the divergences. A typical self-review surfaces two or three within a few minutes of honest comparison.
4. Treat the divergences as hypotheses to verify, not verdicts. One divergence might be an anomaly. Three out of ten is a pattern. Re-check against a second sample of ten before changing anything.

The same protocol works for evaluating others, with one adjustment: you cannot see their internal story, so compare their stated approach against their observable record — the consistency between words and record. The method is identical; only the data source changes.

What to do with the gap

The goal is not to make the story match the record perfectly. Narratives are necessary — they coordinate teams, explain decisions, and carry intent. The goal is to keep the gap visible and small: update the story when the record disagrees, and design decisions around the record rather than the narrative. The story tells you what people intend. The data tells you what actually happens. Both matter. They just are not the same thing.

Your data indicates the gap. The update is up to you.