← Back to Blog
final year project

How to Write Strong Research Questions and Objectives for Your Project

A broad topic being refined step by step into a specific, testable research question

A useful research question identifies what you want to understand and the evidence that could answer it. For a quantitative study, name the population, variables and boundaries. Qualitative, textual and design projects may instead define a phenomenon, material or design problem; objectives should fit that approach.

Clear objectives should remain consistent across your proposal, method and final discussion. UniDraft helps organise the question, scope and instructions you confirm into an editable project document. Start your project document, then review that alignment yourself. See the project workflow; topic or methods approval stays with the responsible academic staff.

The short answer

  • Aim: the one overall purpose of your study.
  • Research question: what you ask to reach that aim. It must be answerable with data you can realistically collect.
  • Objectives: the specific steps that answer the question. Each starts with a measurable verb, and each has a matching result in Chapter 4.
  • Specific means three things: a defined population, a defined variable or relationship, and a boundary in place or time.
  • The test: could a stranger tell exactly what would count as answering it? If not, narrow again.

How the aim, questions and objectives fit together

Students often treat these as three separate boxes to fill in Chapter 1. They are one thread. The aim says what the study is for. The questions turn the aim into something you can investigate. The objectives turn the questions into work.

Here is an illustrative example. The wording is invented for teaching and is not from a real project.

  • Topic: Mobile banking among university students.
  • Aim: To assess how far university students in Lagos use mobile banking and what shapes that use.
  • Research question: Is there a relationship between trust in fintech platforms and how often students use mobile banking?
  • Objectives: (1) To determine the frequency of mobile banking use among students; (2) To measure students' level of trust in fintech platforms; (3) To examine the relationship between trust and frequency of use.

Notice that every objective is something a reader can look for in your results. Objective 1 gives you a frequency table. Objective 2 gives you a trust score. Objective 3 gives you a correlation. Chapter 4 practically writes its own headings from these three lines, and if you are already there, see how to write the results chapter.

Your department may use different vocabulary. Some want "aim and objectives" only, some want "research questions" only, and many want aim, objectives, questions and hypotheses. Follow your department's project guideline, and if it is silent, ask your supervisor which set they expect. That is a formatting-and-convention decision your supervisor controls, not something you should guess.

The four main types of research questions

  1. Descriptive -- what is the current state of X? ("What is the current level of mobile banking adoption among university students in Lagos?")
  2. Comparative -- how does X differ between groups or conditions? ("How does mobile banking adoption differ between urban and rural university students?")
  3. Relational/correlational -- is there a relationship between X and Y? ("Is there a relationship between trust in fintech platforms and adoption frequency?")
  4. Causal/experimental -- does X cause a change in Y? ("Does exposure to a financial literacy programme increase mobile banking adoption?")

Identifying which type you are actually asking clarifies your methodology. A causal question needs an experimental or quasi-experimental design. A descriptive one might only need a well-designed survey, and you can start on that with how to design a questionnaire for your final year project. A relational question leads you toward correlation or regression.

The mistake to watch for: a causal question with a survey design

The most common mismatch we see described is a student who asks "Does X improve Y?" but only collects one round of opinions through a questionnaire. A single survey can show that two things go together. It cannot show that one caused the other. A before-and-after comparison alone does not remove confounding or prove causation. If your design cannot support a causal claim, rewrite the question as relational ("Is there a relationship between X and Y?"), pick the test with which statistical test fits your project, and be honest about that limit in your discussion.

Which type suits which kind of project

Project kind Usual question type Example objective
Software or system build Descriptive or comparative To compare response time of the new system with the manual process
Engineering design and test Comparative or causal To determine the effect of curing time on compressive strength of concrete
Survey in management or social sciences Descriptive or relational To examine the relationship between staff motivation and productivity
Education intervention Causal or comparative To determine the effect of a mobile learning tool on quiz scores
Health or nursing study Descriptive or relational To assess knowledge of hand hygiene among nursing students

Treat this as a guide, not a rule. Departments differ, and your supervisor's expectations decide what is acceptable in your case.

Turning a broad topic into a specific question

A broad topic is missing three things: a specific population, a specific variable or relationship, and a boundary (where or when). Compare:

Broad topic: "Technology in education."

Specific question: "Does the use of a specific mobile learning tool improve quiz scores among 100 secondary school students in Lagos State over one academic term?"

The specific version names the population (secondary school students in Lagos State), the variable (a specific tool's effect on quiz scores), and the boundary (one academic term).

A five-step narrowing routine

  1. Write the topic in a phrase. "Technology in education."
  2. Pick a population you can reach. Not "Nigerian students". Reach means you can get a list, permission, or access. A class, a department, a school, a hospital ward.
  3. Pick one variable or relationship. One thing to measure or compare, not five.
  4. Set a boundary. A place, a period, or a system version.
  5. Choose the question type from the four above and phrase it accordingly.

If you are still stuck at step 1, the free topic generator gives you ideas by department, and our framework for choosing a topic shows how to check that a topic is doable before you build a question on it.

Before and after: three weak questions, rewritten

These are illustrative rewrites, not real projects.

Weak: "What is the impact of social media on students?" Problem: No population, no defined impact, no boundary. "Impact" could mean grades, sleep, mood or spending. Stronger: "Is there a relationship between daily time spent on WhatsApp and CGPA among 300-level students in one faculty?"

Weak: "To study the problems of small businesses in Nigeria." Problem: "Study" is not measurable, "problems" is unlimited, and "Nigeria" is too wide to sample. Stronger: "To identify the three most frequently reported financing challenges among registered tailoring businesses in one local government area."

Weak: "Does the new system work?" Problem: "Work" is undefined. Works for whom, and measured how? Stronger: "To compare the average time to complete student registration using the developed system against the manual process."

In each stronger version, you can already picture the data you would collect.

Check the question against FINER

Health researchers use a checklist called FINER: a good question is feasible, interesting, novel, ethical and relevant. It fits student work well, and it is described in university library guidance such as the Johns Hopkins Welch Medical Library guide to formulating a research question. Apply it honestly:

  • Feasible: can you get the sample, the equipment, the permission and the time within your project calendar?
  • Interesting: would you and your supervisor be willing to read about it for six months?
  • Novel: does it add a local angle, a new setting or a fresh comparison? A project does not need a world-first finding, but copying last year's title with a new year is not novel.
  • Ethical: if people are involved, do you have consent, and will their answers stay confidential?
  • Relevant: does it matter to your discipline, your industry, or a real problem?

Feasibility deserves the hardest look. Many strong-sounding questions collapse because the sample is unreachable. If you are heading to a survey, how to calculate sample size for a final year project will tell you how many respondents you need before you commit.

A useful frame for quantitative and clinical questions: PICO

If your study compares groups or tests an intervention, PICO is a compact frame: Population, Intervention, Comparison, Outcome. It is widely taught in health research, and the Hong Kong Polytechnic University library guide on PICO explains it clearly. Applied to the education example: population is secondary school students in Lagos State, intervention is the mobile learning tool, comparison is students taught without it, outcome is quiz scores. If you cannot fill one of the four slots, your question is missing something.

Objectives should follow the same pattern

Once your main research question is specific, your objectives (the smaller steps toward answering it) should be equally specific and, ideally, individually testable. A reader should be able to tell, after reading your results, whether each objective was met.

Start each objective with a measurable verb

Educators use Bloom's taxonomy to pick verbs that show what someone will actually do. The University of Illinois Chicago's guide to Bloom's taxonomy of educational objectives lists verbs by level. For a project, borrow the ones you can prove:

Weak verb (hard to prove) Stronger verb (points to a result)
To understand To identify, to describe, to measure
To look into To examine, to compare, to determine
To know To assess, to test, to evaluate
To appreciate To rank, to analyse, to quantify
To design a good system To design and test a system against X criteria

"To understand student attitudes" needs an explicit approach and evidence; it may fit a qualitative study better than a numeric scoring objective. "To measure student attitudes toward X on a five-point scale" can.

Keep each objective to one action

An objective such as "To design, implement and evaluate a hospital management system" may need separate sub-objectives if that makes the deliverables and evaluation clearer. Follow the scope your brief requires. Also avoid "and" chains that hide a second question.

How many objectives?

Confirm the expected number with your supervisor. Scope, design and available evidence matter more than a universal target. Reviewing literature can itself be a substantive objective in an appropriate review project; distinguish that from merely listing administrative tasks.

Write objectives in the order your chapters will answer them

If Objective 1 is descriptive, Objective 2 comparative and Objective 3 relational, then Chapter 4 can follow the same order, and your conclusion in Chapter 5 can answer them one by one. Readers and examiners love this, because they can tick each objective off as they reach it.

Hypotheses, briefly

For quantitative studies, some departments also want hypotheses. A hypothesis is a testable statement that follows from a comparative or relational question. If your question is "Is there a relationship between trust in fintech platforms and adoption frequency?", the null hypothesis is that there is no significant relationship, and the alternative is that there is one. Descriptive questions and most qualitative studies do not need them. If your department requires them, they must line up one-to-one with your relational or comparative objectives.

Where the objectives appear in your document

Your aim, questions and objectives normally sit in Chapter 1, after the problem statement. They should be worded exactly the same wherever they reappear. Read how to write a final year project problem statement first, since the objectives should respond to the gap that statement identifies. At proposal stage they are usually presented in a shorter form, and the same wording should carry into the introduction chapter.

Do not let the wording drift. A common flag from supervisors is an objective that says "to determine the effect of" in Chapter 1, while Chapter 5 concludes something about "the relationship between". Copy-paste the final wording, then update it everywhere if you change it.

Common mistakes supervisors flag

  1. The topic is written as a question. "Banking and technology?" is not a question.
  2. No population or boundary. "Nigerian students" or "businesses in Nigeria" is almost never reachable.
  3. Objectives that cannot be measured. "To understand" and "to appreciate" have no result to point to.
  4. Question type does not match the method. A causal question answered with one questionnaire.
  5. Too many objectives. Eight objectives usually get eight thin answers.
  6. Objectives that describe the process. "To review literature", "to collect data" and "to analyse data" describe every project. They do not describe yours.
  7. Objectives that do not match the results. Your Chapter 4 answers something your Chapter 1 never asked.
  8. Answers hidden in the question. "To prove that mobile banking improves savings" decides the result before you collect data. Ask, do not assume. If your results come out differently, that is still a valid finding. You must report what you found.

Worked example: from topic to finished set

Illustrative, for a Computer Science student. Not a real project.

  1. Topic: "Attendance systems."
  2. Broad idea: "A better way to take attendance."
  3. Narrowed: Population is lecturers and students in one department; variable is time to record attendance and accuracy; boundary is one semester's pilot.
  4. Question type: Comparative.
  5. Aim: To develop and evaluate a web-based attendance system for one department.
  6. Research question: How does a web-based attendance system compare with paper registers in recording time and accuracy in one department?
  7. Objectives: (1) To design and implement a web-based attendance system; (2) To measure the time taken to record attendance using the system and paper registers; (3) To compare recording accuracy between both methods across one semester.

Notice how the design is testable, and how Objectives 2 and 3 tell you what your test and results chapters must contain.

A quick check before finalising

Read your question or objective back and ask: could a stranger tell exactly what would count as answering this? If the answer is unclear, it likely needs one more round of narrowing.

Then run this checklist:

  • The question names a population, a variable or relationship, and a boundary.
  • The question type matches the design you can actually run.
  • Every objective starts with a measurable verb.
  • Each objective does one thing.
  • Every objective has a matching result you can point to in Chapter 4.
  • The number of objectives fits your department's expectation.
  • The same wording appears in the proposal, Chapter 1, Chapter 5 and the abstract.
  • Your supervisor has seen and approved the final wording.

That last item matters more than students expect. A recorded agreement helps establish what was intended; it does not guarantee acceptance or a defence outcome. If you are preparing for that, common project defence questions and how to answer them is worth reading, and your abstract, written last, will restate the same objectives.

This same specificity check applies to your full proposal, too. See how to write a final year project proposal for the surrounding structure.

When your question needs to change

Questions do change. Data sometimes cannot be collected, a hospital refuses access, or your first pilot shows the question was too wide. If that happens:

  1. Tell your supervisor early, with the specific reason and a proposed rewording.
  2. Change the wording everywhere, not only in Chapter 1.
  3. Do not conceal result-driven changes. Preserve the original plan, explain justified amendments and any required permissions, and distinguish exploratory work from what was specified in advance.

For the step after this one, how to write hypotheses for a final year project covers null and alternative wording, examples and how to report the decision.

Where UniDraft fits in

UniDraft builds your project's introduction and objectives around your actual, confirmed topic and scope, and it applies project or supervisor instructions first, then student-confirmed guidelines, department pattern, university baseline and platform defaults. It does not invent results, sources or approvals, so your objectives stay consistent with what your methodology and results chapters can actually support. If your supervisor asks for changes to your objectives, you can supply the corrections, confirm the changes, and a new version is produced while earlier versions are kept, with the current correction allowance shown in the workflow. It cannot decide your topic for you or guarantee approval; those remain your supervisor's call.

The free topic generator and citation finder need no signup, and the format guides show your university's expectations.

Start your document →

Sources

Frequently asked questions

What are the four main types of research questions?

Descriptive (what is the current state of X?), comparative (how does X differ between groups or conditions?), relational/correlational (is there a relationship between X and Y?), and causal/experimental (does X cause a change in Y?). Most project objectives fit one of these four patterns, and identifying which one you're asking clarifies your methodology.

Can you give examples of good research questions?

Descriptive: 'What is the current level of mobile banking adoption among university students in Lagos?' Comparative: 'How does mobile banking adoption differ between urban and rural university students?' Relational: 'Is there a relationship between trust in fintech platforms and adoption frequency?' Causal: 'Does exposure to a financial literacy programme increase mobile banking adoption?' Each is specific enough to point to a clear methodology.

How do I turn a broad topic into a specific research question?

Add three things your broad topic is missing: a specific population (who, exactly), a specific variable or relationship (what, exactly, are you measuring or comparing), and a boundary (where or when). 'Technology in education' becomes specific once you add a population, a variable, and a boundary -- e.g. 'the effect of X tool on Y outcome among Z students in [location/timeframe].'

How many objectives should a final year project have?

Follow the number and scope required by your brief and supervisor. No universal minimum or maximum is established here. Each objective should have a clear purpose and be answerable through your design.

What is the difference between an aim, an objective and a research question?

The aim is the single overall purpose of the study. Research questions are what you ask in order to reach it. Objectives are the specific, measurable steps you will take. Many departments want objectives, some want questions, and some want both plus hypotheses. Whichever you use, each one should map to a result you can point to later.

Do I need hypotheses as well as research questions?

Only if your department or supervisor asks for them, which is common for quantitative studies that test a relationship or a difference. A hypothesis is a testable statement (for example, that there is no significant relationship between X and Y), and it should come straight from a relational or comparative question. Descriptive and qualitative projects usually do not need hypotheses.