I once reviewed a dissertation proposal with forty-one variables in the conceptual model. Forty-one. The diagram, when printed, needed to be turned sideways and still ran off the edge of the page, a dense thicket of arrows connecting constructs that the student, when I asked, could not fully explain the theoretical relationship between. When I asked why a particular mediating variable was in the model at all, the answer was some version of "the dataset had it, and it seemed relevant." Not "the theory predicts it matters." Not "prior literature suggests this relationship." The dataset had it. That was the whole justification.

That proposal is not an outlier. It is, if anything, the increasingly normal shape of graduate research in an era where data collection has become nearly frictionless and computing power has made it trivial to run a regression with fifty controls instead of five. And it points to a paradox that deserves far more honest discussion in academia than it currently gets: past a certain point, more data does not produce more understanding. It produces more noise, dressed up convincingly as rigor.

The superstition of more

Somewhere in the culture of modern academia, a quiet and mostly unexamined belief took hold: that a heavier methodology section, a longer bibliography, and a larger dataset are inherently signals of a better study. This belief is understandable, it maps onto a certain intuitive idea of effort, and effort feels like it should correlate with quality. It is also, in a significant number of cases, backward.

A large dataset with forty-one variables and a weak theoretical spine is not a rigorous study. It's a fishing expedition with excellent production values. The sheer volume of data creates an illusion of thoroughness that can mask the much more important, much harder question a researcher is supposed to be answering first: what, specifically, am I trying to understand, and what is the minimum set of well-justified variables that would let me understand it clearly? Piling on additional constructs because the survey instrument happened to measure them, or because a public dataset included the column, is not extra rigor. It's a substitute for the theoretical thinking that should have determined the model's shape before a single data point was collected.

I've come to think of this as data collection functioning as an avoidance mechanism. Building a genuinely tight, well-justified theoretical framework is hard, uncomfortable, intellectually exposing work, you have to commit to a specific claim about how the world works and defend why you believe it, with the ever-present risk that a committee member or reviewer will find the gap in your logic. Collecting more variables, by contrast, feels productive without requiring that same commitment. It's much easier to add a control variable "just in case" than to sit with the harder question of why your core relationship should hold at all. An avalanche of secondary metrics can bury a genuinely weak theoretical framework so effectively that nobody, including the researcher, notices how thin the actual argument underneath it is.

The fishing expedition nobody names out loud

Here's the part of the process that rarely gets described honestly in methods sections, though almost every working researcher has lived through it: the data analysis session where nothing is significant, panic sets in, and the model starts getting quietly reshaped until something is.

A variable gets dropped because it wasn't behaving. A different specification gets tried because a colleague mentioned it "sometimes helps." An interaction term gets added, not because theory predicted an interaction, but because the main effects weren't cooperating and an interaction might. Three hours and eleven model specifications later, something crosses the threshold of statistical significance, and that becomes the "finding," not because it was the relationship the researcher set out, with theoretical justification, to test, but because it was the relationship that happened to survive the search.

"A result mined from eleven specifications is not evidence about the world. It's evidence about how many specifications were tried before something looked publishable."

This is not fraud, in the vast majority of cases. It's an understandable, deeply human response to pressure, operating inside a research culture that rewards significant findings and rarely rewards the harder, more honest alternative: reporting that the well-justified hypothesis simply didn't hold. But the practice has a name in methodology circles, data dredging, or the garden of forking paths, and it is one of the primary, quiet engines behind the replication crisis that has embarrassed entire fields.

Contrast that entire panicked process with what a genuinely well-designed, parsimonious study looks like. A handful of carefully chosen variables, each with a clear theoretical reason for being in the model, tested against a clean, specific, falsifiable hypothesis. The result, whatever it turns out to be, means something, because there was no garden of forking paths to get lost in, there was one path, chosen in advance, walked honestly to its end. That kind of study is often less impressive-looking on paper. It has fewer tables. It has a shorter methods section. It is also, far more often, actually true.

The case for methodological minimalism

None of this is an argument against rich, well-collected data, or against the genuine value of large samples when a research question calls for them. It's an argument against volume as a substitute for judgment. The discipline that separates a strong study from a bloated one isn't how much data was gathered, it's how disciplined the researcher was in deciding what belonged in the model before ever running it, and how honest they were about reporting what they found, including the parts that complicated the story.

Practically, this means treating every variable in a model as something that has to earn its place through theoretical justification, not through availability. It means writing the analysis plan, including which variables will be included and why, before looking at the data, a habit borrowed from pre-registration practices in more rigorous corners of psychology and medicine, and one that any researcher, at any level, can adopt without needing a formal pre-registration process. It means being willing to report a null result cleanly rather than expanding the model until something, anything, clears a significance threshold. And it means recognizing that a shorter, tighter methods section is not a weaker one. Often it's the opposite: it's the sign of a researcher who did the hard theoretical work up front, instead of outsourcing that work to a spreadsheet full of variables collected because they were there.

Clarity is the actual metric

The best studies I've ever reviewed, across every field I've worked in, share a quality that has nothing to do with their sample size or their variable count: I finish reading them and understand, with total clarity, exactly what was tested, why it mattered, and what the honest result actually was. That clarity is not incidental to good research. It is the entire measure of it.

A dissertation chapter with forty-one variables and no clear theoretical throughline is not more rigorous than one with five variables and an airtight argument for each of them. It's more crowded, which is a different thing entirely, and often the opposite of impressive once anyone looks closely enough to notice.

"The best research is defined as much by the deliberate discipline of what a researcher chose to leave out as by what they chose to include."

And in a culture still quietly convinced that more data always means more truth, that discipline may be the most undervalued skill in academia today.

Not sure your model is disciplined, or just crowded?

We help researchers pressure-test a conceptual model before data collection, and tighten one that's already sprawling, so every variable in it earns its place.

See research & data analysis services →