Skip to content

Data AnalyticsArticle

Excel to SQL to Python: a learning path for aspiring analysts

You do not need to learn everything at once. A sequenced path — what to learn in each tool, when to move on, and which projects prove you are ready.

ActuateMinds EditorialPublished 2 min read

The problem with learning "data" all at once

Aspiring analysts often start five courses in parallel — Excel, SQL, Python, statistics and a BI tool — and finish none. The tools overlap so much that a sequence works far better: each one builds intuition the next one relies on.

Here is the path we recommend, with a clear signal for when to move on.

Stage 1 — Excel: learn to think in tables

Excel is where you build intuition for rows, columns, filters, lookups and aggregation — the same ideas SQL formalises.

Learn:

  • Clean data: TRIM, TEXT, DATE, splitting columns, removing duplicates
  • Look up values: XLOOKUP (or INDEX/MATCH)
  • Aggregate conditionally: SUMIFS, COUNTIFS, AVERAGEIFS
  • Summarise with PivotTables and simple charts

Move on when you can take a messy export, clean it, and answer "which region grew fastest last quarter?" in under 30 minutes. Our Excel practice set is designed for exactly this.

Stage 2 — SQL: ask questions of real databases

Almost every analyst role tests SQL. It is also where your Excel intuition pays off: a PivotTable is a GROUP BY; a lookup is a JOIN.

Learn, in this order:

  1. SELECT, WHERE, ORDER BY, LIMIT
  2. GROUP BY and HAVING
  3. INNER and LEFT JOIN (and why row counts change)
  4. Subqueries and CTEs
  5. Window functions — see our guide to window functions

Move on when you can solve medium-difficulty SQL interview questions without looking up syntax, and explain why a LEFT JOIN returned more rows than expected.

Stage 3 — Statistics: know what your numbers mean

Before Python, spend focused time on the ideas that stop you from overclaiming:

  • Mean vs median, and when outliers matter
  • Variance and standard deviation
  • Sampling, confidence intervals and why sample size matters
  • Hypothesis testing and A/B test basics
  • Correlation is not causation — with examples from your own data

Stage 4 — Python: scale and repeat

Python (with pandas) is for when spreadsheets strain: bigger files, repeated cleaning, merging many sources, or analysis you need to rerun every week.

Learn: DataFrames, read_csv, filtering, groupby, merge, handling missing values, and basic plotting. Use the Python compiler to practise small snippets without installing anything.

Stage 5 — A BI tool: make it self-serve

Finally, learn one of Power BI, Tableau or Looker Studio well. The concepts — data models, measures, filters, dashboard layout — transfer between them.

A project for each stage

Stage Project that proves it
Excel Clean and analyse a year of sales data; one-page summary
SQL Funnel and retention queries on an e-commerce schema
Statistics Analyse an A/B test and write a recommendation
Python Automate a weekly report from three CSV sources
BI An operations dashboard with defined KPIs

Key takeaways

  • Learn sequentially: Excel → SQL → statistics → Python → BI.
  • Each stage has a concrete "ready to move on" signal.
  • One project per stage builds a portfolio as you learn.
  • Depth in SQL matters more than breadth across tools for most first analyst roles.

Written by

ActuateMinds Editorial

The ActuateMinds editorial team writes practical guides for people moving into product, design, data and applied-AI roles.

Get the next article in your inbox

One short email a week. No spam.

No spam. Unsubscribe from any issue.

Career Advice5 min read

Switching from engineering to product: a 90-day plan

Engineers already have half of what product work demands. This 90-day plan shows how to build the other half — customer insight, prioritisation and written judgement — while you are still in your current role.