This repository contains a fictional coffee chain sales dataset and a starter Jupyter Notebook for the Data Visualization Ethics Challenge.
In this challenge, youβll practice applying ethical design principles by fixing two intentionally bad charts.
The goal is to identify misleading or unclear design choices and create clear, accurate, and honest visualizations that follow best practices.
You will:
- Identify problems with each bad chart.
- Redesign them to follow ethical visualization guidelines.
- Document your changes and explain why they improve the chart.
coffee_sales.csvβ Fictional dataset containing multiple years of sales data for a coffee chain.ethics_challenge.ipynbβ Starter notebook containing:- The dataset import code
- Two intentionally bad charts
- Prompts for you to analyze and improve each chart
- Cells for creating your improved visualizations and writing explanations
git clone https://github.com/CodeYouOrg/DA_M3_DataVizChallenge.gitYou can open directly into VS Code via the terminal:
code DA_M3_DataVizChallenge- Review each bad chart.
- Write down everything you find wrong with it in the provided Markdown cell.
- Create an improved chart using the dataset.
- Explain what you changed and why.
Save your updated .ipynb file, then commit and push your changes:
git add data_viz_ethics_challenge.ipynb
git commit -m "Completed Data Visualization Ethics Challenge"
git pushSubmit the GitHub repository link as your final project.
The dataset contains fictional sales data for a coffee chain across multiple years and locations.
Columns include:
YearMonthRegionStoreProductSales (in millions)Marketing Spend (in millions)
When redesigning your charts:
- Use the correct variables for the message you want to communicate.
- Start the y-axis at zero unless you have a transparent reason not to.
- Use neutral colors unless highlighting a legitimate difference.
- Add clear axis labels, a descriptive (neutral) title, and the data source.
- Avoid βchartjunkβ - unnecessary 3D effects, heavy gridlines, or distracting colors.
- Always provide context and avoid misleading design choices.
Once youβve committed and pushed your changes, submit your repository link in OpenClass.
Have fun, and remember: Good charts tell the truth.