How do I organize evidence for a skill that appears across several different projects?

Start with a one-sentence description of the skill you want to demonstrate. Make it specific enough to guide your choices: for example, “turning unclear requests into agreed next steps,” rather than simply “communication.”

Then give each project example a different job. One might show how you clarified an initial request, another how you adapted when circumstances changed, and a third how you made the approach useful to other contributors. You do not need to include every project. Choose examples that add something new.

Create an index before writing full stories. For each example, capture the project, situation, your contribution, an artifact or observable result, and the particular part of the skill it demonstrates. Keep claims within what you can support; if you cannot verify a result, describe the action or artifact instead.

Assuming these are representative projects, you could organize them like this. The project details below are placeholders, not claims about your experience.

Skill: Turning ambiguous requests into agreed next steps.

1. Project A — Clarifying the request. A stakeholder’s initial request lacked a clear outcome. I asked what decision or deliverable was needed and recorded the agreed scope. Evidence: [brief, decision note, or message]. Role: Shows how I uncover the actual request.
2. Project B — Managing a changing request. The requirements shifted during the work. I summarized what had changed, identified open questions, and confirmed the next priorities. Evidence: [updated plan or review notes]. Role: Shows adaptation, not just initial clarification.
3. Project C — Making the approach repeatable. Several contributors needed a shared understanding of the work. I used a concise handoff or checklist to make responsibilities and next steps visible. Evidence: [handoff or checklist]. Role: Shows how I help others act on clarified requests.

The examples work together because they show different situations and behaviors. Replace the placeholders with details you can substantiate. If two projects show the same behavior, combine them or choose the clearer example; a longer list is not automatically stronger.

Keep the index compact enough to scan. A few lines per example are usually enough for a working draft: context, your action, evidence, and the example’s distinct role. You can expand a selected example later for a particular application or conversation. The index is organized material to draw from, not a script you must repeat word for word.

A reusable row might be:

Skill | Project | Situation | My specific action | Evidence or artifact | What this example shows | Details to verify

For instance: “Making ambiguous requests actionable | [Project] | [Request had unclear outcome] | [Questions asked and agreement recorded] | [Artifact] | Clarifies scope before work begins | [Confirm dates and wording].”

When tailoring the material, select the examples that best fit the opportunity or discussion. Explain the situation briefly, emphasize your own contribution, and use the artifact or result to keep the account concrete. Distinguish your work from other people’s contributions rather than implying a team outcome was solely yours.

Not necessarily. A saved document or metric can make an example easier to check, but you can still describe a specific action and what followed, as long as you do not present an estimate or memory as a verified result. Mark uncertain details for checking, and avoid claiming impact you cannot support.

If an example depends on confidential project material, describe the work at an appropriate level without copying sensitive content into the index. You can also choose another example that makes the same point more clearly. The goal is a useful, honest set of distinct examples—not a complete record of every project.