Preview a lesson
Below is an illustrative example of the kind of short lesson used inside the framework, along with a sample update rewrite and a sample win-log entry. Consider this a walk-through of the format, not a claim about outcomes.
Turning a status update into something worth reading
A common starting point is a status update built around a simple structure: Situation, Contribution, Impact, Next step. It's short enough to write in ten minutes and short enough that someone will actually finish reading it.
Before
"This week we continued working on the migration. Made some progress on a few things. Will keep everyone posted."
After
"The migration was blocked by a schema mismatch between the two systems. I mapped the conflicting fields and rebuilt the sync logic, which unblocked QA a day ahead of schedule. Next: confirming rollback steps with the infra team."
What a win-log entry tends to include
A useful entry is short enough to write in a few minutes but specific enough to be useful eight months later. Here's an illustrative example of the fields we suggest using.
A short set of prompts before a meeting that matters
These are the kinds of questions we suggest sitting with for two or three minutes before a meeting where you want your input remembered, not rehearsed word for word.
What's the one point?
If you only get to make one contribution in this meeting, what should it be? Write it down in a single sentence beforehand.
What's it called?
Giving an idea a short, memorable name makes it easier for others to reference it later, and easier for you to bring it up again.
When's the right moment?
Sometimes the strongest contribution is a well-placed question early on, not a comment squeezed in at the end.
What's the follow-up?
A short written recap sent afterward, even two sentences, is often what actually gets remembered next quarter.
Want to know more about how this works?
If you have questions about the format, the reasoning, or whether this fits your particular role, reach out directly.
