Start where the listener can enter
Imagine a project comparing two survey formats. Opening with the name of a statistical procedure may leave the listener unsure what problem the study addressed. “We wanted to know whether the format changed who completed the survey” gives the method a purpose.
The next sentence can identify the approach. A later sentence can describe the result and its boundary. This order makes technical detail easier to understand without removing it.
Four pieces to prepare
- The question: what was being investigated?
- The approach: why was this design or method used?
- The contribution: what work did you personally perform?
- The limitation: what could the project not establish?
Cornell's academic-statement guidance emphasizes preparation and academic interests. Those same distinctions can help organize an explanation, although a written-statement guide does not predict an interview committee's questions.
When a question exceeds your knowledge
It is possible to say, “I did not handle that part of the analysis; my role was…” and then explain the relevant contribution. NISO's research-contribution taxonomy illustrates why a team project can involve distinct kinds of work.
A limitation is not a required confession that the project failed. It is a statement about what the methods and evidence support.
Practice for interruption
A useful practice conversation allows follow-up questions before the prepared explanation ends. If the listener asks about the comparison group, that is an opportunity to clarify the design rather than a reason to rush back to the script.
The aim is to make the work understandable and discussable. A compact, accurate explanation gives the interviewer something substantive to ask about without requiring a performance of certainty about every part of the field.
