How-to: Document Performance Facts
Memory is a biased filing system. When performance talks rely on vibes, people feel ambushed and managers struggle to coach. Documenting performance facts (specific, dated, observable) gives you a fairer base for praise, course-correction, and reviews. This is workplace education, not legal advice. For formal actions, PIPs, accommodations, or disputes, follow employer policy, HR, and counsel.
Time box: 15–25 minutes per meaningful example when it happens (or weekly 20-minute capture). Do not wait for review season.
Use with feedback, how HR works, and manager habits in the New Manager hub. ICs keeping a work journal can pair with the Individual Contributor hub.
When to use / when not
Use when:
– You need examples for coaching, calibration, or a review draft
– Patterns are emerging (strengths or gaps) and you want evidence, not anecdotes alone
– You are preparing balanced feedback (positive and constructive)
– Handoffs between managers require continuity
Do not use when:
– You are building a secret dossier to punish someone. That is not coaching.
– The issue is harassment, discrimination, safety, or legal risk. Escalate through proper channels immediately.
– You only have rumors. Verify or drop.
– HR has instructed a specific documentation process. Follow that process.
Fact logs support clarity. They do not replace human conversations.
Prep
- Private, secure notes location approved by company norms (not a random personal app if policy forbids it)
- Template fields: date, context, what happened (observable), impact, what you said/did, next check
- Access to goals, job expectations, or scorecards if they exist
- Calendar reminders for a weekly 15-minute capture
Managers: separate coaching notes from formal HR case files unless HR directs otherwise.
Steps
- Capture close to the event (5–10 min). Same day beats three weeks later.
- Write observables (5 min). What was said, shipped, missed, or decided. Avoid mind-reading.
- Add impact (3–5 min). Customer, team, timeline, quality, risk. Stay proportional.
- Note the conversation (3–5 min). Feedback given? Commitments made?
- Tag theme lightly. e.g., ownership, communication, craft. Do not over-label.
- Review weekly (10–15 min). Look for patterns worth a live conversation now.
- Use in talks, then update. After 1:1s or reviews, record outcomes and new expectations.
For praise, document too. People deserve receipts for strong work (praise that lands).
Script (what to say / send)
Fact line (private note):
2026-09-08 – Sprint review. Deliverable X missed agreed date after two check-ins (9/1, 9/5). Impact: blocked Design handoff by 2 days. Discussed in 1:1: agreed daily standup update and mid-week risk flag. Follow-up: 9/15.
Strength example:
2026-09-03 – Customer call. Clarified scope live and wrote recap with owners in 20 minutes. Impact: prevented a wrong build. Called out in team channel.
Feedback opener using facts:
“I want to talk about the last two release dates. On [dates], we missed the agreed handoff, which delayed [impact]. I want to understand barriers and set a clearer risk-flag habit.”
If the person asks why you take notes:
“I keep short examples so feedback stays specific and fair, including strengths. Happy to share the themes I am seeing.”
When to loop HR (manager):
“This is moving beyond normal coaching. I am going to partner with HR on process before we go further.”
Output
Performance facts log:
1. Dated entries with context, behavior, impact, conversation, next step
2. Balanced mix over time (strengths and gaps)
3. Themes ready for 1:1s or review drafts (manager review draft, write self review)
4. Clear escalation notes when issues exceed coaching
For remote teams, capture facts from written artifacts too: missed handoff notes, strong design reviews, customer emails. Same rules apply. Observable, dated, impact-linked.
When patterns emerge, schedule the conversation within a week. A perfect log you never speak about helps nobody. If the person improves, document that too so the story stays current.
Calibration rooms go better when multiple managers share the same fact standard. Swap anonymized examples of good notes in a manager forum so the bar rises together. Still keep individual files private and policy-aligned.
If you are an IC keeping a personal work journal for reviews, use the same fields. It improves self-reviews and reduces memory bias without turning into self-surveillance theater.
Watch-outs
- Labels without examples. “Bad attitude” is not a fact.
- Absolute language. Prefer “in these three meetings” over “always.”
- Surprise reviews. If the log never becomes a conversation, you failed the point.
- Storing sensitive content unsafely. Follow company systems and retention rules.
- Medical or leave speculation. Do not diagnose. Route accommodations and leave through proper channels. Education only; not legal advice.
- Weaponized volume. Fifty nitpicks are not better than three clear patterns.
Done looks like a short, dated set of examples you can read aloud without embarrassment, used to coach in time rather than reconstruct a year from memory.