Career Change Navigator

90-day transition plan: support specialist to data analytics

Starting point and assumptions

Known: five years in customer support, enjoys troubleshooting and documenting recurring issues, uses spreadsheets for weekly reports, can study five hours weekly, has four months of savings, and does not want to resign before testing the path. Unknown: location, current income and expenses, salary needs, tools used, data access, degree/credential history, job-market demand, family obligations, and training budget. This plan does not assume a job offer or salary outcome.

Transferable strengths to test

• Troubleshooting may transfer to structured problem framing and investigation.
• Recurring-issue documentation may transfer to metric definitions and data dictionaries.
• Weekly spreadsheet reports may provide a starting point for cleaning, summarizing, and communicating data.
  Validate these with work samples and feedback; they are hypotheses, not proof of proficiency.

Weeks 1–2: clarify the destination

Review 15–20 current analyst postings in the user’s target location or remote market. Record tools, responsibilities, experience requirements, and recurring qualifications. Separate must-haves from preferences. Conduct three informational conversations with analysts or hiring managers if available. Do not treat a small sample as a representative market forecast.

Weeks 3–6: build baseline proof

Spend five hours each week: two hours on spreadsheet/SQL fundamentals, one hour on data visualization, and two hours completing a small public or synthetic-data project. Create a support-ticket trend analysis that defines categories, shows cleaning steps, answers one operational question, and clearly describes limitations. Do not expose employer or customer data.

Weeks 7–10: test role fit

Ask two practitioners to review the project. Compare feedback to job-posting requirements. Try one realistic analysis task and note which work is energizing or draining. Identify only the highest-value gap; select a low-cost, short course or practice resource after checking its relevance.

Weeks 11–13: decide the next route

Possible bridges: internal reporting project, support-operations analyst role, part-time portfolio work, or entry-level analytics applications. Before applying, verify role requirements and adapt the project to demonstrate the work.

Guardrails and decision gates

Keep the current role while validating. Set a personal minimum savings reserve and maximum learning spend using actual expenses; four months of savings is not enough information to recommend resignation. Reassess at days 30, 60, and 90. Continue only if evidence supports role fit, skill progress, feasible openings, and acceptable finances. If not, test an adjacent support-operations path or pause. No salary or employment outcome is promised.