The examples in this newsletter are drawn from real partnership experiences. Names and identifying details have been altered to protect privacy.
Who's This For
You're writing the annual report. The deadline is two weeks away. You remember that something important happened - something that would make this report actually compelling instead of a list of outputs and participation numbers.
But you can't quite remember the details.
Was it the workshop in April or May? What exactly did the industry partner say that made everyone stop talking? Who was the student whose project ended up influencing the curriculum redesign?
You know it happened. You were there. But the specifics - the kind that make reports come alive - they're gone. Lost to the six months between when it happened and when you needed to write about it.
This newsletter is for anyone who has sat down to write a report and realized their best evidence walked out the door months ago. It's for PIs, evaluators, partnership professionals, and anyone else who wants to stop scrambling at report time and start building evidence while the work is happening.
A bit about where this comes from: I've watched hundreds of grant teams reach reporting season with the same panicked question - what were those stories we were going to tell? The ones who have compelling reports aren't the ones with better memories. They're the ones who built capture into the work itself.
The Partnership Moment
Picture this: It's month four of your project. A workshop is happening. Something unexpected occurs - maybe a participant makes a connection you hadn't anticipated, or a partner responds to a question in a way that reveals something important about how the collaboration is actually working.
You think: I should write this down.
Then a participant needs your attention. Then the break runs long. Then there's the drive back to campus. Then the next thing.
Six months later, you're writing the annual report. You remember something important happened at that workshop. You open your notes and find: "Workshop 4 - good discussion. 23 participants. Follow up with Maria about next steps."
That's it. The story is gone.
This happens constantly. Not because people don't care about documentation. Because the structures for capturing stories in real time rarely exist. We design the activities. We plan the logistics. We prepare the materials. But we don't design the capture.
Under the Surface
Here's what's actually happening: most grant teams treat story capture as a reporting task instead of a design task.
Reporting task thinking: "We need stories for the annual report. Let's collect them in month eleven."
Design task thinking: "We're creating moments where important things will happen. How do we capture them while they're happening?"
The difference sounds small, but it changes everything about what evidence you have when you need it.
Reporting task thinking puts you in permanent catch-up mode. You're always reconstructing the past, relying on memory, hoping someone took notes. And memory is wildly unreliable - especially for the kind of specific, vivid details that make stories compelling.
Design task thinking embeds capture into the activities themselves. The prompts you use in workshops carry reflective questions. The portfolio pieces participants create represent themselves through the journey. The weekly team reflections include story-spotting protocols.
This isn't about adding more documentation burden. It's about making documentation happen as a byproduct of work you're already doing.
