Onboarding and Ninety Day Plan Questions

Planning and executing an effective onboarding and first ninety day plan in a new role using a phased thirty sixty ninety approach. The first thirty days are focused on learning and discovery, the next thirty days on assessment and planning, and the final thirty days on initial implementation and demonstrating impact. Candidates should define clear priorities and measurable success criteria for each phase, identify key stakeholders and a strategy for building relationships, create a learning plan for domain knowledge and tooling, and identify realistic quick wins that respect ramp time. Strong answers cover how progress will be measured and reported, how decisions will be prioritized and trade offs managed, what risks and dependencies exist, and what resources and access are required to deliver outcomes. At junior levels candidates should show awareness that the earliest period will be heavy on onboarding and learning with gradually increasing independence and contribution. Good responses also explain how they will ask for guidance and feedback, engage stakeholders, and connect early outcomes to longer term objectives.

HardTechnical

27 practiced

As a senior analyst, you need to justify hiring another BI team member within 90 days. Prepare a concise business case including capacity analysis (current vs. desired throughput), ROI projection for the hire, suggested role responsibilities, and how the new hire would accelerate critical strategic initiatives.

Sample Answer

Situation: Our 4-person BI team supports ~12 business partners and delivers 40 dashboards, 25 ad-hoc analyses/month, and 8 executive reports/month. Current backlog: ~18 requests average age 12 days; average lead time for new dashboard = 6 weeks. SLA target is 5 business days for ad-hoc and 3 weeks for dashboards.

Capacity analysis:- Current throughput: 25 ad-hoc analyses/month, 2 new dashboards/month (team constrained by maintenance + firefighting ~45% time).- Desired throughput: 40 ad-hoc analyses/month and 6 new dashboards/month to meet stakeholder roadmaps and reduce backlog to <5 items.- Gap: +15 ad-hoc/month and +4 dashboards/month → requires ~0.8 FTE based on historical throughput; hire recommended: 1 FTE to cover ramp and cross-training.

ROI projection (12 months):- Incremental revenue / cost avoidance from faster insights: estimate $200k (improved pricing, churn reduction, campaign optimization).- Productivity gains: stakeholders save ~6 hours/month each from automated reports → 12 partners × 6h × $75/hr = $64.8k.- Total quantified benefit ≈ $265k. Cost = $120k fully loaded compensation. Net benefit ≈ $145k; payback ≈ 6 months. Intangibles: faster decision cycles, fewer risky manual processes.

Suggested role responsibilities (Senior BI Analyst):- Deliver 60% new dashboards & automated reporting (end-to-end: requirements, data modeling, visualization)- 20% analytics & ad-hoc deep dives (cohort, causal analysis)- 10% data quality & pipeline validation- 10% stakeholder enablement & documentation; mentor junior analysts

How hire accelerates strategic initiatives:- Cuts dashboard lead time from 6→3 weeks enabling quarterly product experiments to iterate twice as fast- Reduces backlog to <5 items, unlocking analytics for pricing and retention initiatives with projected $200k+ impact- Frees senior analysts for strategic modeling (LTV, attribution) improving targeting and ROI of marketing spend- Improves SLA compliance and stakeholder trust, increasing analytics adoption and data-driven decisions.

Recommendation: Approve one Senior BI Analyst hire within 90 days; prioritize onboarding with 30/60/90 day milestones: (30) connect to data sources & deliver 1 automation, (60) deliver 2 dashboards, (90) lead a strategic analysis delivering measurable outcome.

MediumTechnical

31 practiced

You inherited reporting with inconsistent KPI definitions across teams. Outline a 90-day plan to standardize definitions and implement governance. Include stakeholders to involve, milestones, expected artifacts (e.g., glossary, approval flow), and success metrics to indicate adoption.

Sample Answer

Approach: use a 90-day phased plan (Discover → Align → Implement & Govern) with clear stakeholders, artifacts, milestones and measurable adoption metrics.

Days 0–30 — Discover & Assess- Stakeholders: BI, Analytics Lead, Product/Marketing/Sales/Finance owners, Data Engineering, PMO, Legal (as needed).- Activities: inventory all KPIs and reports, map current definitions, identify discrepancies and upstream data sources, prioritize top 20 KPIs by usage/impact.- Artifacts: KPI inventory spreadsheet, source-to-report mapping, priority list.- Milestone: complete inventory and prioritization.

Days 31–60 — Define & Align- Stakeholders: same plus executive sponsor and representative business SMEs.- Activities: run workshops to converge on single definitions for prioritized KPIs (formula, frequency, filters, cohorts), document business rules and SQL/LookML snippets, agree on measurement windows and owners.- Artifacts: KPI glossary entries (definition, owner, calculation, source, examples), decision log, draft approval flow.- Milestone: sign-off on top 20 KPI definitions by owners and exec sponsor.

Days 61–90 — Implement, Automate & Govern- Stakeholders: Data Engineering (ETL), BI engineers, KPI owners, Compliance.- Activities: implement canonical calculations in the BI layer (centralized metrics, parameterized LookML/semantic layer), update dashboards, create automated tests and lineage, roll out training and communication.- Artifacts: centralized metrics library, approval workflow (Jira/Confluence template), monitoring dashboards (data quality, consumption), runbook for changes.- Milestone: deploy canonical KPIs, retire duplicates, publish governance process.

Success Metrics (adoption & quality)- 90% of high-priority dashboards using canonical KPI within 30 days after deployment- Reduction in KPI-definition incidents/clarification tickets by 80%- Number of duplicate KPI variants reduced by 75%- Time-to-resolution for KPI disputes < 3 business days using approval flow- Usage/consumption lift of trusted dashboards (weekly active users +25%)

Ongoing governance: monthly metric review board, versioned glossary, change request workflow, automated lineage and alerts for schema/ETL changes. This balances speed and stakeholder buy-in while establishing sustainable controls.

MediumTechnical

27 practiced

Describe concrete ways to measure dashboard adoption and business impact over the first 90 days. Specify which metrics you would instrument (e.g., active users, time spent), how you would collect those signals (logging, BI-tool APIs), and how you'd present adoption trends to stakeholders.

Sample Answer

Situation: As a BI analyst rolling out a new dashboard, I’d measure adoption and business impact across the first 90 days by instrumenting product- and business-facing signals, collecting them reliably, and presenting clear trends to stakeholders.

Metrics to instrument- User adoption: DAU/WAU/MAU for the dashboard, new users, returning users, % of target users (by team/role) who have opened it.- Engagement: average sessions per user, avg session duration, pages/components viewed per session, click heat (filters used, drilldowns).- Depth: % of users who perform key actions (export, subscribe, set alerts, embed), number of saved views/bookmarks.- Business impact: number of decisions informed (via a short action capture), change in downstream KPIs (e.g., lead-to-conversion rate) tied to dashboard usage cohorts.- Reliability & quality: error rates, data freshness lag, failed loads.

How to collect signals- BI-tool telemetry/APIs: query Tableau Server, Power BI REST API, or Looker usage exports for view counts, user lists, downloads, schedules.- Instrument event logging: add lightweight event tracking in web wrapper or internal app (Segment/GA/Mixpanel) for clicks, filters, exports with user_id and dashboard_id.- Backend logs / data warehouse: ingest scheduled extract logs, query performance, freshness metadata into Snowflake/BigQuery for joining with user metadata.- Surveys/Action capture: short in-dashboard prompt (single-click “Did this help?”) and a follow-up survey capturing decisions.- Link to business systems: tag key users and correlate cohort consumption with downstream system metrics via SQL joins.

How to present adoption trends- Executive one-pager: top-line adoption (DAU/MAU), % of target coverage, 30/60/90 day trend, major wins and blockers.- Dashboards for stakeholders: - Cohort chart: adoption by onboarding week, retention curve (day-1,7,30). - Funnel/heatmap: view → interact → export → decision; drop-off points highlighted. - Segmentation: adoption by department/role, power users vs casual. - Correlation panels: usage vs business KPIs with time-lagged comparison and confidence intervals. - Reliability timeline: data freshness and error incidents overlayed to explain spikes/dips.- Alerts & cadence: automated weekly snapshot email and a 30/60/90 day review meeting with action items (training, content changes, performance fixes).

Example instrumentation snippet (pseudo-SQL) to join usage and business outcome:

sql

SELECT u.team, date(usage.ts) as day, COUNT(DISTINCT usage.user_id) as dau,
       SUM(case when outcome.event='conversion' then 1 else 0 end) as conversions
FROM dashboard_usage usage
JOIN users u ON usage.user_id = u.id
LEFT JOIN business_outcomes outcome ON outcome.user_id = usage.user_id AND date(outcome.ts)=date(usage.ts)
GROUP BY 1,2;

This approach gives measurable adoption signals, links usage to impact, surfaces problems quickly, and provides stakeholders clear, actionable trends over the first 90 days.

EasyTechnical

32 practiced

As an entry-level candidate, explain three concrete behaviors you will practice in your first 90 days to demonstrate a growth mindset while ramping on domain knowledge and BI tooling. Provide a short example for each behavior.

HardTechnical

29 practiced

Create a plan to measure and report the ROI of BI efforts at 30/60/90 days. Define quantifiable metrics (e.g., hours saved, revenue influenced), data sources to attribute impact, an attribution method, and a sample dashboard layout executives would understand.

Sample Answer

Overview: Measure ROI of BI by tracking time savings, revenue influence, cost avoidance, data quality improvements, and adoption over 30/60/90 days. Use a mix of quantitative system logs + business outcomes and a simple attribution model (hybrid: direct + contribution weights). Report via an executive dashboard summarizing impact and confidence.

30/60/90 Plan- Day 0–30: Baseline & quick wins - Collect baselines (manual report hours, current decision cycle times, error rates, revenue KPIs). - Deploy initial dashboards, enable event logging (views, exports, scheduled runs). - Metric targets: 10–20% reduction in manual reporting hours.- Day 31–60: Adoption & intermediate impact - Track active users, frequency, time-to-decision, and specific decisions influenced by BI. - Run surveys + stakeholder attestations to capture decisions enabled and estimated revenue impact. - Attribute conservatively (e.g., 50% of reported decision uplift).- Day 61–90: Outcome validation - Compare outcomes against control groups or pre-post windows; refine attribution; calculate ROI.

Quantifiable Metrics (examples)- Hours saved/week = (#manual reports retired × avg prep time) + reduced ad-hoc requests- FTE cost saved/month = hours_saved × fully-loaded hourly rate- Revenue influenced = sum(case-level estimated lift from BI-enabled decisions)- Cost avoidance = prevented overstock/penalties from alerts- Adoption: DAU/WAU, % of stakeholders with scheduled reports- Data quality: reduction in downstream errors (%)

Data Sources- BI tool logs (views, exports, schedules)- Ticketing/analytics for ad-hoc requests (Jira/ServiceNow)- Time-tracking or time estimates from SMEs- CRM/ERP for revenue, orders, inventory- A/B tests or control cohorts where possible- Stakeholder survey responses (structured form)

Attribution Method- Tiered hybrid model: 1. Direct attribution: If decision explicitly cites dashboard and outcome occurs within expected window → 100% attribution to BI. 2. Contribution attribution: For multi-factor decisions, use weighted contribution via stakeholder survey or Shapley-lite (normalize weights sum to 1). 3. Conservative default: if uncertain, attribute a conservative percentage (e.g., 25–50%).- Use pre-post or difference-in-differences for validation where feasible.

Sample Executive Dashboard Layout (single-page)- Header: Net ROI (monetary) over selected period + confidence band- Left column: Key KPIs (Hours saved, FTE cost saved, Revenue influenced, Cost avoided)- Middle: Adoption & engagement (active users trend, top users, dashboard heatmap)- Right: Attribution breakdown (Direct vs. contribution vs. conservative), top 5 decisions influenced with brief descriptions and impact estimates- Bottom: Methodology & data sources, assumptions, and recommended next actionsVisualization notes: use single-number cards, trend lines, stacked bars for attribution, and a table of audited cases for transparency.

Validation & Governance- Monthly audit of samples (three case audits) to confirm claimed impacts- Maintain assumptions registry and update weights based on evidence- Automate data pulls and update dashboard weekly; include margin-of-error and confidence notes.

This plan balances rapid measurable wins with conservative, evidence-based attribution to produce credible ROI reporting executives can trust.

Unlock Full Question Bank

Get access to hundreds of Onboarding and Ninety Day Plan interview questions and detailed answers.

Join thousands of developers preparing for their dream job.