Learning paths
CluedIn learning paths provide role-based guidance for gradually learning the platform through realistic workflows rather than disconnected feature tours.
These learning paths are designed to complement the existing product documentation. They do not replace the reference articles. Instead, they connect the reference material into a progressive route through the instance so that a learner can understand not only what each feature does, but also when and why it should be used.
Available courses
Design principles
These learning paths follow four principles:
- Walk the instance in the same order work usually happens: ingest, map, process, inspect, improve, govern, and publish.
- Keep roles distinct: the Data Steward is primarily responsible for operational quality and trust in records; the Data Architect is primarily responsible for shaping the model, mappings, rules, and downstream behavior.
- Use the product as it is documented today: modules point learners to the strongest current documentation sections instead of relying on stale or outdated material.
- Practice with real product surfaces: each module tells the learner where to go in the UI, what to look for, what good looks like, and what to hand off to the next role.
How to use these learning paths
- Work through the modules in order.
- Read the linked product documentation alongside each module.
- Practice in a non-production environment first.
- Keep notes on what felt unclear in your own instance so you can adapt the course to your organization’s data model, naming, and governance conventions.
Suggested audience split
- Choose the Data Steward path if your main responsibility is reviewing records, resolving quality issues, investigating duplicates, validating data, and operating recurring governance loops.
- Choose the Data Architect path if your main responsibility is defining business domains, vocabularies, mappings, identifiers, relations, rules, enrichers, streams, and release discipline across environments.