Employee Life Cycle

Most formulations of the life cycle use a similar set of stages, and the exact naming matters less than the sequence.

• Attraction, where the organisation becomes known to people who might work for it.
• Recruitment, from application through assessment to offer.
• Onboarding, covering the administrative setup and the first period in the role.
• Development, being everything that grows capability, including internal moves.
• Retention, which is not a separate stage so much as a continuous outcome of the others.
• Exit, whether voluntary or not, and whatever follows it.

The model earns its place by making the whole relationship visible at once. Organisations tend to manage these stages in separate teams with separate systems and separate measures, and the cycle is a reminder that the employee experiences one continuous thing.

It is worth being clear that the stages are a description rather than a mechanism. Nothing follows automatically from drawing the diagram, and the value comes entirely from what it exposes.

The stages themselves are usually managed adequately. The transitions between them are not, because each one crosses both a team boundary and a system boundary.

The first row causes the most immediate damage and is the easiest to fix. Where recruitment and the employee record are separate systems, someone re-types the new joiner's details, and that transcription is where wrong bank accounts, misspelled names and incorrect start dates enter payroll. A new employee whose first salary is wrong has formed a view of the organisation that takes a long time to revise.

The fourth row is the most expensive and least noticed. Organisations that make internal application harder than external application train people to change employer in order to change role.

Drawn as a circle or a line, the model suggests a single pass through the stages. Real relationships do not work that way.

An employee may move roles four times, be promoted twice, take a long absence, change location and return to a previous team, all without exiting. The middle of the cycle is not a stage but a long period in which several of the stages recur.

Treating it as linear produces two errors. Onboarding is designed only for external joiners, so someone moving internally into a substantially different role gets no induction at all, which is one of the more common causes of a failed internal move. And development is treated as an event following onboarding rather than as something that recurs, so it stops happening for anyone past their first year.

The correction is to treat any significant transition as a joining event of its own, including internal moves, returns from long absence and changes of manager. Each of those has the same characteristics as an external join: unfamiliar context, unclear expectations and a need for deliberate orientation.

Each stage has its own familiar measures, and measuring only within stages hides the connections that matter.

• Source of hire against twelve-month retention, which tells you whether a cheap channel is producing short tenures.
• Onboarding completion against first-year performance, which is the check on whether the induction does anything.
• Internal move rate against attrition, since organisations with low internal mobility usually export their promotions.
• Manager against engagement, absence and attrition together, because these three move as a group.
• Exit reason against the stage at which the problem originated, which is the loop back to the beginning.

The last of these is the point of thinking in cycles at all. An exit reason of no progression is information about the development stage. An exit at four months is information about recruitment or onboarding rather than about retention.

Reading exits back to their origin is the single most useful analytical habit the model supports, and it requires the recruitment, employment and exit records to be connected. Where they sit in different systems, the connection is made by matching names in spreadsheets, and it usually is not made at all.

The risk with life cycle thinking is building an elaborate programme for every stage, which produces process without producing improvement.

A more productive use is diagnostic. Look at where people are actually lost: the stage at which candidates drop out, the point at which new joiners decide it was a mistake, the tenure at which resignations cluster, the transition after which performance dips. Each of those localises a problem to a stage or, more often, to a handoff.

Then fix the specific transition rather than redesigning the whole cycle. Most organisations have one or two badly broken handoffs and several adequate ones, and the return comes almost entirely from the broken ones.

The other durable use is as a check on ownership. Every stage usually has an owner and the handoffs usually have none, which is precisely why they fail. Assigning the transition to someone, rather than the stages either side of it, addresses the actual gap.