How do I present evidence of a skill when the work itself is difficult to understand?
Quick answer
Introduce the work in terms the reader already understands: what needed to change, who or what was affected, and what constraint mattered. Then describe your specific contribution, explain one or two important decisions without specialist shorthand, and point to evidence the reader can inspect. Separate what the sample shows from what it cannot show, such as your role in a team or the effect of the work over time.
The question, the details, the next step.
My work sample is technically detailed, but people outside my field may not understand it. How can I explain it without watering it down?
Keep the work sample intact, but add a short guide that tells readers what to notice. You are not trying to teach the whole field; you are helping someone understand the problem, your contribution, and why the evidence matters.
A useful structure is:
- Context: What needed to happen, in ordinary terms?
- Your role: Which part did you personally handle?
- Decision: What choice or judgment did the work require?
- Evidence: What in the sample lets a reader see that skill?
- Limits: What can’t this sample establish on its own?
For example, suppose the sample is a complex internal report. A plain-language introduction might say: “The team needed a clearer way to compare requests that used different measures. I organized the information into a consistent format and noted where comparisons were uncertain. In the report, look at the definitions and comparison notes to see how I handled that judgment. This sample shows my analysis and presentation; it does not show how the team used the report afterward.” Treat those details as placeholders—use only what is true of your work.
How much background should I give? I worry that either the reader won’t understand the project or I’ll spend too long explaining it.
Give only the background needed to understand your evidence. A practical test is whether each sentence helps the reader answer one of these questions: What was difficult? What did you do? What should I look at? If not, shorten it or move it out of the introduction.
Define a specialist term the first time it matters, using a brief everyday explanation. For instance, instead of leading with “I normalized the inputs,” you might write, “I put the entries into the same format so they could be compared.” Keep the technical term in parentheses only if it helps the reader navigate the sample. Don’t replace a meaningful technical detail with a vague claim such as “I solved a complex problem”; explain the decision in plain language and point to where the work shows it.
What if the work was collaborative, or the strongest evidence is a result that I can’t claim by myself?
Separate the team’s work from your own contribution. Name the shared setting briefly, then specify your part with concrete verbs: drafted, tested, compared, coordinated, revised, or presented—whichever accurately describes what you did. If several people made a decision, say so rather than implying sole ownership.
Be equally careful with results. You can describe an outcome only as far as you can support it, and explain your connection to it. If you cannot attribute a group result to your work, focus on the evidence you can show directly: your analysis, a section you wrote, a decision you documented, or a handoff you prepared. A reader should be able to distinguish the artifact from your account of your role in producing it.
Can you give me a reusable caption I can put beside a work sample?
Yes. Fill in the brackets, then remove any sentence that is not accurate or necessary:
What this is: [Describe the sample in everyday language.] The challenge: [What needed to be done, and what made it difficult?] My contribution: [Name the part you personally completed; distinguish shared work.] A decision I made: [Explain one important choice and the reason for it.] Where to look: [Point to a specific section, feature, or example that demonstrates the skill.] What this shows—and doesn’t: [State the skill this supports and any relevant limit, such as missing context or a result you cannot attribute to yourself.]
For a short sample, keep each line to a sentence or two. If the evidence is not visible in the artifact, say what additional context the reader needs rather than asking them to take a broad claim on trust.
A practical checklist
State the project’s purpose in language a non-specialist can follow.
Identify your personal contribution separately from team work.
Explain one consequential choice and why it mattered.
Direct the reader to a specific place in the sample as evidence.
Avoid unsupported outcome claims and name important limits.
A few more useful answers
Should I remove technical terms from the sample itself?
Not necessarily. Keep terms needed to represent the work accurately, but define the ones a reader needs to understand your contribution. The guide can translate the key idea without rewriting the artifact.
What if I can’t share the original work sample?
Use a permitted excerpt, a redacted version, or a clearly labeled illustrative summary if appropriate. Explain what the substitute preserves and what it leaves out; don’t present a reconstruction as the original artifact.
How can I tell whether my explanation is clear?
Ask a reader unfamiliar with the project to tell you what the challenge was, what you did, and where the evidence appears. If they cannot find those answers, revise the framing rather than adding more specialist detail.