Present research by naming the question, your contribution to the method and the finding supported by the evidence. Distinguish an observation from an interpretation or recommendation. State the main limitation when it affects meaning, and preserve the difference between exploratory work, reviewed findings and decisions made by others.
Identify the question and your research role
Research evidence is easier to assess when the reader knows what the work tried to establish. Begin with a question narrow enough to match the project: how participants interpreted a form, which themes appeared in a set of interviews or how two datasets differed. Avoid replacing that question with a sweeping claim about customer behavior or an entire population.
Define your own role in the work. Designing a study, recruiting participants, conducting interviews, cleaning data, coding responses and preparing a report are distinct contributions. A student or assistant can demonstrate careful research practice through a bounded task. You do not need to claim ownership of the study design or the final recommendation if a supervisor held those responsibilities.
Keep methods, findings and interpretations separate
A method explains how evidence was collected or examined. A finding describes what appeared in that evidence. An interpretation explains what you think it may mean, while a recommendation proposes an action. Draft these as separate notes before compressing them into a CV entry. This prevents the recommendation from being presented as a proven consequence of the research.
Check the language against the study’s reach. A small convenience sample can reveal experiences worth investigating without establishing how common they are. A correlation does not alone show causation. An absence of evidence in the reviewed material does not prove a problem never occurs. You can explain these limits in plain language without turning a career document into a methods textbook.
Choose a claim that can survive discussion
A useful bullet may describe a reviewed research output: a thematic summary, an annotated dataset or a report of observed usability issues. If the organization later made a decision, distinguish your research contribution from the decision itself. “Prepared interview themes used in a design review” is different from “proved the redesign would increase engagement.” The former can be meaningful without borrowing certainty from a hoped-for outcome.
In a portfolio, describe recruitment, exclusions and missing information where those affect interpretation. Explain why you chose an approach and what an alternative might have revealed. Do not publish participant details, raw responses or sensitive data unless sharing is authorized. A fictional excerpt or a diagram of the analysis process can demonstrate reasoning without exposing the original material.
Prepare to discuss what you would investigate next. A research project can be valuable because it narrowed a question or identified uncertainty. That is a stronger account than claiming a universal answer from limited evidence. Before publishing, review every causal verb and absolute term. Words such as demonstrates, suggests and observed have different implications; select the one that matches what the work actually supports.
Fictional example: interpreting feedback on a booking form
A fictional research assistant helps with six exploratory interviews about a booking form. They organize notes using an agreed coding guide and identify repeated confusion about one field label. The sample consists of available volunteers, so it does not represent all users. A supervisor reviews the themes and recommends further testing of revised wording. The assistant did not design a population survey or measure booking completion.
The CV says: “Coded exploratory interview notes using an agreed guide and prepared a reviewed summary of recurring booking-form questions.” A portfolio note explains the recruitment limitation and distinguishes observed confusion from a prediction about future completion rates. The candidate shows a fictional coded excerpt and a next-step question for testing. The example demonstrates disciplined synthesis without implying statistical representativeness or a proven commercial effect.
A checklist for your next step
- Name the research question and your own task.
- Separate method, observation and interpretation.
- Check that population claims fit the sample.
- Distinguish recommendations from measured outcomes.
- Explain the limitation that most affects meaning.
Common questions
Must a short CV bullet include every limitation?
No, but it must not create a misleading impression. Include a key qualifier such as exploratory where needed, and keep a fuller account of methods and limitations ready for discussion.
Can I describe unpublished research?
Often you can describe your role at an appropriate level, but check permissions and confidentiality first. Do not imply peer review, public availability or institutional approval that the work did not receive.
Further reading
These primary resources provide related background. They do not validate the illustrative example or endorse AliveCV.
AI-assisted drafting and automated technical checks. Examples are illustrative; no independent expert review or real-world outcome validation is claimed. Read our editorial policy.