How Research Works

Most people’s first serious encounter with a research paper goes one of two ways. Either it reads like a wall of hedged, citation-studded prose that seems built to keep outsiders out, or it reaches them secondhand, in a headline that says something the paper never actually claimed. A study of forty undergraduates becomes “scientists prove,” a p-value of 0.04 becomes “a breakthrough,” and a cautious line from the discussion section becomes the finding. Without a mental model of how a paper is built and what its numbers can and cannot support, these moments are hard to judge, and it is hard to know which claim to trust or how to check the next one.

This course gives you that model, and it is deliberately not a statistics textbook or a style guide for academic writing. It is the foundation of Nishan’s research training, the course we recommend before you write your first paper with us. It follows the life of a real study from the outside in: first reading and judging the research that already exists, then designing a study of your own, then handling its evidence honestly, and finally writing it up so someone else can trust and reproduce it. Every idea is tied to a real, cited example, and most are paired with something you build or take apart yourself rather than only read about.

The material is organized into four units, each a stage in how research actually works. Reading teaches you to take a paper apart: separate what the authors observed from what they claim it means, trace a finding through its citations, and catch the truncated axis or the bar of averages that flatters a figure. Designing moves you to the other side of the page, turning a vague curiosity into a question you can test, choosing a study design that can answer it, and pinning abstract ideas down into measurements. Evidence is where honesty meets uncertainty: what a p-value and a confidence interval really say, when a cleaning decision becomes a bias, and whether a result would survive an independent replication. Producing closes the loop, from writing methods a stranger could rerun to citing only sources you have verified and disclosing where you used AI. Each unit pairs a short explanation with a hands-on interactive, so you dissect a real claim, build a causal diagram, or run a simulation of the forking-paths problem, and feel where the edges are instead of only reading about them.

The last unit, and the capstone that follows it, look at what happens when these stages collide, because in real research they always do. One flawed paper can measure the wrong thing, oversell a weak result, and report only the analysis that worked, all at once. The capstone puts that to the test: you appraise a paper you have not seen before and write a one-page research proposal of your own, built from the pieces you have been saving since the Designing unit. The habit the whole course trains is a kind of diagnostic. When a claim feels off, you learn to name which stage is failing, whether the design cannot support the conclusion, the measure does not capture the construct, the statistics are oversold, or the reporting is selective, and to apply the specific check that stage calls for rather than a vague sense of doubt.