The Running Impact Log
One always-current log across everything live with a single stakeholder — the artifact that fills the gap between formal reports and a real conversation.
Not for a single workstream — that’s the Sponsor Briefing Pack’s job. Use both. They answer different questions.
When to use it
- Any relationship with more than one active thread running at once
- When weekly reports only capture “completed + metric” and nothing else
- Before any exec-altitude conversation where they need to hand this upward
How it differs from the Briefing Pack
- Briefing Pack: depth on one workstream, at three altitudes
- This: breadth — everything live with one person, in one glance
- Refreshed before every touchpoint, not on a two-week cycle
Altitude tip
Who are you communicating with?
Pick an audience to see how this tool changes for them.
How to run it — Keep it current
- 01
List every thread
Every organization and initiative currently live with this person.
Setup
- 02
Name the outcome
The business outcome each thread actually delivers.
Per row
- 03
Tag the stage
Discovery, Implementation, or Wrap-up.
Per row
- 04
Update before every touch
Not quarterly — before every meeting this could come up.
Ongoing
The trap
Letting it go stale between meetings. This only works if it’s current enough to hand over unedited — a log updated once a quarter is just a report with worse formatting.