Your first 90 days, end to end
Every onboarding follows the same arc: you arrive, you observe, you contribute. What changes between companies is the pace — and how much of the map you are handed on day one.
This class walks that arc with every tool we have: charts, timelines, diagrams, interactive widgets and short checks. Treat it as both a guide and a workout for your attention.
A useful rule of thumb: the ramp is roughly $t_{ramp} = 30d + 30c + 30r$ — thirty days to decode, thirty to contribute, thirty to own something. Your ramp The period between your start date and the moment your output matches that of an established teammate. is not a grace period; it is the work.
In German, the word for onboarding is Einarbeitung — literally "working your way in".

The three phases are not equal in difficulty. Why the middle month is the hardest Month one has no expectations and month three has momentum. Month two is when you are expected to produce without yet owning the context — the classic dip in new-hire confidence.
Decode before you contribute
The org chart tells you who can decide. The first thirty days are about learning who actually decides.
Culture eats strategy for breakfast.
Peter Drucker — The Effective Executive, 1967
What does the informal structure of a company describe?
- The seating plan and who sits near whom
- Who actually influences decisions, regardless of title
- The reporting lines approved by HR
- The list of people with budget authority
What the numbers say
Ramp-up is measurable. Companies that document onboarding see new hires reach full productivity noticeably faster.
| Model | Time to first delivery | Documented process | Buddy assigned |
|---|---|---|---|
| Sink or swim | 9 weeks | No | No |
| Checklist | 6 weeks | Partial | Sometimes |
| Structured | 4 weeks | Yes | Yes |
Where the first month actually goes
Newcomers consistently underestimate how much of month one is spent reading and asking, and overestimate how much is spent producing.
A dip in confidence during the second month is a normal part of onboarding.
The shape of a good ramp
- Days 1-5 · Access and orientation
Accounts, tools, the team calendar, and the first read of whatever documentation exists.
- Days 6-30 · Mapping
Introductory meetings with every adjacent team. One question repeated everywhere: what do you need from my role?
- Days 31-60 · First ownership
A small, complete piece of work delivered end to end — scoped so that failure is cheap.
- Days 61-90 · Full integration
You are now the person someone else asks. Write down what you wish you had been told.
How a request actually travels
The period between your start date and full productivity is called the ____.
- ramp
- probation
- handover
Three habits that shorten the ramp



Check yourself
What is the difference between authority and influence?
Authority is granted by the org chart. Influence is granted by colleagues. Decisions need both.
Week-one checklist
Four things worth finishing before your second Monday:
- Meet every person your role depends on
- Read whatever runbook exists, even if outdated
- Ship one visible, tiny contribution
- Start the confusion log
<callout type="default"> If your team has no runbook, the checklist above is the beginning of one. </callout>

Automating the boring half
Most onboarding checklists can be generated from the org's own data.
def ramp_plan(role, dependencies):
"""Return the meetings a newcomer should book in week one."""
weeks = {1: [], 2: [], 3: []}
for i, team in enumerate(dependencies):
weeks[(i % 3) + 1].append(f"Intro: {role} x {team}")
return weeks
print(ramp_plan("Analyst", ["Finance", "Legal", "Ops", "Data"]))The rest of the toolbox
A class can also carry media that is not text: a clip, a narrated note, an animation, an interactive model.
Drag each phase onto the month where it belongs: Access, Mapping, First ownership, Documentation.
What to leave behind
The end of your onboarding is the beginning of someone else's. The single most valuable artefact you can produce in ninety days is the document you wish had existed on day one.
Structured programmes are not bureaucracy for its own sake: they shorten the ramp and measurably improve retention.
Fuentes
Referencias
- Harvard Business Review on organizational change and stability
- Gallup: Onboarding new employees
- SHRM: New employee onboarding guide
Bibliografía
- Bauer, Talya N. *Onboarding New Employees: Maximizing Success*. SHRM Foundation, 2010.