BlogData Analytics BasicsChapter 3
BASICS · CHAPTER 3Beginner

The Data Analytics Process

All 6 steps — from defining the business question to measuring the outcome — walked through with a real Indian e-commerce revenue investigation. SQL code at every step that needs it.

Step 1Step 2Step 3Step 4Step 5Step 6
DATA ANALYTICS SERIES:← Ch 1: What is DA← Ch 2: Types of DataCh 3: DA Process ←
RUNNING CASE STUDY

Throughout this chapter we follow one real-world investigation: an Indian e-commerce company whose revenue dropped 18% in August vs July. Each step shows exactly what the analyst does — with real SQL queries and decisions — to get from "revenue is down" to a specific, actionable finding.

1
Define the Question
What business problem are you actually solving?

Every analysis starts with a question — not with data. The question determines what data you need, which calculations matter, and what "done" looks like. Without a clear question, you will produce charts that nobody acts on.

A good analytics question has three qualities: it is specific (not "analyse sales" but "which product categories had a >15% MoM decline in July?"), it is answerable with available data, and it has a decision attached to it (someone will change something based on the answer).

In most Indian companies, these questions come from the business — a manager notices a trend and asks why, a finance team needs to explain a variance, or an operations head wants to know which delivery zones are dragging down OTIF.

TOOLS AT THIS STEP

No specific tool — this is a conversation with the business stakeholder

OUR CASE STUDY

Our e-commerce company's revenue dropped 18% in August vs July. The question: "Is the drop concentrated in a specific product category, region, or customer segment — and what happened differently in August vs July in that segment?"

COMMON MISTAKE

Starting with data exploration before defining a question. You will spend hours producing charts that answer questions nobody asked.

2
Collect the Data
Identify the sources and pull the data you need.

Once you know the question, you identify which data sources contain the answer. In Indian companies, data lives in many places: an ERP system (SAP, Oracle, Tally), a CRM (Salesforce, Zoho), a spreadsheet someone maintains manually, a database the tech team manages, or a cloud platform (Google Analytics, Meta Ads Manager).

Your job is to identify which tables and fields contain the relevant data, pull it into a working environment (SQL, Excel, Python), and check that you have the right scope (date range, geography, product lines).

One critical habit: document your data sources. Write down where each dataset came from, when it was pulled, and what the table or file contained. This lets you reproduce your analysis later and answer "where did this number come from?" when a stakeholder challenges your finding.

TOOLS AT THIS STEP

SQL (database queries), Excel (manual exports), Python (API calls or file imports), Power Query

OUR CASE STUDY

Query the orders database for August and July. Pull columns: order_date, category, city, customer_segment, revenue, returns. Also pull the marketing spend table to check if ad budgets changed between months.

COMMON MISTAKE

Pulling too much data "just in case." Collect only what you need for the specific question — more data means more cleaning time and more risk of distraction.

-- Collect August and July orders for the revenue decline analysis
SELECT
    DATE_FORMAT(order_date, '%Y-%m')  AS month,
    category,
    city,
    customer_segment,
    COUNT(*)                           AS order_count,
    SUM(amount)                        AS revenue,
    SUM(CASE WHEN returned = 1 THEN 1 ELSE 0 END) AS returns
FROM orders
WHERE order_date BETWEEN '2026-07-01' AND '2026-08-31'
GROUP BY
    DATE_FORMAT(order_date, '%Y-%m'),
    category, city, customer_segment
ORDER BY month, revenue DESC;
3
Clean the Data
Fix errors, handle missing values, and standardise formats.

Raw data is almost never ready to analyse. Common problems in Indian business data: city names spelled inconsistently ("Delhi", "delhi", "New Delhi", "NCR"), amounts stored as text with "₹" symbols and commas, dates in different formats across rows, duplicate records from system exports, missing values in key columns, and test orders mixed in with real ones.

Data cleaning is not glamorous, but it is the most important step for producing trustworthy results. An analysis built on dirty data produces confidently wrong answers — the worst possible outcome, because wrong numbers that look right cause bad decisions.

The goal is not perfect data — it is data that is clean enough that the errors that remain do not materially affect the conclusions.

TOOLS AT THIS STEP

SQL (deduplication, type conversion, NULL handling), Power Query (Excel/Power BI), Python pandas

OUR CASE STUDY

Found 3,400 rows where city = "delhi" (lowercase). Standardised to "Delhi". Found 120 rows with NULL category — traced to a data entry gap in August; excluded from category analysis but kept in total revenue calculation. Removed 45 test orders (identified by customer_id prefix "TEST_").

COMMON MISTAKE

Cleaning the same dataset twice. Build a reusable cleaning script or Power Query flow so the next analysis on the same source starts clean automatically.

-- Common data cleaning operations in SQL

-- 1. Standardise city names (case + spelling variations)
UPDATE orders
SET city = CASE
    WHEN LOWER(city) IN ('delhi', 'new delhi', 'ncr', 'delhi ncr') THEN 'Delhi NCR'
    WHEN LOWER(city) IN ('mumbai', 'bombay')                        THEN 'Mumbai'
    WHEN LOWER(city) IN ('bangalore', 'bengaluru')                  THEN 'Bangalore'
    ELSE city
END;

-- 2. Remove test orders
DELETE FROM orders WHERE customer_id LIKE 'TEST_%';

-- 3. Check for and handle NULLs in key columns
SELECT
    COUNT(*)                                         AS total_rows,
    SUM(CASE WHEN category IS NULL THEN 1 ELSE 0 END) AS null_category,
    SUM(CASE WHEN amount   IS NULL THEN 1 ELSE 0 END) AS null_amount,
    SUM(CASE WHEN city     IS NULL THEN 1 ELSE 0 END) AS null_city
FROM orders
WHERE order_date BETWEEN '2026-07-01' AND '2026-08-31';

-- 4. Remove duplicates (keep the row with the latest updated_at)
DELETE o1 FROM orders o1
INNER JOIN orders o2
    ON o1.order_id = o2.order_id AND o1.updated_at < o2.updated_at;
4
Analyse the Data
Find patterns, calculate metrics, and answer the question.

With clean data, you run the calculations that answer your question. Analysis is not random exploration — it is a structured investigation of the hypothesis you formed in step 1.

For a revenue decline investigation: start with the top-level number (total revenue by month). Then break it down by each dimension (category, city, customer segment) to find where the decline is concentrated. Then compare what was different in August vs July in that segment — price, volume, marketing spend, competitor activity, or product availability.

The output of analysis is not charts — it is findings. A finding is: "Electronics revenue dropped 34% in August, concentrated in Tier-1 cities. Electronics volume was flat, but average order value fell from ₹8,200 to ₹5,400 — suggesting a price-driven cause, not a demand cause."

TOOLS AT THIS STEP

SQL (aggregations, JOINs, window functions), Excel (pivot tables), Python (pandas groupby, describe)

OUR CASE STUDY

MoM revenue by category: Electronics -34%, Apparel +4%, FMCG +1%. Electronics volume: -2% (nearly flat). Electronics average order value: -31%. Conclusion: the decline is a price/discount issue, not a demand issue.

COMMON MISTAKE

Reporting numbers without a conclusion. "Electronics revenue was ₹2.1 crore in August vs ₹3.2 crore in July" is a data point. "Electronics revenue fell 34% MoM because average order value dropped — not because demand fell" is an insight.

-- Revenue analysis: MoM comparison by category
SELECT
    category,
    SUM(CASE WHEN month = '2026-07' THEN revenue ELSE 0 END)       AS july_revenue,
    SUM(CASE WHEN month = '2026-08' THEN revenue ELSE 0 END)        AS aug_revenue,
    ROUND(100.0 * (
        SUM(CASE WHEN month = '2026-08' THEN revenue ELSE 0 END) -
        SUM(CASE WHEN month = '2026-07' THEN revenue ELSE 0 END)
    ) / NULLIF(SUM(CASE WHEN month = '2026-07' THEN revenue ELSE 0 END), 0), 1)
                                                                    AS mom_pct_change,
    -- Volume vs value breakdown
    SUM(CASE WHEN month = '2026-07' THEN order_count ELSE 0 END)   AS july_orders,
    SUM(CASE WHEN month = '2026-08' THEN order_count ELSE 0 END)    AS aug_orders,
    ROUND(
        SUM(CASE WHEN month = '2026-07' THEN revenue ELSE 0 END) /
        NULLIF(SUM(CASE WHEN month = '2026-07' THEN order_count ELSE 0 END), 0)
    , 0)                                                             AS july_aov,
    ROUND(
        SUM(CASE WHEN month = '2026-08' THEN revenue ELSE 0 END) /
        NULLIF(SUM(CASE WHEN month = '2026-08' THEN order_count ELSE 0 END), 0)
    , 0)                                                             AS aug_aov
FROM monthly_summary     -- the aggregated table from step 2
GROUP BY category
ORDER BY mom_pct_change ASC;   -- worst performers first
5
Visualise and Communicate
Present findings so the right person can understand and act.

A correct insight that nobody understands is worthless. The communication step translates your analytical findings into a format that the decision-maker — a category manager, a VP of operations, a finance director — can absorb in 5 minutes and act on.

This does not always mean a dashboard. Sometimes it is a 3-slide deck. Sometimes it is a one-paragraph WhatsApp message. The format depends on the audience and the urgency. A real-time operational dashboard is different from a monthly review presentation which is different from an ad hoc answer to a manager's question.

The discipline in this step is leading with the conclusion. Do not make the audience read 6 charts and figure out what it means. Start with: "Electronics revenue fell 34% MoM — the cause is a drop in average order value, not in order volume. Here is the evidence and the recommended action."

TOOLS AT THIS STEP

Power BI (dashboards), Tableau, Excel charts, Google Slides, simple email summary

OUR CASE STUDY

For this analysis: a 2-slide summary. Slide 1: headline finding in one sentence + a bar chart showing MoM change by category. Slide 2: the volume vs AOV breakdown showing it is a price issue + the recommended action (review August discount policy).

COMMON MISTAKE

Too many charts, not enough conclusion. Every visual should support the main finding. Remove any chart that does not contribute to the answer.

6
Make a Decision and Measure
Act on the insight — and track whether it worked.

The analytics process is not complete at a dashboard or a presentation. It is complete when a decision has been made and implemented, and when there is a plan to measure whether the decision produced the expected outcome.

This is the step most analysts skip — and it is also the step that builds your reputation and your career. When you close the loop (the analysis led to a decision, the decision led to a measurable outcome, and you tracked it), you demonstrate that analytics creates real value, not just reports.

For the electronics revenue case: the recommended action might be to revise the August discount policy for Q3. The follow-up measurement: electronics average order value in September vs August. If it recovers toward the July level, the hypothesis was correct and the action worked.

TOOLS AT THIS STEP

Same tools as analysis — set up a monitoring dashboard or schedule a follow-up query

OUR CASE STUDY

Decision: remove the flat-discount mechanic from electronics in September and replace with a category-specific promotion that protects AOV. Measurement: electronics AOV tracked weekly in September. Checkpoint: review on 30 September.

COMMON MISTAKE

Delivering the analysis and moving on. If you never track whether your recommendation was right, you learn nothing, the business does not trust analytics, and your career does not grow.

-- Step 6: Follow-up measurement query (run in September)
SELECT
    DATE_FORMAT(order_date, '%Y-%m-%d')   AS week_start,
    ROUND(SUM(amount) / COUNT(*), 0)      AS electronics_aov,
    COUNT(*)                              AS order_count,
    SUM(amount)                           AS revenue
FROM orders
WHERE category   = 'Electronics'
  AND order_date BETWEEN '2026-09-01' AND '2026-09-30'
GROUP BY DATE_FORMAT(order_date, '%Y-%m-%d')
ORDER BY week_start;
-- Compare to: July benchmark AOV ₹8,200 | August (problem) AOV ₹5,400
-- Target for September: ≥ ₹7,000

The Complete Process at a Glance

1
Define the Question What business problem are you actually solving?
2
Collect the Data Identify the sources and pull the data you need.
3
Clean the Data Fix errors, handle missing values, and standardise formats.
4
Analyse the Data Find patterns, calculate metrics, and answer the question.
5
Visualise and Communicate Present findings so the right person can understand and act.
6
Make a Decision and Measure Act on the insight — and track whether it worked.
Continue the Series
← Ch 1: What is DA← Ch 2: Types of DataCh 4: SQL Tutorial →Full Roadmap →

Frequently Asked Questions

What are the steps of the data analytics process?

The data analytics process has 6 steps: (1) Define the question — what business problem are you solving? (2) Collect the data — identify sources and pull the relevant data. (3) Clean the data — fix errors, handle missing values, standardise formats. (4) Analyse the data — apply calculations, aggregations, and statistical methods to find patterns. (5) Visualise and communicate — present findings in charts, dashboards, or a summary that non-technical stakeholders can act on. (6) Make a decision and measure — the analysis must lead to a specific action, and the outcome of that action should be tracked. Most beginners spend too long at step 3 and skip step 6 entirely.

How long does the data analytics process take?

The time depends entirely on the complexity of the question and the state of the data. A simple analysis — for example, which product category had the highest return rate last month — might take 30 minutes in SQL and Excel if the data is already clean. A complex analysis — predicting customer churn using 18 months of transaction data — might take 2–3 weeks including data collection, cleaning, model building, and validation. In practice, data cleaning (step 3) takes the most time — often 50–70% of the total time on a new dataset. Analysts who have worked with a data source before move faster because they know where the quality problems are.

What is the most important step in data analytics?

Step 1 — defining the question — is the most important and most frequently skipped. Every other step depends on it. If the question is vague ("analyse sales") the analysis will be unfocused and the insight will be unusable. A precise question ("which product categories had a >15% MoM revenue decline in the last 3 months, and is the decline concentrated in specific cities?") guides exactly what data to collect, which columns to clean, what calculations to run, and what the answer looks like. Analysts who start with clear questions consistently produce more actionable output than those who start with data exploration and hope to find something interesting.

What is data cleaning and why does it take so long?

Data cleaning is the process of fixing errors, inconsistencies, and gaps in raw data so it can be analysed correctly. Real-world data is almost always dirty: amounts stored as text with currency symbols ("₹1,200"), city names with typos ("Delhi" and "delhi" and "New Delhi" all meaning the same thing), dates in inconsistent formats ("15-08-2026" and "Aug 15 2026" in the same column), duplicate rows from multiple system exports, and missing values where a field was left blank. Data cleaning takes a large proportion of analysis time because fixing one issue often reveals another. Experienced analysts know the common issues in their data sources and build reusable cleaning pipelines so they only solve each problem once.

EVIKA ACADEMY · NOIDA SECTOR 51

Apply this process on real Indian data with a mentor

Our structured programme guides you through the full analytics process — from question to decision — on live business datasets. Free demo class available.

Book Free Demo Class →
🎓 Free Demo Class — Online & Offline · Noida Sector 51