Reading and Presenting Research Papers

$$\huge\textbf{Reading and Presenting Research Papers} $$

1. Reading Papers

When you read a research paper, your goal is to understand the scientific contributions the authors are making. This is not an easy task. It may require going over the paper several times. Expect to spend several hours to read a paper. Here are some initial guidelines for how to read a paper:

Read critically: Reading a research paper must be a critical process. You should not assume that the authors are always correct. Instead, be suspicious. Critical reading involves asking appropriate questions.

  • If the authors attempt to solve a problem, are they solving the right problem?
  • Are there simple solutions the authors do not seem to have considered?
  • What are the limitations of the solution (including limitations the authors might not have noticed or clearly admitted)?
  • Are the assumptions the authors make reasonable?
  • Is the logic of the paper clear and justifiable, given the assumptions, or is there a flaw in the reasoning?
  • If the authors present data, did they gather the right data to substantiate their argument, and did they appear to gather it in the correct manner?
  • Did they interpret the data in a reasonable manner? Would other data be more compelling?

Read creatively: Reading a paper critically is easy, in that it is always easier to tear something down than to build it up. Reading creatively involves harder, more positive thinking.

  • What are the good ideas in this paper?
  • Do these ideas have other applications or extensions that the authors might not have thought of? Can they be generalized further?
  • Are there possible improvements that might make important practical differences?
  • If you were going to start doing research from this paper, what would be the next thing you would do?

Make notes as you read the paper: Many people cover the margins of their copies of papers with notes.

  • If you have questions or criticisms, write them down so you do not forget them.
  • Underline key points the authors make. Mark the data that is most important or that appears questionable.

Such efforts help the first time you read a paper and pay big dividends when you have to re-read a paper after several months.


Summarize the paper in one or two sentences. Almost all good research papers try to provide an answer a specific question. (Sometimes the question is a natural one that people specifically set out to answer; sometimes a good idea just ends up answering a worthwhile question.)

  • If you can succinctly describe a paper, you have probably recognized the question the authors started with with and the answer they provide.
  • Once you have focused on the main idea, you can go back and try to outline the paper to gain insight into more specific details.

Indeed, if summarizing the paper in one or two sentences is easy, go back and try to deepen your outline by summarizing the three or four most important subpoints of the main idea.


Compare the paper to other works. Summarizing the paper is one way to try to determine the scientific contribution of a paper. But to really gauge the scientific merit, you must compare the paper to other works in the area.

  • Are the ideas really novel, or have they appeared before? (Of course you might not be experts and know the areas ahead of time)

It is worth mentioning that scientific contributions can take on many forms. Some papers offer new ideas; others implement ideas, and show how they work; others bring previous ideas together and unite them under a novel framework. Knowing other work in the area can help you to determine which sort of contribution a paper is actually making.

2. Presenting Papers

In contrast toa paper or other technical writing, you present your work and vourself. People remember good presentations:

  • Good content
  • Well presented
  • Well-designed slides

Many of my colleagues and I[1] put a lot of effort into each presentation, and at the beginning of a career it’s even more important.


  1. Markus Püschel, How to give strong technical presentations ↩︎