Module 12 Lesson: Interactive Visuals, Dashboards, and Capstone Story
Let us begin
The final module brings the course together.
You have learned how to ask a data question, inspect data, clean it, summarize it, join it, analyze time, explore patterns, and build static and statistical charts.
Now you will add useful interactivity and package a final analysis story.
When interactivity helps
Interactivity helps when the reader needs to:
- inspect exact values;
- filter or compare groups;
- hover for detail;
- explore many categories;
- move from overview to detail.
Interactivity does not help when the analysis is unclear. A weak chart with hover labels is still weak.
Plotly Express basics
Plotly Express creates interactive charts with compact code.
import plotly.express as px
fig = px.line(
weekly,
x="week",
y="total_minutes",
color="course_name",
title="Weekly Practice Minutes by Course"
)
fig.show()
This creates an interactive line chart with hover details and a legend.
Interactive scatter plot
fig = px.scatter(
df,
x="quiz_attempts",
y="practice_minutes",
color="status",
hover_data=["course_name", "week_number"],
title="Practice Minutes by Quiz Attempts"
)
fig.show()
Hover data should help the reader understand a point. Do not include every column.
Interactive bar chart
fig = px.bar(
course_summary,
x="course_name",
y="learner_count",
color="course_level",
title="Learners by Course"
)
fig.show()
Use color when it carries meaning.
Facets and animation caution
Plotly can facet and animate. Use these features carefully.
Facets can help compare groups. Animation can distract if the reader cannot pause and inspect.
Ask:
> Does this interaction make the evidence clearer?
If not, use a simpler chart.
Dashboard-style structure
A simple analysis dashboard or report should follow a clear order:
- Main question.
- Short answer.
- Data used.
- Cleaning summary.
- Finding 1.
- Finding 2.
- Finding 3.
- Interactive detail.
- Limits.
- Next steps.
The reader should not have to guess what matters.
Capstone story
Your final story should include:
- what you asked;
- what data you used;
- how you cleaned it;
- what you found;
- which visuals support the findings;
- what the data cannot prove;
- what should happen next.
A strong story is not long because it includes everything. It is strong because it includes the right evidence.
Reproducibility
Before submission:
- run the notebook top to bottom;
- check relative paths;
- include the data dictionary;
- include the cleaning log;
- include chart critique notes;
- remove secrets and local absolute paths;
- make sure conclusions match evidence.
Mini capstone frame
Main question:
> Which course activities and support signals appear most connected with healthy learner progress, and where should the academy improve the learner experience?
Careful short answer:
> In the synthetic data, steady practice activity and faster support responses appear connected with healthier progress. The analysis does not prove cause. It suggests areas for closer review: early practice support, support-topic patterns, and course sections with lower engagement.
Takeaway
You now have the full data analysis workflow: question, data, cleaning, transformation, exploration, visualization, interactivity, and story. The next production work is to turn these text modules into executable notebooks, datasets, and a public course shell.
