Skip to main content

How Often to Re-Test (and When Not To)

Re-testing is rarely needed - Develop measures stable traits. Focus instead on updating job titles and applying insights over time.

P
Written by Product
Updated this week

Develop is designed to provide enduring insights, not short-term snapshots. Because the assessment measures stable traits, most users will only ever need to take it once.


Why We Don’t Recommend Frequent Re-Testing

  • Stable Traits: The attributes measured in Develop (behavioral, cognitive, and motivational) don’t change significantly over time.

  • Performance vs. Traits: While someone’s performance can and should grow with experience, coaching, and feedback - their underlying effort patterns remain consistent.

  • Consistency Builds Trust: Keeping results stable helps employees and managers build long-term development strategies, rather than chasing new scores.


What to Update Instead

  • If someone’s job title changes, update it in the platform. This ensures their results are framed in the right job context.

  • Encourage employees to revisit their action plans and goals regularly, since growth happens in how they apply insights - not in re-taking the assessment.


When Not to Re-Test

  • To “improve” a score: Low scores don’t mean poor performance - they indicate areas that may take more effort.

  • After a short time: Retesting within months or even a year will almost always yield similar results.

  • As a measure of progress: Growth shows up in behaviors, feedback, and achievements - not in shifting trait scores.


Bottom line: Re-testing is rare and usually unnecessary. Instead, focus on how results are applied in real work and how performance evolves with experience, support, and practice.

Did this answer your question?