Documenting Your Impact When Your Work Spans Multiple Teams

You shipped a feature that unblocked two other teams, mentored an engineer from a completely different department, and fixed a critical data pipeline that nobody owned. Then review season arrived and your manager — who only sees one slice of your work — asked what you'd been up to.

Working across multiple teams is genuinely good for your career. But it creates a visibility gap: your contributions scatter across Slack channels, Jira boards, and other people's roadmaps. If you don't document them yourself, they effectively didn't happen.

What You'll Learn

• Why cross-team work is harder to document and why that matters for promotions
• A simple weekly logging habit that takes less than ten minutes
• How to frame your impact in terms that resonate with your manager and skip-level
• How to collect and store social proof — kind words from stakeholders that become evidence
• How to synthesize your log into a compelling self-review without bragging

Why Cross-Team Work Creates a Visibility Gap

Most performance systems are built around vertical accountability. Your manager knows what you did on your direct team's projects. They have less visibility into the three days you spent helping the data team debug a broken ingestion job, or the design review you ran for a product team two floors away.

This isn't your manager's fault. They're not in those rooms. And unless you build a deliberate paper trail, neither of you will have accurate recall when it matters. Performance reviews rely heavily on recent memory — documenting in real time is the only fix.

Start a Weekly Impact Log

The simplest system is a private document you update every Friday. Open it before you close your laptop and spend five minutes answering three questions:

1. What did I finish or meaningfully advance this week?
2. Which teams or people outside my immediate group did I help?
3. What was the measurable or qualitative outcome?

You don't need paragraphs. A few bullet points per week add up fast. After a month you'll have a detailed record that your memory alone could never reconstruct.

Keep one log per quarter so you can export it directly into your self-review. Store it somewhere you control — a personal Notion page, a Google Doc in your own Drive, or even a plain text file. Don't rely solely on your company's HR tool; those often get wiped at year-end.

Write Down Outcomes, Not Activities

There's a meaningful difference between