THE ANALYST · CAREER BUILDING SERIES

30-Day Analytics Challenge

Become more than a dashboard builder. Practice framing business problems, designing metrics, writing SQL, building Power BI models, investigating performance, and presenting recommendations like a trusted advisor.

30 daily missions
4 skill levels
1 portfolio case study

How to use this challenge

  • Attempt each task before watching tutorials or looking up solutions.
  • Spend 60–90 focused minutes per day. A missed day is a reschedule, not a reset.
  • Keep evidence: queries, measures, screenshots, assumptions, and decisions.
  • Use synthetic or public data. Never publish confidential employer or customer information.
  • At the end of each week, write what you learned and what you would improve.
The standard: Every analysis must connect a business question to a trustworthy metric, evidence, an explanation, and an action.

Your 30 daily missions

Week 1 · Think like a business analyst

Day 01
Frame the business problem

CEO says revenue looks fine but the business may be slowing. Define the problem, list 10 KPIs, 3 analyses, relevant dimensions, 5 possible causes, and a one-slide executive response.

Open Day 1 challenge →
Day 02
Design a KPI dictionary

Define 10 metrics with business meaning, formula, grain, owner, filters, caveats, and target direction.

Day 03
Answer five questions with SQL

Query revenue trends, order counts, AOV, customer cohorts, and returns. Explain the grain and joins.

Day 04
Investigate a performance decline

Compare periods and decompose change by volume, price/value, mix, customer, product, and region. Separate facts from hypotheses.

Day 05
Challenge misleading metrics

Find five ways a metric can mislead: denominator shifts, mix changes, averages hiding segments, timing, and data quality.

Day 06
Design the data model

Sketch a star schema. Define fact grain, dimensions, keys, relationships, and slowly changing attributes where relevant.

Day 07
Present a five-minute briefing

Summarize the business question, evidence, caveats, and recommended next action. Include one slide or one-page memo.

Week 2 · Build with SQL and Power BI

Day 08
Build a clean star schema

Create fact and dimension tables, validate keys, and document relationships.

Day 09
Write 10 useful DAX measures

Build base measures, ratios, distinct counts, and context-aware measures. Avoid unnecessary calculated columns.

Day 10
Create time intelligence

Build prior-period, year-to-date, rolling-period, and comparable-period measures. Validate date table behavior.

Day 11
Build drill-down analysis

Use hierarchies and drill-through to move from summary to contributing segments.

Day 12
Build dynamic KPI comparisons

Allow users to compare actuals with target and prior period, with clear variance logic.

Day 13
Create an executive dashboard

Design for decisions: concise overview, trends, drivers, exceptions, and action cues.

Day 14
Audit and simplify

Remove redundant visuals, test filters, check totals, validate measures, accessibility, and performance.

Week 3 · Investigate and recommend

Day 15
Detect an anomaly

Identify an unusual KPI movement. Define a baseline, threshold, and false-positive risk.

Day 16
Perform root-cause analysis

Decompose the movement, test plausible drivers, and state what evidence would disprove your explanation.

Day 17
Separate correlation from causation

Identify confounders and propose a credible experiment or quasi-experimental approach.

Day 18
Analyze segments and outliers

Compare customer, product, region, and channel segments. Explain how outliers affect averages.

Day 19
Quantify business impact

Estimate impact in currency or operational units, state assumptions, and show a sensitivity range.

Day 20
Recommend three actions

Rank actions by impact, effort, confidence, owner, and measurement plan.

Day 21
Defend your analysis

Prepare for five skeptical stakeholder questions. Acknowledge limitations and revise weak claims.

Week 4 · Automate and prove your value

Day 22
Automate repetitive reporting

Map the current process, remove manual steps, add validation, and document failure handling.

Day 23
Use Python to investigate data

Profile a dataset, assess missingness and duplicates, summarize drivers, and create a reproducible notebook or script.

Day 24
Design an AI-assisted workflow

Use AI to draft summaries or investigation prompts, but validate every calculation and source. Document privacy guardrails.

Day 25
Create a data quality framework

Define freshness, completeness, uniqueness, validity, consistency, and reconciliation checks.

Day 26
Solve a timed case study

In two hours, frame a problem, query data, build a compact analysis, and present a recommendation.

Day 27
Practice a senior analyst interview

Answer SQL, metric design, stakeholder, prioritization, and analytical judgment questions using specific examples.

Day 28
Publish a portfolio case study

Show problem, dataset, method, model, measures, findings, limitations, and actions. Include reproducible evidence.

Day 29
Rewrite your resume around impact

Turn responsibilities into evidence-backed accomplishment statements. Never invent business outcomes.

Day 30
Present to leadership

Deliver a concise executive presentation and a retrospective: strongest skill, remaining gap, and next 30-day goal.

Definition of done

At the end of 30 days, your portfolio should contain one end-to-end business performance case study, a documented data model, reusable SQL and DAX, a concise executive narrative, and a clear account of limitations and decisions.

Start with Day 01. Do not move to building a dashboard until you can explain the business question and how each KPI helps answer it.

View the source on GitHub