Concept Maps: How to Enter the 21 Modules of the Course
Professional map of the GinnyTech course: 21 modules and 236 core lessons to navigate fundamentals, applications, technical stack, analytical rigor, and AI data work.
What you will learn
- Understanding the updated course structure in 21 modules
- Connecting modules, phases, and professional outputs of the path
- Using the map to choose what to study without losing direction
Mappe concettuali: come entrare nei 21 moduli del corso
Aprire il corso vuol dire trovarsi davanti a 21 moduli, dal tracking e le metriche fino all’AI e all’agentic AI. È un panorama abbastanza ampio da disorientare chi studia, e di solito porta a uno di due errori. Il primo è seguire ogni modulo in modo passivo, senza una strategia. Il secondo è saltare da un argomento all’altro inseguendo urgenze apparenti. Tutti e due consumano energia e impediscono di costruire competenze solide.
Il problema da risolvere
Chi vuole migliorare nel lavoro sui dati si trova davanti a dashboard, SQL, modelli, pipeline e strumenti AI. Senza una mappa, finisce per accumulare conoscenze scollegate e non riesce a legare le fasi agli output. La domanda che conta non è “so ripetere la teoria?”, ma: quale decisione migliora se applico bene questa lezione? Chi studia senza orientamento rischia scelte costose, come lanciare feature premature o spostare budget senza basi causali.
Un modello per governare lo studio
Per orientare lo studio basta una griglia in tre passaggi.
| Level | Guiding question | Expected output |
|---|---|---|
| Phenomenon | What is really happening? | Scope, segments and assumptions |
| Evidence | Which data would change our opinion? | Metrics, observations and guardrails |
| Decision | What will we do if the signal holds? | Action, owner, timing and stop criteria |
La griglia tiene insieme i due estremi che fanno perdere tempo: la teoria fine a se stessa e l’operatività senza ragionamento.
Formalizzare la catena decisionale
La lezione prende la forma di una catena decisionale.
| Element | Operational Definition | Quality control |
|---|---|---|
| Input | Notes, maps, checklists, exercises, projects, and feedback | Declared source, period, granularity, and completeness |
| Hypothesis | Expected relationship between study behavior, output, and competence | Assumptions written before the analysis |
| Metric | Continuity, completed exercises, artifact quality, ability to explain choices | Explicit denominator, segment and time window |
| Guardrail | What must not worsen while optimizing | Understanding, rigor, sustainability, and autonomy |
| Decision | What to study now, what to postpone, outputs to produce | Owner, deadline and review criteria |
Effective formalization lets someone else reconstruct and challenge the reasoning without ambiguity.
Example or case study
Consider a weekly review among student, mentor, and reviewer to decide whether to move on to advanced modules M20 and M21 (AI and agentic AI). The student knows SQL, metrics, and dashboards but hasn’t yet produced a decision memo with checks on leakage and drift.
Before reaching that point, they must connect Directions in Analytics, Philosophical Foundations of Data Analysis, statistics, SQL, and analytics engineering to a concrete decision.
| Observation | Prudent interpretation | Action |
|---|---|---|
| The student wants to use AI on a real case | Valid motivation, but lacks rigor | Check foundations on M3, M14, M17, and M19 |
| Has a dataset and a business question | Positive operational signal | Prepare a brief with baseline and guardrails |
| Does not define owner or stopping criteria | Premature automation | Postpone agentic AI and work on the decision memo |
The goal isn’t the perfect answer but making the study decision defensible.
Lab / exercise
| Level | Activities | Output |
|---|---|---|
| Basic level | Summarize your professional goal and choose 5 priority modules | Mini learning brief |
| Intermediate level | Design an 8-week sequence with practice, reviews, and deliverables | Study plan with deliverables |
| Research-grade level | Write a memo justifying when to introduce M20-M21 in your path | Revisable decision memo |
Recommended datasets and materials: Study schedule, current portfolio, notes from completed lessons, real dashboard or analysis, AI use case, list of risks to monitor.
Typical mistake to avoid
The most common mistake is treating “Concept Maps” as a one-time read and then forgetting them. Instead, consult the map whenever you change goals, lose continuity, or want to jump to advanced tools.
A practical method: before starting a module, write three lines: the skill to build, the output to produce, and the previous module you should be able to explain. If any of these are missing, you’re probably studying out of curiosity, not for transferable skill.
Quiz or checkpoint
- How many phases make up the course path?
- Which phase connects roles, causality, AI-assisted data work, and agentic AI?
- Why do M20 and M21 come after modules on metrics, SQL, statistics, analytics engineering, and causality?
- What output would you use to prove you’ve mastered a phase?
- What risk do you run if you use AI or agentic AI without clear data and ownership?
If you can’t answer specifically, return to the real problem before proceeding.
Conclusions
This map doesn’t simplify the course; it makes it manageable. By following the phased progression, the path remains comprehensive yet clear, advanced yet practical, technical yet focused on real-world work.
You’ve mastered the map when you can use it to explain the path without jargon, apply it to your professional goals, and justify a study sequence with outcomes, limitations, and next checkpoints.
1.How many phases make up the course path?
2.How many core modules and lessons does the path currently contain?
3.Why do M20 and M21 come at the end of the path?
Related Path
Lessons to read together
Questi collegamenti portano la lezione dentro il resto del corso: basi da riprendere, passaggi successivi e connessioni tematiche tra moduli.