Does a High Hogan Development Survey Percentile Mean High Risk?

Does a high HDS percentile mean a problem is likely?

No. A high percentile in a Hogan Development Survey (HDS) report does not, by itself, mean there is a high probability that a particular problem will happen. It locates a score relative to the report’s comparison group. Hogan gives that score a separate interpretation: an elevated result may point to a work-related tendency that could become more visible under strain. A probability forecast makes a stronger claim. It would need evidence connecting a defined score range to a clearly specified behavior, in a relevant group and setting, over a stated period. Those are three different readings of a number: relative rank, conditional risk, and forecast probability.

The distinctions matter because an HDS report can put percentiles and risk categories side by side. In the Hogan Development Survey Insight Sample Report, a percentile describes standing in a population; separate bands label levels of risk. The sample does not give event rates or a method for converting a percentile into the chance that a named behavior will occur. Hogan’s HDS overview describes tendencies that may emerge under increased strain and says the assessment can help identify potential performance risks. That is a meaningful reason to take an elevated result seriously, but it is not a personal forecast.

The reading is neither “this will happen” nor “the score means nothing.” Treat the result as a focused question: in which situations might the tendency matter, and what observable examples support or complicate that interpretation? The report can guide that inquiry without deciding it in advance. The sections that follow separate what the percentile ranks, what Hogan means by risk, and what evidence a genuine probability claim would require. Do not read percentile digits as the percentage chance of a problem.

Sources: Hogan Development Survey Insight Sample Report; Hogan Development Survey | Hogan Assessments

What does a percentile rank, and what does it leave unanswered?

A percentile answers a comparison question: where does this score sit relative to scores in a specified group? It does not answer how likely a particular behavior is to occur. A score is the result produced by the assessment; the percentile is a position assigned by comparing that score with a reference population. Hogan’s *Hogan Development Survey Insight Sample Report* explains percentile scores as the proportion of the population scoring at or below the person’s score. Its example says a score at the 75th percentile is higher than about 75 percent of scores in the report’s stated norm frame. The remaining portion of that comparison is at or above the score, subject to ties and the report’s rounding. The important point is the reference: “75th” refers to relative standing among those scores, not to a 75 percent chance of an event. The sample report identifies a global norm for its illustration; a reader should check their own report for the norm actually used. The *Standards for Educational and Psychological Testing* describe percentile ranks as norm-referenced interpretations: they show standing in relation to a defined population. A norm-referenced result gains meaning from the group used to make the comparison. If that group differs from the one relevant to a reader’s situation, the percentile may still accurately describe the stated comparison while offering a less fitting reference for a particular decision. The percentile alone does not reveal how the comparison group was assembled, whether it matches the reader’s role or language, or whether the score would be the same under another norm or scoring version. Those are questions about the report’s frame, not hidden event odds inside the percentile. Consider a hypothetical illustration, not an HDS result: two people receive the same percentile on a scale. One works in a role with frequent deadlines and visible disagreement; the other has more routine work and fewer such situations. The shared rank does not show whether either person has displayed a related behavior, how often it occurred, or what happened afterward. Nor does it establish that both will respond alike when pressure rises. Those conclusions would require observations and context beyond the rank. The example shows why the comparison number cannot stand in for a personal history or forecast. A percentile is not a percentage correct, a severity rating, or a probability. It is not a count of occasions on which a tendency appeared. Even when the assessment’s interpretation attaches practical meaning to an elevated score, the percentile itself reports only relative position in its norm frame. To interpret it responsibly, first identify that frame and keep the rank separate from any narrative about possible work tendencies. Then ask what behavior, setting, and evidence the narrative concerns. The percentile can locate a score; by itself it leaves the event, timing, frequency, and consequences unanswered.

Sources: Hogan Development Survey Insight Sample Report; Standards for Educational and Psychological Testing

What does Hogan mean by risk in the HDS?

Risk in the Hogan Development Survey (HDS) is Hogan’s interpretation that a measured tendency may interfere with work in relevant circumstances. It is a meaningful warning for reflection, but the public materials reviewed here do not define a risk band as the probability that a named event will happen to one person. A tendency is a pattern that may be expressed; an event is a particular action or consequence in a particular situation. Between them lie conditions that can strengthen, redirect, or contain the tendency.

Hogan’s official “Hogan Development Survey” page describes the HDS as measuring 11 personality scales and 33 subscales, with qualities that may emerge under increased strain. It gives examples: drive may become ruthless ambition, while attention to detail may become micromanaging. These illustrate how a strength can become counterproductive when overused; they do not claim everyone with an elevated score behaves that way. A scale description points to a possible work pattern, but establishes neither its frequency nor its consequences.

Whether a tendency becomes visible depends partly on setting. Pressure, role demands, opportunity, relationships, and self-management can matter. A decision-heavy role may call for action with incomplete information. These are practical examples, not HDS scoring rules. They frame a useful question: when, if ever, does the report’s description match observable behavior, and what follows? A tendency may be inconsequential in one task and costly in another, or remain managed rather than expressed.

Hogan’s “FAQ Blog Series: The Hogan Development Survey” addresses elevated scores with no observed performance effect. It says elevated scores indicate risk of negative workplace behavior, while self-awareness, coaching, and development can help manage that risk. It adds that stressful work may elicit tendencies more than routine work, although jobs vary. This challenges a deterministic reading: Hogan describes a manageable risk whose expression partly depends on circumstances. The post explains intended interpretation; it is not an independent estimate of outcome frequency.

The official 2016 “Hogan Development Survey Insight Sample Report” says elevated-score behaviors can be strengths but may derail work relationships when overused. It presents results as prompts for self-awareness and context-based discussion with a coach. Use the risk label to select a development question, not attach a fixed defect to a person. If a report raises concern about reluctance to decide, look for delayed decisions and counterexamples. The report cannot tell whether hesitation reflected a tendency, missing information, unclear authority, or a sensible response to serious consequences.

The risk label is neither empty nor a personal forecast. It identifies a potential difficulty worth checking against relevant work conditions. Treat it as a development signal: translate the scale description into observable terms, then compare examples and counterexamples. Hogan’s materials support taking the interpretation seriously while examining context; they do not turn a high percentile or band into an individual event probability.

Sources: Hogan Development Survey | Hogan Assessments; FAQ Blog Series: The Hogan Development Survey; Hogan Development Survey Insight Sample Report

How is a risk band different from an event probability?

A risk band and an event probability answer different questions. A band places a score inside an interpretive category, such as low, moderate, or high risk. A probability estimates how often a defined outcome occurs among a defined group over a stated period. Their shared numerical format does not make them interchangeable. The distinction is visible in Hogan's 2016 Insight sample report. It defines percentile scores as relative standing in a population, then assigns score ranges to four risk categories: 70–89 is moderate risk and above 90 is high risk. Those thresholds show how this report organizes its interpretation. It states no behavior-specific event rate, time horizon, or chance such as “this problem occurs in X out of Y cases.” “High risk” signals the report's intended concern; it does not itself say that a particular problem is highly probable for the person. A category can still be useful without being a forecast. It compresses a score into a cue: this scale may deserve discussion or attention before a work difficulty develops. It can guide questions when its description fits the pressures of a role. But a category boundary is a rule for classifying scores, not a point at which a person's behavior suddenly changes. Scores just above and below a threshold need not mark meaningfully different people. The Standards for Educational and Psychological Testing explain that cut scores can aid decisions, while misclassification is generally more likely for people whose scores are close to a cut point. Read bands as summaries, not cliffs. The Standards also show why a score can, in principle, support more than relative ranking. A test score may be linked to a criterion: an outcome or defined domain it is intended to help interpret. The same score can support norm-referenced and criterion-referenced interpretations when suitable methods validate each one. Thus scores can carry evidence about outcomes beyond rank. But support for a criterion interpretation must come from evidence tied to that criterion. A scale's category label alone does not establish a personal probability. To justify probability language, a provider would need to define the problem, the population studied, the period, and how scores relate to that outcome. It should show how predicted rates match observed rates, with uncertainty. A relationship with broad job-performance ratings would not yield the chance of a specific missed deadline or strained exchange without evidence for that behavior and context. Hogan's Personality Assessment FAQs describe local validation work that matches assessment results with job-performance data to study predictive validity in particular contexts. This shows outcome-linked research depends on setting and criterion. It does not mean every HDS band is a calibrated probability: the FAQ gives no rate for a named behavior, time horizon, or individual conversion. Thresholds may differ by version, so check the report received. When a report or conversation uses odds-like language, ask: Is this number my percentile, a score range, a descriptive risk category, or a forecast? If it is a forecast, what precise outcome and period does it cover, which comparison group supports it, and where are observed and predicted rates shown? If those details are absent, treat the label as an interpretive prompt rather than a quantified chance. It can prioritize a coaching question; it cannot answer how likely a specific problem is to happen to you.

Sources: Hogan Development Survey Insight Sample Report; Standards for Educational and Psychological Testing; Hogan Personality Assessment FAQs

Which norm and report version does the percentile depend on?

The percentile is meaningful only against the reference group and scoring version used for that report. Hogan’s public FAQ says HDS norms draw on more than 100,000 working adults, but that figure does not identify the comparison selected for an individual result. The FAQ also recommends interpreting scores in light of current job context and future goals. Before comparing your percentile with another person’s, or with an earlier report, find out what population and scoring system produced each number.

A norm group is the population used as a reference when a score is expressed as a percentile. A broad global norm and a locally relevant norm are different comparison frames; neither is automatically better for every purpose. Ask whether the reference population fits the comparison you want to make. Hogan’s FAQ describes its norms as based on working adults, but does not show which norm was applied in every report or the composition of the comparison used for one person. Sample size alone cannot tell you whether its language, region, or job mix suits your situation.

Because a percentile is relative, a difference between reports using different comparison groups need not mean the underlying response pattern changed by the same amount. Similar percentiles from unlike norms likewise do not establish identical scores or circumstances. Without the report’s norm label and scoring details, the comparison cannot be resolved from the percentile alone.

Version matters too. Hogan’s 2016 Insight HDS Sample Report displays “Norm: Global” and explains its percentile format. It is a dated sample: its label shows what that example used, not what a current report necessarily uses. Hogan’s page Four-Point Assessments and Norm Upgrades says HPI and HDS adopted four response options in 2018, then Hogan updated its global norm and all 39 local norms in 2023. The page also describes a new scoring method intended to make finer distinctions in main and subscale scores. These updates make report date and version relevant when interpreting a percentile or comparing results over time. They do not identify the norm or scoring method selected for a particular report.

Ask the coach or provider: What is the report date and HDS version? Which norm is named, and what geography or population does it represent? Was a global or local norm selected? If comparing with an earlier report, did the norm or scoring method change, and are the scores comparable? Hogan’s public pages describe options and updates, but cannot answer those report-specific questions. The report or its administrator must supply that information.

Do not infer that an updated norm makes an earlier result wrong, or that a local norm is inherently more accurate for every reader. The narrower conclusion is that a percentile needs its frame. Until the norm, language, scoring version, and intended comparison are clear, treat apparent changes across reports cautiously. This check keeps relative standing in its proper role; it still does not turn a percentile into the probability that a particular behavior will occur.

Sources: Hogan Personality Assessment FAQs; Four-Point Assessments and Norm Upgrades; Hogan Development Survey Insight Sample Report

What does HDS validation evidence establish—and what does it not?

Yes, there is evidence worth taking seriously, but its reach is narrower than a personal forecast. Criterion-related validity means scores relate to a specified outcome, such as a performance rating, in a studied setting. Predictive validity asks whether scores help estimate an outcome measured later or otherwise treated as a criterion. These terms describe evidence about a measure and outcome; they do not turn a percentile into the probability that one person will show a particular behavior.

In Hogan’s 2014 “Incremental Validity” summary, the research question was whether adding HDS scores improves prediction of overall job-performance ratings beyond the Hogan Personality Inventory (HPI). Hogan selected 25 archived studies with HPI data, HDS and/or values data, overall performance ratings, and matched assessment and performance records for at least 50 incumbents per study. The HPI-only analysis covered 25 studies and 2,621 people; the HPI-plus-HDS analysis covered 20 studies and 1,933 people. The reported sample-weighted correlation rose from R = .29 for HPI alone to R = .35 for HPI plus HDS, while R-squared rose from .09 to .13. This supports an aggregate claim that HDS added predictive information in the subset of studies analyzed. It is not an event rate: the outcome was an overall performance rating, the included scales were selected through regression, and the report does not give the chance that a person at a specified percentile will experience a named problem. Because these are selected archival studies, estimates should not be generalized across roles or report versions.

Different criteria and populations can produce a different pattern. The 2010 “Exploratory Study on the Construct Validity of Derailment Factors and their Effect on College Life Effectiveness” examined 233 Korean college students who had applied to a university leadership program. Its abstract reports that four HDS factors were negatively related to all of the study’s college-life performance and well-being criteria; five other factors were positively related to performance and well-being; and two factors had no particular relationship with most measured criteria. Regression analyses found incremental variance for four factors on performance and well-being. This is evidence against treating every HDS scale as a uniform warning sign in every setting. It is also bounded evidence: college-life criteria in one applicant sample do not establish how working adults will behave in a particular job, much less an individual’s absolute odds.

The 2016 Hogan technical report makes the design dependence visible. Its case concerns screening sales-representative applicants at one company. Hogan describes reviewing the job, convening nine subject-matter experts, and using job-family meta-analysis and synthetic or job-component validity methods to identify predictors for that role. Its support for selected HDS scales is therefore tied to the job analysis, criteria, and evidence assembled for that application. A role-specific study can strengthen a defined use when the criterion and population fit; it cannot silently answer a different question about a specific adverse episode. A probability for one person would require a named behavior, relevant population and setting, time horizon, and evidence showing calibrated outcome rates across score levels, with uncertainty reported. Neither correlation nor incremental prediction alone supplies those ingredients.

Sources: Incremental Validity; Exploratory Study on the Construct Validity of Derailment Factors and their Effect on College Life Effectiveness; Sample Tech Report

How should uncertainty change the way you read one high score?

Treat a high score as one imperfect measurement and seek repeated, context-specific evidence before concluding that the described behavior is present or likely. The score can guide a focused question; it cannot replace examples, counterexamples, or an outcome study that matches the claim. A percentile locates a score in a comparison group; a risk label summarizes an assessment interpretation. Neither settles how a tendency appears in one role or over time. Reliability concerns score consistency or precision under specified conditions; it is not prediction of an event. The Standards for Educational and Psychological Testing explain that estimates depend on the source of variation measured. Internal consistency describes how items relate and may not capture changes across days. Read a coefficient with its method and purpose, not as a guarantee that each classification is stable. A historical HDS study illustrates the need for context. Innovation and the “Dark Side” of Personality (2008) used the 154-item HDS with a convenience sample of 207 participants from several occupational settings. The authors reported mean internal-consistency alpha of .62 across 11 dimensions; Dependent, Passive-Aggressive, and Detached were lower, prompting caution. This is evidence about score consistency for that version and sample, not a current universal estimate or an error interval for your score. The study examined links with self-reported innovative characteristics, not the probability of a named workplace problem. Internal consistency is not a verdict about accuracy. Items can hang together without yielding a calibrated event chance; a moderate estimate also does not settle whether a score relates usefully to an external criterion. The Standards call for measurement error information in reported-score units, including conditional estimates when appropriate. Near a risk-band boundary, uncertainty could matter. Without relevant error information for that scale, version, and norm, do not invent a margin or assume the boundary marks a sharp change. Turn the report narrative into an observation plan. This is an editorial method for reflection, not a validated instrument. Translate its description into an observable action, such as dismissing a colleague’s concern before checking it, if that is what the report describes. Ask when it might occur, perhaps during disagreement or under a tight deadline. Those contexts are questions to investigate, not proof. Look for more than one episode and seek counterexamples as deliberately as confirming examples. Did the action recur across situations, or was there one unusual exchange? Were there times the person received criticism with curiosity or changed course with new information? Appropriate feedback may clarify impact, but one recollection cannot settle a trait interpretation. The aim is a narrower account of what happened, under what conditions, and with what consequence. A qualified coach can help keep discussion developmental. The score alone establishes neither diagnosis nor a basis for a high-stakes employment decision. A probability claim would require evidence linking the HDS score range to a defined outcome, in a relevant population, over a stated period. It should report how predicted probabilities match observed rates, alongside uncertainty and base rates. The Standards distinguish score interpretation from criterion evidence: accuracy depends on outcome and purpose. A relationship with a broad performance rating cannot establish whether one person will show a specific behavior. Hogan’s FAQ describes matching assessment and job-performance information for local validation, making context central. Until evidence is available for the specific claim, the conclusion should remain modest. A high HDS score can prompt a question about a possible tendency and when it may matter. Examples, counterexamples, context, and feedback can refine reflection; they do not convert a percentile into an event rate. A matched, calibrated study could change the conclusion for a defined outcome. In its absence, treat the report as a starting point for inquiry, not a forecast.

Sources: Innovation and the “Dark Side” of Personality; Standards for Educational and Psychological Testing; Hogan Personality Assessment FAQs

What should you do next with the report?

Keep a high HDS score in its proper role: it describes relative standing in a comparison group and, in Hogan’s interpretation, may flag a work tendency worth examining under relevant conditions. It does not establish that a particular problem will happen. Before comparing the score with another person or an earlier report, ask which norm and report version were used. Hogan’s FAQ recommends interpreting results in the context of current job and future goals. Then translate the scale description into an observable question: in what situations might this response appear, what effect would it have, and what examples point the other way? Discuss those examples with an appropriately trained coach rather than treating the score as a verdict. The practical distinction is simple: percentile means rank; HDS risk language suggests a possible tendency under conditions; probability requires evidence linking a defined score range to a defined outcome in a relevant population and period. For a separate reflection prompt, the [Work Pattern Report](/assessment) covers ten decision-and-collaboration continuums, including planning, feedback, conflict, and change. It is a low-stakes self-report, not an HDS interpretation. Its result provides no norm, cutoff, type, or selection score, and it is not a hiring score, diagnosis, or job recommendation. Use it if naming your work patterns would help you prepare concrete observations for a conversation.

Sources: Hogan Personality Assessment FAQs; Work Pattern Report

Questions readers ask