Skip to content

Results Doctor: what to do when alpha, KMO, HTMT or a hypothesis fails

Cronbach's alpha below .70, KMO below .50 (Kaiser, 1974) or HTMT above .85 (Henseler et al., 2015)? Check for data errors first, then make only pre-specified, reportable changes. Paste your SPSS or SmartPLS tables and the tool lists the legitimate options in order, each with its conditions, consequences, how to report it and a source.

  1. Describe your study: N, planned sample size, method, scale origin
  2. Paste SPSS or SmartPLS tables, or type in your numbers
  3. Click Diagnose, tick what you did, export the change log
1. Study context
The figure in your proposal, set before data collection.
Reads: Reliability Statistics, Item-Total Statistics, KMO and Bartlett's Test, Total Variance Explained, Rotated Component Matrix / Pattern Matrix, Model Summary, ANOVA, Coefficients, Descriptive Statistics (Skewness, Kurtosis); SmartPLS: Construct reliability and validity, HTMT (matrix or list), Outer loadings, Path coefficients / P values, VIF. Your numbers are processed only in your browser.

3. Your results (fill in what you have, leave the rest blank)
Cronbach's alpha reliability (Item-Total Statistics)
EFA (KMO, Bartlett, rotated matrix)

PLS-SEM / CFA (AVE, CR, HTMT, outer loadings)
Regression / structural model (R², β, p, VIF)
Distribution and common method bias (skewness, kurtosis, Harman, full collinearity VIF)
SPSS reports excess kurtosis (normal distribution = 0).

Re-run reliability after checking your coding: Cronbach's alpha calculator. Check your sample size: Sample size calculator. Screen responses properly: Survey data cleaning.

Send to your study group

When the whole group uses one tool, your numbers match when you merge chapters.

Was this tool useful? Feedback / report a bug (by email; please do not paste real data).

Worked example: low Cronbach's alpha on real data

What should you do when Cronbach's alpha is low? Check for data errors first (reverse-worded items, missing-value codes, careless responses), then consider dropping one item for a stated reason, and if alpha is still below the threshold, report it honestly as a limitation. The example uses the Openness scale (O1–O5, 6-point) of the public bfi data set (Revelle, 2026), the same data as on our verification page, so you can reproduce it in the Cronbach's alpha calculator.

StepCheckResult on bfi OpennessDecision
1Have reverse-worded items been recoded?O2 and O5 not reversed: alpha = −.157, with negative item-total correlations for O2 and O5. After reversing (7 − score): alpha = .603Fix the coding; do not drop the items
2Out-of-range values, missing codesAll values within 1–6; 2,726 of 2,800 cases answered all 5 itemsNothing to correct
3Items with item-total correlation below .30O4 (“Spend time reflecting on things”): .220; alpha if O4 deleted = .614 > .603Dropping O4 is defensible on content grounds (reflection differs from intellectual curiosity); report before and after
4After droppingFour-item alpha = .614 (2,740 complete cases), still below .70Stop. Do not drop more items or cases to push alpha up
5ReportAlpha, its 95% confidence interval (.578–.626 for 5 items), the dropped item and the reasonPresent it as a limitation in the Discussion

A model Results paragraph in APA 7 style:

The five-item Openness scale had a Cronbach's alpha of .603, 95% CI [.578, .626]. Item O4 had a corrected item-total correlation of .220, below .30, and its content concerns reflection rather than intellectual curiosity, so it was removed. After removing O4, Cronbach's alpha was .614, which is acceptable only in exploratory research (Hair et al., 2010); this is a limitation of the study.

How to read the diagnosis

Each issue gets a severity (Serious, Needs action, Note, Info), the numbers it is based on, what it means, and a numbered list of options in the order to try them. Every option states what to do, when it is legitimate, what follows from it, how to write it up and the source. Tick the steps you actually carry out and type in the result after re-running: the change log and the procedure paragraph update themselves, ready for your supervisor and your appendix. Everything runs in your browser.

The order matters because many "failed" results come from undetected data errors:

  1. Reverse-worded items not recoded. A negative item-total correlation or a negative loading almost always means this. Dropping the item hides an error you could fix.
  2. Data entry and missing codes. A code of 99 not declared under Missing Values, or out-of-range values, distorts every index.
  3. Low-quality responses. Screen only with rules written down in advance (attention checks, straight-lining, very short completion time), applied once to all cases.
  4. Wording and translation. Double-barrelled or mistranslated items explain why an item performs poorly.
  5. Dropping an item for a reason. Only with a pre-specified rule (for example item-total correlation below .30), at least 3 items left, the construct's content still covered, one item at a time, reporting before and after.
  6. Reporting a limitation. When nothing justifies a change, keep the number and explain it.
  7. Collecting more data, only when valid responses fall below the planned or minimum sample size. Collect the shortfall once and re-analyse; never check p after each batch.

HTMT above .85: what to do

HTMT above .85 (or .90 for conceptually close constructs) means respondents did not clearly separate the two constructs (Henseler et al., 2015). In the SmartPLS example, HTMT between HL and YD is .913, so the tool flags it as serious. Put the two definitions and their items side by side, bootstrap to see whether the HTMT confidence interval includes 1, and merge the constructs or drop an overlapping item only for a theoretical reason, reported as a departure from your proposal. Dropping items one by one until HTMT dips below .85 is not a legitimate fix.

Thresholds the tool uses

These are common conventions, not laws. If your department uses another threshold (for example loadings of .50), follow it and state it in your Methods chapter. Full references with DOIs appear at the end of each diagnosis.

An unsupported hypothesis is not a failure

p > .05 does not ruin a thesis. It is a valid result: the data do not provide enough evidence for that effect in your context. Mark it "Not supported" in the hypothesis table with the actual β and p, then write a separate Discussion paragraph comparing it with prior studies. Note that p ≥ .05 does not prove there is no effect; that conclusion needs an equivalence test.

What you must never do

Frequently asked questions

Will I fail if Cronbach's alpha is below .70?

Not automatically. Examiners judge how you handled it: whether you checked reverse-worded items, missing codes and careless responses, dropped items only for a reason, and reported honestly. Alpha from .60 to just under .70 is accepted in exploratory research (Hair et al., 2010) if you say so.

Why is my Cronbach's alpha low?

Most often: reverse-worded items not recoded, too few items, mistranslated items, careless responses, or a scale that mixes several facets. Alpha also rises with the number of items (Cortina, 1993), so a 3-item scale reaches .70 less easily than an 8-item scale of the same quality.

Will collecting more responses raise alpha?

Not systematically. More cases narrow alpha's confidence interval; they do not push alpha up. Collect more only when valid responses are below your planned sample size, and do it once.

Can I delete cases to get alpha to .70?

No, if the reason is the alpha value. Deleting cases is legitimate only when they break screening rules written beforehand (failed attention check, straight-lining, too-short completion time), applied to every case, with the number removed reported.

References for this guide

One of the free research tools of Research Corner.