Narrowing and Scoping a Research Topic
A topic has to sit inside a band: tight enough to be interesting, loose enough that a literature exists. This page covers the mechanics of finding that band — the list-and-cluster sequence, and the title that has to declare its own limits.
The band a topic has to sit inside
Both halves of that sentence are load-bearing, and they fail in different directions. Too broad and there is no question, only a subject area — the work becomes a summary of what is already known. Too narrow and there is nothing written about it, which the source treats elsewhere as grounds for being advised off the topic altogether.
The third sentence is the one most often skipped. Meeting the requirements of what your final project should look like is a scoping constraint, not administrative housekeeping: the required length, structure and evidence base of the final artefact set an upper and lower bound on the topic before you have chosen one.
Well begun is half done
Too big at first, and how it shows
The source names the failure in a parenthesis, which understates it. Among the questions it puts to a researcher settling a topic is: what should I include and, more importantly, exclude — what are my boundaries — with the note that many people take on too big a project at first.
That ordering is deliberate. Exclusion is the harder decision and the one that actually creates the scope, in the same way that a delivery scope statement is defined by what it rules out.
There is a practical reason this failure is so common among practitioners. Delivery experience gives you a wide view of a domain and a genuine interest in most of it, and the instinct to cover the ground is exactly the instinct that has to be resisted at this step.
The list, cluster, title sequence
The source's method is short and it is the only narrowing procedure it supplies. It begins with brainstorming — you may employ one of the many mind maps available, it suggests — and then moves through three distinct operations.
- List aspects
- List elements
- Cluster into categories
- Choose the aspect
- Write the title
The sequence as the source sets it out
List all possible aspects of the topic
Everything that could count as part of the topic of interest to you. This is deliberately expansive — you cannot narrow a field you have not seen the edges of, and an aspect you never wrote down is one you will keep half-considering.
List as many elements as you can in each aspect
The second pass gives the first one texture. An aspect with two elements under it is usually a heading you have not thought about; an aspect with a dozen is where your actual interest is sitting.
Cluster the elements into categories
Group what belongs together, across aspects as well as within them. Clustering is where you discover that half your elements are really one concern under several names.
Determine the aspect that is of most interest to you
Choose one. The source is unambiguous that the choice is yours to make and that your own interest is the criterion — a topic that does not interest you, it says elsewhere, will be a real slog.
Select a title
Write a title that focuses the nature of your topic and illustrates its boundaries, includes your main interest, and — if you can manage it — is catchy.
Check availability and doability
Ensure relevant material is available and the topic is doable. This is the point at which the narrow-versus-broad constraint is tested rather than assumed.
Writing a title that states its own boundaries
The source treats the title as a working instrument rather than a label to be added at the end, and it asks four things of it.
- It focuses the nature of the topic
- It illustrates the boundaries of the topic
- It includes your main interest
- It is catchy, if possible
The second requirement is the demanding one. A title that illustrates its boundaries tells a reader what is excluded without listing exclusions, which means the words have to do double duty: naming the subject and fencing it at the same time.
SUBJECT AREAS AND SCOPED TOPICS, CONSTRUCTED FOR ILLUSTRATION
| Stated as a subject area | What is unbounded | Boundaries a scoped version could carry |
|---|---|---|
| Risk management in projects | Population, setting, period and outcome are all open | Which practitioners, in which sector, at which phase, judged against what |
| Communication in project teams | No outcome named, so no result would count as an answer | Which communication, between whom, affecting which measurable thing |
| Stakeholder engagement | A domain, not a claim; every article looks relevant | Which stakeholders, on what kind of project, over which stage of the lifecycle |
| Why projects fail | Population and outcome both unbounded, and the framing presumes its own answer | A defined failure type, a defined project population, a defined period |
The left column is constructed for this page and is not drawn from the source. The source supplies a list of broad project management themes, which sit at this level of generality by design and are intended as starting points rather than topics.
Those broad themes — leadership and soft skills, stakeholder management, risk management practices, project costing and estimating, and a dozen more — are given in the source as a starting shortlist, and it says plainly that the list is not exclusive. See Research Themes in Project Management. A theme is where narrowing starts, not where it finishes.
In scope and out of scope, written down
The exclusion decision the source asks for is easier to make on paper than in conversation. A short two-column statement, drafted at the point of clustering, is enough — and its real value is that it can be shown to a supervisor, who can then disagree with something specific.
Decisions that fix the scope in
- The population you will actually collect from
- The setting or sector you will draw it from
- The period or project phase you will cover
- The outcome or effect you are examining
- The literature you are positioning against
Decisions that fence the scope out
- Adjacent populations you will not approach, and why
- Comparisons you will not attempt
- Causal claims you will not make
- Time periods your data does not cover
- Questions a reader will expect and you are not answering
The right-hand column becomes the limitations section of the final document almost verbatim. Written at the start it is scope; written at the end it is apology, and reads that way.
Letting the literature do the narrowing
The most reliable narrowing instrument is not a mind map. It is the literature, because it supplies the one signal the source's own criterion needs and does not provide: whether adequate information exists on the topic as you have currently framed it.
The published volume of master's project management research shows the pattern in use. One chapter, on integrating younger practitioners into the profession, describes its literature review as the means by which the scope was narrowed into aims and objectives — the review preceding the primary collection and determining what the primary collection would be for.
The volume's chapter structure repeats that ordering: an opening problem statement, what the literature contends, the scope of the research narrowed by the literature review into aims and objectives, then the purpose of the paper and how primary data will be sourced. Narrowing sits between the problem and the design, and it is done with reading.
The source frames the same relationship from the other direction, noting that a literature review is often conducted in a subject area before a research question is identified, and that the gaps a researcher identifies will probably generate a more focused question. The mechanics of that reading are covered in Step 3: Checking the Literature.
Flexible, without drifting
The source closes its sequence with an instruction that sits oddly beside all the fixing of boundaries: be flexible about your topic, as it will evolve as you discover more. It says the same thing about the process generally — the steps should be viewed as an ever-changing process rather than a fixed set, and research questions evolve over time as you gather evidence and refine your focus.
Both statements are true and neither licenses drift. The distinction worth holding is between evolution driven by what you find and drift driven by what you did not plan.
EVOLUTION AND DRIFT
| Legitimate evolution | Drift |
|---|---|
| The literature shows the question has already been answered, so you refine it | A new interesting article appears and the topic quietly widens to include it |
| Access to the intended population fails, so the setting changes and the design is revised with it | An easier population becomes available and is added without changing the claim |
| Early data shows the effect you are studying is not where you expected, so the focus moves | The finding is weak, so the topic broadens until something significant appears |
| The scope is cut because the timeframe will not carry it | The scope grows because the work so far feels too small |
The distinction is a synthesis. The source instructs you to stay flexible and does not distinguish between kinds of change.
The operational test is whether the change is recorded. An evolution you can date, explain and defend in the methodology is a research decision. The same change made silently is drift, and it usually surfaces as a mismatch between the title and the findings.
Knowing when to stop narrowing
Signals the topic is scoped
- You can state it in one sentence without using "and also"
- The title names at least two of population, setting, period and outcome
- You can name what you are deliberately excluding, and say why
- You can point to published work on the topic as framed — not on the general subject area
- You can say what result would count as an answer, including a result you would not like
- It still interests you enough to spend a year on it
- It fits the requirements of what the final project has to look like
Scoping settles what the study is about. It does not settle whether the study is worth doing — whether the questions are worth asking, in whose interest they are asked, and how the findings might be used. Those tests are a separate step, covered in Step 2: Reviewing and Testing Your Research Topic, and they run alongside the practical tests in Assessing Research Topic Feasibility.
A scoped topic is still not a question. Turning it into one — stated in a single sentence, with an aim attached — is the next operation, in Step 4: Deciding Your Research Question. If you have not yet settled on a topic at all, start at Step 1: Generating and Refining a Research Idea.
What to carry forward
- The band is fixed at both ends: narrow enough to be interesting, broad enough to find adequate information.
- The dominant failure is taking on too big a project at first, and exclusion is what fixes it.
- List aspects, list elements, cluster into categories, choose the aspect, then write the title.
- The title must focus the topic and illustrate its boundaries — it is an instrument, not a label.
- Write the in-scope and out-of-scope lists early; the second becomes your limitations section.
- The literature is the only narrowing instrument that gives you a countable signal about adequacy.
- Stay flexible, but record every change. An undocumented change of scope is drift, not evolution.
Frequently asked questions
How narrow is narrow enough?
The source sets the criterion — narrow and focused enough to be interesting, broad enough to find adequate information — and gives no test for either end. The workable proxy is the literature: if searching the topic as framed returns nothing, it is too narrow, and if everything looks relevant, it is still a subject area rather than a topic.
What is the list-and-cluster sequence?
List all possible aspects of the topic that interest you, then list as many elements as you can under each aspect. Cluster those elements into categories, determine which aspect interests you most, and select a title that focuses the topic and illustrates its boundaries. Then check that relevant material is available and the topic is doable.
Does the source tell me how to use a mind map?
No. It suggests beginning with brainstorming and says you may employ one of the many mind maps available on the website, but the referenced materials are not part of the supplied dataset. Nothing about mind mapping technique can be asserted on the source's authority.
Should the title be finalised before the research starts?
It should be written early, because the source treats it as the instrument that fixes the boundaries. It should not be treated as final: the same source instructs you to stay flexible because the topic will evolve as you discover more. What matters is that a change to the title is a recorded decision rather than a silent one.
How is this different from testing whether the topic is any good?
Narrowing is a mechanical operation about size and boundaries. Testing asks whether the questions are worth asking, whether they have already been answered, in whose interest they are asked, and how the findings could be used or interpreted by others. Those questions belong to the review step and are covered on a separate page.
References and source attribution
- Naoum, S. G. 2013, Dissertation Research & Writing for Construction Students, 3rd ed., Routledge — cited in the supplied source as the reading on topic selection.
- O'Leary, Z. 2017, The Essential Guide to Doing Your Research Project, 3rd ed., Sage Publications, London.
- Bryman, A. 2016, Social Research Methods, 5th ed., Oxford University Press, Oxford.
- An edited volume of master's degree research projects in project management, 2018, academic publisher, 378 pp. — the exemplar volume, whose chapters narrow scope into aims and objectives by literature review.
- The supplied teaching source: consolidated week 3 teaching notes and slide material on developing a research topic, used here as the basis for all statements attributed to "the source".
Suggested questions for Ask KEVOS
- My topic is too broad — help me run the list, cluster and title sequence on it.
- Rewrite my research title so it states its own boundaries.
- Draft an in-scope and out-of-scope statement for a study of project team communication.
- Is my topic too narrow if I can only find three relevant papers?
- Which of my recent scope changes are legitimate evolution and which are drift?