Đại học Kinh tế Quốc dân – National Economics UniversityMICRO4ASIA
🏆 Arena
Sign inSign up
MICRO4ASIAThe six micro-credentials

Courses are delivered on the Limio learning platform. Limio

← Data Visualization in Business

You are viewing a public preview

Sign in to save your progress, do assignments, join discussions and get feedback.

Sign in
Module 1 — Overview of Data Visualization in Business

1.5 · Data Visualization Process

Print / Save as PDF

In this lesson

Identifying problems and analytical questions; determining information needs; collecting and organizing data; selecting visual methods; building, checking, refining, interpreting and communicating visual outputs.

Learning outcomes

  • LO.2: Explain how analytical thinking, design principles and the visualization process help identify business questions and communicate information.
  • LO.6: Select, build and refine charts that fit the analytical objective and the data.
  • LO.9: Select and justify visualization methods and tools for a business problem.

The lecture slides for this lesson are below.

Practice for Module 1

Review the data concepts and data types; read about visualization principles, chart selection and the visualization process; for a few business questions from your own work or study, decide which chart would answer each one and explain why. (About 12 hours of independent study.)

Study notes

By the end of this lesson you can:

  • Describe the four stages of the data visualization process and why it is a cycle.
  • Turn a broad business problem into specific analytical questions and information needs.
  • Plan the data, metrics and visual methods needed to answer each question.
  • Check, refine, interpret and communicate a visual output before it reaches decision-makers.

Key idea: Visualization is a process, not a single step. You define requirements, prepare data, analyse and visualise, then iterate and refine until the chart reliably answers the business question.

The process as a cycle

The lecture presents the data visualization process as four stages arranged in a circle, with an arrow labelled "Iterate & Refine" linking the end back to the start:

StageFocusTypical output
1. Define requirementsObjectives and scopeBusiness problem, analytical questions, audience, metrics
2. Collect and prepare dataData sources and cleaningA clean, well-structured dataset
3. Analyse dataKey metrics and trendsCalculations, comparisons, patterns, outliers
4. Visualise dataDesigning charts and dashboardsCharts or a dashboard that answer the questions

It is a cycle because the first version is rarely right. Building a chart often reveals a data problem (go back to stage 2) or a better question (go back to stage 1).

Stage 1: define requirements

Start with the problem, then break it into analytical questions that data can answer. "Profit is disappointing" is a problem. Questions could be "Which categories have the lowest profit ratio?", "Is profit lower on orders with higher discounts?" and "Has profitability changed over time?"

Then define information needs: which metrics (Sales, Profit, profit ratio), at what level of detail (order line, customer, month, province), for which period, and for which audience. A director needs a few headline KPIs; an analyst needs detail. Agree on scope early, so you do not chart everything.

Stage 2: collect and prepare data

Identify the sources (for example, order, customer and product tables), check how they link, and clean the data: fix inconsistent labels, handle missing values and duplicates, and check value ranges. Module 2 covers this in Tableau and Tableau Prep. Poor preparation causes double counting and wrong totals that no chart design can repair.

Stage 3: analyse data

Compute the agreed metrics, compare groups, look at trends over time, and look for patterns and outliers. Ask whether a pattern is real and large enough to matter, and whether another factor could explain it.

Stage 4: visualise data

Select a visual method for each question using the chart families from lesson 1.4 (comparison, trend, composition, relationship, distribution, geographic). Build the chart, then check it:

  • Do totals match the source data?
  • Are scales honest and axes labelled?
  • Does the chart follow the clarity, accuracy and efficiency requirements from lesson 1.3?

Refine colours, labels, sorting and titles. Interpret what the chart shows in one or two sentences, including limits ("this is correlation, not proof of cause"). Communicate the result in the form the audience needs: a single chart in a report, a dashboard or a data story (Module 5).

Iterate and refine

Show a draft to a user early. Typical feedback ("I need this by region", "what does this colour mean?") sends you back to an earlier stage. Each loop should make the output more accurate and easier to use.

Worked example

The sales director of the course's office-supplies retailer says: "Our profit margin feels low. Find out why."

  1. Define requirements. Problem: low margin. Questions: (a) Which Category and Sub-Category have the weakest profit ratio? (b) Does profit ratio fall as Discount rises? (c) Is the pattern the same in every Region? Metric: profit ratio = SUM(Profit) / SUM(Sales). Audience: the director, who needs a short answer with a recommendation.
  2. Collect and prepare. Use Orders (Sales, Profit, Discount, Order Date), Product (Category, Sub-Category) and Customer (Region, Segment). Check that product and customer IDs match and that there are no duplicate order lines.
  3. Analyse. Calculate profit ratio by Category and Sub-Category, and by Discount level, and compare across Regions.
  4. Visualise. (a) Sorted bar chart of profit ratio by Sub-Category, with negative values in an accent colour. (b) Line or bar chart of profit ratio by Discount level. (c) The same bar chart with Region as small multiples or a filter.
  5. Check and refine. Confirm the overall total of Sales matches the source. Make sure the profit ratio is aggregated correctly, not an average of row-level ratios. Write titles that state the finding.
  6. Interpret and communicate. Write two or three sentences on what drives the low margin and one recommendation, for example a discount cap for the weakest sub-categories, and present it to the director.
  7. Iterate. If the director asks about specific customers, return to stage 1 with the new question.

Common mistakes

  • Starting in the tool. Opening Tableau before writing down the question produces many charts and no answer.
  • Skipping the check. Totals that do not match the source destroy credibility in the meeting.
  • Treating the first chart as final. Expect to iterate after feedback.
  • Interpretation without limits. State what the chart cannot show, such as causation or missing periods.

Summary

  • The process has four stages: define requirements, collect and prepare data, analyse, visualise.
  • It is a cycle: iterate and refine based on checks and feedback.
  • Good requirements turn a vague problem into specific questions, metrics and an audience.
  • Every chart must be built, checked, refined, interpreted and communicated.
  • The right output form depends on the audience: chart, dashboard or story.

Flashcards · Data Visualization Process

8 words
WordMeaningExample
  • Data visualization process

    A cycle of defining requirements, collecting and preparing data, analysing and visualising, repeated through iteration.

    From 'margin is low' to a sorted profit-ratio chart.

  • Define requirements

    The first stage: set objectives, scope, analytical questions, metrics and audience.

    Question: which sub-categories have the lowest profit ratio?

  • Analytical question

    A specific question that available data can answer, derived from a broader business problem.

    Does profit ratio fall as Discount rises?

  • Information need

    The metrics, level of detail, period and audience required to answer a question.

    Monthly profit ratio by Region for 2023–2025.

  • Collect and prepare data

    The stage of gathering sources and cleaning, standardising and linking them into an analysis-ready dataset.

    Link Orders to Product on Product ID.

  • Iterate and refine

    Returning to earlier stages after checks or feedback to improve accuracy and usefulness.

    Director asks for a region view; add it.

  • Chart check

    Verifying totals, scales, labels and design principles before a chart is shared.

    Total Sales in the chart equals the source total.

  • Interpretation

    A short statement of what a chart shows and its limits, linked to the business question.

    'Higher discounts coincide with lower profit; not proof of cause.'