An evidence bank is a small collection of experiences organized for retrieval. It is not a folder of polished scripts. Its purpose is to help you find a relevant decision quickly and describe it accurately.
The strongest evidence bank includes outcomes and limits. A prototype can demonstrate prioritization. An internal tool can demonstrate stakeholder work. A failed launch can demonstrate judgment. The label matters because it keeps the story defensible.
Start with six to ten experiences
Choose experiences with different tensions rather than collecting every project.
- A decision made under uncertainty.
- A conflict or disagreement.
- A failure or reversal.
- A difficult prioritization choice.
- A technical tradeoff.
- A moment of influence without authority.
- A result you can measure or clearly observe.
- A lesson that changed later behavior.
Record the evidence fields
For each experience, capture the state, your responsibility, the constraint, the decision, the alternative, the observed result, and the lesson. Keep source links or artifacts privately when they help you verify a number.
Apply an honest status label
Use launched only for something that actually reached its intended users. Use internal, staged, prototype, paper-only, planned, or shelved when those descriptions are more accurate. A smaller true claim is easier to defend than a larger fragile one.
Practice retrieval cues
Tag each experience by competencies such as ownership, ambiguity, conflict, speed, quality, influence, failure, or learning. Practice selecting evidence from the competency rather than memorizing one answer per question.