Time to productivity is a knowledge problem wearing a time costume.
Every week a new hire, a transferee or a newly promoted manager runs below capacity, the payroll pays full price for partial output. Most of that gap is knowledge that hasn’t landed yet — which makes it measurable, manageable, and considerably compressible.
You can’t compress what you don’t measure
Ask when a new hire becomes productive and most organisations answer with folklore: ‘about three months’. Folklore can’t be managed. The ramp compresses only when it becomes a measured object — a target capability profile for the role, a baseline of what this person brought, and a weekly curve of verified progress between the two.
Once measured, the compression levers are mechanical: skip what the baseline shows they have; pace material against the forgetting curve instead of front-loading it into oblivion; interleave the confusables early; and intervene the week a topic stalls rather than discovering it at review time. Nothing exotic — just the ramp, run like a process instead of a rite of passage.
Baseline credit shortens every ramp
The diagnostic finds what the person already holds — experienced hires routinely clear 40% of a role’s profile on day one, and the managed ramp skips accordingly.
The weekly curve managers steer by
Verified capability per topic per week, with stalls flagged while a conversation can still fix them. Ramp management becomes five minutes of aimed attention.
An arrival worth announcing
Ramp completion is a verified profile against the role target — a defensible moment to hand over the full portfolio, and a season-over-season metric for the program itself.
The ramp curve, measured
Time-to-productivity as a curve per hire, not a guess per role — and the two interventions that bend it left.
Interface shown as an illustration with representative numbers, not a screenshot — the layout is the product’s.
Price your ramp first.
Headcount × weeks × salary share — then see what a managed ramp does to the weeks term. The calculator’s cousin, live in the demo.
The evidence this page stands on
Questions buyers ask
How much compression is realistic?
Honestly: it depends on how much of your ramp is knowledge versus relationships and system access. The knowledge share — usually the majority — compresses substantially through baselining and pacing; the pilot measures your number instead of promising one.
Does this apply beyond new hires?
Everywhere a ramp exists: internal transfers, promotions into management, returners from leave, post-acquisition integrations. Transfers are often the quickest win — their baselines are rich.
What defines ‘productive’ in the system?
A role capability profile you set: the topics and depths that constitute doing the job. Verification against that profile replaces tenure proxies and gut feel.
Doesn’t measuring the ramp pressure new hires?
Framing decides: the curve shows material landing, not people failing — and stalls route help to the person early. New hires consistently prefer visible progress to ninety days of ambiguity.
What does the CFO see?
Ramp weeks × loaded cost, trending down by cohort — one of the few L&D metrics that translates to payroll arithmetic without a leap of faith.
See it on your own content.
Bring one course. We’ll show you the retention curve your current training leaves behind — and what scheduled review does to it.
- 30 minutes, on your calendar — pick a slot here
- Run on your own content wherever possible, not a canned deck
- You see the dashboards, the learner surface and the evidence exports
- No commitment — and pilot data stays yours either way