The Ramp: Joiners, Leavers and the Months Between
Why a new person is not capacity on their start date, how to put the ramp in the account, and the leaver effect that is larger than the joiner one.
A person who joins on the first of the month does not add their hours to the plan on the first of the month. They add a fraction that rises over weeks or months, and they subtract time from the people around them while it rises.
The reconciliation in “The Ramp: Joiners, Leavers and the Months Between” is strongest when assumptions and current work records can be examined separately. A team considering a transparent small business time tracking process for small business time tracking can add time and project context, with transparent settings, limited access and a clear correction route around consequential decisions.
Plans that pro-rate joiners by calendar date produce a predictable overestimate, every time, in the same direction.
As a separate benchmark for “The Ramp: Joiners, Leavers and the Months Between”, see G2 software and operations resources. Keep source data, calculation, override and decision visible as distinct steps.
The two halves of the ramp
The joiner's own productivity, which starts near zero and rises. And the drag on everybody else: onboarding, questions, review, pairing, explaining things that are not written down.
The second half is routinely omitted, which means a plan can show capacity rising in a month when it is actually falling.
How long it takes
Entirely dependent on the work, the domain and how much is documented. What matters for the account is not a general figure but the organisation's own, which can be estimated by asking three people who joined in the last two years when they felt useful.
That question produces a usable number in a day. In knowledge work the answers cluster between one and six months and the variance is mostly about documentation.
Where the ramp sits in the account
| Period | Joiner contributes | Team pays |
|---|---|---|
| Month 1 | near zero | heavy: induction, pairing, questions |
| Month 2 | a quarter | moderate |
| Month 3 | a half | light |
| Months 4–6 | rising to full | occasional |
That shape is illustrative rather than universal, and an organisation should fill it in from its own experience. What matters is that both columns exist.
The leaver effect, which is larger
A person leaving removes capacity before their last day: notice periods contain handover, knowledge transfer, documentation that was never written, and a visible drop in engagement that nobody should pretend away.
They also remove capacity after their last day, because what they knew is now being reconstructed by somebody else. The account should carry both, and almost none do.
The replacement gap
Between a leaver and a productive joiner there is a gap of notice period, plus recruitment, plus notice on the other side, plus the ramp. Three to nine months is ordinary.
A plan that shows a post as filled because a requisition was approved is describing a budget rather than a capacity. The account should hold the expected productive date, not the start date.
Internal moves
Somebody moving between teams inside the organisation produces the same two effects and is frequently not treated as either a leaver or a joiner, because headcount is unchanged.
Headcount is not capacity. An internal move costs both teams for a period, and the portfolio view that treats it as neutral is wrong in both directions at once.
What this means for growth plans
A plan that adds people to meet a commitment has to show when those people become capacity, which is later than the commitment usually assumes.
Where the commitment lands inside the ramp, the honest answer is that the hiring does not solve it, and that answer is worth more than a plan which implies otherwise.
Documentation as a ramp control
The single biggest determinant of ramp length, in most places, is whether the things a new person needs are written down.
That makes documentation a capacity investment with a measurable return, which is an unusual position for it to be in and a useful argument when it is competing for the same hours.
What to record
For each joiner: start date, expected productive date, and the drag assumption on the team. For each leaver: last day, and the date the handover is expected to be complete.
Four dates per person-change. They are the difference between a plan that tracks headcount and one that tracks capacity.
Asking the three people
The question is not "how long did onboarding take" but "when did you stop needing somebody else to answer a question before you could finish something".
Three recent joiners, ten minutes each, and the answers are usually close together. That is the ramp figure, and it is better than any benchmark because it is about this work and this documentation.
The ramp in a plan that is already short
The worst case and a common one: a team is behind, a person is hired to help, and the first two months make the shortfall worse.
That is not an argument against hiring. It is an argument for saying so in the plan, because a team that is told capacity will dip and then rise behaves very differently from one that is told help is arriving.
The figure nobody wants to publish
Net capacity during a period of churn can be lower than before the hiring started. That is arithmetically true, uncomfortable, and far better said in the plan than discovered in the variance.
Saying it early also makes the case for the thing that actually helps, which is usually retention rather than recruitment.