Short answer: Generally, no. Users typically do not need to be retested in Develop.
Why We Don’t Recommend Frequent Retesting
Stable Traits: Develop measures underlying tendencies - how behaviors, motivations, and cognitive patterns show up at work. These are stable over time.
Performance Evolves, Traits Don’t: Employees may grow in skill, experience, and performance, but their baseline effort patterns stay consistent.
Consistency Creates Confidence: Keeping the same results across time helps employees and managers build strategies they can return to, rather than expecting scores to change.
What to Do Instead of Retesting
Update Job Titles: If someone changes roles, update their job title in the platform so their results are framed in the right job context.
Revisit Action Plans: Encourage managers and employees to update development goals regularly. Growth is reflected in progress and outcomes, not in a retest.
Use Results Over Time: Insights stay relevant for coaching, team dynamics, and career planning even as job responsibilities evolve.
When Not to Retest
To “get a better score”
Shortly after first completing the assessment
As a way to measure short-term development progress
Bottom line: Retesting is rare and usually unnecessary. Development shows up in applied behaviors, coaching conversations, and performance - not in new assessment results.