Analyst Onboarding Playbook (90-day)

Welcome

Getting a new analyst productive quickly requires more than tool training — it needs clear expectations, focused practice on real data, stakeholder alignment, and early decision-oriented wins. This 90‑day playbook provides a practical, adaptable sequence of activities, deliverables, meetings, and assessment checkpoints designed to reduce ramp time, build consistent capability, and surface early value.

How to use this playbook

Use this playbook as a template you adapt for your team and role. Copy and tailor deliverables, swap sample datasets for local datasets, align success criteria with your KPIs/SLAs, and pair new hires with a mentor. Consider turning the First Week checklist and the 30/60/90 assessment into interactive forms so progress can be recorded and reported.

Core goals (the hungers this playbook satisfies)

• Shorten analyst ramp time so they start contributing to decisions faster.
• Set clear, role-specific expectations for skills, deliverables, and stakeholder interactions.
• Create repeatable exercises and an assessment that managers can use to measure early outcomes.

Overview: 30 / 60 / 90 structure (what to accomplish)

The timeline focuses on progressively expanding scope and autonomy while anchoring learning in stakeholder needs and real datasets.

Practical checklists and templates

Below are practical starting templates. Copy these into your local systems and adapt them to local names, KPIs and processes.

Knowledge Transfer Checklist (first week)

• Access checklist: data warehouse, BI tool, code repo, Slack/Teams channels, ticketing system.
• Documentation to read: data catalog entries, current dashboards, recent high‑impact analyses, glossary.
• People to meet: manager, mentor, data owners, product owner, 2–3 primary stakeholders.
• Governance contacts: data steward, security, compliance, and platform ops.

Micro‑project brief (template)

1. Question: (stakeholder question)
2. Why it matters: (decision it supports)
3. Data used: (tables, fields, limitations)
4. Method: (queries, filters, model)
5. Key findings: (3 bullet points)
6. Recommended next actions
7. Attachment: reproducible script/notebook and short slide deck

Manager review template (30/60/90 checkpoints)

• Progress against deliverables and agreed priorities.
• Skill development: strengths, gaps, and suggested learning activities.
• Stakeholder feedback: quality, timeliness, and clarity of communication.
• Next priorities and resources required.

Assessment rubric (lightweight)

Use this short rubric to structure conversations and create consistent expectations. Consider converting it into an interactive assessment so scores and comments are saved.

• Data Literacy (basic queries, understand joins and keys): Emerging / Competent / Proficient
• Reproducibility (scripts, notebooks, documentation): Emerging / Competent / Proficient
• Business Understanding (frames decisions, translates findings): Emerging / Competent / Proficient
• Delivery & Communication (clear briefs, concise visualizations): Emerging / Competent / Proficient
• Production Readiness (tests, monitoring, deployment hygiene): Emerging / Competent / Proficient

Managers and mentors should add specific evidence for each rating (deliverables, reviews, stakeholder quotes).

Sample exercises

Concrete exercises accelerate learning:

• Dataset Walkthrough — annotate a schema and identify three potential quality risks and one new KPI.
• Reproduce & Critique — reproduce a past analysis and write a short note about alternate approaches or missing context.
• Dashboard Handoff — improve a filter, add documentation, and create an "owner" ticket in the tracking system.
• Production Ticket — convert a notebook to a scheduled job or submit a PR that adds a test or data validation step.

Role and RACI guidance

Tailor the playbook by role (e.g., analytics engineer, business analyst, data scientist). For each role define RACI for common onboarding deliverables: data access (R), micro‑project outcome (A), productionization (C), stakeholder acceptance (I), and documentation (R).

Common pitfalls and how to avoid them

• Tool‑first onboarding: Always pair tool training with a concrete decision-oriented exercise.
• Unclear ownership: Assign a mentor and a product owner for each early deliverable.
• Overly broad scope: Keep early projects small and time‑boxed.
• Missing governance: Ensure data access and privacy checks are completed before production work.

Tailoring checklist

Before applying this playbook, adapt these items:

• Map the playbook deliverables to local KPIs and SLAs.
• Replace sample datasets with anonymized local datasets or synthetic data if privacy rules prevent access.
• Adjust skill checkpoints to reflect the role’s expected technical depth (SQL, modeling, machine learning).
• Decide how progress will be recorded — consider interactive forms and saved submissions for auditability.

Next steps & recommended platform enhancements

To make this playbook operational and easier to run at scale, consider the following capability implementations (described in CapabilityEnhancementNotes).

Appendix: Quick templates (copyable)

(Include in your local wiki or HR onboarding docs.)

Decision Map: Stakeholder | Decision | Frequency | Current Report | Owner
Micro‑Project Brief: Question | Why it matters | Data | Method | Findings | Next steps
Manager Review Note: Progress | Evidence | Rating | Plan