Tag: Cronbach alpha

  • What Is a Good Cronbach’s Alpha — and What If Yours Is Low? (2026)

    What Is a Good Cronbach’s Alpha — and What If Yours Is Low? (2026)

    0.70 is the figure most Nigerian departments accept as the minimum for a self-developed questionnaire, with 0.80 and above regarded as good. Below 0.70 the usual cause is not a bad topic — it is unreversed negative items, a section measuring two different things at once, or too few items. All three are fixable before you collect your main data.

    What is Cronbach’s alpha actually measuring?

    Internal consistency: the extent to which the items in one section of your instrument behave as though they are measuring the same underlying thing.

    If Section B has ten items about study habits, and a respondent who agrees strongly with item 1 also tends to agree with items 2 through 10, the section is internally consistent and alpha will be high. If the answers scatter with no pattern, the items are not measuring one construct, and alpha will be low.

    Note what it is not. Alpha says nothing about whether your instrument measures the right thing — that is validity, a separate matter your supervisor and validators handle. A questionnaire can be perfectly consistent and still measure the wrong construct. Panels occasionally ask this, and “reliability is consistency, validity is correctness” is the answer.

    What counts as a good alpha?

    The conventional bands, which most Nigerian departments teach:

    Alpha Usual verdict
    0.90 and above Excellent — but check for redundancy
    0.80 to 0.89 Good
    0.70 to 0.79 Acceptable — the common minimum
    0.60 to 0.69 Questionable; some departments accept it for a new instrument
    Below 0.60 Poor — repair the instrument

    Two honest caveats. These bands are a widely taught convention rather than a statistical law, and different authors set the cut-offs slightly differently — so if your project handout names a threshold, that number outranks this table. And a very high alpha is not automatically better: above roughly 0.95 you may simply have asked the same question in several different ways, which wastes your respondents’ patience and adds nothing.

    Report it with its context, not on its own: “A pilot test involving 30 respondents produced a Cronbach’s alpha of 0.84 for Section B (10 items) and 0.78 for Section C (8 items), indicating that the instrument was reliable.” The number of items and the pilot sample belong in that sentence, in Chapter Three.

    Why is my alpha low?

    Four causes, in the order you should check them.

    1. You did not reverse-score the negative items

    This is the most common cause by a wide margin, and it is the easiest to miss. If Section B contains “I struggle to concentrate when studying at night” among nine positively worded items, a respondent who agrees with the other nine will disagree with that one — and to the calculation, that looks like inconsistency.

    Recode before you compute anything: Transform > Recode into Different Variables, mapping 1→4, 2→3, 3→2, 4→1 on a four-point scale, into a new variable rather than over the original. The full sequence is in the guide to analysing project data in SPSS step by step. Fixing this alone routinely moves an alpha from 0.4 to 0.8.

    2. You put the whole questionnaire in at once

    Alpha is computed per scale, not per instrument. If you feed Section B (study habits) and Section C (academic performance) into one Reliability Analysis, you are asking whether two different constructs behave as one, and they should not. Run each section separately and report an alpha for each.

    3. Your section has too few items

    Alpha rises with the number of items, all else being equal. A three-item section can be perfectly sound and still return a modest alpha simply because it is short. If a section is genuinely important to your study, four to six well-written items is a more comfortable place to be than two.

    4. An item is genuinely bad

    Double-barrelled items (“I find the library quiet and well stocked” — which one are you agreeing with?), ambiguous wording, or an item nobody understood in the same way. These show up clearly in the diagnostic below.

    A printed questionnaire section with one weak item circled in red pen
    Usually it is one item, not the whole section. The output will tell you which one.

    How do you find the item that is dragging it down?

    SPSS will tell you directly if you ask it to.

    1. Go to Analyze > Scale > Reliability Analysis.
    2. Move in the items of one section, leaving the Model on Alpha.
    3. Click Statistics and tick Scale if item deleted.
    4. Run it, and read the column headed “Cronbach’s Alpha if Item Deleted”.

    That column shows what alpha would become if each item were removed. Nearly every value will sit slightly below your current alpha — that is normal, and it means the item is contributing. The one to look at is any item whose deletion would raise alpha noticeably. Check the “Corrected Item-Total Correlation” column alongside it; an item near zero or negative there is not measuring what the rest of the section measures.

    Can you just delete the bad item?

    Usually yes, with three conditions.

    • Do it at the pilot stage, not after main data collection. Repairing an instrument during a pilot is normal research practice. Dropping items from your final data until alpha crosses 0.70 is a different activity, and a panel that notices will treat it as one.
    • Check the item is not essential to your research question. If it is the only item covering a concept your Chapter One promised to measure, replace it with a better-worded item rather than deleting it outright.
    • Report what you did. One sentence in Chapter Three: “Following the pilot test, item 7 was removed from Section B as its deletion improved the reliability coefficient from 0.64 to 0.79, and the final instrument comprised nine items in that section.”

    That sentence is a strength, not an admission. It shows you ran a pilot, read the output and acted on it, which is exactly what a pilot is for.

    A small group of Nigerian students completing a pilot questionnaire at a table
    Twenty to thirty respondents outside your main sample. The pilot is the cheapest hour in the whole project.

    How many respondents does the pilot need?

    Most Nigerian departments ask for between 20 and 30, drawn from a population similar to your sample but not part of it — a neighbouring department, another campus, a different section. If those respondents later appear in your main data, your pilot was not independent and your reliability figure is not what you claimed.

    Check your project handout for the number your department expects, because this is one of the details supervisors specify and panels ask about.

    What if you are using someone else’s instrument?

    Then the original author has probably already published a reliability coefficient, and you cite it — but you still compute your own on your own pilot, because reliability is a property of a scale in a particular population, not a permanent property of the questionnaire. An instrument validated on postgraduates in another country may behave differently among 300-level undergraduates in your department.

    Cite the source of the instrument in your reference list along with the author’s reported alpha, and report yours beside it. Where those citations sit is covered in the guide to writing Chapter Two.

    What will the panel ask about this?

    Three questions, reliably.

    “What was your reliability coefficient?” Know the number for each section without looking it up.

    “How did you compute it, and on what sample?” Name the software and the pilot size. Never report an alpha you did not compute yourself — you will be asked, and there is no recovery from not knowing where your own number came from.

    “Is your instrument valid?” This is the different question. Validity comes from your supervisor and validators reviewing the instrument against your objectives, and it is reported separately from reliability. Both belong in Chapter Three, and the wider set of questions is inventoried in the guide to what is asked during a project defence. Where the resulting figures appear in your results chapter is covered in writing Chapter Four.

    Keep the numbers and the chapter in step

    Tesify holds your chapters in the structure your department expects, so a reliability figure you report in Chapter Three and the instrument you describe stay attached to each other while you work. Over 9,000 students have used it to write more than 15,000 chapters, and every word is still written by you.

    Set up your project in Tesify

    Frequently asked questions

    What is a good Cronbach’s alpha?

    0.70 and above is the conventional minimum, 0.80 to 0.89 is good and 0.90 and above is excellent, though very high values can indicate redundant items. If your department’s handout states a threshold, follow that instead.

    Is 0.6 an acceptable Cronbach’s alpha?

    It is borderline. Some departments accept it for a newly developed instrument in an under-researched area, but many will ask you to improve it. Try reverse-scoring and the “alpha if item deleted” diagnostic before accepting it.

    Why is my Cronbach’s alpha so low?

    Most often because negatively worded items were not reverse-scored, or because two different sections were entered into one reliability analysis. Check both before concluding the instrument is bad.

    Can Cronbach’s alpha be negative?

    Yes, and it almost always means an item is scored in the opposite direction from the others. Reverse-score the negative items and run it again.

    Do I compute one alpha for the whole questionnaire?

    No. Compute one per section or construct. A single alpha across sections measuring different things is not meaningful, however good the number looks.

    How many respondents should the pilot test have?

    Usually 20 to 30, from a similar population but not from your main sample. Confirm the figure your department expects, since handouts often specify it.

    Can I remove an item to improve my alpha?

    At the pilot stage, yes, and you should report that you did and why. Removing items from your main data until the number improves is a different matter and is visible to anyone reading the chapter carefully.

    Do I need a pilot test if I am using a published instrument?

    Yes. Reliability is a property of a scale in a particular population, so compute your own coefficient on your own respondents and report it alongside the author’s.

    Is reliability the same as validity?

    No. Reliability is consistency — whether the items behave alike. Validity is correctness — whether the instrument measures what you claim. Both belong in Chapter Three and they are established differently.

    What if my department does not ask for Cronbach’s alpha?

    Some departments accept a test-retest procedure instead. Follow your handout, name whichever method you used, and report the resulting coefficient with the sample it came from.

    Where does the alpha go in my project?

    In Chapter Three, in the reliability of the instrument section, with the number of items and the pilot sample. It is not a finding, so it does not belong in Chapter Four.

  • How to Analyse Your Project Data in SPSS, Step by Step (2026)

    How to Analyse Your Project Data in SPSS, Step by Step (2026)

    The questionnaires are back. There are two hundred and thirty of them in a nylon bag, SPSS is open on a borrowed laptop, and the cursor is blinking in an empty grid. This is where most Nigerian project groups lose a week — not to the statistics, which are usually simple, but to not knowing the order of operations.

    What follows is that order, in nine steps, with the exact menu path for every procedure an undergraduate project needs. Paths are quoted as documented in Kent State University Libraries’ freely available SPSS tutorials; recent versions keep them stable, but if a menu on your machine reads slightly differently, trust your machine.

    Two things belong upstream of this guide. You should already know which tool answers which research question — that decision is made in choosing the statistical test for your project, not in the software. And what you do with the output afterwards is a separate skill, set out in writing Chapter Four.

    Step 1: Number the questionnaires before you touch a computer

    Output: a physical stack in which every usable copy carries a unique case number.

    1. Separate the incomplete copies into their own pile. Count both piles and write both counts down; your return rate needs them.
    2. Write 1, 2, 3 in the top corner of each usable questionnaire.
    3. Keep the stack in that order for the whole encoding session.

    This takes fifteen minutes and it is the only thing that makes an encoding error recoverable. When SPSS later shows a respondent aged 220, the case number tells you which sheet of paper to check. Without it you are re-reading 231 questionnaires to find one typo.

    A stack of questionnaires with case numbers handwritten in the top corner of each
    Fifteen minutes with a pen. This is what turns “there is an error somewhere” into “the error is on copy 147”.

    Step 2: Build the variable list before entering a single response

    Output: a complete Variable View, filled in before any data exists.

    Click the Variable View tab at the bottom of the data editor. Every questionnaire item becomes one row, and four columns matter.

    • Name — short, no spaces, systematic. Use sex, level, dept, then B1 to B10 and C1 to C10 so the names mirror the sections of your instrument.
    • Label — the full item text. This is what prints on your output tables, so a good label here saves retyping every row of Chapter Four by hand.
    • Values — the numeric code for each option: 1 = Strongly Disagree through 4 = Strongly Agree, or 1 = Male, 2 = Female.
    • Measure — Nominal for categories such as sex or department, Ordinal for Likert items, Scale for genuinely continuous variables such as age or a computed total.

    Getting Measure right early prevents a whole class of later confusion, because SPSS uses it to decide which procedures it offers you for a variable.

    A handwritten codebook page mapping questionnaire answer options to numeric codes
    Agree the codebook on paper first. If three of you are encoding on three laptops, this page is the only thing that makes the files mergeable.

    Step 3: Encode the responses, one row per respondent

    Output: a Data View grid with as many rows as you have usable questionnaires.

    Switch to Data View and work down the numbered stack. One respondent is one row; one item is one column. Never put two respondents on one row and never spread one respondent across two.

    Three rules prevent the expensive mistakes. Leave a genuinely unanswered item blank rather than typing 0 — zero is a real value and it will drag your mean down. Decide as a group how to treat an item where a respondent ticked two boxes, then apply that decision to every case rather than case by case. And if you split encoding across several laptops, agree the codebook in writing first, because merging three files that coded sex differently costs more than the encoding did.

    Save as a .sav file after every fifty cases, with the date in the filename.

    Step 4: Reverse-score the negatively worded items

    Output: new variables in which every item points the same direction.

    If your instrument contains an item like “Power supply has no effect on how long I study”, a high score there means the opposite of a high score on the rest of the scale. Averaging it in unreversed will depress your grand mean and wreck your reliability coefficient.

    1. Go to Transform > Recode into Different Variables.
    2. Move the negatively worded item across and give the output variable a new name, such as B7r.
    3. Click Old and New Values and enter the reversal for a four-point scale: 1→4, 2→3, 3→2, 4→1.
    4. Click Add for each pair, then Continue and OK.

    Always recode into a different variable, never over the original. Keeping the raw column means a mistake here is one recode away from being fixed rather than a re-encoding away.

    Step 5: Screen the data before you analyse it

    Output: a frequency table for every variable, checked against the range each is allowed to take.

    Run Analyze > Descriptive Statistics > Frequencies, move all your variables across, and read the output for three things.

    • Impossible values. A four-point item with a maximum of 5 is a typo. Find the case number and check the paper.
    • Missing counts. Every variable’s Valid N should equal your analysed N unless you know why it does not.
    • Category totals. The frequencies for sex should sum to your N. If they do not, a case is miscoded.

    Fix everything you find here before running anything else. An error corrected now costs a minute; the same error found after three tables are written costs the afternoon.

    Step 6: Run the reliability analysis

    Output: a Cronbach’s alpha for each section of your instrument.

    1. Go to Analyze > Scale > Reliability Analysis.
    2. Move in the items of one section only — Section B on its own, then Section C on its own. A scale measuring two different constructs is not one scale.
    3. Leave the Model on Alpha.
    4. Click Statistics and tick Item, Scale, and Scale if item deleted.
    5. Read the alpha, then read the “Cronbach’s Alpha if Item Deleted” column to see whether one bad item is dragging the section down.

    Report the coefficient with the number of items and the pilot sample it came from, in Chapter Three. You will be asked at the defence which software produced it, so do not report a figure you did not compute.

    Step 7: Produce the descriptive tables Chapter Four needs

    Output: the bio-data table and the per-item mean tables, in that order.

    For the respondent profile — sex, level, department — use Analyze > Descriptive Statistics > Frequencies and take the frequency and percentage columns straight into your table.

    For the “level of” or “extent of” research questions, use Analyze > Descriptive Statistics > Descriptives with the Likert items of that section selected; the Mean and Std. Deviation columns are exactly what your table needs. For the grand mean, build a computed variable first with Transform > Compute Variable using the MEAN function across the items of that section.

    Compare each mean against your criterion mean — 2.50 on a four-point scale — and fill the Decision column accordingly.

    Step 8: Run the inferential test each hypothesis needs

    Output: one output block per hypothesis, and no blocks you cannot attach to a hypothesis.

    What your hypothesis asks Procedure Menu path
    Are two categorical variables associated? Chi-square test of independence Analyze > Descriptive Statistics > Crosstabs, then Statistics > Chi-square
    Are two scale variables related? Pearson correlation Analyze > Correlate > Bivariate
    Are two ordinal or non-normal variables related? Spearman’s rho Analyze > Correlate > Bivariate, tick Spearman
    Do two groups differ? Independent-samples t test Analyze > Compare Means and Proportions > Independent-Samples T Test
    Do three or more groups differ? One-way ANOVA Analyze > Compare Means > One-Way ANOVA
    Is the distribution normal? Shapiro-Wilk and Kolmogorov-Smirnov Analyze > Descriptive Statistics > Explore, then Plots > Normality plots with tests

    Three details the dialogs will force on you. In Crosstabs the chi-square statistic is not produced unless you tick it under Statistics — the crosstab alone is only a contingency table, and this is the single most common reason a Nigerian student cannot find their chi-square value. In Bivariate, Pearson is selected by default and the test is two-tailed by default, with significance flagged at the .05 and .01 levels. And the Independent-Samples T Test will not run until you click Define Groups and specify the two codes being compared.

    Step 9: Save the output and reconcile it before writing

    1. Save the data as .sav and the output as .spv, both dated, and copy both to a second device or a cloud folder.
    2. Check that the Valid N on your output matches the analysed N you stated in Chapter Three.
    3. Check that every research question and hypothesis has exactly one output block, and delete the exploratory runs you did along the way.
    4. Check that the tools that produced your output are the ones you named in Chapter Three. If you changed one, change the chapter too.

    Only then start writing. A Chapter Four built from unreconciled output will contradict Chapter Three somewhere, and that contradiction is the first thing a panel finds — as the standard question list in what is asked during a project defence makes clear. How the analysis chapter sits within the whole document is summarised in how many chapters a final year project has.

    You have the output. Now write the chapter.

    Tesify holds your chapters in the structure your department expects and keeps every citation attached to a source you actually opened, so the week after analysis goes into interpretation rather than formatting. Over 9,000 students have used it to write more than 15,000 chapters, and every word is still written by you.

    Write up your results in Tesify

    Frequently asked questions

    How do I analyse my project data using SPSS?

    Number the questionnaires, build the full Variable View before entering data, encode one row per respondent, reverse-score the negative items, then screen with Frequencies. Only after screening do you run reliability, descriptives and your inferential tests.

    What is the menu path for Cronbach’s alpha?

    Analyze > Scale > Reliability Analysis, with the Model left on Alpha. Enter one section at a time and tick “Scale if item deleted” under Statistics to see which item is weakening it.

    Why is my chi-square value not showing?

    Because it is not produced by default. Open the Statistics button inside the Crosstabs dialog, tick Chi-square, then run it again.

    How do I encode a four-point Likert scale?

    Set the item’s Measure to Ordinal and define its Values as 1 to 4 with the verbal label attached to each number. Then type only the numbers into Data View.

    Should I enter 0 for an unanswered item?

    No. Leave it blank. Zero is a real value on a numeric variable and it will pull the mean down and misstate the count of valid responses.

    Do I have to reverse-score negative items?

    Yes, if you are averaging items into a section score or computing a reliability coefficient. Skipping it is the commonest cause of an unexpectedly low Cronbach’s alpha in an otherwise sound instrument.

    How do I get the grand mean in SPSS?

    Build the section score first with Transform > Compute Variable using the MEAN function across that section’s items, then run Descriptives on the new variable.

    Which SPSS version do I need?

    Any recent version handles everything an undergraduate project needs. Menu wording shifts slightly between releases, so state in Chapter Three the version you actually used rather than copying a number from another project.

    My groupmates encoded on separate laptops and the files will not merge. What now?

    Compare the Variable View of each file side by side before merging. Mismatched variable names, different codes for the same answer and different Measure settings are the usual culprits, and all three are fixable in the file that deviates rather than by re-encoding.

    Do I keep the output file after the defence?

    Keep it until your project is finally approved and bound. Panels ask to see output, corrections can require reruns, and rebuilding a lost analysis from paper questionnaires under deadline is a miserable weekend.

    Can I do all of this without SPSS?

    Yes. Free packages cover the same undergraduate procedures, and spreadsheets handle means and percentages. Whichever you use, name that one in Chapter Three rather than naming SPSS by habit.