Understanding the Data Analysis Process and the Data Life Cycle#

🌱 Foundations 🔄 The Analysis Process & Data Life Cycle Lesson 008

Important

✨ AI-generated content. This page was written with the assistance of an AI language model and is provided as a learning aid. Despite careful review, it may still contain mistakes, omissions, or out-of-date information. Whether you are new to the topic, a team lead, or a senior practitioner, treat it as a starting point rather than an authoritative reference: read it critically and independently verify anything you act on (code, commands, figures, and factual claims) against official documentation and primary sources before relying on it.

Two journeys, often confused#

Two sequences run through every data project, and they are not the same. The data analysis process (Ask, Prepare, Process, Analyze, Share, Act) describes what the analyst does to answer a question. The data life cycle describes what happens to the data itself, from the moment someone decides to collect it to the day it is deleted. One follows the worker; the other follows the material. Keeping them straight prevents a common muddle — and interviewers like asking about exactly this distinction.

The data life cycle#

A widely taught version has six stages:

Plan. Before any collection: decide what data is needed, how it will be managed, who is responsible for it, and under what rules.
Capture. Bring the data into existence or into the organisation — collecting from sources, sensors, forms, or external providers.
Manage. Store, secure, organise, and maintain it so it stays usable: where it lives, how it is backed up, who may access it.
Analyze. Use it — the stage where the entire analysis process happens.
Archive. Move data no longer in active use into long-term storage, still retrievable if needed.
Destroy. Delete it — securely and deliberately — when retention rules or privacy obligations say its time is up.

The exact stages and names vary by company and industry; regulated sectors add compliance checkpoints. The shape, though — from planned birth to deliberate death — is universal.

How the two interlock#

The whole six-phase analysis process lives inside one stage of the life cycle: Analyze. Conversely, the analyst constantly depends on the other stages. Good planning upstream determines whether the data you need even exists; good management determines whether you can find and trust it; archive and destroy determine whether last year’s comparison data is still there — or legally must not be. When a lesson later in this course says “check where the data came from,” it is sending you back up the life cycle.

Why analysts should care about the whole cycle#

Because the biggest analysis problems are usually born outside the analysis. A question that cannot be answered often traces to a Plan stage that never anticipated it; dirty data traces to Capture; a missing year traces to Destroy. Analysts who understand the life cycle diagnose these quickly — and, when consulted early, help design collection so the next question is answerable.

The caveat#

Life-cycle diagrams look tidier than reality: data gets copied, forked into spreadsheets, and half-archived, so the same record can sit at several stages at once. Treat the cycle as the intended governance path, and expect to do some detective work about where a given dataset really is on it.

Hint