Career Change Navigator (Alt)

90-day transition plan

Known facts and unknowns

Known: five years in customer support, recurring spreadsheet reports, interest in troubleshooting, five weekly learning hours, four months of savings, and a preference to validate before resigning. Unknown: location, income, expenses, salary needs, tools, training budget, job demand, and family obligations. Treat any inferred strength as a hypothesis, not proven proficiency.

Days 1–14: test the target

Review 15–20 current analyst postings in the target market. Record repeated tools and responsibilities, separating common requirements from preferences. If possible, speak with three practitioners. This small sample is directional, not a labor-market forecast.

Days 15–42: build evidence

Allocate five hours weekly: two to spreadsheet or SQL practice, one to visualization, and two to a synthetic-data project. Create a support-ticket trend analysis that documents cleaning, definitions, one operational question, and limitations. Do not use confidential employer or customer data.

Days 43–70: test fit

Ask two practitioners to review the sample, compare feedback with postings, and try a realistic analysis task. Identify the highest-value skill gap and choose relevant, affordable practice only after checking requirements.

Days 71–90: compare bridge routes

Consider an internal reporting project, support-operations role, entry-level analytics application, or continued part-time portfolio building. Verify each role’s requirements before applying.

Guardrails and gates

Remain employed while testing when feasible. Set a personal reserve and learning budget from actual expenses; four months alone is insufficient to recommend resignation. Reassess at days 30, 60, and 90 against role fit, demonstrated skills, market evidence, and financial comfort. Continue, adjust to an adjacent role, or pause. No job, salary, or timing is guaranteed.