Academic writing

Why Your Research Questions Sound Generic (And the One Shift That Fixes It)

A research question isn't 'what I don't know yet.' It's 'what I think I know that no one else has tested here.' The first is curiosity. The second is contribution.

You've rewritten your research question four times tonight. "Investigate" became "examine." "Examine" became "explore." "The impact of" became "the influence of." You feel like progress is being made. Your advisor reads it at 9 a.m. and types three words back: still too broad. You stare at your screen and don't know what she means. You changed five words and two prepositions. Here's the thing nobody drills into you during that one-methodology-lecture you skipped: the problem was never the verb. Your question isn't "too broad" in the way that adding a time-frame or a population would fix it. It's broad because you never actually committed to a position. You wrote a question that any second-year student could answer from common sense. That's not a research question. That's a multiple-choice question on a midterm you've already studied for.

Here's the uncomfortable truth that most writing centers won't say to your face: ninety percent of undergraduate research questions are the same sentence with different nouns swapped in. "How does [X] affect [Y] among [Z]?" or "To what extent does [X] influence [Y]?" That's the entire formula. I've seen it in sociology, public health, education, business, psychology. A professor who has marked two hundred proposals this decade can complete your sentence before you finish the first clause. You're not asking a question. You're filling in a worksheet. And the reason it feels safe is that it's unfalsifiable—you can always retreat to "well, it depends on the context." But "it depends" isn't a finding. It's a cop-out wearing an academic blazer. When your advisor says "too broad," translate that: "I could have written this sentence in my sleep. What makes this yours?"

The difference between a generic question and a sharp one has nothing to do with vocabulary. It's about whether you've already made a judgment call. A generic question asks what you don't know. A sharp question asks what you think you know but haven't proven yet. See the difference? The first one is a survey. The second one is a test. When you write "How does X affect Y?" you're inviting your reader to assume the answer could go in any direction. You haven't committed. You haven't risked being wrong. And a question where you haven't risked being wrong is a question where you haven't done the thinking yet. The thinking that actually drives a proposal isn't "what's interesting?" It's "what do I suspect, and what would it take to prove me wrong?" Translate that suspicion into a question and your research question finally has a spine.

Let me show you what I mean with actual rewrites. Three pairs. ❌ "How does social media use affect the academic performance of university students?" ✅ "To what extent does algorithmic content curation on Instagram correlate with self-reported attention fragmentation among first-year undergraduates at UK Russell Group universities?" The first can be answered by any second-year literature review. The second forces you to choose a platform, a measurement instrument, a population, and an institutional context. You can't hide behind "generally speaking." ❌ "This study aims to examine the impact of remote learning on student engagement." ✅ "How do asynchronous discussion forums in hybrid lecture formats reshape the distribution of classroom participation among non-native English-speaking undergraduates?" Notice the second question has an answer that could be wrong. That's the whole point. If your question can't be falsified by data, it isn't a research question. ❌ "This paper will explore the challenges faced by international students in the UK." ✅ "How do differences in formative feedback frequency between Chinese and UK undergraduate programmes predict time-to-first-submission for first-year international students in essay-based modules?" "Challenges faced by" is universal filler. "Predict time-to-first-submission" is a specific, testable claim someone can disagree with.

Three checks I run before a research question leaves my desk. First: read it aloud to a non-academic friend. If they can answer it from common sense in under thirty seconds—"oh, social media makes you less focused, right?"—your question is a trivia card, not a research question. Second: ask yourself "what makes me positioned to answer this?" If your honest answer is "I'll read a bunch of papers," congratulations, you're writing a review, not designing a study. A real research question implies a method. If you can't name the method in one sentence, your question is too vague to be worth answering. Third: flip your question into a declarative statement. If it reads like "This paper will discuss the relationship between..." you haven't written a question. You've written your abstract's first sentence. Submitting your abstract's opening line as your research question is the academic equivalent of bringing the menu to the table and calling it dinner.

My actual workflow is unglamorous and I'm not going to dress it up. I write the question first—ugly, over-qualified, full of "this study aims to"—and then I run it through easydue just to see where it flags redundant hedging or generic scope markers. It won't think for you. It won't tell you what to study. But it will tell you exactly where you're padding, where your scope is so wide it might as well be a Wikipedia lead paragraph. And that's the whole game. The time you save from not manually cross-referencing every hedging phrase isn't spent making the sentence prettier. It's spent reading one more paper that actually narrows your gap. One more paper is the distance between "I have a topic" and "I have a question." Don't spend your hours swapping synonyms. Spend them making the question smaller.

One last thing, and I need you to actually hear this. A research question is not "what I don't know yet." That's curiosity, and curiosity is free. Everyone's got it. It costs nothing and proves nothing. A research question is "what I think I know that no one else has tested in this specific context." That's contribution. The bar for an undergraduate proposal is not that you change the field. It's that you prove you thought one step further than the person sitting next to you in the same lecture hall. If your question could have been written by any student in your cohort without opening a single paper, you haven't done the work yet. The question is where the work starts. Not the topic. Not the title. The question.