Advisor Intelligence · · 7 min read
Career Trajectories: Why Equal Tenure Does Not Mean Equal Risk
Two advisors can have the same tenure and completely different trajectories. Context turns a date into a useful management signal.
By Jan Kluz, Founder, Emable
Jan builds data and AI products for European financial distribution, with a focus on advisor intelligence, decision validation and responsible use of regulatory data.
Two advisors have worked with their current firms for four years. A simple retention dashboard puts them in the same category. A useful intelligence system asks what those four years mean inside each person’s broader trajectory.
Tenure is a date difference. Stability is a pattern.
The company context changes the signal
Every organisation has its own movement curve. In one firm, most early departures may happen during the first eighteen months. In another, movement may concentrate much later. Four years can therefore describe someone who has moved well beyond the company’s typical risk period, or someone approaching it.
This is why a universal rule such as “three years equals stable” is weak. The same tenure needs to be interpreted against the environment in which it occurred.
Emable’s approach compares an advisor’s position with relevant peer and company histories while keeping the underlying observations visible. The output is a management signal, not a claim that a departure will happen.
Prior movement matters at the edges
The number of previous company relationships is often overused. Most people with one or two documented relationships do not become meaningfully different because one count is higher. The signal becomes more relevant at the extremes, where a repeated pattern of short relationships may deserve a different retention or recruitment conversation.
Even then, interpretation matters. Product-authorisation changes can look like job moves if the data is not resolved correctly. A person can also have legitimate parallel relationships across product categories. Career analysis must distinguish these situations before assigning meaning to the count.
Product breadth is not a personality test
Managers sometimes assume that a broad product portfolio signals commitment, while specialisation signals risk, or the reverse. The data rarely supports such a simple conclusion.
Product coverage is useful for understanding fit, capability and market position. It should not be converted automatically into a retention judgement. A specialist can be deeply established in a strong niche. A generalist can hold many registrations without meaningful production in each category.
The better question is how the portfolio changed over time and whether the change fits the person’s wider career direction.
Use signals to improve conversations
Retention intelligence should help managers allocate attention, not label people.
A useful workflow might identify that an advisor:
- is entering a historically important tenure window for the firm;
- has recently changed one product-company relationship;
- works in a region with increased competitive movement;
- has a career history that contains several short relationships;
- still has incomplete or ambiguous records that reduce confidence.
None of these facts proves intent. Together, they can justify a timely conversation about support, progression, economics or role design.
Avoid self-fulfilling scores
Risk scores become dangerous when managers treat them as verdicts. A person marked “high risk” may receive less trust or fewer opportunities, creating the very departure the model was meant to anticipate.
Emable therefore treats career signals as explainable indicators. Managers should see the contributing factors, the confidence level and the information the model does not possess. Sensitive employment decisions remain human decisions.
The objective is not to predict people as if they were machines. It is to notice patterns early enough that leaders can respond with judgement and context.
Two equal tenure values may hide two different stories. The value of advisor intelligence is making those stories easier to inspect without pretending that the data knows the ending.
Methodology and limitations
The patterns discussed are observational signals from Emable's advisor-history model. They are not deterministic predictions and should be combined with manager judgement, current performance and direct conversation.