How to Interpret a Heterotrait-Monotrait Ratio? (2026 Guide)

Structural equation modeling (SEM) lives or dies on one foundational assumption: the constructs in your model must measure genuinely distinct concepts. That assumption is called discriminant validity, and the most reliable tool for testing it today is the heterotrait-monotrait ratio of correlations, or HTMT. If you are working through a measurement model for a thesis, a journal article, or an organizational survey, knowing how to interpret a heterotrait-monotrait ratio correctly can save you from reviewers rejecting your work or from drawing flawed conclusions.

HTMT was introduced by Jorg Henseler, Christian M. Ringle, and Marko Sarstedt in their 2015 paper in the Journal of the Academy of Marketing Science. Since then it has steadily replaced the older Fornell-Larcker criterion as the standard discriminant validity check in both covariance-based SEM (CB-SEM) and partial least squares SEM (PLS-SEM). Monte Carlo simulation studies showed that Fornell-Larcker fails to detect discriminant validity problems far more often than researchers had assumed, and HTMT was designed to fix that blind spot.

This guide walks you through everything you need to know. You will learn what HTMT measures conceptually, see the exact formula with every term explained in plain language, follow a fully worked numeric example with real correlation values, understand the strict and lenient thresholds, and learn how to report your results in an academic paper. We also cover the HTMT2 variant, bootstrapping confidence intervals, software implementation in R and SmartPLS, and common pitfalls that can throw off your interpretation.

Whether you just discovered HTMT during a reviewer’s request or you are building a measurement model from scratch, by the end of this article you will be able to read an HTMT matrix with confidence and defend your discriminant validity claims. We have built this guide to serve PhD students running their first SEM analysis, experienced researchers updating their validation toolkit, and methodologists who need a reference they can cite when explaining HTMT to collaborators.

Quick Answer: How to Interpret a Heterotrait-Monotrait Ratio

The short version: an HTMT value below 0.85 (strict threshold) or below 0.90 (lenient threshold) between two reflectively measured constructs means discriminant validity has been established. An HTMT value above 0.90 means the two constructs overlap too much and discriminant validity has not been demonstrated.

For inference, you should also run bootstrapping and check that the upper bound of the 95% confidence interval for the HTMT is below 1.0. If it crosses 1.0, the two constructs are statistically indistinguishable and you cannot meaningfully estimate structural paths between them.

The strict 0.85 threshold, recommended by Henseler and colleagues, is the safer choice for most published research. The lenient 0.90 threshold is sometimes used when constructs are conceptually related and a slightly more permissive standard is justified. We explain when each threshold applies in the dedicated decision thresholds section below.

HTMT applies to reflective measurement models only. It does not work for formative constructs, single-indicator constructs, or categorical indicators treated as exogenous variables. If your measurement model mixes reflective and formative constructs, compute HTMT only for the reflective pairs.

What Is the Heterotrait-Monotrait Ratio (HTMT)?

The heterotrait-monotrait ratio is a discriminant validity measure that compares how strongly indicators of two different constructs correlate with each other versus how strongly indicators within each construct correlate with themselves. In simple terms, it asks: do the items measuring Construct A correlate more with the items measuring Construct B than they correlate with their own construct’s other items?

If they do, you have a problem. Two constructs that share more variance with each other than within themselves cannot be treated as separate variables in a structural model. Any path coefficients, R-squared values, or indirect effects you estimate between them will be unreliable and potentially misleading.

To understand HTMT, you need to understand the two building blocks in its name. Heterotrait-heteromethod correlations are correlations between indicators that belong to different constructs and are measured by different items. For example, if your “Customer Satisfaction” construct has three indicators (CS1, CS2, CS3) and your “Loyalty” construct has three indicators (LOY1, LOY2, LOY3), the nine correlations between each satisfaction item and each loyalty item are heterotrait-heteromethod correlations.

Monotrait-heteromethod correlations are correlations between indicators that belong to the same construct but are different items. The three pairwise correlations among CS1, CS2, and CS3 are monotrait-heteromethod correlations for the Customer Satisfaction construct. The same logic applies to the three Loyalty indicators. These correlations capture how consistently the items within a single construct hang together.

HTMT takes the average of all heterotrait-heteromethod correlations between the two constructs and divides it by the geometric mean of the two within-construct averages. The result is a ratio that should be well below 1 if the constructs are truly distinct. In practice, it should be below 0.85 for most studies.

Think of it this way: if you ran a survey asking customers about satisfaction and loyalty, and the satisfaction items correlated with the loyalty items almost as strongly as they correlated with each other, you would have no evidence that satisfaction and loyalty are separate psychological constructs. HTMT quantifies that intuition precisely.

Before HTMT, the dominant approach was the Fornell-Larcker criterion, which compares the square root of the average variance extracted (AVE) for each construct against its correlations with other constructs. Henseler and colleagues ran Monte Carlo simulations and found that Fornell-Larcker failed to detect discriminant validity problems in a large percentage of scenarios, especially when constructs were highly correlated but still technically distinct. HTMT was specifically designed to be more sensitive, and the simulations confirmed it catches problems that Fornell-Larcker misses.

HTMT also has a practical advantage. Unlike Fornell-Larcker, which requires factor analysis or composite scores to compute AVE, HTMT works directly on the observed correlation matrix of indicators. This makes it simpler to calculate, easier to understand, and applicable across a wider range of modeling approaches. You can compute HTMT even before fitting a structural model, which means you catch measurement problems early in your analysis pipeline.

Since 2015, HTMT has been adopted by every major SEM software platform. SmartPLS added native HTMT reporting and bootstrapping. The semTools package in R provides a dedicated function. ADANCO, the software developed by Henseler’s team, computes HTMT by default. Even IBM SPSS AMOS users can access HTMT through James Gaskin’s widely used Stats Tools Package plugin. The methodological community has reached a clear consensus: HTMT is the primary tool for discriminant validity in modern SEM research.

The HTMT Formula Explained

The HTMT formula for a pair of constructs looks like this:

HTMT = mean(rheterotrait-heteromethod) / geometric mean(mean(rmonotrait-heteromethod-A), mean(rmonotrait-heteromethod-B))

Let us break each piece down in plain language so you can explain it to a thesis committee or a co-author who has never encountered the formula before.

The numerator is the average of all correlations between indicators of Construct A and indicators of Construct B. If A has 3 indicators and B has 3 indicators, you have 3 times 3, or 9 correlations. You take the arithmetic mean of those 9 values. This number represents how strongly the two constructs’ items relate to each other on average.

The denominator is the geometric mean of two separate averages. First, you compute the average of all pairwise correlations among the indicators of Construct A (3 indicators produce 3 unique pairs). Then you compute the same for Construct B. Finally, you multiply those two averages together and take the square root to get the geometric mean. This denominator represents the typical strength of within-construct relationships.

The geometric mean is used instead of a simple arithmetic average because it provides a balanced reference point when the two constructs have different levels of internal consistency. If Construct A’s indicators correlate at 0.80 on average and Construct B’s indicators correlate at 0.50, the arithmetic mean would be 0.65. The geometric mean would be the square root of (0.80 times 0.50), which is about 0.632. The geometric mean penalizes imbalance more heavily, which is the more conservative and appropriate behavior for a validity check.

There is also a variant called HTMT2, which uses the arithmetic mean of the two within-construct averages in the denominator instead of the geometric mean. HTMT2 was proposed to address cases where the geometric mean produces slightly biased estimates when construct reliabilities differ substantially. Most software packages, including the semTools::htmt() function in R, compute HTMT2 by default alongside the original HTMT. The difference between the two is usually small, but HTMT2 is considered the more refined version and is recommended when your software offers it.

One more technical detail: most implementations take the absolute values of all correlations before computing the averages. This prevents negative correlations (which can occur with reverse-coded items) from artificially lowering the HTMT and producing a false sense of security. The absolute = TRUE argument in semTools handles this, and SmartPLS has used absolute values by default since version 3.2.1. If you compute HTMT manually in Excel, take the absolute value of every correlation before averaging.

The formula generalizes to any number of indicators per construct. If Construct A has 4 indicators and Construct B has 5 indicators, the numerator averages 20 cross-correlations. The denominator computes the average of 6 within-A pairs (4 choose 2 equals 6) and the average of 10 within-B pairs (5 choose 2 equals 10), then takes the geometric mean of those two averages. The procedure is identical regardless of how many indicators each construct has.

Step-by-Step Calculation: A Worked Numeric Example

This is the section most guides skip. Let us calculate HTMT by hand using a realistic two-construct example so you can see every intermediate step. Walking through this once builds the intuition you need to interpret software output later.

Imagine you have two reflectively measured constructs from a customer survey. Service Quality (SQ) has three indicators: SQ1, SQ2, SQ3. Customer Satisfaction (CSAT) has three indicators: CSAT1, CSAT2, CSAT3. After collecting 300 responses, you compute the correlation matrix among all six indicators.

Here is the correlation matrix:

SQ1 and SQ2 = 0.70
SQ1 and SQ3 = 0.65
SQ2 and SQ3 = 0.72
CSAT1 and CSAT2 = 0.68
CSAT1 and CSAT3 = 0.66
CSAT2 and CSAT3 = 0.74

Now the cross-construct (heterotrait-heteromethod) correlations:

SQ1 and CSAT1 = 0.45
SQ1 and CSAT2 = 0.42
SQ1 and CSAT3 = 0.40
SQ2 and CSAT1 = 0.48
SQ2 and CSAT2 = 0.44
SQ2 and CSAT3 = 0.41
SQ3 and CSAT1 = 0.46
SQ3 and CSAT2 = 0.43
SQ3 and CSAT3 = 0.39

Step 1: Compute the average heterotrait-heteromethod correlation (the numerator).

Add all nine cross-construct correlations: 0.45 + 0.42 + 0.40 + 0.48 + 0.44 + 0.41 + 0.46 + 0.43 + 0.39 = 3.88. Divide by 9 to get the mean: 3.88 / 9 = 0.431.

Step 2: Compute the average monotrait-heteromethod correlation for Service Quality.

Add the three within-SQ correlations: 0.70 + 0.65 + 0.72 = 2.07. Divide by 3: 2.07 / 3 = 0.690.

Step 3: Compute the average monotrait-heteromethod correlation for Customer Satisfaction.

Add the three within-CSAT correlations: 0.68 + 0.66 + 0.74 = 2.08. Divide by 3: 2.08 / 3 = 0.693.

Step 4: Compute the geometric mean of the two within-construct averages (the denominator).

Multiply 0.690 by 0.693: 0.690 times 0.693 = 0.4782. Take the square root: sqrt(0.4782) = 0.6915.

Step 5: Divide the numerator by the denominator to get the HTMT value.

HTMT = 0.431 / 0.6915 = 0.623.

Step 6: Interpret the result.

An HTMT of 0.623 is well below both the strict 0.85 threshold and the lenient 0.90 threshold. Discriminant validity between Service Quality and Customer Satisfaction is clearly established. You can confidently include both constructs in your structural model and interpret the path between them as a relationship between two distinct concepts.

If you wanted to compute HTMT2 instead, you would replace the geometric mean in Step 4 with the arithmetic mean of 0.690 and 0.693, which is 0.6915. In this particular example the two values are nearly identical because the within-construct averages are so close, but with real data the difference can be more noticeable. When the two constructs have very different internal consistency levels, HTMT2 can diverge from HTMT by several percentage points.

This example used two constructs with three indicators each, but the same procedure applies to larger models. For a model with five constructs, you would repeat this calculation for every pair of constructs (10 pairs total) and present the results as an HTMT matrix. Software automates this, but understanding the manual process helps you spot errors and explain results to others.

A second example with a failing pair. Consider two constructs from the same survey: Trust (TR) with indicators TR1, TR2, TR3 and Credibility (CR) with indicators CR1, CR2, CR3. These concepts are conceptually very close, and the correlations reflect that. The within-TR correlations average 0.71. The within-CR correlations average 0.69. The geometric mean of those two averages is sqrt(0.71 times 0.69) = sqrt(0.4899) = 0.6999. The nine cross-correlations average 0.64. The HTMT is 0.64 / 0.6999 = 0.914.

This value exceeds 0.90, which means discriminant validity has not been established between Trust and Credibility. The two constructs are too similar to be treated as separate variables. You would need to either merge them into a single construct, remove overlapping items, or justify why the two concepts should remain separate despite the high HTMT and re-specify the indicators to reduce overlap.

Decision Thresholds: How to Interpret HTMT Values

The threshold question is the most common source of confusion for researchers learning HTMT. There are two widely cited thresholds, and knowing when to use each matters for how you report your results and how reviewers evaluate your measurement model.

The strict threshold is HTMT below 0.85. This was the original recommendation from Henseler, Ringle, and Sarstedt (2015) based on their Monte Carlo simulations. They found that 0.85 provided a strong balance between correctly identifying discriminant validity problems and avoiding false positives. Use this threshold when your constructs are conceptually distinct, when you are publishing in a rigorous journal, or when a reviewer asks for the more conservative standard.

The lenient threshold is HTMT below 0.90. This threshold is appropriate when your constructs are conceptually related by design. For example, “Job Satisfaction” and “Organizational Commitment” are known to overlap in the literature, so a slightly more permissive standard may be justified. Some methodologists also use 0.90 when they want to avoid discarding otherwise strong measurement models that sit just above 0.85.

Values above 0.90 indicate that discriminant validity has not been established. This means the two constructs are too similar to be treated as separate variables. You should not interpret structural paths between them as independent relationships, and you should not report them as distinct constructs without substantial theoretical justification and possibly a respecification of the measurement model.

Some researchers cite an ideal range of 0.011 to 0.389 as the values that most cleanly satisfy discriminant validity in simulation studies. Values this low indicate the constructs are almost entirely independent. This range is useful as a benchmark but is not a requirement. Most real-world measurement models produce HTMT values between 0.40 and 0.80, which is perfectly acceptable.

Bootstrapping and confidence intervals. A point estimate of HTMT is not enough for rigorous inference. You should run bootstrapping (typically 5,000 resamples) to generate a 95% confidence interval around each HTMT value. The decision rule is: if the upper bound of the confidence interval is below 1.0, you can be confident that the two constructs are distinct. SmartPLS, the R semTools package, and ADANCO all support bootstrapped HTMT confidence intervals.

If your point estimate is 0.87 but the upper bound of the confidence interval is 0.98, you are in a much stronger position than if the point estimate is 0.87 and the upper bound is 1.05. The confidence interval tells you how much uncertainty surrounds your estimate, which a single number cannot. Reviewers increasingly expect to see bootstrap confidence intervals reported alongside point estimates.

Some researchers prefer bias-corrected bootstrap confidence intervals, which adjust for skewness in the bootstrap distribution. SmartPLS offers this option, and semTools supports it through the boot.ci.type argument. Bias-corrected intervals are slightly narrower than percentile-based intervals, but for most datasets the difference is minor.

Summary of threshold decision rules:

HTMT below 0.85: discriminant validity established at the strict level. Report with confidence.

HTMT between 0.85 and 0.90: borderline. Check bootstrap confidence intervals, inspect items, and justify theoretically.

HTMT above 0.90: discriminant validity not established. Do not treat the constructs as distinct without respecification.

Upper bound of bootstrap confidence interval above 1.0: constructs are statistically indistinguishable regardless of the point estimate.

Practical Interpretation Guide: Reading and Reporting Your HTMT Results

When you run HTMT in software, you typically get a matrix where each cell contains the HTMT value for a pair of constructs. The diagonal is blank because a construct compared with itself always produces an HTMT of 1.0. Your job is to scan the off-diagonal cells and verify that every value falls below your chosen threshold.

If all values are below 0.85, you are in the clear. Report the matrix, cite Henseler et al. (2015), and move on to your structural model. If one or two pairs sit between 0.85 and 0.90, you have a borderline situation that requires justification. If any pair exceeds 0.90, you have a serious measurement problem that must be resolved before proceeding.

Handling borderline values. If a pair lands at 0.87, you have three options. First, check the bootstrap confidence interval. If the upper bound is below 1.0, you can argue that discriminant validity is supported. Second, examine the items involved. Sometimes one poorly worded item is driving the overlap, and removing it brings the HTMT down. Third, if the constructs are theoretically related, you can justify using the 0.90 lenient threshold and cite literature supporting the conceptual overlap.

Forum discussions on Reddit’s AskStatistics and SmartPLS forums reveal that many researchers face borderline HTMT values and feel stuck. The most common advice from experienced methodologists is to focus on the confidence interval rather than the point estimate alone. A borderline point estimate with a tight confidence interval that stays below 1.0 is far more defensible than a lower point estimate with a wide interval that crosses 1.0.

What to do when HTMT is above 0.90. This is a serious issue that requires action. First, check for data entry errors or reverse-coded items that were not recoded. A single reverse-coded item left in its original scoring direction can inflate cross-construct correlations dramatically. Second, check whether two constructs are really measuring the same underlying concept. If “Trust” and “Credibility” produce an HTMT of 0.94, they may need to be merged into a single construct. Third, consider whether common method bias is inflating correlations across the board.

Fourth, inspect the indicator correlation matrix for unusually high cross-loadings. One item that correlates more strongly with another construct than with its own indicators can drag the entire pair’s HTMT above threshold. Removing or reassigning that item often resolves the problem. Fifth, if you have a small sample, collect more data. HTMT estimates stabilize as sample size increases, and what looks like a violation at n=80 may disappear at n=250.

Reporting guidance for academic papers. A clear reporting template looks like this: “Discriminant validity was assessed using the heterotrait-monotrait ratio of correlations (HTMT; Henseler et al., 2015). All HTMT values were below the recommended threshold of 0.85 (maximum HTMT = 0.72), indicating that discriminant validity was established for all pairs of constructs. Bootstrapping with 5,000 resamples confirmed that the upper bounds of all 95% confidence intervals were below 1.0.”

If you had a borderline pair, the template expands: “All HTMT values were below 0.90, with one pair (Trust and Commitment, HTMT = 0.87) falling between 0.85 and 0.90. Following the lenient threshold recommended for conceptually related constructs (Henseler et al., 2015), discriminant validity was supported. The upper bound of the 95% bootstrap confidence interval for this pair was 0.96, well below 1.0.”

Include the full HTMT matrix in an appendix or supplementary table. Some journals also expect you to report Fornell-Larcker results alongside HTMT, even though HTMT is the stronger criterion. Reporting both demonstrates thoroughness and satisfies reviewers who are accustomed to the older standard. Always cite Henseler, Ringle, and Sarstedt (2015) as the source for HTMT and include the full reference in your bibliography.

Reverse-coded items. If your survey includes reverse-coded items, they produce negative correlations with the other items on the same construct. Without taking absolute values, these negative correlations deflate the monotrait average and can artificially inflate the HTMT ratio. Always ensure your software uses absolute values (semTools does this by default with absolute = TRUE), or manually recode reverse items before computing HTMT in Excel. This is one of the most common sources of unexpected HTMT values reported in forums.

Multi-group analysis. If you plan to compare structural paths across groups (for example, male versus female customers, or employees in different regions), you should compute HTMT separately for each group. Discriminant validity that holds in the pooled sample may fail in a subgroup, or vice versa. Establishing measurement invariance, including discriminant validity, is a prerequisite for meaningful multi-group comparisons.

HTMT vs Fornell-Larcker Criterion: Which Should You Use?

The Fornell-Larcker criterion was the gold standard for discriminant validity for nearly three decades. It works by comparing the square root of each construct’s average variance extracted (AVE) against that construct’s correlations with all other constructs. The rule is: the square root of AVE for each construct should be greater than the construct’s correlation with any other construct.

It sounds reasonable, and for many years researchers applied it without question. But Henseler and colleagues ran extensive Monte Carlo simulations and found a serious problem. Fornell-Larcker fails to detect discriminant validity violations in a large percentage of cases, particularly when sample sizes are small, when constructs are highly correlated, or when indicator loadings are moderate rather than very high.

In some simulation conditions, Fornell-Larcker correctly identified discriminant validity problems in fewer than 20% of cases. That means four out of five times, it gave a false green light for constructs that were actually not distinct. HTMT, by contrast, maintained detection rates above 70% across the same conditions, and in many scenarios it detected problems in over 90% of cases.

Here is a quick comparison of the two approaches:

Method. Fornell-Larcker compares the square root of AVE to between-construct correlations. HTMT compares average between-construct indicator correlations to within-construct indicator correlations.

Data required. Fornell-Larcker requires AVE values from a factor analysis or composite-based model. HTMT works directly on the observed indicator correlation matrix.

Sensitivity. HTMT is significantly more sensitive to discriminant validity problems. Fornell-Larcker has a high false-negative rate, especially with correlated constructs.

Applicability. Both methods apply to reflective measurement models. Neither is appropriate for formative constructs.

Software support. Fornell-Larcker is built into nearly every SEM package. HTMT is built into SmartPLS, semTools, ADANCO, and available as a plugin for AMOS.

Recommendation. Report both for completeness, but rely on HTMT for your discriminant validity decision. Most current reviewers and methodologists treat HTMT as the primary criterion. If your HTMT passes but Fornell-Larcker fails, trust HTMT. If Fornell-Larcker passes but HTMT fails, you almost certainly have a real discriminant validity problem that Fornell-Larcker missed.

The HTMT2 variant offers an additional refinement by using the arithmetic mean instead of the geometric mean in the denominator. It addresses minor upward bias in the original HTMT formula and is recommended when your software supports it. In practice, HTMT and HTMT2 produce very similar values, and both use the same threshold guidelines. When in doubt, report HTMT2 as your primary statistic since it represents the most current methodological recommendation.

Researchers on academic forums frequently report switching from Fornell-Larcker to HTMT after reviewers requested it. Many PhD students discover HTMT late in their analysis process and have to redo their validation chapter. If you are early in your project, adopt HTMT from the start so you do not face rework later.

Calculating HTMT in Software: R, SmartPLS, and Excel

You do not need to calculate HTMT by hand for real datasets. Here is how to get it done in the three most common environments researchers use.

R with semTools and lavaan. The semTools package provides a dedicated htmt() function that works with lavaan model syntax. Install the packages, define your measurement model, and call the function:

library(semTools)
library(lavaan)
model <- ' SQ =~ SQ1 + SQ2 + SQ3
CSAT =~ CSAT1 + CSAT2 + CSAT3 '
htmt(model, data = mydata)

The function returns an HTMT matrix by default. It uses absolute correlations and computes HTMT2 by default. You can disable either by setting absolute = FALSE or htmt2 = FALSE. For bootstrapped confidence intervals, use the htmt() function within a bootstrapping wrapper or use the sampleFunc argument. The semTools documentation includes worked examples using the HolzingerSwineford dataset, which is a good starting point for learning the function.

The htmt() function in semTools also handles missing data gracefully. By default it uses the lavCor function from lavaan, which applies listwise deletion for continuous variables and pairwise deletion for ordered variables. You can override these defaults through the missing argument if your data requires a different approach.

SmartPLS. SmartPLS has built-in HTMT reporting for PLS-SEM models. After running your PLS algorithm, navigate to the “Discriminant Validity” section of the results report. You will see an HTMT matrix showing all construct pairs. To get bootstrap confidence intervals, run the bootstrapping procedure (choose 5,000 subsamples) and the HTMT confidence intervals will appear in the bootstrapping report. SmartPLS uses absolute correlation values by default since version 3.2.1, and the software cites Henseler et al. (2015) directly in its output.

SmartPLS also offers an HTMT+ variant, which extends the standard HTMT to handle models where some constructs have only two indicators. The standard HTMT formula requires at least two indicators per construct, and HTMT+ adjusts the calculation to work with the minimum case. If you have any two-indicator constructs, HTMT+ ensures the output remains meaningful.

Excel manual calculation. If your software does not support HTMT (notably, IBM SPSS AMOS does not have a built-in function), you can compute it in Excel. First, generate the indicator correlation matrix using SPSS or R. Then, for each pair of constructs, identify the heterotrait-heteromethod cells (the cross-construct correlations) and average them. Next, average the within-construct correlations for each construct. Finally, compute the geometric mean of the two within-construct averages and divide the heterotrait average by that geometric mean. Repeat for every pair.

The Excel approach is tedious but works reliably. For a model with five constructs and four indicators each, you will compute 10 separate HTMT values manually, each involving averaging 16 cross-correlations and 6 within-correlations per construct. Use the AVERAGE and SQRT functions to streamline the arithmetic, and lay out each pair in its own worksheet tab for clarity.

James Gaskin’s Stats Tools Package, a free AMOS plugin, automates HTMT calculation and is widely recommended in forum discussions. If you use AMOS, this plugin is the most efficient path to HTMT results. It generates the full HTMT matrix and bootstrap confidence intervals directly from your AMOS output without requiring manual Excel work.

Online calculators. Jorg Henseler maintains an HTMT calculator on his website (henseler.com), which accepts a correlation matrix as input and returns the HTMT matrix. This is useful for quick checks or for verifying software output, though it does not support bootstrapping. Always cross-check surprising software results against a manual calculation or an independent tool.

Limitations and Common Pitfalls

HTMT is the best available discriminant validity tool for most reflective measurement models, but it is not perfect. Understanding its limitations helps you avoid misinterpretation and overconfidence in your results.

Reflective models only. HTMT assumes that indicators are reflective, meaning they are caused by the underlying latent construct. It does not apply to formative measurement models, where indicators cause the construct. Applying HTMT to formative constructs produces meaningless results because the correlation patterns of formative indicators do not reflect the internal consistency that HTMT is designed to evaluate.

Sample size sensitivity. With small samples (below 100), correlation estimates become unstable, and HTMT values can swing significantly between different subsets of your data. Bootstrapping is especially important with small samples because it reveals how much uncertainty surrounds your point estimates. As a general guideline, aim for at least 10 observations per indicator and ideally 200 or more total responses for stable HTMT estimates.

Inconsistent results across estimators. Different SEM estimation methods (maximum likelihood, PLS, composite-based) produce slightly different correlation estimates, which in turn produce slightly different HTMT values. This is normal and not a cause for alarm, but it explains why researchers sometimes report different HTMT values for what appears to be the same model in different software. If you switch software mid-project, recompute HTMT from scratch rather than carrying over values.

HTMT does not replace convergent validity checks. A passing HTMT matrix tells you your constructs are distinct from each other. It does not tell you that each construct is well-measured. You still need to check indicator loadings (above 0.70), composite reliability (between 0.70 and 0.95), and AVE (above 0.50) to confirm convergent validity before moving to your structural model.

Common method bias. If all your indicators come from a single self-report survey administered at one time, common method bias can inflate correlations across the board. This can push HTMT values above threshold even when constructs are conceptually distinct. Consider Harman’s single-factor test or a common latent factor approach to check for this issue. If common method bias is present, HTMT may overstate the true overlap between your constructs.

Single-indicator constructs. HTMT requires at least two indicators per construct to compute within-construct correlations. If you have single-indicator constructs in your model, HTMT cannot be calculated for any pair involving them. You will need to rely on theoretical arguments or alternative validity checks for those pairs.

HTMT does not test causal distinctiveness. Two constructs can have a low HTMT and still be causally related in ways that make them redundant for practical purposes. HTMT tests statistical distinctiveness at the measurement level, not theoretical redundancy at the conceptual level. Always pair your HTMT results with a clear theoretical argument for why your constructs should be treated as separate.

How to Interpret a Heterotrait-Monotrait Ratio: Key Takeaways

Learning how to interpret a heterotrait-monotrait ratio is one of the most practical skills you can develop as a researcher working with structural equation modeling. The core rules are straightforward: aim for HTMT values below 0.85, never accept values above 0.90, and always check bootstrap confidence intervals to confirm the upper bound stays below 1.0.

Remember that HTMT works on the observed correlation matrix, requires reflective indicators, and is more sensitive than the older Fornell-Larcker criterion. Report both methods in your paper for completeness, but base your discriminant validity decision on HTMT. When values are borderline, look at confidence intervals, inspect individual items, and draw on theoretical justification for your constructs.

If you follow the calculation steps and interpretation guidelines in this article, you will be equipped to validate your measurement model with confidence and to defend your discriminant validity claims to reviewers, advisors, and colleagues. HTMT is not a formality to check off on the way to your structural model. It is a substantive test of whether your measurement design actually works, and treating it with the seriousness it deserves will improve the quality and credibility of your entire research project.

FAQs

What is the acceptable value of HTMT?

An HTMT value below 0.85 (strict threshold) or below 0.90 (lenient threshold) between two reflectively measured constructs indicates that discriminant validity has been established. Values above 0.90 mean the constructs are too similar to be treated as distinct.

What is the heterotrait monotrait ratio?

The heterotrait-monotrait ratio (HTMT) is a discriminant validity measure that compares the average correlation between indicators of different constructs (heterotrait-heteromethod) to the geometric mean of the average correlations within each construct (monotrait-heteromethod). It was introduced by Henseler, Ringle, and Sarstedt in 2015.

What is the rule of thumb for HTMT?

The rule of thumb for HTMT is that values should be below 0.85 for a strict pass or below 0.90 for a lenient pass. Values in the range of 0.011 to 0.389 are considered ideal. If bootstrapping is used, the upper bound of the 95% confidence interval should be below 1.0.

What is the difference between Fornell-Larcker and HTMT?

Fornell-Larcker compares the square root of average variance extracted (AVE) to between-construct correlations. HTMT compares average between-construct indicator correlations to within-construct indicator correlations. Monte Carlo simulations show HTMT is significantly more sensitive and detects discriminant validity problems that Fornell-Larcker misses.

Can HTMT be used for formative constructs?

No. HTMT is designed for reflective measurement models where indicators are caused by the underlying latent construct. It does not apply to formative measurement models, where indicators cause or define the construct. Using HTMT with formative indicators produces meaningless results.

What do I do if my HTMT value is above 0.90?

Check for reverse-coded items that were not recoded, verify there are no data entry errors, and consider whether the two constructs are actually measuring the same underlying concept. If the constructs are theoretically distinct, run bootstrapping to check the confidence interval. If the upper bound exceeds 1.0, you may need to merge the constructs or remove problematic items.

Leave a Comment