Onboarding — The First 90 Days
Ayesha Raza's first day at the EdTech company started with forty-five minutes in the lobby. The laptop that had been ordered three weeks earlier had arrived configured for a different department. By 10am, she was in the second of eight back-to-back induction meetings — Finance, then IT security, then Compliance, then a 90-minute company history session she had already half-completed on the pre-hire portal. By 3pm she had met fourteen people whose names she would not remember by Friday, sat through four presentations she would not retain, and still had no access to the data systems that were the reason she had been hired. Omar Farooq, her manager, had blocked the afternoon for a team welcome lunch but had been pulled into an escalating client situation at noon and sent his apologies via Slack.
By the end of Week 1, Ayesha remembered approximately 10% of what she had been told. She was not sure what she was supposed to have achieved by the end of her first month. Nobody had told her, because nobody had written it down.
This is a story about three structural failures — not about effort or care. The HR team had prepared carefully. The induction calendar had taken hours to build. The problem was not that anyone worked badly; it was that the programme had been designed without asking the right question: What does success actually look like at 30, 60, and 90 days — and how will the new hire know whether they are on track?
The Three Onboarding Failure Modes
Most onboarding failures trace back to one of three structural problems. Recognising them is the first step to designing a programme that avoids them.
| Failure Mode | What It Looks Like | Why It Happens |
|---|---|---|
| Information Dump | Day 1 is 8 hours of back-to-back inductions. New hire retains 10%. | Programme was designed around what the organisation wants to communicate, not what the new hire can absorb |
| Administrative Bottleneck | Laptop not ready. Access not provisioned. Manager on holiday. New hire cannot do their job on Day 1. | Pre-boarding checklist exists but ownership is unclear — nobody confirmed completion before the start date |
| Invisible Ramp | No defined success criteria at 30, 60, or 90 days. New hire is busy but cannot tell whether they are performing. | 30-60-90 plans exist as aspiration documents, not as measurable contracts between manager and new hire |
The failure modes are not mutually exclusive. Ayesha's first week combined all three: she was information-dumped, administratively bottlenecked, and had no idea what the first 30 days were supposed to produce.
The Success Criteria Quality Rule
The Invisible Ramp is the hardest failure mode to see, because organisations often have a 30-60-90 plan and still fail to provide direction. The problem is the quality of the success criteria.
| Quality | Example | Why It Fails or Works |
|---|---|---|
| Weak — vague | "Understands the company culture" | Cannot be observed or assessed. Neither the manager nor the new hire can tell whether this is achieved. |
| Weak — process | "Completes all mandatory compliance training" | Observable, but describes a task, not an outcome. Compliance training completed ≠ employee performing. |
| Strong — observable | "Can describe the company's three strategic priorities and explain how their role contributes to each one" | Specific, observable, and directly relevant to job performance. Can be verified in a 30-day check-in conversation. |
| Strong — role-specific | "Has completed the first solo analysis task and presented the findings to at least one stakeholder" | Tied to actual work. Unambiguous. Either done or not done. |
The test of a strong success criterion: could the new hire assess themselves against it on Day 30 without asking their manager? If yes, it is strong. If they need to ask "does this count?", it is weak.
Worked Example: Ayesha Raza's Onboarding Plan
With the failure modes identified and the success criteria standard clear, Omar uses /onboarding to design an onboarding programme that addresses all three structural problems.
Step 1 — Invoke the skill with role details:
/onboarding
New starter: Ayesha Raza
Role: Senior Data Analyst
Department: Finance & Analytics
Start date: 10 March 2026
Reports to: Head of Analytics (Omar Farooq)
Location: Hybrid — Karachi HQ (3 days) + remote (2 days)
Prior experience: 5 years at a fintech; strong SQL and Python; new to edtech
Key projects in first 90 days: Q1 analytics refresh; data pipeline audit
Seniority framework: Senior (7+ years experience context — high autonomy expected by day 60)
Step 2 — Review the output. The skill returns a structured plan including:
ONBOARDING PLAN: Ayesha Raza — Senior Data Analyst
Start date: 10 March 2026 | Manager: Omar Farooq
SENSITIVITY: ROUTINE
════════════════════════════════════════════════════════════
── PRE-BOARDING CHECKLIST (complete before Day 1) ──────────
HR / IT (owner: HR team):
□ Offer letter signed and filed
□ HRIS record created; benefits enrolment pack sent
□ Laptop ordered and configured (data analyst build: Python, SQL, BI tools)
□ System access provisioned: HRIS, data warehouse, BI platform, GitHub
□ Security training scheduled (complete by Day 10 — mandatory)
□ Day 1 schedule sent to Ayesha with logistics (building access, parking)
Manager (Omar):
□ Team introduction email sent before Day 1 (with Ayesha's background)
□ First week's schedule: no all-day meetings, no travel, no conflicts
□ Buddy assigned from analytics team and briefed on their role
□ Key stakeholder intro meetings booked for Week 2 (not Week 1)
□ 30-60-90 plan drafted and ready to share on Day 1
□ First assignment identified — agree with Ayesha by Day 5
── WEEK 1: ORIENTATION ─────────────────────────────────────
Theme: "Understand the organisation, the team, and the tools"
Maximum 3 context sessions. No all-day induction marathons.
Day 1 (AM): IT setup and system access confirmation
Day 1 (PM): Welcome meeting with Omar — context, team, first 30-day priorities
Day 2: Company strategy briefing (Omar, 60 min) + data infrastructure overview (Data Engineering, 60 min)
Day 3-5: Shadow existing analytics work; explore dashboards and documentation; buddy check-in (informal)
Week 1 success criterion: Ayesha can describe what the company does, who her three key stakeholders are, and where the major data assets live.
── DAYS 8–30: LEARNING AND FIRST CONTRIBUTION ──────────────
Theme: "Learn the domain; make first contribution"
Goals:
□ Understand edtech domain and student/institution data model
□ Learn BI tooling and reporting conventions
□ Understand Q1 analytics refresh scope and timeline
□ Complete mandatory compliance and data security training (by Day 10)
□ First solo analysis task agreed with Omar by Day 5; delivered by Day 25
30-day success criteria (strong, observable):
□ Has completed and presented first solo analysis task to at least one stakeholder
□ Can describe Q1 analytics refresh scope, current status, and their role in delivery
□ Has met all key stakeholders (confirmed by Ayesha, not assumed by manager)
□ Has identified at least one gap or question in the existing analytics documentation
30-day check-in agenda (Omar + Ayesha, 1 hour):
- Review progress against 30-day success criteria
- What has been unclear or harder than expected?
- Priorities for Days 31-60
── DAYS 31–60: INDEPENDENCE ────────────────────────────────
Theme: "Own work streams; reduce day-to-day dependency on manager"
Goals:
□ Lead day-to-day delivery on Q1 analytics refresh
□ Present analysis to Finance team stakeholder group
□ Begin data pipeline audit: scope and initial findings documented
□ Identify and document one data quality issue with remediation proposal
60-day success criteria:
□ Q1 analytics refresh is on track; Ayesha is the day-to-day owner without Omar directing tasks
□ Has presented independently to Finance team (without Omar in the room)
□ Pipeline audit scope documented and agreed with Omar
60-day check-in: Omar + Ayesha (performance); separate HR Business Partner check-in (onboarding experience)
── DAYS 61–90: PERFORMANCE ─────────────────────────────────
Theme: "Perform at Senior Data Analyst level; begin strategic contribution"
Goals:
□ Deliver Q1 analytics refresh
□ Deliver pipeline audit initial report
□ Propose one improvement to current analytics process with business case
□ Share one edtech insight or domain knowledge with the broader team
90-day success criteria:
□ Q1 analytics refresh delivered; stakeholder feedback is positive
□ Pipeline audit report complete with at least two actionable findings
□ One process improvement proposed — specific, evidenced, costed
90-day formal review: Omar + HR Business Partner (1 hour)
Topics: Performance against plan; development areas; priorities for Month 4+
════════════════════════════════════════════════════════════
Step 3 — Audit against the three failure modes:
| Failure Mode | How This Plan Addresses It |
|---|---|
| Information Dump | Week 1 has maximum 3 context sessions, all capped at 60 minutes. No all-day induction marathon. |
| Administrative Bottleneck | Pre-boarding checklist has named owners and specific items. HR and Omar both have explicit pre-Day-1 responsibilities. |
| Invisible Ramp | Every milestone has observable success criteria in the strong format — specific, verifiable, not contingent on manager interpretation. |
The exact plan structure and success criteria wording will depend on the role details, department context, and seniority level you provide. The teaching point is the audit process: check every 30-day checkpoint against the strong success criteria standard before finalising the plan. If a milestone reads "understands the team priorities", rewrite it until it reads like something you could verify in a 30-minute conversation.
Seniority Differentiation
The same /onboarding skill produces meaningfully different outputs depending on seniority level. This is intentional — a junior hire who is performing well at 30 days looks nothing like a senior hire performing well at 30 days.
| Milestone | Junior (0–3 years) | Mid (3–7 years) | Senior (7+ years) |
|---|---|---|---|
| 30-day focus | Tool fluency; supervised tasks; orientation to team norms | First independent contribution; key stakeholder relationships | First stakeholder relationships; independent scoping of work |
| 60-day expectation | Contributing to defined tasks with light supervision | Owning at least one work stream independently | Delivering independently; beginning to contribute to team direction |
| 90-day standard | Performing at role level on defined tasks | Full role performance; developing areas visible | Strategic contribution beginning; role-level expectations fully met |
| Manager time investment | High in Days 1-30 (daily check-ins); reduces steadily | Moderate in Days 1-30; transitions to weekly by Day 45 | Light in Days 1-30 (context only); peer relationship by Day 60 |
The Manager Briefing
The best onboarding plan in the world fails if the manager has not internalised it before Day 1. The pre-boarding checklist item "30-60-90 plan ready to share Day 1" means more than a document — it means the manager has read the plan, understands the success criteria, and can have a substantive 30-minute conversation about priorities with the new hire on their first afternoon.
A manager briefing from /onboarding typically includes:
- The new hire's background and what they bring from prior experience
- What they will find familiar and what will be genuinely new (for Ayesha: SQL and Python familiar; edtech domain and the company's data infrastructure genuinely new)
- The single most important thing the manager can do in Week 1 (create the conditions for the new hire's first contribution, not add more context sessions)
- Red flags to watch for in the first 30 days (signs the Invisible Ramp failure mode is occurring: new hire is busy but cannot articulate their 30-day priority)
Exercise: Design a Complete Onboarding Programme
Type: Applied Practice
Time: 35 minutes
Plugin command: /onboarding
Goal: Design an onboarding programme for a real or fictional role that explicitly addresses all three failure modes and uses strong success criteria at every checkpoint
Step 1 — Choose Your Role
Select one of:
- A role you have hired for recently or are planning to hire (anonymise if needed)
- A role in your own team that you wish had better onboarding when you joined
- The fictional EdTech Senior Data Analyst role (to practice with the Ayesha scenario)
Step 2 — Define Strong Success Criteria First
Before running /onboarding, write three success criteria for Day 30 using the strong format. Each should be:
- Observable without interpretation
- Specific to the role, not generic
- Verifiable in a 30-minute check-in conversation
Write these before proceeding. This step ensures the tool is guided by your judgment, not replacing it.
Step 3 — Generate the Onboarding Plan
Run /onboarding with full role context:
/onboarding
New starter: [Name or "fictional hire"]
Role: [Title]
Department: [Department]
Start date: [Date or approximate]
Reports to: [Manager name and role]
Location: [Office / Hybrid / Remote]
Prior experience: [Key background and what is new to them]
Key projects or priorities in first 90 days: [2-3 specific items]
Seniority: [Junior / Mid / Senior]
Step 4 — Audit the Output
Review the /onboarding output against the three failure modes:
| Failure Mode | Question to Ask | Pass / Needs Revision |
|---|---|---|
| Information Dump | Does Week 1 have more than 4 structured sessions? | Pass if ≤4; revise if more |
| Administrative Bottleneck | Does the pre-boarding checklist have named owners for every item? | Pass if owned; revise if generic |
| Invisible Ramp | Are the 30-day criteria specific enough to verify in a conversation? | Pass if strong; revise if vague |
Rewrite any weak criteria to strong format before finalising.
Step 5 — Create a Manager Briefing
Using the /onboarding output, draft a 200-word manager briefing that covers:
- What the new hire brings from prior experience
- What will be genuinely new to them
- The single most important thing the manager should do in Week 1
- The three 30-day success criteria (in strong format)
Deliverable: A complete onboarding programme — pre-boarding checklist with named owners, week 1 schedule (maximum 4 structured sessions), 30-60-90 plan with strong success criteria at each checkpoint, and a one-page manager briefing.
The onboarding programme you design here connects to Lesson 12, which covers the Onboarding Orchestrator agent — a persistent agent that automates the pre-boarding checklist and sends reminders to owners automatically. The plan you produce here is the input the orchestrator needs.
Try With AI
Use these prompts in Cowork or your preferred AI assistant.
Reproduce: Generate Ayesha's onboarding plan and audit the success criteria.
I am onboarding a new Senior Data Analyst named Ayesha Raza. She starts
10 March 2026, joins the Finance & Analytics team (4 people), and reports
to Omar Farooq. She has 5 years of fintech experience with strong SQL and
Python skills but is new to edtech. Her first 90-day priorities are the Q1
analytics refresh and a data pipeline audit. She will be hybrid — Karachi HQ
3 days, remote 2 days.
Generate a complete onboarding plan: pre-boarding checklist with named
owners (HR/IT/Manager), a week 1 schedule with no more than 3 context
sessions, and a 30-60-90 plan with specific, observable success criteria
at each checkpoint. Mark each success criterion as WEAK or STRONG using
this test: could Ayesha assess herself against it on the checkpoint date
without asking her manager?
What you are learning: The discipline of auditing success criteria quality separates an onboarding plan that helps from one that merely documents intention. Running the WEAK/STRONG test on every milestone is the core habit this lesson is building.
Adapt: Apply the framework to your own most-hired role.
I need to design an onboarding programme for the role I hire most
frequently: [describe the role, team, seniority, and top 2-3 priorities
for the first 90 days].
Generate the programme, then for each 30-day success criterion,
tell me: is this strong (observable, verifiable, role-specific) or
weak (vague, process-only, or dependent on manager interpretation)?
Rewrite any weak criteria to the strong format.
What you are learning: Applying the success criteria quality test to your own familiar roles forces you to articulate what "performing well" actually means — a question many managers have never explicitly answered.
Apply: Generate and compare seniority-differentiated variants.
I am building a hiring pipeline for Data Analysts at three seniority levels
in the same team: Junior (0-3 years), Mid (3-7 years), and Senior (7+ years).
Generate a 30-60-90 framework for each level — not three separate full plans,
but a comparison table showing how the expectations at each checkpoint differ
by seniority. Focus on: independence threshold (when do they work without
supervision?), stakeholder scope (who do they interact with independently?),
and contribution type (tasks vs work streams vs strategic input).
Then identify the single most important difference between Mid and Senior
onboarding that managers consistently underestimate.
What you are learning: Seniority differentiation is where onboarding design separates experienced HR practitioners from beginners — senior hires who receive the same Day 1 experience as junior hires frequently disengage within 60 days because the programme signals that their experience is not recognised.
Flashcards Study Aid
Continue to Lesson 6: Job Descriptions & Interview Preparation →