Grandmaster · Growth Library
Keep a Work Wins Log You Can Reuse
Capture concrete outcomes while the details are still easy to reconstruct.
Try this
After a meaningful piece of work, add a short entry with the situation, your contribution, the concrete result or current state, and one or two tags. During a review, retrieve entries that match the purpose and verify any figures or claims before reusing them.
Check-in: What changed, what did I contribute, what detail will I need later, and is the entry specific enough to reuse without exaggeration?
Evidence: Practical guidance; no evidence-like claim is detected in the current source record.
Review note: The inherited article contained fabricated pilot and user outcomes, unsupported confidence and motivation effects, arbitrary logging frequencies, pseudo-precise timing and invented retrieval improvements. The effective public record is narrowed to maintaining a compact reusable record of completed work, solved problems, decisions and contributions without claiming psychological or performance effects.
A work wins log is a retrieval aid, not a scoreboard. Its job is to preserve concrete examples that are easy to lose after several weeks: what happened, what you contributed, what changed, and enough context to explain the example accurately when a review, resume, proposal, interview, retrospective, or planning session needs it.
1. Capture the concrete change
Write the entry close enough to the work that the details are still available. Name the deliverable, problem, decision, recovery, or contribution. Prefer a short factual description over a broad label such as productive day or great meeting.
2. Add only the context you may need later
Record your role, the constraint that mattered, and the current result or state. If a figure is important, include it only when it is known and traceable. If the useful example contains confidential details, redact or generalize them before storing the note.
4. Reuse the record without inflating it
When you need an example, retrieve the relevant entries and adapt them to the purpose. Separate what you personally did from what the team did, distinguish the observed result from your interpretation, and verify dates, numbers, names, and scope before publishing or sending the claim.
Questions to consider
What belongs in a work wins log?
Include completed deliverables, problems solved, decisions clarified, risks reduced, useful support, recoveries from mistakes and other concrete contributions you may need to explain later. Small entries are useful when they preserve a fact that would otherwise be forgotten.
Should every entry include a number?
No. Use a number only when you actually know it and can verify it. A precise description of what changed is better than an invented metric added to make the entry sound stronger.
What should I avoid recording?
Do not store secrets, credentials, unnecessary personal data, customer information or confidential internal details in a place that is not approved for them. Use redacted wording when the useful lesson does not require the sensitive detail.
Maintenance record
Review history
Current status: Reviewed. An editorial or evidence review is recorded and no later event changes that conclusion.
2026-09-10 · reviewed · Brali claim cleanup agent Source: protocol-content-overrides-claim-cleanup-batch-5.json
Replace fabricated pilot outcomes, unsupported confidence and motivation claims, invented adherence figures, arbitrary logging targets and pseudo-precise review schedules with a bounded work-record workflow.
Browse the review ledger · Challenge or update this hack
Implementation observations can trigger a review, but they cannot change an evidence conclusion by themselves. Commercial relationships do not control review status or outcomes.
Continue from here
Choose the next useful path.
Article versions
Brali keeps substantive article history visible. Later reviews may refresh wording, sources, examples, or boundaries without silently replacing the record.
- Version 2025-10-06: first recorded publication in the migrated Brali corpus.
- Evidence review 2026-09-10: reviewed by Brali claim cleanup agent; evidence state is
practical.
Canonical source record · Evidence state: practical.